Rooting was giving error by reflash_package.exe . Then i foolishly tried Alpharev
I run Alpharev by making CD with ISO of Alpharev .. halfway on the process its stops & says that S-ON .
Now its Hangs on HTC Logo with Black Line .
Image version
2.13.707.1
bravo pvt4 ship s-on
h-boot 0.93.0001
microchip-051d
touch panel-synt0101
radio-5.09.05.30.2
aug 10
RUU_Bravo_HTC_WWE_1.21.405.2_Radio_32.36.00.28U_4.06.00.02_2_release_126984_signed.exe
Error ID 131
Please Help . what should i do ?
Can i make GoldCard with HTC Hang ...
Please help ..
Thanks
Waiting for Urgent help .
Are you sure you are on "2.13.704.1" and not "2.13.707.1" ?
I have PVT4 i have rooted it using unrEVOked.
E: Can't find MISC:
E: Can't mount CACHE: recovery/command
E: Can't find MISC:
E: Can't mount CACHE: recovery/log
E: Can't find MISC:
But this message keeps showing everytime im in Recovery.
I have tried LeeDrOiD_v2.2f_A2SD but installation aborted. I tried other roms but still i can't manage to install it
Now i have tried Virtualbox method for S-off(AlphaRev) but flashing failed. The message says something like im not properly
rooted. "The phone is not bricked."
You can safely reboot your phone." But i have noticed that during the process 2 black lines appeared at the HTC logo and hangs.
I can Power+VolD to Hboot but im stuck at HTC logo with 2 black lines. It seems i can no longer boot my phone.
I have to pop up the battery and tried again but no luck..
I had the same thing!
I went on this page http://shipped-roms.com/shipped/Bravo/
downloaded PB99IMG_Bravo_Froyo_HTC_WWE_2.29.405.2_Radio_32.49 .00.32U_5.11.05.27_release_151783_signed.zip (third one from above)
, renamed it to PB99IMG.zip
and put it on sdcard and flashed it in bootloader and everything back to normal!
I tried downgrading but fail.Now waiting for more info how to install custom rom
i found the above solution in forums
But when i do it it says me that " Incorrect CID Update Fail " do u want to restart now ..
Anyone helps
3722 said:
Are you sure you are on "2.13.704.1" and not "2.13.707.1" ?
Click to expand...
Click to collapse
yes Sorry .. You are write . spelling mistake
now i m downloading RUU_Bravo_Froyo_hTC_Asia_WWE_2.13.707.1_Radio_3..>
hope this will revive my phone .... i will keep you updated ..
RUU_Bravo_Froyo_hTC_Asia_WWE_2.13.707.1_Radio_32.44.00.32U_5.09.05.30_2_release_143921_signed.exe
131 Customer ID error ..
WTF is happening ..
What should i do ?
You should not get this error if you are truly on that version
Are you sure you are downloading this
http://www.shipped-roms.com/downloa...00.32U_5.09.05.30_2_release_143921_signed.exe
If it indeed gives you CID error than this wasn't your original firmware.
In that case make a goldcard and flash a generic WWE RUU or the Asian one again.
goldcard
I had exactly the same problem, but already rooted and had AmonRa recovery. My device is also a new PVT-4... luckily I had a goldcard, and did a nand backup.
I do not know of any solution, except Goldcard one, but hardly possible, since you cannot boot the device. if somehow you manage to get to your CID, look at this post: http://forum.xda-developers.com/showpost.php?p=7826990&postcount=8
Make sure u did everything right and it should work hope it helps
Dude, did you try booting the updated Alpharev CWM recovery through ADB ? Or if you can still enter fastboot, try unrevoked one more time, but this time with custom recovery (updated CWM). This should solve the MISC problem and allow you to flash custom ROMs.
Also, when in fastboot or recovery, did you try creating a goldcard, also through ADB?
If this doesn't help, i think it's time for warranty...
some one posted this solution will this work ?
got desprate while my friend Desire is semi bricked.
usb , wifi , ADB is not worked...constant reboot happened...
tried to flash almost RUU from http://www.shipped-roms.com/shipped/Bravo/ without success
i knew my success key to solve this problem is creating goldcard to flash the RUU
I cannot get CID for goldcard...because ADB, wifi and usb not worked..only fastboot is worked
I tried to create goldcard using nexus one and my sdcard...
1.format my nexus sdcard using fat32 partitiion.
2.generate the reserve CID with goldcard helper (you can download it from market)
3.i am follow guide from http://www.droid-den.com/android-gui...te-a-gold-card
from step 12 to step 19 (using SDcard adapter with my pc)
4.put that goldcarded sdcard to the semi bricked desire
5. flash RUU rom you want....(please also do some research before you do this)
Sucesss!!
aamszia said:
I have PVT4 i have rooted it using unrEVOked.
E: Can't find MISC:
E: Can't mount CACHE: recovery/command
E: Can't find MISC:
E: Can't mount CACHE: recovery/log
E: Can't find MISC:
But this message keeps showing everytime im in Recovery.
I have tried LeeDrOiD_v2.2f_A2SD but installation aborted. I tried other roms but still i can't manage to install it
Now i have tried Virtualbox method for S-off(AlphaRev) but flashing failed. The message says something like im not properly
rooted. "The phone is not bricked."
You can safely reboot your phone." But i have noticed that during the process 2 black lines appeared at the HTC logo and hangs.
I can Power+VolD to Hboot but im stuck at HTC logo with 2 black lines. It seems i can no longer boot my phone.
I have to pop up the battery and tried again but no luck..
I had the same thing!
I went on this page http://shipped-roms.com/shipped/Bravo/
downloaded PB99IMG_Bravo_Froyo_HTC_WWE_2.29.405.2_Radio_32.49 .00.32U_5.11.05.27_release_151783_signed.zip (third one from above)
, renamed it to PB99IMG.zip
and put it on sdcard and flashed it in bootloader and everything back to normal!
I tried downgrading but fail.Now waiting for more info how to install custom rom
i found the above solution in forums
But when i do it it says me that " Incorrect CID Update Fail " do u want to restart now ..
Anyone helps
Click to expand...
Click to collapse
You clearly don't know wat your doing, you already might have bricked it by flashing your asia rom with a wwe rom, you can't flash it if you don't have a goldcard.
Read post before yours, he's fixed...lucky, mind
Rooted (via Revolutionary) Incredible 2. Was running stock Rom.. Decided to try CM7. downloaded and installed via ROM Manager. MMS didn't work so i tried to restore to my backup via Rom Manager. Now phone sticks at white HTC Screen.
Can get into recovery.
But receive the following error messages:
E: Can't Mount/cache/Recovery/command
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
INFO:
VIVO_W XB SHIP S-OFF RL
HBOOT-6.13.1002
RADIO 1.09.01.0622
EMMC-BOOT
When I attempt to restore a backup I get:
Checking MD5 sums...
Erasing boot before restore...
Restoring Boot Image...
Restoring System Image...
Error while Formatting/System!
TRIED FLASHING A COUPLE DIFFERENT ROMS:
FINDING UPDATE PACKAGE
OPENING UPDATE PACKAGE
INSTALLING UPDATE
E: ERROR IN /SDCARD/CCM7_INC2_V1.4ZIP
(STATUS 1)
INSTALLATION ABORTED
Tried Flashing the return to stock PG32img.zip
get these messages:
Loading [PG32DIAG.ZIP]
NO IMAGE!
Loading [PG32DIAG.NBH]
NO IMAGE OR WRONG IMAGE
IT LOADS THE FILE AND I START THE UPDATE.
IT BYPASSES (1) BOOTLOADER
AND THEN STICKS AT (2) BOOT----UDATING
MESSAGES AT BOTTOM OF SCREEN SAY:
DO NOT POWER OFF DEVICE!
CAN NOT ROLL BACK HBOOT VERSION
WILL JUST SAY STAY LIKE THIS FOR HOURS.
Any help to get a working phone would be greatly appreciated. THANKS!!!
Any chance the SD card is corrupted?
card
Not sure, the card seems to work ok in my computer, and I used a different card to try and flash the roms and the return to stock PM32IMG.ZIP. I will try another card when i get one.
Install another recovery... I personally like 4ext. Its in the dev section... also did u nandroid your stock rom before flashing? Try restoring it an verifying it is a correct md5 for the rom and that your recovery is up to date
Sent from my Incredible 2 using Tapatalk 2
I tried 2 different sd cards with no luck. i have 5 or 6 backups but none of them will load. how would I go about install the 4ext recovery?
http://forum.xda-developers.com/showthread.php?p=20013819
Read down where it says if you lost your recovery img... that's how u install it via fast boot
Sent from my Incredible 2 using Tapatalk 2
Hey, this is DroidDev from AndroidCentral. Just incase you didnt see it there:
Seems like corrupted HBOOT or Bootloader to me? Will do some more digging/thinking but it doesnt look good.
When you install the pg32img.zip, which is the stock RUU, you roll everything back to stock. HBOOT, OS, everything, even loosing root. First thing it tried to do is roll back the HBOOT, it if cant do that then you probably have corrupted HBOOT.
In the mean time I would grab the Froyo RUU here and try that:
http://forum.xda-developers.com/show....php?t=1466295
If you were trying with the Froyo RUU, then try the Gingerbread one. The Guide in this thread, if you read it, has instructions on pushing hboot starting at step 11. But I would just do the guide from beginning to end. It will return your phone to complete stock froyo. If successful you can upgrade back to GB.
Click to expand...
Click to collapse
If you cant get the Froyo RUU to install then I would not continue with the guide, could make it worse.
Here is a link to the GB RUU for you.
Turn on your phone and enter the bootloader, select fastboot and plug into your computer. Leave the phone here, then just run the .exe file on your computer. This'll wipe everything including bootloaders, radio, recovery etc. back to stock GB, without relying on your SD card to do the work.
It's worth a shot, while I don't think the SD card is the issue I haven't been able to not recover with an RUU before, from anything
Good luck!
Sounds like flash memory is messed up, I bet all partition sizes read zero, same thing happened to me. I tried to reformat with parted but no luck.I never could find exact sizes for the various mtblk's but my final judgment was that the physical flash memory was fried. dunno maybe if you knew the exact format sizes for everything you could try to push the needed Linux file through adb and try to reformat them one at a time, but I never could get it to work.
On a side note someone on XDA who said they work @ Verizon said they've had a rash of inc2's being turned in with similar problems, maybe a manufacturing glitch
Sent from my 2nd Incredible 2
Ok, so i tried flashing the 4EXT recovery by loading on an sd car and flashing with fastoot. Appeared to install, but still getting same problems. Tried to flash the recovery with abd fastboot from computer...just sticks a writing... never completes. Also tried flashing different backups and ROMS from flashboot with computer, with ROMS I get a message saying their is an error in zip file and can't be read. Tried to install Froyo ROM again via fastboot from SDcard. Just hangs at 2nd 1 saying updating for hrs, never completes. Not sure how to run GB RUU by the exe file? Do i extract the RUU file first? Whenever I have tried to extract those update files in the past i got an error. I'll try and figure it out this afternoon. An interesting side note, CM9 rom appears to install via flashboot from card but never loads upon reboot. Thanks to All for their continuing help!!!
PS...surfing at work and found this post - http://forum.cyanogenmod.com/topic/6433-solved-messed-up-partitions-on-internal-storage/ - sounds similar to my problem...basically says partitions on internal storage are messed up and how to use parted to fix. May also try that.
well, tried to install the gb rom exe file. Hung almost from the start, trying to reboot phone into bootloader. I'm at loss. Guess I have a new red paperweight. Not sure how to do parted, so holding off on that for now. Open to any other suggestions.
your using the wrong ruu i think you have to get the latest update, god and i forget the link, go to rootzwiki, jelly belly has what you need or condemned soul on here
My DINC2 is FIXED!
Turn on your phone and enter the bootloader, select fastboot and plug into your computer. Leave the phone here, then just run the .exe file on your computer. This'll wipe everything including bootloaders, radio, recovery etc. back to stock GB, without relying on your SD card to do the work.
It's worth a shot, while I don't think the SD card is the issue I haven't been able to not recover with an RUU before, from anything
Good luck![/QUOTE]
Hey man thank you, I had the same issue as the thread starter and tried all the same methods as he did before searching the forums. Your solution worked for me after getting the latest RUU from jellybelly. This event happened to me randomly, i think the wrong buttons were pushed while my phone was in my pocket. I have a commuter otterbox case and it makes the buttons easier to press. But some tips:
1. verify md5sum
2. i had s-off so I used the latest 2.3.3 ruu file from jellybelly
3. rename downloaded zip file "PG32IMG" only exclude the .zip part like what most folks tell you.. i explain below
i initially renamed the zip "PG32IMG.zip" and stored on the root location of the sdcard, well fastboot/hboot could not find the file, after loading the sdcard back on my computer and clicking the files properties i noticed the the file name was "PG32IMG.zip.zip", after renaming the file to "PG32IMG" the bootloader was able to find the zip file and the process was completed.
4. I do not know about an .exe file, If you can get into fastboot/hboot by holding the "volume down button" + power , that is the method i did
I hope I helped somebody and thanks everybody for yours!
I had similar problems sticking on white with green HTC on it. Mine had to do with the boot.img. I had to extract a boot.img out of a rom put it in folder on C Drive installed rom with 4extrecovery let it load but did not reboot I connect to computer pulled up bootloader with adb and flashed the boot.img and flash reboot and it past that screen and loaded. Had to be unlocked to do it.
daddythree said:
Rooted (via Revolutionary) Incredible 2. Was running stock Rom.. Decided to try CM7. downloaded and installed via ROM Manager. MMS didn't work so i tried to restore to my backup via Rom Manager. Now phone sticks at white HTC Screen.
Can get into recovery.
But receive the following error messages:
E: Can't Mount/cache/Recovery/command
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
INFO:
VIVO_W XB SHIP S-OFF RL
HBOOT-6.13.1002
RADIO 1.09.01.0622
EMMC-BOOT
When I attempt to restore a backup I get:
Checking MD5 sums...
Erasing boot before restore...
Restoring Boot Image...
Restoring System Image...
Error while Formatting/System!
TRIED FLASHING A COUPLE DIFFERENT ROMS:
FINDING UPDATE PACKAGE
OPENING UPDATE PACKAGE
INSTALLING UPDATE
E: ERROR IN /SDCARD/CCM7_INC2_V1.4ZIP
(STATUS 1)
INSTALLATION ABORTED
Tried Flashing the return to stock PG32img.zip
get these messages:
Loading [PG32DIAG.ZIP]
NO IMAGE!
Loading [PG32DIAG.NBH]
NO IMAGE OR WRONG IMAGE
IT LOADS THE FILE AND I START THE UPDATE.
IT BYPASSES (1) BOOTLOADER
AND THEN STICKS AT (2) BOOT----UDATING
MESSAGES AT BOTTOM OF SCREEN SAY:
DO NOT POWER OFF DEVICE!
CAN NOT ROLL BACK HBOOT VERSION
WILL JUST SAY STAY LIKE THIS FOR HOURS.
Any help to get a working phone would be greatly appreciated. THANKS!!!
Click to expand...
Click to collapse
I'm having this exact same problem. Did you ever get your fixed? Any new suggestions ??
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!