Problems Unrooting!! DESPERATE FOR HELP


Last Updated:

  1. Mrkarias

    Mrkarias Member This Topic's Starter

    Joined:
    May 21, 2010
    Messages:
    20
    Likes Received:
    0
    Ok Android Forums, Ive used all my info for Root from this website and this website only. all the instructions have been extremely precise. :)

    So I rooted my phone, and now im trying to unroot to get the OTA 2.1.
    I followed the Unzipme instructions and I went through the downgrade and the downgrade went very smoothly. But as soon as I tried to Flash the Recovery Image and the Hboot, I keep getting "error: cannot load recovery.img"

    What am i not doing right? I have rooted the phone all over again and downgraded again and ONLY tried the FASTBOOT FLASH RECOVERY RECOVERY.img and it still kept getting me the ""error: cannot load recovery.img" after that i didnt try the Hboot

    I turned the phone back on and it tried to do the OTA update and it seemed to be working and it even downloaded successfully as soon as it tried to reboot and install it gives me this error
    E: No signature required (690 Files)
    E: Verification failed

    I am desperate for some help...

    Thank you all in advance
     

    Advertisement
  2. erisuser1

    erisuser1 Well-Known Member

    Joined:
    Nov 11, 2009
    Messages:
    1,644
    Likes Received:
    759

    The first error that you reported looks like a simple "file not found" error: the "fastboot" program on your PC simply did not find a file named "RECOVERY.img" in the current directory.

    The rest of the instructions will not work if you don't complete those first steps. In particular, the second error that you reported, "No signature required (690 Files)" was reported to you by Amon_RA's recovery boot, which does not process the HTC OTA .zip files correctly - you have to restore the factory "recovery.img" file, because it is the recovery boot which actually installs the HTC/Verizon OTA.

    Now, I have bad news and good news for you. First, the good news: I went through the exact steps you are reporting last night (for fun, to see how it worked). So, I am sure of multiple ways to fix it up. The bad news is only minor really - if you reboot into 1.5 and try to check for system updates, your phone will tell you that you are up to date - even though the install failed.

    That means you should start the 1.5 downgrade process over. It will work, because you still have both Amon_RA's recovery on the phone (boot up with Vol-Up + End), and the S-OFF bootloader.

    But, you can not skip steps in the process and get the right result. All steps need to work correctly - there is no point in skipping over stuff that mysteriously fails.

    Let me know if you want more instructions

    eu1
     
    Mrkarias likes this.
  3. Mrkarias

    Mrkarias Member This Topic's Starter

    Joined:
    May 21, 2010
    Messages:
    20
    Likes Received:
    0
    YES PLEASE Can you provide detailed instructions. Im sorry I feel really dumb But i know someone like yourself can ease the process for me, im just trying to get it back to 100% stock.

    Thanks again for all your help.
     
  4. Mrkarias

    Mrkarias Member This Topic's Starter

    Joined:
    May 21, 2010
    Messages:
    20
    Likes Received:
    0
    Oh Sorry, but you mentioned that the first error was due to the fact that it didnt find a "recovery.img" on my directory right?
    But I am certain I pasted that recovery.img on my Sdk tools directory.
    This is where it's supposed to go right which means my command line sshould read like this or at least the last part
    android-sdk-windows\tools\fastboot flash recovery recovery.img ??????? right?

    Cause I can see the recovery file on my tools directory...So i was really confused

    ErisUser1, thanks for your patience man....
     
  5. erisuser1

    erisuser1 Well-Known Member

    Joined:
    Nov 11, 2009
    Messages:
    1,644
    Likes Received:
    759
    The instructions you are working with are correct.

    Repeat them from the beginning. At the moment, your phone appears to have on it the:

    - S-OFF (or "root") bootloader (hboot*.img)
    - Amon_RA's recovery boot
    - 1.5 release OS

    When you get to the part where you need to use the fastboot command (the phone will have "FASTBOOT USB" displayed), first check to see that you are successfully communicating with the phone from the PC by using the command:

    fastboot devices

    (If you see your device ID - a bunch of letters and digits starting with "HT", followed by "fastboot" on the same line, then you are connected to the phone correctly)

    As I said before, that error message "Cannot load recovery.img" appears to be a simple case of a mis-spelled file name... or you do not have that file in the same directory from where you you are running the fastboot command. That shouldn't be too hard to check for.

    I can't write a novel to cover all possible scenarios - follow the directions (which are correct), and if you encounter an error, stop. Paste the exact (not paraphrased) error message into a reply here.

    eu1
     
    Mrkarias likes this.
  6. erisuser1

    erisuser1 Well-Known Member

    Joined:
    Nov 11, 2009
    Messages:
    1,644
    Likes Received:
    759
    OK, then perhaps the PC is not communicating with the phone. Check with the "fastboot devices" command.

    Well, it needs to be in whatever directory is your current directory. If you "CD \android-sdk-windows\tools\" before you issue the fastboot command, then yes, that should be fine. You can certainly check to see it is there by typing

    DIR recovery.img

    eu1
     
    Mrkarias likes this.
  7. Mrkarias

    Mrkarias Member This Topic's Starter

    Joined:
    May 21, 2010
    Messages:
    20
    Likes Received:
    0
    OK awesome Dude, I will try the steps all over again. Starting from the downgrade.

    Will let you know if I get any more errors..Cross your finger.

    Thanks Again Dude.
     
  8. erisuser1

    erisuser1 Well-Known Member

    Joined:
    Nov 11, 2009
    Messages:
    1,644
    Likes Received:
    759
    BTW, just curious: are you trying to revert to "stock" so you can sell or return the phone?

    If you just want something which is extremely close to the 2.1 OTA (factory) software, you could just load jcase's Plain Jane 2.1 ROM

    eu1
     
    Mrkarias likes this.
  9. erisuser1

    erisuser1 Well-Known Member

    Joined:
    Nov 11, 2009
    Messages:
    1,644
    Likes Received:
    759
    Standing by.
     
    Mrkarias likes this.
  10. Mrkarias

    Mrkarias Member This Topic's Starter

    Joined:
    May 21, 2010
    Messages:
    20
    Likes Received:
    0
    Yeah I was hoping to return it and get the HTC Incredible. Im new to this entire ANDROID world...
     
  11. erisuser1

    erisuser1 Well-Known Member

    Joined:
    Nov 11, 2009
    Messages:
    1,644
    Likes Received:
    759
    Progress?

    Have you verified that you can communicate with the phone with either fastboot or adb

    "fastboot devices" (with phone in Fastboot-USB mode), or
    "adb devices" (with phone booted into Amon_RA's recovery)

    ?

    eu1
     
    Mrkarias likes this.
  12. Mrkarias

    Mrkarias Member This Topic's Starter

    Joined:
    May 21, 2010
    Messages:
    20
    Likes Received:
    0
    YES Sir, It communicates fine through Adb just fine (this is after I downgraded again). it shows a "$" ----- is that right?

    Trying fastboot devices now
     
  13. erisuser1

    erisuser1 Well-Known Member

    Joined:
    Nov 11, 2009
    Messages:
    1,644
    Likes Received:
    759
    Just don't re-try the OTA install until you succeed in getting the recovery.img file flashed to the phone.
     
    Mrkarias likes this.
  14. erisuser1

    erisuser1 Well-Known Member

    Joined:
    Nov 11, 2009
    Messages:
    1,644
    Likes Received:
    759
    A lot of folks don't know this, but you can use adb to communicate with Amon_RA's recovery, too. If you were doing that (boot phone with Vol-up + End/Power), you would see a "#" prompt.

    Since you said "$" prompt, I take that to mean that you had the phone booted up. (The restored 1.5 OS is not rooted, so you shouldn't see a root prompt, just the regular "$" prompt). That's OK, but let's stay focused - you probably don't need the regular OS for anything until we are done here.

    eu1
     
    Mrkarias likes this.
  15. Mrkarias

    Mrkarias Member This Topic's Starter

    Joined:
    May 21, 2010
    Messages:
    20
    Likes Received:
    0
    Ok Great! My laptop's battery just died on me..should be home in about 15 mins to try to fastboot devices. I will make sure to flash the recovery and hboot before trying the OTA install.

    As long as fastboot devices seems to work.. and i point the command line to the correct recovery image it should be able to work....Im hoping.

    I plan on staying online here until i get this right today.

    Just dont giveup on me man! HAHA
     
  16. erisuser1

    erisuser1 Well-Known Member

    Joined:
    Nov 11, 2009
    Messages:
    1,644
    Likes Received:
    759
    When you get home,

    0) Check the battery status on your phone - should be better that 40% or more.

    1) Make sure you are doing this with your laptop plugged in. I would feel even safer it the battery in the laptop had a bit of a charge on it, but then what's the chance that the power will go out? :(

    2) Make sure there is no PB00IMG.ZIP file in the root of the SD card; either that or just pull the SD card out of the phone.

    3) Turn the phone off and plug it (USB) into the computer/laptop

    4) Boot the phone by:

    - Press Vol-down + End/Power, (HBOOT mode), then
    - Press Send key (Fastboot Mode)

    You should see "FASTBOOT USB" on the Eris display

    5) On the PC, type "./fastboot devices". Does it look like it is connected? If you don't see a status here indicating you are connected, don't continue - sort out the PC driver issues first.

    6) Now run the fastboot flash commands. You should have put the "recovery.img" and "hboot.nb0" file in your (SDK) tools folder. If you want to be extra-super careful, you should check the md5sum signatures of those files (I honestly don't know what tool Windoze folks use for that, I'm sure something can be found)

    38899da4e5e002e3be22900f5f4eb6f7 hboot.nb0
    71a4b633bdb32de9dcdd8953fef43cdc recovery.img


    7) Try the recovery flash first:

    ./fastboot flash recovery recovery.img

    and finally (ONLY if the above step succeeds!)

    ./fastboot flash hboot hboot.nb0


    eu1
     
    Mrkarias likes this.
  17. Mrkarias

    Mrkarias Member This Topic's Starter

    Joined:
    May 21, 2010
    Messages:
    20
    Likes Received:
    0
    Oh Wow man I actually didnt know that But that's good to know instead of having to boot up to make sure that adb is working. But it shouldnt matter that I booted though right?

    Damn what the HELL would I do without the Pro's?
     
  18. erisuser1

    erisuser1 Well-Known Member

    Joined:
    Nov 11, 2009
    Messages:
    1,644
    Likes Received:
    759
    No it shouldn't matter. Follow my instructions above. I feel the force weakening.
     
    Mrkarias likes this.
  19. Mrkarias

    Mrkarias Member This Topic's Starter

    Joined:
    May 21, 2010
    Messages:
    20
    Likes Received:
    0
    Awesome thanks for your detailed instructions!

    if you can I would appreciate if you check up on this thread and I will let you know if I was successful!
     
  20. Mrkarias

    Mrkarias Member This Topic's Starter

    Joined:
    May 21, 2010
    Messages:
    20
    Likes Received:
    0
    Nah Hell NO Dude THE FORCE IS STILL STRONG with this one!

    I just wanted to make sure i wasn't missing anything. All this process is amking my experience with Adobe Dreamweaver seem like a SINCH!
     
  21. erisuser1

    erisuser1 Well-Known Member

    Joined:
    Nov 11, 2009
    Messages:
    1,644
    Likes Received:
    759
    I want you to do this right now so that I can be done dragging this out. Hope you don't mind.
     
    Mrkarias likes this.
  22. Mrkarias

    Mrkarias Member This Topic's Starter

    Joined:
    May 21, 2010
    Messages:
    20
    Likes Received:
    0
    NOOO!!! Hey ErisUser1....I have no clue what is going on man but i keep getting the same error message "error:recovery.img cannot load recovery.img"

    What the Hell is wrong with my phone. i did everything EXACTly as you mentioned. I even made sure the recovery image was in my directory and there was no mis-spells.

    My HTC Incredible possibility looks slimmer now!
     
  23. erisuser1

    erisuser1 Well-Known Member

    Joined:
    Nov 11, 2009
    Messages:
    1,644
    Likes Received:
    759
    Did the "fastboot devices" command appear to work correctly?

    Did the PC command

    DIR recovery.img

    succeed, or give you an error?
     
    Mrkarias likes this.
  24. Mrkarias

    Mrkarias Member This Topic's Starter

    Joined:
    May 21, 2010
    Messages:
    20
    Likes Received:
    0
    the fastboot devices brought up all those things you said it would. To be honest i didnt try that other DIR recovery.img. would that go into the command file also after the tools directory?
     
  25. erisuser1

    erisuser1 Well-Known Member

    Joined:
    Nov 11, 2009
    Messages:
    1,644
    Likes Received:
    759
    Lookit.

    With my own phone & linux box, I just ran the command

    fastboot flash recovery recovery.img

    But I did something special - I made sure there was no "recovery.img" file in my current directory.

    Guess what error message it gave me?

    Code (Text):
    1. # /android/android-sdk-linux_86/tools/fastboot flash recovery recovery.img
    2. error: cannot load 'recovery.img'
    Now I have pretty much confirmed - after 3 hours - that the problem is exactly what I said it was in my first post.

    Use Windows Explorer or the DIR command to confirm the files are in your folder and named the way you expect them to be!
     
    Mrkarias likes this.

Share This Page

Loading...