I've never experienced this and all my boxes have R6T3 removed. There is no reason whatsoever why this would stop Flash360 from updating. I've used XeLLous, Flash360 and NAND Flasher for Xbox 360 1.20 all with success.Personally I don't bridge or remove them, but if you have to do it I'd suggest making a bridge via switch for a very good reason. If you remove or bridge the resistors, it will also stop you from performing standard freeboot update/flash via Flash360 tool.
Of course you'll get E80! flashing stock 6717 to 7371 will result in eFuses being burned, so the update will fail.I had 2 consoles come in when their owners tried to update them directly via flash360 and the update failed. Then I re-flashed the original NAND which one had 6717 dash and I thought to update to 7371 but instead greeted with E80 that's when I looked under the board to find one of them the resistor was removed or bridged.
So this caused both freeboot update as well as standard dash update from 6717 to fail (which is exactly meant to do) but that's from my own experience.
Because they used a stock dash update instead of a freeboot one?That's understandable, but why did the consoles give E80 when updating from an earlier freeboot to the latest dash?
Unless the previous owners did something else that I'm unaware of?
Ditto...Because they used a stock dash update instead of a freeboot one?
E80 is good on a JTAG console. It means that someone has tried to update the eFuses (namely the CB lockdown) but the console hasn't been able to.
Nowhere in your statement above does it say anyone got E80 when trying to update from one freeboot to another. Your E80 was going from stock 6717 to stock 7371, which as I said WILL happen with R6T3 removed.