I'm trying to install red_ribbon_rc6 on me 3.55 ps3.
I have encountered TOO many problems to count and right now i have gotten up to the part where i am in petitboot mode and have entered "cd /tmp/petitboot/mnt/sda1/"
and "./create_hdd_region.sh", but when i re-reboot it just gives me the same options of "boot gameOS, Set video mode and exit to shell".
What on earth can i do? I am using a Fat NOR and on rebug 3.55.2 20gig partition.
I suppose you noticed that your output reports number of free sectors = 0
Did you perform the rebuild database after you installed the otheros pup? What size is your hdd and which firmware pup did you use i.e. the size of the gameos/otheros partitions? If you would report the exact steps you have followed, it might be possible to track any possible mistake.
I suppose you noticed that your output reports number of free sectors = 0
Did you perform the rebuild database after you installed the otheros pup? What size is your hdd and which firmware pup did you use i.e. the size of the gameos/otheros partitions? If you would report the exact steps you have followed, it might be possible to track any possible mistake.
Thanks heaps for your help.
So i installed the stock rebug 3.55.2 20gb partition other os CFW on my 40gb fat ps3 that has a 1t hdd.
I then rebuilt the database.
installed and booted all 4 ps3light applications. All of which beeped and sent me to a screen saying that the console couldn't start and told me to re-install 3.55 or pres PS button to try another restart. I restarted and all was good.
I then went into petitboot shell mode and typed "cd /tmp/petitboot/mnt/sda1/" and "./create_hdd_region.sh".
Im gunna re-try everything
Last edited by otherchris; 10-23-2012 at 06:37 AM.
I suppose you noticed that your output reports number of free sectors = 0
Did you perform the rebuild database after you installed the otheros pup? What size is your hdd and which firmware pup did you use i.e. the size of the gameos/otheros partitions? If you would report the exact steps you have followed, it might be possible to track any possible mistake.
ok so i retried everthing and i got the same problem. i believe it has somthing to do with when i install and run the "setup_flash_for_otheros.pkg" the console beeps 3 times and goes to a screen asking for 3.55 ofw. however it also says i can restart to try again and that works. Do you know where i can get the original CFW355-OTHEROS++.PUP (not the rebug one)
Are the links on this page down? http://ps3devwiki.com/wiki/OtherOS%2B%2B
I can't check them right now.
if they are down you can use, mfwbuilder with 3.55 official to make your own, you should even be able to find a checksum posted for it, if you want to check it.
I never got that message, hmmm.
from the instructions:
1. install other os firmware
2. when installation is finished, go to recovery menu and choose "Restore PS3 System"
3. your gameos should use only half of your HDD
4. run setup_flash_for_otherosp.kg beep beep beep
5. reboot (shut down and turn on your ps3)
did you check your hdd to see if it was split in half?
how many times did you run the create_hdd_region script before you got that specific message in the screenshot? was it just once?
Are the links on this page down? http://ps3devwiki.com/wiki/OtherOS%2B%2B
I can't check them right now.
if they are down you can use, mfwbuilder with 3.55 official to make your own, you should even be able to find a checksum posted for it, if you want to check it.
I never got that message, hmmm.
from the instructions:
1. install other os firmware
2. when installation is finished, go to recovery menu and choose "Restore PS3 System"
3. your gameos should use only half of your HDD
4. run setup_flash_for_otherosp.kg beep beep beep
5. reboot (shut down and turn on your ps3)
did you check your hdd to see if it was split in half?
how many times did you run the create_hdd_region script before you got that specific message in the screenshot? was it just once?
Yes, those links are down and MFW Builder does this MFW errror.PNG
Ok i just tried it with 3.55 OFW and it worked fine. Do you know what could be wrong with the rebug firmware to do that?
So you tried to patch the rebug oos pup? You should use the regular rebug and patch it. Could not find pattern to patch, yea, I guess it checks the values that are already there before it applies the patch (instead of just using the address). Either you are trying to patch a non-compatible firmware (at least not with the patches you chose) or could your firmware be corrupted? Did you compare the checksum of the copy you have with what it is supposed to be? There is nothing wrong with patching the ofw like you did, but if you want to be on rebug it doesn't really help you. There is already a thread for oos rebug with instructions for patching: http://www.ps3crunch.net/forum/threa...3-55-2-OTHEROS I don't know if the links there are still good. Some of their files were also hosted on ps3scenefiles. There are some checksums for the firmware in that thread; you should definitely check your copy.
So you tried to patch the rebug oos pup? You should use the regular rebug and patch it. Could not find pattern to patch, yea, I guess it checks the values that are already there before it applies the patch (instead of just using the address). Either you are trying to patch a non-compatible firmware (at least not with the patches you chose) or could your firmware be corrupted? Did you compare the checksum of the copy you have with what it is supposed to be? There is nothing wrong with patching the ofw like you did, but if you want to be on rebug it doesn't really help you. There is already a thread for oos rebug with instructions for patching: http://www.ps3crunch.net/forum/threa...3-55-2-OTHEROS I don't know if the links there are still good. Some of their files were also hosted on ps3scenefiles. There are some checksums for the firmware in that thread; you should definitely check your copy.
Ok so i tried with normal rebug 3.55.2 and when it finished it saved the file as a ".file" instead of ".pup".
All of the links are down on that thread.
Tomorrow im going to see if i can use a kmeaw otheros cfw. Ill let you know how that goes.
Thanks heaps for your help.
So you tried to patch the rebug oos pup? You should use the regular rebug and patch it. Could not find pattern to patch, yea, I guess it checks the values that are already there before it applies the patch (instead of just using the address). Either you are trying to patch a non-compatible firmware (at least not with the patches you chose) or could your firmware be corrupted? Did you compare the checksum of the copy you have with what it is supposed to be? There is nothing wrong with patching the ofw like you did, but if you want to be on rebug it doesn't really help you. There is already a thread for oos rebug with instructions for patching: http://www.ps3crunch.net/forum/threa...3-55-2-OTHEROS I don't know if the links there are still good. Some of their files were also hosted on ps3scenefiles. There are some checksums for the firmware in that thread; you should definitely check your copy.
This is just been taken too far. So i converted the rebug firmware to a PUP and this time when i boot the applications they don't take me to that screen asking for 3.55 update. But when in Petitboot i get the same message still. And when i check system information i still have full HDD on game OS. The thing is that i must do a restore ps3 system via the xmb because when i try to access recovery it takes me to petitboot. And a full format via the xmb takes "57 hours 24 minutes".
Can you think of anotherway to access recovery mode?
Thanks
I never had that problem, but if I remember correctly, I think the remedy is to run boot_gameos from petitboot or there is a bootgameos.pkg. I believe that setting the flag back to boot gameos will allow you to access the recovery menu.
Have you ever booted up petitboot with a livecd of redribbon already in the drive? Just curious.
Last edited by Gemma Arden; 10-27-2012 at 08:31 AM.
Reason: major typo
Reply With Quote
Originally Posted by Gemma Arden
There is already a thread for oos rebug with instructions for patching: 
