My droid audio port has gone kaputz again (droid #3), which means time to unroot! No biggie, I've done this twice before without a problem, right?
Here's where I'm at:
Started on CM with Clockwork Recovery. Stupidly thought 'back to stock, unrooted option' in Rom manager would get me back to stock, unrooted.
Ended up on stock 2.2.1, stock recovery, but still having su icon. Except that Rom Manager can no longer gain su permissions (other root requiring programs like Cachemate still work.) Someone suggested trying z4root. It crashes as soon as it tries to acquire shell... So it's acting sort of rooted, sort of not.
I try flashing new recovery with RSD Lite. The process fails (recovery file fails to flash.) I try flashing a new rom: FRG22D file keeps the run button greyed out. I try various update.zips directly on the droid but of course these fail because I'm running stock recovery.
Okay, so I really need to get a new recovery image. Back to Rsd Lite, and I try moving the sprecovery sbf to different folders since I understand it can be finnicky...new problem: Rsd will no longer detect my phone! :icon_eek: It did 12 hours ago no problem. I've tried about thirty different iterations, rebooting everything and nothing has worked. Rsd has decided my phone's drama is too much for it.
So here's the thing...When I first rooted my phone everything had to be done via adb shell, but I can no longer find the commands and file now that Rsd seems to have gone de rigueur. Does anyone either know of a way I can trick Rsd into noticing my phone again or have a walkthrough of the old school recovery flashing method with the correct files?
Another question...for warranty purposes, would it be possible to just delete the superuser.apk out of /system? For all other extents and purposes it's currently stock (I got an OTA update after installing 2.2 for instance.)
Thanks for any thoughts, suggestions or words of encouragement!
Here's where I'm at:
Started on CM with Clockwork Recovery. Stupidly thought 'back to stock, unrooted option' in Rom manager would get me back to stock, unrooted.
Ended up on stock 2.2.1, stock recovery, but still having su icon. Except that Rom Manager can no longer gain su permissions (other root requiring programs like Cachemate still work.) Someone suggested trying z4root. It crashes as soon as it tries to acquire shell... So it's acting sort of rooted, sort of not.
I try flashing new recovery with RSD Lite. The process fails (recovery file fails to flash.) I try flashing a new rom: FRG22D file keeps the run button greyed out. I try various update.zips directly on the droid but of course these fail because I'm running stock recovery.
Okay, so I really need to get a new recovery image. Back to Rsd Lite, and I try moving the sprecovery sbf to different folders since I understand it can be finnicky...new problem: Rsd will no longer detect my phone! :icon_eek: It did 12 hours ago no problem. I've tried about thirty different iterations, rebooting everything and nothing has worked. Rsd has decided my phone's drama is too much for it.
So here's the thing...When I first rooted my phone everything had to be done via adb shell, but I can no longer find the commands and file now that Rsd seems to have gone de rigueur. Does anyone either know of a way I can trick Rsd into noticing my phone again or have a walkthrough of the old school recovery flashing method with the correct files?
Another question...for warranty purposes, would it be possible to just delete the superuser.apk out of /system? For all other extents and purposes it's currently stock (I got an OTA update after installing 2.2 for instance.)
Thanks for any thoughts, suggestions or words of encouragement!
