Go Back   Android Forums > Android Phones > HTC Droid Incredible > Incredible - All Things Root
Incredible - All Things Root Rooting, ROMS, Overclocking, etc.

Like Tree5Likes
  • 1 Post By scotty85
  • 1 Post By scotty85
  • 1 Post By scotty85
  • 1 Post By scotty85
  • 1 Post By nschiwy

test: Reply
 
LinkBack Thread Tools
Old January 20th, 2012, 05:25 PM   #1 (permalink)
AF Addict
Thread Author (OP)
 
scotty85's Avatar
 
Join Date: Jul 2010
Posts: 11,014
 
Device(s):
Carrier: Not Provided

Thanks: 7,893
Thanked 7,228 Times in 4,485 Posts
Default an easier way to flash PB31IMG files

all htc phones utilize a PxxxIMG file system to flash RUUs and such in hboot. having guides up here,the thunderbolt,and merge forums, and being active on the board i see alot of folks have trouble getting PxxxIMG(PB31IMG in case of the incredible) to work. the prollem usually has simple fix,but sometimes causes folks an extreme amount of confusion.

but there is an easier way

i mess with my various htc devices alot,and have found using fastboot is a much faster,easier way to flash PxxxIMG files. you dont need to transfer files to your SD,or boot to change files if youve got a couple to do.

in a nutshell,youre going to place your file into the folder where adb and fastboot live(prolly platform tools or tools if youre an advanced user that has the sdk installed),place the phone in fastboot,put it in RUU mode and flash the file with this command: fastboot flash zip <filename>.zip

if you rooted with revolutionary or unrevoked,and have no idea what fastboot or adb even are,heres a step by step:

1)set up adb and fastboot download this file,wich contains adb and fastboot.
Multiupload.com - upload your files to multiple file hosting sites!
md5 sum: 9d1c0e2a98f09bb65521889870334b65

extract it,and place the extracted(not zipped) mini-adb folder on the root of the C drive of your PC. in windows 7,you should be able to just right click,then extract files. if not,you may need a utility such as 7 zip

re-install unrevoked/revolutionarys drivers,if you dont still have them on your PC from when you rooted.

open a command window. in windows 7,just click the start bubble,then type "command" in the search box. this should open a small black window.

change to your mini-adb directory(folder) by the entering the following command at the prompt in your command window: cd c:\mini-adb this should change your prompt to "mini-adb>" indicating that youve changed to that directory.

2)flash your file put the file that you want to flash into the mini adb-folder. you can copy/paste,drag/drop or move it however you are comfortable moving files.

plug in your phone. enable usb debugging,if its not allready.

enter the following commands. from here on,commands will be bold and italics,comments will be blue. each line is one command,enter them one at a time. you can copy/paste or type them in.

md5sums <filename> this will output the md5 sum of the file you will flash. make sure it matches that listed for your download

adb devices should output your phones serial number

adb reboot bootloader will boot you into the fastboot screen(white with colored letters)

fastboot devices will again output serial number

fastboot erase cache

fastboot oem rebootRUU

fastboot flash zip <filename>.zip

you will see a green line on your phone as the file flashes.youll see outut in your cmd window. sometimes when flashing a complete RUU you will get an error that says "failed,reflush immediately". dont panic,just run the above line again to reflash your file

after you get a "finished" message:

at this point,ycould actually flashe more files if you wanted. for example,a radio and a recovery. just repeat the "fastboot flash zip" command untill youve flashed all your files. then:

fastboot reboot-bootloader this will take you back to the white fastboot screen

fastboot reboot your phone should reboot

and of course,heres what the outputs will look like in the command window. red are my inputs. in this example,im installing twrp recovery on my thunderbolt,with a .zip file called: twrp111rbox1_PG05IMG

Code:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

C:\Users\Scott>cd c:\mini-adb

c:\mini-adb>md5sums twrp111rbox1_PG05IMG.zip

