What changed in the way the of installing the flash from the last version? since I bricked and fixed I have not been back to dex. was the problem actually found that caused the bricks? I am interested in what was causing it. was it the hash checks or what? I ask because it seems from the few posts that are here that it seems it is fixed or safe now?
What changed in the way the of installing the flash from the last version? since I bricked and fixed I have not been back to dex. was the problem actually found that caused the bricks? I am interested in what was causing it. was it the hash checks or what? I ask because it seems from the few posts that are here that it seems it is fixed or safe now?
From what I've gathered:
- mM now flashes the TargetID + 192 bytes out of the EID section
- QA-flagging your console will help reduce the chances of a console from bricking
- Flatz's EID Root Key-dumping application negates the Linux requirement completely but if you already have the root key, then there's no need to re-dump the root key, but however, you'll most likely need to re-dump your flash if you plan to do the conversion again as the flash dumps vary from dump to dump if you look at/compare the hashes between them
In short, the CEX-DEX conversion process has gotten noob-friendly and a lot safer than before.
Did you installed CFW CEX without turning off the PS3 or turned off and then installed?
And a last thing, if you turned off first did you installed from Recovery Mode or XMB?
Here's what I did throughout the whole CEX-DEX-CEX process after I FSM-friendly-bricked the console:
Part 1.1: Preparing The Flash Dump For DEX Firmware Installation
- I QA-Flagged my system using REBUG's Toggle-QA
- Used multiMAN (referred to mM hereafter) 4.4.4/MemDump to dump the FLASH (and I used the mM-dumped one instead, even though the MemDump/mM dumps are the same as each other, hash-wise)
- Used flatz's EID root key application on the PS3, and compared that with the otherOS-dumped EID root key that I had from the previous CEX-DEX attempt, and they're also the same (use any hex editor to compare them)
- Used Gunner54's CEX-to-DEX application to patch the flash dump
- Clicked on the DEX TargetID-modified dump in mM 4.4.4, and I changed the TargetID from there
- Restarted the system by:
--- Exiting mM and returning to the XMB by pressing the PS button, and selecting "Quit Game"
--- Selecting the "Users" menu in XMB and then shutting down the system from there
--- Pressing the <POWER> button on the PS3
Part 1.2: Installing DEX Firmware
- Having an official 3.55 DEX firmware PUP on my USB in the "USB:\PS3\UPDATE\PS3UPDAT.PUP" (must be named as such) directory:
--- I installed it in XMB via the "Settings" XMB menu, and then selecting the "System Update" option, and then;
--- I selected the "Update from storage media" whilst having the "Turn system off automatically after update" option unchecked, providing that the option is there, and then following the instructions from there.
Part 2.1: Rolling Back to CEX
- Having installed the official DEX 3.55 firmware now (after playing about with the DEX features for a bit), I then used mM again, but this time, I used the original CEX flash dump, and simply selected it in order to change the TargetID back to the original TargetID (mine was 87 = CEX-UK)
- I then quitted mM and returning to the XMB by pressing the PS button, and selecting "Quit Game", and then from there, I attempted to install the KMEAW 3.55 (CEX) firmware via XMB (see Part 1.2), but the KMEAW firmware was grayed out, and upon selecting the firmware and attempting to install it, the PS3 threw up a "data is corrupted" error, so then from there I restarted the system by:
--- Selecting the "Users" menu in XMB again and then shutting down the system from there
--- Pressing the <POWER> button on the PS3.
Part 2.2: Installing CEX Firmware
- Having the KMEAW 3.55 (CEX) firmware PUP on my USB in the "USB:\PS3\UPDATE\PS3UPDAT.PUP" (must be named as such) directory:
--- I installed it in XMB via the "Settings" XMB menu, and then selecting the "System Update" option, and then;
--- I selected the "Update from storage media" whilst having the "Turn system off automatically after update" option unchecked, providing that the option is there, and then following the instructions from there (basically the same as Part 1.2).
To summarize, I had to restart my PS3 every time I had to install the firmware after the TargetID changeover and I had to install it via XMB, as it was safe enough for me to do so.
So there's no need to use Rogero CFW to prevent the problems with LV1 syscon checks?
No problem, and you don't need any syscon-patched firmwares if you manage to successfully change TargetIDs and install the appropriate firmware.
The only time you need them though is when you manage to FSM-friendly brick your console, in which you then need to follow Rogero's dehashing (syscon reset) tutorial in the "C2D.EXE v2 Released" thread - just look at the news article on the first page, and it'll mention Rogero's tutorial.
No problem, and you don't need any syscon-patched firmwares if you manage to successfully change TargetIDs and install the appropriate firmware.
The only time you need them though is when you manage to FSM-friendly brick your console, in which you then need to follow Rogero's dehashing (syscon reset) tutorial in the "C2D.EXE v2 Released" thread - just look at the news article on the first page, and it'll mention Rogero's tutorial.
hmmm... understood
Gonna try tomorrow and hopefully not receive a brick because I don't have anything that can enter in factory mode =/
And now that we can increase the number of games on hdd up to 255 everything gets better XD
Reply With Quote
Originally Posted by Piratan
