![]() |
cok-001 tristate pic
I need a pic of the cok-001 motherboard testpoints. The tristate to be exact.
I know your going to say ps3devwiki, duh. But the site is not loading and must be down for some reason. I have been googling for it. I know I had found a site before with all the pinout pics. But I can not find it now. I was hoping someone might have a pic with the points mapped handy they could post for me. As I am a little impatient and have this ps3 taken apart right now. Maybe ps3devwiki will be back up soon, but if anyone could help me before that I would be much appreciative. Thanks. |
if you use PROGSKEET + nand 360 clip do not need to use the Tristate
|
Quote:
I am using Progskeet and after I flashed the patched .bin files to each nand, I now get ylod. I know soldering a wire from tristate to ground will allow me to figure out if it is a bad flash or rsx problem. But if there is no tristate, how do I test? This is the first nand model I have tried to downgrade. After severely modifying the 360 clip, I was able to get plenty of good backups. I was getting ylod when putting the console back together sometimes, but after messing with the heat sink and getting it put back together, I was able to boot the ps3 fine. But now after I flashed the nands, I keep getting ylod. On ps3devwiki it says to ground tristate and if you get green light no video, its a bad flash. Was hoping to test somehow to find this out. |
Simplified 256Mb NAND PS3 3.6x Downgrade Guide:
Software needed: Hardware flasher (Progskeet, Infectus) Flow Rebuilder v4.1.3.2 Hexeditor (HxD is FREE) First make sure you have the PROGSKEET drivers installed. 1. When making your first dump, make 100% sure you have a good dump, make several to be safe and compare them with HxD. If you don’t have a good backup and erase your NANDs then you’re pretty much screwed... THIS IS IMPORTANT! 2. Once you have your NAND flash dumps, use FlowRebuilder v.4.1.3.2 unscramble then interleave flashes into one unified dump. Let’s call the output file 256Mb.bin.If is error bloks check if mixed up with nand0 to nand 1 3. Open 256Mb.bin with HxD 3.a.This is the old way. 3b. Go to offset: 000C0020 (Ctrl+G) which should look something like this (BRICKED PS3 DUMP @ 000C0020) Code: 00 00 00 00 00 00 00 00 00 00 00 00 00 53 CC 78 .............SÌx 00 00 00 01 00 00 00 18 00 53 CC 78 00 00 00 00 .........SÌx.... OR SIMILAR TO THIS (WORKING CONSOLE) Code: 00 00 00 00 00 00 00 00 00 00 00 00 00 6F FF E0 .............oÿà 00 00 00 01 00 00 00 17 00 00 00 00 00 6F FF E0 .............oÿà 00 00 00 00 00 00 04 60 00 00 00 00 00 00 44 98 .......`......D˜ 61 69 6D 5F 73 70 75 5F 6D 6F 64 75 6C 65 2E 73 aim_spu_module.s 65 6C 66 00 00 00 00 00 00 00 00 00 00 00 00 00 elf............. 00 00 00 00 00 00 49 00 00 00 00 00 00 01 E2 54 ......I.......âT 61 70 70 6C 64 72 00 00 00 00 00 00 00 00 00 00 appldr.......... Open 1patchcos.bin in HxD, Select All and Copy Go back to your NAND dump and go Edit – Select Block In the box that pops up, tick the length button to enable the text and enter DFFFE1 as block length. Then go Edit – Paste Write (not insert!) This next step is optional, I would suggest trying without this patch first as I did have success without it. 1patchcos.bin is based on 3.41 CoreOS, and 1patchcos355.bin is based on 3.55 CoreOS. The second worked for me. The original 1patchcos.bin should work so try that first, in rare cases (like me & EiKii) it doesn’t then try 1patchcos355.bin. 3b. Now go to offset: 00093800 and you should find something like this: Code: 00 00 00 00 00 00 00 20 00 00 00 00 00 00 00 20 ....... ....... <-PASTE WRITE FROM HERE 00 00 00 00 00 00 20 00 00 00 00 00 00 00 00 00 ...... ......... 00 00 00 00 00 00 00 00 00 00 00 00 00 00 02 60 ...............` 53 43 45 00 00 00 00 02 00 00 00 02 00 00 00 00 SCE............. 00 00 00 00 00 00 02 00 00 00 00 00 00 00 00 60 ...............` Open 1patchtrvk.bin in HxD, Select All and Copy Go back to your NAND dump and go Edit – Select Block offset: 00093800 In the box that pops up, tick the length button to enable the text and enter 1F00 as block length. Then go Edit – Paste Write (not insert!) 4. Save the changes – IF THE FILESIZE HAS CHANGED YOU DID SOMETHING WRONG! 4.a-This is a new way-Use WINSKEET tool pather for pacht jour nand-256mb.bin(progskeet pacht txt) 5. Again open FlowRebuilder v.4.1.3.2 and this time we want to Re-scramble the modified dump then de-interleave it into two new flashes. Choose your flash0.bin, flash1.bin and the 256Mb.bin you modified. When done it should say 42 or 43 blocks modified each NAND depends on if you only did one or both patches Now you end up with 2 new files called flash0.bin.new.bin and flash1.bin.new.bin. if use PROGSKEET + NAND 360 CLIP NO NEED POWER ON PS3,USE 3.3V External Power Supply ************* [ - Post Merged - ] ************* This is all you need to downgrade NOR or NAND PS3,link:http://www.mediafire.com/?wlxfgc8zobdl2cl |
Use the newer patches found on ps3devwiki if you haven't already, they seem to work better than the older patches.
Try flashing back your original dumps to see if the ps3 will boot. Grounding tristate on a nand ps3 has never worked for me to keep it on....not saying it doesn't, but i've never had any success with it. Also use the newest flowrebuilder available 4.2.1.2 i think it is. |
Quote:
Thanks for your guys help. I feel like such a noob with Progskeet. LOL. Well I am gonna have to try flashing the original dump back later. I have someone dropping off 5 nor models. Also I have a nor model for someone else I need to get done. At least I shouldn't have problems with those. :). I hope I can get as good with the nand models. |
Quote:
|
Quote:
I just got done downgrading a bunch of nor models with my e3. I think I'm gonna take a break and maybe work on this nand model tonight. |
| All times are GMT -5. The time now is 12:12 AM. |
Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2013, vBulletin Solutions, Inc.