MD5sums 1.2 freeware for Win9x/ME/NT/2000/XP+
Copyright (C) 2001-2005 Jem Berkes - http://www.pc-tools.net/
Type md5sums -h for help

[Path] / filename                              MD5 sum
-------------------------------------------------------------------------------
[c:\mini-adb\]
twrp111rbox1_PG05IMG.zip                       31ae566360d4729ff1be2a5a67952777

c:\mini-adb>adb devices
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
HT12CS012936    device


c:\mini-adb>adb reboot bootloader

c:\mini-adb>fastboot devices
HT12CS012936    fastboot

c:\mini-adb>fastboot erase cache
               erasing 'cache'... OKAY [  0.262s]
finished. total time: 0.263s

c:\mini-adb>fastboot oem rebootRUU
                              ... OKAY [  0.222s]
finished. total time: 0.223s

c:\mini-adb>fastboot flash zip twrp111rbox1_PG05IMG.zip
       sending 'zip' (5573 KB)... OKAY [  0.907s]
                 writing 'zip'... INFOzip header checking...
INFOzip info parsing...
INFOchecking model ID...
INFOchecking custom ID...
INFOstart image[recovery] unzipping & flushing...
INFO[RUU]UZ,recovery,0
INFO[RUU]UZ,recovery,15
INFO[RUU]UZ,recovery,27
INFO[RUU]UZ,recovery,37
INFO[RUU]UZ,recovery,47
INFO[RUU]UZ,recovery,60
INFO[RUU]UZ,recovery,70
INFO[RUU]UZ,recovery,82
INFO[RUU]UZ,recovery,98
INFO[RUU]UZ,recovery,100
INFO[RUU]WP,recovery,0
INFO[RUU]WP,recovery,100
OKAY [  7.010s]
finished. total time: 7.918s

c:\mini-adb>fastboot reboot-bootloader
     rebooting into bootloader... OKAY [  0.151s]
finished. total time: 0.151s

c:\mini-adb>fastboot reboot
                     rebooting...
finished. total time: 0.150s

c:\mini-adb>
seems a lil complicated,but once you do it a couple times,its quick and easy.
zimlokks likes this.

Advertisements
__________________
The Delivery Guy
If someone has helped you,please click the THANKS button on that post.
Please post questions so others can benefit from the answers.
donate to my device fund
scotty85 is online now  
Last edited by scotty85; January 20th, 2012 at 05:36 PM.
Reply With Quote
The Following 5 Users Say Thank You to scotty85 For This Useful Post:
DrDooGood (January 29th, 2012), rsarno (February 21st, 2012), sdrawkcab25 (January 20th, 2012), speedster63 (June 17th, 2014), zimlokks (July 18th, 2012)
sponsored links
Old January 20th, 2012, 07:34 PM   #2 (permalink)
Senior Member
 
Join Date: Aug 2010
Location: PA
Gender: Male
Posts: 5,569
 
Device(s): Rooted Samsung Galaxy Nexus, Rooted HTC Incredible, Stock 4G Motorola Droid Xyboard 10.1 (32GB)
Carrier: Verizon

Thanks: 477
Thanked 1,982 Times in 1,340 Posts
Default

Added this to the root guide sticky
sdrawkcab25 is online now  
Reply With Quote
Old January 21st, 2012, 01:52 PM   #3 (permalink)
New Member
 
Join Date: Jan 2012
Posts: 5
 
Device(s):
Carrier: Not Provided

Thanks: 0
Thanked 1 Time in 1 Post
Default

So I got the PB31IMG file mentioned here --> [How To] Regain Root With S-Off or HTC unlocked bootloader
confirmed the MD5 checksum. Then followed those instructions and it diddnt work. So I followed your instructions and it is perfect until I reach the command fastboot flash zip <filename>.zip

I get the following error:
C:\mini-adb>fastboot flash zip PB31IMG.zip
sending 'zip' (3064 KB)... OKAY [ 0.681s]
writing 'zip'... INFOzip header checking...
INFOzip info parsing...
INFOchecking model ID...
FAILED (remote: 41 model id check fail)
finished. total time: 2.401s

