• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root Stuck on Hboot 6.17

I had my evo 4g rooted with mikmik. Was working beautifully until my screen cracked and I needed to take it in. I rooted using captain throwbacks guide , also unrooted the same way also. Took phone in and got new screen. But my hboot is stuck on hboot 6.17 with s-on . When I try to flash the 3 supersonic files on the guide via hboot by renaming the file to pc3 6img. It loads up and then it says, main version is older! Update fail! Been googling this for almost 3 weeks and cant find a solution. Would like to get mikmik back on my phone and use the wireless tether. Any help would be amazing.

Supersonic evt2-3 ship s-on
Hboot-6.170001
Touch panel-atmel224_16ab
Radio-2.15.00.01.15
 
I had my evo 4g rooted with mikmik. Was working beautifully until my screen cracked and I needed to take it in. I rooted using captain throwbacks guide , also unrooted the same way also. Took phone in and got new screen. But my hboot is stuck on hboot 6.17 with s-on . When I try to flash the 3 supersonic files on the guide via hboot by renaming the file to pc3 6img. It loads up and then it says, main version is older! Update fail! Been googling this for almost 3 weeks and cant find a solution. Would like to get mikmik back on my phone and use the wireless tether. Any help would be amazing.

Supersonic evt2-3 ship s-on
Hboot-6.170001
Touch panel-atmel224_16ab
Radio-2.15.00.01.15

ok you need to flash a ruu to finish the unrooting process. the ruu needs to match your radio. which ruu's have you tried?
 
the reason why i ask is because if you unrooted correctly your hboot should have changed to whatever radio you had at the time which is not what you have now. the unrooting process changes your hboot to 6.17 which then allows you to get s-on and use a ruu to switch everything back to stock.....so something went wrong there as your hboot did not change.

now the current radio you have is the most current one out there which means that either you or the tech who worked on your phone had updated it.

unfortunately now it might be harder to root the phone now. the only thing i can think of is to see if your phone will still accept an ota and see if that changes your hboot. if not then i'm not too sure what can be done.

i'm gonna see if i can get some help on this, but i do not think that there is much you can do at this point.
 
When they gave me my phone back, the tech said he updated everything because I was behind on updates. Thanks any help would be great to get back to rooted phone, primarily for wifi. Dont wanna pay sprint for their hotspot service. Thanks again.
 
When they gave me my phone back, the tech said he updated everything because I was behind on updates. Thanks any help would be great to get back to rooted phone, primarily for wifi. Dont wanna pay sprint for their hotspot service. Thanks again.

yeah that explains it then. in the future make sure that you tell the tech to not update the phone.

the only thing like i said earlier is to try and see if the phone can take the ota. it might not.
 
hi,cApTaIn GoOfY! i just have a couple questions at this point.

1)i assume that you have a working,booting phone,is this correct? id hope a repair facility would not give you back an unworking device,that was working when you took it in for a hardware repair.

2)is this 6.17 hboot htcdev compatible? i.e.,does it have a big,pinked locked across the top?

all we should need to do,is lower your main version so you can run an old ruu. this should be fairly straight forward if your phone is still working and booting,and even easier if we can unlock the bootloader to install a recovery and root.

id suggest we pick an ruu old enuff to run unrevoked on,so that you have radio s off,rather than revolutionarys hboot s off. this should greatly simplify things in the future :)
 
hi,cApTaIn GoOfY! i just have a couple questions at this point.

1)i assume that you have a working,booting phone,is this correct? id hope a repair facility would not give you back an unworking device,that was working when you took it in for a hardware repair.

2)is this 6.17 hboot htcdev compatible? i.e.,does it have a big,pinked locked across the top?

all we should need to do,is lower your main version so you can run an old ruu. this should be fairly straight forward if your phone is still working and booting,and even easier if we can unlock the bootloader to install a recovery and root.

id suggest we pick an ruu old enuff to run unrevoked on,so that you have radio s off,rather than revolutionarys hboot s off. this should greatly simplify things in the future :)


Yes my phone works. It is the only way I get online vs wifi at school or coffee shop.
I have tried 3 ruu that were on the captain throwback unroot guide . All 3 of the supersonic ones. When I flash via hboot pc36img I get an error message " main version is older! Update fail!" It does not say locked on hboot my first post I typed what my hboot says on the bottom of the post. Been interesting registering/posting via my evo.. I do have recovery but it is the recovery with the little picture of phone with red triangle.
 
hi,cApTaIn GoOfY! i just have a couple questions at this point.

