EXCLUSIVE: C2D v2 (PS3 Flash Patcher) - Now Allows Users to Modify TargetID Settings

[JLM]

This error cause me about 3 days work. Thank you so much for posting this. Can I remind people to perhaps put this vital information in the tutorials! They could be made so much easier! (I.e. Download Red Ribbon R5, install to USB, download precompiled metldrpwn, bash the script a couple of times to get rid of that error)

I have done this process many times now. If anyone needs help or needs to know what worked or didn't, please do contact me on Twitter - @xangma.

Thanks again deank.

Sorry, but no one received that error in testing. Also, posted on the same page as Deank's instructions is the following:

if (in response to sudo ./run.sh) a long message containing the words "cannot allocate memory" appears on screen then you have too many windows open. The ps3 has a small amount of memory; close the filemanager if it's open and try again.

JLM@ps3:~/metldr838exploit$ sudo ./run.sh
[sudo] password for JLM:
+ insmod ./metldrpwn.ko
insmod: error inserting './metldrpwn.ko': -1 Cannot allocate memory
+ cat metldr
./run.sh: line 4: /proc/metldrpwn/metldr: No such file or directory
+ sleep 1
+ cat appldr-metldrexploit350.self
./run.sh: line 6: /proc/metldrpwn/mathldr: No such file or directory
+ sleep 2
+ echo 1
./run.sh: line 12: /proc/metldrpwn/run: No such file or directory
+ sleep 5
+ cat /proc/metldrpwn/debug
cat: /proc/metldrpwn/debug: No such file or directory

Thanks to Rogero for releasing the modified pups and for his explanations.

I think he didn't have the E3 hooked up until after he bricked.

[tul]

hi, trying to get back to CEX i loaded trought multiman the orignal dump he perfomed in the first place, in the reboot sequence to install the CEX firmware the ps3 wont boot anymore, alot of beeps and turn off automaticly, any help?

[andreus]

you had exactly the same problem that i had. I also followed the tutorial and when converting (for the second time from DEX to CEX), after updating the cex nor in muiltiman cex (with good result) and shutting down the ps3 wont boot anymore ... only beeps.

I think mine and yours nor are corrupted.

Only with a flasher you can restore it if you have a flash backup.

[tul]

you had exactly the same problem that i had. I also followed the tutorial and when converting (for the second time from DEX to CEX), after updating the cex nor in muiltiman cex (with good result) and shutting down the ps3 wont boot anymore ... only beeps.

I think mine and yours nor are corrupted.

Only with a flasher you can restore it if you have a flash backup.

i have make a flash backup with multiman and with memdump, is that worthit?

[andreus]

i have make a flash backup with multiman and with memdump, is that worthit?

i tihnk so, but i'm no expert.
I tested extract with FlowRebuilder and checked the ps3devwiki page for validating flash dumps and mine seems ok, you should test your to and save them in a safe place, becuase, i think without them you can't recover the console.

[Piratan]

hi, trying to get back to CEX i loaded trought multiman the orignal dump he perfomed in the first place, in the reboot sequence to install the CEX firmware the ps3 wont boot anymore, alot of beeps and turn off automaticly, any help?

same thing happened with me.
updated CEX through Multiman and then it won't boot up but beeps like 8 or 9 times and turns off.

[CloneD]

I haven't tried to go back to cex yet but you are all scaring me with this stuff. Did you all copy out the first 48 bytes and make a .bin with it to go back or did you use the original dump from MM to flash back ??

EDIT: This is why I ask,

If the dump-eid0.bin doesn't have the proper keys at the begining (0x00-0x2f) you will have to search for the keys.
Mark the first 16 bytes (0x00-0x0f) and search for them in the dump. You'll find them at another location.
Save the 48 bytes following from the location you found the keys to a NEW file (eid_root_keys.bin) and use the file with "c2d"

This leads me to believe that they aren't all the same and that something would be different somewhere, but then I'm not that knowledgeable on the matter. Could someone explain a little more about what may have happened here.

[tul]

fixed my ps3, with a service jig and this lvd... http://www.ps3devwiki.com/wiki/Downg...her#PUP_to_use

always at the right usb port, put in service mode ( donf forget to power off, then dongle, power on, power button followed with eject )
if suceeded entering service mode, it will power off without those anoying beepers.
then with a USB Pen
put file lvldiag file 1 and official 3.55 cex firmware, after that, you will see that can boot in service mode, only takes usb pen with lvldiag file 2

im back at 3.55 kmeaw restoring my backup to go again to Dex.

[master737373]

fixed my ps3, with a service jig and this lvd... http://www.ps3devwiki.com/wiki/Downg...her#PUP_to_use

always at the right usb port, put in service mode ( donf forget to power off, then dongle, power on, power button followed with eject )
if suceeded entering service mode, it will power off without those anoying beepers.
then with a USB Pen
put file lvldiag file 1 and official 3.55 cex firmware, after that, you will see that can boot in service mode, only takes usb pen with lvldiag file 2

im back at 3.55 kmeaw restoring my backup to go again to Dex.

By any chance, did you try to write full nor?

[Piratan]

fixed my ps3, with a service jig and this lvd... http://www.ps3devwiki.com/wiki/Downg...her#PUP_to_use

always at the right usb port, put in service mode ( donf forget to power off, then dongle, power on, power button followed with eject )
if suceeded entering service mode, it will power off without those anoying beepers.
then with a USB Pen
put file lvldiag file 1 and official 3.55 cex firmware, after that, you will see that can boot in service mode, only takes usb pen with lvldiag file 2

im back at 3.55 kmeaw restoring my backup to go again to Dex.

what service jig you use?

and you used the official 3.55 firmware?



When doing this , after a min does the green power light start to blink? is that saying it is installing? I read that it installs without no video output, didn't know this was a sign.



After waiting and no luck I checked my USB and it had a update log(UPDATER_LOG.TXT) and it talks alot about succeess untill this point.

compare vsh package elapsed = 435 msec
Update VSH Package done(0x8002f000)
Bul-ray Disc Player Revoke
read bdp revoke package (1775 bytes) elapsed = 6 msec
decrypt and verify bdp revoke package elapsed = 55 msec
write bdp revoke package elapsed = 1 msec
Bul-ray Disc Player Revoke done(0x8002f057)
update package elapsed time = 147930 msec
Updating or Verifying failure 0x8002f057
UpMng.UpdatePackage() failure
manufacturing updating FAILURE(0x8002f057)
Total Elapsed time = 160395 msec