Not sure why model id check is failing. What could I be doing wrong? my bootloader shows S-On but it is unlocked for sure with htcdev. All I want is root so I can tether. Why isnt my poor rezound liking this? Please help!
rooterbooter is offline  
Reply With Quote
Old January 21st, 2012, 02:22 PM   #4 (permalink)
AF Addict
Thread Author (OP)
 
scotty85's Avatar
 
Join Date: Jul 2010
Posts: 11,014
 
Device(s):
Carrier: Not Provided

Thanks: 7,893
Thanked 7,228 Times in 4,485 Posts
Default

Quote:
Originally Posted by rooterbooter View Post
So I got the PB31IMG file mentioned here --> [How To] Regain Root With S-Off or HTC unlocked bootloader
confirmed the MD5 checksum. Then followed those instructions and it diddnt work. So I followed your instructions and it is perfect until I reach the command fastboot flash zip <filename>.zip

I get the following error:
C:\mini-adb>fastboot flash zip PB31IMG.zip
sending 'zip' (3064 KB)... OKAY [ 0.681s]
writing 'zip'... INFOzip header checking...
INFOzip info parsing...
INFOchecking model ID...
FAILED (remote: 41 model id check fail)
finished. total time: 2.401s

Not sure why model id check is failing. What could I be doing wrong? my bootloader shows S-On but it is unlocked for sure with htcdev. All I want is root so I can tether. Why isnt my poor rezound liking this? Please help!
well,first of all,this is for the incredible,not the rezound. if you do in fact have a rezound and not an incredible,that is why the id check is failing and not letting you flash,you will need your own rezound specific recovery image,and you may need a different superuse zip file,but otherwise the following will apply,with exception that rezound hboot files are PH98IMG,NOT PB31IMG

if you do have an incredible:

unfortunately,htcdevs unlocked s-on and the radio s-off via unrevoked forever are not the same.

some htcdev unlocked models seem to allow PxxxIMG to be installed via hboot,while some do not. typically you get the ID check error when trying to flash firmware for another carrier,so the issue must be something to do with the CID of the phone,and it *may* actually work to flash the PB31IMG in hboot by placing it on a "gold card". i unfortunately do not have any unlocked s-on devices to experiment with. only things i have htcdev unlocked were allready radio s-offed ,so im not 100% sure on the limitations of different models.

you have a couple different options for getting your recovery. take the image out of the PB31IMG file(extract it first if you have to) and then place that image into your mini-adb,tools,platform tools,or wherever you are putting the files you want to push/flash. put the phone in fastboot as described above,and make sure its being recognized in your command window with "adb devices"

the first option,if you want to permanently install a custom recovery,you can flash your recovery with the following command:

fastboot flash recovery <recoveryname>.img

for example,if your recovery is named PB31IMG-clockwork your command wuld be:
fastboot flash recovery recovery-clockwork.img

if you dont really need a custom recovery(i.e.,never intend to make backups,flash roms,etc.) you can "softboot" the recovery into the phones memory temporarily with the following command:

fastboot boot <recoveryname>.img

the recovery will launch on the phone,and you can flash the superuser zip file from your linked thread. wile on screen,the recovery will look and function just like it was there permanently. after you reboot to your OS,the custom recovery will be gone,and youll have the stock recovery in case OTA updates come that you dont want to miss.(yes,an OTA will break root,but all youll need to do is reflash the superuser zip files afterward). if you need to make a backup or flash a file,youll just need to repeat the process to softboot it again.

so,with the a recovery named PB31IMG-clockwork your command would be:
fastboot boot recovery-clockwork.img

hope that helps
scotty85 is online now  
Last edited by scotty85; January 21st, 2012 at 02:40 PM.
Reply With Quote
Old May 29th, 2012, 10:37 PM   #5 (permalink)
Junior Member
 
nschiwy's Avatar
 
Join Date: Apr 2012
Gender: Male
Posts: 29
 
