[sxcevo]

Hello. I have an issue i pressed the right button on my controller by mistake in reactpsn. I didnt change my target ID and now my ps3 just turns on and beeps.

I have already explained my situation else where but i am now desperate for anyone that has any ideas or has been in the same situation or very similar.

Here is a link to where i have posted my problem and my username is the same "sxcevo" and my comments start near bottom of the page and carry on over to page 74.

http://www.ps3crunch.net/forum/threa...ettings/page73

http://www.ps3crunch.net/forum/threa...ettings/page74

I will be very grateful to anyone who can help me out of my predicament.

[Gringo]

Well I've bricked mine going from dex to cex. I've tried unbricking with Ps3jig (psp) and my HTC HD2 but it hasn't worked. All I have available to me are a HTC HD2, HTC Sensation, iPhone 3GS, and an original psp. Can I use any of these to unbrick my ps3?

[gingerbread]

Originally Posted by Gringo Well I've bricked mine going from dex to cex. I've tried unbricking with Ps3jig (psp) and my HTC HD2 but it hasn't worked. All I have available to me are a HTC HD2, HTC Sensation, iPhone 3GS, and an original psp. Can I use any of these to unbrick my ps3?

I believe Ps3jig is very buggy. The best option is to get hardware dongle.

[Gringo]

Originally Posted by gingerbread I believe Ps3jig is very buggy. The best option is to get hardware dongle.

Fair enough, I'm a broke arse student though, where can I get one for proper cheap? :D

[gingerbread]

Originally Posted by Gringo Fair enough, I'm a broke arse student though, where can I get one for proper cheap? :D

Try modchip central.

[daflip]

anyone know how to verify if the flash dumped i have saved is CEX
i got myself confused when i rename file to "355DEX.EID0.NORBIN" which i think thats the converted DEX dumped to be flash with MM... i dont want to risk
or is there anyway to modify the converted dex dump back to CEX.. im really confused i might have deleted the original CEX flash dump, im also sure that this is the original dump coz i had it saved in "important" folder but the only problem is how it was renamed..

edit;
i think i can try flashing it, to be sure and it will confirm the target ID but not sure which for CEX

[haz367]

check the file/targetid, for CEX its e.g 85, debug/DEX = 82 -- offset 0x2f075

[pcwhockey18]

Originally Posted by HipHopStyler I have to add something! Before you switch back to CEX, you must be on 3.55DEX. If you are on 4.** than downgrade with 3.55 DEX Downgrade PUP. After downgrade , flash back your "my-original-cex.NORBIN" in mmOS . Close Multiman. ATTENTION: DONT TURN OF THE CONSOLE. BECAUSE IT WONT TURN ON AGAIN AND YOU WILL BRICK YOUR CONSOLE. After closing Multiman install 3.55 CEX FW and your PS3 is RETAIL. THIS METHOD IS CONFIRMED IN OTHER FORUM.

What do you mean by "flash back your "my-original-cex.NORBIN" in mmOS ." ?

Thanks

[haz367]

after some tests here(NOR), it's really hit&miss going back to cex, anyway not consistant

the first time i flashed back cex(kmeaw) using Hardware flasher and normally shutdown PS3, it booted straight into XMB and all worked, tested going into FSM wich worked with dongle but after it did the firmware install the PS3 didn't shutdown(blinking green led)
replaced with "exit" lv2diag.self and exit fine and PS3 boots into CEX firmware(kmeaw)
dvd/bd/game disc all working from the start.

now the second,3th..time it won't work as the first time, every time(soft-bricked with flasher) after flashing cexflash.bin and either poweroff or first put PS3 into FSM mode doesn't work after reboot = RLOD damnit..weird behaviour....

this time cannot enter FSM with dongle after flashing cexflash( note this time its OFW355 cex.bin not kmeaw), every time i try = RLOD, this is easaly fixed with hardwareflasher otherwise u are screwed for the time.....

then i tested Multiman way and this worked great and altough here the guide posted to not REBOOT the PS3 or it bricks isn't the case for me, when after flashing my "355CEX.EID0.NORBIN.BIN" in mmOS (multiman 4.4.3) it ask to exit multiman and reboot PS3 and install cex firmware as normal
if u try to install OFW355 CEX via system update XMB without REBOOT! it gives an corrupt file error on trying.

normally reboot(via controller) and the PS3 boots fine into XMBdebug settings removed-qaflag back), then via system update or recovery re-install OFW355 and all is good again

for sure this is weird and a risk to (soft)brick involved if u have no flasher at hand
after flashing with multiman the cexofw355, i had the dex355 on "original" settings(region N.America)

the first time i converted as posted i didn't have to do a thing, dvd/bd/game all worked

this time it spitted an region error(PAL not supported) at me on DVD's and another error on BD's, game is fine

then i changed in the QA debug menu the "sp-int" to "np"
changed in "security settings" bd/dvd parental region code from america to nl
and also did a "restore PS3 sysyem" via XMB

after this the dvd's and blu-ray's and games worked fine again without re-marry


so the BIG red letters saying to NOT shutdown/reboot with Multiman isn't correct, atleast on my end when trying to install via XMB it fails, it required a reboot = no brick


just sharing my tests..[b]be carefull[/b[ if u have no hardware flasher, cuse the outcome isn't constant meaning the first way/option1 worked and trying again a second time fails

back on working cex via multiman this time

[gingerbread]

@haz367

Thanks for sharing your experience.

Does QA-Flagging help prevent/reduce brick?