Slim Spontainous Death

V

Vest1ge

Hay, Guys

Had this slim I was glitching, turned it on for 30secs outside of the steel case to get the CPU key. After it hadn't booted in that time, I decided to put it in the case, as that has helped boot times for me in the past.

Turn it on again, fan spins a couple of times and the xbox powers down.

Now it just beeps and doesn't power on, however power to the coolrunner is still there.
 
jsinger47

jsinger47

Troll Eating Dogs
Feb 6, 2011
8,133
128
Grand Rapids, MI
A fried r3B15 resistor can cause this. Its a 33 ohm resistor. However your first step should be to remove everything and try the console stock
 
Last edited:
V

Vest1ge

Were is that resister located?

It wouldn't be heat damage unless there was a loose blob of solder shorting it out potentially.
 
V

Vest1ge

Yea i didn't see your post edit.
I know which one it is
Its not damaged and still working
 
jsinger47

jsinger47

Troll Eating Dogs
Feb 6, 2011
8,133
128
Grand Rapids, MI
Vest1ge said:
Yea i didn't see your post edit.
I know which one it is
Its not damaged and still working
Click to expand...
Sorry about that ninja edit there. Wasn't ninja enough. Haha

Yeah, I've seen that caused by that resistor. However i'd start freash with stock nand and no wires. Get it to boot stock is the best way to try to diagnose an issue
 
V

Vest1ge

Attempting to read the nand with J-Runner

Looks like its killed the nand.
Hopefully a Progskeet would allow me to rewrite the nand.

Arm Version: 3
Flash Config: 0xFFFFFFFF
Unknown Flash Config found.
This may due to a new console type, bad soldering or hardware failure.
If it isnt the first check your soldering and reset your device.
 
jsinger47

jsinger47

Troll Eating Dogs
Feb 6, 2011
8,133
128
Grand Rapids, MI
Vest1ge said:
Attempting to read the nand with J-Runner

Looks like its killed the nand.
Hopefully a Progskeet would allow me to rewrite the nand.

Arm Version: 3
Flash Config: 0xFFFFFFFF
Unknown Flash Config found.
This may due to a new console type, bad soldering or hardware failure.
If it isnt the first check your soldering and reset your device.
Click to expand...
Where is biohazard when you need him? Anyway I think that bad resistor killed his reading too, but I'm not 100% on that. He's the guy I've seen a similar issue with. He fixed it by replacing the resistor with a 33 ohm smd. And yes his soldering was impeccable. crazy things happen sometimes though
 
V

Vest1ge

I've seen it too,

get quite a few blotched jobs sent to me to fix. However this is just WTF!

EDIT: This was for two posts up!

---------- Post added at 15:21 ---------- Previous post was at 15:18 ----------
joesinger47 said:
Where is biohazard when you need him? Anyway I think that bad resistor killed his reading too, but I'm not 100% on that. He's the guy I've seen a similar issue with. He fixed it by replacing the resistor with a 33 ohm smd. And yes his soldering was impeccable. crazy things happen sometimes though
Click to expand...
Now i need to find that info!
(im pretty sure a progskeet can fix this, I got one on the way from chinadistrib after 2 months of it being out of stock.)

Tried bad flash recovery managed to change the flash config looks a bit corrupt

Arm Version: 3
Flash Config: 0xFAFA0EE0
Unknown Flash Config found.
This may due to a new console type, bad soldering or hardware failure.
If it isnt the first check your soldering and reset your device.
You can always press ESC to cancel the read.
Error: EFE reading block 0
Error: A7E reading block 1
Error: A1A reading block 2
Error: EFE reading block 3
 
C

cskalash

Full Member
Dec 6, 2011
83
0
europe
Did you fixed it?
have you tried connecting the power cable just 1 second after you pressed enter on nandpro?
Those things happened to me more then once. Usually i get the nand erased that way. Then it's just writing it back. You may need a few tries although.
 
You must log in or register to reply here.