• 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

mefnj said:
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]
Click to expand...

yup... should work just fine :)

also,if the dev cooks the updates into the rom youre running,the differences are likely minor enuff that you can do a "dirty flash" overtop of your current rom:
-make a backup(just in case)
-wipe cache
-wipe dalvik
*do NOT wipe data
-flash rom

doing this usually works out fine when flashing the same rom,with only minor updates/changes
 
scotty85 said:
yup... should work just fine :)

also,if the dev cooks the updates into the rom youre running,the differences are likely minor enuff that you can do a "dirty flash" overtop of your current rom:
-make a backup(just in case)
-wipe cache
-wipe dalvik
*do NOT wipe data
-flash rom

doing this usually works out fine when flashing the same rom,with only minor updates/changes
Click to expand...


OK, just a few more clarifications...

-I can just do the edit to the /system/build.prop, and not have to do anything more like flashing a rom, correct?

-before I reboot to recovery, do i need to find and remove the OTA update that the phone already downloaded? i saw a few posts that IF there is an update.zip on the SD card, then booting to recovery could result in the update being installed and/or brick the phone.

-just as a refresher... "boot to recovery" means
1) power down phone and remove battery
2) hold down both power and volume rockers while powering up phone by replacing the battery

is this going to bring up the CW recovery menu, or the default recovery menu?

[i did the battery out/in method the whole time while rooting to power the phone off/on, as it was easy and seemed to worked every time]

thanks again,
-mark
 
mefnj said:
OK, just a few more clarifications...

-I can just do the edit to the /system/build.prop, and not have to do anything more like flashing a rom, correct?
cirrect. that will stop the OTA notifications,but not get you any of the benefits the OTA provides.

-before I reboot to recovery, do i need to find and remove the OTA update that the phone already downloaded? i saw a few posts that IF there is an update.zip on the SD card, then booting to recovery could result in the update being installed and/or brick the phone.
wiping cache and dalvik should remove the OTA from phone memory,but if you do find an update.zip on your sd card,yes,go ahead and delete it :)

-just as a refresher... "boot to recovery" means
1) power down phone and remove battery
2) hold down both power and volume rockers while powering up phone by replacing the battery
as long as "fastboot" is unchecked in settings/power or settings/apps then you do not need to pull the battery. power off,then hold volumd down,slightly first,then power until you see hboot. after the green writing flashes,then select recovery. you can also boot directly to recovery via apps like "quickboot"

is this going to bring up the CW recovery menu, or the default recovery menu?
if you mean the stock recovery,that should be gone. cw is now in its place.

[i did the battery out/in method the whole time while rooting to power the phone off/on, as it was easy and seemed to worked every time]

thanks again,
-mark
Click to expand...

hope that helps :)
 
Scotty,

thanks. it worked great .. although i did have a long pause during final reboot at the droid "eye" that made me sweat a little, thinking i bricked it. the update notification showed up briefly, then went away forever! i never found the update.zip on the SD card, so it must have been in the cache or something

-mark
 
Hey Scotty, Appreciate this post and I have followed everything and it worked for me but Im stuck on step 8 finishing up as I cant download

"software build 4.08.605.15 radio/hboot
hboot(1.07.0000)
PB31IMG-4.08.605.15-hboot-1.07.zip
md5: PB31IMG-4.08.605.15-hboot-1.07.zip db019de010ae8ef6a2c250fd8b378ba1"

I click the link and hit download but all of a sudden my browser says there is no internet connection. I was wondering if there is another link I can download from?
 
eatyourgreenes said:
Hey Scotty, Appreciate this post and I have followed everything and it worked for me but Im stuck on step 8 finishing up as I cant download

"software build 4.08.605.15 radio/hboot
hboot(1.07.0000)
PB31IMG-4.08.605.15-hboot-1.07.zip
md5: PB31IMG-4.08.605.15-hboot-1.07.zip db019de010ae8ef6a2c250fd8b378ba1"

I click the link and hit download but all of a sudden my browser says there is no internet connection. I was wondering if there is another link I can download from?
Click to expand...

Mediafire links work for me, but here are others.

Radio: http://dinc.does-it.net/Radios/2.15.10.12.20/PB31IMG.zip
MD5: http://dinc.does-it.net/Radios/2.15.10.12.20/PB31IMG.zip.md5

Hboot: http://dinc.does-it.net/Hboots/Hboot_1.07/PB31IMG.zip
MD5: http://dinc.does-it.net/Hboots/Hboot_1.07/PB31IMG.zip.md5
 
working fine for me as well. if you have trouble with cmlusco's links,try adjusting your browser/firewall/antivirus settings or try a different browser
 
Thank you cmlusco those helped me out. Yea I'm not sure what it was since I was able to download other files from mediafire, just not that one. but thank you both. I'll keep you updated on whether or not I successfully finish this process.
 
Just wanted to come in and commend Scotty. I used this as a guide to rooting mine 7 months ago and I've been subscribed to this thread since. I am always amazed at how quickly and often Scotty is helping others out.

Great job man!
 
Hey, wondering if I could get some help here..

I have gotten as far as entering the token and recieving the Unlock Code, but once I do the command

fastboot flash unlocktoken Unlock_code.bin

instead of my phone going to the bootloader screen, the command window gives the response

C:\ANDROID>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
FAILED (status read failed (Too many links))
finished. total time: 1413.002s

Any suggestions??
 
make sure unlock_code.bin is in your android folder. make sure the phone is in fastboot,not hboot.

