Related
Updated 01/05/2011
Support for both AMOLED & SLCD owners!
With the release of Unrevoked 3.31, DINC owners are now able to obtain root and S-OFF with the Nov OTA and it also supports recoveries for both AMOLED and SLCD users!
I have put together an extensive guide on how to get root for both AMOLED & SLCD users! Rooting is now even easier than ever.
The guide is available at http://jonsuh.com/2010/11/root-your-droid-incredible-how-to/
FAQ
Blank Recovery Screen Issue
For those of you coming across the issue of the blank/black recovery screen:
Do NOT boot straight into recovery with Volume Up+Power.
Boot into HBOOT FIRST with Volume Down+Power.
Then select RECOVERY from the HBOOT menu.
I rooted before the OTA and the OTA will not install
Read my article on how to Unroot your Droid Incredible at http://jonsuh.com/2011/01/unroot-your-droid-incredible/
Then read my article on how to root.
link doesnt work
I apologize; link is fixed and should be working now.
Looking to try this, but my SD card appears to be formatted to FAT16. How do I format it to FAT32?
Edit: Spoke too soon, got it. I'll post an update when once I'm done.
works perfectly took about 45 minutes
Sent from my ADR6300 using XDA App
papi92 said:
works perfectly took about 45 minutes
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
It is more time consuming but it does work! Glad to know u were able to get it to work. I think it was worth it. So much better having root back
Sent from my ADR6300 using XDA App
I'm already S-Off and rooted, running (mostly) stock. I skipped to step 5B, to update to the OTA update. However, when I attempt to apply update.zip, it fails during the "Verifying current system" step. The text is below:
assert failed: apply.patch.check("/system/app/Mail.apk", <insert two long non-matching hash values here>)
E:Error in /sdcard/update.zip
(Status 7)
Installation aborted.
Anyone run into this or have a clue?
Thanks.
danman7 said:
I'm already S-Off and rooted, running (mostly) stock. I skipped to step 5B, to update to the OTA update. However, when I attempt to apply update.zip, it fails during the "Verifying current system" step. The text is below:
assert failed: apply.patch.check("/system/app/Mail.apk", <insert two long non-matching hash values here>)
E:Error in /sdcard/update.zip
(Status 7)
Installation aborted.
Anyone run into this or have a clue?
Thanks.
Click to expand...
Click to collapse
Well truthfully, the OTA update doesn't do much but add more crapware. There isn't any other reports of the OTA being a significant update so you'd be safe to not even install the OTA. If you're annoyed with the reminder, if you've done all I've told you to, if you click "Install" it should just time out and not do anything and never remind you again.
Not Working For Me
This process does not appear to be working for me.
After doing all up to and including the "ADB" stuff and typing "reboot bootloader", my phone just boots to the bootloader and does nothing. I never get the prompt to process the update.
Where did I go wrong? I've tried this four times with the same results.
ozone777 said:
This process does not appear to be working for me.
After doing all up to and including the "ADB" stuff and typing "reboot bootloader", my phone just boots to the bootloader and does nothing. I never get the prompt to process the update.
Where did I go wrong? I've tried this four times with the same results.
Click to expand...
Click to collapse
Did you make sure you didn't rename the file something different? It should be "PB31IMG.zip" in the root of your SDCARD.
Also did you make sure your SDCARD was formatted to FAT32? and not FAT/FAT16?
UNREVOKED 3.22 HAS BEEN RELEASED.
Get your copy at www.unrevoked.com.
This thread will be changed within the next 24 hours to accommodate the new Unrevoked. No longer need to downgrade to root.
jsuh said:
Did you make sure you didn't rename the file something different? It should be "PB31IMG.zip" in the root of your SDCARD.
Also did you make sure your SDCARD was formatted to FAT32? and not FAT/FAT16?
Click to expand...
Click to collapse
No good.
I am running Windows 7 64-bit.
I formatted the removable sdcard to fat32 and the PB31IMG.zip file is named correctly.
I type in "./flash_image misc /sdcard/mtd0.img" and immediately get the "#" prompt after it confirms my entry.
I then type "reboot bootloader" and the phone goes to the bootloader and just sits there until I tell it to reboot.
Should I be doing all of this from the internal storage instead of the removable card?
New Info:
I just tried it again and this time instead of rebooting from the bootloader screen I selected "bootloader" and it checked the image and gave me the option to flash. I said "yes" and it is now loading the image.
ozone777 said:
No good.
I am running Windows 7 64-bit.
I formatted the removable sdcard to fat32 and the PB31IMG.zip file is named correctly.
I type in "./flash_image misc /sdcard/mtd0.img" and immediately get the "#" prompt after it confirms my entry.
I then type "reboot bootloader" and the phone goes to the bootloader and just sits there until I tell it to reboot.
Should I be doing all of this from the internal storage instead of the removable card?
Click to expand...
Click to collapse
Nope, you shouldn't, but no worries, the new Unrevoked version should be able to get you root without having to follow all my directions.
Just go to www.unrevoked.com/recovery then download and run the proper version.
Uh-Oh!
I think I just bricked the phone.
After saying yes to flashing the image, the phone went black and never woke up. now I can't turn it on although the soft buttons light up when I press the power button.
Is there any key combination that will get me to recovery or am I screwed?
Updated 12/2/2010
With the release of Unrevoked 3.22, I provided instructions for root for BOTH AMOLED & SLCD owners!
Enjoy
http://jonsuh.com/2010/11/root-your-droid-incredible-how-to
ozone777 said:
I think I just bricked the phone.
After saying yes to flashing the image, the phone went black and never woke up. now I can't turn it on although the soft buttons light up when I press the power button.
Is there any key combination that will get me to recovery or am I screwed?
Click to expand...
Click to collapse
Is there any way to get the phone back?
ozone777 said:
Is there any way to get the phone back?
Click to expand...
Click to collapse
You can try to hold volume down and the power button to get back into hboot. That may get you back to a workable position.
Hope that help...
g00gl3 said:
You can try to hold volume down and the power button to get back into hboot. That may get you back to a workable position.
Hope that help...
Click to expand...
Click to collapse
Already tried all the standard key combos with no success.
I thinks its time to stick a fork in it.
Time of death...3PM.
This doesn't mean I won't try again with the replacement Verizon sends out to me.
Gotta get back on the horse.
ozone777 said:
Already tried all the standard key combos with no success.
I thinks its time to stick a fork in it.
Time of death...3PM.
This doesn't mean I won't try again with the replacement Verizon sends out to me.
Gotta get back on the horse.
Click to expand...
Click to collapse
Pull the battery out put it back in and turn it back on (u said that it was an slcd?). U mentioned that the soft keys turn on right? Have u tried re running unrevoked with the new recovery mod for slcds? Look at my site for directions.
It may b that unrevoked would still recognize ur phone being plugged in and rerun the root process with the proper recovery.
Sent from my ADR6300 using XDA App
The 3.22 works great. The one thing I kept getting hung up on was after I installed the drivers by going into device manager etc etc was that windows was still asking me to install hardward drivers for usb device... so I followed along with windows and installed the driver again. Immediately after I installed the drivers for the second time unrevoked picked up my phone and started the process. It went all the way through and went to "done." (forgot to remove the PB31IMG.zip from trying to push the downgrade before - so it tried loading the update and failed...all I had to do was choose dont reboot, that brought me back to the hboot screen then unrevoked picked it back up).
The one problem I kept running into was that the new 3.22 unrevoked wouldnt pick my phone up even after I installed the drivers with device manager etc. So I tried a few different computers...still nothing and still asking me a second time to install the drivers. After I installed the drivers the second time everything was smooth from there.
So I purchased a used G1 and I knew it has some software issues. I have no idea what version OS or anything is on this phone. Issue is it will not boot up into the OS. After researching (I am new to android) I have found what it can and what I cant get it to do. I can get into recovery mode no problem and after an ALT-L I see "Android System Recovery <2e>". The phone usually boots into this mode straight away, or I can hold home+power and it will enter the mode. Tried doing a "wipe data/factory reset" but nothing changes. If I reboot the phone and hold "back" I would expect it to enter Fastboot mode where I could do stuff. Instead I see the "rainbow screen" very briefly and then a message saying that if I want to restore factory setttings press send, otherwise hit any other key to cancel. No matter what I press nothing happens and I have to pull battery. I can only get into this mode every now and then. It seems pretty finicky about getting into it, and again no options when I do. Finally the camera+power to get into the bootloader does nothing. I can get the PC to see the phone when in recovery mode. It showed up as a mass storage device and i got that changed over to "Android Phone" by installing the SDK drivers.
Is there anything I can do on the recovery screen? That is the only thing that consistently works. I have tried a few update.zip files (various OTA updates I downloaded) but I either get a "No signature" error or it starts installing and then immediately get an "Installation aborted".
Any help to get this up and running would be appreciated. Hopefully its not just useless. For now an OEM 1.5 build is really all a i need. I can worry about updating/rooting later.
Download dream.nbh and format your sd card then place the dream onto ur sd card reboot holding home+cam button and let it do its magic that's how I fixed mine I'm sure if you go to the htc site you will find all the files u need just do a bit more research before trying this
Sent from my HTC Magic/Dream using XDA App
I mentioned in my original post that the camera+power button to enter bootloader mode does not do anything. I have already researched solutions, but it only seems I have access to the recovery mode screen. What can be done from there to assist with this issue (if anything)?
Download and flash the files from here http://developer.htc.com/adp.html (ota radio and system image) rename them update and flash them one at a time
Sent from my HTC Magic/Dream using XDA App
As for the no sig error just do some reasarch on adb shell and flash clockworkmod recovery from there its easy once u do some searching.....dw a couple of weeks ago I was you lol it'll pan out ok the people round here are really helpful
Sent from my HTC Magic/Dream using XDA App
Does this require adb? I have not been successful in making my pc get an adb connection. When in recovery mode the phones shows up on my pc and I got it to show up as android, but "adb devices" does not show anything listed. Everything referencing adb says it needs USB Debugging enabled, but I cant do that I cant get into the OS to enable. I dont seem to be able to enter fastboot mode either (see original post).
Download the radio and recovery image format sd card rename the ota radio update.zip boot into recovery and select apply update from sd card one you have that done delete the update.zip and then place the recovery image on sd card but rename update.zip and do the same....should work for ya
Sent from my HTC Magic/Dream using XDA App
When trying to update the radio files (tried all 3 versions on the download page) I get the "E: No signature (5 files)" error. Can I generate a valid signature for the files?
its worth a try lol if that dont work then i really dont know whats wrong lol
So far I have tried the following files:
The following pass verification and I get to the "Installing update..." but I then instantly get an "Installation Aborted". No other error message as to why:
signed-kila-CRC1-from-CRB43-FIX.7ca4a1d7.zip
signed-kila-DRC83-from-CRC1.c41b93c1.zip
signed-kila-ota-148830.de6a94ca.zip
signed-PLAT-RC33-from-RC30.zip
signed-RC30-from-RC29-fat.1582cace.zip
The following I get a "No Signature" error:
signed-dream_gfh-ota-147201.6d1386de.zip
ota-radio-2_22_19_26I.zip
ota-radio-1_22_12_29.zip
ota-radio-1_22_14_11.zip
I did a Wipe data and Cache before each update.zip attempt and this was using the "Android system recovery <2e>" screen.
Ideas? I will look and see if I can add a signature to the radio files.
dont spose u flashed the recovery with clockworkmod recovery 2.5.0.7
too short
I have not been successful flashing anything to the phone so far. All this was done via the "Android system recovery <2e>".
I signed the radio files myself, but they came out identical and same issues occurred. No idea what the "No signature" error is. Seems like a bunch of people get it on the forums, but no solutions. No idea why the good updates suddenly abort.
forum.xda-developers.com/showpost.php?p=4647751&postcount=1
Unfortunatly that seems to require fastboot, adp, or a rooted phone. I tried installing another SPL and I keep getting the "No Signature" error.
wow man your having a tough ass time lol ill keep researching for ya
i think your home button maybe stuck lol
far to short
You know thats not a bad idea. It does actually boot into recovery mode without holding the home button like you are meant to. Would holding home when powering on prevent the boot loader from starting if I hold the camera button?
on my g1 if i hold home power and cam buttons i get the bootloader/fastboot menu
So I ordered a new battery for it today too. The phone does not seem to work too long without being plugged in. Maybe that will help.
I also managed to capture some pictures of the screens I have, so maybe that will assist people with diagnosing the issue.
The first is the rainbow screen I get when holding back on a reboot. It flashes for 1 second or so and then displays the white screen with blue text. The last pic is the recovery menu I have access to.
It looks like this is a fully stock phone, no flashes. I am going to keep trying to get into that bootloader screen. Getting into the rainbow screen works once every 20 tries or so. Maybe the bootloader is similar. Hitting send on the white screen does nothing and requires a battery pull to reset phone.
how long can you stay in the coloured menu for ?????? also what happens if you stay there like what options do you get???
I recently recieved a Nexus One that I cannot reflash at all. It simply will sit at the static X logo upon boot. I can still access the bootloader. Recovery does not work at all. I have tried to wipe and restore using fastboot, and whenever I try to write any images, they seem to push to the phone (progress indicator on phone fills up, etc) but I never get a finished message on the computer. I let it sit for half an hour before I gave up on it and pulled the battery. I have tried this with Windows 7 on a desktop and a MacBook Pro, using various different USB ports and cable combinations on them. I cannot do the PASSIMG.zip method either because the phone never seems verify the FRG83 image but will never offer me the Yes or No dialog to write out the files. It kicks back to the regular bootloader options.
Is this Nexus One bricked? Can I bring it back from the next-to-dead? Am I really just missing something obvious here?
By the way, have you unlocked the bootloader? Using fastboot to push anything requires unlocked bootloader.
The bootloader is unlocked.
Ok well this might be a stupid question but you said you were using windows 7 and with windows the extension is hidden so if you name the file passimg.zip it will actually be named passimg.zip.zip and the phone won't recognize it so try naming it passimg
Also for the passimg method did you try using the frg33 file instead of the frg83 file.
I have Windows set to show all extensions regardless. I would say I'm plenty savvy when it comes to computers, just not Android (yet )
I tried both the FRG33 and FRG83 files. They just don't seem to do anything. The phone seems to check them: It says that it found the PASSIMG.zip and the progress bar in the upper right slowly fills up. Once it fills, it sits for a second and just kicks back to the normal bootloader choices as usual.
Thank you for all the quick responses! I hope I can fix this Nexus One. It's practically in mint condition...
It's strange that the bootloader is unlocked but you can't flash any ROMs :/
When you say that recovery doesn't work at all what exactly do you mean by that? When you boot into recovery what happens?
Now since we talked passimg I doubt it will work more than the others but did you try the GRI40 file?
I cannot seem to find a GRI40 that can act as a passimg. And when I say recovery doesn't work at all I mean that I just proceed to the the static, non-moving nexus logo and it doesn't ever proceed past it. I have tried to use "fastboot boot recovery.img" with a ClockworkMod and Amon_RA image and it seems to upload to the phone but I just end up with the nexus logo.
It seems that I can fastboot erase the userimg and cache, and get results that are expected. When I fastboot flash anything it sends to the phone but the phone never seems to do anything with it past that point.
When it gets stuck on the static X logo do you get 7 vibrations?
Did you try and fastboot flash Amon-RA then try and reboot into recovery. And for the GRI40 file it's on htc's developers web site http://developer.htc.com/
I only get one vibration. I tried to flash Amon_RA and reboot but it's like the flash never completes. I don't get anything different.
same issue here and browsing since yesterday for a proper solution and not yet !! any brave ideas ,pls share!
OverdrivenCore said:
I only get one vibration. I tried to flash Amon_RA and reboot but it's like the flash never completes. I don't get anything different.
Click to expand...
Click to collapse
Try fastboot erase to erase everything on the phone then flash fresh recovery
Sent from my Nexus one using xda app-developers app
Kind of in the same boat, opened a thread my self but none of the suggestions are working. When im in fast boot it freezes for a second a runs a quick check. I just about catch it saying wrong passimg image or something along them lines.
Sent from my GT-I9100 using xda premium
Hello my lovely Nexus family,
I need your help! I've searched all over the web and these forums, and have yet to find a single thing that would help me.
After making a stupid mistake from tinkering, my phone was stuck on the "Google" screen. Not a big deal, just a simple wipe and fresh flash (and yeah, that's what I wanted anyways), right? So I went straight to Wugfresh's Nexus Root Toolkit to full wipe. It did the whole process of flashing MRA58R to the phone until I got to "sending sparse 'system'" on the terminal window. "Fastboot.exe has stopped working. Windows is finding a solution....." suddenly appeared while the terminal was processing everything. When the phone decided to reboot after thinking it had finished, it came back with the "Phone Corrupt" message.
I don't know what to do, as this is the 9,999th time I've flashed a phone, and I've never seen this before (obviously) so I'm not really sure what to do.
If I'm missing any details, which I feel I am, do not hesitate to ask.
May be obvious no... But you didn't actually say...
Will phone boot into fastboot if you have it powered off, the first pressing and holding volume down, then pressing and holding power until the phone boots?
scryan said:
May be obvious no... But you didn't actually say...
Will phone boot into fastboot if you have it powered off, the first pressing and holding volume down, then pressing and holding power until the phone boots?
Click to expand...
Click to collapse
Yes, I'm able to boot into fastboot with the phone powered off using the physical buttons. I'm also able to get working commands from the terminal.
Then what is the issue? Flash The image manually, re-install fastboot if needed... Or better yet download the image from google manually, check MD5, extract the main zip, as well as the update zip inside... using the fastboot that comes with it to flash all partitions?
One flash went wrong... So ok try again. And don't use the toolkit so you can actually follow whats going on (and because the only posts with troubles seem to be from people using toolkits)
scryan said:
Then what is the issue? Flash The image manually, re-install fastboot if needed... Or better yet download the image from google manually, check MD5, extract the main zip, as well as the update zip inside... using the fastboot that comes with it to flash all partitions?
One flash went wrong... So ok try again. And don't use the toolkit so you can actually follow whats going on (and because the only posts with troubles seem to be from people using toolkits)
Click to expand...
Click to collapse
I've done more than one flash today. My next will make 20 in the same hour with failed results. I'll try flashing the bits of the file manually and see how that works.
It could even be the computer I'm using. I'll report back soon.
Are you using the same fastboot.exe every time and getting the same error? Did you verify MD5
So, I got home, hopped on my laptop and got to work as usual. I used the factory provided cable and the problem was solved. I believe it has something to do with either the cord I was using to transfer the data, or the computer I was using.
Other than that - PROBLEM. SOLVED.
If the fastboot exe was fail ("stopped working") the cable was less likely the issue, most likely just the binary on that computer.
Perfect example of why not to use a tool kit until "after" you know how to do it manually.
okay, i had a slim rom running on my fire (5.1.1) and tried to go to cm12 using flashfire. i made sure that wipe was at the top of the list. it got stuck on installing the new rom, so after 30 minutes i restarted tablet. i got stuck in the cm logo bootloop. i do still have access to the amazon stock recovery. tried to do a data wipe/factory reset. still stuck at logo bootloop. i tried to sideload the amazon stock bin file, but it stops after 5 seconds and says "failed to read command: invalid argument" and goes back to the recovery main menu. if you try to do another sideload, it instantly says "timed out waiting for package. installation aborted" before you even press anything. have to restart device to try sideloading again.
at one point i had it almost install cm12 from a zip file through sideload, but at the very end it gave me a signature verification fail. since i can't boot the phone, i can't turn on usb debugging. sometimes it'll show up in the device manager as mtp but never shows up as fire or android device or any of that. it will show up on adb devices command when its in fastboot, but can't do anything with it from there. i've tried all the different ways in the forums here and rootjunky, but nothing seems to work at all. any ideas if i'm doing something wrong or is this just bricked, regardless of stock recovery?
tried a few commands to see if i could fastboot one of the roms or stock images, but they all tell me its missing the android-info.txt
dorkydroid said:
okay, i had a slim rom running on my fire (5.1.1) and tried to go to cm12 using flashfire. i made sure that wipe was at the top of the list. it got stuck on installing the new rom, so after 30 minutes i restarted tablet. i got stuck in the cm logo bootloop. i do still have access to the amazon stock recovery. tried to do a data wipe/factory reset. still stuck at logo bootloop. i tried to sideload the amazon stock bin file, but it stops after 5 seconds and says "failed to read command: invalid argument" and goes back to the recovery main menu. if you try to do another sideload, it instantly says "timed out waiting for package. installation aborted" before you even press anything. have to restart device to try sideloading again.
at one point i had it almost install cm12 from a zip file through sideload, but at the very end it gave me a signature verification fail. since i can't boot the phone, i can't turn on usb debugging. sometimes it'll show up in the device manager as mtp but never shows up as fire or android device or any of that. it will show up on adb devices command when its in fastboot, but can't do anything with it from there. i've tried all the different ways in the forums here and rootjunky, but nothing seems to work at all. any ideas if i'm doing something wrong or is this just bricked, regardless of stock recovery?
tried a few commands to see if i could fastboot one of the roms or stock images, but they all tell me its missing the android-info.txt
Click to expand...
Click to collapse
try stock 5.1.2 firmware
otherwise there is no fix that I know of
Sent from my KFFOWI using XDA Labs
i started trying to get it going, but got the same results. eventually the battery died and it doesn't want to charge anymore, so hopefully i'm still under warranty. thanks for all the help though, been a reader here for a really long time. just sucks to get a hard brick for the first time. used a droid x for four years straight with a locked bootloader and never came across a problem like this
dorkydroid said:
i started trying to get it going, but got the same results. eventually the battery died and it doesn't want to charge anymore, so hopefully i'm still under warranty. thanks for all the help though, been a reader here for a really long time. just sucks to get a hard brick for the first time. used a droid x for four years straight with a locked bootloader and never came across a problem like this
Click to expand...
Click to collapse
I fear I'm in the same boat. Which version of flash fire were you using?
Any further progress?
Sent from my Nexus 7 using XDA-Developers mobile app