I did not mean any disrespect or to appear to doubt you.
Neither I was being mean or anything of the sort. I just wanted to emphasis what I said earlier as I am also thinking about the possibility of other people reading this thread. So don't think I'm angry or anything. I'm not... lol
I'm just trying to broaden my understanding of nand and fuses. In one of my earlier questions I had asked if there was anyway to test what fuses were blown. The answer if I remember correctly without looking back was "not if Jtag has been disabled by updated fuse".
Again, very understandable. To help you a little further I'll post this:
Xenon console, CB 1903
00: C0FFFFFFFFFFFFFF \ I believe these two are used to differ the system from DEV to RETAIL.
01: 0F0F0F0F0F0F0FF0 /
02: 0F00000000000000 <- CB 1903
03: XXXXXXXXXXXXXX \ These two are doubled... 1st half of CPU key
04: XXXXXXXXXXXXXX /
05: XXXXXXXXXXXXXX \ So are these. 2nd half of CPU key
06: XXXXXXXXXXXXXX /
07: FFFFFFFF00000000 <- Fusebits for updates. They blow 4 bits on each update so an extra F will show up here each time you update.
Jasper, CB 6723
0000F00000000000 <- CB6723
My question was not about if my board has had the fuse updated. I believe and understand what you told me. The questions was about if I could utilize the jtag hack to diagnose IF a unknown boards CB fuse had been updated.
If you flash a hacked image onto an "fixed" (updated) board you will get 3RLOD with secondary error code 0022. So it's possible to test. It's just that there's a good chance you might be wasting time with it. With a XELL image, you don't even need to worry if the system is software-bricked, if the hardware is in perfect working order and the JTAG hack wired up properly it will boot onto XELL. That actually allowed me to unbrick two XBOX360 consoles that failed updating due to power outage.
Just yesterday I did not know that write protecting the nand would cause me to kill a board. I'm well aware that what I don't know would fill volumes.
Of course the person who had the idea to setup the write protect, test it and posted it on X-S never had bad intentions, but of course the person forgot to think of eventual collaterals/side effects such a mod could have.
I simply wanted to know if attempting jtag hack after CB Revocation fuse has been updated will cause anything bad or unrecoverable to happen?
Not at all but it won't work. Restoring the original image would then be necessary to make the system work again.
Like I mentioned on other thread, even a system that has E74 will boot the hack...
But once the revocation fuse is set, kiss JTAG goodbye on that CPU chip.