[Q] need assistance with possible bricked evo - EVO 4G Q&A, Help & Troubleshooting

I've been working on this issue for the last few days, with no luck and I wanted to see if this community could help. I'll break down what is happening, what I've tried and which resources I've used. First and foremost I've read the beginners FAQ here and a how to recover here as well as the basics of ADB here.
The problem started while trying to mount SD storage from within CWM recovery. It was working fine until it said "can't mount sd card" and would not allow me access to the SD card either from within recovery or from within the phone.
Now my phone seems to be stuck in a boot loop. It pulls up the boot image and vibrates for about 5 seconds then the screen goes dark. It procedes to loop this process over and over until a battery pull is initiated. This occurs when trying to load normally and when trying to load into CWM recovery. I am able to get into the bootloader if I hold volume down and power. The only way I am able to boot my phone is by going into the bootloader, selected fastboot, opening up a command prompt, typing "fastboot oem enableqxdm 0" then "fastboot reboot". It will then load. It appears to prepare the SD card but I am not able to mount it. If I attempt to then boot into recovery I am unable to access the SD card.
From what I've read, it is recommended to re-flash the recovery (to restore my ability to mount SD storage) but since I am unable to mount the storage I an unable to do so. I have also tried to flash a new recovery image from ADB but I get the following error. FAILED (remote: signature verify fail). I tried to type "fastboot oem unlock" which some posters say works but it did not. Another fix is booting the recovery img via fastboot but that failed as well.
I'm sure I left something out or you have questions. Please ask.
Any help is greatly appreciated.

This is probably a dumb question, but have u ruled out a bad SD card.

fitz420 said:
This is probably a dumb question, but have u ruled out a bad SD card.
Click to expand...
Click to collapse
Swapped out the SD card with a fresh one. No dice.

I have also tried to reflash PC36IMG from HBOOT and it continues to loop.
I also tried to recover with RUU and it gives me a low battery warning (the battery is at 98%).
I'm starting to think this is totally bricked....

I'm still hoping for an update on this if anyone can.

You need to install a new recovery. CWM doesn't play nicely, Amon Ra 2.3 is the best evo recovery there is. Just search it.
Flash Amon Ra, boot into it wipe cache and dalvik cache, and see if you can boot into your rom.
If not, wipe cache dalvik cache and system and re flash the rom you were on and it should restore with all of your data.
Last, but not least, wipe everything and start from scratch.
A fresh partition on the sd card is always helpful and be sure to wipe cache, dalvik cache, data, system and boot.
Sent from my PC36100 using xda premium

I downloaded and installed Amon RA using these directions to a T.
Still bootlooping the Evo splash screen.
I can't even get into a recovery screen. I can only get to HBOOT or it loops.

Can you give some more info? What is your bootloader version?
S-off?
Have you formatted your sd card?
Sent from my PC36100 using xda premium

*** UNLOCKED ***
Supersonic EVT3 SHIP S-ON
HBOOT-2.18.0001
MICROP-041f
TOUCH PANEL-ATMEL224_16ab
RADIO-2.15.00.12.19
Dec 21 2011, 12:50:32
I have done a full format on my SD card to FAT32.

You might try this method, starting at step 28:
http://forum.xda-developers.com/showthread.php?p=22013438
This will take you back to froyo and be able to root with unrevoked.
I think something is corrupted, and since you are on the latest versions when you run RUU nothing actually updates...
Just a thought let me know
Sent from my PC36100 using xda premium

TheTitleist said:
*** UNLOCKED ***
Supersonic EVT3 SHIP S-ON
HBOOT-2.18.0001
MICROP-041f
TOUCH PANEL-ATMEL224_16ab
RADIO-2.15.00.12.19
Dec 21 2011, 12:50:32
I have done a full format on my SD card to FAT32.
Click to expand...
Click to collapse
you are still s-on.
ropodope
Here's to your thin red line. Hmm... I'm stepping over.

I am unable to access an ADB shell, only fastboot. I tried to update my drivers (seems to be issues with getting to the ADB shell are driver related) but I am unable to. My phone does not show up in my device manager when plugged in.
I have placed those files on the root of my SD card using a card reader but without being able to find my device in ADB I cannot proceed any farther.

ropodope said:
you are still s-on.
ropodope
Here's to your thin red line. Hmm... I'm stepping over.
Click to expand...
Click to collapse
How does that create the bootloop?

Kind of hard to utilize recovery very well, flash kernels or updates your radios if you are.
ropodope
Here's to your thin red line. Hmm... I'm stepping over.

TheTitleist said:
How does that create the bootloop?
Click to expand...
Click to collapse
here's the deal no one wants to tell you but I will. You have corrupted one of your main partitions. Ruu back to stock. This will force a format and repartition of all of your partitions like when you first got your phone. Now reroot your device and flash to your hearts' content.
ropodope
Here's to your thin red line. Hmm... I'm stepping over.

The problem with that is I am unable to use RUU.
I get an error that claims my battery level is below 30% but I am fully charged.
Any suggestions how to combat that?

TheTitleist said:
The problem with that is I am unable to use RUU.
I get an error that claims my battery level is below 30% but I am fully charged.
Any suggestions how to combat that?
Click to expand...
Click to collapse
yes, get an ruu that lets you flash it from the bootloader. They have them a plenty at goo for example. Rename PC36IMG.zip (without the .zip in the title if naming from windows since the .zip is already assumed). Place in the root of your sd card and boot into bootloader. let it load up and apply that mother. If you can get to your bootloader you aren't bricked.
ropodope
Here's to your thin red line. Hmm... I'm stepping over.

Looks like that may have done it.
I appreciate the help!

TheTitleist said:
Looks like that may have done it.
I appreciate the help!
Click to expand...
Click to collapse
absolutely bro. I'm glad to help. Way to stick with it!
ropodope
Here's to your thin red line. Hmm... I'm stepping over.

