[munchy_cool]

you mention Then navigate to Network settings and press L1,L2,L3,R1,R2, and down on the d-pad.where is the l3 button ? I cant find it on the controller?

edit - found the l3 but cant get the debug option , any tips?

edit - got it , need to press all of them at the same time and not one after the other.

[euss]

Quickly glanced O.P. (did not read all 29 pages, so some might already be covered) -> Of the steps that its covers, the guide looks ok, but some very important steps are missing in my opinion:

1. Validation of good dumps to prevent permabricks (also to make sure your clip is still ok) : http://www.ps3devwiki.com/wiki/Validating_flash_dumps

Importance: high priority imo, there is NO undo or debrick after it is flashed. E3 has /some/ checks (e.g. it checks metldr header to look for nondowngradeable model), but it is known to fail in most other checks.

If you have trouble with Validation steps, upload it somewhere + visit IRC ef.net #ps3downgrade where me and others do this regulary and post the link.

2. Manual(auto) patching + Debricking : http://www.ps3devwiki.com/wiki/E3#Ma...3_downgrade_v2 / http://www.ps3devwiki.com/wiki/E3#E3_debricking_notes

3. Samsung (multiconsole) update for being able to use E3 universal is breefly mentioned, (not the why though), mirror : http://www.ps3devwiki.com/files/flash/Tools/E3/BIN/

4. Alternatives for PSgrade: http://www.ps3devwiki.com/wiki/Talk:...PSgrade_Dongle

5. Marriage/working BDboard is needed for QA (no need to do button toggle for dehash btw), install packages and running games, and solving it: http://www.ps3devwiki.com/files/lv2diag/remarry/

6. More information about QA : http://www.ps3devwiki.com/wiki/QA_Flagging

7. Alternatives for dehashing : http://www.ps3devwiki.com/wiki/Downg...sher#Dehashing + http://www.ps3devwiki.com/files/firm...r/355noBDnoBT/

Good luck!

[munchy_cool]

@playerkp420 - just to let you know I skipped the step wherein it says to flash OFW 3.41 from recovery and then OFW 3.55 from the xmb, I directly updated to OFW 3.55 from recovery followed by CFW 3.55 from recovery and all went smooth.

Maybe you can mention that as well in the tutorial ...

[playerkp420]

Originally Posted by euss Quickly glanced O.P. (did not read all 29 pages, so some might already be covered) -> Of the steps that its covers, the guide looks ok, but some very important steps are missing in my opinion: 1. Validation of good dumps to prevent permabricks (also to make sure your clip is still ok) : http://www.ps3devwiki.com/wiki/Validating_flash_dumps Importance: high priority imo, there is NO undo or debrick after it is flashed. E3 has /some/ checks (e.g. it checks metldr header to look for nondowngradeable model), but it is known to fail in most other checks. If you have trouble with Validation steps, upload it somewhere + visit IRC ef.net #ps3downgrade where me and others do this regulary and post the link. 2. Manual(auto) patching + Debricking : http://www.ps3devwiki.com/wiki/E3#Ma...3_downgrade_v2 / http://www.ps3devwiki.com/wiki/E3#E3_debricking_notes 3. Samsung (multiconsole) update for being able to use E3 universal is breefly mentioned, (not the why though), mirror : http://www.ps3devwiki.com/files/flash/Tools/E3/BIN/ 4. Alternatives for PSgrade: http://www.ps3devwiki.com/wiki/Talk:...PSgrade_Dongle 5. Marriage/working BDboard is needed for QA (no need to do button toggle for dehash btw), install packages and running games, and solving it: http://www.ps3devwiki.com/files/lv2diag/remarry/ 6. More information about QA : http://www.ps3devwiki.com/wiki/QA_Flagging 7. Alternatives for dehashing : http://www.ps3devwiki.com/wiki/Downg...sher#Dehashing + http://www.ps3devwiki.com/files/firm...r/355noBDnoBT/ Good luck!

Thanks for your input. A lot of good info there. I am going to add your post to the OP.

