[Sarah1331]

Originally Posted by jeeqer somebody should please help, i keep getting CFI Inalid (does not begin with "QRY") i think the wiring on the ps3 is OK.

What flasher are you using?? It's most likely wiring issue


Sent from my iPhone 5 using Tapatalk

[baileyscream]

Originally Posted by LiteSoul Is a 128MB microSD enough to make dumps with the E3 Flasher? I'm all set with a 128MB one? Thanks PS: To the OP: In your Tutorial, you could specify the minimum microSD capacity required

a dump is 16.0mb
you will get either 1 or 3 dumps depending on the E3 update so the max space this needs is 48mb

you then need 1 dump and the e3_downgrader.bin (14.5mb)
(if you use this way to downgrade and not the flowrebuilder to pre patch or rogero's auto patcher that will soon be in the guide)
so this uses 30.5mb

so you need a micro sd card no smaller than 50mb (there are no micro sd cards this small that i know of)

so any micro sd card is fine

if you use the e3 card reader for fsm then get a decent size that way you can use the e3 card reader as a usb drive so your not wasting your money on a fsm tool / micro sd that you wont ever use again

[baileyscream]

DO NOT FOLLOW THIS AS IT IS UNDER CONSTRUCTION

for the progskeet v1.2 guide see this first CLICK HERE
and the latest bitstreem HERE

Downloading and installing

Downloading and installing

Needed Downloads

Needed Downloads



download ProgSkeet NAND programs.rar from HERE and put then into c:/ your main hdd found in My Computer

1 Install the ProgSkeet’s drivers

Install the ProgSkeet’s drivers (called “winskeet”)



1. Install the ProgSkeet’s drivers (called “winskeet”):-



2. go to the "ProgSkeet NAND programs" folder and select extract here with WinZip



3. scroll to the bottom to find winskeet



4. right click and send to desktop
Plug in the Progskeet to the pc with the ps3's controller usb cable



5. the card will be detected and the install new hardware wizard will run. click not this time



6. click install from a list or specific location



7. un select (search removable media (floppy CD ROM....)) and select (Include this location in the search) then click (browse)



8. browse to (Local Disk c: ) > (ProgSkeet NAND programs) > (drivers_winusb_111121)



9. installing



10. completed

2 Now the board needs testing for shorts.

Now the board needs testing for shorts. ( DO NOT do this with the board connected to anything but the pc.)

1. Run Winskeet from the desktop icon



2. Warning message



3. Opening screen



4. click Tools TAB



5. click Test for Shorts



6. No Shorts Found



7. if it’s not plugged in or no driver installed or you have a problem you will see this


8. now Close winskeet

Setting Up The ProgSkeet

Setting Up The ProgSkeet

wiring the injectus to the progskeet

injectus diagram from ps3devwiki
solder the pads on the injectus to the pads on the progskeet. the flat cable that comes with the injectus is not to be used.

installing the injectus usb driver

connect progskeet with usb to pc.
connect injectus with usb to pc.
found new hardware will open.


click (not this time) click (next)
screen will change to this


click (install from a list or specific location (Advanced))
click (next)
screen will change to this


un-click (Search removable media (floppy, CD-ROM...)
click (Include this location in the search.)
click ((browse) button)


goto (My Computer) > (Local Disk (c: )) > (ProgSkeet NAND programs) > (InfectusProgrammer-3.9.9.0) > (USB-Drivers3.1) > then click (ok)


then click (next)


it will install


you will get the warning just click (Continue anyway)


its done just click (finish)


you should get this bubble message.

updating the bitstreem

goto (My Computer) > (Local Disk (c: )) > (ProgSkeet NAND programs) > (InfectusProgrammer-3.9.9.0) and click (InfectusProgrammer_3.9.9.0)


the infectus program will start and you will get this message. just click (ok)


you will hear the "bing" sound of the injectus being disconected then reconected to the pc and then you will just have this screen.


close then re-start the injectus programer so it will detect the board


click (tools) > (Open Infectus)


this window will open "Actel Panel" click (Load DAT)


this window will open. NB it has a delay before opening so dont keep clicking it.


goto (My Computer) > (Local Disk (c: )) > (ProgSkeet NAND programs) > (ProgSkeet_Bitstreams_111126) > (DAT) and select the file (ProgSkeet_Retail_SL_NAND111126) then click (open)


you will be back at this screen (no changes to see)
click (Program)


it will check the dat file


then erase > write the bitstream to the progskeet


after a few min's it will finish. just click (ok) then close the 2 infectus windows and the progskeet is now ready for connecting the NAND clip(s)

NOW DESOLDER THE WIRES FROM INJECTUS TO PROGSKEET

Soldering the ProgSkeet

1. With the new Blue Boards (currently in production) there are 2 jumpers to create (bridge). The areas in YELLOW circles (R9 & R 11 the 3.3v setting) need soldering (bridge) (ignore the RED Circle) and donot remove R7 & R8.


2. it should look like this (ignore the RED line)

2. Attaching the ProgSkeet with the NAND clip

Attaching the ProgSkeet with the NAND clip

good tip from ps3hax member Dark_hades

[QUOTE=Dark_hades;467957]
The biggest pain by far of the whole process was getting that solderless clip on correctly for WinSkeet to recognise it. I would add that gently scrubbing the pins with some cleaning Alcohol on a clean toothbrush (on the solderless clip and NAND chips) can help in making sure it's won't fail due to the pins being dirty (as that was the case with my solderless clip).
QUOTE]

this is the COK-001 board. i have marked which NAND is which take note which is which or print this image for reference

for boards with a NAND chip on eithes side of the board then the cpu / gpu is the "bottom" nand


a close up of the clips in place
the clip in the blue circle will clip on no problem.
the clip in the red circle needs altering to sit flush.
the circle in red on both clips is a nipple on the clip marking pin 1 position.
you will find the same on the NAND chips.
just put the clip on the chip with the nipple in the same position


this NAND chip has 5 components too close for the clip to sit flush


a closeup of the NAND and components circled in red


the different types of cut needed (cut as in file very gently )


a different angle of the cuts


once done the clip will sit flush


conect the flat cables to the clip(s).

right now the progskeet can only read from the (A) side of the "Y" adaptor.
so you can only connect one clip at a time.

the one shown is the "TOP" "0 NAND chip"

you also need to conect the "3.3v" pad on the "Y" adaptor to the "3.3v" pad on the progskeet

this is done as we are not powering up the ps3 but using the progskeet to power the NAND chips

yes i still have the injectus connected to mine.

use good strong "quick clamps" to hold the clips in place

i have the mainboard sat on an angle on the ps3's base as it holds it just right with the clamps inplace

create your dump

create your dumps
Run winskeet
Power on ps3 and connect Progskeet to the pc via usb to halt the boot up


you should be on the main screen so first select your NOR type



MINES THE SPANSION 128P



A CLICK “DUMP CFI” save it as cfi dump (this will verify your NOR if this fail’s double check your wiring and that you have selected the right NOR in the first page)



click dump



Dumping (it takes seconds so don’t go anywhere)



Complete dump. Click clear and then dump again (number your dumps i.e. nor dump 1 , nor dump 2 etc (repeat this 10 times)



if the dump fail's

If it fail’s (I made a cuppa after my 4th dump when I came back and did a 5th it failed I just unplugged the usb and re-inserted it again to get good dumps again)

Why does it give verification errors when writing or halt/freeze when dumping?
Bad wiring
30AWG (bad) instead of 26AWG (ok) for NOR
Too long wires (>15cm)
Bad PC / USB chipset, just try an old PC with Windows XP/Linux
Bad USB cable
Interference
Bus not free / Halted incorrect
Power drops
Bad grounding

verify the dumps

verify the dumps

In the “program’s” folder find the HxD (hex editor) (install it like you did with Progskeet) and then run it.


first time opening



click file click open



select all your dumps and select compare



leave the top as it is and change the bottom as you check each dump.



you should see this message after each dump has been checked. If you don’t delete all your dumps and try dumping again. If you still get errors at this point check your wiring.
When there all the same just have 1 dump open (we will use this all the time now)



get a statistics.



The fine blue bars at either side are what need checking (the one to the left is highlighted in red put your mouse on the left line and you should get a reading between 18.71% - 29.01% (in the area circled in blue) and the line on the right should be between 10.42% - 10.48%
Now close the statistics tab



The first thing you should see at offset 00000010 is FACEOFF , DEADBEEF



if you see AC OF FF EO , AD DE EF BE then your dump’s need byte reversing if you don’t see either then you have a bad dump. Re-do all your wiring and start again

Byte reverse

Byte reverse

Inside “programs” folder find FlowRebuilder run it



this is the main screen




select byte reverse a dump



click the box next to brows, drag & drop, drop down



select your dump



click execute operation



and it’s done it in the same place as the dump and its added “swap” to the name

you should see at offset 00000200 is IFI



if you see FI.I then your dump’s needs byte reversing. again if you don’t see either then you have a bad dump. Re-do all your wiring and start again

If you did see FI.I in your dump then you need to use flow rebuilder with the byte reverse option if it says IFI then you can skip this step

Byte reverse

Byte reverse

Inside “programs” folder find FlowRebuilder run it



this is the main screen




select byte reverse a dump



click the box next to brows, drag & drop, drop down



select your dump



click execute operation



and it’s done it in the same place as the dump and its added “swap” to the name

First find the IDPS/TARGET ID & METLDR and then BOOTLDR (were still using the hex editor)
The area to find these depends on your ps3 model


IDPS/TARGET ID is at 0002F077 (scroll down to 0002F070 then the top row of numbers is your last digit)
CECH-20xx (DYN-001 boards) it should have the value 09 (this is what is in the image)
CECH-21xx (SUR-001 boards) it should have the value 0A
CECH-25xx (JTP-001 boards) it should have the value 0B
CECH-25xx (JSD-001 boards) it should have the value 0B
CECHHxx (DIA-001 boards) it should have the value 05 or 06 or 07


METLDR is at 0000081E & 00000842
CECH-20xx (DYN-001 boards) it should have either one of these value’s E9 20 at 0000081E & 0E 8E at 00000842 “OR” E8 90 at 0000081E & 0E 85 at 00000842 (this is what’s shown in the picture)
CECH-21xx (SUR-001 boards) it should have the value E9 20 at 0000081E & 0E 8E at 00000842
CECH-25xx (JTP-001 boards) it should have either one of these value’s E9 20 at 0000081E & 0E 8E at 00000842 “OR” E9 60 at 0000081E & 0E 92 at 00000842 WARNING IF IT HAS THIS F9 20 at 0000081E & 0F 8E at 00000842 STOP NOW YOU CANNOT DOWNGRADE THIS PS3 MODELCECH-25xx (JSD-001 boards) it should have this value E9 20 at 0000081E & 0E 8E at 00000842 WARNING IF IT HAS THIS F9 20 at 0000081E & 0F 8E at 00000842 STOP NOW YOU CANNOT DOWNGRADE THIS PS3 MODEL
CECHHxx (DIA-001 boards) it should have either one of these value’s E7 B0 at 0000081E & 0E 77 at 00000842 “OR” E8 C0 at 0000081E & 0E 88 at 00000842 “OR” E8 E0 at 0000081E & 0E 8A at 00000842 “OR” EA 60 at 0000081E & 0E A2 at 00000842



BOOTLDR is at 00FC0002 & 00FC0012
CECH-20xx (DYN-001 boards) it should have either one of these value’s 2F 3B at 00FC0002 & 2F 3B at 00FC0012 “OR” 2F 13 at 00FC0002 & 2F 13 at 00FC0012 (this is what’s shown in the picture)
CECH-21xx (SUR-001 boards) it should have the value 2F 4B at 00FC0002 & 2F 4B at 00FC0012
CECH-25xx (JTP-001 boards) it should have either one of these value’s 2F 4B at 00FC0002 & 2F 4B at 00FC0012 “OR” 2F 53 at 00FC0002 & 2F 53 at 00FC0012 WARNING IF IT HAS THIS 2F 5B at 00FC0002 & 2F 5B at 00FC0012 OR 2F FB at 00FC0002 & 2F FB at 00FC0012 STOP NOW YOU CANNOT DOWNGRADE THIS PS3 MODELCECH-25xx (JSD-001 boards) it should have this value 2F 4B at 00FC0002 & 2F 4B at 00FC0012 WARNING IF IT HAS THIS 2F FB at 00FC0002 & 2F FB at 00FC0012 STOP NOW YOU CANNOT DOWNGRADE THIS PS3 MODEL
CECHHxx (DIA-001 boards) it should have either one of these value’s 2F 1C at 00FC0002 & 2F 1C at 00FC0012 “OR” 2E F4 at 00FC0002 & 2E F4 at 00FC0012 “OR” 2E E3 at 00FC0002 & 2E E3 at 00FC0012

If you’re not getting some or none of these then you need to check your wiring and re-dump

Ok now we need to take a look and check there are no malformed headers / file names / region names. This is what we are looking for:-

Correct Malformed location

IFI IJI 00000200

asecure_loader asecure_loaher 00000420

eEID eIIH 00000450

cISD cESH 00000480

cCSD cCSH 000004B0

trvk_prg0 trvg_prk0 000004E0

trvk_prg1 trvg_prk1 00000510

trvk_pkg0 trvg_pkk0 00000540

trvk_pkg1 trvg_pkk1 00000570

cvtrm cztrm 00000600

metldr mitldr 00000820

Now find the same positions as shown in blue in the following pictures yours should match



ASECURE LOADER (00000800)



eEID (0002f000)



cISD (0003f000)



cCSD (0003F800)


Look for SCE on the line below the blue in the following pictures



trvk_prg0 (00040010)



trvk_prg1 (00060010)



trvk_pkg0 (00080010)



trvk_pkg1 (000A0010)

Make sure all the words below the blue in the following pictures match yours



ros0 (000C0000)



ros1 (007C0000)

Make sure the following in blue matches



cvtrm (00EC0000)
note you may get this instead in the blue highlight:
00EC0000 53 43 45 49 FF FF FF FF FF FF FF FF FF FF FF FF SCEIÿÿÿÿÿÿÿÿÿÿÿÿ



0FACEOFF DEADFACE (00F00010)



CELL EXTNOR AREA (00F20000)



bootldr (00FC0000)

extracting your dump

go to FlowRebuilder for extracting your dump



Click extract a byte reversed NOR dump or an interleaved and unscrambled NAND dump



click button next to input file



select your nor dump



click execute program



dump extraction complete. It will put the extracted files into a folder called i.e. (dump.ext) in the same folder where you selected the original one



You should now have these files

If any are missing try extracting again.

now go to the ps3devwiki's validating flash dumps pages and do the checks there
MAIN VALIDATE PAGE
DISCUSSION PAGE WITH MORE CHECKS

Once it all checks out ok upload your dump NOT the file you just created. to a file share site copy the link and CLICK HERE to post your dump. do not use "#ps3downgrade" they nolonget wish to check dumps.
paste your link with “can someone please check my dump. I have followed the guide here (this guide) I have checked it myself.
Once it comes back ok it’s time to patch it (don’t forget to thank the person or persons who checked it for you)

Patching the dump

Patching the dump


Open flow rebuilder and select “PATCH a Byte reversed NOR dump or an interleaved and unscrambled NAND dump”.



Select your nor dump (the one you just had checked)



Select the patch file (c:/progskeet NOR programs/NOR downgrade/progskeet_patch.txt)




Click execute



completed it will put the patched dump in the same folder as your original dump called dump.patch.bin (you won’t see the word .bin at the end)

Flashing the ps3

Flashing the ps3

Turn on ps3 then plug the Progskeet into your pc



Open winskeet & select your NOR



click the NOR tab and click “Dump CFI” this will insure your nor is set right in winskeet



at the bottom it says “options” under that you have 2 drop down boxes set yours as it shows here (these seem to be the best settings) if you don’t change them you may get freezing issues.

if you have some address that simply wont verify then simply change the bottom box to [USB transfer timing (avoid)] (yes i know it says avoid) it takes about 3 min to write each 128kb address but let it. once it has finnished you shouldnt get any verify errors

other settings if you have difficulty flashing

(if you have a spansion p chip then you may get (verification error's) if you do then try (Ready Triggered Timing) as this seems to work on this NOR chip. (thanks to MHMProSoft (ps3hax) for informing me about this)

Originally Posted by 3absiso @Sarah1331 Hi; Will i really do not know if you tried that but; i have done a lot of Spansion P chip and they are a pain: For sure if you have verification errors: it is one of two things or both combined :-): 1- check your wires again and again and make sure they are not touching anything else but since you are doing RGH and you are good in wiring we can roll this out. (but double check). Reading Good Dumb does not mean your wiring is perfect since i had this issue with two Ps3 and get good read but bad write so i did re-wired every thing. 2- the second issue which is the common one and it solved 90% of the problem is: - Use WinSkeet40000_111004 instead of the newest one - connect the Progskeet as libusb Via zadig - write the dumb at 8bit. - use X86 windows 7 or XP this done it for all my Spansion if you still has issues try bridge the (gp4 on progskeet) with (rdy on progskeet) with small wire and wire the (RY/BY# on PS3) to (rdy on progskeet) alone as usual. this is the links for the Programs: http://www.ps3devwiki.com/wiki/Hardware_flashing

click the “flash” tab & select your patched NOR dump (now called dump.patched)



it will read



erase



flash



verify


Repeat the steps until you get this message

Now turn off the ps3, unplug the Progskeet from pc, disconnect the Progskeet from the ps3 (un plug the flat cable if you have the adaptor like mine) (if no adaptor then you need to de-solder the Progskeet)

Finishing the down grade in service mode

Finishing the down grade in service mode

re-insert the hdd then connect the ps3 to a TV the usual way



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.


Unplug the ps3 from the mains. Wait 10 - 15 seconds then plug it back in.
(the wiki says its to discharge the capacitors but as the ps3 is not turned on the capacitors will take many months to discharge.)

Turn the ps3 back on then immediately press eject within ~200ms. Your console will turn on and if your dev usb has led's then the dongle will light up the red LED followed by the green LED and turn back off.



After triggering Factory Service Mode, go to the folder called “service mode files” & in there is a folder called “service mode 3.55 downgrade files” put the contents of that folder into your usb stick and plug it in the PS3's right most USB port (remove the dev usb & put your usb memory stick in its place) REPLACE YOUR HDD (the files are rogero cfw v3.2 and the normal Lv2diag.self (365.5 KB) 3.55 get in FSM )

Turn PS3 on, it will install the firmware you had put there (even though you have no screen output, you can see it is busy by looking at the activity led of the hard drive and of your USB Mass Storage Device).

if you get the flashing green power light then this is due to the firmware not installing. first check your hdd is plugged in properly. this is usually what I forget to do. if it still flashes remove your usb stick put it in your pc and you will see “UPDATER_LOG” as a notepad file upload this to a file share site copy the link and CLICK HERE to enter the chat room. create your nic name press enter then click the green word "#ps3downgrade" to enter the correct room.
paste your link with “can someone please check my updater log. I have followed the guide here (this guide) I cannot get rogero cfw to install in service mode.


PS3 will turn itself back off when it has finished installing the f/w.



Now remove your usb stick put it in your pc and you will see “UPDATER_LOG” as a notepad file open it & look through it to see if it contains errors (if it does upload the log to your file share account and ask for help online on IRC) (it should say at the bottom “0x83manufacturing updating SUCCESS(0x8002f000)”)

Now you need to get the ps3 out of service mode.



Open the folder “service mode files” and inside you will see a folder called “get out of service mode” copy the file inside to your usb stick. Put the usb stick back into your ps3 it will boot then the hdd light will flash then turn off. Remove the usb stick. (the file is Lv2diag.self (201.42 KB) get out FSM)

after that re-build your ps3



turn on your ps3 and it should now boot to this screen follow the on screen instructions

De-hashing

Now to DeHash the console so it is brick protected when / if you decide to upgrade the firmware

THIS IS THE RECOMENDED WAY

QA flag method

Install and run QA-toggle and make sure it beeps
if you just get a blank screen and nothing happens then you have a faulty bdvd and you cannot do this step. try re-marry bdvd found in the main post then try this step again.

to check you are QA flagged Set your cursor on Network Settings and press the key combo (all at the same time):L1 + L2 + L3 (press left stick) + R1 + R2 + dpad_down
if you are QA flagged a new option will show up right below network settings

Power off console
Put unpatched official firmware (e.g. 3.55) on USB Mass Storage device as /PS3/UPDATE/PS3UPDAT.PUP and insert in PS3

Boot into Recovery Menu:
press and hold power button you get 1 beep then a wait then a second beep then the ps3 turns off
press and hold power button again you get 1 beep then 2 beeps let go of power button
select "6. System Update" to reinstall firmware.
If installation finishes without error (there will be no logs you can check!) and boots XMB OK, then dehashing was successful.
Congrats, you now finished downgrading and dehashing. Console runs 3.55 and any firmware of choice can be installed, no longer needing to be patched for downgrader.

DO NOT DO THE SERVICE MODE WAY AS I AND OTHERS GET RLOD EVERYTIME IT IS DONE

Now you should be on 3.55ofw

You can now install the 3.55cfw of your choice

that’s it simple.

[Sarah1331]

Someone check me this over please


Thanks


Sent from my iPhone 5 using Tapatalk

[zapptheman]

ok i was following the tutorial and it says failure to initialize ps3 bios. i have tried putting cons on top of the clips to hold them down firmly but no luck.. could someone please help me. if anyone could do a tutorial on a ps3 fat console it would also help greatly. thanks.

[MJ999]

Originally Posted by zapptheman ok i was following the tutorial and it says failure to initialize ps3 bios. i have tried putting cons on top of the clips to hold them down firmly but no luck.. could someone please help me. if anyone could do a tutorial on a ps3 fat console it would also help greatly. thanks.

Try to use Hard foams.

Did you sand the edges of the clip ?

[Brenza]

Originally Posted by master737373 I wasn't spreading misinformation, I was just saying its safer to manually patch, but you get the same outcome. ************* [ - Post Merged - ] ************* You can read, but not write. It's a bitstream issue.

thanks for reply, do you know if they'll be able to fix it?
I wonder why they sold the chips without testing the software, bah!

[Sarah1331]

Originally Posted by Brenza thanks for reply, do you know if they'll be able to fix it? I wonder why they sold the chips without testing the software, bah!

Not the software that's gone its huge actual "firmware" on the progskeet

But yes it's shocking


Sent from my iPhone 5 using Tapatalk

[the_lost_soul]

OK the irc://efnet/psl1ght --- doesn't not work i have no clue how to get it working

i did this with E3 linker
Now i finished installing my E3 flasher but i have a huge problem.

what did is i has the 1st 2 switches down the others up to update the E3 flasher.
then i pressed the reset button and i has this error: 00001000

then i turned it off unplugged it took out SD card out and pluged it back in then i had 4 blue led lights blinking so i think it was like this 10101010 to 01010101 that sort of pattern and i think there were like 01011001 kinda thing and red screen

then i used the FactoryServiceMode_Lv2diag_RSOD to fix the red screen thing.

sort of fixed it.

i the turned ps3 off took of cover board plugged back in the ESATA connection held the power button on until second beep and it works like a charm XMB working perfectly.

when i plug cover board back in red screen of death.
so what am i doing wrong? i think the update killed the cover? board the update.bin

or what is the the difficult switch layout for cover board?

atm i have it on like this 1=down 2=down 3=up 4=down 5=down 6=down

and ps3 is not dual boot
************* [ - Post Merged - ] *************
Nm i set all the switches to down now it works.

but still the upgrade failed at 1st all the lights were on after upgrade. then i preset the Reset button under the cable and i had 1 light on like this
00001000

what is safest way of having the switches arranged by of by accident you preset start without the SD card in?

i don't want to end up flashing to NOR with no data and end up bricking PS3 4 good.

what does that mean did upgrade go successful?
************* [ - Post Merged - ] *************
OK when ps3 boots with TF cover board there are 4 lights that are on blinking like Christmas lights going left right left right and so on.

when i try to make a back up of NOR i get the middle light as a solid colour a few seconds later i get the 1st and 6th blue lights flash rapidly and the 5th one remains a solid blue

so 10001100
************* [ - Post Merged - ] *************
should i just just disorder the linker and try on the clip instead?
************* [ - Post Merged - ] *************
if i were to go with the ribbon cable do i still need to solder on SBE, SBCE, BVCC, VCC on the ribbon cable?

and what are they used for?

or can i just clip it on and that's it?

[jeeqer]

Originally Posted by Sarah1331 What flasher are you using?? It's most likely wiring issue Sent from my iPhone 5 using Tapatalk

thanks sara, i am using progskeet v1.2