why does an
ofw355 cexdump(qa flag) works then if the console has been on 421dex, back to 355ofw and flashing back with multiman,
no "downgrade patches" on the flash needed....and it boots as normal like one does cex2dex or a kmeaw one, also no downgrade patches required, this is something new on the horizon..oh well gonna test it later on just because we can
edit
@
sandungas
, thx man learning thing every day, still a bit weird cuse as mentioned, and it would have been noted in the guides if it's the case, it must be the QA afterall on cex, im talking from the 4.xx cex hardware downgrade point of view - dehash with ofw355, then any cfw = dehashed
then decide to go dex and it goes without a hitch, after flash reboot and ps3 acts normal, install dex to finish off, then go up and down and in dex the "those" syscon checks must be disabled right?! if one can "software" downgrade from 4.21
then make sure both ros 0/1 contain ofw355, then flash back either cex ofw355/kmeaw backup and just normally "reboot" (this worked 2 out of 3 tests - teensy v kmeawflash/fail1 ofw355 - multiman v ofw355 = same dump as fail1 teensy)
no downgrade patches used so far and everything working just in reverse, it boots, debug settings are removed, check "qa" combo, install ofw355/kmeaw from recovery
maybe if one goes from "355" without ever been on cex 4.xx and not QA flagging console on forehand could cause the "brick" i don't know, in my view the "syscon checks" are not present in dex(and that 355 downgrader, either the renamed? one..diff hash or the real one?! from the "update" folder, the one s*ny made for soft downgrading back to 355
the only strange thing is 2 times flashing the full cex back, only 1 time it worked as normal, also before convert entering FSM no dice..... also FSM formats the drive, a bit overkill anyway, anyway for flashing, after that second "soft" brick, decided to use Multiman for restoring CEX, now it backups full NOR/NAND(no bootloader) and flashes/restore only the EID/TargetID sectors/offsets, after flashing, there are some different opiniums on what to do now:
1) not reboot - install from XMB = fail on my end and for others to...
2) exit multiman - power off system normal way - reboot and "normally" it just boots just as it did when doing cex2dex, be it a ofw355 or kmeaw flash, only differents ofcourse the debug settings are gone (tested&works)
3) following ps3tools.de from that guy "iceman" not that i use his cfw's
those guys there also now there stuff like us and in that guide u can simply use the "reboot" option from within multiman after restore CEX flash, seems to work also
it must be the??! full nor/nand vs eid only makin the differents for the brick on reboot
i also have no clue realy
, just saying my testings with it, never used the cex hardwareflash "downgrade patches" for dex2cex, perhaps it makes it bulletproof method for going back to cex like euss explained:
1) be on ofw355 dex
2) patch the cexflash with the patches as u do for cex hardware downgrade
3) restore cexflash via multiman/preloader/hardware flasher
4)enter FSM or enter FSM before restore cexflash?! ^
5) fsm using PKG >reboot with USB stick (enter lv2diag+Rogero 3.6 pup) or using fsm dongle after shutting down ps3 normal
could be totally wrong here...the "patch" the cexflash with the hardware patches just add's a little more confusion to the whole dex2cex hehe
if it makes the convert bulletproof, shoutout to euss for the tip
can't be arsed to test it right away, awaiting some cfw cex news right
...or is that ship a total loss already, maybe one day another anon dude droppin off some guide/howto DIY like the dex one..what a rush that day was hehe...