Related
I had rooted my phone and updated the radio to 1.47.651.1 when I tried to update a custom rom I accidently re-ran PC36IMG.zip and it rebooted quick NOW the radio says 1:39:00:04:26
and in the options below I now have
FASTBOOT
RECOVERY
CLEAR STORAGE
SIMLOCK
HBOOT USB
I tried putting the phone on FASTBOOT then connected it to the USB and began a stock rom not rooted and it boots my phone into an HTC Black screen Boot mode and begins to update until it comes to the signatures and it gives me an error.
I run windows 7
I went and tried this, connected sd card to Computer with adapter and transferred stock rom rooted and renamed it to sdcard.zip
booted Evo to bootloader and chose recovery.
I as usual got the black background with EVO Icon and red triangle with exclamation mark.
There I click on hold Volume Up and Power until I get the following error:
E:Can't open /cache/recovery/command
Then I click volume up and the following title and menu appear:
Android system recovery <2e>
reboot system now
apply sdcard:update.zip
wipe data/factory reset
wipe cache partition
When I choose the sdcard:update option the following message is displayed
----Install from Sdcard ------
Finding Update package
Opening update package
verifying update package
E:signature verification failed
instalation aborted
After, I downloaded tha froyo 2.2 file and placed it on the sd and rename it to update.zip
and when I ran Update.zip from bootloader it ran half way but then stopped saying the following error
failed to verify whole-file signature
So now I load any PC36IMG and I get NO QUESTION to update just puts me onto the bootloader screen….
Not bricked, just stuck. Download stock ruu, plug phone into computer and install. Or put pc136.img on rot of sd, boot into fast boot, it should install automatically. If none of the above, go to a sprint store, tell them it won't boot and you don't know why, and they will flash or replace.
Sent from my PC36100 using Tapatalk
What I would do from here if I were you is put that sd card back in the computer and erase everything on it.
while your at it shut down the phone. Hold down the volume down button and press power. When that comes up post what version of Hboot you have please.
And I'll be better able to help out.
WOw
did you try to reinstall another ROM?
if you still see the RECOVERY menu item, go there and then go where it says update from zip on sdcard. then using up/down buttons highlight the .zip file of the ROM then push the power button to make it run.
this hoping you got a ROM on your sdcard. if not just get one at the forum and download.
i got clockworkmod but im sure the other recovery tools have similar options.
@ adelaney Stock Ruu begins to update and gives me an error when signatures are being installed. I tried three Stock ROMS
RUU_Supersonic_1.32.651.1_Radio_1.39.00.04.26_release_171253
RUU_Supersonic_1.32.651.6_Radio_1.39.00.05.31_release_171253_signed
RUU_Supersonic_1.47.651.1_Radio_2.05.00.06.10_release_CL195459
@ rjmjr69
Hboot information is:
SUPERSONIC EVT2-3 SHIP S-ON
HBOOT-0.79.0000
MICROP-041F
TOUCH PANEL-ATMWLC03_16ac
RADIO-1.39.00.04.26
@mogul420
Recovery gives me an error
E:Can't open /cache/recovery/command
Then I click volume up and the following title and menu appear:
Android system recovery <2e>
reboot system now
apply sdcard:update.zip
wipe data/factory reset
wipe cache partition
When I choose the sdcard:update option the following message is displayed
----Install from Sdcard ------
Finding Update package
Opening update package
verifying update package
E:signature verification failed
instalation aborted
Ok here's the deal. If you have nan unlock, fully rooted then you should have a nandroid back. If you do then boot into recovery and no a nandroid restore. This should boot you to one of your pervious backup/ system state.
Please note.
If you are fully rooted u should always do a nandroid backup before you flash any update, that way u can do a restore in the even something goes wrong.
http://WWW.rootznculture.com
Thank you for the information but it was a step I did not do... The tutorial that I went with did not speak about that when I rooted my phone...
EDIT: I even tried mixing files that I have downloaded with various PC36IM.zip and nothing triggers the update question.
Would they be able to notice if its rooted?
adelaney said:
Not bricked, just stuck. Download stock ruu, plug phone into computer and install. Or put pc136.img on rot of sd, boot into fast boot, it should install automatically. If none of the above, go to a sprint store, tell them it won't boot and you don't know why, and they will flash or replace.
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
Most likely NOT bricked if it boots!
Sounds like you re-applied root but glitched somewhere?
Try root again - may still work?
http://forum.xda-developers.com/showthread.php?t=706411
Another helpful post
http://forum.ppcgeeks.com/showthread.php?t=123714
What version is your hboot - press power and volume down WITHOUT pc36img.zip, update, etc on your sd - i.e. rename it or remove it, i.e. with adb or sd card slot on pc.... See if you can still access recovery?
I've been hammering on these things for a bit and if I can get into the boot screen, it's pretty much good to go...
Hboot-0.79.0000
Also the error that began all of this was running the wrong PC36IMG to begin with... I had 1.4 radio and I think that the one I used had the 1.3 radio so the only thing that helped me boot up again was that 1,2,3 step flashing so I thought that I had to take the second step and that placed in on booter, I have not been able to boot again ever since.... That was yesterday been trying for about 9 hours lol
lwarranty said:
sounds like you re-applied root but glitched somewhere?
Try root again - may still work?
http://forum.xda-developers.com/showthread.php?t=706411
another helpful post
http://forum.ppcgeeks.com/showthread.php?t=123714
what version is your hboot - press power and volume down without pc36img.zip, update, etc on your sd - i.e. Rename it or remove it, i.e. With adb or sd card slot on pc.... See if you can still access recovery?
I've been hammering on these things for a bit and if i can get into the boot screen, it's pretty much good to go...
Click to expand...
Click to collapse
Yes your just not rooted anymore. Run whatever process worked for you the first time
Try whitslack's method.
EDIT: Nevermind, no can do.
What happens is that my phone DOES read the PC36IMG.zip but it does not give me update option as it used to before. Any suggestions?
rjmjr69 said:
Yes your just not rooted anymore. Run whatever process worked for you the first time
Click to expand...
Click to collapse
xx1479 said:
Try whitslack's method.
Click to expand...
Click to collapse
latinsbest said:
What happens is that my phone DOES read the PC36IMG.zip but it does not give me update option as it used to before. Any suggestions?
Click to expand...
Click to collapse
Like he said
Make sure you delete all the files off your sdcard first
Do you have a link? I made a quick search and could not find a direct link...
xx1479 said:
Try whitslack's method.
Click to expand...
Click to collapse
I have several times even formatted (fat32) various times too
rjmjr69 said:
Like he said
Make sure you delete all the files off your sdcard first
Click to expand...
Click to collapse
latinsbest said:
I have several times even formatted (fat32) various times too
Click to expand...
Click to collapse
Reroot your phone using toast method! That is all! If you are on 1.47 then use simple root!
Seems you have un-rooted the boot me thinks but also read something about mixing radio's causing grief, someone more in the know could answer that... If you can get to hboot usb and try the RUU from your PC? Sometimes taking the battery out and restarting, if communication fails, try it again, rebooting the pc, hell I have no procedure, I just hammer till it makes sense, however 9 hours - holy crap, I'd be foaming at the face!
Ok will do right away and post update
novanosis85 said:
Reroot your phone using toast method! That is all! If you are on 1.47 then use simple root!
Click to expand...
Click to collapse
I have done that via PC and the only thing that works with that are the stock roms since they come in EXE they manage to reboot my phone and everything but when the update gets to the signature part it says it fails in the signatures and aborts... any other custom roms that have EXE?
lwarranty said:
Seems you have un-rooted the boot me thinks but also read something about mixing radio's causing grief, someone more in the know could answer that... If you can get to hboot usb and try the RUU from your PC? Sometimes taking the battery out and restarting, if communication fails, try it again, rebooting the pc, hell I have no procedure, I just hammer till it makes sense, however 9 hours - holy crap, I'd be foaming at the face!
Click to expand...
Click to collapse
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
Hello.
I have HTC Evo 4g brought to me from US.
And here is the trouble: it is random reloading at different boot sequences(for example while htc EVO 4g logo on whitescreen, while Sprint4g logo running), few times even Android started up, and a after few seconds device again reloads.
I have not do any changes to phone, here some info:
SUPERSONIC EVT2-3 SHIP S-ON
HBOOT 2.10.00001
MICROP 041f
TOUCH PANEL-ATMEL224_16ab
RADIO 2.15.00.11.19
Oct 15 2010, 12:07:00
What have I to do to fix my phone ?
Or how i can unroot it without booting Android for trying other ROM file ?
I want to re-flash device for any android with eingeneer menu to use it in Ukraine CDMA operator.
Thank you and sorry for my English.
TaTaPuH said:
Hello.
I have HTC Evo 4g brought to me from US.
And here is the trouble: it is random reloading at different boot sequences(for example while htc EVO 4g logo on whitescreen, while Sprint4g logo running), few times even Android started up, and a after few seconds device again reloads.
I have not do any changes to phone, here some info:
SUPERSONIC EVT2-3 SHIP S-ON
HBOOT 2.10.00001
MICROP 041f
TOUCH PANEL-ATMEL224_16ab
RADIO 2.15.00.11.19
Oct 15 2010, 12:07:00
What have I to do to fix my phone ?
Or how i can unroot it without booting Android for trying other ROM file ?
I want to re-flash device for any android with eingeneer menu to use it in Ukraine CDMA operator.
Thank you and sorry for my English.
Click to expand...
Click to collapse
That right there means your phone is NOT rooted. I would boot into recovery and do a factory reset of the phone.
I entered the boot menu and hit RECOVERY... after that i got black screen with a picture of an evo, and an red triangle with an explanation mark.
After that i've done Factory reset, but my device is still reloading...
TaTaPuH said:
I entered the boot menu and hit RECOVERY... after that i got black screen with a picture of an evo, and an red triangle with an explanation mark.
Did i something wrong, how could i factory reset my phone ?
Click to expand...
Click to collapse
That is stock recovery, which is no recovery. Do a battery pull, go back to the bootloader, and select clear storage. That's a factory reset from the bootloader.
After a Clear Storage phone is still reloading, do microSD card have to be plugged in while clear storage ? and if it is, in what filesystem format SD ?
After a CLEAR STORAGE device first time runs Android and after few seconds reboots, and after that continue to reboot forever)
TaTaPuH said:
After a Clear Storage phone is still reloading, do microSD card have to be plugged in while clear storage ? and if it is, in what filesystem format SD ?
Click to expand...
Click to collapse
Your phone is stock unrooted so your SD card wont affect the boot sequence. Since it is unrooted you may want to just take it to Sprint and have them take a look at it.
Concordium said:
Your phone is stock unrooted so your SD card wont affect the boot sequence. Since it is unrooted you may want to just take it to Sprint and have them take a look at it.
Click to expand...
Click to collapse
So it is probably broken ? I can't get it to Sprint because i'm in Ukraine with this phone. what else can i do to fix device ?
TaTaPuH said:
So it is probably broken ? I can't get it to Sprint because i'm in Ukraine with this phone. what else can i do to fix device ?
Click to expand...
Click to collapse
Do you not have Sprint in Ukraine? If not then what exactly are you using a stock, unrooted, Sprint phone from America for? There are a number of cheaper MP3 player alternatives out there.
You can try running an RUU. Since I think that usb debugging has to be on (but I'm not positive), download one in zip form (not exe, you run those from a computer). Be sure that it's named PC36IMG.zip exactly and put it on the root of your SD card - that means not in any folders. Boot into hboot by holding volume down & power. Your phone will search for the file and ask you to update. Select yes with volume up. When it asks you to reboot, do so.
Use this here, it should be properly named.
http://goo-inside.me/supersonic/ruu/4.53.651.1/PC36IMG.zip
Supersonic Evo 4G | MIUI | Tapatalk
plainjane said:
You can try running an RUU. Since I think that usb debugging has to be on (but I'm not positive), download one in zip form (not exe, you run those from a computer). Be sure that it's named PC36IMG.zip exactly and put it on the root of your SD card - that means not in any folders. Boot into hboot by holding volume down & power. Your phone will search for the file and ask you to update. Select yes with volume up. When it asks you to reboot, do so.
Use this here, it should be properly named.
http://goo-inside.me/supersonic/ruu/4.53.651.1/PC36IMG.zip
Supersonic Evo 4G | MIUI | Tapatalk
Click to expand...
Click to collapse
But is it the 3.70 RUU?!
plainjane said:
You can try running an RUU. Since I think that usb debugging has to be on (but I'm not positive), download one in zip form (not exe, you run those from a computer). Be sure that it's named PC36IMG.zip exactly and put it on the root of your SD card - that means not in any folders. Boot into hboot by holding volume down & power. Your phone will search for the file and ask you to update. Select yes with volume up. When it asks you to reboot, do so.
Use this here, it should be properly named.
http://goo-inside.me/supersonic/ruu/4.53.651.1/PC36IMG.zip
Supersonic Evo 4G | MIUI | Tapatalk
Click to expand...
Click to collapse
OK, thnx very much, i'll try this today.
Do you not have Sprint in Ukraine? If not then what exactly are you using a stock, unrooted, Sprint phone from America for? There are a number of cheaper MP3 player alternatives out there.
Click to expand...
Click to collapse
If i could run a Android then i've unrooted it and could use it in Ukraine 3g.
Go here and download the 4.53 and run it from your PC
http://goo-inside.me/supersonic/ruu
Sent From My Pocket
I Tried to flash STOCK RUU 4.53 firmware from SD Card, the result was the same - device still constantly re-booted, but with 4.53 firmware it was restarting after 5 sec.
So i flashed it second time and phone freezed at flashing SYSTEM section, so i had do too pull out the battery, after that my phone turned into brick))))
not even loading bootloader or charging. ))
Thank everyone)) for attention payed too.
plainjane said:
You can try running an RUU. Since I think that usb debugging has to be on (but I'm not positive), download one in zip form (not exe, you run those from a computer). Be sure that it's named PC36IMG.zip exactly and put it on the root of your SD card - that means not in any folders. Boot into hboot by holding volume down & power. Your phone will search for the file and ask you to update. Select yes with volume up. When it asks you to reboot, do so.
Use this here, it should be properly named.
http://goo-inside.me/supersonic/ruu/4.53.651.1/PC36IMG.zip
Supersonic Evo 4G | MIUI | Tapatalk
Click to expand...
Click to collapse
or you other choice will be to ROOT you phone and flash a custom ROM
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.
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!