Cant access my sd card through cwm - HTC One X

Gday
I was wondering if it were possible to get some help. I have been playing around with my HTC one x and have unlocked the bootloader, placed the clockwork recovery on there and have flashed cyanogen 9 onto the device. It booted up just fine but when i tried to flash a different rom suddenly i couldnt see any of my files from within clockwork recovery. Now i can only get into fastboot and clockwork recovery and cant mount usb within clockwork as i get an an error saying um lunfile cant be found.
Since then i have tried everything i could do within clockwork recovery and fast boot, as well as using adb and quick adb pusher to try and get some files onto my device so i can get it back up and running. Nothing seems to be working. It seems as though I have lost the connection with my sd card somehow?
The closest i have gotten to getting things to work is within quick adb pusher where it will detect my device but when i browse to tell it where to put the files on my device there are no folders, just an error folder called '"/error: device not found/". In the information it says that it faled to mount as r/w.
I have also been trying out adb with commmands such as "fastboot erase cache" but just get a
"failed (command write failed (unknown error))".
Does anybody know what might be going on here? is this something ive done and can be fixed or has my sd card just failed? if so do you think HTC will fix it for me?
Many thanks in advance to any help i can get here!
... Camm

use the newest ClockworkMod (5.8.4.0), that bug (ums lunfile) has been fixed since June. You're likely on 5.8.3.1 or older.

Related

Dead USB port and MicroSD slot

