1. Greg Goodson's Avatar
    i have an old Verizon HTC Droid Incredible 2 that i'm trying to root just to learn the ropes .. i dont use it anymore so its just a guinea pig for now .. I was able to unlock the phone, install the Clockwork Mod Recovery, flash it, and install superuser .. however the superuser updated but didn't get admin rights. i can still boot the phone to recovery mode but after trying to install a few different roms, the phone freezes at the white htc screen .. i have let it run for 10, 15, even 20 minutes but never gets past the white screen. currently when i hold volume down and power and boot to recovery i see this: ****UNLOCKED**** / VIVO_W XB SHIP S-ON RL / RADIO-1.09.01.0312 / eMMC-boot / July 18 2011, 12:39:36 .. the last time it loaded was with version 2.3.4 .. i am able to clear cache, wipe data, ect and the rom zip installs always work, but once i reboot after the install, it never gets past the white htc screen. am i missing a step or done something to break it for good. any help would be greatly appreciated. thanks!
    08-23-2013 02:09 PM
  2. Golfdriver97's Avatar
    i have an old Verizon HTC Droid Incredible 2 that i'm trying to root just to learn the ropes .. i dont use it anymore so its just a guinea pig for now .. I was able to unlock the phone, install the Clockwork Mod Recovery, flash it, and install superuser .. however the superuser updated but didn't get admin rights. i can still boot the phone to recovery mode but after trying to install a few different roms, the phone freezes at the white htc screen .. i have let it run for 10, 15, even 20 minutes but never gets past the white screen. currently when i hold volume down and power and boot to recovery i see this: ****UNLOCKED**** / VIVO_W XB SHIP S-ON RL / RADIO-1.09.01.0312 / eMMC-boot / July 18 2011, 12:39:36 .. the last time it loaded was with version 2.3.4 .. i am able to clear cache, wipe data, ect and the rom zip installs always work, but once i reboot after the install, it never gets past the white htc screen. am i missing a step or done something to break it for good. any help would be greatly appreciated. thanks!
    I don't know for sure, but I can try to get some help.
    08-23-2013 03:45 PM
  3. Golfdriver97's Avatar
    Try to reflash the stock ROM, and then redownload the ROM, and reflash. GO through everything again, wipe cache, data, dalvik.
    08-23-2013 03:48 PM
  4. Greg Goodson's Avatar
    thanks for reply .. will try again .. but could you or anyone possibly confirm the steps to recover/flash/install rom for me ? still very new to this and seems each video or set of instructions is different .. i just have a terrible feeling i am missing a step or not doing something in correct order .. going to try to install the stripped factory setting rom called 6.01.605.05_VZW__OTA-stripped-odex.zip .. thanks again!
    08-24-2013 09:32 AM
  5. Golfdriver97's Avatar
    thanks for reply .. will try again .. but could you or anyone possibly confirm the steps to recover/flash/install rom for me ? still very new to this and seems each video or set of instructions is different .. i just have a terrible feeling i am missing a step or not doing something in correct order .. going to try to install the stripped factory setting rom called 6.01.605.05_VZW__OTA-stripped-odex.zip .. thanks again!
    Where are you getting instructions?

    Sent from a SlimROM S3.
    08-24-2013 10:20 AM
  6. Greg Goodson's Avatar
    just different sites from searching google ... some step by step print, some are you tube videos. i was able to boot up with the rom i listed before, but my wifi is broken from that one
    08-24-2013 10:42 AM
  7. Golfdriver97's Avatar
    just different sites from searching google ... some step by step print, some are you tube videos. i was able to boot up with the rom i listed before, but my wifi is broken from that one
    Do the YouTube videos have the same steps?

    Sent from a SlimROM S3.
    08-24-2013 11:36 AM
  8. Greg Goodson's Avatar
    breakthrough ! because my phone has S-ON .. after i install the rom .. have to go back and drop the boot.img file in the fastboot folder on the computer, and flash the boot.img .. once i did that, i was able to load the Cyanogenmod that i had installed before with no success .. i assume most roms will come with a boot.img if you extract all of the files
    08-24-2013 11:41 AM
  9. Golfdriver97's Avatar
    breakthrough ! because my phone has S-ON .. after i install the rom .. have to go back and drop the boot.img file in the fastboot folder on the computer, and flash the boot.img .. once i did that, i was able to load the Cyanogenmod that i had installed before with no success .. i assume most roms will come with a boot.img if you extract all of the files
    All of my rooting and flashing experience us with Samsungs. There are less steps to unlock the boot loader and obtain root.
    So in short, I don't know. I would guess yes.

    Sent from a SlimROM S3.
    08-24-2013 01:01 PM
  10. Scott Kenyon's Avatar
    Generally this is how it works:

    • Download all of the files necessary
    • Unlock the bootloader via HTC Dev if possible, if not with a workaround
    • Push and flash your recovery of choice, I like CWM better but am using TWRP as it's mostly foolproof
    • Push flashable Superuser or SuperSU to the phone and flash it
    • Reboot and make sure everything is working as it should
    • Copy the rom file to the root of your sdcard directory on your device
    • Reboot recovery, wipe cache/dalvik/factory reset
    • Flash the rom from sdcard
    • Rewipe cache/dalvik/reset
    • Boot into your new firmware


    I use adb for most everything when it comes to modifying devices. It's part of the SDK. You can download the whole SDK for free at developer.android.com. The one click tools are great, but you don't learn anything by using them. Jerry had posted a great mini-adb-tutorial to the blog last month that you should read. Knowing how to utilize adb can help you save your devices.

    [TIP]Always always always keep a copy of the correct ruu file for your HTC device on your computer. Running the ruu in windows with your phone plugged in will restore it to factory without you having to do anything else.[/TIP]

    [TIP]Always keep USB debugging ENABLED on your device at all times. This will always allow you to interface with your phone through the adb console, even if you cannot get into the OS. So long as you can get into recovery, you'll have a way to fix it.[/TIP]

    [TIP]Ensure your have the correct version of a rom for your device. An AT&T HTC rom will not work on a Verizon device and vice versa.[/TIP]

    If you have any specific questions, post them on in here. I'll be subscribed and will respond when I can.
    Golfdriver97 likes this.
    08-24-2013 01:38 PM
  11. Greg Goodson's Avatar
    my "real" phone is a Samsung Galaxy S3 ... was just using my old droid to kind of get the hang of what the rooting process is all about. still leary of creating a $200 paper weight with my Samsung !!... any sites you would recommend to walk through the process ? Thanks again for your help !
    08-24-2013 02:03 PM
  12. Golfdriver97's Avatar
    my "real" phone is a Samsung Galaxy S3 ... was just using my old droid to kind of get the hang of what the rooting process is all about. still leary of creating a $200 paper weight with my Samsung !!... any sites you would recommend to walk through the process ? Thanks again for your help !
    Root galaxys3. Pretty good videos of how to root and descriptives of ROMs themselves.

    Sent from a SlimROM S3.
    08-24-2013 02:44 PM
  13. Greg Goodson's Avatar
    Thanks Scott .. i do have the adb file and the sdk for htc and have been using CWM recovery.. what is the ruu file .. is there one specific for each rom or is there just one for each type of phone that is the stock operating system
    08-24-2013 02:48 PM
  14. gollum18's Avatar
    Thanks Scott .. i do have the adb file and the sdk for htc and have been using CWM recovery.. what is the ruu file .. is there one specific for each rom or is there just one for each type of phone that is the stock operating system
    They are device specific. And are named based in the device baseband and codename. Like the evo4glte, its ruus have "jewel" appended to it.

    Sent from my SPH-L710 using Tapatalk 2
    Golfdriver97 and Greg Goodson like this.
    08-24-2013 07:59 PM
  15. Scott Kenyon's Avatar
    They are device specific. And are named based in the device baseband and codename. Like the evo4glte, its ruus have "jewel" appended to it.

    Sent from my SPH-L710 using Tapatalk 2
    Good reply!

    To expand upon this, ruus are device, carrier, baseband and version specific. It should also be noted ruu is a HTC specific thing. You won't find one for any other brand.

    Sent from my HTC One using Mobile Nations mobile app
    08-25-2013 10:17 PM

Similar Threads

  1. Replies: 108
    Last Post: 09-01-2013, 12:04 PM
  2. Can't use data in Russia, 3G or edge.
    By cgordey in forum Samsung Galaxy Ace
    Replies: 4
    Last Post: 08-25-2013, 10:52 PM
  3. Nexus 4 Android OS-4.3 is consuming almost 90% of Battery
    By Jayavel Bharathi in forum Google Nexus 4
    Replies: 10
    Last Post: 08-25-2013, 08:46 PM
  4. Are there any phone GPS comparisons anywhere?
    By Just_Some_Nobody in forum General News & Discussion
    Replies: 0
    Last Post: 08-23-2013, 11:40 AM
  5. Ghost Armor or Invisible Shield
    By DOOG9517 in forum Motorola Droid MAXX
    Replies: 4
    Last Post: 08-23-2013, 11:39 AM
LINK TO POST COPIED TO CLIPBOARD