203w ago - Another update from graf_chokolo and Marcan42 who are working to bring OtherOS back to PS3, to quote:
I managed to boot an unencrpyted LV2 kernel from VFLASH. The decrypted LV2 kernel from Service JIG just made some strange sounds for several seconds and then did shutdown Normal unencrypted LV2 kernels boot normally. We could kick out lv2ldr from HV completely and boot enencrypted LV2 kernel always Working now on Linux bootloader. Stay tuned.
I didn’t use default.spp to boot decrypted LV2. I patched HV process which loads LV2 kernel, kicked out lv2ldr, replaced the function which loads lv2_kernel.self with my own code which loads just any OS from a VFLASH region It can be either petitboot, LV2 kernel or something else And dual boot is also possible with this approach. We could store several kernels on VFLASH and decide at boot time which one to boot.
And yesterday i found also out how to enable all debug and log messages in HV and HV procs and actually see these log messages Expect more soon. And greetings to SONY I will try today to boot decrypted 3.56 LV2 on my 3.41 PS3
If you could upload a binary image of AsbestOS for me please, i could test booting it today from VFLASH. Thanks.
Guys, i would be greatful if someone could upload me decrypted 3.56 lv2 kernel. Thanks.
If i got the right version then i just booted decrypted lv2 kernel 3.56 from VFLASH
Thanks for the images. Just booted your tftp image from VFLASH And i see UDP packets coming from PS3
From marcan42: twitter.com/marcan42
Don't confuse AsbestOS itself (a Linux bootloader) with the way you launch it: USB exploit, lv2 payload, lv2 replacement, or (now) OtherOS++
In other words, there's absolutely no reason why you couldn't use AsbestOS with his "OtherOS++"; in fact, you should! (once it's done)
Graf_chokolo doesn't seem to "get" AsbestOS. It isn't mutually exclusive with GameOS; AsbestOS built as otheros.bld is still a good idea.
graf_chokolo, I don’t think you “get” AsbestOS. It’s just a linux bootloader, in fact it would work great as otheros.bld or any other way of running it as an lv2 binary, and it’s more robust than petitboot (and smaller and easier to modify).
OtherOS + extra rights isn’t a replacement for AsbestOS, it’s an alternative to our original approach of replacing lv2 with AsbestOS. There’s already one released way to boot AsbestOS (USB exploit, which isn’t very clean/handy), Hermes is working on a runtime lv2 bootstrap for it (also not very clean but handy for people who like CFWs), there’s the lv2 replacement that we demoed but which isn’t out yet (which is clean, though can’t dual-boot GameOS yet), and once you release what you’re working on you will be able to just boot AsbestOS with it. Of course you could just run petitboot too, but where’s the fun in that? (we could’ve just used petitboot as a lv2 kernel for the 27c3 demo too, but AsbestOS is just much easier to make work and I already have a working new boot ABI using the devtree to pass the region1 allocation to Linux and patches that make it work regardless of whether the bootmem split is 128/128 or 16/240).
This isn’t a competition, I see no reason why AsbestOS can’t work great with whatever you’re getting ready
Btw, re: disk encryption, they use the same key and a NULL IV (can’t remember if all 00 or all ff) for every sector. It’s a very stupid/insecure block encryption scheme. There are flags for the sector read commands to toggle encryption on and off, that’s what we used to boot Linux off of a raw, totally DOS formatted disk with no encryption or lv1 regions.
Also, we thought about booting an unencrypted lv2 kernel too (I assume you’re messing with default.spp?) but we were very short on time and self was easier. Of course, you know a lot more about lv1 than we do
I think this blog is eating my comments if they have URLs…
Here are three binaries (compiled off of the public git, it’s just stage2_native.bin) with three different boot modes (config.h settings):
-hdd boots from a raw DOS formatted HDD (first partition must be FAT and contain a kboot.conf, same as we used at 27c3), -tftp boots from DHCP/TFTP (bootfile should be a kboot.conf), and -netrpc sets up a server that lets you read/write memory and issue hypercalls from a client on your PC, for experiments (see netrpc scripts in asbestos.git). See the AsbestOS readme for info on how to boot kernels with it (you need my ps3-linux.git patches). Git is at git.marcansoft.com.
You should run dbgcli on your PC on the same network as the PS3 to watch the debug output (even if you don’t set up the kernel/kboot.conf, if you get that it means it’s working). You can compile it from git, or here are two Linux binaries (64/32bit):
Stay tuned for more PS3 Hacks and PS3 CFW news, follow us on Twitter, Facebook and be sure to drop by the PS3 Hacks and PS3 Custom Firmware Forums for the latest PlayStation 3 scene and PlayStation 4 scene updates and fresh homebrew releases!
Another quick update from Graf_chokolo: [Register or Login to view links]
Please be patient guys, i'm working day and night on HV reversing and Linux booting Regarding dual boot GameOS+Linux, yeah, it's definetely doable, i'm implementing it currently Regarding dual boot GameOS CFW + GameOS OFW, is also doable, but harder. In both cases we need a custom HV. All HVs are nearly the same in all firmwares from SONY, and i know it very good and can add functionality, patch or remove it however i want.
Booting Linux from VFLASH/HDD or decrypted LV2 kernel from VFLASH/HDD is just a small proof to SONY how good i know your HV Or should i say now my HV
Without patching HV you cannot get GameOS rights on 3.15 with Linux. So custom HV is still needed. And that is exactly what i'm doing right now, creating custom HV. And with original HV from 3.15 you won't be able to communicate with Update Manager or Dispatcher Manager e.g.
Just booted petitboot from VFLASH on my 3.41 PS3 Created a new VFLASH storage region of size 16MB and stored there uncomressed petitboot compiled by me with openwrt I only patched HV, didn't touch any Linux files Sorry marcan, i will stick with petitboot I intend to install Debian Linux on this weekend on my HDD Greetings to SONY OtherOS is back But now with GameOS features. Stay tuned.
Dual boot GameOS+Linux is close
Look at that piece of dmesg output guys Great news
ps3disk_init:588: registered block device major 254
ps3_system_bus_match:354: dev=7(sb_01), drv=6(ps3disk): miss
ps3_system_bus_match:354: dev=6(sb_02), drv=6(ps3disk): match
-> ps3_system_bus_probe:365: sb_02
ps3disk sb_02: ps3stor_probe_access:70: 3 accessible regions found. Only the first one will be used
ps3disk sb_02: First accessible region has index 1 start 524312 size 130611352
ps3disk sb_02: ps3da is a Hitachi HTS542580K9SA00 (76319 MiB total, 63775 MiB for OtherOS)
3 accessible HDD regions All GameOS regiosn are accessible
I guess i won't have sleep on this weekend. Sray tuned.
Here is the complete dmesg output: [Register or Login to view links]
And RSX works with petitboot 1080pi
Guys, someone compiled latest openwrt, i didn't manage because gcc couldn't build. If someone knows what is wrong with gcc for powerpc64 in openwrt please contact me
Hehe, i should take care where i install my Linux or else GameOS wont' boot
Yeah, i'm cross compiling it on x86 Linux.
Holy crap, guys, unbelievable petitboot can read UFS filesystem of GameOS UNENCRYPTED I have access to all GameOS HDD regions.
Here is a snippet from "hexdump -C /dev/ps3da | less": [Register or Login to view links]
Stay tuned, it's certainly not the last good news from me
Holy crap, allmost all VFLASH regions are accessiable
ps3flash sb_03: ps3stor_probe_access:70: 5 accessible regions found
my repositories do not contain any SonyŽ software nor any software designed to bypass security set in place to protect copyrighted material.
The keys does not have any protection what so ever from the Norwegian copyright law.
Also “Norwegian law commands us to respond to such a notice by removing potentially infringing content until it’s legality can be fully clarified.” is simply not correct. It is not mandated to do no such thing – you are only forced to remove content that IS illegal. Yes, you face a harsher penalty for not removing it IF you should have realized it is illegal, but not if it by a fair persons judgement seemed to be legit.
You are only allowed to use my repositories to make legal homebrews. I do not condone piracy!