Related

Oops, I've deleted / formatted...

I seemed to have trouble with my phone on certain bugs in using alot of different roms, switching, testing, etc...Now I completely deleted everything off my phone by accident and was wondering if I can get back my screen?
I'm stuck on HBoot when I turn on phone, It has no rom, no recovery, no system, no data, and this basically happened due to me trying to wipe CM6 RC 6.1 ROM with snapKernel 7.6 loaded and on.
I did wipe data/cache/dalvik but it didn't allow me to roll my phone on Myn's latest rom.
I tried re-installing adb and variables / drivers / but I got nothing.
I think it's basically because I'm having this trouble due to having no files loaded on my android EVO 4g.
Here are the specs read from the Hboot screen
SUPERSONIC EVT2-3 ENG S-OFF
HBOOT-0.76.2000 (PC3610000)
MICROP-041f
TOUCH PANEL-ATMEL224_16ab
RADIO-2.5.00.09.01
Mar 30 2010, 11:24:04
HBOOT
Click to expand...
Click to collapse
Here's what I do remember and what I can say about my phone atm...
I did wipe sdcard by using format, and using the format on all other options too from recovery but now I have no files, how do I put back the files I'm missing to run my phone to normal?
Yes my phone is rooted. No, I don't think it's bricked.
Just missing complete files to my phone's system / data / etc
Nice... yeah if you deleted / (the root directory) that's never a good idea. In my sig is a link to Amon_RA's recovery where he has instructions on how to flash it with fastboot. After you do that you should be able to flash a ROM like normal.
Thank for your reply, I'll give it a start and let you know.
No, it's not working, I think I bricked my phone completely, It has just a Hboot screen with no files...zzz I'm not sure if that's understood or not, but I formatted the whole sd card and looks like theres nothing in this phone?
Edited: I think I have no device seen by my pc, and It shows error: devices not found ;(
alekosy said:
No, it's not working, I think I bricked my phone completely, It has just a Hboot screen with no files...zzz I'm not sure if that's understood or not, but I formatted the whole sd card and looks like theres nothing in this phone?
Edited: I think I have no device seen by my pc, and It shows error: devices not found ;(
Click to expand...
Click to collapse
from the hBoot menu select Fastboot. You should be able to see it over USB afterwards
I was doing that but it still doesn't see my device. I'll give it an another try
Okay, It worked.
Here's what I did.
I downloaded the file recovery-RA-evo-v1.8.0.img and flashed it with the command in fastboot on cmd.
im now in recovery, how do i put my myn's rom and the king's 11 cfs kernel in there to make it work now?
Edited: I now see the USB - MS toggle function feature, very nice Amon Recovery saved my phone ;D ty
yw, If you push the files to your sd card amon_ra should see them. Also be sure to dismount/eject your SD card from your computer before leaving MS mode in the recovery, I've noticed it can corrupt your card if you cancel out while it is still writing to it.
Thank you for the help Haus, I appreciate the sincere generosity.
I think my phones back now after flashing up my new rom and kernel, plus goodies
It feels brand new.
/Close pls

[problem] desire restarting after cyanogen flash

Heya,
I was using the LeeDroid ROM until today, when I desided I want Cyanogen.
I backed up the phone using ROM Manager, wipe and flashed Cyanogem 6.1 RC2. The phone restarted, turned on - but it cn't load the actual android OS - just keeps restarting on the blue wheel-thing animation.
I can boot my phone into recovery, but can't do much from there since its S-ON.
The recovery windows says:
bravo pvt1 ship s-on
hboot-0.80.0000
microp-031d
touch panel-synt0101
radio-5.10.05.23
fastboot
recovery
clear storage
simlock
what can I do to get my phone working again? Will a simple restore using HTC software do the trick (followed by root with unrevoked)?
Thanks
CoreOxide said:
Heya,
I was using the LeeDroid ROM until today, when I desided I want Cyanogen.
I backed up the phone using ROM Manager, wipe and flashed Cyanogem 6.1 RC2. The phone restarted, turned on - but it cn't load the actual android OS - just keeps restarting on the blue wheel-thing animation.
I can boot my phone into recovery, but can't do much from there since its S-ON.
The recovery windows says:
bravo pvt1 ship s-on
hboot-0.80.0000
microp-031d
touch panel-synt0101
radio-5.10.05.23
fastboot
recovery
clear storage
simlock
what can I do to get my phone working again? Will a simple restore using HTC software do the trick (followed by root with unrevoked)?
Thanks
Click to expand...
Click to collapse
Which version of Clockworkmod recovery did you fakeflash? There is an issue with the latest one that makes your SDcard unaccessible afterwards. It also mess up your USB.
Here is a thread that guides you how to fix it: http://forum.xda-developers.com/showthread.php?t=691639
I used the latest one, 2.5.1.7 I think.
Isn't there a way to restore the phone with the HTC software, sonething lite the iphone+itunes combo?
Is your sd card not being recognzed?
As you said you created a backup using rom manager before you flashed the new rom. So why dont you just enter hboot, go to recovery and the restore youre phone to the backup that you made using rom mabager before you flashed?
When I select "recovery" using the HBOOT I get a picture of a phone, and a red triangle with an exclamation mark. Does this mean I have to do the USB brick fix?
hmmm thats odd ... sounds like it could be a usb brick related issue, im not sure as i havnt had the same problem before or seen anyone else in the forum experiencing this problem.
I think you should read up more about the usb brick fix, hopefully there is something there that would be able to help you ... if its already known that the latest version of clockworkmod does give this problem then im sure its this and you would be able to find a solution to this problem.
Good luck
UPDATE:
My bad, I was supposed to press volumeup+power to see the recovery screen.
Now, when I do that I get "E:Can't open /cache/recovery/command", and get only 4 options:
reboot system now
apply sdcard:update.zip
wipe date
wipe cache
Is this related to the USB BRICK thing?
You need to wipe data when switching roms, this will fix the bootloop.
I would also suggest you flash a permanent recovery for ease of use. You need to use unrevoked to do this.
CoreOxide said:
UPDATE:
My bad, I was supposed to press volumeup+power to see the recovery screen.
Now, when I do that I get "E:Can't open /cache/recovery/command", and get only 4 options:
reboot system now
apply sdcard:update.zip
wipe date
wipe cache
Is this related to the USB BRICK thing?
Click to expand...
Click to collapse
This is the default android recovery screen. The error "E:Cant open...." is something I also get.
Do you have an update.zip on your SDcard? Like the clockworkmod recovery? http://forum.xda-developers.com/showthread.php?t=839640Use 2.5.0.7 and not 2.5.1.2 (has the fail you most likely see now). If correct update.zip on SDcard, try to press apply sdcard. If youre able to do so, you are accessing your sdcard. If youre getting problems applying this update file. I suggest following the thread I told you in my first post You then have to make your SDcard accessible with a fastboot command.
You are accessing fastboot by holding vol down while powering your phone on. Select fastboot. Plug your USB. Download the Android SDK or only fastboot.exe. Run this command from cmd: "fastboot oem enableqxdm 0". You should get a return command like "okay", and your SD card should be accessible again. Now you will need to follow the guide and fix your USB. However, you should be able to flash a new ROM now when your SDcard is accessible again, or just restore the nandroid backup that gave you this problem to begin with
Update: post #30, weee!
jmelhus said:
This is the default android recovery screen. The error "E:Cant open...." is something I also get.
Do you have an update.zip on your SDcard? If so try to press apply sdcard. If youre able to do so, you are accessing your sdcard. If youre getting problems applying this update file. I suggest following the thread I told you in my first post You then have to make your SDcard accessible with a fastboot command.
Click to expand...
Click to collapse
When i select that I get "E; failed to open sdcard\update.zip (no such file or directory)
E: signature verification failed"
Does this simply mean I don't have that file on my card?
If so, is there a way to access the card in mass storage mode while the phone is in HBOOT?
CoreOxide said:
When i select that I get "E; failed to open sdcard\update.zip (no such file or directory)
E: signature verification failed"
Does this simply mean I don't have that file on my card?
If so, is there a way to access the card in mass storage mode while the phone is in HBOOT?
Click to expand...
Click to collapse
Do you have a mem reader for windows/linux? Look if you have the file or not. If you don't have it, copy it there. If it's there, you have a problem with accessing the SDCard.
I would say, If I were you, I would try to "repair" the SDcard with the fastboot command first. Most likely, your ROM will boot again when it can read from your SDcard.
Other options would be to try to push the update file with ADB in Android Recovery. Most likely you can't push it either since your SDcard most likely is inaccessible. Try fastboot
Download Android SDK for Windows here: http://dl.google.com/android/android-sdk_r07-windows.zip
MD5: 69c40c2d2e408b623156934f9ae574f0
Unzip the file. Open CMD, navigate to the tools folder in SDK. Issue the command.
Source: http://developer.android.com/sdk/index.html
I ran the SDcard fix on CMD, it said "OKAY", but nothing changed in the phone's condition.
I put the SDcard on a card reader and saw there are backup files (.img) in the clockworkmod directory. how do i get the phone to recover from them?
The "update.zip" file, where can i get that one?
CoreOxide said:
I ran the SDcard fix on CMD, it said "OKAY", but nothing changed in the phone's condition.
I put the SDcard on a card reader and saw there are backup files (.img) in the clockworkmod directory. how do i get the phone to recover from them?
The "update.zip" file, where can i get that one?
Click to expand...
Click to collapse
You can get your update.zip file from here: http://forum.xda-developers.com/showthread.php?t=839640
Download the 2.5.0.7 zip file and rename to update.zip. Put on root of SDcard and apply sdcard: update.zip in android recovery. From here, go to nandroid, restore, and select your backup.
Doesn't the Update.zip file suppose to be a zipped ROM?
Not necessarily. A zip can flash a lot of different things. I'm not that much into it. But it all depends on the content of the zip file.
How do I " go to nandroid"?
CoreOxide said:
How do I " go to nandroid"?
Click to expand...
Click to collapse
Don't remember what it's called exactly. But when running update.zip (clockworkmod), you should have a restore menu somewhere...
Thanks a lot man! recovering right now.. will update when done.
About that S-ON thing, will the Unrevoked reflash option "Remove phone security" take care of this? Is there a risk in re-rooting?
I want to add some notifications sounds and the "system" folder is write protected
EDIT:
The restore works just fine!

[Q] Please Help! "cleared storage" now stuck.

Hello any help will be appreciated, sorry if there is another post already dealing with this issue.
I recently installed Virus Rom Kingdom Rev. .02 and it was running really slow. I restarted it through the power down feature, and now my phone would not boot past the "HTC EVO 4G" startup screen. I rebooted into recovery, however it kept kicking me out of the recovery and back to Fastboot. After some time of frustration, i "cleared storage". Now phone goes from "HTC EVO 4G" screen to a screen that flashes ANDROID slowly and does not go beyond that. How if at all can i recover from this issue.
These are my particulars:
sUPERSONIC evi2-3 eng s-off
HBOOT-0.76.2000
MICROP-041f
Touch panel- ATMEL224_16ab
Radio 2.15.00.11.19
Mar 30 2010, 11:24:04
When fastboot runs its very fast but states very often.....NO IMAGE
Please help me,
JD
Reflash RA recovery in fastboot, reinstall Rom
so do I place the RA Recovery file on my SD via computer, reinsert then run fastboot?
Affirmative, the pc36img.zip one, not the recovery.img
Place on the root of your sdcard, then boot into the bootloader, apply the update, reboot, reboot into recovery, and you'll be on amon_ra 2.3.
When I downloaded and put on root of SD card, it won't check for the update in bootloader. Any advice?
shades333 said:
When I downloaded and put on root of SD card, it won't check for the update in bootloader. Any advice?
Click to expand...
Click to collapse
Did you rename it?
It doesn't do its normal scan?
No I didn't rename it. Should it be update.zip ?
No its not even checking for it now. It's weird.
Pull battery and hold volume down and power, there is a difference between the white fastboot screen and the hboot bootloader screen, although they do look very similar.
Once in fastboot, how do I get it to scan for update? It's not doing it automatically.
Nevermind, the SD card must have shifted. It's working now. Thank you for all your help.

[q] need help asap!!!!

OK SO, I DONT THINK IM A NOOB, BUT APPARENTLY I AM. MY HTC EVO 4G IS ROOTED, AND IM RUNNING CM7. FOR SOME REASON MY RADIO HAS BEEN ACTING UP. MY CALLS DONT GO OUT, AND MY FRIEND SAYS MY PHONE WOULDNT RING AT ALL. I TRIED TO BACKUP, RESTORE, AND EVEN HARD RESET MY SUPERSONIC. NOW, IM STUCK AT THE BOOT SCREEN. IVE WIPED THE DELVIK, THE DATA, AND THE PARTITION. NOTHING. IT WONT LOAD PAST THE ORIGINAL HTCEVO SCREEN. I DONT KNOW WHAT TO DO. ALLL I REALLY CAN ACCESS IS THE BOOTLOADER, AND RECOVERY. IN RECOVERY, MY SD-EXT WONT LOAD, I CANT CREATE A BACKUP, AND I CANT RESTORE. WELL I CAN, BUT I CANT MAKE IT PAST THE BOOT SCREEEEEEEEN. HELP PPLS. PLEASE.
Click on amonRA in my signature to download its PC36IMG.zip file and place it on the root of your SD card (not in any folder). Turn off your device. Now simultaneously press the DOWN volume button and the power button until your device starts. After a short pause, a few lines of text will flash across the screen. Look at the top of the screen and see if it says "S-OFF". Hopefully, it does. If it displays "S-ON" then you will need to re-root. Anyway, the bootloader *should* auto-detect the file and prompt you to install it. Follow the prompts to install. Installation should take no more than 10 seconds. When it is complete, select recovery from the available options on the left side of the screen. If all went well, you should boot into your new recovery. If so, go to the wipe menu and wipe EVERYTHING in it EXCEPT the SD card. After that, try to flash a rom. Do not attempt to restore a nandroid backup unless your backups were created with amonRA. If you are able to flash a rom, be very patient during the initial boot. It may take a while. Let it finish. Get your mind set to wait 30 minutes even though it shouldn't take that long.
Posting & Replying from my EVO 4G
dougjamal said:
Click on amonRA in my signature to download its PC36IMG.zip file and place it on the root of your SD card (not in any folder). Turn off your device. Now simultaneously press the DOWN volume button and the power button until your device starts. After a short pause, a few lines of text will flash across the screen. Look at the top of the screen and see if it says "S-OFF". Hopefully, it does. If it displays "S-ON" then you will need to re-root. Anyway, the bootloader *should* auto-detect the file and prompt you to install it. Follow the prompts to install. Installation should take no more than 10 seconds. When it is complete, select recovery from the available options on the left side of the screen. If all went well, you should boot into your new recovery. If so, go to the wipe menu and wipe EVERYTHING in it EXCEPT the SD card. After that, try to flash a rom. Do not attempt to restore a nandroid backup unless your backups were created with amonRA. If you are able to flash a rom, be very patient during g the initial boot. It may take a while. Let it finish. Get your mind set to wait 30 minutes even though it shouldn't take that long.
Posting & Replying from my EVO 4G
Click to expand...
Click to collapse
for some reason, i cant place the img on my sd card? its odd but its saying "insert a disk into drive E" unless im doing it wrong, im not sure i can place anything on my sd card without selecting "turn on usb storage" or is there? thanks for the help so far. just a few more tips and ill be on my way.
Can you get to the bootloader and then into recovery from there? If so, then disregard trying to flash amonRA right now. If you can, then select the MS-USB option or its equivalent if your recovery is ClockworkMod to copy a rom or any other file onto the card.
Posting & Replying from my EVO 4G
yea i can. but ive done all. wiped all, and nothing. what EXACTLY should i do?
Since you're able to get to recovery (I am assuming it's ClockworkMod), go to my initial reply and follow the instructions to flash amonRA v2.3 and everything else I stated. In the meantime, I'm going to locate a ruu for you to flash via your PC that *should* get you up and running. By the way, when you boot into the bootloader, what is the hboot version that is listed at the top of the screen?
Posting & Replying from my EVO 4G
dougjamal said:
Since you're able to get to recovery (I am assuming it's ClockworkMod), go to my initial reply and follow the instructions to flash amonRA v2.3 and everything else I stated. In the meantime, I'm going to locate a ruu for you to flash via your PC that *should* get you up and running. By the way, when you boot into the bootloader, what is the hboot version that is listed at the top of the screen?
Posting & Replying from my EVO 4G
Click to expand...
Click to collapse
supersonic evt3 ship s-off
hboot-2.10.0001
microp-041f
touch panel-atmel224_16ab
radio-2.15.00.11.19
oct 15 2010, 12:07:00
and as far as the amon-ra, i cant put it on my sd card at all. so im not sure how to update. man, i thought i knew about all this stuff from a siimple root, rom, and bootloader. guess i still suck i appreciate your help and patience. thank you.
If your hboot is version 2.10, then download the first RUU listed on THIS page. Connect your device via USB to your PC and then initiate the file. I'm preparing for bed. Take care.
Posting & Replying from my EVO 4G
Do u have any way of putting the PC36IMG on the SD card with your computer. Like a SD card adapter or anything? If so take the SD card out of.your phone and try to put the IMG file on it that way
Sent from my PC36100 using XDA Premium App
If u have Clockwork, u can mount the sdcard while in recovery.
Or use another phone to place the img file in the sdcard.
Sent from my PC36100 using XDA Premium App

