Wait so now the xbox police are playing good cop bad cop with each other? And how did he attack your kit seems like you ran something you wasn't supposed to. Also you can use I think nand healer to select a 64mb dev nand for reading. And I would advise you to use a usb reader/writer. Also I'm guessing you have a good nand dump before this happened? The reason for the read errors could be many things, if your using lpt then it could be that. I remember u had trouble with the cygnos, so you might want to check your wires. If need be you can send it to me and I can flash it back via usb. Hawk
I have done about 7 or 8 jtag's now and I tripple checked my wiring. Soniciso was never the "xbox police", he was one of the people who stood behind and had a huge hand in bricking kits. However he isn't my concern the immaturity of these people can drop where it lyes. I used redlines tool to make two backups of my nand so it should be fine. I guess I'll just send it to a friend I was hoping it was a simple thing I was doing wrong in nandpro but apparently it might be more than that. Thanks anyway. If anyone else has suggestions throw them my way.
I should have made my nand write protected and had it removed but unfortunately no I did not. Still it should throw an error if the fuses are blown but it seems like there is something wrong with my writing. I have resoldered everything like 3 different times.
Yeah he could have made a syscall to fuck the fuses. The same one M$ uses to brick kits. You should find out if thats what he did. If so, you are out of a devkit.
I think shorting the pins should be the best solution at this point and I doubt I have a paper weight people have recovered from this before. I'll let you guys know how it goes in a few days.
Fixed thanks everyone. It wouldn't have took me so long if I wasn't so busy with life. Tomorrow I will write a tutorial to protect against soniciso and companies' petty attacks on the scene. Just know if you have been bricked (not by partnernet) and have not sold or sent away your kit and have a backup you can come back from this. Don't listen to anyone else kids. I have a fool proof way of protecting running new or untested software that may contain smc corrupting and or malicious code as a thanks to the scene. I will post tutorial tomorrow.
I had the same happen to my box, will using a nand-x or similar device work to flash back my backup of the flash? If not, what can I do to revive it?
this is what i pmd to lllsondowlll,and that worked for him. i have once flashed a xenon nand on a falcon board,so it didnt boot,got the same error 01198030. take a stripped wire,hold it with your fingers on both sides on all the pins of the nand chip,then plug in your power brick(dont' be scared,was swaeting when i had to do this!but you won't get shocked!) then quickly remove your wire. if your powerbrick is red,you have to do it all over again,means it didnt work... if your powerbrick stays orange,you schould be good to go and be able tio write to your nand and have the good flashconfig and be able to flash. do not remove your powerbrick after you did this and remember to firmly push your wire on all pins. this resets the nand. this can take a few attempts but it worked for me. i think your "kill switch" is nothing more then another or wrong smc version from another type of nand then yours. let me know how it goes...