PS3 Anything I should know about side effects of a failed OtherOS install attempt?

jakint0sh

Forum Noob
Yeah, yeah, I know, another noob writing a "PLEASE HELP MEEE!!!1!!1" post. I know this isn't a good look for my first post here, but I'm not trying to be malicious or negligent with your time, I promise.

So, I decided to go messing around trying to install linux on OtherOS. I have a PS3 Slim CECH-2001A, and IIRC the minimum version reported by MinVerChk is 2.70. I was running an outdated firmware (Evilnat 4.90 CEX) so I decided to do wipe the hard drive and install Evilnat 4.92.2 CEX, and try installing OtherOS with a fresh environment. I had nothing of value on the PS3 itself, so doing a complete wipe was fine for me.

Well, it didn't work. I got as far as finding the correct dtbImage.ps3.bin and trying to install petitboot. I was using the tools built into Evilnat (or maybe it's technically part of xai_plugin, I don't know), and as far as I could tell it got as far as resizing the VFLASH regions, and then failed while trying to install petitboot. I should note that I never attempted to convert my system from CEX to DEX, and as far as I know, nothing I did should've affected that. I also recall some similar attempts from a few years ago, and I did get linux to boot (but not install properly) so maybe some debris from that caused the present petitboot install failure, I couldn't say for sure.

Most of the information I could find on doing OtherOS was pretty outdated at this point (from around 6 years ago) and mostly assumed that you would be using Rebug CFW for it. I figured I'd try anyway, because I love messing with this stuff, and I can usually handle whatever technical problems crop up. But, after a couple of attempts with no success, I found this, which seems to imply that OtherOS is so broken at this point that it's not worth trying anymore, I decided to try to undo everything and erase the hard drive again, and do another fresh install of Evilnat 4.92.2 CEX and set all of my stuff back up again.

Now, are there any possible side effects or damage I should be aware of and/or try to fix? My PS3 seems completely fine, but obviously there could be latent issues, possibly with the flash or EEPROM being corrupted.

I have a NOR flash backup from before I jailbroke my PS3, and PyPS3checker validated it with zero warnings or dangers. I assume that if worst comes to worst, I can restore this flash image to repair things and then just re-jailbreak it. If I need to buy a hardware flasher tool, I could do that.

Any guidance or help would be greatly appreciated. I have tried to provide as much relevant information as I can, but if you need additional details please let me know, and I will try to respond quickly.
 
Dump EID Root Key. Can be handy to manually tinker with oos bootloader on PC.

Resizing VFLASH failed or only installing Petitboot on it failed? That option in Evilnat enlarging space for oos bootloader to ~20MiB from 4, so any should fit. Maybe yours is broken (PS3 should accepting raw or GZ compressed bld).

Easiest be just set QA flag, go to CFW 3.55.4 Rebug, then to OFW 3.16. It was last fw with out of the box OOS support and you can install OOS (Linux) on HDD region 4, not only on VFLASH region 5 (bootloader).

By toying with OOS/OOS++, you cannot damage console in any way.

Make flash image from current state when you have CFW installed. It can safe your headache in future.

Worth to read my journey from years ago:
https://www.psx-place.com/threads/bootloaders-doesnt-see-usb-and-dvd.39650/
 
It reporting it's failed is not necessarily a bad thing; it's happened to me many times. Usually just triggering the OtherOS install again after a console reboot will get it working (in Evilnat 4.92.2 at least, as that's all I tested with since I wanted to retain OOS++). Seconded on flash backup & dumping ERK!

See also https://github.com/losgatosbandidos/ps3-archlinux-guide and the automated version by NGX, https://github.com/vmo64/archpower-linux-installer-ps3 - we've been doing this a lot as part of the PS3 Cell overclocking efforts, Linux is much easier (and handier) to benchmark with. Successfully used on my own 2001A as well.
 
Well, after MUCH messing around, I managed to get it working! I used the dtbImage.ps3.bin from losgatosbandidos/ps3-archlinux-guide and I used the automated installer ISO from vmo64/archpower-linux-installer-ps3 which is linked at http://ps3.christianresearchservice.com/archpower/dl/ARCH_202509.iso in the readme there.

However, I do have a small problem. For whatever reason. any and all boot options in petitboot fail with a "Failed kexec" message and freeze the console, unless I immediately unplug my keyboard after pressing enter. I have NO idea why this makes it work or why having a keyboard connected makes it fail, but a bit of googling led me to https://www.reddit.com/r/ps3homebrew/comments/803974/cant_install_red_ribbon_linux/ which describes the solution, so at least I was able to get past it.

Is there a way to make it so that I don't have to unplug my keyboard to boot? Could it be that the dtbImage.ps3.bin provided in the ps3-archlinux-guide repo is defective in some way, and would work fine on a NOR Phat model but doesn't quite work properly for my Slim?

Also, I will definitely look into dumping the EID root key soon, thank you for the advice. I would've done it already but I've been busy with college classes and other things.
 
Glad you got it working! That same dtbimage was used on slims as well - it's for all NOR flash models. I've never presonally run into this before. If you put a USB hub in the path or change the port the keyboard's in, does anything change? If you use a different keyboard, does anything change?
 
Well, after MUCH messing around, I managed to get it working! I used the dtbImage.ps3.bin from losgatosbandidos/ps3-archlinux-guide and I used the automated installer ISO from vmo64/archpower-linux-installer-ps3 which is linked at http://ps3.christianresearchservice.com/archpower/dl/ARCH_202509.iso in the readme there.

However, I do have a small problem. For whatever reason. any and all boot options in petitboot fail with a "Failed kexec" message and freeze the console, unless I immediately unplug my keyboard after pressing enter. I have NO idea why this makes it work or why having a keyboard connected makes it fail, but a bit of googling led me to https://www.reddit.com/r/ps3homebrew/comments/803974/cant_install_red_ribbon_linux/ which describes the solution, so at least I was able to get past it.

Is there a way to make it so that I don't have to unplug my keyboard to boot? Could it be that the dtbImage.ps3.bin provided in the ps3-archlinux-guide repo is defective in some way, and would work fine on a NOR Phat model but doesn't quite work properly for my Slim?

Also, I will definitely look into dumping the EID root key soon, thank you for the advice. I would've done it already but I've been busy with college classes and other things.


Your problem is likely coming from the dtbImage file. All of the testing I have done was done on Evilnat's dtbImage which you can find here https://github.com/Evilnat/xai_plugin/tree/main/Petitboot. Which firmware are you using?
 
Back
Top