1)i assume that you have a working,booting phone,is this correct? id hope a repair facility would not give you back an unworking device,that was working when you took it in for a hardware repair.

2)is this 6.17 hboot htcdev compatible? i.e.,does it have a big,pinked locked across the top?

all we should need to do,is lower your main version so you can run an old ruu. this should be fairly straight forward if your phone is still working and booting,and even easier if we can unlock the bootloader to install a recovery and root.

id suggest we pick an ruu old enuff to run unrevoked on,so that you have radio s off,rather than revolutionarys hboot s off. this should greatly simplify things in the future :)

ok so this 6.17 hboot is a hex edited version of hboot 6.16 from revolutionary. the idea is that you flash the hex edited version thru the bootloader and then you run a ruu to complete the unrooting process.

my guess is that after flashing the 6.17 hboot, the next step of running the ruu did not change the hboot for whatever reason.

and the most unfortunate thing is that the tech updated the phone to a radio firmware that most likely will not work any of the ruu's out there.

you mentioned scotty of lowering the misc partition. i'm not sure if that is possible with an s-on hboot and no custom recovery. if only we can get the phone to update the hboot.

How do I go about getting a different ota?

in the phone's settings, you need to go to"about phone" and then "software" and then check for the latest software update. let it download and then install it., if that is possible.
 
Yes my phone works. It is the only way I get online vs wifi at school or coffee shop.
I have tried 3 ruu that were on the captain throwback unroot guide . All 3 of the supersonic ones. When I flash via hboot pc36img I get an error message " main version is older! Update fail!" It does not say locked on hboot my first post I typed what my hboot says on the bottom of the post. Been interesting registering/posting via my evo.. I do have recovery but it is the recovery with the little picture of phone with red triangle.

right. the ruus are failing becasue they have lower main version numbers than your current build. htc does not want us installing older firmware,so the main version is one of many checks an s on hboot does.

the recovery you have is the stock recovery,wich will only install official singed by htc files,thus not not offering us much help.

ok so this 6.17 hboot is a hex edited version of hboot 6.16 from revolutionary. the idea is that you flash the hex edited version thru the bootloader and then you run a ruu to complete the unrooting process.
well, i dont think its a hex edited revolutionary hboot. if it were,it would still be protecting itself from overwrite,and it would still be s-off,leaving him with options ;)

the hboot is a hex edited ship s on hboot,wich can be overwritten with the ruu. the tech prolly simply made the phone OTA to current,wich alot of times does not actually update the hboot like an ruu will. ive seen plenty of thunderbolts running 1.04.0000 hboot all the way up until ICS took over,even tho ruus started installing 1.05 several versions of GB earlier.

i made a "downgrader" hboot for thunderbolt,and for increidble 2,but i used an eng hboot to hex edit,so it was not only overwriteable,but it also was s off... just in case ;)



you mentioned scotty of lowering the misc partition. i'm not sure if that is possible with an s-on hboot and no custom recovery. if only we can get the phone to update the hboot.
i dont think the hboot version matters. its just a version number. im fairly certain he could download the htc dev compatible hboot ruu and install it,as it just looks at main version number,and not the actual hboot version(tho its possible im wrong on this). if that worked,it would be a relaible way to get root access to downgrade.

the other option,is since the phone is still on GB, zergrush may work. if so it should be a pretty straight forward to use zerg rush for temp root,then flash the modded misc image,then flash the older ruu.

as far as that goes,it may actually work to just run revolutionary,i dont see anywhere if this has been tried or not. if the tool checks the hboot version number,it will prolly fail,as it knows it should only work on hboots 2.15 and 2.16. but if it doesnt,it may work. :smokingsomb:

i for one would try and downgrade to an "unrevoked"able firmware. radio s off is a million billion zillion times better :p

do you evo 4g gurus know what main version the misc image in the unroot guide lowers to? and what is the lates ruu that has an unrevoked forever supported baseband? we can easily modify the misc image if its not low enuff.

this is pretty cool. yall have it pretty well covered here so i usually only get a PM when the phone has irrecoverable hardware issues,lol. i think we can work this one out :cool:

cApTaIn GoOfY,if you could paste us the output of fastboot getvar all

some basic directions if you need them:
first download and install these drivers: revolutionary drivers (mirror)

then,download this small file:
mini-adb.zip

-unzip it,and place the unzipped folder onto the root of your C drive(not inside a folder)

-open a cmd window(with win 7,click start bubble,type "command" or "cmd" in hte search box)

