|
|
#151 |
|
Senior Member
![]() Join Date: Dec 2010
Posts: 2,038
Likes: 1,041
Liked 583 Times in 473 Posts
Mentioned: 237 Post(s)
Tagged: 0 Thread(s)
|
@gingerbread
yes&no, why should it for this(dex2cex and visa versa)right? cuse once qa flagged/dehashed it is dehashed, ONLY if u update back to 4.xxOFW cex and downgrade again to 355 u'll need to dehash/qa flasg console to prevent brick!it can't hurt to have to enabled anyway, no need to remove if u not using PSN i have not tested without QA flag! i leave it there, but if it's required for going back dex2cex i'm not sure, cuse u are already ON 3.55 right, i think QA isn't required for this, then again don't quote me on it cuse i'm not sure, i can maybe test it later on, removing the qa and try it, also when on dex u can soft up/downgrade, only if u cex update to latest 4.xx then the syscon? needs to be dehashed/qa before installing any 355 without the "no-checks" to prevent brick |
|
|
|
|
|
#152 |
|
Senior Member
![]() Join Date: Mar 2012
Posts: 1,405
Likes: 284
Liked 812 Times in 418 Posts
Mentioned: 302 Post(s)
Tagged: 0 Thread(s)
|
@haz367
Thanks for sharing your info. For users (NOR PS3) who have disciplined themselves not to update above 3.55 and just the same users who wants (CEX <--> Dex). Could I say qa flag could prevent "pseudo-brick"? If it happend, they could use usb dongle to recover. |
|
|
|
|
|
#153 |
|
Senior Member
![]() Join Date: Dec 2010
Posts: 2,038
Likes: 1,041
Liked 583 Times in 473 Posts
Mentioned: 237 Post(s)
Tagged: 0 Thread(s)
|
hey
@gingerbread
to my knowing.... nothing is mentioned in the original guide to "qaflag" before convert, one must be on 355 already to get it working so i'd say it isn't required, correct me someone if that's wrong if they brick it's not because of QA?! they mentioned it earlier that only flashing the "EID section only" is safer like Multiman does the strange thing for me is when i do the dex2cex using a Teensy it worked fine the first time(kmeaw-flashcex) the second time doing the same way only this time i'll started from ofw355, after shutdown it RLOD on me and i tryed to get into FSM with dongle with no luck whatsoever, i flashed back full 355 dex backup and ps3 boots again then i used Multiman to see what it does, altough it backups FULL NOR flash, when flashing/restore it seems to only flash/restore the CEX EID section, and then some claim to not REBOOT, but that didn't work here cuse after flashing, back into XMB, the debug settings are still there and trying to install OFW355 cex via "sysytem update" gives an error(cex), so i just power down PS3 with controller and normally boot the ps3, all fine, this time the "debug settings" are gone as it should ![]() if u think about it, its just the same visa versa when one convert to dex and reboot with cex firmware it booted correct right, only when u check QA combo, it should be removed, then after install of 355dex u'll get real "debug settings" only now in reverse, and installled OFW355 cex via recovery, no FSM this time. another thing the second time, is Blu-ray movies, they play tho!.. only sometimes hit&miss, kicks me back to xmb with error i can't remember now, i believe its some region output problem, really strange cannot say for real what's the cause, the drive is working OK, only need to run it couple times before it play's and no its not the laser ![]() maybe also nandvsnor phatvsslim is different behaviour, but this is only guessing, anyhow all this aside it should be 100% safe with hard flasher ![]() off-topic: hopefully someone with a Teesny can tell us HOWTO flash/restore only EID section like multiman does, not flashing full NOR, i asked @judges but he could not tell me for sure, i just like to test it to see any differents happens after a reboot, altough like i said, the first time it worked perfect flashing full cexnor |
|
|
|
|
|
#154 |
|
Senior Member
![]() Join Date: Mar 2012
Posts: 1,405
Likes: 284
Liked 812 Times in 418 Posts
Mentioned: 302 Post(s)
Tagged: 0 Thread(s)
|
@haz367
Thank you for contributing to this thread with our information. Say we are talking about NOR PS3 and we are using multiman method. There is one thing that is Hit or Miss like what you have said. Say we are now on DEX, after flashing your DEX.NORBIN file, should the user reboot or not. Does this mean hold power to shutdown and from shutdown go direct to recovery? Some have mention that you can't are shutdown via controller. For some users, from DEX after flashing your DEX.NORBIN file, they exit MM and install FW via XMB. |
|
|
|
|
|
#155 |
|
Senior Member
![]() Join Date: Dec 2010
Posts: 2,038
Likes: 1,041
Liked 583 Times in 473 Posts
Mentioned: 237 Post(s)
Tagged: 0 Thread(s)
|
the thing about not rebooting is weird, cuse it may be for some, the original multiman guide also writes to "reboot" after flash, and this working fine overhere
![]() cuse when i tryed to install CEX 355 after multimanflash-exit to xmb, check the settings, debug is still in place and the installing cex update fails from XMB(for me that is!) it needs a reboot just like we did with cex2dex, after flashing whatever way user choose(preloader etc..) u shutdown/reboot PS3 normal with front button or controller and power on with front button, the ps3 boots fine, only to VERIFY, check the settings menu after flash/reboot from cex2dex> qa is gone (install dex from recovery = best way) from dex2cex: debug settings are gone (install cex from recovery) from recovery is always better, i've heard when installing from XMB it's not the same, best to use Recovery, so first reboot normally into XMB after convert, then shutdown again normall and enter RECOVERY Code:
22) Copy your 355DEX.EID0.NORBIN & your renamed 355CEX.EID0.NORBIN to your PS3 (FTP in mmCM or on a USB stick) mmCM will not flash unless the file ends with .EID0.NORBIN 23) Open mmOS ([SELECT] + [START]), browse to your 355DEX.EID0.NORBIN and double click on it. 24) Reboot your console and install 3.55 DEX FW 25) To switch back to retail, simply double click on your 355CEX.EID0.NORBIN, reboot and reinstall then again the first time switching back to cex i used teensy full cexnor and it worked like it should, second time same procedure is fail= RLOD, can't enter FSM, maybe i needed to remove teesny usb cable like i did first time, heh can't remember cuse first time it worked like that, second time nogo, and the ps3 needs to shutdown anyway no other way with hardwareflasher, need to release nor/trisate to get it bootingbtw, no errors 8002997F today anymore on BD movies, only now it ask when booting the BD: Do u want to allow internet conn for BD Settings - video settings - BD internet connection click NO and play aargh its doing my head in haha crazy shiiit
Last edited by haz367; 09-30-2012 at 05:37 AM. |
|
|
|
|
Likes: (1) |
|
|
#156 | |
|
Homebrew Developer
![]() Join Date: Jul 2011
Posts: 303
Likes: 33
Liked 219 Times in 104 Posts
Mentioned: 86 Post(s)
Tagged: 0 Thread(s)
|
![]() You cannot JUST flash the EID section (assuming it's from 0x2f000 to 0x3efff), because you have to erase a complete sector from the nor to be able to rewrite it (sector size = 128KB or for Samsung K8Q for this address range 2x64KB). That's not a limitation of NORway/Teensy, but how NORs are organized internally. So, in both cases, you would have to rewrite 0x20000 to 0x3ffff. Simply extract that range from you nor dump and you end up with a 128KB file. Then do: NORway.py COMx write my128kbfile.bin 0x20000 That's it. But you can as well reflash the whole dump. Nothing ever gets rewritten if the content is the same. |
|
|
|
|
|
Likes: (1) |
|
|
#157 |
|
Senior Member
![]() Join Date: Mar 2012
Posts: 1,405
Likes: 284
Liked 812 Times in 418 Posts
Mentioned: 302 Post(s)
Tagged: 0 Thread(s)
|
|
|
|
|
|
|
#158 |
|
Senior Member
![]() Join Date: Dec 2010
Posts: 2,038
Likes: 1,041
Liked 583 Times in 473 Posts
Mentioned: 237 Post(s)
Tagged: 0 Thread(s)
|
hehe, i think u told me the same back then, it's me not grasping it
so i wasn't clear howto, but as u mention, writing full nor only overwrites the differents only , the second time flashing a ofwcexflash it wasn't the same for some reason giving a RLOD, and again this is/must be user error, then again clueless as how the first time it worked fine with a kmeawflash ![]() thx @judges for reply and giving the noob some tips ![]() anyway full flash is OK, not gonna mess with it ![]() [QUOTE=judges;443715]I told you that I don't know how to use my own software? [QUOTE]hehe... |
|
|
|
|
|
#159 | |
|
Apprentice
![]() Join Date: Sep 2011
Location: Stanger,KZN,South Africa
Posts: 15
Likes: 5
Liked 1 Time in 1 Post
Mentioned: 1 Post(s)
Tagged: 0 Thread(s)
|
Where is the (flash_eEID_35500.bin) situated and when I attempt to do this it says: "Please install 3.55CEX/DEX firmware first" |
|
|
|
|
|
|
#160 |
|
Apprentice
Join Date: Oct 2012
Posts: 2
Likes: 0
Liked 0 Times in 0 Posts
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
|
Hi guys im now part of the BRICKED KREW
ps3 turns on, then imitates a fire engine, then turns off happened when converting DEX to CEX, turned my ps3 off before installing CEX :$ So basically just came to ask whats the best way to fix this? e3 flasher? cheers jim |
|
|
|
![]() |
| Bookmarks |
| Thread Tools | |
|
|