Print

[Accord]

I've never seen that error ... then again, I've only used Flash360 once to update from XBR3 to FreeBoot .032.

On the original set of instructions I used, it said to dump the NAND via Flash360. The NAND on my current machine was XBR3 (8955). I took the XBR3 NAND into ToolBox Maker and it kept generating errors. Further research proved that the 8955 kernel can't be used with TBM 2.2. Fine.

I took my original NAND and threw it directly into the FreeBoot Toolbox Maker 2.2. No problems at all. With the CPU key, I generated the proper output, renamed it, then flashed away.

(placed the updflash.bin file where Flash360 is installed on the HDD, updated)

[PaganOne]

Don't use flash360 much, I stick with Xellous.  With that being said, IF I remember correctly last time I upgrade a console to freeboot 0.32 from freeboot 0.30 (only had XeLL) w/ flash360 it warned me about not being zero-paired which I ignored.  Also ignored warning about KV not matching, etc. etc. and it flashed just fine.  Take it with a grain of salt, but I don't think I've seen a single freeboot image in 360 flash tools that had zero-pairing data.

[juggahax0r]

Yea dude if you are positive you did the KV and Config correctly then the zero pairing doesn't matter. Well haha let me rephrase open your updflash in flash 360 dump tool Whatever the hell it is called flash tool 360 i think. And check that it is in fact zero paired , in the pairing section it should say 0x000000. The rebooter reboots to post 40 too MFG boot mode which allows it too skip the CPU check or rather it reboots it back to a place after the CPU fuses have been checked already so it doesn't check it again and you can then patch whatever you want in that patch sections as long as it is zero paired , the zero pairing skips the CB check 2bl i think if i remember correctly.

 And your main concern about the Zephyr E79 is just something you have to deal with me and a whole group of people on here have tried different things with no luck , just use the 1n4148 diodes and i usually bridge points 4-7 with a piece of the diode i cut off to shorten the stem works perfectly and environmentally friendly haha , except the lead solder haha. My Zephyrs do it less and it is probably because i strip them very short and i use shrink tube.  The wires could be catching radio signals with those small signals any interference will cause a problem. I shrink tube all my wires right at the diode and keep the part short that i strip. E79 means that it is trying to what you want but it can't shift in the data with Jtag because something isn't getting power. My theory is that it has to do with the connection we "steal" from the ROL , i know a few other HDMI models will have this problem randomly as well just not like the Zephyr , every single Zephyr does it I have yet to see one that didn't.

 In summary , check your pairing data externally on your PC make sure it is zero Paired. When you change any information on the KV it will give you that error it isn't true though and you should be fine.  The SMC is really the main way people have tried to fix it. They used a Falcon SMC but it still happens.