[haz367]

Originally Posted by master737373 I was sure we stopped using e3_downgrade.bin.

really?

it doesn't f*cking matter if ur using the "original way" or the patched way..both have the same outcome...tested and verified working many times....i agree on using the patched way, i'll do that to........ at the end both are equal and the wiki E3 guide recommends to use "default way" first, well atleast couple month's ago...once again it really doesn't make any different, it saves u not much time either

[baileyscream]

Originally Posted by master737373 I was sure we stopped using e3_downgrade.bin.

i still have it in the guide.
i also have patching bkpps3.bin (reversed) using flowrebuilder then re-byte reversing then re-flashing the patched dump back (as its done with TEENSY and progskeet)

has there been problems with the e3_downgrade.bin now?
should it not be used?

[haz367]

no it just works fine but hey sometimes talking to the wall makes more sense

either "e3_downgrade.bin+bkpps3.bin - switch 1-5 DOWN - 6UP

or

patched bkpps3.bin with 355COREOS - all switches DOWN

= same outcome........

if it bricks along the way it's either "corrupt files" or bad e3 clipping..nothing else...

[JohnnyBoyQC]

turn on your ps3 and you should have this on screen Turn the ps3 back off insert your dev usb board (programmed with the correct files) into the right usb slot. a full list of boards are listed at the start of the thread in the second tab down called "Wrong you need these tools before you even think about following a guide" inside that tab you will see the second tab down called "A development board" in there is lists of the different dev boards.

programmed with the correct files ? I Purchased a E3 card ready, is it ready for use or i have to put some files in it ?

Originally Posted by haz367 no it just works fine but hey sometimes talking to the wall makes more sense either "e3_downgrade.bin+bkpps3.bin - switch 1-5 DOWN - 6UP or patched bkpps3.bin with 355COREOS - all switches DOWN = same outcome........ if it bricks along the way it's either "corrupt files" or bad e3 clipping..nothing else...

But if the Dump is valid, the clip should be ok, right ? Had some problem with mine and the DYN-001 board, took me 10-15 time to get a dump that seems good. Had to cut a corner as most people do but the clip wasn't even flat under, had to grind it a bit.

[baileyscream]

Originally Posted by haz367 Another way to fully dehash the PS3 without using toggle_qa.pkg" is while ur installing Rogero 3.7 nocheck via FSM mode, do not EXIT FSM yet, remove the files from the USB root and put OFW3.55 on root of USB and install it 2x after eachother, verify the updater.log on the usb and finally EXIT FSM using the "exit Lv2diag.self" goodluck on the downgrade guys

fsm to de-hash is NOT recomended
it soft bricks to many console's

i have never had it work.

some ppl do but the amount of ppl that posted in here and messaged me about bricking after doing fsm de-hash forced my decission to pull it and not recomend it.

[haz367]

Originally Posted by baileyscream i also have patching bkpps3.bin (reversed) using flowrebuilder then re-byte reversing then re-flashing the patched dump back (as its done with TEENSY and progskeet)

Also this part, all the confusion..i really don't get it.....now i haven't finish the Teensy soldering...so i'm not that Pro ....Mushy fixed it for me, the Teensy dumps the FLASH "unscrambled" by default = IFI header at OFFSET 200 = ready for validate from start, for Progskeet i think there's an option in the TOOL to have it scrambled/unscrambled (IFI or FII at offset 200) by default it's dumped the same as Teensy = unscrambled or byte swapped whatever u name it = IFI header at offset 200 = ready for validate

For E3 flasher it's another story, the E3 flasher dumps it UNSCRAMBLED = FII header at offset 200, so to VALIDATE the E3 dumps one must use option 7 in Flowrebuilder "byte reverse dump" so it is "unscrambled" and reads IFI at OFFSET 200, then to flash back via E3 flasher one must use the original "scrambled" bkpps3.bin (FII header at offset 200)

then we have the 355 COREOS patches, they have made patches for all of them so one doesn't have to waste time bytereversing/byte swapping/ unscrambling/re-scramble dumps

Progskeet_patch.txt:
Progskeet/Teensy NOR Progskeet_patch.txt
E3 NOR progskeet_patch.txt patches
NAND patches

[baileyscream]

Originally Posted by haz367 no it just works fine but hey sometimes talking to the wall makes more sense either "e3_downgrade.bin+bkpps3.bin - switch 1-5 DOWN - 6UP or patched bkpps3.bin with 355COREOS - all switches DOWN = same outcome........ if it bricks along the way it's either "corrupt files" or bad e3 clipping..nothing else...

if e3_downgrade.bin has a low success rate then it really needs removing and we need to stick with a more stable way.

or atleast first time downgraders really need the best way shown to them.

the way least likely to brick a system.

obviously the long time downgraders can do whatever they want as they should know instantly how to fix.

[noobzega]

I always do next:

1. Update my E3 with update, 001111.
2. Then I make backup, 001000, after i make backup, I do it 3 times.
3. Then I copy downgrade.bin with my backup on my E3 and 000001
4. Then I plug PS3 break v1.1 in second slot
5. After that I install rogero 3.1 with Lv2diag.self
6. Afther that Lv2diag.self for go out from FSM
7. Dehash and debug on,
8. Install from recovery 3.55
9. Install from recovery 3.55cfw rogero 3.1

And that was work for me, can anyone check my dump?

Also why on video they do restore proces? What that mean?

[JohnnyBoyQC]

Originally Posted by noobzega I always do next: 1. Update my E3 with update, 001111. 2. Then I make backup, 001000, after i make backup, I do it 3 times. 3. Then I copy downgrade.bin with my backup on my E3 and 000001 4. Then I plug PS3 break v1.1 in second slot 5. After that I install rogero 3.1 with Lv2diag.self 6. Afther that Lv2diag.self for go out from FSM 7. Dehash and debug on, 8. Install from recovery 3.55 9. Install from recovery 3.55cfw rogero 3.1 And that was work for me, can anyone check my dump? Also why on video they do restore proces? What that mean?

Maiby im wrong but i don't tihnk you have to be in recovery mode to instal 3.55 rogero 3.1 after dehashing. After dehashing you should already be on OFW 3.55.

[haz367]

Originally Posted by baileyscream fsm to de-hash is NOT recomended it soft bricks to many console's i have never had it work. some ppl do but the amount of ppl that posted in here and messaged me about bricking after doing fsm de-hash forced my decission to pull it and not recomend it.

agreed on using the "toggle_qa.pkg" but the pro's at the wiki recommends the FSM 2x OFW355 way correct?, Mushy also told me he always did it like that, so it must work, then again i must admit not using it also on NOR consoles, and the NAND that came back also had "toggle_qa" installed

using the "toggle_qa.pkg" from Rebug always works..yes, but for this way one must re-connect the BD drive ofcourse before finish the complete downgrade as otherwise it won't run the pkg etc....the other way is maybe faster at the end while the PS3 is dissambled, i'm sure it should work also or otherwise it wasn't posted onthe wiki or maybe???

but yeah +1 for "toggle_qa.pkg" way