-now change to your mini-adb directory(assuming you didnt chagne the name). type in the black cmd window that opened on your PC:
cd c:\mini-adb

-pull the battery in your phone for a few seconds. hold volume down,then power. hold them both until you see the white/colored writing hboot screen

-select "fastboot" from the hboot menu with the vol rocker/power button

-in your cmd window type:
fastboot devices

it should output your phones serial number. if so youre good to go. if not,youre apparently having a driver issue. i usually recomend these drivers from Revolutionary: modified htc drivers download and install the drivers(you should just have to run that file). afterwards,unplug your phone,plug it back in. make sure its in fastboot. as soon as you get a result from "fastboot devices" your ready to procede to the next step.

-in your cmd window,type(or copy/paste,is much easier):
fastboot getvar all

-copy the info that outputs here. right click in your cmd window,click mark,highlight it all in white. hit enter. paste the info here. it will help us know which ruu for you to run. :)
 
scotty85 said:
do you evo 4g gurus know what main version the misc image in the unroot guide lowers to? and what is the lates ruu that has an unrevoked forever supported baseband? we can easily modify the misc image if its not low enuff.

not really sure captain throwback was the one to come up with the misc.img but when you use it you can use a ruu that will work with unrevoked so i do not think that we will need to lower it.

and unrevoked only works with the 3.70 software version. you can get the ruu from capt's thread over in the mikmik forums. here it is the link:[GUIDE] How to achieve S-OFF after unlocking 2.18 HBOOT with HTCDev.com - No More Watermark! :) - theMikMik
 
right. the ruus are failing becasue they have lower main version numbers than your current build. htc does not want us installing older firmware,so the main version is one of many checks an s on hboot does.

the recovery you have is the stock recovery,wich will only install official singed by htc files,thus not not offering us much help.



cApTaIn GoOfY,if you could paste us the output of fastboot getvar all

some basic directions if you need them:

INFOversion: 0.5
INFOversion-bootloader: 6.17.0001
INFOversion-baseband: 2.15.00.01.15
INFOversion-cpld: None
INFOversion-microp: 041f
INFOversion-main: 5.07.651.6
INFOserialno: HT098HL01242
INFOimei: 355195000000017
INFOproduct: supersonic
INFOplatform: HBOOT-8x50
INFOmodelid: PC3610000
INFOcidnum: SPCS_001
INFObattery-status: good
INFObattery-voltage: 3739mV
INFOpartition-layout: Generic
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: a80b8623
INFOhbootpreupdate: 11
INFOgencheckpt: 0
all: Done!
finished. total time: 0.000s
 
You think I need to run the. Htcdev unlock boot loader ?

No,not at this point. You can certainly try that if you wish,if the taco root method looks a little confusing. Doing htcdev unlock will involve replacing your hboot with a compatible one by downloading an ruu from htcdev. I *think* this will work,but we won't known for sure unless you try it. Since you don't have the pink locked,your hboot is a hex edited older,non compatible version.

What he is sugesting is that you just do section '3)taco root' wich goes thru the entire process to get temp root and flash the misc image that will allow you to run an old ruu. This should work fine,as taco root does not care about your hboot version,and from your getvar all,you're on the latest 5.xx firmware,wich taco root is known to work on :)
 
you know i wonder if taco root might work with your situation.

use this guide and try the taco root method:
http://androidforums.com/evo-4g-all...-rooting-gingerbread-2-3-5-dummies-guide.html

seem to be getting an error after typing: adb shell /data/local/tacoroot.sh --setup
TacoRoot: HTC Edition v1
By Justin Case (jcase)
Presented by TeamAndIRC, RootzWiki and AndroidPolice
With great assistance from Reid Holland (Erishasnobattery)
----------
TacoRoot: HTC Edition v1 is based on a vulnerability independently discovered by

both Justin Case and Dan Rosenberg (Rosenberg first). I believe unrevoked and
AlphaRev were also aware of it.
----------
Usage:
--recovery : For this exploit to work, you must have booted recovery at least on
ce after your last factory reset.
--setup : Setup the phone for root, must be done before --root.
--root : Root the phone.
--undo : Remove TacoRoot.
----------
Rebooting into recovery, please press Volume+, Volume- and Power at the same tim
e, and reboot the system.
rm failed for /data/data/recovery/log, Permission denied
link failed File exists

also when inputing this :adb shell chmod 755 /data/local/tacoroot.sh
should i be getting a response in cmd for it? because i am not.
 
5
 
Back
Top Bottom