[haxxxen]

Originally Posted by haz367 u can make new dump on ofw355 using dumpflash.pkg and take that one and convert it dex2cex, if u like post the dump made here and i'll convert it

i would not recommend using dumpflash pkg to make flash backups, instead use multiman or memdump. dumpflash does make a different backup as flasher or the other 2 apps. especially the cvtrm region is different on dumpflash.

i have tried to flash this backup with flasher and it gave me syscon panic

[playerkp420]

I say install NewDEXKamel and patch your games correctly. Your games will play fine.

No reason to go back to CEX.

[haxxxen]

guess there was some spelling error, playerkp420

you could try naehrwert's method to get root key with 3.41 dex mfw and asbestloader. maybe this works

i would also try to load a cex lv2kernel and then run dumper again. maybe it only depends on lv2kernel

[danger2u]

Originally Posted by playerkp420 I say install NewDEXKamel and patch your games correctly. Your games will play fine. No reason to go back to CEX.

how can install the new dex kamel?
************* [ - Post Merged - ] *************

Originally Posted by haxxxen guess there was some spelling error, playerkp420 you could try naehrwert's method to get root key with 3.41 dex mfw and asbestloader. maybe this works i would also try to load a cex lv2kernel and then run dumper again. maybe it only depends on lv2kernel

how can i load a cex lv2kernel?

[haxxxen]

you copy kmeaw lv2_kernel.self to dev_flash root with devblind and then run lv2loader from rebug

[danger2u]

Originally Posted by haz367 sure, its late already on my end anyway provide these 3 things dump ofw355dex eid_root_key original cex targetid e.g: mine is "85" - Retail Europe http://www.ps3devwiki.com/wiki/Target_ID for creating the original cexflash, if u dont have the root_key run eEID_RKDumper.pkg" on 355 p/p, that should get it the dump prefered from ofw355, the dump_flash pkg should work on it if i remember correctly post/pm files and i'll fix it back to valid cex

here are the key
http://limelinx.com/fi3nl

[haz367]

what haxxxen suggested i was busy with..rebug and dexlove/lv2loader to see if it dumps root_key, was late already and had problems mounting/adding lv2kernel_self, gonna start again with correct multiman just to see it can be done
out of the box it won't run on that rebug releaese...

for dumpflash(NOR backups) thats bull, they work FINE and are identical!! works fine here don't say things that isn't correct, one could aslo use "preloader" on 355 to dump/restore and it works great!! have tested this/compared many times...

btw the key ur posted isn't the root_key, not sure what it is but no root_key in it
Auth-ID [isoldr]
Vendor-ID [hv]
SELF-Type [Secure Loader]

just for testing i'l report back on any luck with dumping the key
if u have both there's no problem in creating cexflash, dont let them discourage u, it will work again they do have a point to stay on there as it all works fine

[danger2u]

if i can downgrade to cex 3.55 i will pay u
thank u for ur work
i wait to see ur result fist do something stupid
if u could make a tutorial

[haz367]

can't seem to dump the root_key whatever way i trying.....and lv2loader is kicking back to xmb, no beeps, correct lv2_kernel.self(p/p) in root dev_flash
the rebug release giving errors on pkg's like 80029567..to much hassle and no root_key dumped, even with correct access to all folders(home/tmp ...)

if u insist or just like to have a cexdump just in case, only option so far, or if someone gets it dumped on 355dex(root_key) i have no luck, only option then would be build MFW355 with OOS support, set it up like usual and get "dump" root_key file that way

no cash needed, just trying to help, if u manage to get root_key, post or pm for cex fix


edit:

@danger2u :

nvm previous edit, root_key dumped, use rebugs lv2loader/kmeaw lv2_kernel.self -- pup_unpacker -all PS3UPDAT.PUP kmeaw

[haz367]

got it couldn't leave it alone lol...

@danger2u

with lv2loader.pkg and kmeaw lv2kernel u can dump root_key
tested&working, lemme know if any problems
root_key is dumped in hdd0\tmp