14 is actually connected, to a small circuit, although I have no clue for what purpose.

Indeed. And since all has been said that was useful info, I'm closing this.

uberfry, drop the picture crap. this isn't 4chan or some kid's forums.

schematics and diagrams are not available publically.. I doubt they're anywhere but in MS' safe.

The channels are empty except for the bots, there's nothing secret going on in them. Work on Xexloader continues nontheless.

That's well out of the area that has anything to do with XBR or your config/kv.

yep.

And if your friend managed to pull "a few" solder points, he better take his hands off that console right now. He's obviously completely incapable of soldering. Those points are huge and quite stable. And as said, the timing attack was fixed over 2 years ago.

My advice? Ask about your pirated crap elsewhere.

same as above, except you go backwards on the highest address.. (I think it's 3FFF for 256 MB).. 3FFF for one, 3FFE for the next, 3FFD.. etc.

There's no way to tell. They generally hold up longer than the xenon/zephyr, but there's still a chance of ROD. Only Jasper finally dropped the dead console rate to a normal level.

The thing is, TX has for years not been the team that developed the great xecuter 3 chips for the xbox 1. these are just guys who make a commercial product out of a free hack, even if it's just replacing some wires, a resistor and a switch.

Networking is heavily encrypted and the servers aren't in any way accessible anyways.
Also, if you don't want to spend money on MS and dislike them, I suggest you stop using windows and the xbox360 right now.

It does work with them.

The order doesn't even matter, the nand filesystem simply checks all the reserved blocks at the end for the missing one.
If the full nand is 7FFF long, then yes, 7FFF.

Read Block B0 from the XBR image with nandpro to a file. Then write the file to whatever the last block of the full nand is.

cause you can't just load xbes, they still have to go through the emulator.

Exactly. Also, it's not a version number check that keeps it from booting, but the efuse configuration "tells" the kernel that it is not permitted to launch. The kernel itself checks against that.

You could still extract secdata from the old dump and insert it into the new flash.

nand write protect makes no sense since you can't go online with a jtagged console anyways. switching the jtag hack doesn't make any sense either, as the hack as such isn't detectable and doesn't cause any issues with any firmware.
it's advisable to remove r6t3, switchable isn't of much use, since XBR/freeboot don't need it, and if you do any official update that needs it, you kill all hope for homebrew on that console.