Most of you have heard the news of the PS3 slim downgrade on firmware 3.70, helping those buying newer or updated PS3 slim consoles to the scene. At the moment push aside “soft modding” and its time to bring on the good ole’ soldering iron back out.
This new method of downgrading basically requires the soldering of a multi-console-compatible chip known as ProgSkeet (or clone) which you can find or purchase HERE…or you can use Teensy++ board if you still have those from the good dongle days. A solder-less ProgSkeet is in the works, more info here.
Now the original tutorial was released in a very technical form and in Spanish, but we at PS3Hax have got you covered, and are bringing you easy to follow tutorial that a noob can follow on. This tutorial is long, but it is more detailed than complicated, making sure your bases are all covered.
So lets get started, this tutorial is split into multisteps. You should also check out the posts made here, and the posts that will be made in this thread to get assistance. The following tutorial was modified from the original Spanish translation by Dospiedras1973, and the tutorial/images were modified from PS3Hax member Mattr92 tutorial over at his site: RootedSystem and and thanks to the many PS3Hax members that brought us the proper/native translation of the original instructions .
Highly advised you read this tutorial fully once, and then again and read the comments in this thread and the other threads linked above to get a GOOD understanding of what your getting yourself into and how the entire process works. Remember, this should be a fun and rewarding experience
DISCLAIMER: PS3Hax.net is not responsible for any damage caused to your system. We do not claim credit for this method, we simply have compiled and reorganized the information so it is easier to follow. I kindly request for other sites to not rip this entire tutorial to their websites, but instead link to this page if you wish to share it on your webpage. This page will be actively updated so please keep checking back to find solutions to encountered/discovered problems.
A PS3 (phat or slim) running PS3 original firmware 3.70 and has NOR memory, not NAND, and has ProgSkeet/Teensy++/Clone installed(click here to check if your console has NAND or NOR) – Note: This guide covers ProgSkeet install.
If your a noob (and I assume most of you are), it may be a good idea to have some what of a idea on what NAND/NOR is. It is basically the PS3 flash memory. If you want to get a better understanding of the PS3 system and its various components, you should check this out.
To quote:
The PS3 has 256 megabytes of flash memory to store firmware, using two NAND 128MB Samsung flash chips. The installed firmware data is interleaved between the two flash chips for speed. To prevent errors, Error Correcting Code Checksum (ECC) is added/used on the data in the PS3 flash chips. In newer PS3, a single 16MB Spansion flash chip is used.
Because of the smaller flash chips in later versions, newer firmware versions allow for the firmware data to be partially stored on the harddrive (instead of totally inside the flash), making the flash purely responsible for holding data involved in the critical booting up process. This allows for cheaper flash chips, while using the harddrive for later bootup stages.
To summarize now we are going to be downgrading a PS3 via NOR flasher, so the PS3 MUST have NOR memory most PS3 units have NOR now, the stock/initial PS3s (phat) that were released had NAND, there is a chart linked above so you can make sure. As of now, all SLIMs have NOR memory so your good to go .
First thing is first you have to install ProgSkeet. You can install Teensy++ board as well, or any other ProgSkeet clone but I don’t know how they work and I assume you need to substitute the tools/files for Teensy++.
So there are plenty of good threads to first checkout related to ProgSkeet, for starters this is what ProgSkeet is:
ProgSkeet is your one and only solution to your flashing needs. Whether it is NAND, NOR or any other kind of non-volatile memory – just solder, plug in and operate!
Works on various other devices (in addition to PS3) and consoles including Xbox 360 and Wii.
Here is a sample image of some ProgSkeet installs (gets you an idea what your getting into):
THERE IS CURRENTLY A SOLDERLESS CHIP IN THE MAKING, BUT AS OF NOW (8/20/2011), YOU MUST SOLDER AND PERFORM THIS METHOD IF YOU WISH TO DOWNGRADE FIRMWARE 3.70
Make sure your PS3 first has NOR memory, all SLIM PS3′s do, the older “phat” PS3 have NAND. Check if your console has NOR memory here.
Find the right pinout for your PS3 motherboard HERE. (Scroll down to “Pinout Gallery“). Additional ProgSkeet pinouts HERE. Teensy++ Pinouts located HERE.
Gather soldering tools, resin, and wire.Recommended gauge for wires: 24 (anything from 20-26 AWG is fine). Keep them at ~20cm each. – Note: 40/80 wire Floppy cables won’t work, to see a full list of compatible wires see this table.
Here are 2 “prep” videos for your ProgSkeet:
STEP 4 – The NOR Dumping
Now the actual work begins and the part you all have been waiting for, the NOR dumping!
Install Microsoft Visual C++ 2008 SP1 Redistributable Package (x86) [Download Here]
Restart your computer.
Launch the ProgSkeet Dumper
Plug in your ProgSkeet and wait for for the jingle/beep
Insert the following values for the NOR: if you have a SPANSION branded flash memory on your PS3 then: NOR Sector Size = 128kb / NOR Sectors = 128. If you have a SAMSUNG branded flash memory on your PS3 then NOR Sector Size = 4kb / NOR Sectors = 4096.
After getting the correct values inserted, select output and then press DUMP, and you should have the exact dump generated as seen in Part B.
Dump the NOR from your PS3 with the ProgSkeet/Teensy++ it should be exactly 16,777,216 bytes. If it is not, go back to part A, and keep re-dumping until it is. Make sure its down to the byte.
Next open up Transplante.exe, in “donador” select your nor-dump.bin.REV and for “receptor” select downgrade.bin and click GO.
Now that your downgrade.bin is successfully hexed open Flow Rebuilder back up. Select “Byte reverse and extract a NOR Dump” and drag downgrade.bin to the bottom option and click “Execute Operation”.
You will now be presented with an error, this is normal. All you are interested in is the file generated: “downgrade.bin.REV” -> This file will be flashed onto your PS3.
Now comes the last, and actual flashing part. Make sure you follow all the instructions above to the letter, and if you have any issues report them before continuing.
From the ProgSkeet flasher you downloaded in step 1, flash the file you generated in step 2 #5: downgrade.bin.REV to your PS3 (make sure your PS3 is on during this process).
If you flashed your PS3 correctly, your PS3 will reboot and show this message: “Push PS button”. DO NOT PRESS THE PS BUTTON!
Turn off the PS3 console as we will now place it in Factory/Service mode.
Copy these files to the ROOT (not subforulder!) of USB Mass Storage Device-: **WARNING: Make sure that this is a USB stick formatted to FAT 32. DO NOT use your MP3 player, phone, or anything except a USB stick as the timings are crucial for the downgrading process! If your having issues, we recommend you reformat your pen drive/usb drive with THIS tool.
Kmeaw CFW PUP File (3.55) [Download HERE or Mirror]
Insert to right most USB port on PS3
Now turn on your PS3 and leave it alone, the PS3 should turn off by itself in 10-15mins.
Unplug your USB from the PS3, and turn the console back on. It should boot to the XMB menu, once it does this turn your PS3 off again.
Now copy and replace this file on your USB: Modded LV2Diag [Download Here]
Insert once again to the right most USB port on your PS3
Turn on your PS3, it should turn off by itself in about ~20 seconds.
You have now successfully downgraded, and installed 3.55 KMEAW CFW on your PS3! You can check out our forums for more info on various homebrew, or drop by our tutorial section for more neat things you can do with your unlocked PS3 .
Don’t use any USB Mass Storage Device with enhanced functions as: encryption, fingerprintreader, U3, pincode etc.
Don’t use USB Mass Storage Devices with a long initialisation time (e.g. some MP3 players)
Don’t use multipartitioned USB Mass Storage Devices, only use 1 single primary FAT32 partition.
Make sure they are formatted according to specifications with FAT32 (e.g. HP USB Format Tool – or TOKIWA / Ridgecrop FAT32 formatter)
Most USB Mass Storage Devices that’ll work effortless with PenDrive Linux, will also work with the PS3 (for downgrading, upgrading, storage of your Game dumps and any normal filestorage under the XMB). Those USB Mass Storage Devices are most likely also the ones giving you the least problems under more exotic platforms like PSX/PSone, PS2/PStwo, Xbox/X360, Gamecube/Wii etc.
The libusb-win32 Kernel Driver needed for the the flasher to get access to the USB port was not installed. Make sure you unpacked the drivers_xxxxxx file and installed the Progskeet driver (VendorID:1988 / ProductID:0001 in case you need it).
In case of “the application has failed to start because its side-by-side configuration is incorrect” make sure Microsoft Visual C 9.0 runtime is installed and “Windows Installer” is not disabled (set to manual or automatic) in Services.msc
And to support Samsung you need the latest Progskeet flasher: 110819
All versions before that will not dump/flash Samsung memory.
With the latest Progskeet flasher, it has "ByteSwap" feature, that should remove the need for FlowRebuilder to swap the bytes around, but I can't personally confirm it, as I have not tested the new feature.
And to support Samsung you need the latest Progskeet flasher: 110819
All versions before that will not dump/flash Samsung memory.
With the latest Progskeet flasher, it has "ByteSwap" feature, that should remove the need for FlowRebuilder to swap the bytes around, but I can't personally confirm it, as I have not tested the new feature.
? would you lose your DLC if you downgraded? i am thinking about updating to 3.70 to get some DLC and then using this to get back onto CFW but want to make sure first..
? would you lose your DLC if you downgraded? i am thinking about updating to 3.70 to get some DLC and then using this to get back onto CFW but want to make sure first..
From my understanding a downgrade formats your HDD.
This is an awesome tutorial (especially for those with soldering skills and an old teensy laying around ) Once the solderless solution is made available that should help a lot of people out. Upgrade if you want to be on latest firmware or downgrade if you want MFW and homebrew. This is great news for people that do not want to have 2 ps3s.
So what happens if this is attempted on a factory base 3.56 firmware PS3?
If its already on 3.56 or greater there is no way check first...
Originally Posted by BobbyBlunt
From my understanding a downgrade formats your HDD.
What happens is that the Registry is lost. (Flash2)
If the PS3 can not find a matching serial number for the HD in the registry it will want to format it.
Also the entire house of cards collapses for PSN\DLC because there is also no matching PSN account information in the Registry.
If you have a back up of Flash2 and the "exdata" folder from a previous jail break you might get lucky.
As for BluRay its always best to know the highest MKB version that has been played in the PS3 prior to Downgrading. (Flash3)
Be ready with the required BRD and DRL's to restore BluRay playback if needed.
Right now your best bet might be to use the PS3 backup utility.
It will restore ALL content, but it wont restore the ACT.DAT or .RIF files if the PSN account information associated with them cannot be found in the current Registry. (Flash2)
No way to get back on PSN, no Flash2 or "exdata" folder back up means no chance at DLC re-activation.
Hopefully someone comes up with a PS3 Backup image decrypter.
Its very possible to reconstruct the Registry but the current ACT.DAT and .RIF's are locked away in that archive until it can be decrypted and the files extracted.
i think RSOD caused by hardware failure. that could be anything, like blueray, harddrive, corrupted firmware, or even the board itself.
sony always give a full replacement (if still under warranty) for rsod problem, don't know why
I flash the file "downgrade.bin.REV" to that extent .REV?
It is possible to solve brick?
Yep, you flash that file with the .REV extension. As for your second question, there has been no hard evidence to say if the progskeet can recover a bricked console successfully (other than the waninkoko brick) but it is very possible.
Love the tutorial. Started work on this when the originally translated one came out, confusing as hell. 1 thing missing from this is the Step 4 Part B, 1st step there should be to bytereverse before doing the auto hex editing...
Anyways, Got everything wired up, DIA-002 board, Teensy++ 2.0 using V.01 of NORway. Firmware dump went fine, dumped a few times and used totalcommander to compare, everything matched. Went through the steps on this tutorial using the autohex program, got my flash ready to write, and queue major issue. Won't write. Commands good, checked every single wired connection with multimeter, all good and proper... NORway goes through to the write screen, but NO progress at all. Just sits there like a dumb ass. Incase this was normal, I left it in that state all night. Still nothing in the morning.
Any ideas? I am all out, thinking I might have to wait until more people give this a shot and run into the same issue. Used the following diagrams for wiring up the board (attached)...
Love the tutorial. Started work on this when the originally translated one came out, confusing as hell. 1 thing missing from this is the Step 4 Part B, 1st step there should be to bytereverse before doing the auto hex editing...
Anyways, Got everything wired up, DIA-002 board, Teensy++ 2.0 using V.01 of NORway. Firmware dump went fine, dumped a few times and used totalcommander to compare, everything matched. Went through the steps on this tutorial using the autohex program, got my flash ready to write, and queue major issue. Won't write. Commands good, checked every single wired connection with multimeter, all good and proper... NORway goes through to the write screen, but NO progress at all. Just sits there like a dumb ass. Incase this was normal, I left it in that state all night. Still nothing in the morning.
Any ideas? I am all out, thinking I might have to wait until more people give this a shot and run into the same issue. Used the following diagrams for wiring up the board (attached)...
Any help is appreciated!
have you tried using the latest NORway? i believe it's 0.3 already....
I see, so you are powering the teensy using the ps3 motherboard? With 5 volt trace cut and the 3 volt pads bridged?
No cut traces or anything. V0.1 indicates no power and no cutting traces, that started with v0.2... Unless I am mistaken?? The teensy is begin powered by the usb connection to the PC as far as I know.
No cut traces or anything. V0.1 indicates no power and no cutting traces, that started with v0.2... Unless I am mistaken?? The teensy is begin powered by the usb connection to the PC as far as I know.
Ah. I just looked over the .01 readme and you are correct. I really didn't get to use version .01 so I am not able to pin point your exact problem. I would just play it safe and wait until your voltage regulator arrives so you can use the new version which working properly.
By the way, your NOR chip is a Spansion right? Currently NORway (all versions) is only able to read/write Spansion and only read Samsung.
Ah. I just looked over the .01 readme and you are correct. I really didn't get to use version .01 so I am not able to pin point your exact problem. I would just play it safe and wait until your voltage regulator arrives so you can use the new version which working properly.
By the way, your NOR chip is a Spansion right? Currently NORway (all versions) is only able to read/write Spansion and only read Samsung.
You had me worried, I was unaware that the make of the chip was important, checked the PS3 Wiki and looks like that is not the problem
"CECHH/DIA-001 up to including CECHK/DIA-002 : 1x Spansion S29GL128N90TFIR2 (NOR 16MB) "
So yeah, looks like I am in a holding pattern until those voltage regulators arrive. Appreciate the help anyways!
Yep, you flash that file with the .REV extension. As for your second question, there has been no hard evidence to say if the progskeet can recover a bricked console successfully (other than the waninkoko brick) but it is very possible.
Thank you very much
************* [ - Post Merged - ] *************
Is this normal? Flash sector skipped?
No cut traces or anything. V0.1 indicates no power and no cutting traces, that started with v0.2... Unless I am mistaken?? The teensy is begin powered by the usb connection to the PC as far as I know.
The voltage regulator is not optional! Do not run the teensy at 5V!
I just can't update any existing v0.1 readmes out there, that's the reason for a v0.2.
hey wait thats very great i want to go back to psn because deleted my modnation racers dlc and stuff i want to go back to psn to redownload and downgrade if i do that will i loose all the dlcs and stuff ? also is there a solderless method this is very complicated
just a patch or something without opening the ps3 and buying teensy or something my country also doesnt have a teensy please man make a solderless thingy with just a simple patch
The voltage regulator is not optional! Do not run the teensy at 5V!
I just can't update any existing v0.1 readmes out there, that's the reason for a v0.2.
So the regulator is required for even v0.1? If so, that is perfect, it explains why I can't get anything written to my PS3... I was worried that even with v0.3 I may still have issues. That's good news, anxiously awaiting my voltage regulators!! Now, this being the case, do you think the dump would have been effected? When trying to write, it did at lease erase the NOR so I have a completely responseless PS3 right now. So long as it does not effect the dump, I should be good... If it did, I think I am screwed. Any thoughts??
Thanks!
Yes. Without voltage regulator you might fry your NOR (although this didn't happen yet).
Originally Posted by WesTek
If so, that is perfect, it explains why I can't get anything written to my PS3...
No, it doesn't. If you have a Samsung NOR it would explain why you can't write. Writing Samsungs is not yet supported. But a beta is already being tested.
Originally Posted by WesTek
Now, this being the case, do you think the dump would have been effected? When trying to write, it did at lease erase the NOR so I have a completely responseless PS3 right now. So long as it does not effect the dump, I should be good... If it did, I think I am screwed. Any thoughts??
Thanks!
It's really crucial that you guys check your original dump before writing anything new to your flash. A really simple wiring mistake (unconnected address or data line) renders your dump unusable. This should be mentionend in this tutorial.
Yes. Without voltage regulator you might fry your NOR (although this didn't happen yet).
No, it doesn't. If you have a Samsung NOR it would explain why you can't write. Writing Samsungs is not yet supported. But a beta is already being tested.
It's really crucial that you guys check your original dump before writing anything new to your flash. A really simple wiring mistake (unconnected address or data line) renders your dump unusable. This should be mentionend in this tutorial.
So FYI, I read the tutorial and made all the steps to make sure my wiring was good. I am a professional modder of 10 years or so, not a rookie. I am hoping my NOR is not fried... As I said, I followed the tutorial to the letter, unfortunately, I did not have a power regulator as it was not required on v0.1... Also, Do not have a Samsung NOR. Double checked original NOR dump (Multiple dumps) with totalcommander and got exact matches across the board. Checked contents and it has pulled the info from the NOR. So, if the lack of voltage regulator would not effect the writing, and the wiring is good (Checked twice with multitester), are you telling me I fried my NOR??
When Writing, it says writing byte 0000000 or however many zeros in there, and does not move. The lack of the voltage regulator will not make this happen?? You can check the top post of page 4 which shows the diagrams I used to wire all this up. Everything has been done to the letter except of course for the voltage regulator which I was under the impression was not necessary. Would appreciate more advice.
************* [ - Post Merged - ] *************
Originally Posted by enohand
without digging through 5+ pages of good read right now while im at work.....
does this only work on slims? no phat love?
Works on Phat too... Although running into issues myself. Your PS3 has got to have a NOR chip, not NAND, and the chip cannot be Samsung. If you fit the bill, it can be done... Although, as I said, running into issues with mine. Hopefully they can be worked out.
So FYI, I read the tutorial and made all the steps to make sure my wiring was good. I am a professional modder of 10 years or so, not a rookie.
Don't get me wrong, didn't mean to offend you. It was more like a general statement to point out that a perfect dump is crucial.
Originally Posted by WesTek
So, if the lack of voltage regulator would not effect the writing, and the wiring is good (Checked twice with multitester), are you telling me I fried my NOR??
Your NOR is probably still functional if you still can dump. I did it many times without voltage regulator (also writing) and it didn't do any harm. Applying 5V signals is just beyond spec.
You might want to check the WP# line on your board. On mine it's always tied to Vcc, and the WP# line isn't controlled by the teensy.
Sorry but ow may god what are you lot doing without a regulated 5v psu, and it should be 3.5 not 5v. Use a 3-4 volts rechargeable battery, as that's the best cleanest regulated power to use for what you are doing. And if your using a multimeter to test with, then use resistance not CONTINUITY as you will kill it.
Keep the wires short and together to keep ingress and RFI down. And use stattic straps.
Step1 - step 4 finished n i stuck in step 5 because when i want to flash it, the downgrade.bin.Rev not detected. can somebody tell me why when i click the flash button on progskeet flasher, the downgrade.bin.REV not showing, just showing downgrade.bin?
Sorry for my bad english. Tq.
Step1 - step 4 finished n i stuck in step 5 because when i want to flash it, the downgrade.bin.Rev not detected. can somebody tell me why when i click the flash button on progskeet flasher, the downgrade.bin.REV not showing, just showing downgrade.bin?
Sorry for my bad english. Tq.
Sorry i may sound a tool saying this as i am not playing with this myself.
Do you not just rename it from downgrade.bin.REV to downgrade.bin before you try flashing it, because you flash with .bin's not .REV's.
n if i checked the "ByteSwap" on progskeet flasher, i don't need to use FlowRebuilder, right?
I just dump (checked ByteSwap), then use transplante,
n then flash (checked ByteSwap) it, right?
Don't get me wrong, didn't mean to offend you. It was more like a general statement to point out that a perfect dump is crucial.
Your NOR is probably still functional if you still can dump. I did it many times without voltage regulator (also writing) and it didn't do any harm. Applying 5V signals is just beyond spec.
You might want to check the WP# line on your board. On mine it's always tied to Vcc, and the WP# line isn't controlled by the teensy.
No worries, not offended... Just wanted to make sure you understood I was no noob and can read instructions. I will check the WP# line to make sure it is tied in... Will also try another dump although the write, even though it stayed at 000000, seems to have at least done the erase... PS3 does not boot... Will see if dumping gives me an error or anything. Might even try writing on another PC incase the issue is PC related and not Teensy related. Appreciate the advice. Will let you know how things go.
************* [ - Post Merged - ] *************
Originally Posted by Dev-Dave
Sorry but ow may god what are you lot doing without a regulated 5v psu, and it should be 3.5 not 5v. Use a 3-4 volts rechargeable battery, as that's the best cleanest regulated power to use for what you are doing. And if your using a multimeter to test with, then use resistance not CONTINUITY as you will kill it.
Keep the wires short and together to keep ingress and RFI down. And use stattic straps.
Didn't use a regulator because the instructions did not require it... Although I have already been corrected. Regulators on the way. Will try keeping my wires together a bit more, a few are straying, so maybe that is the issue. Thanks for the advice.
There is this one thing I dont understand about the progskeet . Does it means I have to open the console and so some soldering works or it is something you install from a usb anyway please help me
There is this one thing I dont understand about the progskeet . Does it means I have to open the console and so some soldering works or it is something you install from a usb anyway please help me
another yes, it means you have to buy the progskeet,open the console,do some soldering on the progskeet, do some soldering on your PS3 motherboard,dump your NVM,modify your dump,flash your modified dump back,do some usb storage's things,power up your console,and you're done.
I'm a big n00b as the title explains, so I was wondering how do you get to the motherboard, I know you can totally take the PS3 apart to access it but then I don't know what to do. Is there a way to view the motherboard while the PS3 is on. Sorry for being such a n00b
I'm a big n00b as the title explains, so I was wondering how do you get to the motherboard, I know you can totally take the PS3 apart to access it but then I don't know what to do. Is there a way to view the motherboard while the PS3 is on. Sorry for being such a n00b
no way. just my advice if you don't know what to do, don't do it
I know how to solder and use Progskeet, just accessing the motherboard is where I'm somewhat lost. I would be very grateful if you just pointed me in the right direction at the least.
I know how to solder and use Progskeet, just accessing the motherboard is where I'm somewhat lost. I would be very grateful if you just pointed me in the right direction at the least.
Okay that helped a lot thanks, I found my motherboard, downloaded the diagrams and got to map out where I would have to solder on the Progskeet, but just one more question (thanks for all the help BTW) When you disassemble the PS3 to get to the motherboard is there a way to still see the motherboard without reassembling it. Thank you for all the help again.
Okay that helped a lot thanks, I found my motherboard, downloaded the diagrams and got to map out where I would have to solder on the Progskeet, but just one more question (thanks for all the help BTW) When you disassemble the PS3 to get to the motherboard is there a way to still see the motherboard without reassembling it. Thank you for all the help again.
see the whole motherboard is impossible i think. because you have to put your fan and heatsink back to the board, connect the psu, blueray drives and hdd.
but when i connected my teensy++ to my ps3, i set it upside down, so i can see the connection i made and the whole bottom of the board.
see the whole motherboard is impossible i think. because you have to put your fan and heatsink back to the board, connect the psu, blueray drives and hdd.
but when i connected my teensy++ to my ps3, i set it upside down, so i can see the connection i made and the whole bottom of the board.
Okay that makes better sense, and I was just wondering in your opinion is the Progskeet or the Teensy++ better, cost wise and size wise, because I was wondering if they fit right on top of the motherboard with the PS3 all closed up.
Okay that makes better sense, and I was just wondering in your opinion is the Progskeet or the Teensy++ better, cost wise and size wise, because I was wondering if they fit right on top of the motherboard with the PS3 all closed up.
they both are good device to dump/flash, and fit on your PS3.
but since teensy++ haven't supported samsung's NOR yet, it depends on your type of flash memory. if you have samsung/macronix NOR, i think you should buy a progskeet which have more compatibility than Teensy++, for now.
i have 1 CECHL console with Spansion chip, and i used Teensy++ permanently on that. but i also have 1 CECH2xxx in RSOD (which i tried to recover) with samsung NOR flash, so i ordered Progskeet to use with it.
they both are good device to dump/flash, and fit on your PS3.
but since teensy++ haven't supported samsung's NOR yet, it depends on your type of flash memory. if you have samsung/macronix NOR, i think you should buy a progskeet which have more compatibility than Teensy++, for now.
i have 1 CECHL console with Spansion chip, and i used Teensy++ permanently on that. but i also have 1 CECH2xxx in RSOD (which i tried to recover) with samsung NOR flash, so i ordered Progskeet to use with it.
Yea I have a CECH-2001A the 120g, are there any unnecessary parts that don't need to be put back in so you can get to the Progskeet easier.
No worries, not offended... Just wanted to make sure you understood I was no noob and can read instructions. I will check the WP# line to make sure it is tied in... Will also try another dump although the write, even though it stayed at 000000, seems to have at least done the erase... PS3 does not boot... Will see if dumping gives me an error or anything. Might even try writing on another PC incase the issue is PC related and not Teensy related. Appreciate the advice. Will let you know how things go.
************* [ - Post Merged - ] *************
Didn't use a regulator because the instructions did not require it... Although I have already been corrected. Regulators on the way. Will try keeping my wires together a bit more, a few are straying, so maybe that is the issue. Thanks for the advice.
OK... @ judges... You hit the nail on the head with the WP#... My board (DIA-002) is missing that point, didn't think much of it as the teensy diagram did not have it on their either, figured that was a progskeet thing that was not necessary... So, I have no WP# at all. Any idea where I can find that on my board and what point on the teensy that would connect to? It also was not in the v0.1 list of points. I think you can fix me by explaining what to do about the WP# line! Getting hopeful! Look forward to your response!
Update: Also tried re-dumping. Looks like about a 10th of my NOR has been wiped then after that the new dump matches my old dump... Looks like it partially erased before it started messing up. So NOR is still accessible, just partially wiped at the moment. I also checked out your V0.3, still indicates no WP# line necessary but the situation fits, unable to write because the write protect is kicking it's ass... Really hope you have a suggestion or two to throw my way.
OK... @ judges... You hit the nail on the head with the WP#... My board (DIA-002) is missing that point, didn't think much of it as the teensy diagram did not have it on their either, figured that was a progskeet thing that was not necessary... So, I have no WP# at all. Any idea where I can find that on my board and what point on the teensy that would connect to? It also was not in the v0.1 list of points. I think you can fix me by explaining what to do about the WP# line! Getting hopeful! Look forward to your response!
Update: Also tried re-dumping. Looks like about a 10th of my NOR has been wiped then after that the new dump matches my old dump... Looks like it partially erased before it started messing up. So NOR is still accessible, just partially wiped at the moment. I also checked out your V0.3, still indicates no WP# line necessary but the situation fits, unable to write because the write protect is kicking it's ass... Really hope you have a suggestion or two to throw my way.
Assuming this picture of the motherboard is similar to yours (DIA-001,) get the data sheet of your NOR and test with a multimeter to see if the WP test point in the picture is on your motherboard:
Here is some info from Judges regarding WP#
Originally Posted by judges
I'm really not much of a hardware guy, but if WP# isn't set to "HIGH", you cannot write (refer to the data sheet). I didn't care about it, because it's always "HIGH" on my board ("WP# tied to VCC"). If there are other boards out there, you might want to adjust that.
You could connect it to the last available IO pin (PB7) and adjust the code or connect WP# to VCC (please double check, "I'm not much of a hardware guy").
Not having one to try my theory so forgive if I'm talking out my ass, but would it make sense not to have the write line open when you are simply just taking a dump, maybe by switch or not connecting wire till you are flashing, less chance of corrupting your backup. Sorry if foolish, just a thought.
Assuming this picture of the motherboard is similar to yours (DIA-001,) get the data sheet of your NOR and test with a multimeter to see if the WP test point in the picture is on your motherboard:
Here is some info from Judges regarding WP#
Thanks for the info. That diagram was the same one I used to wire up my board although as I mentioned, the WP# point is not on the DIA-002, other than that the wiring was identical to DIA-001. Took your advice, found the datasheet and the WP# leg on the IC. Luckily it was directly connected to a resistor, easier to solder to that than the IC leg, tied that directly to VCC. Still not writing. Not much of a coder so no idea how to edit the hex to get that last point on the teensy to accept the WP#. Getting closer but still no joy.
Update: Also just noticed CE in Norway comes up as false in the status when dumping and writing... I am assuming that should be true for everything to work since it is a chip enable input?
Thanks for the info. That diagram was the same one I used to wire up my board although as I mentioned, the WP# point is not on the DIA-002, other than that the wiring was identical to DIA-001. Took your advice, found the datasheet and the WP# leg on the IC. Luckily it was directly connected to a resistor, easier to solder to that than the IC leg, tied that directly to VCC. Still not writing.
This is the wrong thread. Please refer to my previous answer here:
Yes but use the ata/66 80 strand ide ribbon. not the 40, although 40 is ok 80 better, try to keep the ribbon together rather than taking a wire off at a time
I have a little problem (I'm thinking so). I installed very good and clear solders of the progskeet. My purpose downgrade the PS3 with 3.70 software.
I modiffied the the downgrade.bin file with my original dump.bin file. And then I'm trying to flash to PS3. Flashing is succesful but I have no happy ending According to tutorial after the flashing PS3 will boot but I can't see anything like this!
My original dump is safer when I flash back to PS3 original dump is working. If I flash the downgrade.bin.REV it makes brick PS3. I can't open the PS3. When try to open the machine it open then close in 1 or 2 seconds. The red light makes blinking.
thank you ogel2 for your answer....yes unfortunatly teensy is only for NOR (at least for now)
but, if i only try get a dump???
and what diagram i should use for my SEM-001 MB??
thank you once more
update:
i already get my ps3 on 3.55 cfw (phat ps3)...i only want learn how to dump my ps3, because i want try to get (somehow) the keys 3.56+...
http://www.360-clip.com/ will this be ok to use with progskeet and teensy? It has fewer soldering points?
i don't know if xbox NAND will have the same dimension with ps3 NAND, but if they do, i think that would be ok
Originally Posted by tmiguel
thank you ogel2 for your answer....yes unfortunatly teensy is only for NOR (at least for now)
but, if i only try get a dump???
and what diagram i should use for my SEM-001 MB??
thank you once more
update:
i already get my ps3 on 3.55 cfw (phat ps3)...i only want learn how to dump my ps3, because i want try to get (somehow) the keys 3.56+...
well,i don't know about that, because i haven't see a diagram to connect teensy with NAND (yet) and you should make your own flasher program or try using arduino method. AFAIK NORway is only for teensy++ v2.0 and use to flash/dump PS3 with NOR flash (except for samsung NOR, judges is on his way to figure it out)
hello guys excuse my English I am Brazilian.
I've got a problem with the flash. I'm using progskeet.
I managed dump samsung.
when flash ended my ps3 does not appear but . black screen with LED lit. Could someone help me.
put file dump file to download
I have same problem. When I flash downgrade.bin.rev PS3 stay on black screen and led is green. When I flas back my dump ps3 power on back with 3.70 on it
Spansion flas mbo FAT VER-001
I AM STUCK HELPPPP! ok i have opened my ps3 soldered the wires to the correct places i have done the dump thing. now when you dump the new .bin on your ps3 you have to have a wire connected to the progskeet and the computer. my prob is do you put the ps3 back together then go through the downgrade process or do you leave the ps3 open (leaving the motherboard open to the outside) and the start up the ps3 and dump the new .bin . if you do put back together do you have to put a hole somewhere in the ps3 for the wire to go through to then be connected to your ps3????? answer would be deeply appreciated!!
how can i play batman arkhum city on 3.55 pls tell me . Also can i play Batman arkhum city on 3.60 or not ? And last tell me how can i downgrade 3.60 to 3.55 ?
This tutorial is outdated if you use winskeet (this whas my nor flash)
flowrebuilder or transplant is not needed anymore (flowrebuilder is still required to check the dump)
use the dospiedra v2 patches
open winskeet select the patch tab
at the input file line put your backup.bin
and at the patch file line choose the progskeet_patch.txt like this
now click apply and the program asks where to store the file and what name you would like for the patched backup.bin
flash the patched backup.bin reboot and put it in service mode with your dongle
now follow the steps to actualy downgrade to 3.55 with the usb stick
Does this method work for downgrading to 3.55 from a 3.73? I have tried a lot of .PUP files out there hoping I could make some progress. And have came up empty handed left and right. So fed up with surveys, password locked files, and potential viruses. (thank god for a kickass antivirus! ).So yeah, if someone could clue me in on how I could possibly do this downgrade via Progskeet, E3 flasher, etc... I will love you forever! A million thanks!!!
Does this method work for downgrading to 3.55 from a 3.73? I have tried a lot of .PUP files out there hoping I could make some progress. And have came up empty handed left and right. So fed up with surveys, password locked files, and potential viruses. (thank god for a kickass antivirus! ).So yeah, if someone could clue me in on how I could possibly do this downgrade via Progskeet, E3 flasher, etc... I will love you forever! A million thanks!!!
wich ps3 model do you have?
downgrading with a .pup file isn't going to work on 3.73
if ur lucky you can use progskeet to downgrade
i would stay away from E3 flasher as it bricks lots of systems
Hey, I was wondering if I could do this of my stock firmware was 3.66. I'm reading on some tutorials that if the stock firmware was 3.56+ then I can't do it.. Thanks!
Hey, I was wondering if I could do this of my stock firmware was 3.66. I'm reading on some tutorials that if the stock firmware was 3.56+ then I can't do it.. Thanks!
No you cant, factory firmware has to be 3.55 or below.
Anyway back to my question, i cant seem to find a decent NAND downgrading tutorial/video anywhere, any chance someone who has done this to a ps3 with NAND could make a tut please.
i just read that progskeet is now compatible to downgrade for 4.0 as well but i am guessing there might be some files that are specific to this firmware so was wondering is it possible to get these files and also i think its good time to update this post for the latest firmware as i trust only this website on the final say of the firmware hack for ps3 (DUH!)
i have slim running 4.0 any issues to downgrade by buying the progskeet?
Witch dongle is best to put the ps3 in factory mode? I was searching and most of then talk about jailbraiking from 3.41. E3 card reader or EcliPS3 are able to put the ps3 in factory mode?
No you cant, factory firmware has to be 3.55 or below.
Anyway back to my question, i cant seem to find a decent NAND downgrading tutorial/video anywhere, any chance someone who has done this to a ps3 with NAND could make a tut please.
Wow.. Just bought Teensy for nothing then. Woops haha. What about E3?
Wow.. Just bought Teensy for nothing then. Woops haha. What about E3?
E3 Only downgrades NOR Chips, which are found in PS3 Slims and some of the old fats
If you have a FAT model with CECHH or above then you have a NOR chip, if its below that it will be NAND
If you have a ps3 slim it will have NOR but it has to be a certain model for it to be downgraded, if your slim is a CECH-20..A upto cech-251.B then these models can be downgraded, anything that was made after them cannot be downgraded
Progskeet can downgrade both NOR and NAND you just need the right 360 clip for your chip
E3 - Only NOR chips
I'm thinking of getting a progskeet and having my friend solder it in for me, my ps3 is a fat with nor I believe. CECHP01 Hes an expert at soldering and then from there I can do the software side....
I was at a party this weekend and someone updated it via a disc. I've also thought about using teensy++. The main thing I'm worried about, is keeping my files on my hdd intact. Do I have to format my hdd, or will I still be able to use it?
Also If I Use progskeet does it fit in the ps3 with it together?
Could I use this method to unbrick a 3.41 cfw PS3? I messed up appldr and now it seems to be unable to boot into anything, even recovery mode (did the whole thing with harddrives, took it apart and removed battery, etc). If I can get the same console EID and such, I could use those to put into downgrade.bin and flash it with that, would that work?
Could I use this method to unbrick a 3.41 cfw PS3? I messed up appldr and now it seems to be unable to boot into anything, even recovery mode (did the whole thing with harddrives, took it apart and removed battery, etc). If I can get the same console EID and such, I could use those to put into downgrade.bin and flash it with that, would that work?
you messed up console specific data no way you can unbrick
without a 100% dump with your console's data in it
you cannot use other console's data for it
actually ogz if you go on ps3devwiki youll find that there is some ps3s that came with 3.56 out of the factory that will downgrade to 3.55 now since his is a 3.60+ he probably can't if youd like to confirm just check the wiki for yourself....
I should start off my first post here by admitting that I am far more into the Xbox360 scene when it comes to modifications (Phat 120GB Elite 2007 HDMI Zephyr RGH'd with CoolRunner, Hitachi 79 4b00 with Lt+ 2.0b. Sorry, had to drop specs!) It seems as though it was really rather inexpensive compared to what appears to be required for PS3 modifications (assuming you have a somewhat newer system or an older system updated beyond FW 3.55).
With that said, I have a couple general boob, I mean noob, questions for anyone willing to answer and/or take some cheap shots at me...
Today I have acquired a slim model CECH-2501A (160GB) but haven't yet disassembled the console to determine if it has a JSD-001 or JTP-001 board or whether it is utilizing Samsung or Spansion flash chips. Right now the system is currently on 3.72 firmware (unfortunately), however, based on the SKU Models wiki I should be able to downgrade either of these boards using ProgSkeet since the "FW @ Release Date" for both boards is listed as 3.50, is that correct that I can downgrade to 3.55 from my 3.72?
If my above logic is correct and I can downgrade my system to 3.55 FW using ProgSkeet, my next question would be what difference is there between the two "solderless" adapters (aside from the additional ~$5.00)? My usual online mod shops have only two listings, one for "360-CLIP for NOR 56PIN FLASH" and another for "Solderless 360 Clip" and to be brutally honest, it has me a little confused as to which one should be used with my system.
I realize the "solderless" adapter is not required since it only lessens the amount of wires being soldered to the motherboard, but it would be nice to have "just in case". (Sorry, I know I keep quoting solderless. Simply put, it's because conventionally speaking the adapter is not exactly solderless, it's really just less-soldering. Even better yet; it should be called a "Simplified-Solder Adapter for ProgSkeet" =P)
With all that said, any wisdom would be appreciated. Hopefully I don't get "just read the posts" responses because I read all of them to get to the bottom of the page in order to click the "Reply" button. Oh, and sorry this post is probably going to look like a text wall over essentially two-three questions
I should start off my first post here by admitting that I am far more into the Xbox360 scene when it comes to modifications (Phat 120GB Elite 2007 HDMI Zephyr RGH'd with CoolRunner, Hitachi 79 4b00 with Lt+ 2.0b. Sorry, had to drop specs!) It seems as though it was really rather inexpensive compared to what appears to be required for PS3 modifications (assuming you have a somewhat newer system or an older system updated beyond FW 3.55).
With that said, I have a couple general boob, I mean noob, questions for anyone willing to answer and/or take some cheap shots at me...
Today I have acquired a slim model CECH-2501A (160GB) but haven't yet disassembled the console to determine if it has a JSD-001 or JTP-001 board or whether it is utilizing Samsung or Spansion flash chips. Right now the system is currently on 3.72 firmware (unfortunately), however, based on the SKU Models wiki I should be able to downgrade either of these boards using ProgSkeet since the "FW @ Release Date" for both boards is listed as 3.50, is that correct that I can downgrade to 3.55 from my 3.72?
If my above logic is correct and I can downgrade my system to 3.55 FW using ProgSkeet, my next question would be what difference is there between the two "solderless" adapters (aside from the additional ~$5.00)? My usual online mod shops have only two listings, one for "360-CLIP for NOR 56PIN FLASH" and another for "Solderless 360 Clip" and to be brutally honest, it has me a little confused as to which one should be used with my system.
I realize the "solderless" adapter is not required since it only lessens the amount of wires being soldered to the motherboard, but it would be nice to have "just in case". (Sorry, I know I keep quoting solderless. Simply put, it's because conventionally speaking the adapter is not exactly solderless, it's really just less-soldering. Even better yet; it should be called a "Simplified-Solder Adapter for ProgSkeet" =P)
With all that said, any wisdom would be appreciated. Hopefully I don't get "just read the posts" responses because I read all of them to get to the bottom of the page in order to click the "Reply" button. Oh, and sorry this post is probably going to look like a text wall over essentially two-three questions
you have a nor based system so 56 pin
BUT whatever you do don't buy the nor clip from 360clip
they fail to read write and if you don't know how to solve the shorts it may
damage the progskeet or console
team progskeet released their clips and they will be in the shops soon
so best option is wait for those clips if you really want it
BUT whatever you do don't buy the nor clip from 360clip
they fail to read write and if you don't know how to solve the shorts it may
damage the progskeet or console
team progskeet released their clips and they will be in the shops soon
so best option is wait for those clips if you really want it
Thank you very much for the response and clarifying things for me m8 =)
I probably don't absolutely need the clip, I've been using 15w and 30w irons for a ton of various SMD's, resistors, diodes, etc. for about eight years on nearly a daily basis so wire installs (even at 40+ wires that are very close together) come relatively easy for me but it would be nice to have the clip simply as a "safety net", so to speak.
I need to wait for another paycheck or two before I dive into purchasing the ProgSkeet v1.1 Crystal Blue board so perhaps the ProgSkeet brand clip will be in the shops by then, if not I will simply purchase it later when it does become available locally (US online shops). I just hope they're not nearly the same price as the main board itself like the currently available clips, buuut there's not much one can do about it if they are.
Again, your response is much appreciated jhax - thanks!
Thank you very much for the response and clarifying things for me m8 =)
I probably don't absolutely need the clip, I've been using 15w and 30w irons for a ton of various SMD's, resistors, diodes, etc. for about eight years on nearly a daily basis so wire installs (even at 40+ wires that are very close together) come relatively easy for me but it would be nice to have the clip simply as a "safety net", so to speak.
I need to wait for another paycheck or two before I dive into purchasing the ProgSkeet v1.1 Crystal Blue board so perhaps the ProgSkeet brand clip will be in the shops by then, if not I will simply purchase it later when it does become available locally (US online shops). I just hope they're not nearly the same price as the main board itself like the currently available clips, buuut there's not much one can do about it if they are.
Again, your response is much appreciated jhax - thanks!
tbh soldering is still the best way by far
like you say you know your way with a soldering iron it would most likely dump right the first time
be sure to let someone check the dump before you do any flashing DON'T use any tutorials that tell you to check for file size or md5 only
we already have enough doorstops as it is
use the thread in my signature to verify it or upload it and let it be verified
phrizz
If you have experience in soldering you can desolder the nand and read it in a TSOP adapter.
I think is less time consuming this way.
Anyway, if you are doing just your console....its not worth to buy a TSOP adapter.
Originally Posted by Thiefsie
Can I use the 360 clip to downgrade my fat CECHC PS3 down 3.55 with this method?
Any tutorials for that at all?
jhax78 already told ya that 360 clips cannot write the nor; the have shorts on them; they are projected form 360 nand not for ps3.
i suggest you look in a E3 flasher thread and not in a teensy /progskeet one
what model do you have phat or slim?
phat 50% chance you can use it and only if it's nor
slim's can use the E3 bricker
************* [ - Post Merged - ] *************
Originally Posted by Thiefsie
Can I use the 360 clip to downgrade my fat CECHC PS3 down 3.55 with this method?
tbh soldering is still the best way by far
like you say you know your way with a soldering iron it would most likely dump right the first time
be sure to let someone check the dump before you do any flashing DON'T use any tutorials that tell you to check for file size or md5 only
we already have enough doorstops as it is
use the thread in my signature to verify it or upload it and let it be verified
Thanks jhax, I'll definitely take your advice on how to verify the dump when the time comes. After doing a little more research, I think direct soldering is the best method so I won't be waiting around for US shops to start offering the ProgSkeet brand solderless clip. $65 +shipping for the ProgSkeet Crystal Blue v1.1 isn't terribly harsh on the wallet.
I must admit though, the "E3 Flasher 3K Limited Version PlayStation3 Downgrader & Jailbreak" full package looks rather intriguing. It comes with the E3Flasher, an ESATA Docking Station for the HardDrive(s) & a PS3 Slim Switch. No soldering at all on Slims with that, I just wonder how simple it really is compared to how cake-like the video tutorial makes it look. I would post a link but I'm not entirely aware of the rules regarding linking directly to mod-shop sites, so I'll reference it by saying it's the package I have in quotes above at modchipcentral which lists at $88.95 (+shipping).
If it's truly as simple as it is explained, and works as advertised, the additional $20-25 might actually be worth it. I recall reading the E3 bricking a lot of consoles, but can't remember if that was the old E3's or if it involved the specific package I am looking at. I know this thread is for ProgSkeet and Teensy, but do you or anyone else mind weighing in on the specific E3 package I mentioned and referenced?
Originally Posted by playonlcd
phrizz
If you have experience in soldering you can desolder the nand and read it in a TSOP adapter.
I think is less time consuming this way.
Anyway, if you are doing just your console....its not worth to buy a TSOP adapter.
playonlcd:
My system is a CECH-2501A so it has 16MB NOR, not NAND. Even if I was dealing with NAND, like you said the TSOP adapter wouldn't be worth it since I am only doing this to my own console. However, I like your thinking in regards to alternate methods for achieving ones goal! =)
I suppose I foolishly forgot to even ask...will this tutorial and all the files included within work on downgrading OFW 3.72 specifically? Or is this only for 3.70, and I need to track down different files..? *hoping this tut will also work for 3.7x firmware*
sidenote:
I realize this site probably doesn't run ps3devwiki but I have to say that I really really dislike the new layout of ps3devwiki - it feels amateur, more difficult to navigate and less intuitive than the old design. I had to restart my browser and when the sites I had open there re-opened, two of three didn't exist anymore and by time I found them they were downright ugly aesthetically. Oh well I guess..
Hi all, about to attempt this,done tons of reading but I'd like to know if its recommended to use Winskeet as opposed to Progskeet? Does it handle read/write errors better, & what the preferred settings for Winskeet are, mainly on "Common"(check boxs) & "NOR"(mainly the Options section) tabs.
multiupload appears to be history...so the pretty important files linked to multiupload are no longer working and a lot of us are now stuck in the middle of trying to downgrade. Please fix, please
edit-to-add:
I never really got an answer as to whether this same procedure will work with system software v3.72 ...I assume yes, but without the files linked above I'm a SOL at the moment.
---
After going through them all, turns out there is only three links still working:
2. Flow Rebuilder Tool -............*WORKS*
3. Downgrade.bin -..................dead multiupload link
4. Automated HEX File -............links to a post that links to a dead multiupload link
5. LV2Diag -.............................mirror seems okay, scroll down & the download is "Lv2Diag-patch-par-Jaicrab.zip"
6. Modded LV2Diag -.................*WORKS*
7. Kmeaw CFW PUP File 3.55 -...dead multiupload link, no mirror link available
Wish someone would put these critical files up on mediafire or somewhere else that still works.. :/
I just want to downgrade my CECH-2501A NTSC-U slim from 3.72 OFW to 3.55 CFW..
Someone pleeeaaase upload the four files I noted in my previous post that no longer work, multiupload is history. This excellent tutorial is completely obsolete without those files
Does anyone have an updated tutorial with working file links..?
For those of us wanting to use the latest Rogero CFW (V3, Kmeaw LV2_LV1 Patches & 4.11 spoof).. I wonder if we can't just:
1. create a dump of our NOR with ProgSkeet
2. use the downgrade V2 patches to create the downgrade.bin to flash back to the PS3
3. then use the LV2Diag in the OP and Rogero_CFW_V3_KmeawLV2_LV1Patches_4.11spoof_PrivacyPatch_NoBD.PUP (rather than the Kmeaw CFW PUP)
4. finish with the Modded_LV2Diag
Would that work??
I've read so many different tutorials now, all of which consist of completely different methods and tools needed..some say you need Injectus to program the ProgSkeet bitstream before you can even use the ProgSkeet to dump PS3 NOR (this specific tutorial mentions absolutely nothing about needing an Injectus or anything about programming a bitstream to the ProgSkeet) AND some say you need an AVRUSB (or similar) to enter Factory Service Mode (another device that is not mentioned in this tutorial, just says "now we're going to boot into service mode" but doesn't explain how or what is required to do so)
Any input would be appreciated but I'm not expecting much; this thread has gone dead now that the majority of the links in the OP are just as dead :/
-EDIT TO ADD-
Now I'm sort of wishing I would have just bought the damn E3 Flasher kit because all this trying to track down the ProgSkeet files crap and having to nearly beg for answers which never get a response is turning into a major headache. Sadly, I'm real tempted to return my ProgSkeet (fortunately I haven't opened it yet since I can't find a single ProgSkeet downgrade/jailbreak tutorial that actually includes everything you need) and then just order the E3 Flasher kit to downgrade and jailbreak.
Please do not use this guide anymore. It is V1 archaic and has some serious flaws later solved/prevented and does not protect the user from permabricking the console.
PS3devwiki links to splitted guide sections needed for downgrade:
Thanks a LOT for the links m8. So it looks as though on top of the ProgSkeet, you also need an Injectus AND a PSGrade (or PS3Key / similar) dongle? So much for ProgSkeet being a single device solution...that's disappointing news indeed.
I'm also looking at the "Patching and Downgrading" link and don't see my system model number listed, but the board model is. I have a Slim 160GB CECH-2501A that has a JTP-001 motherboard. The only date I can find is on the case and that says "Manufactured August 2010". However, the first link about the SKU models shows my system can be downgraded to 3.40, so that's a bit confusing.
Thanks a LOT for the links m8. So it looks as though on top of the ProgSkeet, you also need an Injectus AND a PSGrade (or PS3Key / similar) dongle? So much for ProgSkeet being a single device solution...that's disappointing news indeed.
ALL downgrader hardware flashers, non excluded (yes, E3 Flasher too) need PSgrade to install the downgrader firmware after patching/reflashing. Luckely there are lots of PSgrade capable devices, from which I had kept a list long time ago and later reposted on the talkpage here: http://www.ps3devwiki.com/wiki/Talk:...PSgrade_Dongle
Originally Posted by phrizz
I'm also looking at the "Patching and Downgrading" link and don't see my system model number listed, but the board model is. I have a Slim 160GB CECH-2501A that has a JTP-001 motherboard. The only date I can find is on the case and that says "Manufactured August 2010". However, the first link about the SKU models shows my system can be downgraded to 3.40, so that's a bit confusing.
Thanks m8, you are awesome! I just bought an Injectus and an AVRKey dongle to go with my ProgSkeet Crystal Blue. Based on the somewhat conflicting data specifically with the dates and SKU of my system, I'll probably end up having to use the minverchk PUP to find out exactly what she's capable of running.
My main goal for this PS3 is simply to install Rogero_CFW_V31_KmeawLV2_LV1Patches_4.11spoof_PrivacyPatch_NoBD.PUP as the CFW and then install the multiMAN_04.02.00 FULL pkg for data management/loading backups from an external hard drive. Essentially, I just want something simple, easy to use and functions properly. I am a strong believer of the KISS method - Keep It Simple Stupid.
The only thing about the Rogero CFW that sort of scares me a bit is the "NoBD" at the end of it; does that mean no BluRay disc movies?? That would be a major bummer..
For anyone that missed it: Flowrebuilder was updated to v.4.2.1.2, which fixed a small bug in the autopatcher routine when patching a unified descrambled NAND file with the NAND patches from ps3devwiki. Thumbs up for the author, who fixed the problem in notime after I reported the bug.
Originally Posted by judges
Well, actually Teensy can do both. So you might wanna call it the only "single-device" solution..
100% true! It is the only mentionable flasher capable of running PSgrade too (there is also PIC32MX but the flasher performance of that is miserable, although PSGradePIC works fine)
Originally Posted by phrizz
The only thing about the Rogero CFW that sort of scares me a bit is the "NoBD" at the end of it; does that mean no BluRay disc movies?? That would be a major bummer..
It just means the BD package has been stripped from the firmware PUP file so it won't error out when no BD drive is attached when installing the firmware in service mode after patching. BD-movies will work fine.
Technically simular to the noBD is the PS3 MFW Builder task I made for someone on request: noBT, for consoles that has no working bluetooth. it makes it possible to get beyond that nasty 0x8002F1F9 error you get when there is no BT/Wifi subboard detected during updates. Ofcourse wired controllers work fine. 3.00-Rogero v3.1 does not contain noBT, if you need it, you must make it yourself with PS3 MFW Builder.
For anyone that missed it: Flowrebuilder was updated to v.4.2.1.2, which fixed a small bug in the autopatcher routine when patching a unified descrambled NAND file with the NAND patches from ps3devwiki. Thumbs up for the author, who fixed the problem in notime after I reported the bug.
100% true! It is the only mentionable flasher capable of running PSgrade too (there is also PIC32MX but the flasher performance of that is miserable, although PSGradePIC works fine)
It just means the BD package has been stripped from the firmware PUP file so it won't error out when no BD drive is attached when installing the firmware in service mode after patching. BD-movies will work fine.
Technically simular to the noBD is the PS3 MFW Builder task I made for someone on request: noBT, for consoles that has no working bluetooth. it makes it possible to get beyond that nasty 0x8002F1F9 error you get when there is no BT/Wifi subboard detected during updates. Ofcourse wired controllers work fine. 3.00-Rogero v3.1 does not contain noBT, if you need it, you must make it yourself with PS3 MFW Builder.
You, my friend, are terrific! Thanks for the updated FlowRebuilder link (I had v4.2.1.1), the PS3 MFW Builder and answering my "NoBD" question I am pretty sure my BlueTooth and Wifi are fully functional, at least I know the Wifi is, so would I need the NoBT? Both of my controllers require their own USB dongles which allows me to run them either wired or wireless (I don't have an official PS3 controller, the kid who sold the system to me said he "lost it"..lol)
I wish someone would take your first post on this page (the one with all of the updated links to ps3devwiki and descriptions), start it as a new thread, merge your last couple of posts with your first, and have it stickied as the new "ProgSkeet/Teensy++ Noob Tutorial"! Then un-sticky this thread and let it get buried since like you said it's truly archaic.
100% true! It is the only mentionable flasher capable of running PSgrade too (there is also PIC32MX but the flasher performance of that is miserable, although PSGradePIC works fine)
You're right, forgot about that one. Actually the USBW32 development board looks like a fine device. 80MHz and 32bit sounds like a huge performance boost compared to Teensy's 8Mhz. If I need a new spare time project, I might get one of those and port NORway to run on the PIC. Should become significantly faster than the Teensy version...
After several more hours of reading and re-reading the ps3devwiki links euss was kind enough to post..there are a few places I'm a bit confused. For what it's worth, I have a slim CECH-2501A model that was manf. August 2010 with a JTP-001 motherboard and has Spansion NOR flash.
There are two methods, method two sounds easier because it doesn't talk about any switches (which quite frankly I just don't understand at all, actual On/Off switches, bridges, wtf kind of "switch"?).
1. Anyway, if I go with Method 2, it says "(with R7 open / R8 closed)", does this mean desolder the R8 [0] bridge resistor and leave the R7 connected? Or desolder R7 and leave R8 connected? Or go oblivious, disregard it and leave both connected as they came on my board? (Crystal Blue v1.1 ProgSkeet)
My next several questions involve the "Patching and Downgrading" section; 2. So I just dump my NOR after selecting the correct presets, (validate that it's a good dump of course) then use the Patcher tab and select my NOR dump bin then the progskeet_patch.txt with patch files (I intend to use "ProgSkeet Patcher's PS3 NOR Downgrade v2 patchfile" by AnGeL) and click Apply?
3. If Yes to 2, once that is done, I simply flash my newly patched OFW (which I guess is now technically a slightly MFW since it's been patched) using the "NOR -> Flash ..." option?
4. If Yes to 3, and the flashing goes fine, then would I move on to the Factory Service Mode part where I put my Rogero PUP (renamed accordingly) and the normal LV2Diag.self (located here) in my AVRKey to install / downgrade to Rogero v3.1? 4a. Will the system shut down after installation is complete or should I unplug the PS3 when activity appears to stop (HDD LED & USB LED)?
5. If Yes to 4(and/or 4a), I then remove those two files from my AVRKey and put the "get out of FSM" LV2Diag.self on it, plug it in & turn system back on then wait for the PS3 to shut itself off? 5a. Then I'm all done downgrading and am running Rogero v3.1 and can install multiMAN 04.02.00 FULL (20120228)?
Completely off my original line of questions, but I figured I might as well ask: 6. Is Rogero v3.1 simply a MFW of 3.55 that has Kmeaw LV2 patches, Dospiedras no-check along with a few other "safety-net" type patches?
edit-to-add: 7. The ProgSkeet does NOT stay in the system once everything is downgraded and flashed the way I want it, right? So I can, for instance, use this on my cousins PS3 when I finish with it?
Sorry for the text-wall, hopefully they're all easy yes/no answers. Thanks for all the help so far
1. Anyway, if I go with Method 2, it says "(with R7 open / R8 closed)", does this mean desolder the R8 [0] bridge resistor and leave the R7 connected? Or desolder R7 and leave R8 connected? Or go oblivious, disregard it and leave both connected as they came on my board? (Crystal Blue v1.1 ProgSkeet)
Open means nothing connecting on that pad, either:
* if there is a bridge/[0] ohm resistor on R7, remove it.
* if there is a switch on R7, set it to OFF position.
Closed means something connecting on that pad, either:
* a bridge/[0] ohm resistor on R7
* a blob of solder connecting both padsides of R7 pad
* if there is a switch on R7, set it to ON position.
Originally Posted by phrizz
My next several questions involve the "Patching and Downgrading" section; 2. So I just dump my NOR after selecting the correct presets, (validate that it's a good dump of course) then use the Patcher tab and select my NOR dump bin then the progskeet_patch.txt with patch files (I intend to use "ProgSkeet Patcher's PS3 NOR Downgrade v2 patchfile" by AnGeL) and click Apply?
Yes, that is true for all autopatching methods (e.g. Winskeet, Flowrebuilder etc) using progskeet_patch.txt file.
pic: Autopatching with Flowrebuilder
Originally Posted by phrizz
3. If Yes to 2, once that is done, I simply flash my newly patched OFW (which I guess is now technically a slightly MFW since it's been patched) using the "NOR -> Flash ..." option?
No it is not a firmware (which is on dozens of other places in the console too, e.g. harddrive), it is only patched flash (CoreOS + revoke to be exact) which is enough for the console to boot and use a dongle for service mode for the real reinstalling/downgrading of the full firmware.
Yes: after patching the local dump, you rewrite that to the flash (and redump to DIFF it) to make sure it is written 100% correct.
Originally Posted by phrizz
4. If Yes to 3, and the flashing goes fine, then would I move on to the Factory Service Mode part where I put my Rogero PUP (renamed accordingly) and the normal LV2Diag.self (located here) in my AVRKey to install / downgrade to Rogero v3.1? 4a. Will the system shut down after installation is complete or should I unplug the PS3 when activity appears to stop (HDD LED & USB LED)?
You forgot the part of using PSgrade JIG to trigger the console into factory service mode.
pic: Triggering service mode with PSgrade JIG
5. If Yes to 4(and/or 4a), I then remove those two files from my AVRKey and put the "get out of FSM" LV2Diag.self on it, plug it in & turn system back on then wait for the PS3 to shut itself off?
You only used dongle to trigger service mode, after this it is no longer used.
The get out lv2diag.self is stored on the USB Mass Storage Device (the same one used in the previous steps together with lv2diag.self FILE1 and PS3UPDAT.PUP), not a dongle.
pic: USB Mass Storage Device used for lv2diag.self + PS3UPDAT.PUP in phase 1, and lv2diag.self for getting out services mode in phase 2 after finished installation of firmware.
5a. Then I'm all done downgrading and am running Rogero v3.1 and can install multiMAN 04.02.00 FULL (20120228)?
In my opinion you are only partly finished, because you did not Rehash (making sure syscon hashes are downgraded too) to prevent bricking later on with unpatched firmwares. -> http://www.ps3devwiki.com/wiki/Downg...sher#Dehashing
Only when completely done, you can install whatever homebrew you want, Multiman (do not forget BDEmu), Rogero Manager etc.
Originally Posted by phrizz
Completely off my original line of questions, but I figured I might as well ask: 6. Is Rogero v3.1 simply a MFW of 3.55 that has Kmeaw LV2 patches, Dospiedras no-check along with a few other "safety-net" type patches?
First: a short simple answer will not do imo.
Second: Rogero proposed to make a modified firmware after he heard my rant (on IRC) about the overpatching done in the nocheck.pup and the many problems users experienced with it. Although I do not agree with his idea of choosing 'kmeaw/fluke/wutangrza like lv2' instead of "MFW Builder patched lv2", he kept the shared vision of KISS (keep it stupid/simple) for the lv1 patches. Users demanded latest spoof too, so each time when I updated the MFW Builder spooftask I informed him, and he released newer versions of his MFW. Until v3, when for some reason he and other users ran into BlueScreenofDeath, which was aftwards solved (v3.1) by patching vsh and using the index.dat from the tobespoofing firmware (simular to how rebug spoofer does it).
From MFW Builder perspective, 3.55-Rogero all have these patches:
* Change PUP build / version
* Patch LV1 (downgrader) checks
* Patch LV1 hypervisor: Allow mapping of any memory area (Needed for LV2 Poke)
* Patch LV2 kernel: Patch to add Peek&Poke system calls to LV2
* Patch package installer: Patch to allow installation of pseudo-retail packages + debug packages
* Patch Application launcher: Patch to allow running of unsigned applications
* Add new icons to the XMB Game category: Add Install Package Files + app_home + icons to the XMB Game Category
* Spoof to 4.11 (including vsh.self patch)
* No BD patch
Full indepth analysis: here (basis is same - later versions only patched errors in the first release and updated spoof)
"kmeaw" is just a bundle of patches from other people (fluke, graf, geo and others) which is very limited and wrongly patched too: http://www.ps3devwiki.com/wiki/Patches
Full indepth analysis: here
"Dospiedras no-check" is even worse, with some of the PsiColeo' proposed patches to alphatest for LV1 and includes a full set of OtherOS++ patches because the author forgot to deselect that task in MFW Builder. One of those unneeded patches, "SS" leads to Trophy errors each time you want to start a game.
Full indepth analysis: here
Conclusion:
* 3.55-Rogerov3.1 from these 3 above has the most proper/KISS set of patches needed for the job.
* Quick 'n Dirty prepatched is the minimal/KISS you need (which does not have the bad lv2 patching, but only proper ones - and also has no spoof or no noBD patches).
Originally Posted by phrizz
edit-to-add: 7. The ProgSkeet does NOT stay in the system once everything is downgraded and flashed the way I want it, right? So I can, for instance, use this on my cousins PS3 when I finish with it?
As long as you are not finished, it is recommended to keep the hardware flasher in the console and make backups of flash inbetween steps.
Once completely done (esp. when you also dehashed!), you can remove the hardware flasher.
Originally Posted by phrizz
Sorry for the text-wall, hopefully they're all easy yes/no answers. Thanks for all the help so far
No problem
I only hope my wall of reply doesnt scare you or others off
If anything, the matter is at least not "Noob proof" and simple. My advice to anyone considering doing themselves: read, read, read.
There is not one single path to follow, it is a myriad of stepping stones, most (if not all) documented on ps3devwiki (and when they are not documented there, someone should/could, as it is a public wiki, anyone can contribute - and oversighters like myself will try to check that the information shared/edits done there is proper/correct/without errors).
I was expecting short answers and a lack of true explanations but you when above and beyond by providing me with absolutely everything I was hoping for when I had my list of questions.
Your long response did just the opposite of scaring me off, I'm looking forward to Friday more than ever now so I can get to work on this thing!
Thank you sooo much for the original links and then answering literally every question I have asked in a professional & thorough manner. It's nice to know people like you do still exist in this world, cheers m8!
Yeah I was a little mixed up about the AVRKey and the USB Flash drive, I thought everything went on the dongle but the dongle is simply just to enter FSM and the files go on the USB drive. I got that part sorted (I flashed the appropriate PSGrade hex to my AVRKey with the FLIP software)
So it sounds as though I should probably go with the patch files (ROS 0/1 & RVK) that are on ps3devwiki as oppose to the patches I first intended to use by AnGeL (his had six files; patch1-patch6 whereas the ps3devwiki patches is just patch1 & rvk-040000)?
The dehashing part, I would prefer to do the reFSM method because quite frankly it just seems easier. Is this method basically: use the file1 LV2Diag.self and Rogero v3.1 PUP first, check the log file when complete, then install 3.55 OFW PUP over Rogero and compare the logs? If everything checks out and is working ok on the OFW, then I would go back to my Rogero PUP and finally use the get out of FSM LV2Diag.self? The dehashing section on ps3devwiki is a little vague, so your advice would be greatly appreciated
EDIT-TO-ADD:
I plan to start my project after work tomorrow (Friday), is there someplace that I can upload my NOR dump when I get that far that someone here with more "know-how" than myself who could verify? I am going to follow Jhax78's thread titled "Jhax78 nor check guide after dumping with progskeet/E3 or any flasher" but I would like to make absolute certain I have a good dump before I go any further.
In my opinion you are only partly finished, because you did not Rehash (making sure syscon hashes are downgraded too) to prevent bricking later on with unpatched firmwares. -> http://www.ps3devwiki.com/wiki/Downg...sher#Dehashing
Actually I never did that, because I've always flashed whatever was required.
I've never had any troubles, but just out of curiosity, after flashing a patched cos I've installed OFW 3.55 in fsm. But installation always ends with an error:
Code:
Update VSH Package done(0x8002f000)
Bul-ray Disc Player Revoke
read bdp revoke package (1775 bytes) elapsed = 5 msec
decrypt and verify bdp revoke package elapsed = 51 msec
write bdp revoke package elapsed = 1 msec
Bul-ray Disc Player Revoke done(0x8002f057)
update package elapsed time = 111461 msec
Updating or Verifying failure 0x8002f057
UpMng.UpdatePackage() failure
manufacturing updating FAILURE(0x8002f057)
Total Elapsed time = 130436 msec
Alrighty, BD error, doesn't happen with Rogero's MFW, but the curious thing is that my BD is working just fine and also, even with above error, OFW 3.55 is working just fine.
[...]
So it sounds as though I should probably go with the patch files (ROS 0/1 & RVK) that are on ps3devwiki as oppose to the patches I first intended to use by AnGeL (his had six files; patch1-patch6 whereas the ps3devwiki patches is just patch1 & rvk-040000)?
The 6 patches method was the old (sept.2011) method, which was refined later and became the 2 files/3 sections autopatching as now it preferred on wiki (less files/offsets so less errors to be made by users -> KISS:keep it simple/stupid).
Originally Posted by phrizz
The dehashing part, I would prefer to do the reFSM method because quite frankly it just seems easier. Is this method basically: use the file1 LV2Diag.self and Rogero v3.1 PUP first, check the log file when complete, then install 3.55 OFW PUP over Rogero and compare the logs? If everything checks out and is working ok on the OFW, then I would go back to my Rogero PUP and finally use the get out of FSM LV2Diag.self? The dehashing section on ps3devwiki is a little vague, so your advice would be greatly appreciated
Yes, after downgrade + FSM install of the prepatched PUP you just do that install again (and sometimes twice) but this time with an unpatched official firmware.
After official firmware works fine without bricking when leaving service mode (which means syscon hashes are reset), you can install any firmware you wish, just like your system was never above 3.56+
Originally Posted by phrizz
I plan to start my project after work tomorrow (Friday), is there someplace that I can upload my NOR dump when I get that far that someone here with more "know-how" than myself who could verify? I am going to follow Jhax78's thread titled "Jhax78 nor check guide after dumping with progskeet/E3 or any flasher" but I would like to make absolute certain I have a good dump before I go any further.
Me and others are on IRC EF.net #ps3downgrade channel providing that very service of second opinion / dump checking. just upload you dump to mediafire or simular and post link there with request for checking.
Originally Posted by judges
[...]
Actually I never did that, because I've always flashed whatever was required.
I've never had any troubles, but just out of curiosity, after flashing a patched cos I've installed OFW 3.55 in fsm. But installation always ends with an error: manufacturing updating FAILURE(0x8002f057)
Alrighty, BD error, doesn't happen with Rogero's MFW, but the curious thing is that my BD is working just fine and also, even with above error, OFW 3.55 is working just fine.
Any ideas what's causing this?
Correct, that is BD error and the reason it does not error on Rogero is because Rogero has BD removed in the PUP.
Three different solutions/workarounds:
It is seen sometimes when flasher is still hooked up to flashbus that the BD is not recognised. Disconnecting only controllines seems to solve that issue (or removing flasher in total).
You can use PS3 MFW Builder to patch an official firmware with only using the "broken blueray" task, thus keeping LV1.self unpatched for downgrader. This should get it beyond BD error and still rehash syscon.
The 6 patches method was the old (sept.2011) method, which was refined later and became the 2 files/3 sections autopatching as now it preferred on wiki (less files/offsets so less errors to be made by users -> KISS:keep it simple/stupid).
Yes, after downgrade + FSM install of the prepatched PUP you just do that install again (and sometimes twice) but this time with an unpatched official firmware.
After official firmware works fine without bricking when leaving service mode (which means syscon hashes are reset), you can install any firmware you wish, just like your system was never above 3.56+
Me and others are on IRC EF.net #ps3downgrade channel providing that very service of second opinion / dump checking. just upload you dump to mediafire or simular and post link there with request for checking.
euss:
Alright, I got a late start to my project. I ended up working some over-time yesterday for extra cash so I'm starting my project early this morning.
When I first took my system apart, I removed both metal shields covering the motherboard (so I could check the exact model of my Spansion memory for WinSkeet) and noticed the CPU, GPU and their heatsinks has some rather old looking thermal compound that didn't exactly cover all of each unit.
Should I use a lint-free cloth and some isopropyl alcohol to clean both units & their heatsinks and apply new compound, or screw it and leave the compound alone? If yes to applying new compound, I have two different kinds of Arctic Silver; Ceramique High-Density Thermal Compound (which is thicker and white in color, I usually use this on my PC GPU's and car amplifier FET's) and some good ol' fashion Arctic Silver 5 Polysynthetic Silver Thermal Compound (which is "silver" in color and is what I use on all of my PC CPU's).
On a side-note, I will indeed be uploading my flash dump probably to mediafire (I've always had the best luck with them lately). Should I post the link on here in this thread or should I just hop on efnet and request someone take a look there?
EDIT-TO-ADD:
By the way, I'm a huge fan of KISS (not the band, the theory!). In my book, the simpler the better especially if provides the functions I want which for this project are very basic; downgrade to a "hack-friendly" firmware, install Rogero 3.1 and use Multiman to manage the stuff on my external USB hard drive.
I have a 2TB external drive that was pre-formatted as NTFS, do I need to re-format it to FAT32 to make it PS3-compatible with the MFW & Multiman?NEVERMIND ABOUT THE FORMATTING QUESTION! I'm going to use Fat32Format GUI by Ridgecrop to format the 2TB drive and my 2GB flash drive.
[...]
Should I use a lint-free cloth and some isopropyl alcohol to clean both units & their heatsinks and apply new compound, or screw it and leave the compound alone? If yes to applying new compound, I have two different kinds of Arctic Silver; Ceramique High-Density Thermal Compound (which is thicker and white in color, I usually use this on my PC GPU's and car amplifier FET's) and some good ol' fashion Arctic Silver 5 Polysynthetic Silver Thermal Compound (which is "silver" in color and is what I use on all of my PC CPU's).
I always use non metallic based compound. E.g. Arctic MX-4 (or MX-2 if MX-4 is hard to get in your country).
Normal 'howto change thermal grease' logic applies, nothing special about PS3, so there are lots of guides on howto do it proper (and yes, cleaning and then reapplying is highly recommended).
Originally Posted by phrizz
On a side-note, I will indeed be uploading my flash dump probably to mediafire (I've always had the best luck with them lately). Should I post the link on here in this thread or should I just hop on efnet and request someone take a look there?
Both will work, on EF.net #ps3downgrade might be quicker, plus the people in charge (ops and voiced) are knowledgeable in the task to helpout.
Correct, that is BD error and the reason it does not error on Rogero is because Rogero has BD removed in the PUP.
It is seen sometimes when flasher is still hooked up to flashbus that the BD is not recognised. Disconnecting only controllines seems to solve that issue (or removing flasher in total).
I'm aware of the noBD patch, but that's the answer I was looking for. Didn't try to disconnect the control lines though, but experimented a little with Teensy's IO ports. Unfortunately I couldn't make it work yet, seems to be tough to make the flasher "invisible" to the console. At least I've found another bug during testing, so now Teensy can be left powered at all times.
I always use non metallic based compound. E.g. Arctic MX-4 (or MX-2 if MX-4 is hard to get in your country).
Normal 'howto change thermal grease' logic applies, nothing special about PS3, so there are lots of guides on howto do it proper (and yes, cleaning and then reapplying is highly recommended).
euss:
Figures, I don't have MX-2 or 4. I don't think I have even seen the Arctic MX line at any of my local R.Shacks, they seem to mostly only carry the "new" Arctic Silver 7 or whatever number it's up to. The closest BestBuy (if they even carry it) is a solid 40 minute drive one-way.
I wonder which of the two types I actually have on-hand would be best to use? I don't like short-cutting, but I would think something I already have could work adequately enough since I don't really abuse my PS3 in regards to how often & long it gets used.
The Ceramique looks closest to what was originally on both units (ie. it's white..hah) but it's high-density so it may not be too CPU-friendly. I think I might just treat it like it were any other computer CPU & GPU; Arctic Silver 5 for the CPU and Ceramique for the GPU...or just Silver 5 on both..or just Ceramique on both...ahh!
Anyway, as always thanks for your help and suggestions! I would without a doubt be embarrassingly lost without your posts here
This is a little off-topic, but I've been digging and digging through posts here because I recall seeing a picture of a ProgSkeet that the owner had soldered tiny male banana-style (I think) adapter plugs to each pad of his ProgSkeet for quick connection / disconnection of wires to the programmer. Anyone have a clue as to which picture I'm talking about or have a link for it??
I wanted to do something similar to add a "cool" factor to my 'Skeet but I simply cannot find anything small enough that can be soldered side-by-side. I tried 22AWG sized spades and pitch-forks but both of those are just too wide, no one carries anything higher than adapters meant for 22AWG wire around here :/ Oh well, the idea is probably more of a pipe-dream than a realistic plan but figured I would ask.
This is a little off-topic, but I've been digging and digging through posts here because I recall seeing a picture of a ProgSkeet that the owner had soldered tiny male banana-style (I think) adapter plugs to each pad of his ProgSkeet for quick connection / disconnection of wires to the programmer. Anyone have a clue as to which picture I'm talking about or have a link for it??
I wanted to do something similar to add a "cool" factor to my 'Skeet but I simply cannot find anything small enough that can be soldered side-by-side. I tried 22AWG sized spades and pitch-forks but both of those are just too wide, no one carries anything higher than adapters meant for 22AWG wire around here :/ Oh well, the idea is probably more of a pipe-dream than a realistic plan but figured I would ask.
Ahh..so he used pin headers so I misremembered when I thought they were banana-plugs. I loved the idea when I first saw it but couldn't find it again anywhere in my browser history, so thanks a lot for posting it
EDIT-TO-ADD:
I wonder where the hell I could buy the pin headers...R.Shack maybe? Probably have to try and find them online somewhere, just not sure where to start looking. Regardless, thanks again for finding the original thread and the specific picture I was seeking
UPDATE
Found some! Ordered a bunch of male pin headers and various sized female headers to go with them. $10.46 shipped for everything I wanted. Well worth it for the "cool"-factor in my opinion
I have everything hooked up (50 wires in all, looks like spaghetti! I connected all five grounds for the hell of it) minus one line, the NOR VCC 3.3v VIA on my ProgSkeet. I put [0] bridges on R9 and R11 to enable 3.3v.
Every ProgSkeet diagram for my board (JTP-001 & JSD-001) shows the NOR VCC point on the motherboard, but says that the VCC is "Not Used" with the ProgSkeet, then a little further down in this part of the ps3devwiki it talks about the flashing methods (method 2 is what I am going to use).
I traced the 3.3v VIA (aka NOR VCC based on the diagrams) on my ProgSkeet and it goes to the R7 resistor bridge; but since I am using method 2 to dump/flash, the R7 [0] bridge is removed so it doesn't seem like the 3.3v would go to anything...am I wrong?
So basically my question boils down to: do I need to solder the NOR VCC VIA on my ProgSkeet to the NOR VCC point on the motherboard even if the R7 [0] bridge is removed? Or does the USB connection to my laptop take care of the 3.3v required to power the ProgSkeet?
SIDE-NOTE:
I bought a 4g "syringe" of Arctic MX-4 for the CPU & GPU per your suggestion euss, even though I discovered prior to ordering it that the Ceramique high-density compound I already had was non-metallic / non-conductive. Only problem with the Ceramique is the ridiculous "break-in period", I simply won't have this PS3 long enough to properly set the compound so I went ahead and got the MX-4.
I also bought the two-part Arctic thermal compound remover; first impression wasn't great but I haven't had a chance to try it on a compound that wasn't about 10 years old, unrecognizable and practically solid. I have an ancient dinosaur Dell tower that I used as a guinea pig for both the remover then MX-4 but it had some strange pink compound that just absolutely refused to come off (even with 91% isopropyl!! had to soak & scrape it off), so I attribute the poor overall results of the Arctic compound remover to the compound I tried removing being archaic and essentially baked into the heatsink. The PS3 will be the real test for the two-part remover
When applying the Arctic MX-4 thermal compoud, do I just do the single dot in the middle of the GPU & CPU or does it need to be spread across the entire surface? I can't seem to find any applying instructions for this particular compound, unlike Arctic Silver that has all sorts of information regarding how to apply it depending on the CPU and cores..
I finally got around to finishing my ProgSkeet install and it seems as though it went perfectly the first attempt. I made six dumps and checked a couple in HxD and they appear to be good but I would greatly appreciate confirmation from someone a bit more experienced in checking such things. I zipped all six dumps and uploaded them to two sites.
NEVERMIND
Went to #ps3downgrade on efnet, getting help there now
I have a ps3 CECH GO2 nand, I want to get the solderless 360clip, since iI would rather solder on the progskeet on the clips PCB rather than the ps3 motherboard. should I be getting the 48 pin or can I use the 56 pin?
Not sure if anyone is viewing this thread but I'll give it a shot anyway.
Just need to know if anyone that has downgraded successfully(I did many months ago) has accidentally down the track installed standard cfw(eg KMEAW V3.55, unlike the NO-CHECK version during the downgrade), which results in YLOD sympton & ps3 turns off.
Is there any saviour at all(preferably without having to hook up the progskeet again) to reserect the PS3 from its brick? Hoping for a USB type solution but if progskeet is the only way, any guides on whats required?
Thanks for ant replies.
hi everyone, need help. when i try to check progskeet v1.2 for short it, it shows ''short found! please check G1, G2, G3'' any help is appreciable, help please.
hi everyone, need help. when i try to check progskeet v1.2 for short it, it shows ''short found! please check G1, G2, G3'' any help is appreciable, help please.
Hello modsters! I have a ? That isn't quite clear in my mind. I'm following the noob tut and have read beginning to end a couple times but before I attempt I am looking at the skus comparing to mine. My slim ps3 is CECH-2501A 160gb. I just bought it used with OFW 3.65. Here I found 4 possible matches! http://ps3devwiki.com/index.php?title=SKU_Models#2 which is not good unless it doesn't matter what the ps3 FW shipped with. 2 of the 4 are in question as the FW @ the release date are 3.56 and 3.61. If by chance I had one of these 2 models WILL THE HARDWARE DOWNGRADE PROCESS ALLOW THESE 2 MODELS TO DOWNGRADE BELOW THERE SHIPPING FW? 3.55? The other 2 models shipped with 3.40 so if it was one of those I know it will downgrade to 3.55. So will the hardware downgrade work if the shipped FW is higher than the target FW 3.55? Thank you all for the help and sorry for the over explanation. I just want to make sure!
Hello modsters! I have a ? That isn't quite clear in my mind. I'm following the noob tut and have read beginning to end a couple times but before I attempt I am looking at the skus comparing to mine. My slim ps3 is CECH-2501A 160gb. I just bought it used with OFW 3.65. Here I found 4 possible matches! http://ps3devwiki.com/index.php?title=SKU_Models#2 which is not good unless it doesn't matter what the ps3 FW shipped with. 2 of the 4 are in question as the FW @ the release date are 3.56 and 3.61. If by chance I had one of these 2 models WILL THE HARDWARE DOWNGRADE PROCESS ALLOW THESE 2 MODELS TO DOWNGRADE BELOW THERE SHIPPING FW? 3.55? The other 2 models shipped with 3.40 so if it was one of those I know it will downgrade to 3.55. So will the hardware downgrade work if the shipped FW is higher than the target FW 3.55? Thank you all for the help and sorry for the over explanation. I just want to make sure!
Ok. Im new here and i have PS3 fat 80GB version CECHL04. My ps3 is on version 3.72 (before that i have cfw 3.55 kmeaw) and i need to know can i downgrade my ps3 without any flashers and hardwares?
Ok. Im new here and i have PS3 fat 80GB version CECHL04. My ps3 is on version 3.72 (before that i have cfw 3.55 kmeaw) and i need to know can i downgrade my ps3 without any flashers and hardwares?
.
08-19-2011
05:33 PM
Not bad only one mistake, the picture of "Samsung Memory" is wrong.
You got RAM showing, not the flash, this is the right picture:
http://www.ps3crunch.net/forum/images/news/samsung.jpg
And to support Samsung you need the latest Progskeet flasher: 110819
All versions before that will not dump/flash Samsung memory.
With the latest Progskeet flasher, it has "ByteSwap" feature, that should remove the need for FlowRebuilder to swap the bytes around, but I can't personally confirm it, as I have not tested the new feature.
08-19-2011
05:40 PM
08-19-2011
05:40 PM
link is not woking for me.
08-19-2011
06:01 PM
this is very helpful. one question though, when the solderless comes out, is it clip onto NOR and done. instead of pin soldering?
08-19-2011
06:08 PM
08-19-2011
06:18 PM
Good stuff!! Any set time on when the solderless version will be released?
08-19-2011
06:25 PM
08-19-2011
06:46 PM
im not a noob but, noob in soldering so.. this isn't for me.
i can could do most step except step 3...
i would wait for solderless and this guide would be perfect!! noob proof :D
08-19-2011
06:56 PM
Yeahh just watch it be super expensive when it comes out though :\
08-19-2011
07:35 PM
Cool, some kind of special cable is need for soldering?
Thanx for the tutorial
:D
08-19-2011
07:46 PM
? would you lose your DLC if you downgraded? i am thinking about updating to 3.70 to get some DLC and then using this to get back onto CFW but want to make sure first..
08-19-2011
08:38 PM
I'm not willing to take my chances in soldering but this is incredible work these developers have done, major credit to them.
08-19-2011
08:45 PM
Ah. Would certainly do this but I take it a little just too complicated.
08-19-2011
08:51 PM
This is an awesome tutorial (especially for those with soldering skills and an old teensy laying around
08-19-2011
10:04 PM
So us phat NAND console owners on 3.70 are still screwed?
08-19-2011
10:07 PM
08-20-2011
12:03 AM
So what happens if this is attempted on a factory base 3.56 firmware PS3?
If its already on 3.56 or greater there is no way check first...
If the PS3 can not find a matching serial number for the HD in the registry it will want to format it.
Also the entire house of cards collapses for PSN\DLC because there is also no matching PSN account information in the Registry.
If you have a back up of Flash2 and the "exdata" folder from a previous jail break you might get lucky.
As for BluRay its always best to know the highest MKB version that has been played in the PS3 prior to Downgrading. (Flash3)
Be ready with the required BRD and DRL's to restore BluRay playback if needed.
Right now your best bet might be to use the PS3 backup utility.
It will restore ALL content, but it wont restore the ACT.DAT or .RIF files if the PSN account information associated with them cannot be found in the current Registry. (Flash2)
No way to get back on PSN, no Flash2 or "exdata" folder back up means no chance at DLC re-activation.
Hopefully someone comes up with a PS3 Backup image decrypter.
Its very possible to reconstruct the Registry but the current ACT.DAT and .RIF's are locked away in that archive until it can be decrypted and the files extracted.
08-20-2011
12:55 AM
is the RSOD already fixed if we downgrade? where can I find minimum firmware version checker?
08-20-2011
12:55 AM
08-20-2011
12:59 AM
08-20-2011
01:08 AM
If you use PrgoSkeet, don't forget to remove R8 and install switch on R7 because dump can't make
(faut que je rvise mon putain d'anglais...)
08-20-2011
01:52 AM
@Pirate
This tutorial is very nice, easy to understand. good job
Can i translate this to japanese? I'll put exact source URL link.
08-20-2011
02:00 AM
08-20-2011
02:31 AM
i think RSOD caused by hardware failure. that could be anything, like blueray, harddrive, corrupted firmware, or even the board itself.
sony always give a full replacement (if still under warranty) for rsod problem, don't know why
08-20-2011
02:35 AM
I mean what's causing RSOD when we downgrade using this tutorial?
08-20-2011
02:48 AM
is there a way to built his own progskeet chip by myself? cause its getting very expansive to ship it from us to germany
btw nice tut :D
08-20-2011
03:05 AM
08-21-2011
10:55 AM
I flash the file "downgrade.bin.REV" to that extent .REV?
It is possible to solve brick?
08-21-2011
11:09 AM
08-21-2011
11:28 AM
Love the tutorial. Started work on this when the originally translated one came out, confusing as hell. 1 thing missing from this is the Step 4 Part B, 1st step there should be to bytereverse before doing the auto hex editing...
Anyways, Got everything wired up, DIA-002 board, Teensy++ 2.0 using V.01 of NORway. Firmware dump went fine, dumped a few times and used totalcommander to compare, everything matched. Went through the steps on this tutorial using the autohex program, got my flash ready to write, and queue major issue. Won't write. Commands good, checked every single wired connection with multimeter, all good and proper... NORway goes through to the write screen, but NO progress at all. Just sits there like a dumb ass. Incase this was normal, I left it in that state all night. Still nothing in the morning.
Any ideas? I am all out, thinking I might have to wait until more people give this a shot and run into the same issue. Used the following diagrams for wiring up the board (attached)...
Any help is appreciated!
08-21-2011
11:44 AM
You should try the new version of NORway V.03
http://git.dashhacks.com/norway
08-21-2011
11:46 AM
08-21-2011
11:46 AM
08-21-2011
12:01 PM
08-21-2011
12:13 PM
08-21-2011
12:46 PM
By the way, your NOR chip is a Spansion right? Currently NORway (all versions) is only able to read/write Spansion and only read Samsung.
08-21-2011
01:03 PM
"CECHH/DIA-001 up to including CECHK/DIA-002 : 1x Spansion S29GL128N90TFIR2 (NOR 16MB) "
So yeah, looks like I am in a holding pattern until those voltage regulators arrive. Appreciate the help anyways!
08-21-2011
03:12 PM
************* [ - Post Merged - ] *************
Is this normal? Flash sector skipped?
08-22-2011
12:00 AM
I just can't update any existing v0.1 readmes out there, that's the reason for a v0.2.
08-22-2011
03:56 AM
hey wait thats very great i want to go back to psn because deleted my modnation racers dlc and stuff
i want to go back to psn to redownload and downgrade if i do that will i loose all the dlcs and stuff ? also is there a solderless method this is very complicated 
just a patch or something without opening the ps3 and buying teensy or something my country also doesnt have a teensy please man make a solderless thingy with just a simple patch
08-22-2011
02:16 PM
Thanks!
08-22-2011
02:57 PM
without digging through 5+ pages of good read right now while im at work.....
does this only work on slims? no phat love?
08-22-2011
04:41 PM
08-22-2011
06:57 PM
When Writing, it says writing byte 0000000 or however many zeros in there, and does not move. The lack of the voltage regulator will not make this happen?? You can check the top post of page 4 which shows the diagrams I used to wire all this up. Everything has been done to the letter except of course for the voltage regulator which I was under the impression was not necessary. Would appreciate more advice.
************* [ - Post Merged - ] *************
08-22-2011
07:51 PM
And if your on a token meter check its got plenty of money in, or better still use a UPS as well.
08-23-2011
02:29 AM
You might want to check the WP# line on your board. On mine it's always tied to Vcc, and the WP# line isn't controlled by the teensy.
08-23-2011
06:48 AM
Sorry but ow may god what are you lot doing without a regulated 5v psu, and it should be 3.5 not 5v. Use a 3-4 volts rechargeable battery, as that's the best cleanest regulated power to use for what you are doing. And if your using a multimeter to test with, then use resistance not CONTINUITY as you will kill it.
Keep the wires short and together to keep ingress and RFI down. And use stattic straps.
08-23-2011
07:31 AM
Jeez, I remeber back in the ps2 day when all you needed was a plastic hook and a CD.
08-23-2011
08:18 AM
Step1 - step 4 finished n i stuck in step 5 because when i want to flash it, the downgrade.bin.Rev not detected. can somebody tell me why when i click the flash button on progskeet flasher, the downgrade.bin.REV not showing, just showing downgrade.bin?
Sorry for my bad english. Tq.
08-23-2011
09:57 AM
Sorry i may sound a tool saying this as i am not playing with this myself.
Do you not just rename it from downgrade.bin.REV to downgrade.bin before you try flashing it, because you flash with .bin's not .REV's.
sorry if I'm wrong on this one.
08-23-2011
10:32 AM
n if i checked the "ByteSwap" on progskeet flasher, i don't need to use FlowRebuilder, right?
I just dump (checked ByteSwap), then use transplante,
n then flash (checked ByteSwap) it, right?
08-23-2011
01:59 PM
thaaaaaaaaaaaaaaaaaaaaaaaaaaaaanks
08-23-2011
04:32 PM
************* [ - Post Merged - ] *************
08-23-2011
06:53 PM
wrong thread....
08-24-2011
02:14 AM
There is this one thing I dont understand about the progskeet . Does it means I have to open the console and so some soldering works or it is something you install from a usb anyway please help me
08-24-2011
02:49 AM
08-24-2011
08:37 PM
I'm a big n00b as the title explains, so I was wondering how do you get to the motherboard, I know you can totally take the PS3 apart to access it but then I don't know what to do. Is there a way to view the motherboard while the PS3 is on. Sorry for being such a n00b
08-24-2011
09:42 PM
08-24-2011
10:05 PM
I know how to solder and use Progskeet, just accessing the motherboard is where I'm somewhat lost. I would be very grateful if you just pointed me in the right direction at the least.
08-24-2011
10:42 PM
http://www.ps3devwiki.com/index.php?...oard_Revisions
diagrams :
http://www.progskeet.com/downloads/diagrams_110805.rar
useful links :
http://www.ps3devwiki.com/index.php?...%28Hardware%29
hope that helps
08-24-2011
11:12 PM
08-24-2011
11:23 PM
but when i connected my teensy++ to my ps3, i set it upside down, so i can see the connection i made and the whole bottom of the board.
08-24-2011
11:41 PM
08-25-2011
12:05 AM
but since teensy++ haven't supported samsung's NOR yet, it depends on your type of flash memory. if you have samsung/macronix NOR, i think you should buy a progskeet which have more compatibility than Teensy++, for now.
i have 1 CECHL console with Spansion chip, and i used Teensy++ permanently on that. but i also have 1 CECH2xxx in RSOD (which i tried to recover) with samsung NOR flash, so i ordered Progskeet to use with it.
08-25-2011
08:21 AM
08-25-2011
08:27 AM
08-25-2011
11:08 AM
Is there anyway at the moment to downgrade a phat?
08-25-2011
11:54 AM
08-25-2011
01:42 PM
ogel2 sorry, but i have been searching since i saw your reply and i haven't still find it could post the link please ??
08-25-2011
07:24 PM
Update: Also tried re-dumping. Looks like about a 10th of my NOR has been wiped then after that the new dump matches my old dump... Looks like it partially erased before it started messing up. So NOR is still accessible, just partially wiped at the moment. I also checked out your V0.3, still indicates no WP# line necessary but the situation fits, unable to write because the write protect is kicking it's ass... Really hope you have a suggestion or two to throw my way.
08-25-2011
09:47 PM
08-25-2011
11:03 PM
Here is some info from Judges regarding WP#
08-26-2011
06:12 AM
how do i do this on a macbook pro??? and is there any other way??
08-26-2011
07:09 AM
Not having one to try my theory so forgive if I'm talking out my ass, but would it make sense not to have the write line open when you are simply just taking a dump, maybe by switch or not connecting wire till you are flashing, less chance of corrupting your backup. Sorry if foolish, just a thought.
08-26-2011
01:00 PM
Update: Also just noticed CE in Norway comes up as false in the status when dumping and writing... I am assuming that should be true for everything to work since it is a chip enable input?
08-27-2011
05:06 AM
http://www.ps3hax.net/showpost.php?p...&postcount=244
and here in general:
http://www.ps3hax.net/showthread.php?t=25408&page=13
08-28-2011
01:04 PM
Added 2 install/prep videos for ProgSkeet (Under STEP 3).
08-30-2011
09:26 AM
can I use IDE cable for pc? like this
http://www.google.com.ph/search?q=id...w=1024&bih=664
08-30-2011
09:42 AM
Yes but use the ata/66 80 strand ide ribbon. not the 40, although 40 is ok 80 better, try to keep the ribbon together rather than taking a wire off at a time
08-31-2011
11:13 PM
Thank you, very usefull
Im on step 1 yet. Im an ass soldering i gotta level my skills.
09-01-2011
06:37 AM
Hello everyone,
According to tutorial after the flashing PS3 will boot but I can't see anything like this!
I have a little problem (I'm thinking so). I installed very good and clear solders of the progskeet. My purpose downgrade the PS3 with 3.70 software.
I modiffied the the downgrade.bin file with my original dump.bin file. And then I'm trying to flash to PS3. Flashing is succesful but I have no happy ending
My original dump is safer when I flash back to PS3 original dump is working. If I flash the downgrade.bin.REV it makes brick PS3. I can't open the PS3. When try to open the machine it open then close in 1 or 2 seconds. The red light makes blinking.
The cables the longest is 10cm.
Cable size 30 AWG
What is my fault?
I need your helps.
Thanks a lots.
09-03-2011
08:57 PM
Just ordered my Progskeet today, will be attempting this method as soon as i receive the package, SUCKS ITS A 3-Day weekend!! Ill keep posted
09-06-2011
01:54 PM
what happen if i connect my teensy++ in my ps3 nand and make backup??? this will work??? will damage my ps3??? or what???
09-06-2011
09:02 PM
I think teensy is for NOR only, if you want to flash NAND you'll need progskeet or infectus
09-07-2011
12:00 AM
http://www.360-clip.com/ will this be ok to use with progskeet and teensy? It has fewer soldering points?
09-07-2011
01:56 PM
thank you ogel2 for your answer....yes unfortunatly teensy is only for NOR (at least for now)
but, if i only try get a dump???
and what diagram i should use for my SEM-001 MB??
thank you once more
update:
i already get my ps3 on 3.55 cfw (phat ps3)...i only want learn how to dump my ps3, because i want try to get (somehow) the keys 3.56+...
09-09-2011
05:05 AM
johnny janosik
sciagnij crack do heroes 5 kuznia przeznaczenia za darmo
kapitan bomba barbarian 4 rapid
serial nero 7 micro
office 2007 chomikuj
czysta krew SEZON 3 ODCINEK 7 TV
Mapy do Heroes IV torrent
nero 8 serial chomikuj.pl
przygody merlina lektor peb.pl
rs house 6 lektor
Nie zmieniajmy nic do pobrania za darmo
Grubasy napisy pl chomikuj
Download settlers narodziny kultur pelna wersja
Pobierz film avatar lektor pl
Darmowe filmy porno z siostrami zakonnymi
grey's anatomy sezon 2 odc 19
tekken(2010) film online
GTA IV key
telewizja discovery online
gry chomikuj
Ekipa z new jersey odc 7 sezon 2
Marcin daniec gwiazda rs
Avatar legenda aanga odcinki online
Gwiezdne wrota wszechswiat sezon 2 rapidshare
Gry hannah montana online jak sims
star wars chomikuj gra
rzym sezon 1 torrent
czterej pancerni muzyka chomikuj.pl
hanah montana forever pecetowiec
stargate atlantis peb.pl
Podkomisarz brenda johnson download
The Jet Set rapidshare
Minecraft za free
Chemia nowej ery 1 testy pdf dowland
Matylda film pobierz
football menager iPod download
brzydula betty sezon 3 lektor rmvb
zachomikuj seksualny rekord swiata
alfabet francuski pisany
teoria wielkiego podrywu lektor sezon 3 rapidshare
Wakfu do pobrania
Download pet party bot
Gry mlodych tytanow
Voir le film ma malakt aymanokom en direct
Piraci z karaibow na nieznanych wodach koncowka filmu
09-09-2011
05:31 AM
09-09-2011
11:52 PM
hello guys excuse my English I am Brazilian.
I've got a problem with the flash. I'm using progskeet.
I managed dump samsung.
when flash ended my ps3 does not appear but . black screen with LED lit. Could someone help me.
put file dump file to download
09-11-2011
01:32 AM
I have same problem. When I flash downgrade.bin.rev PS3 stay on black screen and led is green. When I flas back my dump ps3 power on back with 3.70 on it
Spansion flas mbo FAT VER-001
09-11-2011
03:44 PM
i will try arduino way
thanks ogel2
09-22-2011
03:02 AM
this tutorial is false for many ps3 models. that transplante step is wrong, you must use "dospiedra v2" tutorial. peace.
09-27-2011
02:43 PM
I AM STUCK HELPPPP! ok i have opened my ps3 soldered the wires to the correct places i have done the dump thing. now when you dump the new .bin on your ps3 you have to have a wire connected to the progskeet and the computer. my prob is do you put the ps3 back together then go through the downgrade process or do you leave the ps3 open (leaving the motherboard open to the outside) and the start up the ps3 and dump the new .bin . if you do put back together do you have to put a hole somewhere in the ps3 for the wire to go through to then be connected to your ps3????? answer would be deeply appreciated!!
10-23-2011
08:01 AM
how can i play batman arkhum city on 3.55 pls tell me . Also can i play Batman arkhum city on 3.60 or not ? And last tell me how can i downgrade 3.60 to 3.55 ?
11-09-2011
03:46 PM
I have a COK-002, which chip is chip 0/1?
http://www.ps3devwiki.com/index.php?...e-SAM_1765.jpg
11-09-2011
11:31 PM
Nevermind all is well.
11-25-2011
07:34 AM
This tutorial is outdated if you use winskeet (this whas my nor flash)
flowrebuilder or transplant is not needed anymore (flowrebuilder is still required to check the dump)
use the dospiedra v2 patches
open winskeet select the patch tab
at the input file line put your backup.bin
and at the patch file line choose the progskeet_patch.txt like this
now click apply and the program asks where to store the file and what name you would like for the patched backup.bin
flash the patched backup.bin reboot and put it in service mode with your dongle
now follow the steps to actualy downgrade to 3.55 with the usb stick
11-27-2011
01:45 AM
Does this method work for downgrading to 3.55 from a 3.73? I have tried a lot of .PUP files out there hoping I could make some progress.
And have came up empty handed left and right. So fed up with surveys, password locked files, and potential viruses. (thank god for a kickass antivirus! 
).So yeah, if someone could clue me in on how I could possibly do this downgrade via Progskeet, E3 flasher, etc... I will love you forever! A million thanks!!! 
11-27-2011
03:37 AM
downgrading with a .pup file isn't going to work on 3.73
if ur lucky you can use progskeet to downgrade
i would stay away from E3 flasher as it bricks lots of systems
12-05-2011
01:35 AM
Hey, I was wondering if I could do this of my stock firmware was 3.66. I'm reading on some tutorials that if the stock firmware was 3.56+ then I can't do it.. Thanks!
12-05-2011
03:16 AM
Anyway back to my question, i cant seem to find a decent NAND downgrading tutorial/video anywhere, any chance someone who has done this to a ps3 with NAND could make a tut please.
12-05-2011
12:11 PM
i just read that progskeet is now compatible to downgrade for 4.0 as well but i am guessing there might be some files that are specific to this firmware so was wondering is it possible to get these files and also i think its good time to update this post for the latest firmware as i trust only this website on the final say of the firmware hack for ps3 (DUH!)
i have slim running 4.0 any issues to downgrade by buying the progskeet?
12-08-2011
06:10 AM
Witch dongle is best to put the ps3 in factory mode? I was searching and most of then talk about jailbraiking from 3.41. E3 card reader or EcliPS3 are able to put the ps3 in factory mode?
12-09-2011
06:02 PM
12-10-2011
05:27 AM
If you have a FAT model with CECHH or above then you have a NOR chip, if its below that it will be NAND
If you have a ps3 slim it will have NOR but it has to be a certain model for it to be downgraded, if your slim is a CECH-20..A upto cech-251.B then these models can be downgraded, anything that was made after them cannot be downgraded
Progskeet can downgrade both NOR and NAND you just need the right 360 clip for your chip
E3 - Only NOR chips
12-12-2011
02:03 AM
I'm thinking of getting a progskeet and having my friend solder it in for me, my ps3 is a fat with nor I believe. CECHP01 Hes an expert at soldering and then from there I can do the software side....
I was at a party this weekend and someone updated it via a disc. I've also thought about using teensy++. The main thing I'm worried about, is keeping my files on my hdd intact. Do I have to format my hdd, or will I still be able to use it?
Also If I Use progskeet does it fit in the ps3 with it together?
12-14-2011
06:17 PM
Could I use this method to unbrick a 3.41 cfw PS3? I messed up appldr and now it seems to be unable to boot into anything, even recovery mode (did the whole thing with harddrives, took it apart and removed battery, etc). If I can get the same console EID and such, I could use those to put into downgrade.bin and flash it with that, would that work?
12-19-2011
03:52 AM
just got a ps3. it came with ofw 3.60 out of the box(currently on ofw 4.00), can i use progskeet to downgrade. will it work?
12-19-2011
05:58 PM
No you cant MAK84, factory firmware has to be 3.55 or below.
12-19-2011
06:12 PM
without a 100% dump with your console's data in it
you cannot use other console's data for it
12-19-2011
11:39 PM
actually ogz if you go on ps3devwiki youll find that there is some ps3s that came with 3.56 out of the factory that will downgrade to 3.55 now since his is a 3.60+ he probably can't if youd like to confirm just check the wiki for yourself....
01-14-2012
10:42 AM
my system has 3.61 and NAND in stead of NOR can i still flas?
01-29-2012
03:31 AM
I should start off my first post here by admitting that I am far more into the Xbox360 scene when it comes to modifications (Phat 120GB Elite 2007 HDMI Zephyr RGH'd with CoolRunner, Hitachi 79 4b00 with Lt+ 2.0b. Sorry, had to drop specs!) It seems as though it was really rather inexpensive compared to what appears to be required for PS3 modifications (assuming you have a somewhat newer system or an older system updated beyond FW 3.55).
With that said, I have a couple general boob, I mean noob, questions for anyone willing to answer and/or take some cheap shots at me...
Today I have acquired a slim model CECH-2501A (160GB) but haven't yet disassembled the console to determine if it has a JSD-001 or JTP-001 board or whether it is utilizing Samsung or Spansion flash chips. Right now the system is currently on 3.72 firmware (unfortunately), however, based on the SKU Models wiki I should be able to downgrade either of these boards using ProgSkeet since the "FW @ Release Date" for both boards is listed as 3.50, is that correct that I can downgrade to 3.55 from my 3.72?
If my above logic is correct and I can downgrade my system to 3.55 FW using ProgSkeet, my next question would be what difference is there between the two "solderless" adapters (aside from the additional ~$5.00)? My usual online mod shops have only two listings, one for "360-CLIP for NOR 56PIN FLASH" and another for "Solderless 360 Clip" and to be brutally honest, it has me a little confused as to which one should be used with my system.
I realize the "solderless" adapter is not required since it only lessens the amount of wires being soldered to the motherboard, but it would be nice to have "just in case". (Sorry, I know I keep quoting solderless. Simply put, it's because conventionally speaking the adapter is not exactly solderless, it's really just less-soldering. Even better yet; it should be called a "Simplified-Solder Adapter for ProgSkeet" =P)
With all that said, any wisdom would be appreciated. Hopefully I don't get "just read the posts" responses because I read all of them to get to the bottom of the page in order to click the "Reply" button. Oh, and sorry this post is probably going to look like a text wall over essentially two-three questions
01-29-2012
06:18 AM
BUT whatever you do don't buy the nor clip from 360clip
they fail to read write and if you don't know how to solve the shorts it may
damage the progskeet or console
team progskeet released their clips and they will be in the shops soon
so best option is wait for those clips if you really want it
01-29-2012
12:59 PM
Thank you very much for the response and clarifying things for me m8 =)
I probably don't absolutely need the clip, I've been using 15w and 30w irons for a ton of various SMD's, resistors, diodes, etc. for about eight years on nearly a daily basis so wire installs (even at 40+ wires that are very close together) come relatively easy for me but it would be nice to have the clip simply as a "safety net", so to speak.
I need to wait for another paycheck or two before I dive into purchasing the ProgSkeet v1.1 Crystal Blue board so perhaps the ProgSkeet brand clip will be in the shops by then, if not I will simply purchase it later when it does become available locally (US online shops). I just hope they're not nearly the same price as the main board itself like the currently available clips, buuut there's not much one can do about it if they are.
Again, your response is much appreciated jhax - thanks!
01-29-2012
04:00 PM
tbh soldering is still the best way by far
like you say you know your way with a soldering iron it would most likely dump right the first time
be sure to let someone check the dump before you do any flashing
DON'T use any tutorials that tell you to check for file size or md5 only
we already have enough doorstops as it is
use the thread in my signature to verify it or upload it and let it be verified
01-29-2012
11:30 PM
Can I use the 360 clip to downgrade my fat CECHC PS3 down 3.55 with this method?
Any tutorials for that at all?
01-30-2012
08:51 AM
phrizz
If you have experience in soldering you can desolder the nand and read it in a TSOP adapter.
I think is less time consuming this way.
Anyway, if you are doing just your console....its not worth to buy a TSOP adapter.
01-31-2012
03:58 AM
how can we do with E3 flasher
01-31-2012
04:06 AM
what model do you have phat or slim?
phat 50% chance you can use it and only if it's nor
slim's can use the E3 bricker
************* [ - Post Merged - ] *************
http://www.ps3devwiki.com/wiki/Progskeet
02-02-2012
07:43 PM
I must admit though, the "E3 Flasher 3K Limited Version PlayStation3 Downgrader & Jailbreak" full package looks rather intriguing. It comes with the E3Flasher, an ESATA Docking Station for the HardDrive(s) & a PS3 Slim Switch. No soldering at all on Slims with that, I just wonder how simple it really is compared to how cake-like the video tutorial makes it look. I would post a link but I'm not entirely aware of the rules regarding linking directly to mod-shop sites, so I'll reference it by saying it's the package I have in quotes above at modchipcentral which lists at $88.95 (+shipping).
If it's truly as simple as it is explained, and works as advertised, the additional $20-25 might actually be worth it. I recall reading the E3 bricking a lot of consoles, but can't remember if that was the old E3's or if it involved the specific package I am looking at. I know this thread is for ProgSkeet and Teensy, but do you or anyone else mind weighing in on the specific E3 package I mentioned and referenced?
My system is a CECH-2501A so it has 16MB NOR, not NAND. Even if I was dealing with NAND, like you said the TSOP adapter wouldn't be worth it since I am only doing this to my own console. However, I like your thinking in regards to alternate methods for achieving ones goal! =)
02-06-2012
08:46 PM
I suppose I foolishly forgot to even ask...will this tutorial and all the files included within work on downgrading OFW 3.72 specifically? Or is this only for 3.70, and I need to track down different files..? *hoping this tut will also work for 3.7x firmware*
sidenote:
I realize this site probably doesn't run ps3devwiki but I have to say that I really really dislike the new layout of ps3devwiki - it feels amateur, more difficult to navigate and less intuitive than the old design. I had to restart my browser and when the sites I had open there re-opened, two of three didn't exist anymore and by time I found them they were downright ugly aesthetically. Oh well I guess..
02-25-2012
10:40 AM
is it posible that someone fix links i need this files special downgrade.bin
Downgrade.bin [Download Here]
Automated HEX File [Download Here]
LV2Diag [Download Here or Mirror]
Modded LV2Diag [Download Here]
Kmeaw CFW PUP File (3.55) [Download HERE or Mirror
thanks
02-26-2012
04:31 PM
guys
http://www.multiupload.com
is not working please i need a new links for downloading the file
03-03-2012
01:52 AM
Hi all, about to attempt this,done tons of reading but I'd like to know if its recommended to use Winskeet as opposed to Progskeet? Does it handle read/write errors better, & what the preferred settings for Winskeet are, mainly on "Common"(check boxs) & "NOR"(mainly the Options section) tabs.
03-15-2012
05:14 PM
We need fixed links
multiupload appears to be history...so the pretty important files linked to multiupload are no longer working and a lot of us are now stuck in the middle of trying to downgrade. Please fix, please
edit-to-add:
I never really got an answer as to whether this same procedure will work with system software v3.72 ...I assume yes, but without the files linked above I'm a SOL at the moment.
---
After going through them all, turns out there is only three links still working:
2. Flow Rebuilder Tool -............*WORKS*
3. Downgrade.bin -..................dead multiupload link
4. Automated HEX File -............links to a post that links to a dead multiupload link
5. LV2Diag -.............................mirror seems okay, scroll down & the download is "Lv2Diag-patch-par-Jaicrab.zip"
6. Modded LV2Diag -.................*WORKS*
7. Kmeaw CFW PUP File 3.55 -...dead multiupload link, no mirror link available
Wish someone would put these critical files up on mediafire or somewhere else that still works.. :/
03-17-2012
12:13 PM
I just want to downgrade my CECH-2501A NTSC-U slim from 3.72 OFW to 3.55 CFW..
Someone pleeeaaase upload the four files I noted in my previous post that no longer work, multiupload is history. This excellent tutorial is completely obsolete without those files
Does anyone have an updated tutorial with working file links..?
03-21-2012
01:02 AM
Please someone update these links
************* [ - Post Merged - ] *************
yes that will be the way
03-21-2012
02:32 PM
For those of us wanting to use the latest Rogero CFW (V3, Kmeaw LV2_LV1 Patches & 4.11 spoof).. I wonder if we can't just:
1. create a dump of our NOR with ProgSkeet
2. use the downgrade V2 patches to create the downgrade.bin to flash back to the PS3
3. then use the LV2Diag in the OP and Rogero_CFW_V3_KmeawLV2_LV1Patches_4.11spoof_PrivacyPatch_NoBD.PUP (rather than the Kmeaw CFW PUP)
4. finish with the Modded_LV2Diag
Would that work??
I've read so many different tutorials now, all of which consist of completely different methods and tools needed..some say you need Injectus to program the ProgSkeet bitstream before you can even use the ProgSkeet to dump PS3 NOR (this specific tutorial mentions absolutely nothing about needing an Injectus or anything about programming a bitstream to the ProgSkeet) AND some say you need an AVRUSB (or similar) to enter Factory Service Mode (another device that is not mentioned in this tutorial, just says "now we're going to boot into service mode" but doesn't explain how or what is required to do so)
Any input would be appreciated but I'm not expecting much; this thread has gone dead now that the majority of the links in the OP are just as dead :/
-EDIT TO ADD-
Now I'm sort of wishing I would have just bought the damn E3 Flasher kit because all this trying to track down the ProgSkeet files crap and having to nearly beg for answers which never get a response is turning into a major headache. Sadly, I'm real tempted to return my ProgSkeet (fortunately I haven't opened it yet since I can't find a single ProgSkeet downgrade/jailbreak tutorial that actually includes everything you need) and then just order the E3 Flasher kit to downgrade and jailbreak.
03-21-2012
06:53 PM
Please do not use this guide anymore.
It is V1 archaic and has some serious flaws later solved/prevented and does not protect the user from permabricking the console.
PS3devwiki links to splitted guide sections needed for downgrade:
Infopage about downgradeability of consoles:
- http://www.ps3devwiki.com/wiki/SKU_Models
Hooking up flasher and making dumps:
- http://www.ps3devwiki.com/wiki/Hardware_flashing
- http://www.ps3devwiki.com/wiki/Progskeet
Validating:
- http://www.ps3devwiki.com/wiki/Validating_flash_dumps
Patching and Downgrading:
- http://www.ps3devwiki.com/wiki/Downg...rdware_flasher
Beyond downgrading: dual/multiboot:
- http://www.ps3devwiki.com/wiki/Dual_Firmware
Files links:
- PSGrade: http://www.ps3devwiki.com/files/PSGrade/
- Firmwares: http://www.ps3devwiki.com/files/firmware/
- Flash: http://www.ps3devwiki.com/files/flash/
- Servicemode lv2diags: http://www.ps3devwiki.com/files/lv2diag/
IRC channel (ef.net): #ps3downgrade
03-21-2012
08:03 PM
euss:
Thanks a LOT for the links m8. So it looks as though on top of the ProgSkeet, you also need an Injectus AND a PSGrade (or PS3Key / similar) dongle? So much for ProgSkeet being a single device solution...that's disappointing news indeed.
I'm also looking at the "Patching and Downgrading" link and don't see my system model number listed, but the board model is. I have a Slim 160GB CECH-2501A that has a JTP-001 motherboard. The only date I can find is on the case and that says "Manufactured August 2010". However, the first link about the SKU models shows my system can be downgraded to 3.40, so that's a bit confusing.
03-22-2012
03:14 PM
03-23-2012
01:33 AM
03-23-2012
02:35 PM
euss:
Thanks m8, you are awesome! I just bought an Injectus and an AVRKey dongle to go with my ProgSkeet Crystal Blue. Based on the somewhat conflicting data specifically with the dates and SKU of my system, I'll probably end up having to use the minverchk PUP to find out exactly what she's capable of running.
My main goal for this PS3 is simply to install Rogero_CFW_V31_KmeawLV2_LV1Patches_4.11spoof_PrivacyPatch_NoBD.PUP as the CFW and then install the multiMAN_04.02.00 FULL pkg for data management/loading backups from an external hard drive. Essentially, I just want something simple, easy to use and functions properly. I am a strong believer of the KISS method - Keep It Simple Stupid.
The only thing about the Rogero CFW that sort of scares me a bit is the "NoBD" at the end of it; does that mean no BluRay disc movies?? That would be a major bummer..
03-23-2012
09:17 PM
For anyone that missed it: Flowrebuilder was updated to v.4.2.1.2, which fixed a small bug in the autopatcher routine when patching a unified descrambled NAND file with the NAND patches from ps3devwiki. Thumbs up
for the author, who fixed the problem in notime after I reported the bug. 
Technically simular to the noBD is the PS3 MFW Builder task I made for someone on request: noBT, for consoles that has no working bluetooth. it makes it possible to get beyond that nasty 0x8002F1F9 error you get when there is no BT/Wifi subboard detected during updates. Ofcourse wired controllers work fine. 3.00-Rogero v3.1 does not contain noBT, if you need it, you must make it yourself with PS3 MFW Builder.
03-24-2012
08:43 AM
I wish someone would take your first post on this page (the one with all of the updated links to ps3devwiki and descriptions), start it as a new thread, merge your last couple of posts with your first, and have it stickied as the new "ProgSkeet/Teensy++ Noob Tutorial"! Then un-sticky this thread and let it get buried since like you said it's truly archaic.
Cheers m8! You've been a huge help!
03-24-2012
11:21 AM
03-25-2012
06:28 PM
After several more hours of reading and re-reading the ps3devwiki links euss was kind enough to post..there are a few places I'm a bit confused. For what it's worth, I have a slim CECH-2501A model that was manf. August 2010 with a JTP-001 motherboard and has Spansion NOR flash.
First, the "Hooking up flasher and making dumps" section, specifically the Hardware_Flashing (even more specifically: http://www.ps3devwiki.com/index.php?...ng#Progskeet_3)
There are two methods, method two sounds easier because it doesn't talk about any switches (which quite frankly I just don't understand at all, actual On/Off switches, bridges, wtf kind of "switch"?).
1. Anyway, if I go with Method 2, it says "(with R7 open / R8 closed)", does this mean desolder the R8 [0] bridge resistor and leave the R7 connected? Or desolder R7 and leave R8 connected? Or go oblivious, disregard it and leave both connected as they came on my board? (Crystal Blue v1.1 ProgSkeet)
My next several questions involve the "Patching and Downgrading" section;
2. So I just dump my NOR after selecting the correct presets, (validate that it's a good dump of course) then use the Patcher tab and select my NOR dump bin then the progskeet_patch.txt with patch files (I intend to use "ProgSkeet Patcher's PS3 NOR Downgrade v2 patchfile" by AnGeL) and click Apply?
3. If Yes to 2, once that is done, I simply flash my newly patched OFW (which I guess is now technically a slightly MFW since it's been patched) using the "NOR -> Flash ..." option?
4. If Yes to 3, and the flashing goes fine, then would I move on to the Factory Service Mode part where I put my Rogero PUP (renamed accordingly) and the normal LV2Diag.self (located here) in my AVRKey to install / downgrade to Rogero v3.1?
4a. Will the system shut down after installation is complete or should I unplug the PS3 when activity appears to stop (HDD LED & USB LED)?
5. If Yes to 4(and/or 4a), I then remove those two files from my AVRKey and put the "get out of FSM" LV2Diag.self on it, plug it in & turn system back on then wait for the PS3 to shut itself off?
5a. Then I'm all done downgrading and am running Rogero v3.1 and can install multiMAN 04.02.00 FULL (20120228)?
Completely off my original line of questions, but I figured I might as well ask:
6. Is Rogero v3.1 simply a MFW of 3.55 that has Kmeaw LV2 patches, Dospiedras no-check along with a few other "safety-net" type patches?
edit-to-add:
7. The ProgSkeet does NOT stay in the system once everything is downgraded and flashed the way I want it, right? So I can, for instance, use this on my cousins PS3 when I finish with it?
Sorry for the text-wall, hopefully they're all easy yes/no answers. Thanks for all the help so far
03-29-2012
06:22 AM
* if there is a bridge/[0] ohm resistor on R7, remove it.
* if there is a switch on R7, set it to OFF position.
Closed means something connecting on that pad, either:
* a bridge/[0] ohm resistor on R7
* a blob of solder connecting both padsides of R7 pad
* if there is a switch on R7, set it to ON position.
pic: Autopatching with Flowrebuilder
Yes: after patching the local dump, you rewrite that to the flash (and redump to DIFF it) to make sure it is written 100% correct.
pic: Triggering service mode with PSgrade JIG
Basically you are going to do this: http://www.ps3devwiki.com/wiki/Downg...PSgrade_Dongle blindly (without video output, only LED activity and shutdown when complete as hint)
The get out lv2diag.self is stored on the USB Mass Storage Device (the same one used in the previous steps together with lv2diag.self FILE1 and PS3UPDAT.PUP), not a dongle.
pic: USB Mass Storage Device used for lv2diag.self + PS3UPDAT.PUP in phase 1, and lv2diag.self for getting out services mode in phase 2 after finished installation of firmware.
* http://www.ps3devwiki.com/files/lv2d...%20downgrader/
* http://www.ps3devwiki.com/files/lv2d...%20downgrader/
Only when completely done, you can install whatever homebrew you want, Multiman (do not forget BDEmu), Rogero Manager etc.
Second: Rogero proposed to make a modified firmware after he heard my rant (on IRC) about the overpatching done in the nocheck.pup and the many problems users experienced with it. Although I do not agree with his idea of choosing 'kmeaw/fluke/wutangrza like lv2' instead of "MFW Builder patched lv2", he kept the shared vision of KISS (keep it stupid/simple) for the lv1 patches. Users demanded latest spoof too, so each time when I updated the MFW Builder spooftask I informed him, and he released newer versions of his MFW. Until v3, when for some reason he and other users ran into BlueScreenofDeath, which was aftwards solved (v3.1) by patching vsh and using the index.dat from the tobespoofing firmware (simular to how rebug spoofer does it).
From MFW Builder perspective, 3.55-Rogero all have these patches:
* Change PUP build / version
* Patch LV1 (downgrader) checks
* Patch LV1 hypervisor: Allow mapping of any memory area (Needed for LV2 Poke)
* Patch LV2 kernel: Patch to add Peek&Poke system calls to LV2
* Patch package installer: Patch to allow installation of pseudo-retail packages + debug packages
* Patch Application launcher: Patch to allow running of unsigned applications
* Add new icons to the XMB Game category: Add Install Package Files + app_home + icons to the XMB Game Category
* Spoof to 4.11 (including vsh.self patch)
* No BD patch
Full indepth analysis: here (basis is same - later versions only patched errors in the first release and updated spoof)
"kmeaw" is just a bundle of patches from other people (fluke, graf, geo and others) which is very limited and wrongly patched too: http://www.ps3devwiki.com/wiki/Patches
Full indepth analysis: here
"Dospiedras no-check" is even worse, with some of the PsiColeo' proposed patches to alphatest for LV1 and includes a full set of OtherOS++ patches because the author forgot to deselect that task in MFW Builder. One of those unneeded patches, "SS" leads to Trophy errors each time you want to start a game.
Full indepth analysis: here
Conclusion:
* 3.55-Rogerov3.1 from these 3 above has the most proper/KISS set of patches needed for the job.
* Quick 'n Dirty prepatched is the minimal/KISS you need (which does not have the bad lv2 patching, but only proper ones - and also has no spoof or no noBD patches).
Once completely done (esp. when you also dehashed!), you can remove the hardware flasher.
I only hope my wall of reply doesnt scare you or others off
If anything, the matter is at least not "Noob proof" and simple. My advice to anyone considering doing themselves: read, read, read.
There is not one single path to follow, it is a myriad of stepping stones, most (if not all) documented on ps3devwiki (and when they are not documented there, someone should/could, as it is a public wiki, anyone can contribute - and oversighters like myself will try to check that the information shared/edits done there is proper/correct/without errors).
03-29-2012
12:01 PM
euss:
You are AWESOME!
I was expecting short answers and a lack of true explanations but you when above and beyond by providing me with absolutely everything I was hoping for when I had my list of questions.
Your long response did just the opposite of scaring me off, I'm looking forward to Friday more than ever now so I can get to work on this thing!
Thank you sooo much for the original links and then answering literally every question I have asked in a professional & thorough manner. It's nice to know people like you do still exist in this world, cheers m8!
03-29-2012
04:25 PM
euss:
Yeah I was a little mixed up about the AVRKey and the USB Flash drive, I thought everything went on the dongle but the dongle is simply just to enter FSM and the files go on the USB drive. I got that part sorted (I flashed the appropriate PSGrade hex to my AVRKey with the FLIP software)
So it sounds as though I should probably go with the patch files (ROS 0/1 & RVK) that are on ps3devwiki as oppose to the patches I first intended to use by AnGeL (his had six files; patch1-patch6 whereas the ps3devwiki patches is just patch1 & rvk-040000)?
The dehashing part, I would prefer to do the reFSM method because quite frankly it just seems easier. Is this method basically: use the file1 LV2Diag.self and Rogero v3.1 PUP first, check the log file when complete, then install 3.55 OFW PUP over Rogero and compare the logs? If everything checks out and is working ok on the OFW, then I would go back to my Rogero PUP and finally use the get out of FSM LV2Diag.self? The dehashing section on ps3devwiki is a little vague, so your advice would be greatly appreciated
EDIT-TO-ADD:
I plan to start my project after work tomorrow (Friday), is there someplace that I can upload my NOR dump when I get that far that someone here with more "know-how" than myself who could verify? I am going to follow Jhax78's thread titled "Jhax78 nor check guide after dumping with progskeet/E3 or any flasher" but I would like to make absolute certain I have a good dump before I go any further.
03-30-2012
04:12 AM
I've never had any troubles, but just out of curiosity, after flashing a patched cos I've installed OFW 3.55 in fsm. But installation always ends with an error:
Any ideas what's causing this?
03-30-2012
12:12 PM
After official firmware works fine without bricking when leaving service mode (which means syscon hashes are reset), you can install any firmware you wish, just like your system was never above 3.56+
Three different solutions/workarounds:
03-31-2012
08:29 AM
euss:
Alright, I got a late start to my project. I ended up working some over-time yesterday for extra cash so I'm starting my project early this morning.
When I first took my system apart, I removed both metal shields covering the motherboard (so I could check the exact model of my Spansion memory for WinSkeet) and noticed the CPU, GPU and their heatsinks has some rather old looking thermal compound that didn't exactly cover all of each unit.
Should I use a lint-free cloth and some isopropyl alcohol to clean both units & their heatsinks and apply new compound, or screw it and leave the compound alone? If yes to applying new compound, I have two different kinds of Arctic Silver; Ceramique High-Density Thermal Compound (which is thicker and white in color, I usually use this on my PC GPU's and car amplifier FET's) and some good ol' fashion Arctic Silver 5 Polysynthetic Silver Thermal Compound (which is "silver" in color and is what I use on all of my PC CPU's).
On a side-note, I will indeed be uploading my flash dump probably to mediafire (I've always had the best luck with them lately). Should I post the link on here in this thread or should I just hop on efnet and request someone take a look there?
EDIT-TO-ADD:
By the way, I'm a huge fan of KISS (not the band, the theory!). In my book, the simpler the better especially if provides the functions I want which for this project are very basic; downgrade to a "hack-friendly" firmware, install Rogero 3.1 and use Multiman to manage the stuff on my external USB hard drive.
I have a 2TB external drive that was pre-formatted as NTFS, do I need to re-format it to FAT32 to make it PS3-compatible with the MFW & Multiman? NEVERMIND ABOUT THE FORMATTING QUESTION! I'm going to use Fat32Format GUI by Ridgecrop to format the 2TB drive and my 2GB flash drive.
04-02-2012
03:34 AM
Normal 'howto change thermal grease' logic applies, nothing special about PS3, so there are lots of guides on howto do it proper (and yes, cleaning and then reapplying is highly recommended).
04-02-2012
12:06 PM
Thanks for that..
04-02-2012
04:46 PM
euss:
Figures, I don't have MX-2 or 4. I don't think I have even seen the Arctic MX line at any of my local R.Shacks, they seem to mostly only carry the "new" Arctic Silver 7 or whatever number it's up to. The closest BestBuy (if they even carry it) is a solid 40 minute drive one-way.
I wonder which of the two types I actually have on-hand would be best to use? I don't like short-cutting, but I would think something I already have could work adequately enough since I don't really abuse my PS3 in regards to how often & long it gets used.
The Ceramique looks closest to what was originally on both units (ie. it's white..hah) but it's high-density so it may not be too CPU-friendly. I think I might just treat it like it were any other computer CPU & GPU; Arctic Silver 5 for the CPU and Ceramique for the GPU...or just Silver 5 on both..or just Ceramique on both...ahh!
Anyway, as always thanks for your help and suggestions! I would without a doubt be embarrassingly lost without your posts here
04-02-2012
08:05 PM
This is a little off-topic, but I've been digging and digging through posts here because I recall seeing a picture of a ProgSkeet that the owner had soldered tiny male banana-style (I think) adapter plugs to each pad of his ProgSkeet for quick connection / disconnection of wires to the programmer. Anyone have a clue as to which picture I'm talking about or have a link for it??
I wanted to do something similar to add a "cool" factor to my 'Skeet but I simply cannot find anything small enough that can be soldered side-by-side. I tried 22AWG sized spades and pitch-forks but both of those are just too wide, no one carries anything higher than adapters meant for 22AWG wire around here :/ Oh well, the idea is probably more of a pipe-dream than a realistic plan but figured I would ask.
04-02-2012
08:30 PM
http://imageshack.us/photo/my-images/802/progsd.jpg/
http://www.progskeet.com/forum/viewtopic.php?f=3&t=3749
04-03-2012
11:38 AM
Ahh..so he used pin headers so I misremembered when I thought they were banana-plugs. I loved the idea when I first saw it but couldn't find it again anywhere in my browser history, so thanks a lot for posting it
EDIT-TO-ADD:
I wonder where the hell I could buy the pin headers...R.Shack maybe? Probably have to try and find them online somewhere, just not sure where to start looking. Regardless, thanks again for finding the original thread and the specific picture I was seeking
04-03-2012
07:34 PM
UPDATE
Found some! Ordered a bunch of male pin headers and various sized female headers to go with them. $10.46 shipped for everything I wanted. Well worth it for the "cool"-factor in my opinion
04-07-2012
09:54 AM
euss (or anyone else who knows for sure):
I have everything hooked up (50 wires in all, looks like spaghetti! I connected all five grounds for the hell of it) minus one line, the NOR VCC 3.3v VIA on my ProgSkeet. I put [0] bridges on R9 and R11 to enable 3.3v.
Every ProgSkeet diagram for my board (JTP-001 & JSD-001) shows the NOR VCC point on the motherboard, but says that the VCC is "Not Used" with the ProgSkeet, then a little further down in this part of the ps3devwiki it talks about the flashing methods (method 2 is what I am going to use).
I traced the 3.3v VIA (aka NOR VCC based on the diagrams) on my ProgSkeet and it goes to the R7 resistor bridge; but since I am using method 2 to dump/flash, the R7 [0] bridge is removed so it doesn't seem like the 3.3v would go to anything...am I wrong?
So basically my question boils down to: do I need to solder the NOR VCC VIA on my ProgSkeet to the NOR VCC point on the motherboard even if the R7 [0] bridge is removed? Or does the USB connection to my laptop take care of the 3.3v required to power the ProgSkeet?
SIDE-NOTE:
I bought a 4g "syringe" of Arctic MX-4 for the CPU & GPU per your suggestion euss, even though I discovered prior to ordering it that the Ceramique high-density compound I already had was non-metallic / non-conductive. Only problem with the Ceramique is the ridiculous "break-in period", I simply won't have this PS3 long enough to properly set the compound so I went ahead and got the MX-4.
I also bought the two-part Arctic thermal compound remover; first impression wasn't great but I haven't had a chance to try it on a compound that wasn't about 10 years old, unrecognizable and practically solid. I have an ancient dinosaur Dell tower that I used as a guinea pig for both the remover then MX-4 but it had some strange pink compound that just absolutely refused to come off (even with 91% isopropyl!! had to soak & scrape it off), so I attribute the poor overall results of the Arctic compound remover to the compound I tried removing being archaic and essentially baked into the heatsink. The PS3 will be the real test for the two-part remover
04-08-2012
12:23 PM
04-14-2012
09:30 AM
When applying the Arctic MX-4 thermal compoud, do I just do the single dot in the middle of the GPU & CPU or does it need to be spread across the entire surface? I can't seem to find any applying instructions for this particular compound, unlike Arctic Silver that has all sorts of information regarding how to apply it depending on the CPU and cores..
04-14-2012
01:19 PM
OK nevermind my MX-4 question.
I finally got around to finishing my ProgSkeet install and it seems as though it went perfectly the first attempt. I made six dumps and checked a couple in HxD and they appear to be good but I would greatly appreciate confirmation from someone a bit more experienced in checking such things. I zipped all six dumps and uploaded them to two sites.
NEVERMIND
Went to #ps3downgrade on efnet, getting help there now
04-15-2012
06:32 AM
I have a ps3 CECH GO2 nand, I want to get the solderless 360clip, since iI would rather solder on the progskeet on the clips PCB rather than the ps3 motherboard. should I be getting the 48 pin or can I use the 56 pin?
04-17-2012
04:53 PM
n64hk:
The 56pin clip is for NOR, for NAND solderless it's the smaller clip/adapter
04-19-2012
05:36 AM
What is the basic version Progskeet?
I do not have Injectus for Program.
My ProgSkeet Blue model is 1.1
I've used the methods of soldering. for NOR ps3 slim
But it is freeze on 0.0.
09-15-2012
03:31 AM
Not sure if anyone is viewing this thread but I'll give it a shot anyway.
Just need to know if anyone that has downgraded successfully(I did many months ago) has accidentally down the track installed standard cfw(eg KMEAW V3.55, unlike the NO-CHECK version during the downgrade), which results in YLOD sympton & ps3 turns off.
Is there any saviour at all(preferably without having to hook up the progskeet again) to reserect the PS3 from its brick? Hoping for a USB type solution but if progskeet is the only way, any guides on whats required?
Thanks for ant replies.
10-16-2012
11:43 PM
Howdie experts, any can clarify if the nand based board after downgrading, it will lose bd playback? Anyone can verify? Thanks mates.
11-05-2012
12:11 AM
progskeet 1.0 converted to 1.2 lite
Winskeet111205
Windows 7 x64
PS3 cech-2008b OFW 4.20
Nor samsung K8Q2815UQB-PI4B
nor read without error, but open with hxd see this
[spoiler]
.....................ая....Ю.ѕп..............x.................................................................................................................................................................................................................................................................................................................................................................................................................................................................................IFI.............яяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяя.............пь...............и.asecure_loader........................м.........eEID..................................м.........cISD..................................ф.........cCSD..................................ь.........trvk_prg0.............................ь.........trvk_prg1.............................ь.........trvk_pkg0.............................ь.........trvk_pkg1.............................ь......p..ros0.................................{ь......p..ros1.................................ль.........cvtrm................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................ая....Ю.ѕп..............x.................................................................................................................................................................................................................................................................................................................................................................................................................................................................................IFI.............яяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяяя.............пь...............и.asecure_loader........................м.........eEID..................................м.........cISD..................................ф.........cCSD..................................ь.........trvk_prg0.............................ь.........trvk_prg1.............................ь.........trvk_pkg0.............................ь.........trvk_pkg1.............................ь......p..ros0.................................{ь......p..ros1.................................ль.........cvtrm...........................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................хШ`ЪЃ"Єdt.пeлЂe$RЁ9.Љ|тАп.:so.|Ж..'тШ0зФJ...HzАЁУ.ѕ._Ъ.jбmЌ.sr@эж.Й2л*Жђmдъв}.зЄд-ЏҐ1g'.Оs.ёЋВїПЫц.kтЌђ+oќия..цfull dump from progskeet
correct dump from memdump
what wrong?
11-27-2012
11:10 AM
hi everyone, need help. when i try to check progskeet v1.2 for short it, it shows ''short found! please check G1, G2, G3'' any help is appreciable, help please.
11-27-2012
11:20 AM
11-27-2012
02:57 PM
progskeet v1.2 bitstream 121018_0031
12-19-2012
02:53 PM
Hello modsters! I have a ? That isn't quite clear in my mind. I'm following the noob tut and have read beginning to end a couple times but before I attempt I am looking at the skus comparing to mine. My slim ps3 is CECH-2501A 160gb. I just bought it used with OFW 3.65. Here I found 4 possible matches! http://ps3devwiki.com/index.php?title=SKU_Models#2 which is not good unless it doesn't matter what the ps3 FW shipped with. 2 of the 4 are in question as the FW @ the release date are 3.56 and 3.61. If by chance I had one of these 2 models WILL THE HARDWARE DOWNGRADE PROCESS ALLOW THESE 2 MODELS TO DOWNGRADE BELOW THERE SHIPPING FW? 3.55? The other 2 models shipped with 3.40 so if it was one of those I know it will downgrade to 3.55. So will the hardware downgrade work if the shipped FW is higher than the target FW 3.55? Thank you all for the help and sorry for the over explanation. I just want to make sure!
12-20-2012
12:42 AM
03-19-2013
07:15 AM
Ok. Im new here and i have PS3 fat 80GB version CECHL04. My ps3 is on version 3.72 (before that i have cfw 3.55 kmeaw) and i need to know can i downgrade my ps3 without any flashers and hardwares?
03-19-2013
07:57 AM
05-12-2013
08:53 AM
anyone knows where to get the diagram of progsheet and infectus
thanks
05-12-2013
10:43 AM