Related
Out of no where I got a message on my phone, saying that my sd card was unmounted. I wasn't doing anything other than I normally would. Now when I try to access my SD card, it's not even seen by the G2. I've formatted it to FAT32 and nothing, I've restarted the phone multiple times and no dice, and I have given it time to rest. I cannot seem to find the issue with this, but I have heard about some issue with the SD card latch thing. What can I do to fix this issue? Any advice would be greatly welcome
Have you tried another SD card to see if it is the phone or the SD card giving you problems?
Sent from my SilverBullet 'HTCDesireZ running CM7'
Fireflyz said:
Out of no where I got a message on my phone, saying that my sd card was unmounted. I wasn't doing anything other than I normally would. Now when I try to access my SD card, it's not even seen by the G2. I've formatted it to FAT32 and nothing, I've restarted the phone multiple times and no dice, and I have given it time to rest. I cannot seem to find the issue with this, but I have heard about some issue with the SD card latch thing. What can I do to fix this issue? Any advice would be greatly welcome
Click to expand...
Click to collapse
Is it the SD card that came with the g2 or a different one?
I had this happen with a 32GB patriot class 10 I put in my G2. It would corrupt and do the exact same until I full formatted it on a PC. (long story short it's a issue with the sdcard itself and has to be formatted a special way, but it's ONLY THIS CARD).
Try a different card, if a different card works then full format the nonworking card. If that still doesn't work then there may be a off chance (a very very off chance) that the card went bad.
Went to the T-mobile store and tried 2 different sd cards. Neither of them worked... any way to fix this on my own? If not, then can I un-root my G2 without an SD? If I call up costumer care, they'll probably want me to send my G2 in and will notice it has been rooted and such. I heard somewhere that as long as it looks stock, they won't do/say anything... not sure if this is true though..
Fireflyz said:
Went to the T-mobile store and tried 2 different sd cards. Neither of them worked... any way to fix this on my own? If not, then can I un-root my G2 without an SD? If I call up costumer care, they'll probably want me to send my G2 in and will notice it has been rooted and such. I heard somewhere that as long as it looks stock, they won't do/say anything... not sure if this is true though..
Click to expand...
Click to collapse
Yikes, I'm not sure if you can if it can't read a image off the sdcard to flash.
You do have a legit hardware issue that rooting couldn't cause though.
The sd slot is not fixable most likely.
But getting your phone back to stock is.
if you have an eng s-off bootloader you can usually fasboot update the PC10IM.zip if you rename it to update.zip and place it in your adb/fastboot fodler on your pc like so:
fastboot update
ot
fastboot update update.zip
not sure, it's been a while
if you have an s-on bootloader have no fear, you can still get to stock, it's a little more complicated.
find a PC10IMG.zip that has a stock recovery.img in it.
extract it and place it somwhere it is easy to locate and the path is short for ease. like c:\
download a flashable recovery update zip for the stock rom you want to load back on the device. keep it for later.
download this special recovery image:
View attachment CWM-3.0.2.4-sd-spoof.zip
extract the image and flash it from the OS, you'll need to boot your phone first then when it is up and running you need to enable usb debugging and use it to push the recovery image to your /data partition
adb push recovery.img /data
or the path is required if you put it elsewhere like c:\
adb push c:\recovery.img /data
it should be in /data/recovery.img
then open terminal or since you shoudl have adb open you can use 'adb shell' then type enter to enter a root shell
flash_image recovery /data/recovery.img
it should just spir out a
#
that means it's successful, reboot to recovery
now you will be able to push items to the root of your /data folder (or anywhere in /data really)
when you select the flash zip from recovery option it will spoof the /data folder as the /sdcard and display the contents of your /data folder rather than the /sdcard allowing you to flash without needing the sdcard to work.
now flash any stock rom from recovery.
while still in recovery you will need to flash the stock recovery image as well once you verify the stock rom is in place and boots. you will still have CWM but you wont be rooted so flashing from recovery is required. it can be flashed with the same commands you used to flash the other recovery from the OS
if you get a return of error -1 when you try to use the flash_iamge command to flash recovery PM me, i have a fix for that as well. it should be updated though not to do that any more.
ONCE YOU FLASH THE STOCK RECOVERY AND STOCK ROM, unless you manually root again, which will be tricky, you are stuck.
hope this has been helpful.
amazinglarry311 said:
The sd slot is not fixable most likely.
But getting your phone back to stock is.
if you have an eng s-off bootloader you can usually fasboot update the PC10IM.zip if you rename it to update.zip and place it in your adb/fastboot fodler on your pc like so:
fastboot update
ot
fastboot update update.zip
not sure, it's been a while
if you have an s-on bootloader have no fear, you can still get to stock, it's a little more complicated.
find a PC10IMG.zip that has a stock recovery.img in it.
extract it and place it somwhere it is easy to locate and the path is short for ease. like c:\
download a flashable recovery update zip for the stock rom you want to load back on the device. keep it for later.
download this special recovery image:
View attachment 582547
extract the image and flash it from the OS, you'll need to boot your phone first then when it is up and running you need to enable usb debugging and use it to push the recovery image to your /data partition
adb push recovery.img /data
or the path is required if you put it elsewhere like c:\
adb push c:\recovery.img /data
it should be in /data/recovery.img
then open terminal or since you shoudl have adb open you can use 'adb shell' then type enter to enter a root shell
flash_image recovery /data/recovery.img
it should just spir out a
#
that means it's successful, reboot to recovery
now you will be able to push items to the root of your /data folder (or anywhere in /data really)
when you select the flash zip from recovery option it will spoof the /data folder as the /sdcard and display the contents of your /data folder rather than the /sdcard allowing you to flash without needing the sdcard to work.
now flash any stock rom from recovery.
while still in recovery you will need to flash the stock recovery image as well once you verify the stock rom is in place and boots. you will still have CWM but you wont be rooted so flashing from recovery is required. it can be flashed with the same commands you used to flash the other recovery from the OS
if you get a return of error -1 when you try to use the flash_iamge command to flash recovery PM me, i have a fix for that as well. it should be updated though not to do that any more.
ONCE YOU FLASH THE STOCK RECOVERY AND STOCK ROM, unless you manually root again, which will be tricky, you are stuck.
hope this has been helpful.
Click to expand...
Click to collapse
S-off and S-on bootloader? Is that the same as having S-on/S-off in general?
Larry was banned this morning, apparently being helpful isnt something highly valued around here.
yeah, you achieve s-off using gfree and you can decide if you want to install the ENG bootloader.
If you did, it should say ENG S-OFF instead of SHIP S-OFF
if fastboot allows you to do anything remotely you're in a good shape and that means you probably have a ENG bootloader.
Hi guys, sorry to say I'm back with another problem.
I have a Desire Z, rooted and S-off. Rooted with the wiki method (downgrade version, adb, gfree).
Using clockworkmod recovery 3.0.2.4, and have made a backup of my first 1.32 boot.
However, I tried flashing a new rom, but recovery just won't take it. It will say Can't open /sdcard/rom.zip (Bad) installation aborted, with every rom I tried. And I've tried more than 10.
So I thought, no biggie, I have a nandroid backup. So I run the restore, which works fine. But upon booting the device, it gets stuck on the white HTC loading screen. I have tried this multiple times, deleting cache/data etc fully. Also I used the FULL-WIPE-VISION.zip for this purpose to no avail.
I have followed the semi-brick guide which said I had to go get a stock rom with root, so I did. But I can't load it through clockwork restore, because I get the same Bad rom error.
What's left to try?
Additional info I should give according to the semi-brick thread (http://forum.xda-developers.com/showthread.php?t=842495):
The last and only Rom I had was the stock 1.32.4xx to which I had to downgrade before I got perm root. This rom is my nandroid recovery.
The command adb devices recognizes my device.
adb remount is succesful
adb shell gives me root
I have /data and /system mounted when trying most roms (but I get the same error when I don't have it mounted)
After booting and waiting a minute when it's stuck in white screen, adb devices will not recognize my device anymore, adb remount and shell also say that the device is not found.
Thanks a lot for helping out!
TL;DR: Clockworkmod recovery does not load roms, nand restore gives WSOD. How come?
EDIT: Problem was due to my budget 32GB microSDHC. Operations were successfull using the original 8GB card. Apologies for the spamtopic.
Noboo said:
EDIT: Problem was due to my budget 32GB microSDHC. Operations were successfull using the original 8GB card. Apologies for the spamtopic.
Click to expand...
Click to collapse
This isn't spam, and no need to apologize. Your post may be of benefit to others. If somebody has a similar issue, they may find your post, and from it find out how to fix it.
If nothing else, you should add [SOLVED] to the thread title.
cwm v3.2.0.0
cwm v3.0.0.5
RA v2.0.0
All now
"E:Can't mount /dev/block/mmcblk0p1 (or /dev/block/mmcblk0)
(no such file or directory)
E:Can't mount /sdcard"
This happens with both cm7 and bravo Hboots and different SD cards repartitioned SD card (well recovery reported 'done'), SD card works fine in my PC.
I'm s-off, the trouble all started when I noticed that there was a new cwm recovery this morning and applied it through Rom Manager.
Got a bricked phone now unless someone can help, OS doesn't load past my custom boot splash screen. I can flash new Hboots and recoveries but can't get a rom to load from a recovery.
Help please
Matt
(searched the forum to no avail!)
Hboot will not see a PB99IMG.zip either
SOLUTION
Yes, I was totally unable to see the sdcard, the problem was the phone not the sdcard:
With phone in Hboot Fastboot mode
At the commant prompt on my Win 7 32 bit PC:
C:\adb\tools\fastboot devices
SH11APL03395 fastboot
C:\adb\tools\fastboot oem boot
Blah blah blah
INFOCID is ORANG001
Blah Blah Blah
C:\adb\tools\fastboot oem enableqxdm 0
...OKAY [ 0.164s]
finished. total time: 0.165s
C:\adb\tools\fastboot oem eraseconfig
...INFOEraseconfig complete
All recoveries and Hboots can now mount the sdcard, The last command which I initially omitted gave me USB connection and Bluetooth problems.
Now all sorted, hope this helps someone.
Thanks for all your efforts guys
Matt
would the clockwork mod recovery topic be a good place to post?
Last post on there might help you - have you repartioned your sd?
--------------------------------------------------------------------------------
hello I just wanted to test this new recovery, to be updated ^^
I had installed on my phone RA_recovery 2.0.0 which works fine, so I flashed ClockworkMod Recovery - 3.2.0.1 zip file and during restart my system can no longer mount my SD card .... now I'm trying to debrick it
Be careful before flashing this file, it's just an advise !
Edit: I looked better at my problem and it seems to come from the EXT partition that no more recognized...
hi,
@msivister try this command => fastboot oem enableqxdm 0
you do this in fastboot (boot into bootloader), i guess this is not a brick device.
hope this help
I get
... FAILED <status malformed <1 bytes>>
finished. total time: 0.002s
I had a look at the modaco downgrade hboot thread but the CID editor page is obsolete, should I persue that avenue?
Thanks
Matt
did you try re-partioning your card? maybe your ext is corrupt
Or try another sd card
Blank sd, reformat, put new rom zip on sd via PC, sd in phone, full wipe then flash it?
msiviter said:
I get
... FAILED <status malformed <1 bytes>>
finished. total time: 0.002s
I had a look at the modaco downgrade hboot thread but the CID editor page is obsolete, should I persue that avenue?
Thanks
Matt
Click to expand...
Click to collapse
I'd try again, make sure your in fastboot not the bootloader screen.
I had the exact same problem last night (i used clockworkmod to flash their recovery over amonras) and that modaco thread (link below) worked for me.
Still took a lot more steps after that to get a working ROM on there though.
I'll stick with AmonRa and flashing though the recovery from now on!
http://android.modaco.com/content/htc-desire-desire-modaco-com/309939/usb-brick-rickrolled-b0rked-fixed/
hi, agree with stringer, seems to be a bad partition table... redo your partition with gparted
fragargon said:
hi, agree with stringer, seems to be a bad partition table... redo your partition with gparted
Click to expand...
Click to collapse
If the problem is similar to mine then he's not going to see the sdcard from his phone no matter how its partitioned.
Sent from my HTC Desire using Tapatalk
unable mount sdcard - solved
Yes, I was totally unable to see the sdcard, the problem was the phone not the sdcard:
With phone in Hboot Fastboot mode
At the commant prompt on my Win 7 32 bit PC:
C:\adb\tools\fastboot devices
SH11APL03395 fastboot
C:\adb\tools\fastboot oem boot
Blah blah blah
INFOCID is ORANG001
Blah Blah Blah
C:\adb\tools\fastboot oem enableqxdm 0
...OKAY [ 0.164s]
finished. total time: 0.165s
Alpharev bravo Hboot
CWM v3.1.0.1
All recoveries and Hboots can now mount the sdcard, I dont know why the 'enableqxdm' command worked this time, I'm by no means an expert! All I know is that my phone is useable again- hurrah!
Thanks for all your efforts guys
Matt
Cool, glad your up and running.
I'm having a bit of a weird problem now I've managed to put a rom (insert coin) back on. Neither the phone or my pc see each other over usb and bluetooth will not turn on.
Do I need to run the usb brick fix or something?
I've tried putting the recommended radio on.No change.
Any ideas?
Edit: sorted,see first post.
Yeah, that's what I had to do. (Flash the update.zip fix from modaco)
Sent from my HTC Desire using Tapatalk
Instructions in first posted sorted me out, thanks a lot!
Thanks a lot!! Sorry for reviving this thread, but I looked for ages around the web for a solution to this problem, tried lots of stuff and only your solution worked for my Desire. So I'm posting some details about the problem that haven't been referenced in the thread, to make the topic come to the surface of search results more easily. Perhaps a sticky would be in order, since I saw this affects quite a number of people?
Anyway, the problem is that, at some point, the phone stops seeing the sdcard. Can't mount it from Recovery, can't access it to install zips, can't even partition it. For some, like in my case, not even Android can see the SD, which causes some grand headaches.
The error messages in the recovery (from what I've gathered, it seems the problem has been linked to ClockwordMod recoveries) are the following:
- E:Can’t mount /sdcard
when trying to access the SD card directory
- Unable to open ums lunfile (No such file or directory)
when trying to mount the card as USB storage
The real bummer in this case is that the SD card appears (and is) perfecty healthy and can be viewed and manipulated on a PC via card readers. The solution is a bit obscure with all those commands to issue to fastboot, and this is the only thread listing them that I found.
So, thanks!
billerr.g said:
Thanks a lot!! Sorry for reviving this thread, but I looked for ages around the web for a solution to this problem, tried lots of stuff and only your solution worked for my Desire. So I'm posting some details about the problem that haven't been referenced in the thread, to make the topic come to the surface of search results more easily. Perhaps a sticky would be in order, since I saw this affects quite a number of people?
Anyway, the problem is that, at some point, the phone stops seeing the sdcard. Can't mount it from Recovery, can't access it to install zips, can't even partition it. For some, like in my case, not even Android can see the SD, which causes some grand headaches.
The error messages in the recovery (from what I've gathered, it seems the problem has been linked to ClockwordMod recoveries) are the following:
- E:Can’t mount /sdcard
when trying to access the SD card directory
- Unable to open ums lunfile (No such file or directory)
when trying to mount the card as USB storage
The real bummer in this case is that the SD card appears (and is) perfecty healthy and can be viewed and manipulated on a PC via card readers. The solution is a bit obscure with all those commands to issue to fastboot, and this is the only thread listing them that I found.
So, thanks!
Click to expand...
Click to collapse
it's funny you should mention that this should be stickied because a few hours ago I added this to my troubleshooting guide.. which is a sticky
I had the same issue a week ago
i have same issue like this
Thanx
I've just needed to go through this and thankfully it helped. Any idea what causes it?
(Btw. Probably first post should underline to check whether you are in fact in fastboot. I booted into HBOOT waited till buttons were available then selected fastboot and I stayed in Hboot. Which I did not notice so I also got errors on fastboot commands. Selected fastboot again and then it worked.)
And as an FYI. Fastboot.exe was accidentally left out of recent SDK installs (R14, R15), so you have to manually download it [There's a link in Android Issue 21115 on google code (comment 3). This is the link: http://tools.android.com/knownissues#tools_r14 ,look at the end of section Tools R14] and put it in /platform-tools ! (As adb itself was moved from /tools to platform-tools).
Saved me from a dead SDcard slot
Many thanks, this thread also worked for me - Desire with ICS, lost all sight of the SDcard, whether from recovery or from ICS.
After "C:\adb\tools\fastboot oem boot" I got a black screen with a flashing green LED - most odd! But I took the battery out, rebooted into Fastboot USB, typed "fastboot oem enableqxdm 0" and it worked. Phew!!
So Ive been having problems with my SD card as posted here http://forum.xda-developers.com/showpost.php?p=16689682&postcount=286, and my question is, can someone explain to me how to flash back to stock without the use of my SD card ? Or am I screwed ? Thanks.
What you can do is download the RUU exe for the hboot you are on, if 2.10, its the 3.70, if 3.16, its 4.24 [the new ota], then connect the phone to the pc via usb, boot into the bootloader, select fastboot, then run the exe on the pc.
Thanks for the reply, and sorry for the noob question but how do you determine what hboot you are on ? Cause if I boot to the white Revolutionary screen (volume down + power) the third line down says "HBOOT-6.16.1002", is this right ?
----------
*EDIT*
Also dont know if this will help but when I am in recovery, if I try to mount my SD card it says "E:Can't mount /dev/block/mmcblk0p1 (or /dev/block/mmcblk0) (I/O error)"
Well I don't know if it was changed, but since you were on 2.3.3, you had to be on the 2.16, so for ruu purposes, look for that.
Alright, got stock back on. Thanks a lot.
I didn't know which one to use so I decided that since I have only had my evo for less than a month then I would use the latest version and it seems to have worked. So again, thanks a lot.
Okay, so I guess that I have a hardware problem and I will have to have it replaced. While my phone was just sitting there a notification came up that said "SD card unexpectedly removed"
Do I have to change the phone back to S-On before I get it replaced or can I keep it S-Off ?
Glad that you got it working, and you need to be s-on.
If you're s-off, re-root, then download the unrevoked s-on tool, flash the zip in recovery, make sure the bootloader reads s-on, the unroot again.
okay, so when I try to use the unrevoked s-on tool it fails and says unsupported radio type. any fix for this ?
BioBot said:
okay, so when I try to use the unrevoked s-on tool it fails and says unsupported radio type. any fix for this ?
Click to expand...
Click to collapse
try the 3.70 radio
You need to go to the development thread, then download the 2.1...11.19 radio and flash that.
Thanks for all the help guys. I've ran into another problem now. Before this new problem, if I wanted to put a new file on my SD card I had to flash to stock which gave me a 30-45 second window to mount the card to my pc and copy any files I needed to and power off before it unmounted it. Then I had to reboot, run revolutionary and get a recovery before it unmounted. Then I could flash a zip from my SD. BUT NOW, even if I reflash stock, it auto unmounts the SD at bootup.
Frustrated but still trying to problem solve.... Will update if anything changes.
Okay. I think I got it fixed now. After spending all day trying and flashing my phone at least 12-15 times it seems to be doing okay.
Solution : New SD card
Thanks for your help everyone !
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!