PS3Hax Network - Playstation 3 Hacks and Mods - View Single Post

ps3dude2 · 01-11-2013

thanks for the reply and it was your guide that i followed which is a great guide, i followed the prog 1.2 section for nands but i guess as you said above that the guide doesnt fully support it.

i have been doing one nand and only one nand but i alos thried the other nand, and i also tried the nands of another phat ps3 and all the same results, nothing.

but what puzzles me is when i plug in the slave board windows automatically says the device has malfunctioned with out the progskeet even plugged in so could it be the slave board not communicating well? and when i test for shorts its perfectly fine like theres nothing wrong but as soon as i plug the y Adapter in, it says its shorted.

i know im putting alot of info its just theres aot i did to try to make it work but nothing worked, nothing.

so one last thing which i somehow forgot to mention in the original post, it is when i did the infectus thing to program it the progskeet the device info button reported this

ActID = 02a121cf
ExpID = 03a121cf

Initializing Target Device...

Setting BSR Configurations...

Reading Security...

SILSIG:
E5 B1 00 0B

ACTEL_SLOG_UROW =
FF FF FF FF FF FF FF FF FF FF FF FF FF 00 FF FF

User information:
CYCLE COUNT: 00000003

CHECKSUM =
FF FF

Design Name =
FF FF FF FF FF FF FF FF FF

the FF's is what concerned me so is it the progskeet thats F'ing up??

thanks in advance

P.S one of the links is broken on your tut, the one to check for the 1.2 defective pcb.

01-11-2013	#3
ps3dude2 Apprentice Join Date: Dec 2010 Posts: 14 Likes: 1 Liked 0 Times in 0 Posts Mentioned: 1 Post(s) Tagged: 0 Thread(s)	thanks for the reply and it was your guide that i followed which is a great guide, i followed the prog 1.2 section for nands but i guess as you said above that the guide doesnt fully support it. i have been doing one nand and only one nand but i alos thried the other nand, and i also tried the nands of another phat ps3 and all the same results, nothing. but what puzzles me is when i plug in the slave board windows automatically says the device has malfunctioned with out the progskeet even plugged in so could it be the slave board not communicating well? and when i test for shorts its perfectly fine like theres nothing wrong but as soon as i plug the y Adapter in, it says its shorted. i know im putting alot of info its just theres aot i did to try to make it work but nothing worked, nothing. so one last thing which i somehow forgot to mention in the original post, it is when i did the infectus thing to program it the progskeet the device info button reported this ActID = 02a121cf ExpID = 03a121cf Initializing Target Device... Setting BSR Configurations... Reading Security... SILSIG: E5 B1 00 0B ACTEL_SLOG_UROW = FF FF FF FF FF FF FF FF FF FF FF FF FF 00 FF FF User information: CYCLE COUNT: 00000003 CHECKSUM = FF FF Design Name = FF FF FF FF FF FF FF FF FF the FF's is what concerned me so is it the progskeet thats F'ing up?? thanks in advance P.S one of the links is broken on your tut, the one to check for the 1.2 defective pcb.