-
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
If I can't get this phone to boot into recovery using recovery-clockwork-5.0.2.0-inc.img, can I use another program in order to flash recovery or am I toast?
Any way that I can flash the original OTA or do I have to be able to get into recovery first in order to do this? How about using the file called Stock_inc_4.08.60519_deodexed.zip. Apologies if these are dumb questions
Any way that I can flash the original OTA or do I have to be able to get into recovery first in order to do this? How about using the file called Stock_inc_4.08.60519_deodexed.zip. Apologies if these are dumb questions
Is it possible that the reason that I can't get the phone to boot into recovery is because I flashed the recovery while in Windows 7?
sdrawkcab25
Extreme Android User
you need a working recovery to really flash anything. the only other way to flash the recovery, would be to rename the recovery file to PB31IMG.zip and place it onto the root of the sd card and let hboot install it.
so to go that route, you will need another way for your pc to communicate with your sd card, ie, a card reader or any other device that accepts the sd card that you can plug into your pc.
then you would need to make sure your sd card is formatted to FAT32(right click on the drive and select properties). if it isn't you will need to format it to FAT32. Formatting will erase everything on there, so copy the contents to somewhere safe. do not use the "quick format" option.
then you would rename the clockwork recovery file to exactly PB31IMG.zip
place that file on the root of your sd card (not inside any folders). put the sd card back into your phone and boot the phone into hboot. after a few moments, your phone should then recognize the file and prompt you to install it.
scotty85
Extreme Android User
a non-booting phone is often fixed by running an "RUU" wich is factory software/firmware from htc. the prollem that we have is that there is no ruu availble for your firmware build,and that the phone in its current state will not let you flash older RUUs.
its sort of a snowball affect
we need to modify the misc image to allow an older ruu flash
we need root access in some sort of OS to change the misc image. we cant use the android OS becsue the phone wont boot,so we need a recovery to be able to modify the misc image.
so,without a working recovery,we are somewhat up a creek,unless htc happens to release an RUU for your build.
no,that shouldnt have mattered. lots of things can interfere with the flash,even if it appears successful. the following is not quite for the issue youre having,but go thru the checklist,its possible that something simple is preventing recovery from "sticking":
one last bit,in order to get PB31IMG to flash,you will need to modify the android info text document inside the .zip file.
it will look something like this:
youll need to edit 3.12.605.0 to match your current build.
something like this:
just unzip,open the text document,edit the main version number,save,then rezip the image and text document. then follow the rest of sdraws directions
one good thing about the PB31IMG method,is that if something on the PC is causing an issue,then installing in this manner should take the pc out of the equation.
Where do I find the android info text document that I need to modify. Is it somewhere imbedded within miniadb_inc.zip?a non-booting phone is often fixed by running an "RUU" wich is factory software/firmware from htc. the prollem that we have is that there is no ruu availble for your firmware build,and that the phone in its current state will not let you flash older RUUs.
its sort of a snowball affect
we need to modify the misc image to allow an older ruu flash
we need root access in some sort of OS to change the misc image. we cant use the android OS becsue the phone wont boot,so we need a recovery to be able to modify the misc image.
so,without a working recovery,we are somewhat up a creek,unless htc happens to release an RUU for your build.
no,that shouldnt have mattered. lots of things can interfere with the flash,even if it appears successful. the following is not quite for the issue youre having,but go thru the checklist,its possible that something simple is preventing recovery from "sticking":
one last bit,in order to get PB31IMG to flash,you will need to modify the android info text document inside the .zip file.
it will look something like this:
youll need to edit 3.12.605.0 to match your current build.
something like this:
just unzip,open the text document,edit the main version number,save,then rezip the image and text document. then follow the rest of sdraws directions
one good thing about the PB31IMG method,is that if something on the PC is causing an issue,then installing in this manner should take the pc out of the equation.
scotty85
Extreme Android User
oops
a zip file i dont believe was included in the download,just the image file.
you can download a PB31IMG containing clockwork 5.0.2.0 from here: Recoveries | PvilleComp's
I just noticed that this Pvillecomp.com link also has a Stock HTC Recovery by HTC file listed. This may show my ignorance........... but is it possible to use this Stock recovery (rename it to PB31IMG, load it onto a SD card and then boot it thru HBOOT) to see if it would reset the phone back to stock. With a working stock phone, I then could start the rooting process all over again?oops
a zip file i dont believe was included in the download,just the image file.
you can download a PB31IMG containing clockwork 5.0.2.0 from here: Recoveries | PvilleComp's
sdrawkcab25
Extreme Android User
that would give you just the stock recovery which is pretty useless, you need clockwork recovery for any chance of recovering the phone.
hey scotty sorry to bother u, i read step one from ur guide, u talk about hboot and with some version, i have hboot 2.02 what im suppose to do? sorry mate for stupid question. i read lot of guides in last couple of days how to root incredible s, but i haven't found any luck because every guide say something different. http://androidforums.com/members/scotty85.html
sdrawkcab25
Extreme Android User
this guide is for the original incredible, not incredible s
... i'll get you the link to the guide you need.over at XDA:
http://forum.xda-developers.com/showthread.php?t=2118187
thanks i'll check that. cheersthis guide is for the original incredible, not incredible s
over at XDA:
http://forum.xda-developers.com/showthread.php?t=2118187
Ok. I downloaded ClockworkMod 2.0.5.0 by Koushik Dutta, renamed it to PB31IMG.zip and put it on a FAT32 formatted SD card using an allocation size of 1024 bytes. I'm not sure if the allocation size mattered, though. Booted into HBOOT and loaded recovery that way, but even though the recovery said that it was successful... upon Reboot, I ran into the exact same problem as before. It won't reboot, but goes into that annoying loop. I'm about ready to use my shop press downstairs and make it into an Incredible book marker.oops
a zip file i dont believe was included in the download,just the image file.
you can download a PB31IMG containing clockwork 5.0.2.0 from here: Recoveries | PvilleComp's
Now, as fate may have it, my wife's HTC incredible, which was purchased the same time as mine, started having random rebooting issues this past weekend. For no reason at all, it would reboot, but unlike mine, it would get to the Droid eye and start up again. Knowing that it was only a matter of time before it freezes up, I decided to root it using the instructions in the OP. I have gotten as far as making a backup of the stock, unrooted rom in Step 3( Flash Superuser Root Files) which got me thinking. If my wife's HTC has exact same Android Version, Baseband Version, Kernel Version, Software number, and Build Number as mine, is it possible to somehow use this backup to load it back onto my phone to make it operational so that I can root and get around the problem that I am having. If so, how would I go about doing this?
Root Files).
scotty85
Extreme Android User
if you could get recovery to install,you could attempt to restore her backup. it would prolly not help the situation,as there is prolly something corrupt in another partition,wich is why were aiming for running the ruu,wich should fix all partitions,not just boot and system,like a rom or backup flashed in recovery.
unfortunately,it all revolves around getting a working recovery,wich your phone doesnt seem to be permitting
unfortunately,it all revolves around getting a working recovery,wich your phone doesnt seem to be permitting
scotty85
Extreme Android User
miniadb_inc is fine. there is an exploit called zergrush that will trigger antivirus programs. if you need to,temporarily disable avg to get the file to download. if you have the file,just missing zergrush,then youre good to go,as that exploit is not needed for this process
you do not unzip PB31IMG. it must remain a zip file to flash.
sunthas
Well-Known Member
scotty85 your dedication to this thread blows my mind.
I did stuff all out of order when I ran into problems and I'm in a strange place on my phone.
I've never been able to get the fastboot oem get_identifier_token to function or the RUU update tool from HTC. I finally found a version of adb or stumbled on the right combination of files that allows adb devices to function properly.
I've got superusers installed, but now I've got the wrong recovery installed.
About Phone:
Android: 4.1.1
Baseband: 2.15.10.07.07
Kernal Version: 2.6.38.8-evervolve-dives-jellybean+drew@master #1
Mod Version: RC1
Build number: inc-eng 4.1.1
INCREDIBLE XC SHIP S-ON
HBOOT-0.92.0000
MICROP-0417
ClockworkMod Recovery is at v2.5.0.5
I've run unrevoked3 a few times and I installed the Rom Manager and flashed this current version on the phone system I have in attempt to bypass other issues and in the idea that it was just another way to do what I wanted.
attempting to update recovery with fastboot flash recovery recovery-clockwork-5.0.2.0-inc.img results in a FAILED due to signature verify fail.
I'm going to continue scanning through the 15 pages of thread, but I figured my questions should get posted either way.
I also tried to do the shell step and it failed with a Segmentation fault when trying to execute ./flash_image misc /sdcard/mtd0.img
thanks for the help.
P.S. fastboot getvar mainver: 4.08.605.2
P.S.S. was FAT on sdcard now FAT32.
I did stuff all out of order when I ran into problems and I'm in a strange place on my phone.
I've never been able to get the fastboot oem get_identifier_token to function or the RUU update tool from HTC. I finally found a version of adb or stumbled on the right combination of files that allows adb devices to function properly.
I've got superusers installed, but now I've got the wrong recovery installed.
About Phone:
Android: 4.1.1
Baseband: 2.15.10.07.07
Kernal Version: 2.6.38.8-evervolve-dives-jellybean+drew@master #1
Mod Version: RC1
Build number: inc-eng 4.1.1
INCREDIBLE XC SHIP S-ON
HBOOT-0.92.0000
MICROP-0417
ClockworkMod Recovery is at v2.5.0.5
I've run unrevoked3 a few times and I installed the Rom Manager and flashed this current version on the phone system I have in attempt to bypass other issues and in the idea that it was just another way to do what I wanted.
attempting to update recovery with fastboot flash recovery recovery-clockwork-5.0.2.0-inc.img results in a FAILED due to signature verify fail.
I'm going to continue scanning through the 15 pages of thread, but I figured my questions should get posted either way.
I also tried to do the shell step and it failed with a Segmentation fault when trying to execute ./flash_image misc /sdcard/mtd0.img
thanks for the help.
P.S. fastboot getvar mainver: 4.08.605.2
P.S.S. was FAT on sdcard now FAT32.
sunthas
Well-Known Member
Code:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Droid>fastboot devices
HT04LHJ02986 fastboot
C:\Droid>fastboot oem get_identifier_token
... INFO[ERR] Command error !!!
OKAY [ 0.007s]
finished. total time: 0.008s
C:\Droid>no idea how to handle this error, its so early in the process.
scotty85
Extreme Android User
as above,sounds like youre on .92 hboot. read the directions more carefully. part 1)unlock with htcdev mentions you need to check the hboot screen,and what to do to update it if you find 0.92.0000
Hey Scotty85 and Sdrawkcab25. I wanted to let you guys know that I rooted and achieved S-Off with my wife's Incredible. Recovery is working great and now I'm searching for a Rom to flash, since I can't handle the constant requests to upgrade. I'm leaning towards CM7.if you could get recovery to install,you could attempt to restore her backup. it would prolly not help the situation,as there is prolly something corrupt in another partition,wich is why were aiming for running the ruu,wich should fix all partitions,not just boot and system,like a rom or backup flashed in recovery.
unfortunately,it all revolves around getting a working recovery,wich your phone doesnt seem to be permitting
I'm still trying to flash and make stick Clockmod recovery on my own Incredible and hope that one day I can break thru and make it work (but so far the rebooting persists), but at least now, I know what to expect. Many, many Thanks for all the help.