163w ago - As
promised, today
JaicraB has revealed the PS3 Hypervisor LV2 (GameOS) dump method and circuit used to allow the PS3's memory to persist while booting into OtherOS, which then allows dumping of the memory.
This was apparently on a
CECHG model system with board model
SEM-001 1-875-384-21
To quote, roughly translated:
DemonHades /
JaicraB Extraction Method:
First of all, be careful if you're going to attempt this, I am not responsible.
It's about keeping the RAM alive when moving to OtherOS. To do this the ram must be fed at all times so as not to erase the data.
Overview map
Refer to the First Image below.
Zone A
http://4.bp.blogspot.com/_4rtVxQc9D6s/S7dexn30R7I/AAAAAAAAAFs/tpo2XxknPKs/s1600/Zona+A.JPG
This area is sensitive. At that point we had settled with two resistors together. You have to remove it (remove it, but you could also cause a short circuit). It has 4 legs. At this point it tells the RAM and the integrated MOSFET turns off.
Zone B
http://3.bp.blogspot.com/_4rtVxQc9D6s/S7deyC8VeyI/AAAAAAAAAF0/bGUuh1knvRA/s1600/Zona+B.JPG
From the point labeled we get the feed. You can put anywhere on the track.
Zone C
http://2.bp.blogspot.com/_4rtVxQc9D6s/S7deye-D8wI/AAAAAAAAAF8/1EeIUE6Keyw/s1600/Zona+C.JPG
At this point labeled we have to make a bridge to defeat the two resistors.
Zone D
http://2.bp.blogspot.com/_4rtVxQc9D6s/S7dYDoRKnRI/AAAAAAAAAE0/tp9grVoM5kQ/s1600/Zona+D.jpg
The original point of the exploit.
Mini Circuit
Refer to the Second Image below.
The Technique
It is possible that the first time you start count him to do for the recovery.
It Summarized a bit with the following steps:
• Log into XMB.
• Touching, ejectura, configure, filling the memory with more information.
• Run a game, insert a BD, etc, etc.
• Then boot to OtherOS.
• Dump memory to exploit.
Remember: The first 36 Megabytes are the "privileged memory" that contains LV00, LV1, LV2. The rest is waste memory of XMB (very interesting) and data from OtherOS.
The next thing to try is to start a tiny linux system and do a full dump. So we would get more data from the XMB and less disturbed memory (from OtherOS)
The bad thing is my two-week vacation is over
(I would have liked to have one more week to follow up).
Good luck to all and share!
i have the ofw 4.41 can i use this cfw?...
actually it is the lv2 right now.. the hypervisor have been done a few weeks back.
yes, some part of it has been overwritten but hey, there is at least something to start with!
well, it's not the cross-dump, but the content of the ram what has the problems: AFAIK the ram can be decoded by the runnung sys (thus it's encrypted)
another option is to figure out how to build an external chip, aka MODCHIP (i know everyone cringes at the mention as they require hardware modification but this dose too), that would somehow record and output all everything thats loaded into the ram or other chips be recoded and outputted to a computer. but this is a very complicated process and could take years.
hi, is posible build a bld whith the ps3sdk,but the problem is the store dump file.
The sdk ps3 dont have include for mount and storage.
the best is using ethernet cable for dump,using a otheros whith it support but need included the exploit files
1saludo and yes that dump have parts linux,remember when rst don't volatilice the ram the old data mix with the new.
Nice point, beside the LILO/GRUB he catched as an example is our case petiteboot/kboot that's better to rebuild..
Building a kernel image as small as possible and running it into the highest memory space avaliable coul make the thing easier..
Even better could be to find a way to run a minimal linux in the backward compatibility reserved memory (32MB) of some models but this, even if possible, could envolve quite more work...
memmap=nn[KMG]$ss[KMG]
Mark specific memory as reserved. Region of memory to be used, from ss to ss+nn. Example: Exclude memory from 0x18690000-0x1869ffff:
memmap=64K$0x18690000
or
memmap=0x10000$0x18690000