Long story here. My desire has decided to become sd bricked
Hboot version is 0.93
Software is 2.29.405.5
Phone is not routed and is s-on.
I can use adb and fastboot but I cant do anything that requires the sd card. Can someone please help me in getting the sd card working again please.
John
did you already triy the "fastboot oem enableqxdm 0" command in fastboot mode?
Yes it comes back with
fastboot oem enableqxdm 0
...
FAILED (status malformed (1 bytes))
finished. total time: 0.000s
You need to have s off to use that command. Follow the root and s off guides in the development forum then try again.
Sent from my Motorola Startac running Atari 2600 software!
I've ran unrevoked and it says I am rooted and titanium backup runs.
I tried alpharev to get s off and it doesn't appear to work, it cant find my phone.
John
no you don't need s-off.
i think you are in the wrong directory. The fastboot.exe is in the folder tools,
so you have to change the directory in cmd and then "fastboot oem enableqxdm 0".
(also fastboot mode on your desire)
You tried reformatting the SD using "SD Formatter"?
Also, which ROM were you running? Some roms dont seem to boot (stuck on HTC logo screen) if theres probs with the SD card format - especially if your sd-ext is ext 4.
Can you boot into recovery? If so and you arent bothered about losing phone data, format your SD (using SDFormatter), stick something like LeeDroid 2.3d on and flash it (with full wipe).
Maybe this'll help:
http://forum.xda-developers.com/archive/index.php/t-1070863.html
Related
Hello everyone!
I have run into problems with my hero since I flashed Drizzy's hero rom.
My sd card reader is no longer functioning and hence I am locked into drizzy's rom without any possibility of any kind of sd card use.
The sd card can't be read from cyanogens recovery even.
Is there any way to put a new rom on the phone without access to the sd card?
(I have root if that helps)
Thanks in advance,
Hampan
Can I use the fastboot update command without an sd-card available to the phone?
you can push (=upload) with adb (command is: adb push [local] [remote]) a file to the sdcard (just connect your phone via usb to computer)
example:
update.zip is here: C:\update.zip
then do:
adb push C:\update.zip /sdcard/update.zip
then it will upload the file (about 5-10 minutes).. ready to flash
Thank you for your reply , no I can't make adb connect to the phone.
Only fastboot works, and even if adb was working I couldn't possibly make it push the update to the sdcard since the phone can't see the sd card at all.
and you are even not able to access the sdcard via cyanogen recovery AND adb shell??
No exactly, the sd card can't be reached from ANYTHING , adb shell won't connect although fastboot does, and i can use fastboot commands.
I tried using the "fastboot update update.zip" with modacos rom but got the message:
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
I'm thinking maybe one can flash the device without putting anything on sd via "fastboot update" .. can anyone confirm?
simply restore your nandroid backup that im sure you did.
./fastboot flash system system.img
./fastboot flash userdata data.img
./fastboot flash boot boot.img
./fastboot reboot
Thanks for your reply, yes I did make a nandroid backup and copied it to my pc
However, as it stands now I can only reach the phone from the computer with fastboot, usb is not recognized in windows and sd card is not functioning (even in cyanogen fastboot).
So, if I use my old stock nandroid backup and somehow the sd and usb is still not functioning, would there be a possibility that I would be stuck with the old slow rom forever?
Thanks for any help!
keatonreckard said:
simply restore your nandroid backup that im sure you did.
./fastboot flash system system.img
./fastboot flash userdata data.img
./fastboot flash boot boot.img
./fastboot reboot
Click to expand...
Click to collapse
Yup, now I tried .. doesn't work
C:\android-sdk-windows-1.5_r3\tools>fastboot flash boot boot.img
sending 'boot' (2560 KB)... OKAY
writing 'boot'... INFOsignature checking...
FAILED (remote: signature verify fail)
I'm sh*t out of luck aren't I?
maybe the remaining option is to send it to htc... :-( but that will cost money cuz you lost the garanty
Yup, that, sadly -Is my conclusion as well.
Anyway, the phone works as usual , just no SD and no updates.
Since I have no warranty I might just wait until a new android version is released for Hero.
Thank you all for replying and trying to help me.
stupid question, but did you check to see if it is the micro sd that went bad, not the reader? you don't need to embarrass yourself by responding, I just hope it helps if that is what it was.
I have the same problems and follow these threads:
http://forum.xda-developers.com/showthread.php?t=556335
http://forum.xda-developers.com/showthread.php?t=559106
Can't you try to 'update' (restore) it with the htc RUU .exe
?
not totally sure since i dont have a hero myself, but i think this might work...
Hey guys!
My SD card won't mount in Recovery mode... When I try to flash zips or partition the SD card I get the following error:
Code:
E:Can't mount /dev/block/mmcblk0p1 (or /dev/block/mmcblk0)
(No such file or directory)
Upon further reading, I've tried going into Fastboot (which does work thankfully) but every command I use, including:
Code:
fastboot oem enableqxdm 0
Chucks me the following error:
Code:
... FAILED (status malformed (1 bytes))
I'm totally at a loss here guys, and I'm way out of my depth with this one. Any help would be appreciated!
first try fastboot devices
to see if ur phone is detected
It does list the device in Fastboot, but not in adb shell devices :S
now re type fastboot oem enableqxdm 0
FAILED (status malformed (1 bytes))
type fastboot oem boot
then take a print screen of the writing
ur phone will reboot
Same error.
let me look for a fix
is ur desire s-off
Yup. It's running AlphaRev's 1.8 HBoot with S-OFF
HBoot version is 0.93.0001
what does fastboot devices show
dont post ur full serial number
dont post ur full serial number
dont post ur full serial number
dont post ur full serial number
dont post ur full serial number
just post the first two letters or numbers
HT*********421
Blanked of course
good ok do u have a sd card reader i.e sd to usb
do u have windows 7 or xp and are the hboot and fastboot drivers installed propery
I have all of the above. I've been installing ROMs for some time now, its only just happened after I installed AlphaRev's Hboot.
the only thing i can say is do u have a ruu for ur phone if not i can find 1 for u
I've downloaded the RUU.exe for my phone, but it requires a working ROM in order to work, of which I don't have. :-/
not true i used my ruu from fastboot usb plug
run the ruu
It's an .exe... you saying just to Run that? I've ran it and it tries to find the phone, but it can't as it searches for USB debugging, but since theres no running ROM it fails.
what os are u on win 7 or xp
Hi All,
Via a particularly stupid series of steps I've ended up with:
1) stock boot 0.93 (S-ON)
2) RA-desire-v2.0.0 recovery image which won't mount the sd card.
(Can't mount /dev/block/mmcblk0p1 etc.
3) Result of half way through alpha rev process:
AlpahRev SPLBOOT version 2.0
New NAND detected. Possibly Bravo PVT4.
Dumping old HBOOT.
Flashing AlphaRev HBOOT:
Flashing AlphaRev HBOOT: Verifying HBOOT: Old HBOOT matches.
Procedure soft-failed. We were unable to flash HBOOT, but the old BHOOT is still in place.
Reminder: your phone is not bricked. Restart the procedure and try again. You may need to restore your most recent nandroid backup from recovery.
Snag is with out sd working in recovery I can't do that.
I don't have a gold card.
Anyone know of a way out of this mess?
At least partly out of the mess via:
fastboot oem enableqxdm 0
found in a post on [email protected] forums.
Thanks due to ZiCon and sorry for the noise to everyone else.
as posted above, in fastboot, type:
fastboot oem enableqxdm 0
fastboot oem eraseconfig
Should get your SD card back up and running.
i had a similar issue with mine.. cm7 hboot, recovery and looping os.. try connecting your SD car to your computer and see if you can get the files off, then format it all as a FAT32 partition and try to repartition on the device.. it worked for me after a few tries, plus various other fiddling..
It all started when i tried to flash Insertcoin's Sense 2.1+ GB ROM. That involve messing about with partitions. I have re-formatted several times and erased all partitions, but still no help. the phone doesn't boot up, When SD card is in the phone, only the most basic android splash screen comes up and stays there. If my SD card is not on the phone. it is able to boot to the ROM, but nothing can be accessed, there is no keyboard, i can't answer calls, because the screen is just blank (apart from background image). also in Recovery mode i can't "choose zip from sdcard" because of the "E: can't mount /dev/block/mmcblk0
(or /dev/block/mmcblk0)" error.
edit: I tried un-rooting from http://forum.xda-developers.com/showthread.php?t=696189 thread. and in the beginning of the un-rooting it gave me the ERROR [140] BOOTLOADER VERSION ERROR. Now when SDcard is in, the boot process stops at HTC's own splash screen and when it's out of the phone, i can still access the obviously misinstalled ROM. At this point i'm very confused about what to do next. Can anyone help me?
Can you access and use fastboot??? If you can -
fastboot oem enableqxdm 0
and then
fastboot oem eraseconfig
That should fix your sd card mounting again....
i'm not really familiar with that command. In fastboot menu i can see Bootloader, Reboot, Reboot Bootloader and Power Down menu items
edit: okay, i understand you mean using that with cmd. Well, adb devices command shows no devices attached,
Amphor said:
i'm not really familiar with that command. In fastboot menu i can see Bootloader, Reboot, Reboot Bootloader and Power Down menu items
edit: okay, i understand you mean using that with cmd. Well, adb devices command shows no devices attached,
Click to expand...
Click to collapse
Not adb -
Boot to bootloader (vol down + power )
plug in usb - bootloader will change to say usb is plugged in
Boot fastboot - scroll down to and press power - bootloader will again change to show fastboot mode
open CMD then type -
fastboot devices
- if nothing happens make sure you have changed your directory to where fastboot.exe is stored
e.g. (is how my hard drive is set up but yours will prob be different
cd C:/android/tools
When fastboot devices command shows your phone -
fastboot oem enableqxdm 0
fastboot oem eraseconfig
That will re-eastblish your usb again
What set up do you have?? S-off?? Sd card partitioned etc... Hboot (all info from bootloader)
Oh and do you actually want to unroot or are you just trying to fix it?
i am just trying to fix it, any means necessary, whether it's unrooting or not
s-on, in the recovery menu there is format sdcard and format sd-ext. so, i would think that there is a partition, but not sure.
oh, and
C:\Users\Amphor>fastboot oem enableqxdm0
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.019s]
finished. total time: 0.020s
C:\Users\Amphor>
normal behaviour? Still can't choose zip from sdcard
http://forum.xda-developers.com/showthread.php?t=691639
Should get you going unless someone else has an easier way?
Not really sure what it did, but definitely not did it fix my problem. The solution was for some kind of USB connectivity issue which i have luckily. Wasn't it?
Amphor said:
Not really sure what it did, but definitely not did it fix my problem. The solution was for some kind of USB connectivity issue which i have luckily. Wasn't it?
Click to expand...
Click to collapse
http://forum.xda-developers.com/archive/index.php/t-1077985.html Read that one .... I believe it is pretty much the problem you have?
C:\Program Files (x86)\Android\android-sdk\tools>fastboot oem enableqxdm 0
...
OKAY [ 0.024s]
finished. total time: 0.024s
C:\Program Files (x86)\Android\android-sdk\tools>fastboot oem eraseconfig
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.007s]
finished. total time: 0.008s
was my error, as was his. Strrangely, this time the first command didn't give me an error. But yeah, this is the problem pretty much yes. And there were no other solutions given, apart from the two lines in fastboot. Also, the last post stated that i have to be S-OFF to use fastboot (properly), but i am S-ON. Also, i couldn't find a way to format the card to fat, not fat32
Amphor said:
C:\Program Files (x86)\Android\android-sdk\tools>fastboot oem enableqxdm 0
...
OKAY [ 0.024s]
finished. total time: 0.024s
C:\Program Files (x86)\Android\android-sdk\tools>fastboot oem eraseconfig
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.007s]
finished. total time: 0.008s
was my error, as was his. Strrangely, this time the first command didn't give me an error. But yeah, this is the problem pretty much yes. And there were no other solutions given, apart from the two lines in fastboot. Also, the last post stated that i have to be S-OFF to use fastboot (properly), but i am S-ON. Also, i couldn't find a way to format the card to fat, not fat32
Click to expand...
Click to collapse
Is your sd card partitioned correctly??? How is is set up exactly??? Make sure that your partitions are EXT 3 /4 NOT LOGICAL
You still can't access SD card in recovery?
would you define "correctly"?
Finally got a chance to test with another card and i can access sd card from recovery. And i think the dog is buried under the issue that the testcard is FAT, but mine is FAT32. though my 8GB card couldn't be FAT. So what was it?
And again, what is correctly. If i look with Gparted, then my card has 7.40 gb and 512 mb partitions (dev/sda and sdb) and i can't delete that 512 mb one
Amphor said:
would you define "correctly"?
Finally got a chance to test with another card and i can access sd card from recovery. And i think the dog is buried under the issue that the testcard is FAT, but mine is FAT32. though my 8GB card couldn't be FAT. So what was it?
And again, what is correctly. If i look with Gparted, then my card has 7.40 gb and 512 mb partitions (dev/sda and sdb) and i can't delete that 512 mb one
Click to expand...
Click to collapse
Ah.... Insert coin states requirements - A2SD+ STOCK HBOOT - stock hboot - the one with 250 mB for /system
- 1 gB ext2/3/4 partition
So your correct sd card setup is FAT 32 7GB and 1GB EXT 3/4
If I were you I would backup ALL files from Sd card to computer...
Format your sd card with gparted..
New partition - Fat 32 - 7gb
New partition - Ext 3 or 4 - 1 gb
Apply
Transfer all files back to your sd card
Put in phone and see if it's fixed?
Make sure you are using the Stock HBOOT version of insert coin... I'm surprised nothing has got you up and running so far ?!
My problem is the mounting, not the "not booting" issue, still
but yes, thats why i started mazking partitions in the first place
Amphor said:
My problem is the mounting, not the "not booting" issue, still
but yes, thats why i started mazking partitions in the first place
Click to expand...
Click to collapse
I know I didn't mention not booting....
either way, it didnt solve my problem
Well if none of the 3 suggested fixes work... I'm out though
Good luck
Hello,
I posted this in the General section by mistake.
My HTC desire won't read the SD card. It is not a problem with the card since I tried it on Windows & other phones and it works + Tried cards that work in other phones and won't work on mine.
What do I have access to:
- The phone is S-OFF
- I have Clockworkmod Recovery
- I can't see the card from the recovery either ("Can't mount /sdcard")
- my phone is not rooted
- I have stock 2.2 android (2.29.405.5)
- I have the drivers installed on my PC and I can access the phone via abd or fastboot
I have tried:
"fastboot oem enableqxdm 0" from fastboot, it didn't fix it.
Unbrick from 4eXT Recovery:
Asked a coworker for his working SD Card
Used the "fastboot oem enableqxdm 0"
Installed "4eXT Recovery Touch v1.0.0.5 RC9"
Entered Recovery with msg "Error mounting your card .... "
Tools > Usb unbrick
"Your CID: HTC__032
Patching misc image..
Your misc partition size: 640kb
Writing mtd0..
Done.. please reboot!"
After reboot the same issue "Error mounting your card .... " in Recovery, loaded rom: No SD card
Returned the card to my coworker, card is still functional in his phone.
I am opened to suggestions. Worst case scenario: Hardware malfunction
Ty,
Danny
One additional question:
Assuming that I can't get my SDcard to work. Is there a way to install custom rom's?
I have s-OFF, Clockworkmod and adb + fastboot access. Can I flash a new rom from fastboot?
I tried like this with no success:
fastboot erase cache
erasing 'cache'...
OKAY [ 0.284s]
finished. total time: 0.284s
fastboot oem rebootRUU
...
OKAY [ 0.092s]
finished. total time: 0.092s
fastboot flash zip Official_Stock_Sense-Gingerbread_v1.2__GB-2.3.3_A2SD.zip
sending 'zip' (146730 KB)...
OKAY [ 21.102s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 24 parsing android-info fail)
finished. total time: 29.371s
Danny
Im not an expert but it seems to be a hardware issue.
Also, if i would be in your situation i would try to change the hboot. Not sure if it has anything to do with it though. Like i said, not an expert.. but id try it anyway hehe..
Wait for someone with more knowledge on this matter to reply or take it to the service.
Please don't change hboot, it has nothing to do with your problem...
You only change hboot before you flash a rom to match the rom's /system size in order to maximize /data (internal memory)
To flash a rom you don't do it thru fastboot, you need to do it thru recovery like normal (full wipe then install zip from sdcard)
However it's strange why your phone can't detect your sdcard. suspect might be hardware after your current logical testing.
Last thing I would try is to delete all partitions and reformat to FAT32 partition using gparted, see if phone detects it after that
What is the capacity of your SDcard? (32Gb maximum for Desire if i'm right)
zinconnu said:
What is the capacity of your SDcard? (32Gb maximum for Desire if i'm right)
Click to expand...
Click to collapse
Just 2 GB and I also tried a 8 GB
If your sd-card is working in computer, so that is something wrong with the phone. Can you access your sd-card from recovery? If not, the system won't too.