So today, I was upgrading from modaco 2.7 to 2.7.1,
after the upgrade (using recover mode and the signed zip file (core chinese)), I did a system wipe and reboot the device with the USB still plugged in my PC, and everything seems to be normal until my pc's tray notification pops up with the "unknown device found" message - i thought it was a little bit odd, so then I waited for the hero to boot up completely - it reboots after showing the HTC logo once, and then it boots normally to the setup wizard (select language, etc);
I then followed the normal procedure of typing all the wifi, flickr, gmail stuff in, and when i got into Rosie, it shows a notification icon on the hero saying "SD Card removed". I can't access the SD card, nor my pc can recognize the hero. I ejected the SDCard and re-insert it but it's not detected either. HTC Sync on the device does not give a notification nor the mass storage notification shows up either.
I tried rebooting into recovery mode, (Hero 1.2.3) and i can see the menus just fine; however, when i try to mount SD card as usb, or flash update.zip or any zip, or fix ext3, or clear dalvik-cache or wipe the sdcard's ext partition, it keeps giving me errors saying
error: run 'whateverprogram' in terminal
when i try to set 'USB Mass storage on', it says "Error enabling USB mass storage! Run ums_enable manually from console.
I then try to login the device using adb shell through window's command prompt, it says device not found as well.
giving up, i tried to reboot teh device into fastboot mode, the PC recognizes the USB device just fine. it's really odd.
Anyway I can do a recovery on this to make these device work again?
p.s. when i try to choose zip file in recovery mode, it says
Code:
"E: Can't mount /dev/block/mmcblk0p1 (or /dev/block/mmcblk0) (No such file or directory)
Can't mount sdcard, aborting".
after every reboot (shutdown, start), the setup wizard shows up again as if I have not written anything on my device after any setup.
I can't download anything to run on the Hero as it requires the SD card. I can't flash any recovery images either as again it requires the SD card.
Any ideas??? I'm left with a half-brick now
Update1: using ConnectBot I can login my own device using root,
it shows the following when i run df -h:
Code:
/dev/block/mtdblock3 1700M 157.3M 12.7M 93% /system
/dev/block/mtdblock5 165.8MB 12.8M 152.9M 8% /data
/dev/block/mtdblock4 130.0M 1.2M 128.8M 1% /cache
kazuni,
Can you read SD card in your PC?
Several persons reported problems with SD card after upgrading to modaco 2.7 or 2.7.1. They have to format SD card.
Al936 said:
kazuni,
Can you read SD card in your PC?
Several persons reported problems with SD card after upgrading to modaco 2.7 or 2.7.1. They have to format SD card.
Click to expand...
Click to collapse
Thanks for the quick reply.
I have tried doing so, in fact, i have 4 SD cards to try and none of them are readable in the Hero; they are readable using a card reader in my PC though.
kazuni said:
Thanks for the quick reply.
I have tried doing so, in fact, i have 4 SD cards to try and none of them are readable in the Hero; they are readable using a card reader in my PC though.
Click to expand...
Click to collapse
Update2: the only way that my pc can detect my device as "My HTC" is when i boot it into fastboot mode; unfortuantely there are no way for me to update the device in this mode, so i can't do anything to modify the rom, or to check it using dropbear or any shell client. =\
C:\Documents and Settings\user>fastboot devices
HT97RL900725 fastboot
it sees it just fine.
I wonder if the goldcard method + fastboot update will work or not; let me give it a shot and try to flash it back to 405.5 first ;\
update3: can't. fastboot update is still locked for any rom type.
damn man. its freaking. i am not going to update to 2.7.1 untill this issue is resolved.
still no go.
im left with a half-bricked device that:
1) clean wiped, normal boot, cannot detect SD card nor the Hero is detectable by XP.
2) clean wiped, recovery mode, can't run any of the script except :
Reboot System Now
Wipe data/factory reset
Fix apk uid mismatches
Fix rotate
3) can't download anythign from browser as it needs to save onto sd card.
4) android market doesn't have flashrec so i can't reinstall the recovery image.
wget ftp://myhost/system.img /data/
flash_image system /data/system.img
hope this works
When you are in the shell check out the file /proc/cmdline.
Would be interresting to see if the HBOOT send a command line to the kernel to disable the SD card.
packetlss said:
When you are in the shell check out the file /proc/cmdline.
Would be interresting to see if the HBOOT send a command line to the kernel to disable the SD card.
Click to expand...
Click to collapse
can't. It doesn't even boot into normal mode, nor boot loop. it just holds at the HERO logo.
I think I have the same problem, i can charge my phone but trying to mount my phone to either my pc or mac it just won't be picked up
tried using RUU with a goldcard, no go. remote not allowed (fastboot flash system system_rel.img, nor fastboot boot boot.img or fastboot flash boot boot.img. no go. sigh.)
now i have a brick :\
wonder if there is any way to go into fastboot mode and flash ANY part of the blocks (device, recovery, or system, if at all).
Some progress: using hboot mode, i placed HEROIMG.zip into the sdcard and it loads successfully. it works! and im now rolled back to official 2.7.405.5; however, the USB and the sd card is still dead ;\
I guess I'll be bringing it back to HTC to see if they would do anything about it (fortunately It's now back to stock recovery and 2.74.405.5)
I managed to do the same thing, i'm hoping the tmobile will replace my phone
hi all,
I am having the same issue... what I don't understand is: it has to be a software problem, because, from what I've read, everyone of us have been installing radio and firmware updates to the htc hero, and since some of these updates the USB and sdcard mounting is not properly working... I believe it's not possible to break a USB port just by installing software...
so there should be a way to fix this other than sending the phones back... If anyone has any suggestion I can try it on my phone
cheers : )
I know it's weird! Funny thing is, official updates includes radio + recovery + pretty much every part of the rom is being re-flashed (including hboot, from what i understand); how ever, ONLY in hboot mode, the device is recognized properly as "Android USB" by windows.
Some of your problems I had to. To be exact: that my pc wouldn't recognize the phone when connected with usb except for fastboot and charging.
For weeks I searched and found some people with similar problems, but never a solution.
I had no problems with my sdcard however.
Now my problem is gone. How? I had the HTC Generic 2.73.405.5 ROM (pre-rooted and packaged as update.zip by MoDaCo) and decided to update to Paul's ROM v2.5.
After I was finished with the installation wizard and connected the phone with usb to my pc everything suddenly worked again!!!
So I got the usb and HTC Sync notification at the top of the screen and can mount the sdcard using the notification bar.
This tells me that in my case it definately wasn't a hardware problem as I always thought, but a software one.
I hope you can something with my experiences because I know how frustrating it is when this doesn't work!
dennis333 said:
Some of your problems I had to. To be exact: that my pc wouldn't recognize the phone when connected with usb except for fastboot and charging.
For weeks I searched and found some people with similar problems, but never a solution.
I had no problems with my sdcard however.
Now my problem is gone. How? I had the HTC Generic 2.73.405.5 ROM (pre-rooted and packaged as update.zip by MoDaCo) and decided to update to Paul's ROM v2.5.
After I was finished with the installation wizard and connected the phone with usb to my pc everything suddenly worked again!!!
So I got the usb and HTC Sync notification at the top of the screen and can mount the sdcard using the notification bar.
This tells me that in my case it definately wasn't a hardware problem as I always thought, but a software one.
I hope you can something with my experiences because I know how frustrating it is when this doesn't work!
Click to expand...
Click to collapse
I tried this but it didn't seem to work for me, so I just put the official rom update and sent the phone back to my network saying that it was broken, now i've gotta wait for another 2-3 weeks to get my phone back , but i'm hoping they'll give me a new phone as i did kinda drop it and there two scuff marks on it
hello dennis333,
today I tried going from 2.8 to the HTC generic ROM you told, and then to 2.5. no results.
I also installed the official HTC / Orange Rom update, which I have now. It has improved a bit because now when I plug the USB cable the PC detects something, but it does'nt work... it says 'unknown device' (tried this on two computers)
when I boot to fastboot ( BACK + POWER BTN ) my computer detects Hero ok (My Htc)
I really don't know what else to try...
I saw another post from someone who had the exact same problem and got it fixed by installing SPL and ROM from fastboot menu
http://forum.xda-developers.com/showthread.php?t=556038
I tried it too, but when trying to use the SPL zip file he says I get an error ( I guess it's because he has a T-Mobile and I have an Orange Hero)
[update]: I finally got the SPL to flash correctly and then installed a modaco 2.8 ROM, but I still cannot connect the Htc Hero to the PC via USB.
regards

[Q] Changed Recovery now "Can't mount /sdcard" - SOLUTION

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!!

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

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

Flashed without Correct CID

Hi Everyone,
I did a boo boo. I flashed my One X without a supported CID with the Android Revolution 14.2 ROM. Is there a way to correct this and revert back to my previous ICS? Help please.
There's a Q&A section especially for Questions and Answers, please use that in future.
That being said you wouldn't have been able to update the hboot so just reflash an ICS rom
ClydeB1 said:
There's a Q&A section especially for Questions and Answers, please use that in future.
That being said you wouldn't have been able to update the hboot so just reflash an ICS rom
Click to expand...
Click to collapse
I'm having problems moving an ICS ROM to the phone to flash it. Whenever I connect the phone to my notebook, the MTP USB device driver is unable to install. because of that Windows could not recognize the phone. I also tried to mount the sdcard in CWM. It is giving me a 'unable to open ums lunfile..." error message.
Is there any other way to flash the phone? I tried "fastboot flash zip rom.zip". It showed OKAY for the copy, however, a second line remark "writing 'zip' ... FAILED (remote not allowed)" appeared. The process then was aborted.
I also tried formatting the sdcard and then tried to mount the sdcard. Same 'unable to open ums lunfile...' error constantly appears. Just afraid that my phone is now a brick. Can anyone help? Thanks in advance.
kevintan12 said:
I'm having problems moving an ICS ROM to the phone to flash it. Whenever I connect the phone to my notebook, the MTP USB device driver is unable to install. because of that Windows could not recognize the phone. I also tried to mount the sdcard in CWM. It is giving me a 'unable to open ums lunfile..." error message.
Click to expand...
Click to collapse
Install a version of CWM that isn't ancient, I.e., 5.8.4.0.
I suspect that I hard brick my phone now.
Following some advice to "fastboot flash recovery recovery.zip", not the phone is unable to even get into recovery mode. when I select recovery, it just comes back to the bootloader screen. I tried to flash CWM again and the message I got was "error: cannot load cwd....img"
Funny thing though, when i select HBOOT, some messages appears and disappears saying "Failed to open sdcard, dalvik, cache, etc. etc." I believe that is why windows is unable to recognize the USB drive and is unable to install the drivers.
Have I hard brick my phone?
kevintan12 said:
I suspect that I hard brick my phone now.
Following some advice to "fastboot flash recovery recovery.zip", not the phone is unable to even get into recovery mode. when I select recovery, it just comes back to the bootloader screen. I tried to flash CWM again and the message I got was "error: cannot load cwd....img"
Funny thing though, when i select HBOOT, some messages appears and disappears saying "Failed to open sdcard, dalvik, cache, etc. etc." I believe that is why windows is unable to recognize the USB drive and is unable to install the drivers.
Have I hard brick my phone?
Click to expand...
Click to collapse
No, everything is recoverable, if your phone won't turn on at all, then you're bricked for real.
Just flash the one from here:
http://download.clockworkmod.com/recoveries/recovery-clockwork-touch-5.8.4.0-endeavoru.img
then put in the same folder as fastboot and use command:
fastboot flash recovery recovery-clockwork-touch-5.8.4.0-endeavoru.img
Thanks everyone for the advice. Really appreciate it. I finally managed to use TeamWin Projects and it allowed me to mount the USB. Managed to then transfer an ICS ROM for flashing.

quick hand with adb

OK so I put the newest nightly for CM10 onto my Nexus and it has been a while since I did a clean install so I performed a full wipe, but accidentally wipped the sdcard as well. Soooo, I have no update on the phone to flash via recovery and I wiped sysetem, data etc.... so I got nothing.
I know I can either flash the update via fastboot, or send the update to the sdcard via abd but for the life of me I cannot remember how to do either. This is my only phone and im home alone with my two kids right now so I need it fixed asap. Everything I have found doesn't seem to be working for me. I tried
while in recovery mode hook phone to computer via usb, then open cmd and "abd push c:\android\platform-tools\update,zip (I renamed it to this) /sdcard
No luck there.
I also tried from fastboot mode :fastboot flash update update.zip" Thought I had success here because it was sending the date but the phone still wouldn't boot past the "Google" screen.
I know someone on here has the answer for me easily, and it would be much appreciated if anyone could help me out.
Thanks in advance
brunswick000 said:
OK so I put the newest nightly for CM10 onto my Nexus and it has been a while since I did a clean install so I performed a full wipe, but accidentally wipped the sdcard as well. Soooo, I have no update on the phone to flash via recovery and I wiped sysetem, data etc.... so I got nothing.
I know I can either flash the update via fastboot, or send the update to the sdcard via abd but for the life of me I cannot remember how to do either. This is my only phone and im home alone with my two kids right now so I need it fixed asap. Everything I have found doesn't seem to be working for me. I tried
while in recovery mode hook phone to computer via usb, then open cmd and "abd push c:\android\platform-tools\update,zip (I renamed it to this) /sdcard
No luck there.
I also tried from fastboot mode :fastboot flash update update.zip" Thought I had success here because it was sending the date but the phone still wouldn't boot past the "Google" screen.
I know someone on here has the answer for me easily, and it would be much appreciated if anyone could help me out.
Thanks in advance
Click to expand...
Click to collapse
Try ...
adb push c:\android\platform-tools\update,zip /sdcard/
or
adb push c:\android\platform-tools\update,zip /data/media/
fastboot flashes .img files
Ok so I have figured something strange out here. I thought that I had accidentally wiped the sdcard. I thought this because in recovery I select "install from sdcard" and then "choose zip from sdcard". Then I see " 0/ " It didn't even occur to me that everything was in there because that has never happened before. I would love to just restore a nandroid I have saved, but when I select restore in recovery it tells me that no files are found, because they are in "0/sdcard/". If I navigate there in recovery I can see the nandroid but CWM cant find it. Any ideas on this??

Categories

Resources