Incorrect voltage on 3v3 point?

Disperat

Senior Member
Jan 3, 2012
100
0
Hello,

First of all, very detailed and useful information on this forum and thank you for that.

LE: Noticed that I've wrote a lot, so, for the short version, read the quote:

1. On dash 14699, read nand, created ECC, write ECC, save CPU Key.
2. Reverted to stock dash.
3. Updated to 14719.
4. I've redumped the nand. Created 14719 glitch image and wrote it using NAND-X and J-Runner.
5. Even on Nor position on the CR, the red light isn't lighting.
6. Using a multimeter between GND and 3v3 I've got 0.5V.

Things I've tried:
- changed all the wires and resoldered them;
- writing the stock nand back with the CR on Prog: the console boots normally (at least for 1 min, before I've shutted it down);
- tried with another CR;
- using QSB top side.

For more details, please read below
The story so far...

I've bought an Xbox Slim in August 2011, with Trinity motherboard and DG-16D4S. In December, by doing kamikaze method I've written the Custom FW on the DVD without problems.

At that moment, with dashboard 14699, I've considered even if I don't want to RGH, it would be a good ideea to have the CPU Key, so I've soldered a CoolRunner, read nand with NandX, got the CPU Key, rewritten the stock nand back. I've left the CR and wiring on board, CR switched on Prog.

Following that, for two-three months, the Xbox was used for multiplayer on XBL. Yesterday I wanted to activate the RGH, so I've got busy. :)

First, resoldered the NAND wires, reading twice the nand with J-Runner - I've read again using J-Runner because my last dump was from 14699, and now the console was on 14719, so my LDV was changed for sure.

I skipped the part with Create/Write ECC, already having the CPU Key, programmed again the CR with the Trinity timings, created a 14719 Image and written it via USB with the NandX. Now the weird issues started.

I've power cycled the Xbox (1-2 min), switched the CR on Norm and plugged the power cable. At that moment, before turning it on, I've noticed that the red light on the CR wasn't on, althrough the CR was in Norm position. I thought that maybe I've moved or unsoldered the 3v3 line, so I've replaced it with a spare shielded cable (RG174).

Now the red light was on, so I've powered up the console, the CR glitched 2-3 times and stopped (no more green led), and I've noticed that I've forgot to plug the video cable. I thought that it glitched, but not having the video cable plugged obviouslly it didn't show anything on the screen (althrough the green light circle, the one from startup, didn't show, just it sopped glitching). Powered down, unplugged the power, plugged the video cable, plugged the power back. Again, the red light wasn't lighting anymore.

Things I've tried:
- changed all the wires and resoldered them;
- writing the stock nand back with the CR on Prog: the console boots normally (at least for 1 min, before I've shutted it down);
- tried with another CR;
- using QSB top side.

Having another console around, already with RGH, using a multimeter I've measured the voltage between GND and 3v3 in standby, and, "surprise" :D, it had around 3.3 V. That was on a console with working RGH.

I've taken the same measures on my console, first between 3v3 ont the CR and Ground, and got around 0.5V. Measured again from back of the board, at the point, also 0.5V. Hmmm.

Has anyone an ideea of what did I do? :D And how to repair it, of course. If it helps, I'll post pictures as soon I'll got my camera back in a few hours.
 
Last edited:

Disperat

Senior Member
Jan 3, 2012
100
0
Pics are needed - we cannot possibly help without them.
I've seen that post from you a hundred times by now and yet you have patience not to ban/warn/yell at. Thank you for that, Martin. :)

I know I must post pictures of soldering and I will, but instead of using crappy phone camera, I'll wait a few more hours until I'll get my hands on a Canon with macro function. Sorry for not attaching them from the first post.

I'll put them here the moment I'll take them.
 

Disperat

Senior Member
Jan 3, 2012
100
0
Just for the record:

I didn't put pictures anymore because until the camera got to me, I've solved the problem. It appears that at some point I think I broke the trace to the 3.3V point. I discovered by mistake that when I was gently flexing the board I had 3.3v on that point, but without any pressure the point was dead.

Anyway, I've noticed that a nearby point has standby 3.3V and have continuity with the original point (I don't remember which without opening the console) and now all is well.

Thanks for the support to all!