i tried to post the guide yesterday in the afternoon but i suppose i'm still under moderation.
great job DemonHades / JaicraB. You have done a great service to the ps3 world. Keep up the great work!
That was the whole problem with GeoHot in the first place - people had to recreate what he had already done just so they could see the lv1 dump. But because DemonHades and JaicraB have released a dump for all to see, anyone with the knowledge can just examine it without having to go through what they did.
They've released a mini tutorial on how to do it yourself purely for those that are interested in how it was obtained and incase someone else wants to try and do it.
So I think no it's been released publically it's just going to be under the scrutiny of the dev's now.
It's not a bad idea at all but... who tells the linux OS to NOT overwrite memory blocks used by XMB ?
This needs a specially crafted allocation table in the initrd to work, otherwise the system booting may corrupt the RAM content...
Am I wrong ? And who tell us the memory blocks which are not used by XMB in order to use them to boot linux ?
Experience maybe, just try, try, try again I suppose...
This is great!!! Now that just about everything on the ps3 is ready to be examined, I´m hoping we´ll be able to see something for the basic user.
Good luck to everyone who´s putting the effort into it. i´m guessing there´s going to be people with reverse engineering skills needed. I hope a few step up to the plate and deliver.
Again this seem like great development towards some progress. I hope we have something soon... Keep up the great work everyone...
Having the method of dumping out there could allow people with different (older?) firmware versions to dump their firmware which could lead to the discovery of some security holes that $ony patched and that were never found.
Data would be corrupted cause HV is not knowing it should keep track of the RAM content into this process, nothing tells it to do it and keeping the RAM content alive is not preventing linux to overwrite it while HV tables are gone, this leads to the need of using unallocated memory blocks to boot linux, guessing for example that the higher you can boot it the better the result...
Obviously this could be done better with a "made on purpose" microkernel requiring the lowest amount of memory possible....in the try to dodge useful content...
Maybe on a DECR it could be done even better since there is little to no chance to expand RAM onto a retail/debug unit...
EDIT: otherwise it could be possible to boot into linux, map the memory, instruct the HV and then switch to XMB, do what we have to do and then switch back to linux keeping memory alive....but I'm not sure neither I've time to try...
However, for any news - you will have a much better chance getting your post on the frontpage if you submit it here: http://www.ps4news.com/submit