[GUIDE] How To Root HBOOT 1.02/1.07 and gain S-OFF

warpurlgis

Senior Member
Feb 25, 2012
159
45
0
Erie
C:\Users\Warpurlgis\Desktop\Droid Incredible\Phone>fastboot flash recovery recov
ery.img
sending 'recovery' (3064 KB)...
OKAY [ 0.437s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 0.975s

This is what happens when I try.

Also the phone no longer checks for OTA updates, well it did. Now it says it's up to date but it's on 2.2 Froyo. I know this isn't true.

Isn't gingerbread the lowest version number of android you can have the new market for? I didn't think Froyo could have it.
 

cmlusco

Senior Member
Nov 20, 2010
3,244
968
0
Michigan City, IN
C:\Users\Warpurlgis\Desktop\Droid Incredible\Phone>fastboot flash recovery recov
ery.img
sending 'recovery' (3064 KB)...
OKAY [ 0.437s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 0.975s

This is what happens when I try.

Also the phone no longer checks for OTA updates, well it did. Now it says it's up to date but it's on 2.2 Froyo. I know this isn't true.

Isn't gingerbread the lowest version number of android you can have the new market for? I didn't think Froyo could have it.
In hboot does it still say unlocked at the top? I dont see how it would let you fastboot flash it in step 11 to downgrade, but not now.

The ota will probably pop up again at some point.

Yes the new market is only on gb.
 
Last edited:

warpurlgis

Senior Member
Feb 25, 2012
159
45
0
Erie
Prepared to be mind boggled then.

HBOOT is locked. It was unlocked after I did the HTC unlocking method.

I have Froyo. I also have the new market

I don't know what is happening.

I followed every step precisely.
 

warpurlgis

Senior Member
Feb 25, 2012
159
45
0
Erie
Haha I read to "save it cause you would need it later". I was thinking when I was getting to the unrevoked part when we would be using it.

I got the OTA to take so I might do this over.

For the HTC unlocking part. Do you know if you would need the same key if you were going to redo the unlocking, or does it generate a new one?
 

cmlusco

Senior Member
Nov 20, 2010
3,244
968
0
Michigan City, IN
Haha I read to "save it cause you would need it later". I was thinking when I was getting to the unrevoked part when we would be using it.

I got the OTA to take so I might do this over.

For the HTC unlocking part. Do you know if you would need the same key if you were going to redo the unlocking, or does it generate a new one?
Just using the fastboot flash unlocktoken Unlock_code.bin command should unlock it again with the same key. I believe the keys are specific to the devices serial number.

So you shouldnt have to start over. Just unlock again with the fastboot command, and then do unrevoked with the custom img again.
 

warpurlgis

Senior Member
Feb 25, 2012
159
45
0
Erie
Well for how convoluted my whole experience has become tonight, I feel it would just be better to start fresh tomorrow night. I have what I need, know for the most part what to do again, and with your last piece of the puzzle all will go smoothly... I hope.

Thanks for your help. I'll try again when I get out of work tomorrow.
 

bhatt86

Member
Mar 30, 2011
46
1
0
Franklin
Forgive me if I am reposting this but I've searched here and the cyanogen forums for a solution. I recently purchased a HTC Incredible as an upgrade from my Sanyo Zio. I am currently running 2.3.4 and I am attempting to achieve s-off so I can root with unrEVOked 3.22 I looked through all the write up's and couldn't find anything to answer the paticular issue I'm running into. I've installed and reinstalled all of the correct software designated in this write up. I went step by step on the HTCDev.com bootloader program but having no success.

When I load the RUU the I accept the check boxes and click next but it comes to this error.


I installed every possible driver I can find for my phone. I checked my device manager and there are no errors on the driver but it only comes up as
Android USB Devices>My HTC

I installed the HTC Sync but it will only recognize my phone if it is in sync mode. This is the only issue I've had any I don't know what I'm missing probably something I've overlooked but some clarification would be great.
 

cmlusco

Senior Member
Nov 20, 2010
3,244
968
0
Michigan City, IN
Forgive me if I am reposting this but I've searched here and the cyanogen forums for a solution. I recently purchased a HTC Incredible as an upgrade from my Sanyo Zio. I am currently running 2.3.4 and I am attempting to achieve s-off so I can root with unrEVOked 3.22 I looked through all the write up's and couldn't find anything to answer the paticular issue I'm running into. I've installed and reinstalled all of the correct software designated in this write up. I went step by step on the HTCDev.com bootloader program but having no success.

When I load the RUU the I accept the check boxes and click next but it comes to this error.

I installed every possible driver I can find for my phone. I checked my device manager and there are no errors on the driver but it only comes up as
Android USB Devices>My HTC

I installed the HTC Sync but it will only recognize my phone if it is in sync mode. This is the only issue I've had any I don't know what I'm missing probably something I've overlooked but some clarification would be great.
Try this, i found it on another site.

1: Install HTC Sync. (Read 1a first)
1a: If you already tried the update with it and failed, uninstall HTC Sync and install a program called CCleaner (http://www.piriform.com/ccleaner/download).
1b: When installed run CCleaner and go to registry (the blue box on the left).
1c: Scan for issues and then press Fix selected issues... and fix all of them.
1d: Reboot computer to be sure problems are fixed.
1e: Reinstall HTC Sync.

2: Run HTC Sync if it isn't already running.

3: Turn on Dinc and plug it in, then choose HTC Sync on the connections menu that pops up ( The one that says Charge Only, Disk Drive, HTC Sync, and Mobile Broadband Connect). If Dinc says it can't find HTC Sync that is fine.

4: Turn off any internet connections on the PC. Ex: disable or disconnect wifi/wired connections.

5: Run the RUU and follow the steps.
 
Last edited:
  • Like
Reactions: bhatt86

bhatt86

Member
Mar 30, 2011
46
1
0
Franklin
So tried this both ways updating Sync first then uninstalled reinstalled then used ccleaner to clear any then redownloaded RUU and still coming to the same error. When I start HTC Sync the phone shows up and I am able to use sync I verified that it works but as soon as I tell RUU to search for my device and click next it disconnects itself from sync and RUU comes back with the same error, then once I exit RUU it reconnects to HTC Sync.

Also I did turn wifi off on the phone and the laptop.

---------- Post added at 10:52 PM ---------- Previous post was at 10:27 PM ----------

I just looked into the ruu_log on my hard disk and I'm noticing a pattern.

<LOG>
<T221929><INFO><VERSION>1.0.1.30</VERSION></INFO></T221929>
<T221929><DEBUG><PAGE>====== WelcomeDlg ======</PAGE>
</DEBUG></T221929>
<T221957><DEBUG><PAGE>====== VerifyingMobileDlg ======</PAGE>
</DEBUG></T221957>
<T221958><DEBUG><CMD>adb devices</CMD>
</DEBUG></T221958>
<T222004><DEBUG><OUT>adb server is out of date. killing...
* daemon started successfully *
** daemon still not runningerror: cannot connect to daemon</OUT>
</DEBUG></T222004>
<T222004><DEBUG><CMD>fastboot devices</CMD>
</DEBUG></T222004>
<T222004><DEBUG><OUT />
</DEBUG></T222004>
<T222004><DEBUG><CMD>adb devices</CMD>
</DEBUG></T222004>
<T222011><DEBUG><OUT>adb server is out of date. killing...
* daemon started successfully *
** daemon still not runningerror: cannot connect to daemon</OUT>
</DEBUG></T222011>
<T222011><DEBUG><CMD>fastboot devices</CMD>
</DEBUG></T222011>
<T222011><DEBUG><OUT />
</DEBUG></T222011>
<T222012><DEBUG><CMD>adb devices</CMD>
</DEBUG></T222012>
<T222018><DEBUG><OUT>adb server is out of date. killing...
* daemon started successfully *
** daemon still not runningerror: cannot connect to daemon</OUT>
</DEBUG></T222018>
<T222018><DEBUG><CMD>fastboot devices</CMD>
</DEBUG></T222018>
<T222018><DEBUG><OUT />
</DEBUG></T222018>
<T222018><DEBUG><CMD>adb devices</CMD>
</DEBUG></T222018>
<T222024><DEBUG><OUT>adb server is out of date. killing...
* daemon started successfully *
List of devices attached
HT078HJ08876 device
</OUT>
</DEBUG></T222024>
<T222024><DEBUG><CMD>fastboot devices</CMD>
</DEBUG></T222024>
<T222024><DEBUG><OUT />
</DEBUG></T222024>
<T222025><DEBUG><CMD>adb devices</CMD>
</DEBUG></T222025>
<T222030><DEBUG><OUT>* daemon not running. starting it now *
* daemon started successfully *
** daemon still not runningerror: cannot connect to daemon</OUT>
</DEBUG></T222030>
<T222030><DEBUG><CMD>fastboot devices</CMD>
</DEBUG></T222030>
<T222030><DEBUG><OUT />
</DEBUG></T222030>
<T222030><DEBUG><CMD>adb devices</CMD>
</DEBUG></T222030>
<T222037><DEBUG><OUT>adb server is out of date. killing...
* daemon started successfully *
** daemon still not runningerror: cannot connect to daemon</OUT>
</DEBUG></T222037>
<T222037><DEBUG><CMD>fastboot devices</CMD>
</DEBUG></T222037>
<T222037><DEBUG><OUT />
</DEBUG></T222037>
<T222037><DEBUG><CMD>adb devices</CMD>
</DEBUG></T222037>
<T222042><DEBUG><OUT>adb server is out of date. killing...
* daemon started successfully *
List of devices attached
HT078HJ08876 device
</OUT>
</DEBUG></T222042>
<T222042><DEBUG><CMD>fastboot devices</CMD>
</DEBUG></T222042>
<T222043><DEBUG><OUT />
</DEBUG></T222043>
<T222046><DEBUG><CMD>adb devices</CMD>
</DEBUG></T222046>
<T222052><DEBUG><OUT>adb server is out of date. killing...
* daemon started successfully *
** daemon still not runningerror: cannot connect to daemon</OUT>
</DEBUG></T222052>
<T222052><DEBUG><CMD>fastboot devices</CMD>
</DEBUG></T222052>
<T222053><DEBUG><OUT />
</DEBUG></T222053>
<T222053><DEBUG><CMD>adb devices</CMD>
</DEBUG></T222053>
<T222059><DEBUG><OUT>adb server is out of date. killing...
* daemon started successfully *
** daemon still not runningerror: cannot connect to daemon</OUT>
</DEBUG></T222059>
<T222059><DEBUG><CMD>fastboot devices</CMD>
</DEBUG></T222059>
<T222059><DEBUG><OUT />
</DEBUG></T222059>
<T222059><DEBUG><CMD>adb kill-server</CMD>
</DEBUG></T222059>
<T222100><DEBUG><OUT />
</DEBUG></T222100>
</LOG>

So I'm wondering if the downloaded version of ADB isn't bad, going to attempt to uninstall and reinstall.
 

cmlusco

Senior Member
Nov 20, 2010
3,244
968
0
Michigan City, IN
So tried this both ways updating Sync first then uninstalled reinstalled then used ccleaner to clear any then redownloaded RUU and still coming to the same error. When I start HTC Sync the phone shows up and I am able to use sync I verified that it works but as soon as I tell RUU to search for my device and click next it disconnects itself from sync and RUU comes back with the same error, then once I exit RUU it reconnects to HTC Sync.

Also I did turn wifi off on the phone and the laptop.

---------- Post added at 10:52 PM ---------- Previous post was at 10:27 PM ----------

I just looked into the ruu_log on my hard disk and I'm noticing a pattern.


1.0.1.30
====== WelcomeDlg ======

====== VerifyingMobileDlg ======

adb devices

adb server is out of date. killing...
* daemon started successfully *
** daemon still not runningerror: cannot connect to daemon

fastboot devices



adb devices

adb server is out of date. killing...
* daemon started successfully *
** daemon still not runningerror: cannot connect to daemon

fastboot devices



adb devices

adb server is out of date. killing...
* daemon started successfully *
** daemon still not runningerror: cannot connect to daemon

fastboot devices



adb devices

adb server is out of date. killing...
* daemon started successfully *
List of devices attached
HT078HJ08876 device


fastboot devices



adb devices

* daemon not running. starting it now *
* daemon started successfully *
** daemon still not runningerror: cannot connect to daemon

fastboot devices



adb devices

adb server is out of date. killing...
* daemon started successfully *
** daemon still not runningerror: cannot connect to daemon

fastboot devices



adb devices

adb server is out of date. killing...
* daemon started successfully *
List of devices attached
HT078HJ08876 device


fastboot devices



adb devices

adb server is out of date. killing...
* daemon started successfully *
** daemon still not runningerror: cannot connect to daemon

fastboot devices



adb devices

adb server is out of date. killing...
* daemon started successfully *
** daemon still not runningerror: cannot connect to daemon

fastboot devices



adb kill-server





So I'm wondering if the downloaded version of ADB isn't bad, going to attempt to uninstall and reinstall.
Did you use the adb package i have in the op, or did you already have adb setup? If you used my package i know it works and is not out of date, it is from the latest sdk. Im not sure when it says out of date if it means the actual adb file is out of date or if it just means its not up to date with the info on the phone. Can you manually connect with adb thru a cmd prompt, by typing adb devices?

Also do you have a program on your pc called droid explorer? Also hit ctrl alt del select task manager and kill all processes of adb.exe, then try again. There may be multipul instances of adb running at once.
 
Last edited:

garfchong

Member
Apr 28, 2010
33
0
0
hi, i follow all the steps mentioned above and when i completed step 11 and proceed to step 12.

when i selected "recovery", i found my phone restart and it was hang there (white screen with htc logo).... nothing more....

may i know what was went wrong? how should i solve the problems?

thanks a lots.....
 

bhatt86

Member
Mar 30, 2011
46
1
0
Franklin
I was able to manually connect via adb through cmd prompt.
HTML:
C:\Users\Admin Account>cd c:\adb

c:\adb>adb devices
List of devices attached
HT078HJ08876    device


c:\adb>
I did not have Droid Explorer set up, I have now installed it and connected to my device. I also went into task manager and ended adb.exe and verified that when sync is runing there is only 1 adb.exe running.

I verified that I am running your adb_fastboot from post 1 as well.
Went again from step 1 and same result as soon as RUU starts to run HTC Sync loses connection to the device and it comes back with Error 170.

I also checked the RUU_logs and this was added.

List of devices attached
HT078HJ08876 device
</OUT>
</DEBUG></T112251>
<T112251><DEBUG><CMD>fastboot devices</CMD>
</DEBUG></T112251>
<T112252><DEBUG><OUT />
</DEBUG></T112252>
<T112310><DEBUG><CMD>adb devices</CMD>
</DEBUG></T112310>
<T112317><DEBUG><OUT>adb server is out of date. killing...
* daemon started successfully *
** daemon still not runningerror: cannot connect to daemon</OUT>
 
Last edited:

cmlusco

Senior Member
Nov 20, 2010
3,244
968
0
Michigan City, IN
hi, i follow all the steps mentioned above and when i completed step 11 and proceed to step 12.

when i selected "recovery", i found my phone restart and it was hang there (white screen with htc logo).... nothing more....

may i know what was went wrong? how should i solve the problems?

thanks a lots.....
Sounds like cw didnt take for some reason. Your bootloader is unlocked correct (says unlocked at the top of hboot)? If so i would start at step 8 and try to flash recovery again. Does it give any errors when flashing the recovery? Try this, before typing the "fastboot flash recovery recovery.img, type thid "fastboot erase recovery" then do the command above.
 
Last edited: