n1ghtwish said:
does the downgrade use the recovery?? if not, wouldn't he be able to upgrade to 2.1 root again, delete the recovery through ADB, then follow the downgrade method again???
There's lots of ways to skin this cat, but all methods either need to use Amon_RA's recovery, OR have the S-OFF (aka "root") bootloader on the phone. So, yes - if he was worried about being "pristine 1.5 (1.17.605.1)", then he would need to re-root. If I was in his shoes and wanted to do that, I would:
1) Use "Toastcfh"'s battery pull trick with the root-ROM to
only install the S-OFF bootloader. This would leave his stock 1.5 intact, but have both the non-factory bootloader and recovery installed. Then,
2) Manually use fastboot mode to flash the recovery partition back to the 1.17.605.1 "factory" state, and finally
3) Manually use fastboot mode to flash the HBOOT image (or bootloader, or SPL, or whatever you want to call it) back to the "factory" 1.17.605.1 state. This should produce a "near factory" phone. (I have some suspicions that the NVRAM - not the flash - gets modified during the MRx/leak installs, and
none of the recovery methods deal with this at all)
I'm not really desperate to get rid of the recovery image, I would just like everything to be kosher with the phone once the OTA 2.1 update comes around so it can be legitimate.
If I were a betting man, I would bet that the OTA install process does not inspect the contents of the recovery partition - it simply over-writes it. That's my guess, but I don't know that for a fact.
eu1
PS. I would also bet that within a few days after the OTA, there will be a root ROM sort of like what jcase produced when leak-v3 came out: mostly identical to the factory code, but with root thrown in (and preserving the S-OFF bootloader, too). Your call - but if you've already been root, why give it up? You'll be very likely to get all of the new software that's in the OTA - but with root, too.
Just saying - but it's your call.