Device(s): Google Nexus 4 Google Nexus 10 Samsung Galaxy Nexus Amazon Kindle Fire (OG) HTC Droid Incredibl
Carrier: Straight Talk

Thanks: 10
Thanked 6 Times in 6 Posts
Default

So i followed the instructions to flash the 7.07 radio to my incredible and now it has been sitting at the splash screen for a long time... I decided to leave it alone in case this is something normal that it needs to do but it is getting to the point where I am feeling like I may have a brick is this something normal or is there something I can do to revert to my former settings to at least have a working phone? even if it has the ancient 7.28 radio (like it did before) I don't really care...

Thanks!

the following is what I did in CMD, I admit that I didn't check the MD5 but I have never had a problem with it before. Maybe when using hboot/fastboot I should have been more careful.

Code:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

C:\Users\Nick>cd /

C:\>cd miniadb_inc

C:\miniadb_inc>adb devices
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
HT05PHJ02533    device


C:\miniadb_inc>adb reboot bootloader

C:\miniadb_inc>fastboot devices
HT05PHJ02533    fastboot

C:\miniadb_inc>fastboot erase cache
               erasing 'cache'... OKAY [  1.262s]
finished. total time: 1.262s

C:\miniadb_inc>fastboot oem rebootRUU
                              ... OKAY [  0.100s]
finished. total time: 0.100s

C:\miniadb_inc>fastboot flash PB31IMG.zip
unknown partition 'PB31IMG.zip'
error: cannot determine image filename for 'PB31IMG.zip'

C:\miniadb_inc>fastboot flash zip PB31IMG.zip
       sending 'zip' (5824 KB)... OKAY [  0.850s]
                 writing 'zip'... INFOzip header checking...
INFOshift signature_size for header checking...
FAILED (remote: 32 header error)
finished. total time: 6.547s

C:\miniadb_inc>fastboot reboot-bootloader
     rebooting into bootloader... OKAY [  0.098s]
finished. total time: 0.098s

C:\miniadb_inc>fastboot reboot
                     rebooting...
finished. total time: 0.096s

C:\miniadb_inc>
As you can tell, probably, it seems like it failed to flash the radio and in hboot it still says radio:..."7.28" so I am pretty sure that no update occurred which begs the question why did it change anything at all?? I AM able to access hboot and CWM and I am currently attempting to restore a nandroid I made with the hopes that when I reboot things will be back to normal


UPDATE: Good News: performing the nandroid restore DID bring me back to where I was before in CM7.2 and I am perfectly happy with that. However, I wouldn't mind being able to update my radio to something that performs better because I did notice a significant change in the signal quality when switching from my D2 to the inc and at first I owned that up to the age of the phone but maybe that was because of the radio and if I could update that, I would be very happy!
nschiwy is offline  
Last edited by nschiwy; May 29th, 2012 at 11:04 PM.
Reply With Quote
Old May 30th, 2012, 06:35 AM   #6 (permalink)
AF Addict
Thread Author (OP)
 
scotty85's Avatar
 
Join Date: Jul 2010
Posts: 11,014
 
Device(s):
Carrier: Not Provided

Thanks: 7,893
Thanked 7,228 Times in 4,485 Posts
Default

i would verify the md5 of your download,and try it again. you can use the md5 sums utility inside the mini-adb file,as described in the first post, with the command:

md5sums filename.ext

with a pb31img.zip file,youd use:

md5sums PB31IMG.zip

it is extremely important to check md5 sums,or file sizes,or something,to verify the integrity of your download,as a corrupt hboot or radio WILL leave you with an unrecoverable brick.

its pretty important with rom flashes as well,especially if youre using clockwork recovery. flashing bad files can destroy memory blocks that can eventually lead to the phone being unusable.

in short- checking md5 sums is a habbit that would be good for you to get in to

where did you get your PB31IMG? it looks like it failed without even trying to flash it(wich may be good for you). im not 100% sure what the header failure is refering to. are you s-off?
nschiwy likes this.
scotty85 is online now  
Reply With Quote
The Following User Says Thank You to scotty85 For This Useful Post:
nschiwy (May 30th, 2012)
Old May 30th, 2012, 07:46 AM   #7 (permalink)
Junior Member
 
