[stevorkz]

Hey

I installed gitbrews otheros and gave red ribbon rc5 a try and loved it.
However id rather have rebug 3.55.2 otheros so i updated to rebug no sweat and found petitboot was still there.Cool...my problem is i want to start completely afresh and go back to a time when my ps3 had no trace of otheros.

My reason for this is after running boot_other os package in order to boot linux i get the "Connect controller and press ps button" screen and i still get it when running boot_gameos package. After pressing the ps button i get the "the system software cannot run correctly" screen. I press the ps button then it reboots and i can run the reboot package and get into linux fine but that "connect controller" screen was never there previously and i dont like it cos its a waste of time.

The thing that really worries me is what if I need to get into recovery one day and cant boot my gameos. Then im skrewed because the only way i can get into recovery at the moment is this : Run boot_gameos, go through the annoying "Connect controller" screen and then the "system software cannot run correctly" screen, it reboots to gameos, then i shutdown and do the hold power button in thing for recovery. Thats the only way. After that If i want to run linux i have to run boot_otheros and I get the same annoying screens that never was there with my gitbrew otheros. I even got the screens when running setup_flash_for_otheros.pkg which was the first package I ran after installing rebug through recovery

Im sure restoring everything back the way it was when i had kmeaw then trying otheros again with rebug otheros would sort it out. So how would I make it so otheros was never there?

Thanx in advance. Going nuts here

PS: I even tried formatting my hard drive on my pc and still nothing. Im sure it has to do with the flash although Im no pro

[DarkMessiah]

maybe try to install the ofw first then install the rebug maybe that will help

[Pockets69]

Format your hdd low level formatting, not just simple format, it will work.

[nevik]

Originally Posted by stevorkz Hey I installed gitbrews otheros and gave red ribbon rc5 a try and loved it. However id rather have rebug 3.55.2 otheros so i updated to rebug no sweat and found petitboot was still there.Cool...my problem is i want to start completely afresh and go back to a time when my ps3 had no trace of otheros. My reason for this is after running boot_other os package in order to boot linux i get the "Connect controller and press ps button" screen and i still get it when running boot_gameos package. After pressing the ps button i get the "the system software cannot run correctly" screen. I press the ps button then it reboots and i can run the reboot package and get into linux fine but that "connect controller" screen was never there previously and i dont like it cos its a waste of time. The thing that really worries me is what if I need to get into recovery one day and cant boot my gameos. Then im skrewed because the only way i can get into recovery at the moment is this : Run boot_gameos, go through the annoying "Connect controller" screen and then the "system software cannot run correctly" screen, it reboots to gameos, then i shutdown and do the hold power button in thing for recovery. Thats the only way. After that If i want to run linux i have to run boot_otheros and I get the same annoying screens that never was there with my gitbrew otheros. I even got the screens when running setup_flash_for_otheros.pkg which was the first package I ran after installing rebug through recovery Im sure restoring everything back the way it was when i had kmeaw then trying otheros again with rebug otheros would sort it out. So how would I make it so otheros was never there? Thanx in advance. Going nuts here PS: I even tried formatting my hard drive on my pc and still nothing. Im sure it has to do with the flash although Im no pro

If you need to get to recovery menu and petitboot is loading go to cli and type "ps3-flash-util -g" or "ps3-boot-game-os" without the quotes. This will clear the flag for petitboot and let you reboot in to recovery mode. then just install_otheros.pkg again to reset the flag.

hope this helps.

[stevorkz]

Originally Posted by nevik If you need to get to recovery menu and petitboot is loading go to cli and type "ps3-flash-util -g" or "ps3-boot-game-os" without the quotes. This will clear the flag for petitboot and let you reboot in to recovery mode. then just install_otheros.pkg again to reset the flag. hope this helps.

Thanx nevik. I'll give it a try...
************* [ - Post Merged - ] *************

Originally Posted by Pockets69 Format your hdd low level formatting, not just simple format, it will work.

Thanx gna give this a try rather. Says its gna take 9 hours is that normal? Or do you mean in the pc?

[stevorkz]

Ok so I just did a low level format on the pc using Hard Disk Drive Low Level Format (nice app I might add and its free), slapped the drive back in the ps3 and was greeted with the same annoying thing. "Connect controller and press ps button" then the "The system software cannot run correctly" screen

[haz367]

i also played arround with it..and had same issues..also other hdderrors wich indeed HDD low level format worked great
eg: "updating firmware 100%-reboots and the same thing again/kind looping...


anyway, i always put stuff that worked on a txtfile, so give it a shot to have clean hdd

Format OtherOS drive – Clean state HDD via PC – Disc Managment – Rightclick HDD – "new simple volume" – Quik format Format HDD again with FAT32formatter HDD back into PS3 PS3 formats the drive and re-install firmware: OFW3.55 OtherOS 20GB partition is not removed at this point XMB – System – Restore PS3 Formats and restore drive to DEFAULT HDD = clean – 20GB partition removed Install Rebug 3.55 OtherOS/rebug update package 0.2 Recovery mode – Restore PS3 – 20GB OtherOS partition created

that should do it

ps: anyone knows and howto fix the "system did not shutdown correctly on rebug otheros", everything installed correctly+updaate package0.2 to fix crash issues on exit app/game

or is it normal behaviour with oheros installed and booting back into gameos?
thx anyway..

[stevorkz]

Originally Posted by haz367 i also played arround with it..and had same issues..also other hdderrors wich indeed HDD low level format worked great eg: "updating firmware 100%-reboots and the same thing again/kind looping... anyway, i always put stuff that worked on a txtfile, so give it a shot to have clean hdd that should do it ps: anyone knows and howto fix the "system did not shutdown correctly on rebug otheros", everything installed correctly+updaate package0.2 to fix crash issues on exit app/game or is it normal behaviour with oheros installed and booting back into gameos? thx anyway..

Thanx alot dude I'll give that a shot and report back. After doing what @Pockets69 told me to about low level formatting I put the drive in and as I stated the same thing happened. However if it does help, that only happened if I simply turned the ps3 on. If I did the whole recovery holding the power button down thing it gave me the "Connect controller" screen and went into recovery and I was able to see the familiar recovery options including "system update". So I updated to 3.55 OFW and tried the power button thing again just incase and got into recovery fine once again. So I installed kmeaw and same thing. Worked like a charm. THEN...I installed rebug 3.55.2 otheros and ran the setup_flash_for_otheros.pkg which gives me 3 beeps as it always does followed by the annoying "connect controller" and "The system software cannot run correctly" screens. I think I'll give your method a go @haz367 and then I'll give up. Has anyone else had this kind of problem or know of it?

[haz367]

the connect controller message you are getting is unknown to me, you installed rebugs update package 0.2 to get rid of the errors on rebug otheros? otherwise i have no clue there, a full format like above should get it going again, although it may look a hassle, i never had to "full" low level format a ps3 hdd so can't speak for it how long it takes, the above is quite fast

or maibe NAND console error?, the install is atleast different from NOR(the vflash files..)