RGH Error creating ecc for Zephyr

[Krafter]

And just so you know, the CB will be rebuilt to 4578.

 

[The504]

That I can do. I'll report back once I'm done.

A Split Kernel is like CB_B, they're on all of MS refurbs.

 

[Martin C]

oh FFS stop!

Now I have the history of it, it makes sense.

It was JTAG'd using standard wiring. Therefore you re-wire it as a JTAG to make it work. Flash back the original NAND and it should boot up.

If not, Random E79's were caused by the wiring method, so keep this in mind whether you need standard or AUD_CLAMP wiring.

You do NOT need to RGH this.

 

[charincol]

Just got done reading this thread and was wondering why, if it was Jtagged before, the OP is trying the RGH it, but you posted the solution Martin.

There is absolutely no reason to RGH a Zephyr if it was booting perfectly fine with the Jtag/SMC hack.

(There's a good reason why you shouldn't consider Jtag and RGH the same hack. This thread is an excellent example of the confusion it creates.)

 

[Krafter]

oh FFS stop!

Now I have the history of it, it makes sense.

It was JTAG'd using standard wiring. Therefore you re-wire it as a JTAG to make it work. Flash back the original NAND and it should boot up.

If not, Random E79's were caused by the wiring method, so keep this in mind whether you need standard or AUD_CLAMP wiring.

You do NOT need to RGH this.

He doesn't have to original nand or the keys. I suggested he use the AUD_CLAMP method to JTAG but he said that's how it was before and still had the random errors (not sure I believe that though). He seems to be pretty adamant about RGHing this thing. That's why I suggested he JTAG it to get the keys so he can create a RGH image.

 

[Martin C]

With a JTAG you don't need ANYTHING to boot to Xell.

Get Xell (Xellous) booting first to get the CPU key. We can then go from there. The keyvault in the JTAG image will still be valid, as will the config.