nschiwy's Avatar
 
Join Date: Apr 2012
Gender: Male
Posts: 29
 
Device(s): Google Nexus 4 Google Nexus 10 Samsung Galaxy Nexus Amazon Kindle Fire (OG) HTC Droid Incredibl
Carrier: Straight Talk

Thanks: 10
Thanked 6 Times in 6 Posts
Default

checking the MD5s is just a pain but it's worth not breaking my phone so i guess i will have to start keeping an eye on it

I do have S-Off, and I got the radio from DINC.DOES-IT.NET - HTC Incredible Files

As with a lot of people, for some reason trying to flash the file in hboot does not work for some reason so when i saw your guide to using adb and oemRUU I was excited because even though I haven't had a lot of trouble with the old radio one thing that I want with my phone or just things in general is to have full control over it. When I buy something it is mine and I believe that any modifications that I make to it are completely fair game and it would be a much better world (in my opinion) if more phone manufacturers were more cooperative with the dev community like HTC is with their unlocked bootloader.
nschiwy is offline  
Reply With Quote
Old May 30th, 2012, 08:13 AM   #8 (permalink)
AF Addict
Thread Author (OP)
 
scotty85's Avatar
 
Join Date: Jul 2010
Posts: 11,014
 
Device(s):
Carrier: Not Provided

Thanks: 7,893
Thanked 7,228 Times in 4,485 Posts
Default

i agree completely, tho i do also believe that if i mess up my phone with a bad bootloader flash,then the manufacturer shouldnt have to warranty it. maybe if more folks were honest when they brick their devices it could be different.

at any rate,i downloaded this radio file from your link,and made sure the md5 matched the one listed: 617E6969061DCBC3CA613FA6D02565F0

fired up the junk inc into hboot,chose fastboot and at first i thot the android info document looked wierd,but it flashed fine,and rebooting back to bootloader it now shows 2.15.10.07.07 for the baseband.

im not sure why you had trouble with it... other than maybe a bad download,or maybe you were in hboot,not fastboot? make sure you have in red: FASTBOOT USB under the green writing.

if you have a blue HBOOT USB PLUG you are in the wrong mode it can be misleading,as you do get a serial number back from "fastboot devices" while in hboot.

Code:
c:\miniadb_inc>md5sums PB31IMGradio.zip

MD5sums 1.2 freeware for Win9x/ME/NT/2000/XP+
Copyright (C) 2001-2005 Jem Berkes - http://www.pc-tools.net/
Type md5sums -h for help

[Path] / filename                              MD5 sum
-------------------------------------------------------------------------------
[c:\miniadb_inc\]
PB31IMGradio.zip                               617e6969061dcbc3ca613fa6d02565f0

c:\miniadb_inc>fastboot erase cache
               erasing 'cache'... OKAY [  0.569s]
finished. total time: 0.569s

c:\miniadb_inc>fastboot oem rebootRUU
                              ... OKAY [  0.101s]
finished. total time: 0.102s

c:\miniadb_inc>fastboot flash zip PB31IMGradio.zip
       sending 'zip' (9713 KB)... OKAY [  1.310s]
                 writing 'zip'... INFOzip header checking...
INFOzip info parsing...
INFOchecking model ID...
INFOchecking custom ID...
INFOstart image[radio] unzipping & flushing...
INFO[RUU]UZ,radio,0
INFO[RUU]UZ,radio,9
INFO[RUU]UZ,radio,18
INFO[RUU]UZ,radio,23
INFO[RUU]UZ,radio,32
INFO[RUU]UZ,radio,37
INFO[RUU]UZ,radio,46
INFO[RUU]UZ,radio,51
INFO[RUU]UZ,radio,60
INFO[RUU]UZ,radio,69
INFO[RUU]UZ,radio,78
INFO[RUU]UZ,radio,87
INFO[RUU]UZ,radio,92
INFO[RUU]UZ,radio,97
INFO[RUU]UZ,radio,100
INFO[RUU]WP,radio,0
INFO[RUU]WP,radio,7
INFO[RUU]WP,radio,16
INFO[RUU]WP,radio,21
INFO[RUU]WP,radio,26
INFO[RUU]WP,radio,35
INFO[RUU]WP,radio,40
INFO[RUU]WP,radio,45
INFO[RUU]WP,radio,50
INFO[RUU]WP,radio,100
OKAY [ 27.300s]
finished. total time: 28.611s

