Buck147 wrote

XGrizzlYX41 wrote u said its 7371 then asked if it was bricked cause it was nxe dash, if it has nxe dash then its not 7371

7371 IS NXE DASHBOARD DUMBA#S! It is Jtagable as long as you didnt buy it from Microsoft with that kernal. If you had kernals before the current one you have and then you updated to the kernal to what it is now it is Jtagable...

why does it matter if you bought it from microsoft.
just as long as the kernel isn't past 7371 it can be jtagged because any kernel after that wipes the efuses rendering it incapabable of retrieving the cpu key. man i wish there was a way around that. microsoft is so stupid lol.

oh and if you need someone to jtag it for you PM me bro.

xxLONEx_xWOLFxx wrote

Buck147 wrote

XGrizzlYX41 wrote u said its 7371 then asked if it was bricked cause it was nxe dash, if it has nxe dash then its not 7371

7371 IS NXE DASHBOARD DUMBA#S! It is Jtagable as long as you didnt buy it from Microsoft with that kernal. If you had kernals before the current one you have and then you updated to the kernal to what it is now it is Jtagable...

why does it matter if you bought it from microsoft.
just as long as the kernel isn't past 7371 it can be jtagged because any kernel after that wipes the efuses rendering it incapabable of retrieving the cpu key. man i wish there was a way around that. microsoft is so stupid lol

He is correct on the MS thing...If one gets sent in for a "Repair" or you get one from MS, they block the exploit so you cannot Jtag it..

I thought everyone knew that!

how though? nitz0.....

Have you ever heard of MS consoles coming back with xmas lights??

They're not that stupid...They have their ways that people like "us" are oblivious too..

yeah that dash can be jtagged