4.30 DEX: Do *NOT* install this on a converted machine, it will result in a brick. There is a check on eid0(!) in lv1ldr, that will trigger a panic (fun fact: it's impossible to generate the checked data yourself, so no cex2dex without ugly patches anymore).
PUP file information
Package version: 1
Image version: 99999
File count: 9
Header length: 656
Data length: 186813495
PUP file hash : F1CA59DB50C7D9B86175B95EBBF1A39D0F1AB3AE
Entry id: 0x100
Filename : version.txt
Data offset: 0x290
Data length: 5
File hash : 1E49F1F42C18AC829E29A1CABA8404073A8631FE
Entry id: 0x101
Filename : license.xml
Data offset: 0x295
Data length: 308970
File hash : 5003EBF1548E8F002545561B74BBF5C470EE92C7
Entry id: 0x103
Filename : update_flags.txt
Data offset: 0x4B97F
Data length: 5
File hash : 65A0A6DA7FDB7F7A93C50F2439F6D5FE4C55AF74
Entry id: 0x200
Filename : ps3swu.self
Data offset: 0x4B984
Data length: 5669536
File hash : 401FD78D850CF1EB797A5E4F96FB86BF429E5877
Entry id: 0x201
Filename : vsh.tar
Data offset: 0x5B3C24
Data length: 10240
File hash : D9B66E0D2845D71A67D76E7907AB06368CE61E08
Entry id: 0x202
Filename : dots.txt
Data offset: 0x5B6424
Data length: 3
File hash : 1AA4749D0EE0D0AE937FBF73BC4B9ACD352F732A
Entry id: 0x300
Filename : update_files.tar
Data offset: 0x5B6427
Data length: 175083520
File hash : 884BF69AC877FD054FD3DC92C88AF439FBA32FD6
Entry id: 0x501
Filename : spkg_hdr.tar
Data offset: 0xACAF427
Data length: 71680
File hash : AA3090A65BBAFFFB306B2FA8EE600C689B6F030F
Entry id: 0x601
Filename : ps3swu2.self
Data offset: 0xACC0C27
Data length: 5669536
File hash : 1677EC061EDA6AD3D50C12B47599220E931A8552
As always, keep in mind these PUP updates will currently NOT install on a retail PS3, and so they are intended for examination and comparison purposes only.
We have 100% confirmed that running this updater on a retail PS3 will not damage it, however, it will give the following error before the installation completes: The data type is not supported. (8002F029)
Stay tuned for more PS3 Hacks and PS3 CFW news, follow us on Twitter and be sure to drop by the PS3 Hacks and PS3 Custom Firmware Forums for the latest PlayStation 3 scene updates and homebrew releases!
Something must of gone wrong, after I flashed my CEX NANDBIN I went to the XMB screen and turned it off. Then when I turn it on it does a quick few beeps and powers down. I can screw with it a little by jamming on the eject button but I doubt that helps. Also my USB stick will not light up at all.
What should I do to fix this? I know there are multiple flasher dongle things is that my way out?
Hello, i was wondering if someone could help on converting my rebug 3.55 cex to dex... Here's the prob.. I dumped my nandbin file and i got my eid_root_key.. i installed SSL and got the c4d.exe file... all worked but when i start up cmd and run it as admin, typed in c:\c2d> c2d.exe eid_root_key.bin flashCEX.bin flashDEX.bin 82...
soo i was wonder originally it is named flashCEX.nandbin... do i switch it to just switch it to bin cuz when i type that the cmd msg appear file is in use... so am i missing here?? or is it the fact i'm doin it in windows 8.. if so can someone convert it for me or point me in the right direction cuz my ps3 JB bd rom is messed up and i would like to make the switch ..ty
You should be OK if you've got your original CEX dumps/files. If you brick converting back it won't be permanent and you can fully convert back. Do you have any USB device that you can get a psgroove payload on?
I've got a converted Dex PS3 Slim console (initial firmware 3.20 120gb) Now on 4.21 OFW DEX. I'm trying to revert the PS3 back to CEX after all the scene progress of DEX has stopped as everything is again about CEX now.
I've tried to follow all the guides on the internet and they all make reference to having QA Flagged your console before the initial CEX->DEX conversion. Since I didn't do that, I'm wondering if this compromises my chances of reverting back from DEX->CEX. I'm worried because of the increased chance of brick that people report. As apparently, it's more dangerous converting back
I'm not so clear on the matter and whether it's ok for me. In fact, what does QA Flagging have to do with this conversion process anyway?