c:\miniadb_inc>fastboot reboot-bootloader
     rebooting into bootloader... OKAY [  0.099s]
finished. total time: 0.100s

c:\miniadb_inc>
nschiwy likes this.
scotty85 is online now  
Reply With Quote
The Following User Says Thank You to scotty85 For This Useful Post:
nschiwy (May 30th, 2012)
Old May 30th, 2012, 08:22 AM   #9 (permalink)
Junior Member
 
nschiwy's Avatar
 
Join Date: Apr 2012
Gender: Male
Posts: 29
 
Device(s): Google Nexus 4 Google Nexus 10 Samsung Galaxy Nexus Amazon Kindle Fire (OG) HTC Droid Incredibl
Carrier: Straight Talk

Thanks: 10
Thanked 6 Times in 6 Posts
Default

UPDATE: I just downloaded it again from the dinc.does-it website and checked the md5 sum with a sum checker that i downloaded from the play store. They were equal so i am going to try everything again later. It was definitely a bad download the first time, the file size is significantly larger this time. I'm just glad it was so bad that it didn't know what to do with it rather than trying to flash a bad file. I don't have time to do the work now because I have to go to class but when i get home from work later I will try again and report back. Thanks for all of your help!
nschiwy is offline  
Reply With Quote
The Following User Says Thank You to nschiwy For This Useful Post:
scotty85 (May 30th, 2012)
Old May 30th, 2012, 08:31 AM   #10 (permalink)
AF Addict
Thread Author (OP)
 
scotty85's Avatar
 
Join Date: Jul 2010
Posts: 11,014
 
Device(s):
Carrier: Not Provided

Thanks: 7,893
Thanked 7,228 Times in 4,485 Posts
Default

no prollem... let me know how it goes. definately was a good thing it didnt flash... bad radio flash can brick your device

also,a good app for checking things on your phone is scary aliens AFV "android file verifier". i use it... its a great app!
nschiwy likes this.
scotty85 is online now  
Reply With Quote
The Following User Says Thank You to scotty85 For This Useful Post:
nschiwy (May 30th, 2012)
sponsored links
Old May 30th, 2012, 10:40 AM   #11 (permalink)
Junior Member
 
nschiwy's Avatar
 
Join Date: Apr 2012
Gender: Male
Posts: 29
 
Device(s): Google Nexus 4 Google Nexus 10 Samsung Galaxy Nexus Amazon Kindle Fire (OG) HTC Droid Incredibl
Carrier: Straight Talk

Thanks: 10
Thanked 6 Times in 6 Posts
Default

So I wound up flashing it using hboot and it worked! So it was a bad file that was holding me back the whole time. I'm just very glad it didn't try to flash the bad file through fastboot, I was very lucky for that. Anyway thank you very much for your help and guidance.

To those reading this I highly recommend checking your MD5s if you don't already. I got lucky this time but I could have bricked my phone just as easily because I was being careless. Take that extra time so you don't wind up with a $200 paperweight
scotty85 likes this.
nschiwy is offline  
Reply With Quote
The Following User Says Thank You to nschiwy For This Useful Post:
scotty85 (May 31st, 2012)
Reply


Go Back   Android Forums > Android Phones > HTC Droid Incredible > Incredible - All Things Root
Thread Tools

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On



All times are GMT -5. The time now is 11:41 AM.
Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2014, vBulletin Solutions, Inc.