scotty85
Extreme Android User
Upgrading the hboot and radio are optional,but I would prolly recomend.it.
Like a backup,a rom will never contain firmware. So once you're on a particular hboot and radio,they will remain until you purposely change them
-
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
Upgrading the hboot and radio are optional,but I would prolly recomend.it.
Like a backup,a rom will never contain firmware. So once you're on a particular hboot and radio,they will remain until you purposely change them
Forza Nightmare
Newbie
Upgrading the hboot and radio are optional,but I would prolly recomend.it.
Like a backup,a rom will never contain firmware. So once you're on a particular hboot and radio,they will remain until you purposely change them
Thank you Scotty! Sorry about the questions that may belong in another thread, or another topic all together. I finally decided to root this phone when I realized the Dinc 4g was not going to be my upgrade. I like the GS3, but at this point I'm waiting to see how the fall/winter offerings turn out. Anyway, thanks again.
Ok, I'm stumped. I get to step 4, and each time I get stuck at a loading screen. The "eye" to be specific. I've followed the instructions to the tee, and no dice. No error messages come up during the process. I've got an Incredible. The phone was stock and updated as of yesterday before I started, if that helps.
All the md5 hashes match, and I didn't get any weird error messages. Any ideas? Naturally, the only error occurred when I tried to back it up...
All the md5 hashes match, and I didn't get any weird error messages. Any ideas? Naturally, the only error occurred when I tried to back it up...
gbiggie
La patience et le pardon
Welcome to Android Forums bwhorton :thumbup:
What does the ADB window say-are your able to copy and paste it here
scotty85
Extreme Android User
that issue has been fixed for everyone so far simply by doing a factory reset in hboot(with stock recovery) failing that,you can run the downgrade ruu again.
Welcome to Android Forums bwhorton :thumbup:
What does the ADB window say-are your able to copy and paste it here
Hey, nice dog! And thanks for getting back so fast! Sorry, I posted right before I went to bed and I just got back from work.
Well, after failing step 4, when I boot the phone into recovery (not Clockwork, which is wiped), ADB lists the serial for the phone but shows it as offline.
I can't boot the phone, so I can't start exactly from the beginning of step 1 (enabling debugging mode, etc.), but I can start from using fastboot to unlock the bootloader.
1. Unlock bootloader: success. Select "yes" on phone and reboot. Pull battery before the phone loads to get to the bootloader.
2. 'adb devices' shows no devices attached. 'fastboot devices' shows the serial and "fastboot". Flashing clockwork first results in a failure because, like a dope, I didn't put the phone in fastboot. When I do, it works. Windows makes the "disconnect" sound." Don't see any progress bars. 'fastboot reboot' reboots phone, I pull the battery right away to get back to bootloader.
3. Superuser is already on the card, which is handy, since I can't connect to the phone through Windows Explorer. Recovery takes me to Clockwork. For completeness' sake, I backup. I get, "Error while making a backup image of /data!" Wipe the cache and the Dalvik cache successfully, install the zip with no problem. Reboot, pull battery, blah.
4. Have to go back to recovery mode to get 'adb devices' to see the phone, and when it does, it lists it as being in recovery. All three md5's match. Can't push "flash_image" to the directory, so I have to run shell and make the directory; then it flashes fine. All of the shell commands work, I reboot to the bootloader, and 'fastboot getvar mainver' returns 1.22.605.2, as per the instructions. Bootloader is already relocked. Fastboot erases the cache. 'fastboot oem rebootRUU' results in a black screen with a silver "htc" logo. Windows makes the "disconnect" sound. I enter 'fastboot flash zip PB31IMG.zip'. After a minute or so, no error messages and it starts unzipping and flushing, while a green status bar appears on the phone. No error messages, the green bar fills all the way up and stays there. Fastboot shows "okay" and "finished". I reboot the phone to the bootloader to be safe and to check version numbers. I've got:
HBOOT-1.02.000
MICROP-0417
TOUCH PANEL-ATMELC03_16ac
RADIO-2.15.00.07.28
Dec 21 2011, 23:37:16
Again, to be safe, factory reset. Clockwork appears to be gone, and when the phone reboots I see green arrows in a circle above a phone, along with a status bar. The phone reboots. Locks up at the red eye thing. If I plug it in, Windows makes the "connected" sound, and I can see the embedded driver from Verizon, but no SD card or anything else.
I've attached the output from the command prompt for the whole sequence. Thanks for taking a look at this!
that issue has been fixed for everyone so far simply by doing a factory reset in hboot(with stock recovery) failing that,you can run the downgrade ruu again.
No dice on the factory reset, still freezes at the same place. In fact, I can't tell if it's actually doing anything. The status bar just has grey stripes, then the phone reboots. Now, when you say "run the downgrade ruu again", do you mean just repeat the last bit of Step 4. Like kinda just flash it till it sticks?
scotty85
Extreme Android User
first of all,stop. do not just randomly flash ruus,as you are on the downgrade firmware,so if it will boot youll be creating more work for yourself to actually get rooted.
im about to read your posts,so hang tight for a few...
Thanks, man. I just tried a Froyo and a Gingerbread, both stock, and no love from either. I've restrained myself from going into full-panic-install-everything mode
I've also formatted the SD card and tried just shoveling the downgrade onto the blank card to see if HBOOT would grab it, with the same results. Thanks again for helping me out, I definitely appreciate it!
I've also formatted the SD card and tried just shoveling the downgrade onto the blank card to see if HBOOT would grab it, with the same results. Thanks again for helping me out, I definitely appreciate it!
scotty85
Extreme Android User
how long have you given the phone on the red eye? first boot can take several minutes. i would honestly give it as long as 20 minutes on the eye before pulling the battery.
thats correct. do the last bit of step 4 and run the downgrade ruu again.
you did have the stock recovery in place when doing the factory reset,correct? and you allowed the phone to finish up and reboot itself?
there are no obvious or outward errors in your cmd promts the main version successfully changed,and the ruu flashed all partitions with no errors. hopefully running the downgrade again will get you up and running,some have had to run it a second time.
as for your last post,there are only 2 reasons a correct,signed file isnt found in hboot:
1)the file is not named correctly(windows adds and hides the file ext,so a common error is the file ends up named "PB31IMG.zip.zip" or in rarer cases,just "PB31IMG". phone needs to see PB31IMG.zip so using windows the correct name usually is PB31IMG
2) the card is not formatted FAT32. if its plain FAT,or anything else,PB31IMG is invisible.
these are the reasons i like to run it from fastboot,rather than the sd. it takes those 2 variables out of the equation,wich tend to cause folks alot of fustration.
HOWEVER,if the phone finds the file,you see the status bars, and then it does not update,it could be failing any of a number of security checks. a few possible causes:
-the bootloader is unlocked
-the file is older than the version on the phone(wich s-on will not allow without trickery)
-the file is not an official,signed by htc ruu
-the file is for a different phone
-the file has become corrupt during download or transfer,and thus failing the signiture check
scotty85
Extreme Android User
Thanks, man. I just tried a Froyo and a Gingerbread, both stock, and no love from either. I've restrained myself from going into full-panic-install-everything mode
I've also formatted the SD card and tried just shoveling the downgrade onto the blank card to see if HBOOT would grab it, with the same results. Thanks again for helping me out, I definitely appreciate it!
youre quite welcome. definately do not panic.
-run the downgrade again(last bit of step 4)
-give the eye 15-20 minutes
-if not boot,try the facotry reset again
-give the eye 15-20 minutes
been a long day,so i may not be up much longer... if i fall asleep ill check on you 1st thing in the am
Hmm. Well, the bootloader is relocked. Stock recovery was on the SD card. One time I sent it via fastboot from the command line, the other time I moved it to the SD card from Windows. I checked the name from the terminal, and it's definitely PBG31IMG.zip. As far as I can tell there isn't a newer version on the phone. I can't swear that the USB cable isn't the culprit, so I'll try with a different one. Is there a known-good source for an HTC-signed, up-to-date rom?
I'll keep plugging away. Thanks for sticking with me on this!
I'll keep plugging away. Thanks for sticking with me on this!
scotty85
Extreme Android User
if the file is named correctly,it may well be the sd format. running the file from fastboot should eliminate sd card format and name errors.
you can do:
fastboot getvar all
or
fastboot getvar mainver
and double check that the main version has not changed. the ruu you you run will have to be that number,or higher.
the downgrade ruu,is an official,signed by htc rom. its just one that still has exploitable holes
there are a couple of newer ones here:
Shipped ROMs
one here:
FileFactory Folder View - Generic Releases
and one here:
http://pvillecomp.com/wp/wp-content/uploads/Images/Gingerbread-Stock_PB31IMG.zip
be aware that some are .exe files wich are run on your pc. start them with the phone in fastboot,and follow the onscreen directions.
all usb cables and ports are defaintely not created equal. its defaintely a good idea to try different ones.
scotty85
Extreme Android User
Forza Nightmare
Newbie
8)Finishing up
1)update hboot/radio.
you can install the following in hboot by renaming PB31IMG,or you can place them in miniadb_inc,and flash them like you did the froyo downgrade(phone in fastboot mode):
fastboot devices
fastboot erase cache
fastboot oem rebootRUU
fsatboot flash zip zipname.zip
fastboot reboot-bootloader
fastboot reboot
*whatever method you use,make sure to double check the md5s,as a bad hboot or radio flash can and will leave your device unworking and unrecoverable
-4.08.605.15 radio and 1.07 hboot:
PB31IMG-4.08.605.15-hboot-1.07.zip
md5: PB31IMG-4.08.605.15-hboot-1.07.zip db019de010ae8ef6a2c250fd8b378ba1
PB31IMG-4.08.605.15-radio.zip
md5: PB31IMG-4.08.605.15-radio.zip cb8b3ac72c0ae13e1f088b302135bd58
note:the bootloader may still be in ints previous state when you re-flash it(i.e.,if it was unlocked,it will still be). if you find it to be locked or relocked you can use your original unlock-code.bin to re-unlock it,if you wish. this is optional,but unlocking the bootloader does give you access to a few extra fastboot commands.
hboot will say 2.15.10.12.20. so apparetly your flash was not successful.
Hey Scotty, I finished up, and all is well. Now for updating the radio. I have read step 8, but I'm a little confused by the "Install in hboot by renaming PB31IMG". I download the radio and hboot file and rename them to PB31IMG? Then flash in hboot?
Hi guys, I am a new user working on Rooting and obtaining S-off for my Dinc. I made it to step 4 but ran into a hitch with the PB31IMG zip file and installing that on the phone, I have tried running the command prompts but it crashes out and says file cannot be read, I also tried moving the zip to the SD card and running off the recover/ install zip file in the bootloader but it also crashes out and says (bad). Has anyone seen this before and if so how do you solve it? I made it most of the way through without any issues up to this point. My computer OS is windows XP also.
scotty85
Extreme Android User
correct. you can rename to PB31IMG,place on the sd card,and let hboot install(one at a time),or you can simply install them from fastboot like you did the downgrade ruu,with the fastboot flash zip command
either method is ok,use wich ever one is most comfortable.
did the md5 sum match when you checked it earlier in the commands? the file is still zipped,correct?
the name will need to match exactly the zipfile that is in miniadb_inc,and make sure you tacked on the file extension. (example fastboot flash zip PB31IMG.zip)
copy and paste the contents of your cmd window. its a lil difficult to figure out what happened from "the file crashes out"
did the md5 sum match when you checked it earlier in the commands? the file is still zipped,correct?
the name will need to match exactly the zipfile that is in miniadb_inc,and make sure you tacked on the file extension. (example fastboot flash zip PB31IMG.zip)
copy and paste the contents of your cmd window. its a lil difficult to figure out what happened from "the file crashes out"[/QUOTE]
Ok I found the issue, the PB zip was not in the miniadb folder on the c root drive, causing it to go invalid. I finished the root and tutorial! thanks for putting this together, I cannot seem to get the radio flashed back to the updated version its still 2.15? I am hoping to flash the Jellybean RC2 rom as soon as possible and get the phone back up and running.
Thanks again for the help scotty.
the name will need to match exactly the zipfile that is in miniadb_inc,and make sure you tacked on the file extension. (example fastboot flash zip PB31IMG.zip)
copy and paste the contents of your cmd window. its a lil difficult to figure out what happened from "the file crashes out"
[/QUOTE]Ok I found the issue, the PB zip was not in the miniadb folder on the c root drive, causing it to go invalid. I finished the root and tutorial! thanks for putting this together, I cannot seem to get the radio flashed back to the updated version its still 2.15? I am hoping to flash the Jellybean RC2 rom as soon as possible and get the phone back up and running.
Thanks again for the help scotty.
Forza Nightmare
Newbie
Hi nwrolla, I just now flashed my hboot and radio to the latest updates. It was a piece of cake (with Scotty's help). Read back a couple of posts to see what he told me to do. Hope this helps.
Thanks Forza, did you use the original PB file and just run the Cmd prompt for it? Does anyone know if it will matter that I already flashed a new ROM to my phone when I update the radio?
Forza Nightmare
Newbie
I did not use Cmd prompt (miniadb) to push the file. I installed them from hboot ONE AT A TIME. Here is what I did.
I downloaded both files from the link a few posts back. I then took the hboot file and renamed it PB31IMG and placed it on the root of my sd card, booted into bootloader (volume down and power), and selected yes to update (it found the file on its own and asked if I wanted to apply update). It did its thing really fast, then I rebooted the phone.
Removed the hboot file from my sd card, renamed the radio file to PB31IMG and placed it on the root of my sd card. From there, it was the same process as before except it took a little longer for it to flash (maybe 10 seconds).
scotty85
Extreme Android User
awsome! glad you got it working. i had a usb cable once that would actually cause windws 7 to crash if i tried to use it for data transfer
i bought a used,rooted eris that the guy said he couldnt update- turns out the only prollem with it was that usb cable. swapped it out and i could transfer stuff to and from the phone just fine.nope. it will not matter what rom you are on when you change the radio and hboot