other than that,make sure nothing is running on the PC that can communicate with the phone( pda ner,easy tether,htc sync,even i tunes)

try differen usb cables and ports

sometimes a reboot of phone and/or pc can help

this the token than you just got,with this phone,by following the guide,correct?
 
I completed process successfully and was on froyo. I fd up and uninstalled some system apps to prevent ota but then the Rom in op kept failing to install so I started over. Tried a bunch of things but it always fails when I try to reunlock writing failed I think but I will look again in sec. Right now I'm froyo locked s-off hboot 1.07........ any ideas?
Edit: oh yeah no root also. Can I unlock run unlock if I'm on froyo? In my panick I reset in bootloader
Edit2: Ok I read post #505 and my sit is very similar except mine says 'FAILED (remote: unlock token check failed)'.......also header says 'locked (oow)' I think....?...instead of relocked....do I need a new unlock bin?
 
drewade17 said:
i keep get a path not found message in the command window
HELP PLEASE!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Click to expand...

as sdraw said,something is not in the right spot. it may help us to know after what command you get that error. preferably,copy and paste the entire contents of the cmd window. :)
 
Alright I just completed through step 7 and I'm s-off. I downloaded the two updates (hboot and radio) and put them in the miniadb_inc folder. I now just copy and paste each of these into the command prompt?
Click to expand...

correct. just follow the directions in step 8 :)
 
I had to register an account and say Thank you!! so much for this guide. I followed every step and now I have Froyo and S-off. Now I guess i need to see whats next to do.

what do you recommend?
 
harleyblinn said:
I had to register an account and say Thank you!! so much for this guide. I followed every step and now I have Froyo and S-off. Now I guess i need to see whats next to do.

what do you recommend?
Click to expand...


Follow the "finishing up" steps in the guide :) or proceed to picking out a ROM and flashing it... I just put the Jelly bean ROM on my old incredible and it seems to work well.
 
So i get everything done perfectly. I've gone through the steps three times (on Linux and Wndoze).

Each time I choose "Recovery" my HTC Incredible just sits at the white screen with the hTC letters (lime green) forever. I've waited up to 20 minutes.

Each time I take the battery out, it boots fine in the stock rom or I can go back to the hboot screens too.

I'm unlocked, but not rooted. Please help?

thanks,
yok
 
yoknapatawpha said:
So i get everything done perfectly. I've gone through the steps three times (on Linux and Wndoze).

Each time I choose "Recovery" my HTC Incredible just sits at the white screen with the hTC letters (lime green) forever. I've waited up to 20 minutes.

Each time I take the battery out, it boots fine in the stock rom or I can go back to the hboot screens too.

I'm unlocked, but not rooted. Please help?

thanks,
yok
Click to expand...

Make sure the boooader is still unlocked. Then you need to erase and reflash the recovery with fastboot.

fastboot erase recovery

fastboot flash recovery recovery.img

CWM img - http://dinc.does-it.net/Guide_Root_New_Hboot/recovery.img

TWRP img - http://dinc.does-it.net/Recoveries/TWRP_2.4.4.0/recovery.img
 
OP- Thank you for the wonderful instruction...

cmlusco- My friend from xda... good to see you here... As you can tell... I'm still struggling to get the S-off and unlock

I was following the steps carefully until I got got too smart and wiped system, data and datadata even though the instructions only called for cache and dalvik..

I flashed cmlusco's TOB V3.0 to proceed
I got to step 4 and downgraded to froyo. But now the phone will not stay connected to the PC to continue. I'm not sure if this is due to be screwing up by wiping sys and data or the phone connector is acting up.

If the issues is only with the connector. How can I proceed from step on wards using the only the phone. I can move the sd card back and forth from the PC to get all the required files to root on sd card.

Looking for any kind of advise or direction
 
raghublr said:
OP- Thank you for the wonderful instruction...

cmlusco- My friend from xda... good to see you here... As you can tell... I'm still struggling to get the S-off and unlock

I was following the steps carefully until I got got too smart and wiped system, data and datadata even though the instructions only called for cache and dalvik..

I flashed cmlusco's TOB V3.0 to proceed
I got to step 4 and downgraded to froyo. But now the phone will not stay connected to the PC to continue. I'm not sure if this is due to be screwing up by wiping sys and data or the phone connector is acting up.

If the issues is only with the connector. How can I proceed from step on wards using the only the phone. I can move the sd card back and forth from the PC to get all the required files to root on sd card.

Looking for any kind of advise or direction
Click to expand...

So you got all of step 4 done? After flashing the ruu did you remember to re enable usb debugging? The only way to flash the unlock_code.bin is to use fastboot. So you will need to get usb working for that. If you can get it unlocked, and a recovery flashed, you can do the rest without adb. I suppose since your on froyo already, you could do the froyo ruu again and see if that clears up your adb issue.
 
cmlusco said:
So you got all of step 4 done? After flashing the ruu did you remember to re enable usb debugging? The only way to flash the unlock_code.bin is to use fastboot. So you will need to get usb working for that. If you can get it unlocked, and a recovery flashed, you can do the rest without adb. I suppose since your on froyo already, you could do the froyo ruu again and see if that clears up your adb issue.
Click to expand...

Yes, I got all of step 4 done. I have since tried different computer and usb cables but still no luck.

So, you suggest that I update from hboot using PB31IMG.zip
 
You must log in or register to reply here.
Back
Top Bottom