Can get to HBOOT, but dead end from there...

Hi,
I have a Droid Incredible (Verizon) that won't boot. I think it's toast, but wanted to list the things that I've done to see if there are any folks out there that think I may have another option besides selling it for parts.
***History***
1. I had no intention of ever rooting the phone, but the stupid "phone storage low" issue caused me to install clockworkmod and superuser so that I could resize the partitions for data/data (or so I believed at the time). In hindsight I never actually got S-OFF, and it's possible that this is where things went wrong.
2. Anyways, one day a few weeks ago after an OTA update from VZW and a reboot, the phone started looping and has never since booted back into the OS. I'd get the black and white "htc Incredible" screen, then the loud "DROID" sound, rinse and repeat. The behavior would change somewhat depending on whether I had the external SD installed or not, but regardless, the phone would never boot up. I tried a bunch of things I found on various forums, but nothing has worked. The current behavior is that the device just sits at the black/white "htc Incredible tm" screen upon boot .
***Things I've Tried***
1. I can get into HBOOT and managed to unlock the bootloader, but from there, I can't get it to factory reset and I can't get it to load any other firmware (likely because I'm still S-OFF). I've got clockworkmod installed, and when I try to install any new Roms from there, I get a bunch of errors:
E: Invalid command or argument
E: Can't mount /cache/recovery/log
E: Can't open /cache/recovery/log
E: Can't mount /cache/recovery/last_log
E: Can't open /cache/recovery/last_log
Anything I try to do in Clockworkmod errors out (wipe data, show log, install zip from SD, etc.). Either I get an error that the dir can't be mounted or the file can't be found.
2. I've also re-deployed the RUU (PB31IMG.zip), but it didn't work. I got to the "Loading… [PB31IMG.zip]" screen where it hung for a few minutes as the blue bar crept up, but then it flashed a message saying "No image or wrong image!" and kicked me back to the HBOOT menu again without asking me if I want to upgrade. I then go to FASTBOOT and hit REBOOT, and then it sent me back to the black/white "htc incredible" screen where it once again hangs and won't boot the OS.
3. Oddly, whenever I load anything on the external SD card and then put it on the phone, the phone will read the SD card once, but then seems to corrupt the file. If I put the SD card back in my Win7 machine, it always tells me the card needs to be formatted again. I re-format it to Fat32 and try again, but the cycle just repeats. I've tried 4-5 different SD cards that work fine in other devices, but the behavior is always the same. So I'm sure the SD cards are not the issue.
***Help!***
Does anyone have any ideas on what I can do to troubleshoot from here? I've spent hours on this and am about to give up and declare this phone no longer worthy of my time, but I figured I'd check here first.
This could all stem from the fact that I'm still S-ON, but I thought I'd at least be able to flash back to factory.
Here's what my HBOOT screen displays (notice that the bootloader is unlocked, but I'm still S-ON)
*** UNLOCKED ***
INCREDIBLEC XD SHIP S-ON
HBOOT-1.02.0000
MICROP-0417
TOUCH PANEL ATMELCO3_16ac
RADIO-2.15.10.07.07
Dec 21 2011, 23:37:16
Thanks!
BigEdgar said:
Hi,
I have a Droid Incredible (Verizon) that won't boot. I think it's toast, but wanted to list the things that I've done to see if there are any folks out there that think I may have another option besides selling it for parts.
***History***
1. I had no intention of ever rooting the phone, but the stupid "phone storage low" issue caused me to install clockworkmod and superuser so that I could resize the partitions for data/data (or so I believed at the time). In hindsight I never actually got S-OFF, and it's possible that this is where things went wrong.
2. Anyways, one day a few weeks ago after an OTA update from VZW and a reboot, the phone started looping and has never since booted back into the OS. I'd get the black and white "htc Incredible" screen, then the loud "DROID" sound, rinse and repeat. The behavior would change somewhat depending on whether I had the external SD installed or not, but regardless, the phone would never boot up. I tried a bunch of things I found on various forums, but nothing has worked. The current behavior is that the device just sits at the black/white "htc Incredible tm" screen upon boot .
***Things I've Tried***
1. I can get into HBOOT and managed to unlock the bootloader, but from there, I can't get it to factory reset and I can't get it to load any other firmware (likely because I'm still S-OFF). I've got clockworkmod installed, and when I try to install any new Roms from there, I get a bunch of errors:
E: Invalid command or argument
E: Can't mount /cache/recovery/log
E: Can't open /cache/recovery/log
E: Can't mount /cache/recovery/last_log
E: Can't open /cache/recovery/last_log
Anything I try to do in Clockworkmod errors out (wipe data, show log, install zip from SD, etc.). Either I get an error that the dir can't be mounted or the file can't be found.
2. I've also re-deployed the RUU (PB31IMG.zip), but it didn't work. I got to the "Loading… [PB31IMG.zip]" screen where it hung for a few minutes as the blue bar crept up, but then it flashed a message saying "No image or wrong image!" and kicked me back to the HBOOT menu again without asking me if I want to upgrade. I then go to FASTBOOT and hit REBOOT, and then it sent me back to the black/white "htc incredible" screen where it once again hangs and won't boot the OS.
3. Oddly, whenever I load anything on the external SD card and then put it on the phone, the phone will read the SD card once, but then seems to corrupt the file. If I put the SD card back in my Win7 machine, it always tells me the card needs to be formatted again. I re-format it to Fat32 and try again, but the cycle just repeats. I've tried 4-5 different SD cards that work fine in other devices, but the behavior is always the same. So I'm sure the SD cards are not the issue.
***Help!***
Does anyone have any ideas on what I can do to troubleshoot from here? I've spent hours on this and am about to give up and declare this phone no longer worthy of my time, but I figured I'd check here first.
This could all stem from the fact that I'm still S-ON, but I thought I'd at least be able to flash back to factory.
Here's what my HBOOT screen displays (notice that the bootloader is unlocked, but I'm still S-ON)
*** UNLOCKED ***
INCREDIBLEC XD SHIP S-ON
HBOOT-1.02.0000
MICROP-0417
TOUCH PANEL ATMELCO3_16ac
RADIO-2.15.10.07.07
Dec 21 2011, 23:37:16
Thanks!
Click to expand...
Click to collapse
I would fastboot flash the stock recovery, do a factory reset from hboot, fastboot flash back to cwm recovery, and then see if you can get cwm to work correctly. Or try the ruu again after the factory reset.
cmlusco said:
I would fastboot flash the stock recovery, do a factory reset from hboot, fastboot flash back to cwm recovery, and then see if you can get cwm to work correctly. Or try the ruu again after the factory reset.
Click to expand...
Click to collapse
Thanks for the thoughts. I thought I'd already tried fastboot flashing the stock recovery with no success, but maybe I did something wrong?
Here's what I did:
1. Downloaded a recent copy of PB31IMG.zip
2. Via my Win7 machine, loaded PB31IMG.zip onto an SD card formatted as Fat32
3. Put the SD card in my Dinc
4. Boot into HBOOT
5. Select Fastboot
6. Fastboot finds the image, spends a few minutes loading it, but then errors out with "No image or wrong image!" message. Boo.
FWIW, I've only been able to get adb to recognize my device intermittently so adb isn't really an option (unless I can figure out
Am I doing something wrong?
BigEdgar said:
Thanks for the thoughts. I thought I'd already tried fastboot flashing the stock recovery with no success, but maybe I did something wrong?
Here's what I did:
1. Downloaded a recent copy of PB31IMG.zip
2. Via my Win7 machine, loaded PB31IMG.zip onto an SD card formatted as Fat32
3. Put the SD card in my Dinc
4. Boot into HBOOT
5. Select Fastboot
6. Fastboot finds the image, spends a few minutes loading it, but then errors out with "No image or wrong image!" message. Boo.
FWIW, I've only been able to get adb to recognize my device intermittently so adb isn't really an option (unless I can figure out
Am I doing something wrong?
Click to expand...
Click to collapse
That will only work if your s-off. With an unlocked bootloader you need to take that stock recovery pb31img.zip and extract the recovery.img file out with 7zip or the like. Place the img in the same folder on your pc as adb.exe and fastboot.exe. Boot to the bootloader and then on your pc open a cmd prompt to where fastboot.exe is. At the prompt type without quotes " fastboot flash recovery recovery.img ". Do the same thing to flash back to cwm.
cmlusco said:
That will only work if your s-off. With an unlocked bootloader you need to take that stock recovery pb31img.zip and extract the recovery.img file out with 7zip or the like. Place the img in the same folder on your pc as adb.exe and fastboot.exe. Boot to the bootloader and then on your pc open a cmd prompt to where fastboot.exe is. At the prompt type without quotes " fastboot flash recovery recovery.img ". Do the same thing to flash back to cwm.
Click to expand...
Click to collapse
Thanks again for the help - I really appreciate it.
I was able to get the recovery.img loaded:
\miniadb_inc>fastboot flash recovery recovery.img
sending 'recovery' (3514 KB)... OKAY [ 0.531s]
writing 'recovery'... OKAY [ 1.059s]
finished. total time: 1.604s
I then clicked on FASTBOOT --> RECOVERY and the phone rebooted. After reboot, I see the green arrows for a minute or so, and then... the red triangle with the exclamation point. Is that normal?
BigEdgar said:
Thanks again for the help - I really appreciate it.
I was able to get the recovery.img loaded:
\miniadb_inc>fastboot flash recovery recovery.img
sending 'recovery' (3514 KB)... OKAY [ 0.531s]
writing 'recovery'... OKAY [ 1.059s]
finished. total time: 1.604s
I then clicked on FASTBOOT --> RECOVERY and the phone rebooted. After reboot, I see the green arrows for a minute or so, and then... the red triangle with the exclamation point. Is that normal?
Click to expand...
Click to collapse
Ok, quick update. After getting the red triangle with the exclamation point, I did the following:
- Power button + Up Volume to get to the System Recovery menu.
- Selected "Wipe cache partition"
- Selected "Wipe data/factory reset"
The factory reset just errored out all over the place (see attached image). It's almost like the boot partition is the only partition that is readable on this phone, and the partition that contains the OS is completely hosed. This is pretty consistent with everything else I've seen. Anytime I try to factory reset or do anything else, the phone just throws a bunch of errors basically telling me it can't mount drives and can't find directories.
Upon reboot, the phone still just hangs at the black/white "htc Incredible" screen.
Any thoughts on where to go from here?
BigEdgar said:
Ok, quick update. After getting the red triangle with the exclamation point, I did the following:
- Power button + Up Volume to get to the System Recovery menu.
- Selected "Wipe cache partition"
- Selected "Wipe data/factory reset"
The factory reset just errored out all over the place (see attached image). It's almost like the boot partition is the only partition that is readable on this phone, and the partition that contains the OS is completely hosed. This is pretty consistent with everything else I've seen. Anytime I try to factory reset or do anything else, the phone just throws a bunch of errors basically telling me it can't mount drives and can't find directories.
Upon reboot, the phone still just hangs at the black/white "htc Incredible" screen.
Any thoughts on where to go from here?
Click to expand...
Click to collapse
This post seems to echo my current situation: http://forum.xda-developers.com/showthread.php?t=1487675 (unfortunately no solution). I'll do some more investigating to see if there's a way to confirm that the partition is borked...
BigEdgar said:
This post seems to echo my current situation: http://forum.xda-developers.com/showthread.php?t=1487675 (unfortunately no solution). I'll do some more investigating to see if there's a way to confirm that the partition is borked...
Click to expand...
Click to collapse
Instead of doing the factory reset from the recovery menu, try it right from the main hboot screen. If that dosent work it sounds like the data partition is is fubar.
Are you able to use adb now? If you can, i have another sugestion i came across in another thread. A guy said he could not access, format, or use his data partition. He claims he fixed it by adb pulling the file system from a working inc, and adb pushing the files to the borked inc, fixing it. If you can get adb to stay connected long enough to push the files it might be worth a try.
cmlusco said:
Instead of doing the factory reset from the recovery menu, try it right from the main hboot screen. If that dosent work it sounds like the data partition is is fubar.
Click to expand...
Click to collapse
Thanks again for the suggestions.
I tried that but it's pretty much the same results.
HBOOT--> Factory Reset --> Screen with green arrows --> Red triangle with Exclamation point --> - Power button + Up Volume to get to the System Recovery menu --> Reboot:
Phone hangs on the black/white "htc Incredible" splash screen
One other odd note - if I do this same factory reset process with the USB cable *unplugged*, the instead of hanging on the black/white splash screen, it just goes into an infinite loop (black/white splash screen --> HTC quietly brilliant screen --> droid eye --> back to the black/white splash screen). FWIW this isn't new behavior, I just forgot to mention it earlier. In fact this is what the phone started doing once Verizon pushed the OTA update that screwed up the phone in the first place (there are a number of threads on this over at HTC and VZW forums, but their solutions aren't working for me).
I think this thing is a brick. If anyone has any recommendations for tools that can be used to analyze the partitions on a phone that won't boot, let me know. Otherwise this thing is getting sold for parts : )
Ok, some more progress. Most importantly, I learned that adb has a shell! I obviously didn't RTFM well enough.
Anyways, with the shell I was able to verify that the partitions on the phone are accessible (at least from a Windows machine) and I can, in fact, write files to the device (using "adb push" to push files to /sdcard, for example). That's great as it proves that the storage on the device *is* accessible, but just not from CWM. I followed some instructions that I followed partially before (http://androidforums.com/incredible...ow-unlock-downgrade-achieve-s-off-htcdev.html) in an attempt to see if I could get S-OFF. This tutorial is nice because most of the actions are via adb and fastboot instead of using the UI on the phone, which I couldn't get to. I was able to do most of the work I needed to get S-OFF via adb instead of using CWM or some other recovery tool, which was key, since CWM always tells me that it can't read or write any partitions.
I was actually able to get Froyo installed and boot into it! That's the first time this POS has booted into anything in almost a month!!
Now to my current problem - the last few steps of the tutorial linked above require that I install superuser and unrevoked, and suggest that this be done via CWM. Unfortunately, CWM can't read any of my data partitions, so this doesn't work for me. Not many others seem to have this problem, so googling it doesn't turn up any help.
Is there any way I can use ADB to install superuser and unrevoked forever? I also have access to the UI via Froyo and could conceivably install apks as well.
Here are the instructions from the tutorial that don't work for me, as they rely on CWM:
******************
use the recovery menu on your phone to:
-wipe cache
-wipe dalvik cache
-install zip from sd card(chose your superuser file)
-install zip from sd card(chose your forever file)
******************
Those last two steps - install zip from sd card - are the ones that completely fail for me. CWM just gives me a bunch of "E:can't mount /sdcard/" errors.
If anyone has any ideas on how to install superuser and unrevoked using ADB, I'm all ears : )
Thanks!
So I know you have been going in circles but at least you can boot into froyo! Do you have a spare SD card though? If not try reformatting your current SD again. It could be that your SD card has just gone bad though so it might be worth borrowing one from a friend to find out. If you're booting into froyo though that should mean you have access to /data now so I think those troubles are behind you. You don't really need to flash superuser.zip if you're just planning on flashing a new rom though. Unrevoked forever is the s-off tool and since you're already on froyo (with the froyo radio) that is all you need!
Sent from my ADR6300 using xda app-developers app
nschiwy said:
So I know you have been going in circles but at least you can boot into froyo! Do you have a spare SD card though? If not try reformatting your current SD again. It could be that your SD card has just gone bad though so it might be worth borrowing one from a friend to find out. If you're booting into froyo though that should mean you have access to /data now so I think those troubles are behind you. You don't really need to flash superuser.zip if you're just planning on flashing a new rom though. Unrevoked forever is the s-off tool and since you're already on froyo (with the froyo radio) that is all you need!
Sent from my ADR6300 using xda app-developers app
Click to expand...
Click to collapse
Thanks for the thoughts. I've got like 5 SD cards, and I've been able to validate with my other Android phone that they are all good.
I agree that it's good to be on Froyo, but to be able to swap to a different ROM, I still need S-OFF. And the only way I can see to get S-OFF is to install unrevoked forever. And the only method that I can find for installing unrevoked forever is via Recovery, and CWM just doesn't appear to be able to see any of my disks, so I need a different option for installing unrevoked forever besides CWM. Maybe it's time to ditch CWM and try a different recovery tool. I suppose I'll give amon_ra a try and see if that changes anything. Or is there some other way to install unrevoked?
BigEdgar said:
Thanks for the thoughts. I've got like 5 SD cards, and I've been able to validate with my other Android phone that they are all good.
I agree that it's good to be on Froyo, but to be able to swap to a different ROM, I still need S-OFF. And the only way I can see to get S-OFF is to install unrevoked forever. And the only method that I can find for installing unrevoked forever is via Recovery, and CWM just doesn't appear to be able to see any of my disks, so I need a different option for installing unrevoked forever besides CWM. Maybe it's time to ditch CWM and try a different recovery tool. I suppose I'll give amon_ra a try and see if that changes anything. Or is there some other way to install unrevoked?
Click to expand...
Click to collapse
Try using unrevoked 3.22 pc program instead of the forever zip.
Download unrevoked http://dinc.does-it.net/Unrevoked/Unrevoked_3.22.exe, to your pc. Boot the phone and enable usb debugging if its not already. Do not plug the phone in yet. Run unrevoked, when it opens click file at the top and select custom recovery. Then download and select this file http://dinc.does-it.net/Guide_Root_New_Hboot/recovery.img, as the custom recovery. Then plug in the phone and continue by following the prompts. If all goes well, it will reflash the recovery and install su. You can then install busybox from the market.
cmlusco said:
Try using unrevoked 3.22 pc program instead of the forever zip.
Download unrevoked http://dinc.does-it.net/Unrevoked/Unrevoked_3.22.exe, to your pc. Boot the phone and enable usb debugging if its not already. Do not plug the phone in yet. Run unrevoked, when it opens click file at the top and select custom recovery. Then download and select this file http://dinc.does-it.net/Guide_Root_New_Hboot/recovery.img, as the custom recovery. Then plug in the phone and continue by following the prompts. If all goes well, it will reflash the recovery and install su. You can then install busybox from the market.
Click to expand...
Click to collapse
Thanks for the suggestion. I tried this a few times and while Unrevoked is reporting success, I'm still S-ON and BusyBox and ROM Manager report that I'm not rooted. Back in CWM, CWM still reports errors mounting all drives and is basically crippled. In addition to the "can't mount SD card" errors, I'm also seeing "E:cant mount /dev/block/mmcblk0p2" and "E:Can't mount /cache/recovery/command". Weird. Can't tell if the mount errors are causing my inability to root or my inability to root is causing the mount errors.
(I also tried using AmonRa and got the same "can't mount" blah blah issues). Time for a drink : )
There's a fix. I have a thread on it but the xda app is acting up. Tell u later once I'm home
Sent from my ADR6300 using xda app-developers app
---------- Post added at 10:05 PM ---------- Previous post was at 09:51 PM ----------
Here you go man
http://forum.xda-developers.com/show...php?p=14440621
And thats for amoled screens, if you have the newer SLCD you would have to do it blindfolded basically because the screen will go off
eljean said:
There's a fix. I have a thread on it but the xda app is acting up. Tell u later once I'm home
Sent from my ADR6300 using xda app-developers app
---------- Post added at 10:05 PM ---------- Previous post was at 09:51 PM ----------
Here you go man
http://forum.xda-developers.com/show...php?p=14440621
And thats for amoled screens, if you have the newer SLCD you would have to do it blindfolded basically because the screen will go off
Click to expand...
Click to collapse
Eljean - that link's a 404...
I'm viewing it right now...
Sent from my ADR6300 using xda app-developers app
---------- Post added at 04:03 PM ---------- Previous post was at 04:02 PM ----------
http://forum.xda-developers.com/showthread.php?t=14440621
Try again
Sent from my ADR6300 using xda app-developers app
eljean said:
I'm viewing it right now...
Sent from my ADR6300 using xda app-developers app
---------- Post added at 04:03 PM ---------- Previous post was at 04:02 PM ----------
http://forum.xda-developers.com/showthread.php?t=14440621
Try again
Sent from my ADR6300 using xda app-developers app
Click to expand...
Click to collapse
Thanks, but that link still fails for me. Is the title of the thread [HOW-TO] Fix 5 vibrate and black screen? This one works for me: http://forum.xda-developers.com/showthread.php?p=14440621 (p= instead of t= in the URL).
If that's the thread you're pointing to, then I read through the thread earlier today and was hoping that the fix for the SD card would help (running fastboot oem enableqxdm 0), but that didn't. I don't seem to have the problem about not being able to communicate with the phone using USB - USB connectivity is working when the phone boots into Froyo and I'm also able to use ADB in Froyo and Recovery.
Unfortunately CWM (or any other Recovery tool) still can't read any of my drives, and while Unrevoked claims to be successful, I'm still S-ON.
I'm still poking around for a solution, I'll reply back if I discover anything.
BigEdgar said:
Thanks, but that link still fails for me. Is the title of the thread [HOW-TO] Fix 5 vibrate and black screen? This one works for me: http://forum.xda-developers.com/showthread.php?p=14440621 (p= instead of t= in the URL).
If that's the thread you're pointing to, then I read through the thread earlier today and was hoping that the fix for the SD card would help (running fastboot oem enableqxdm 0), but that didn't. I don't seem to have the problem about not being able to communicate with the phone using USB - USB connectivity is working when the phone boots into Froyo and I'm also able to use ADB in Froyo and Recovery.
Unfortunately CWM (or any other Recovery tool) still can't read any of my drives, and while Unrevoked claims to be successful, I'm still S-ON.
I'm still poking around for a solution, I'll reply back if I discover anything.
Click to expand...
Click to collapse
But it also fixes the usb problem. Trust me I went thru the exact same thing and this fixed it
http://forum.xda-developers.com/showthread.php?t=695243
eljean said:
But it also fixes the usb problem. Trust me I went thru the exact same thing and this fixed it
http://forum.xda-developers.com/showthread.php?t=695243
Click to expand...
Click to collapse
I appreciate the thoughts, but I think we're talking about different issues here. One of your issues seemed to be that you couldn't access the device at all via USB. I don't have that problem. My USB connection has always been fine. My problem is that CWM can't mount the SD card (or any other drives, for that matter). Everything mounts fine in Froyo, so I'm guessing it has to do with the way the drives are mounted in Recovery vs. Froyo.
The thread you referenced stated that the fix for not being able to access the SDcard was the fastboot oem enableqxdm 0 fix. I tried that a few times but it didn't make any difference.
Thanks for the thoughts!

Categories

Resources