Originally Posted by munchy_cool @playerkp420 - just to let you know I skipped the step wherein it says to flash OFW 3.41 from recovery and then OFW 3.55 from the xmb, I directly updated to OFW 3.55 from recovery followed by CFW 3.55 from recovery and all went smooth. Maybe you can mention that as well in the tutorial ...

Thanks munchy. I figured it would work like that also, just never tried. It's always good to cut out a step to make it easier. Will add info to the OP.

[munchy_cool]

You are welcome bro ..and thanks for all the help ..tekken 6 is being backed up as we speak.

Also, if in the OP wherein we have to press L1,L2,L3,R1,R2 and down on Dpad, maybe you can mention what L3 is (for n00bs like me) and also that all of them have to be pressed at the same time and not one after (that is you can release them, in the end they all have to pressed down not that you press L1, release it and then L2)..I hope you understand what am trying to say ...

[nzie]

L1,L2,L3,R1,R2, and down on the d-pad combination is pressed at the same time?

[munchy_cool]

Originally Posted by nzie L1,L2,L3,R1,R2, and down on the d-pad combination is pressed at the same time?

QA flag part, to get the Debug Options...

[playerkp420]

That step is actually not needed. I just do it to make sure the qa flag worked. But like euss said in his post above it is not necessary. I added his post to the guide too. There is a lot of good info in those links. Like qa flag can be toggled off after you are done with the guide. I did not know that until after reading the info on ps3devwiki.

I think most users know what L3 is on the controller. I use it a lot when running from zombies on black ops.

[euss]

Originally Posted by playerkp420 Thanks for your input. A lot of good info there. I am going to add your post to the OP.

Sure, no problem. Just helping out where I can


OK, i've read all 29 pages and these kinda stood out, they may already be solved long time ago, I just like a topic with all questions answered

Originally Posted by playerkp420 I believe the backups bios and the wire are only needed just in case you brick.

Correct, for normal downgrade it is not needed. E3 debricking: The SBE wire releases the flashbus by pulling down Tristate to ground, so the E3 can use it. It is also handy if you want quickly to be able to reflash with a manual prepared flash .bin

Originally Posted by * PLAYER 1 The new method to enter FSM using a .pkg is not valid to downgrade after flash, cause it need you press PS button when you shouldnt do that.

Actually, it is not valid, because you need a 3.55 firmware on the XMB to start to use it. As your last run version was 3.56+ those keys are revoked and will only work after flash was downgraded (but to get to install and run a package, you need XMB and that needs reinstallment of firmware in service mode -> chicken + egg).

Originally Posted by * PLAYER 1 I dont know if there are 3.56 minimum version ps3, but in that case JFW 3.56MA is the natural choise.

1. Known minver locks are:
- 1.00
- 1.90
- 1.97
- 2.30
- 2.45
- 2.70
- 3.20
- 3.40
- 3.50
- 3.56
- 3.60

2. Imo (You will have much more joy on latest FW and all your games + PSN working then you will have with 95% of your homebrew having problems on JFW 3.56MA) there is no reason to use JFW 3.56MA, it is marked "bad idea" for good reason in ps3devwiki.

Originally Posted by tyxaioonoma ROGERO_CFW3.55-V2-4.00SPOOF_PS3UPDAT.PUP or can i use KMEAW_CFW3.55_NO_CHECKPS3UPDAT.PUP?

KMEAW_CFW3.55_NO_CHECKPS3UPDAT.PUP is not proper and will give trophy errors because of (specifically SS patch) its large block of OtherOS++ patches. Therefore, using latest Rogero build is imo the best proper downgrader PUP of choice, after that, dehash and you can install whatever you want.

Originally Posted by ahmed73 wanted to put kmeaw 3.55, went into recovery mode, put kmeaw cfw 3.55, on usb flash drive, selected option 6 from recovery menu. same surprise, system came back to ofw 2.56.

