Search results

Its kind of bricked if its retail. Something went wrong with the hardware, and now hardware and software values don't match. Out of everything that could happen with 360 hardware, this is pretty unlucky. He could possibly fix it by doing the RGH up to the point that he gets his CPU key, then...

From what I understand is that they didn't bypass the check itself, they instead bypassed it by not incrementing the value and not letting the console burn the fuses. Although I understand I may be wrong.

Also, an E80 usually just means you LDV value is wrong in your nand. This makes perfect sense if R6T3 was shorted, as that resistor has to do with burning your efuses(1 fuse gets burned after every update). Did you recently update your console? The LDV in your nand gets checked against your...

Yes. Also if you get no lights again, do it an extra time. So five times total just to be sure your not missing one. How the error codes work: 1 light: 1 2 lights: 2 3 lights: 3 4 lights: 0 It'll turn out to be a 4 digit code, for example 0102

You need to do it four times total. Also, no lights on the second one is a bit unusual. Double check if it happens again.

To get the secondary error code, when the console is on with the red lights, press the sync and eject button at the same time. The lights should change and blink faster, do this 3 more times and post what you got.