[hellsing9]

Originally Posted by Nicolas19 @hellsing9 ;click on Pic

This news is not frontpaged anymore because what happened with the user.
Until further notice or some solid info or solution we have to check (i removed it from frontpage) because any new user or someone who wants to try it could end in a problematic situation.

That's why you see 404 not found like @MajorDisaster said.
================================================

Ontopic:

Another message from @euss

http://pastie.org/private/jc6ha9lcbxbrnaqbfjx3eg

It's a conversation with nice info that worths reading it. (It's an irc log)

[shareboy]

Originally Posted by hellsing9 [..] It's a conversation with nice info that worths reading it. (It's an irc log)

So, to switch dex2cex without brick, I need to patch the cex.nor.bin with this "NOR downgrade.rar"? I'm confused.

patch1;0C0010;6FFFE0
patch1;7C0010;6FFFE0
rvk-040000;040000;080000

[DANNY G]

lol im sorry if the dudes app got a bad rep i have no idea as to why it froze the xmb.and pissing on your ps3 well that i would like to see wtf.

[haz367]

thx for the update andreus


off-topic about the dex2cex bricks...

Originally Posted by shareboy So, to switch dex2cex without brick, I need to patch the cex.nor.bin with this "NOR downgrade.rar"? I'm confused. patch1;0C0010;6FFFE0 patch1;7C0010;6FFFE0 rvk-040000;040000;080000

hmm don't know, the pastie say so, not realy sure about it cuse my console is qa flagged before convert and flashing a "kmeaw full flash with Teensy working fine the first time, check qa combo..check then the same thing using an OFW355 cex from start, converted, convert back to cex(console qa flagged) flashing full nor with Teensy, power down, power on = soft brick..beep..beep

then re-flashed the ofw355dex flash with the Teensy and console boots again
then flashed the same ofw355 cex flash(= qa flagged ofw355) this time using Multiman 04.04.03, exit to XMB after restore(eid only!) power off as normal, no FSM mode, normal boot and voila back on CEX ofw355, re-install ofw355 and all back to default

whatever it is, thx euss for posting it and i'm testing this later on with that ofw355 dump and flash it back using Teensy while i trigger FSM on 355dex wich previous give the RLOD, patch it with downgrader files and install rogero in FSM

[sandungas]

Originally Posted by DANNY G lol im sorry if the dudes app got a bad rep i have no idea as to why it froze the xmb.and pissing on your ps3 well that i would like to see wtf.

We was talking serious, but there are some "jokes" between all this talk, dont take this jokes too serious, no offend intended

I was trying to find an explain of what happened, and later i prefered not to explain here what euss explained to me, because as i said (and you can see in the logs) im not an expert with unbricking, so i thought it was not a good idea to come here talking about something ignore (as an smart ass)

Previously i thought that your brick can be fixed with an flash programmer, but thats wrong, actually is easyer (if is a typical brick caused by the syscon checks)... all the people that had this type of brick... was able to unbrick from service mode
So is supposed your console still has "service/factory mode" working

Before this you need to patch your "cex_dump.bin" in PC to remove the syscon checks (aka... the downgrade patches)
This patching is something common for everybody that updated firmware over 3.56 (the syscon stores the hashes of the bigger firmware, so when you return to an older firmware.... the syscon has the data of the other firmware and doesnt matches = no boot)
DEX firmware disables this checks... but iirc in last dex firmware they implemented some kind of protection for this checks (that i ignore and i cant explain, im just talking about it for the record)
This is why there is an "dex 3.55 downgrade"... this dex firmware is official, made by sony

[haz367]

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...

[sandungas]

Originally Posted by haz367 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....

I think is because when you install this official "3.55 dex downgrader"... the hases stored in syscon (updated in this installation) are the same than in a 3.55cex
This is a coincidence btw...

Also, when you are in "factory/service mode" this checks are disabled (so when you install a firmware from factory/service mode, this installation updates the syscon hashes correctly, and the check returns a "match" and all works fine)
*This is what danny g was trying... is an step taken from some manual of one of the different methods to convert

But dont take my words as an expert, im just talking about things that are involved in the process, but i have not much idea about them

[DANNY G]

sandungas my problem is dude i have no recovery menu or usb function.im thinking maybe buying a progskeet?what you think seing as i have the rflash.bin?

[heywhosjake]

Originally Posted by DANNY G sandungas my problem is dude i have no recovery menu or usb function.im thinking maybe buying a progskeet?what you think seing as i have the rflash.bin?

Yes definately as it's possibly cheaper and you won't have a big black door stop just laying around

[DANNY G]

is it possible to use the backupurflash.bin with progskeet?