-
After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.
Root [HOW TO](gaining root)unlock,downgrade,and achieve s-off with htcDev
- Thread starter scotty85
- Start date
-
- Tags
- htc droid incredible
cmlusco
Member
For anyone having issues with the stock 4.08.605.15 odexed rom linked in step 8, it has been fixed. I messed up the updater script when updating for TWRP.
cachemunny
Lurker
I was able to flash the recovery perfectly fine... but I can't actually get into recovery...
My cmd prompt looks like this
c:\miniadb_inc>md5sums recovery-clockwork-5.0.2.0-inc.img
MD5sums 1.2 freeware for Win9x/ME/NT/2000/XP+
Copyright (C) 2001-2005 Jem Berkes - [Link removed for posting purposes]
Type md5sums -h for help
[Path] / filename MD5 sum
-------------------------------------------------------------------------------
[c:\miniadb_inc\]
recovery-clockwork-5.0.2.0-inc.img ea382ca5809cb872d0582aa22741d592
c:\miniadb_inc>adb reboot bootloader
error: device not found
c:\miniadb_inc>adb reboot bootloader
c:\miniadb_inc>fastboot devices
HT18LMA06387 fastboot
c:\miniadb_inc>fastboot flash recovery recovery-clockwork-5.0.2.0-inc.img
sending 'recovery' (3064 KB)... OKAY [ 0.965s]
writing 'recovery'... OKAY [ 0.847s]
finished. total time: 1.814s
c:\miniadb_inc>fastboot reboot
rebooting...
finished. total time: 0.225s
but whenever i try to get into recovery i just get the HTC logo. I let it sit for a good 10 minutes but nothing has happened. I also tried adb reboot recovery but I got the same result: the HTC logo with no CWM recovery followed. So, I'm stuck not able to get into recovery to flash the SU zip
My cmd prompt looks like this
c:\miniadb_inc>md5sums recovery-clockwork-5.0.2.0-inc.img
MD5sums 1.2 freeware for Win9x/ME/NT/2000/XP+
Copyright (C) 2001-2005 Jem Berkes - [Link removed for posting purposes]
Type md5sums -h for help
[Path] / filename MD5 sum
-------------------------------------------------------------------------------
[c:\miniadb_inc\]
recovery-clockwork-5.0.2.0-inc.img ea382ca5809cb872d0582aa22741d592
c:\miniadb_inc>adb reboot bootloader
error: device not found
c:\miniadb_inc>adb reboot bootloader
c:\miniadb_inc>fastboot devices
HT18LMA06387 fastboot
c:\miniadb_inc>fastboot flash recovery recovery-clockwork-5.0.2.0-inc.img
sending 'recovery' (3064 KB)... OKAY [ 0.965s]
writing 'recovery'... OKAY [ 0.847s]
finished. total time: 1.814s
c:\miniadb_inc>fastboot reboot
rebooting...
finished. total time: 0.225s
but whenever i try to get into recovery i just get the HTC logo. I let it sit for a good 10 minutes but nothing has happened. I also tried adb reboot recovery but I got the same result: the HTC logo with no CWM recovery followed. So, I'm stuck not able to get into recovery to flash the SU zip
cmlusco
Member
Do " fastboot erase recovery " first then " fastboot flash recovery recovery.img " or what ever your img is named.
iowabowtech
root@android:/ #
Good to see you around man. I've bumped into a thread or 2 with your name in it throughout my travels.
sdrawkcab25
Extreme Android User
also... make sure you have an original droid incredible,and not an incredible 2 or incredible 4g
^^^ your fastboot device looks like an incredible 2, not an original Incredible
cmlusco
Member
Good to see you around man. I've bumped into a thread or 2 with your name in it throughout my travels.
You too, its been awile. I didnt even notice that he has an inc2. Oops
skelterhelter
Lurker
hi. I followed your guide up to step three were i have to put the superuser on the sd card. when i plug my phone into the computer, running windows xp, it says removable drives e,d anf f. all of them say insert something into this drive and i cant put superuser onto the phone. Any advice?
cmlusco
Member
Did you put the phone in disk drive mode? You can do it from the notification bar or from menu - settings - connect to pc - default connection type.
difinka2
Newbie
Check this out Scotty85. I actually recognize that issue! Me, the girl who knew too little! Kewl! That is as far as that goes! That's like stalling the dragster once you've left the line!!!
I have had the low space issue with plenty of space remaining for a minimum of twice and I do believe I have had it happen more than two times! Fixed by someone who doesn't live here anymore. :->
I have had the low space issue with plenty of space remaining for a minimum of twice and I do believe I have had it happen more than two times! Fixed by someone who doesn't live here anymore. :->
Hello all. I have just acquired a dinc 2.3.4 and I was wondering if I should unlock and root it before I activate it?
I am on a droid 3 right now but I am not happy with it. I am on vzw prepaid with unlimited 3g data so my phone selection is limited. I had the droid X before but the battery finally died. The X had less problems and way better wifi tethering. I rooted my friends froyo dinc and seem to remember it having a strong tether signal as well....maybe it was froyo lol.
I am on a droid 3 right now but I am not happy with it. I am on vzw prepaid with unlimited 3g data so my phone selection is limited. I had the droid X before but the battery finally died. The X had less problems and way better wifi tethering. I rooted my friends froyo dinc and seem to remember it having a strong tether signal as well....maybe it was froyo lol.
sdrawkcab25
Extreme Android User
Doesn't matter much if it's active or not first
but this rooting process will wipe the phone, so just don't set up any apps or customize the phone n any way or you'll hav to redo it.THANK YOU scotty85 for this detailed guide for rooting. I'm totally new, and so I proceeded very cautiously, but I rooted, thanks to you!
I had trouble with the final step, updating the hboot, radio, and going back to GB with the link you had.
I am on radio 2.15.10.12.20, and I can't tell if that's the one I should be on (latest one). I went to that web site that lists the lastest radios, and mine isn't even listed. I tried putting your radio file on the phone with the adb/fastboot commands exactly per your instructions, and so I didn't rename the file, just left it at the long name.zip. Is that OK?
When trying to install the stock ROM in the last step, it failed with the same problem quoted here. cmlusco, perhaps it's not all the way fixed? IDK. I installed Touch of Blue instead, but would have been more comfortable if the 'stock' ROM had worked.
Also, after installing the Touch of Blue, I can't get my phone into hboot anymore. I hold down the <volume down> button and the power button, like I did many many times before, but I get nothing. When I let go of the volume button, it just does the regular boot. Any hints?
I am rooted, unlocked, s-off, though. Yay!
Sorry for the long post. Lots of questions for my first experience!
cmlusco
Member
THANK YOU scotty85 for this detailed guide for rooting. I'm totally new, and so I proceeded very cautiously, but I rooted, thanks to you!
I had trouble with the final step, updating the hboot, radio, and going back to GB with the link you had.
I am on radio 2.15.10.12.20, and I can't tell if that's the one I should be on (latest one). I went to that web site that lists the lastest radios, and mine isn't even listed. I tried putting your radio file on the phone with the adb/fastboot commands exactly per your instructions, and so I didn't rename the file, just left it at the long name.zip. Is that OK?
When trying to install the stock ROM in the last step, it failed with the same problem quoted here. cmlusco, perhaps it's not all the way fixed? IDK. I installed Touch of Blue instead, but would have been more comfortable if the 'stock' ROM had worked.
Also, after installing the Touch of Blue, I can't get my phone into hboot anymore. I hold down the button and the power button, like I did many many times before, but I get nothing. When I let go of the volume button, it just does the regular boot. Any hints?
I am rooted, unlocked, s-off, though. Yay!
Sorry for the long post. Lots of questions for my first experience!
What issues did you have trying to flash the radio and hboot? Any specific errors?
2.15.10.12.20 is the newest radio. If using the mini_adb way of flashing, it should not matter what its named. It really is easier just to flash them thru hboot though. Just take the file named exactly PB31IMG.zip and put it on your sdcard in no folders. Then boot to hboot. Hboot should find the file and promt you to press vol up to install.
I just tried both the odexed and deodexed versions of my stock rom and they both flashed fine for me. Try redownloading it again.
To get to hboot from TOB (or any stock GB rom) you need to first go to menu - settings - applications, and uncheck fast boot. If you like the phone booting up faster, you can leave fast boot checked. But you will need to pull the battery and then reinsert to get vol down and power to take you to hboot.
Radio: If I'm on the latest radio, then I"m good. Based on the name of the file, I thought the radio was 4.08.605.15. From another post, I guess that's the build number for the file, not the radio number. Little confusing, but I'm good.
cmlusco, yesterday I downloaded your stock rom, checked the md5sums, and got that Status 7 error both times I tried to install it. Has the file changed since yesterday? If I would try downloading it again today, what would be the difference? Anyway, I did install Touch of Blue instead, so then I think I"m set right now. I do have a couple questions about TOB, but I will post them on the xda developer site for TOB, to not get off topic here.
Thanks for the info about unchecking fastboot. I would not have figured that out.
Thanks!
cmlusco
Member
cmlusco, are your updated roms at the same links? if there are new links,i will update the OP
They are at the same links, should be no need to update.
Hello again,
I have had time to use my unlocked dinc for a bit now. All was going well but I'm running into some issues and don't know how to troubleshoot them. I thought I'd post an update here since I followed this howto by scotty85 and cmlusco seems to be weighing in a bit here also and some of my issues may be related to Touch of Blue.
A couple of things started to act up, like when typing in this quick reply box to post, my cursor would just start flying across the box. Couldn't type after that. May have had something to do with my connection at the time....not sure. Then I started having problems listening to podcast and listening to mp3's on the phone. Not streaming but songs on the sdcard and podcast that were downloaded. They would get to a certain point and just stop. I would restart the phone but it wouldn't help. The next day I could listen, no problem.
The next thing I've had happen, just last night is that I got a alert to download an OTA update, (4.08.605.19). Since I have Touch of Blue flashed I didn't think I would get hit with those notices anymore, so I checked to see that I was still unlocked/Soff, which I am. So I was wondering if anyone has experienced any of these things or has any thoughts. It seems like it might benefit someone out there, as this thread has so much already.
fewjr
I have had time to use my unlocked dinc for a bit now. All was going well but I'm running into some issues and don't know how to troubleshoot them. I thought I'd post an update here since I followed this howto by scotty85 and cmlusco seems to be weighing in a bit here also and some of my issues may be related to Touch of Blue.
A couple of things started to act up, like when typing in this quick reply box to post, my cursor would just start flying across the box. Couldn't type after that. May have had something to do with my connection at the time....not sure. Then I started having problems listening to podcast and listening to mp3's on the phone. Not streaming but songs on the sdcard and podcast that were downloaded. They would get to a certain point and just stop. I would restart the phone but it wouldn't help. The next day I could listen, no problem.
The next thing I've had happen, just last night is that I got a alert to download an OTA update, (4.08.605.19). Since I have Touch of Blue flashed I didn't think I would get hit with those notices anymore, so I checked to see that I was still unlocked/Soff, which I am. So I was wondering if anyone has experienced any of these things or has any thoughts. It seems like it might benefit someone out there, as this thread has so much already.
fewjr
scotty85
Extreme Android User
That's unusual about the ota notification... A custom Rom will usually have the files that check for the ota remmoved. That,combined with the issues your having,it may be time to give another Rom a whirl. Or,you might search the touch of blue thread and see if anyone else is having those issues,and what they did to fix them. The inc is suppose to recieve a small ota to address "random reboots" ,so that is prolly what your phone wants to download.very soon the roms dev should hve those updates cooked into touch of blue,so you could flash the new version and give it another shot.
Unfortunately,I can't be of much help with Rom issues,it has been a long time since this device was my daily driver. You'll prolly get more info about Roms by searching/posting in the forum
Scotty,
my Incredible has been working GREAT since the root back in Sept 2012. However, I recently started getting the OTA update nag notifications. Apparently, the update was automatically downloaded and is just waiting to be installed [i think b/c i powered off/on my phone while taking a trip on an airplane... i rarely power off my phone otherwise]
I am happy with the phone as is. I see that this OTA has caused issues as posted by others in this thread.
My question: Is there anyway to do any/all of these:
-turn off the install update notices
-delete the downloaded update from my phone so it cannot be accidentally installed
-stop further automatic OTA downloads
many thanks again,
-mark
my Incredible has been working GREAT since the root back in Sept 2012. However, I recently started getting the OTA update nag notifications. Apparently, the update was automatically downloaded and is just waiting to be installed [i think b/c i powered off/on my phone while taking a trip on an airplane... i rarely power off my phone otherwise]
I am happy with the phone as is. I see that this OTA has caused issues as posted by others in this thread.
My question: Is there anyway to do any/all of these:
-turn off the install update notices
-delete the downloaded update from my phone so it cannot be accidentally installed
-stop further automatic OTA downloads
many thanks again,
-mark
thanks. will this work even if my phone specs are not the same as the original poster?
mine are [differences in BOLD]
Android Ver. 2.3.4
Baseband Ver. 2.15.10.12.20
Kernel Ver. 2.6.35.13-g22d3486
Build No.4.08-605.15 CL389630 release-keys
Software No. 4.08.605.15 71ORD
Browser Ver. WebKit/533.1
i assume so, since the process is "fooling" the build to think it is the new OTA update by changing one line in the build [i really don't have any intimate knowledge of what i am typing, but i gleaned these words from the cited post]