[Psymon]

Okay it's a bad dump. Did you clean your Nand pins with Isopropyl and a brush?? I think it is a connection Problem with the NAND-Clip. It should always identify your NAND correct when you press Auto.

How long did it take to "dump" your NAND??

[amined]

Originally Posted by Psymon How long did it take to "dump" your NAND??

one minute or less

[mmmilo]

Originally Posted by Psymon Okay here we go: -PS3 Model CECHC04, -Motherboard COK-002, -Progskeet V1.2, -360 Nand Clip 48, -Winskeet Version 111205, -Nothing changed with R7 or R8, -Power supply via USB (3.3 V and GND from Progskeet to PCB Board), -Bitstream Version 121018.0031, -Slave Board switch on (LED is on) while connecting to PC, then switch off to dump, -in Winskeet select double NAND Samsung K9F..., -at NAND Register the NAND gets recognized via AUTO correctly, -dump the NAND (hopefully without errors). Hope this helps. Greetz Psymon

Wich driver did you use for progskeet? libusb or winusb?



And please coud you check what values you got in the pop up window at infectus programmer at "ACTEL_SLOG_UROW=" when updating bitstream of progskeet? I got FF FF FF FF ..., but Winskeet recogizes the progskeet.
I'm still afraid of bricking my PS3, if my progskeet isn't working.
please

[Lizard360]

Infectus shows me the same sequence (FF FF ...) and I already dumped my nor with my progskeet 1.2 So don't be afraid. If your WinSkeet recognizes your Progskeet then you should be good to go. Taking a good dump (Let somebody verify it for you if you are not sure) should be possible. Writing it back will probably be your problem...

[MJ999]

Originally Posted by Serena5233 Kazrael, mind to share where u get the skeet 1.2? thank

Check progskeet distributors list

[Psymon]

Originally Posted by amined one minute or less

That is too short. It should take 8-9 Minutes. Try cleaning your Nand and the clip and dump again.

@mmmilo I used libusb driver. Don't know the ACTEL_SLOG_UROW Values but as Lizard360 said i think that if the Progskeet gets recognized correctly then you're fine. Did you try to dump?

[mmmilo]

Originally Posted by Psymon That is too short. It should take 8-9 Minutes. Try cleaning your Nand and the clip and dump again. @mmmilo I used libusb driver. Don't know the ACTEL_SLOG_UROW Values but as Lizard360 said i think that if the Progskeet gets recognized correctly then you're fine. Did you try to dump?

No, but today i'll try And if succesfull Post some pics And more Infos.

Sry, but if you say libusb, did you checked that with zadig.exe?
Cause Windows Shows always The Same Description for progskeet.
What i ment is, did you used The regular progskeet driver?

I used zadig.exe to Transfer drom winusb to libusb And winskeet doesnt recocnizes it, but The Old progskeet flasher program does. And with Win USB only winskeet detects progskeet.

I Managed Dumping wirh both drivers And both Tools an xbox 360 nand, but only The size did Match- The jrunner says: "Wrong Header"

I will Share my solideres experience this afternoon.


Thx for your help, this ist The 5th Forum i Asked for The Actel values And The Otters just ignored my question.

Thx

[xerxesrex]

Originally Posted by Kazrael21 http://www.vgcrepairs.biz/progskeet-...progskeet-v1.2 Use this coupon code to save some money too :WeBrewWii -I got it cheaper than advertised haha. ************* [ - Post Merged - ] ************* So I have 3 NAND models I am trying to recover from bad flashes, so i guess I dont need the address lines...Ill still be e-mailing progskeet to get those and I will post whatever replies I get here. so I guess its because I am still very new at this but this is whats confusing me when I try to connect my chip: NAND1 Connection: Data signals P41 = IO7 / DQ7 P40 = IO6 / DQ6 P39 = IO5 / DQ5 P38 = IO4 / DQ4 P37 = IO3 / DQ3 P36 = IO2 / DQ2 P35 = IO1 / DQ1 P34 = IO0 / DQ0 Control signals P09 = CLE P08 = ALE P07 = WE P06 = RE P05 = CE_A P04 = WP P03 = CE_B P02 = R/B# NAND2 Connection: Data signals P49 = IO15 / DQ15 P48 = IO14 / DQ14 P47 = IO13 / DQ13 P46 = IO12 / DQ12 P45 = IO11 / DQ11 P44 = IO10 / DQ10 P43 = IO9 / DQ9 P42 = IO8 / DQ8 Control signals P33 = CLE P32 = ALE P31 = WE P30 = RE P29 = CE_A P28 = WP P27 = CE_B P26 = R/B# **** I dont know what Im looking at .. A picture tutorial would be Ideal or if someone could explain what Im looking at. ************* [ - Post Merged - ] ************* @baileyscream what else do I need? this is everything I have.

thanks for your tip, i am looking to my arrival of skeet 1.2 anytime next week, finger crossed. will post my tutorial here hopefully. sharing is caring :D

[Psymon]

Originally Posted by mmmilo No, but today i'll try And if succesfull Post some pics And more Infos. Sry, but if you say libusb, did you checked that with zadig.exe? Cause Windows Shows always The Same Description for progskeet. What i ment is, did you used The regular progskeet driver? I used zadig.exe to Transfer drom winusb to libusb And winskeet doesnt recocnizes it, but The Old progskeet flasher program does. And with Win USB only winskeet detects progskeet. I Managed Dumping wirh both drivers And both Tools an xbox 360 nand, but only The size did Match- The jrunner says: "Wrong Header" I will Share my solideres experience this afternoon. Thx for your help, this ist The 5th Forum i Asked for The Actel values And The Otters just ignored my question. Thx

Can't say for sure. Doesn't have my Progskeet around atm. I used the drivers which were in Baileys Tutorial if i remember correct. Just try to dump your NAND and share it so we can verify it.

[Decoy]

Originally Posted by Psymon Can't say for sure. Doesn't have my Progskeet around atm. I used the drivers which were in Baileys Tutorial if i remember correct. Just try to dump your NAND and share it so we can verify it.

So u didn't power the ps3 from its own power supply , u used 3.3 from prog ?