It can only install another version if that was present in the system somewhere (e.g. CompactFlash, SD, MemoryStick, USB harddrive, Previously stored in QA FW harddrive folder, BD/DVD/CD drive or other file/folder on USBstick. See also: PUP Installation locations. Golden rule: always remove all other storage devices and only have a PUP where you WANT it.

Originally Posted by ahmed73 I guess each machine has its own minimum firmware backup built-in somewhere, from where it resets itself.

The backup of both CoreOS in ROS of flash is not enough to get a console running on XMB, as 99% of the firmware is not even in flash but on harddrive and in most cases, esp. newer versions, errors out with BSOD/RSOD on version mismatches.

Originally Posted by tantu ok playerkp420 i see in e3 flasher site they enable system update in system debug first before doing downgrading is it must to do or not

That option only enables the copy of multiple firmwares to a local folder on harddrive, see here. It has nothing to do with enabling QA Recovery Downgrade (which is QA-flag extra) and which does not need any button combo to enable.

Originally Posted by nzie got a ps3 with rsod error while booting up ps3 before entering xmb.can i downgrade the console with e3?

RSOD will not prevent you from downgrading. RSOD can be solved (provided it is not caused by bad hardware) with : RSOD Fix with lv2diag.self for RSOD Fix

Originally Posted by lrtopshot does anyone know you can still dual boot after doing this ?

Yes, even when not natively supported by hardware, it is pretty easy to dual swap.

Originally Posted by MajorDisaster Buying a Cobra USB soon, That has a downgrade option right?

Yes, just select it with switch on the side.

Originally Posted by Asure For example, a user account with act.dat and rif files you could use to backup your legally purchased PSN games with ReactPSN?

Several problems:
- Backup Utility does not backup DRM locked content
- FTP backup on 3.56+ not possible
- QA will destroy ACT.DAT file (therefore, for NOR consoles that need to keep that data, reFSM for dehashing is a better option or backup that perconsole/peruser data before dehashing with QA).

Originally Posted by Snails Inc Does this methode also works with progskeet instead of e3 flasher?

All downgrades are in hearth the same (in fact, it has not changed since 2.4x first JIG leak or 3.41 PSJB + FOSS PSgrade), besides differences in hardware to accomplish certain steps (like dumping + reflashing prepatched). That is why on ps3devwiki, validating and downgrading itself are universal pages, and dumping/flashing is bounded together on the Hardware Flashing page and from there splitted to the specific hardware pages (Infectus, Noraliser, NorWay with Teensy 2.0 ++, Progskeet, PNM, PIC32MX, E3 etc). Dehashing is universal and nonflasher related (both the reFSM and the QA method).

Originally Posted by p0c4 is there another way to downgrade to 3.15 with e3 flasher to remarry drive? thanks for ANY help

Only if console is capable of running 3.15 - but old remarry did not need console on 3.15 but on 3.50 or lower. But that is all archaic now: you do not need to downgrade below 3.55 to remarry anymore: Remarry files for 3.55 and lower

Originally Posted by Zirak Is there some sort of indicating that it's actually updating or something? (Also, I've tried installing 4.10 on my HDD because thats the version my PS3 has but it keeps failing on update at 99%)

USB + HDD Activity LED and a log in root of USB Stick when using Service Mode. In your case it did not install, errored out and thus halted install without poweroff.

Originally Posted by playerkp420 (Except for the qa flag, do not ever run the qa flag app again, or I believe you will brick).

If QA-toggle was used to dehash and nondowngrader patched firmware installed, then using QA-toggle again to remove QA flagging, will not brick it.

Originally Posted by Chovoman Can I flash that e3_downgrade.bin file on any PS3 fw version?

Downgrade will always be firmware independant, as it completely replaces CoreOS in ROS and Revoke in trvrk areas inside flash at fixated locations. So even if your console gets updated to 9.99 it should be downgradeable to 3.55 again with hardware flasher methods.

Originally Posted by playerkp420 The e3 linker is not needed for nor models. It works for nand or nor chips, but you have to solder to all the points on the motherboard.

Wrong: the E3 linker is a NOR only clip that can be clipped onto the flash of NOR consoles. The subboard can then be used to solder to a NOR capable flasher. In no way are ps3 motherboard norpoints used (besides maybe Tristate/SBE point).

Originally Posted by playerkp420 I'm not sure what that reset button does.

On press, it disconnects SATA power.

