1. Check out our companion app, Forums for Android! Download from Google Play

Root For those having trouble getting into recovery mode

Discussion in 'Android Devices' started by computerpro3, Jun 15, 2010.

  1. computerpro3

    computerpro3 Well-Known Member
    Thread Starter

    Apr 22, 2010
    Perhaps try this - this is the only repeatable way on my phone. This is assuming you have the required files and SDK kit already set up and are just having trouble entering recovery mode.

    Go to your C:/sdk/usb_driver folder and open android_winusb.inf.

    As other instructions have mentioned, copy and paste these lines twice total - once under [Google.NTx86] and once under [Google.NTamd64]:

    ;HTC Incredible
    %SingleAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C9E
    %CompositeAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C9E&MI_01
    %SingleBootLoaderInterface% = USB_Install, USB\VID_0BB4&PID_0C94

    Start with your phone off but unplugged. Boot the phone while holding the optical trackpad. Go to device manager at your computer. You should see the ADB interface listed near the top of your devices. Look back at your phone, hit the volume down arrow to select recovery and then hit the power button.

    Now here, what normally happened for me (and those having trouble accessing recovery mode) is that the ADB would dissapear from device manager after 20 seconds and something called Android 1.0 would pop up. The computer could not access the proper drivers for this and hence ADB can not communicate with the phone. Once you see this Anroid 1.0 pop up in device manager, right click on it and hit update drivers. Don't do automatic update - point your computer to C:/sdk/usb_driver folder. Hit okay and it should automatically recognize the proper driver and install it. You know you are golden when Android 1.0 is replaced with something like HTC Bootloader Interface in device manager.

    In short, you are:

    1. Loading the phone into recovery mode without drivers installed to force the error to pop up in device manager
    2. Install the modified driver .inf file WHILE THE PHONE IS IN THE "RECOVERY" MODE

    Next, unplug the phone and pull the battery. Replace the battery and boot the phone as if you were going to use it normally. Once you reach your home screen, power down the phone normally - DO NOT PULL THE BATTERY. Once the phone has shut down, power it up again as if you were going to use it normally. However, this time in the split second between the HTC Quietly Brilliant logo and the Verizon logo, pull the battery.

    This was the critical step for me. If I pull the battery during the first HTC logo or after the phone boots, recovery mode will never be activated. IF I wait until that second between the HTC Quietly Brilliant Logo and the Verizon logo, it works 100% of the time. I suspect this is because the phone is detecting a failed boot and somehow enabling recovery mode.

    After pulling the battery, start the phone while holding down the optical trackpad. Hit the volume down, and select recovery. This time, your computer will recognize the drivers after a few seconds and won't give you the Android 1.0 error.

    You should not be able to push the files and payload and achieve root.

    In summation, there are two absolutely critical components that are neccessary for me - installing the modified drivers through device manager while the phone is in the bootloader, and only trying to launch recovery mode after pulling the battery to simulate boot failure in between the Quietly Brilliant and Verizon logos.

    I'd be interested to know if this is just my device or if this works for others having trouble achieving recovery mode as well.


  2. r1dePrkCty

    r1dePrkCty Well-Known Member

    Mar 14, 2010
    Well you definitely fixed me driver problems as now i am seeing htc bootloader interface right before i hit recovery, but after that... nothing. Thanks for the help tho
  3. shoebox

    shoebox New Member

    Jul 1, 2010
    To get this working I run loop.bat, then with the phone usb unplugged I boot into the bootloader and wait a few seconds for the bootloader (on phone) to get passed the files not found error (it's looking for files on the sdcard).

    Once the bootloader menu is working (when you can move the selector up and down with your volume buttons), I then I plug the usb cable into phone and wait for windows to recognize it. It usually shows up as "Android 1.0" device.

    At that point, I uninstall the "Android 1.0" device (or whatever device shows up). At this point check your loop.bat to see if you are getting the new error yet. If not, sometimes I have to reinstall the android_winusb.inf (sometimes not).

    When I start getting the expected error in loop.bat indicating I can proceed to root my phone. I select the recovery mode option on the phone.

    I never have to remove the sd card when doing this method.
  4. welbinator

    welbinator Well-Known Member

    Jul 1, 2010
    As other instructions have mentioned, copy and paste these lines twice total - once under [Google.NTx86] and once under [Google.NTamd64]:

    I'm a noob and have no idea what that means.

    I recently rooted my phone, and it seems to be a good root, I've been wirelessly tethering and what-not. However, when I try to go into recovery mode, it gives me the picture of an incredible with a red question mark above it. then turns off after a few seconds. i turn the phone on normally and it works fine and everything I just can't get into recovery mode, whether I try it from rom manager ClockworkMod or the volume down + power button method.

    my friend is trying to help me install binny's ROM which is when this problem surfaced.
  5. outsid0r

    outsid0r Active Member

    Jul 4, 2010
    Milwaukee, WI
    when you get to that screen you need to hit the volume up and power button to get past and see the recovery screen, this wouldve needed to be done for your root as well, all part of the instructions.
  6. ktan91

    ktan91 Active Member

    Jul 6, 2010
    Ran into a problem: once I'm in recovery the previously present Android Bootloader Interface disappears as it should, however, once in recovery nothing pops up. Any ideas as to why this is and how to fix it?
  7. welbinator

    welbinator Well-Known Member

    Jul 1, 2010
    I did that and it didn't really go into recovery mode, instead it gave me somethign about failed to install pacakaged, rebooting...and it rebooted. (this was after trying to isntall binny's ROM with rom manager)
  8. welbinator

    welbinator Well-Known Member

    Jul 1, 2010
    here is the process I went through:

    open rom manager
    choose download rom
    download rom
    choose install rom from sd card
    choose the ROM
    select Backup Existing ROM and Wipe Data and Cache
    I get the green exclamation point icon
    then I get the red question mark icon
    I press up arrow + power
    This is what I get:
    finding update pacakge...
    opening update packages...
    verifying update pacgkaes...
    E:failed to verify whole file
    E:signature verification failed
    installation aborted.
    E: failed to install package...

    ....and it reboots. any suggestions? was there anything I was supposed to do after the 10 minute video?
  9. welbinator

    welbinator Well-Known Member

    Jul 1, 2010

Share This Page