Accidentally Turned On Xbox

J

JTAGJasper

Junior Member
Apr 29, 2011
11
0
I was in the process of trying to obtain a nand dump using a NAND-X and I discovered I had inadvertently turned on my Xbox. I have no clue as to how it happened.

Prior to this I was having difficultly detecting my controller and I was getting constant errors during the dump. Now I am having no luck at all detecting the controller. I am certain it was a soldering issue and I fully intend to bring it to a friend with stronger soldering skills and steadier hands. Now I am having no luck at all detecting the controller.

I am still able to boot and write to the Xbox's memory unit using the original dash. So my question is.. Is it possible I have damaged the controller or my NAND-X or am I safe in assuming correcting the soldering issues should resolve my problem.
 
D

dec0y7

VIP Member
Apr 15, 2010
160
0
Sheffield uk
i would say it the soldering, you can never go wrong with having a multi meter at hand to check.

and as for the detecting the controller, if you look around the forum im sure you will find loads of threads with help on this.
 
J

JTAGJasper

Junior Member
Apr 29, 2011
11
0
Thank you for your response. But I really should ask my question more pointedly. The guide states that the Xbox should NOT be powered on while the nand-x is in use. Can doing so cause catastrophic damage to the NAND or the NAND-X?
 
J

JTAGJasper

Junior Member
Apr 29, 2011
11
0
Thank you. It seems that as my Xbox seems to be working normally and that my points are testing out OK with the multimeter that this could be the case. I'm not excited by the prospect of using an LPT on a 256 Jasper but it doesn't apepar as though I have much of a choice.

It'd be great to know how the unit turned on. I have no memory of touching the button or bumping against it with anything. C'est la vie.
 
J

JTAGJasper

Junior Member
Apr 29, 2011
11
0
RDUBBS: Windows still shows in the dev manager and is detected by NANDPRO.
TEAJUNKIE: I'm certainly entertaining that posibility. Do you think it would be worth resoldering using the pinheader cable?
Has anyone else reported their NAND-X blowing from having the Xbox turned on?
 
Last edited:
U

umpa2011

Full Member
Apr 28, 2011
78
0
England
i also turned on one of my xboxes whilst reading the nand. i have just about done anything and everything wrong at some point lol.

nothing bad happened, my nandx is still ok.

have you tried plugging it in to another usb port.

ump...
 
J

JTAGJasper

Junior Member
Apr 29, 2011
11
0
Umpa2011: Thank you for sharing your experience with me. It's very encouraging.

TeaJunkie: Will do. I plan to meet with a friend who has a ton of experience with soldering surface mount electronics and again has much steadier hands. Hopefully we can knock this one out.

What a great support forum this is. You are all so responsive and helpfull. I'll do my best to "pay it forward" once this is all sorted out.
 
J

JTAGJasper

Junior Member
Apr 29, 2011
11
0
I think I can rule out a blown NAND-X being the problem. I brought my console into a professional console modder who has jtagged at least 20 systems in the past. He removed the QSBs from my board and direct wired the J2B1 and J1D2 pads. He was unable to detect any apparent damage to the pads through casual observation. He used the Maximus 360 NAND flasher and was also unable to detect the NAND controller. He checked and rechecked the points and both the top and bottom of the pads to no avail.

So here is my question. If the USB flasher and wiring is fine. And the 360 is still able to boot and write to the Memory Unit via the stock dashboard. How do we proceed? Are there alternate points we should be looking to wire to or is their some other means of bypassing the motherboard to read and write to the NAND.
 
J

JTAGJasper

Junior Member
Apr 29, 2011
11
0
Here's what I found out from the hero that is has taken over the daunting task of fixing my botched attempt to install a NAND-X.

It would seem that I have blown the Xbox's SPI (Serial Peripheral Interface Bus) which NAND-X uses to access the NAND. I'm not sure how it occurred. I suspect it was done either by soldering very poor connections with my QSBs or by inadvertantly turning on the XBOX while the NAND-X was plugged in. The good news is that my console still works but I am unable to dump or flash the Xbox's NAND using traditional methods. Fortunately my console modder may have found a workaround.

The Cygnos V2 rev. F bypasses the Xbox's SPI and solders to directly to the NAND points on the back of the motherboard.

I have ordered the Cygnos but it has not been installed yet. I can not confirm that it works for my situation however I have seen a couple posts in other forums stating that this is a valid solution for damaged SPIs. I'll be posting again to confirm if and/when it is working.
 
Last edited:
J

JTAGJasper

Junior Member
Apr 29, 2011
11
0
The Cygnos V2 rev. F was able to update my flash and I now have a 360 which is befitting of my name. This is not a pitch for the Cygnos. I like many aspects of the mod and I am thrilled that it has enabled me to overcome this problem. However, documentation for it is vague and it seems like support for it is on the decline. That said, if there is no apparent damage to your board and yet no matter what you try to still can't detect the NAND controller. You may want to entertain the possibility that you to may have damaged the motherboards SPI. So you may need to either have your board serviced by a technician who can replace your SPI or you'll need to use a solution like the Cygnos with a built in SPI. Hope my misadventure can help someone else.
 
You must log in or register to reply here.