Originally Posted by playerkp420 I think the solution was to make sure it is scratched out deep enough between point A and B

Warning: PS3 motherboards are 8 to 10 layers, so do not scatch too deep, as you will easily destroy layers below it.

Originally Posted by dubakak problems with dualboot starts after installation jb2usb cfw instead of default rogero 3.55 cfw

jb2usb fw is not downgrader patched and thus bricks on syscon checks. Enable QA on Rogero, then install jb2fw to workaround that issue.

Originally Posted by dvd -Do i need to do the QA flag step if i am using the E3's TB CFW no check? Or should i do it anyway to future proof.

Enabling QA gives you some extra debricking options, prevents some sorts of bricking too. Plus you get nice options, therefore no reason to not use it

Originally Posted by dvd i heard the PSjig software only works on PS3 console that are <FW3.55? as my PS3 were on 3.7x, will it still work and get me into service mode?

If flash is downgraded, the PSgrade/JiG will work again. You cannot enter service mode on 3.56+ as we do not know the dongle authentication key for those versions (atm).

Originally Posted by nzie is it possible to qa flag from 3.55 to 3.50 instead of 3.41?

Sure QA-toggle works on all 3.41/3.50/3.55 firmwares with mmap114+ peek/poke enabled (that includes Rogero builds). Lowest downgrade /with/ QA seems to be 2.50/2.70 (at least on my 1.00 capable CECHC04's),

Originally Posted by playerkp420 If you flashed a bad backup to the ps3's nor, and don't have a good one(from the same console), then I dont think it can be recovered.

100% correct, that is why Validating flash dumps is so important, to prevent permabricking and making sure the user has a good backup to use for debricking.

Originally Posted by helooth Yes, I know it, but I need this dump , I know what I am doing : CECH-2504B , So can you help me & share the link of this valid dump ?

Never. 0% chance. See above and the nice red in the Flash table. Bootldr, metldr and alot of other regions in the flash are perconsole and peruser encrypted, not exchangeable and unique for every one of those millions of consoles.

Originally Posted by playerkp420 I am not sure about Nexus One, but there is a list of devices you can use, somewhere. Search for psfreedom compatibility list.

My old list might be handy.

Originally Posted by redmarine Anyone know where I can get Lv2Diag.self and R_CFW_v3.1_PS3UPDAT.PUP from as per step 11 Part 1 Downgrade to Rogero v3.1 w/ 4.11 Spoof?

downgrader lv2diag.self's will be here: http ://www.ps3devwiki.com/files/lv2diag/3.55%20downgrader/
downgrader firmwares will be here (including latest Rogero build) : http://www.ps3devwiki.com/files/firm...EX/Downgrader/

Originally Posted by mage333 I have CECH-2503B (320GB) PS3 with Datecode 1a. I cant downgrade to 3.55 and I get immediate shutdown of PS3 after running e3_downgrade.bin. Anyone have any idea if it is possible to downgrade?

Only if your bootldr and your metldr are marked "OK" in green in this metldr/bootldr table (compare with your own flashdump) then it is possible to use the Manual ps3devwiki method with Flowrebuilder + E3 autopatches
If your bootldr / metldr is marked red in that table, then it is not possible to downgrade to 3.55.

Originally Posted by moskvichh Manual says, that i need to downgrade again it to 3.41 OFW and than i can update to any 3.55 CFW.

Manual is flawed. You just need reFSM or QA with nonpatched firmware to dehash.

Originally Posted by Tokobo because I downgraded from 4.11 Demo firmware with the e3

If you have a Kiosk/Demo/SEX console, then you need to kioskify downgrader firmware or downgrader patch a Kiosk/Demo/SEX firmware. In both cases PS3 MFW Builder can be used.

[nzie]

Originally Posted by euss RSOD will not prevent you from downgrading. RSOD can be solved (provided it is not caused by bad hardware) with : RSOD Fix with lv2diag.self for RSOD Fix

so how i can downgrade with red screen while booting ps3 to xmb?(e3 flasher). or just downgrade like normal way and reFSM to use RSOD fix Lv2diag.self ?