[Droid Eris Q&A, Help & Troubleshooting] bftb0:
That's precisely what I was getting at. Because the supply voltage to the CPU is stepped up as frequency is stepped up, it generates a lot more heat when running at high clock rates. Way more than you would expect. There have been users over on AF that burned their phones up in as little as one week by aggressively overclocking. I wouldn't recommend to any of my friends that they OC an Eris to 806. (I have mine peaking at 729, and I have never even tried to see how high it would go.)

Well, your first post indicated you were also having problems with "old, very stable nandroid restores" - I suppose that they were not OC'ed to 806, and also didn't have these new tweaks applied. So, there is no reason to believe those older ROMs would be affected unless physical damage had occurred to your Eris.

Same comment as above - why would a software change in one ROM affect the behavior of a completely different ( "old, very stable nandroid restores" ) ROM? If the 1.5 ROM is also crashing, remember that it isn't even overclocked!

You are correct that the OTA doesn't touch the bootloader, but if you have run the Leak-V3 before, doesn't that would mean that you already have the 1.49.000 S-ON bootloader on your phone? (unless you were you able to change the bootloader back to 1.47 when you "went back to 1.5").

In any event, you might be getting overly anxious about it for several reasons. While you are absolutely correct that a team of forensic experts hired by Verizon to examine your phone might be able to look up the date of purchase and customer history to determine that you shouldn't have the 1.49.0000 S-ON bootloader on your phone, the chances of them taking that kind of interest in your phone is essentially zero - they get thousands of returned phones every day (all makes and models). There have been posters on this forum that reported returning multiple rooted Eris without making any effort to clean them up, and were never contacted or charged by VZW. So, the chances of them taking an interest in your phone because it has a 1.49.0000 S-ON bootloader is pretty small, especially considering that they have been shipping phones for a couple of months now with that bootloader installed.

Still, if you want to try returning it to absolute stock, you probably need to perform Jcase's "Flash any RUU" technique (which modifies the "misc" partition so that you prevent those "Main Version is Older" lock-outs by the bootloader.) That would also allow you to use the PB00IMG.ZIP file from the MR2, along with Toastcfh's "battery pull trick" to only flash the bootloader.

The thing to bear in mind is that the OTA process relies on having a stock recovery partition and the exact version of HTC software that the OTA expects to be upgrading - you didn't say exactly what state your phone was in when you restored to 1.5. Does it have the stock 1.17.605.1 recovery installed, too? Manually downloading the 1.5 -> 2.1 OTA and installing it as an "update.zip" will work - so long as your phone doesn't decide to crap its' shorts in the middle of that update. And after that, one more OTA (July 2010) to put it back to "current" stock status.

But as I said, if you think your phone has bad hardware and could fail at any moment, doing a lot of flashing just increases the chances that you will have a disaster right in the middle of flashing. Flashing the Leak-V3 ROM takes about 5 minutes including the first boot; but applying the 1.5 -> 2.1 OTA takes considerably longer - it goes in and manually patches 600+ files. It burns less than 100 MB to the phone, but it spends a lot of time running when it does so.

I don't know that makes me feel any better. If it is crashing with 1.5 on it, it is damaged goods.

bftb0