[Q] Think I've bricked my Desire, help needed! - Desire Q&A, Help & Troubleshooting

Hello, I was happily using a previous miui build and updated using ROM Manager and it was going fine until the phone stopped being able to recognise the SD card whatsoever, so I tried looking that up, and was finding things about reformatting memory cards, trying different ones etc. I tried all these things to no avail, I am now trying to RUU it back to a stock Sense ROM in the hope that will fix the SD card problem but when I try to connect it via USB to the PC it isn't recognised at all. I've tried installing HTC Sync etc. I've no idea what to do anymore?
ANY ideas much appreciated!
Thanks~

You have a classic USB brick. Don't panic, it's pretty frequent. Try this: http://forum.xda-developers.com/showthread.php?t=691639&highlight=usb+brick

It says on that article ' SD card functionality has to work' at the minute the Desire won't recognise the SD card whatsoever!
When they are giving these instructions, are they assuming that your phone is connected to a computer and in the adb thing?
Thanks so much!

matthewamac said:
It says on that article ' SD card functionality has to work' at the minute the Desire won't recognise the SD card whatsoever!
When they are giving these instructions, are they assuming that your phone is connected to a computer and in the adb thing?
Thanks so much!
Click to expand...
Click to collapse
Retarded post: Download a terminal program and: For this, do 'fastboot oem enableqxdm 0' in fastboot mode. Strike that.
Can you boot in Fastboot ? Back arrow + power.
Is your phone visible to the computer in fastboot ?

Don't jump into restoring an RUU as you will really be in trouble then!
Trust me, I've bricked mine and gone down this road to put it right and it can be done.
Get hold of Android-SDK (Google it), get that installed and prepare to learn. In my case I managed to restore SD card functionality and thought I had won, then discovered that I still had a USB brick. Nevertheless, many hours reading and several vodkas later I had it fully restored.
If you still have clockwork recovery on the phone (I'm assuming you're using that?) then it's a pretty easy fix, don't panic! And above all, don't attempt to go back to stock as then you'll still have a knackered phone but with no root to recover it (although I doubt you can if your phone can't read it, unless you learn the fastboot stuff and flash the RUU before actually fixing the problem).
The thread linked gives some idea, there's also a lengthier one, search 'USB brick'.

And good point by paul.c, that would be far simpler but I've never tried it myself - although esentially that is indeed the command required to get the SD card working again.
Just beware that getting the SD card working may not be the end of your woes, you may then find (as I did) that USB functionality is broken and bluetooth doesn't work, classic 'USB brick' symptoms. Again, pretty easily fixed.

paul.c said:
Retarded post: Download a terminal program and: For this, do 'fastboot oem enableqxdm 0' in fastboot mode. Strike that.
Can you boot in Fastboot ? Back arrow + power.
Is your phone visible to the computer in fastboot ?
Click to expand...
Click to collapse
Yes, I can get to fastboot ok and the phone's recognised in it. I've been trying to use the command prompt & do 'adb devices' but that's not working it states 'adb' is not recognized...etc. Should I be doing the 'fastboot oem enableqxdm 0' in a terminal on the phone or in the SDK on my computer ?

matthewamac said:
Yes, I can get to fastboot ok and the phone's recognised in it. I've been trying to use the command prompt & do 'adb devices' but that's not working it states 'adb' is not recognized...etc. Should I be doing the 'fastboot oem enableqxdm 0' in a terminal on the phone or in the SDK on my computer ?
Click to expand...
Click to collapse
Adb only works when running a rom. You have to run this comment in android sdk on your computer.
Swyped from my HTC Desire using XDA App

MatDrOiD said:
Adb only works when running a rom. You have to run this comment in android sdk on your computer.
Swyped from my HTC Desire using XDA App
Click to expand...
Click to collapse
So for Android SDK should you be properly booted or should you be in the Fastboot screen?

matthewamac said:
So for Android SDK should you be properly booted or should you be in the Fastboot screen?
Click to expand...
Click to collapse
If you have to issue fastboot commands your phone has to be in fastboot.

paul.c said:
If you have to issue fastboot commands your phone has to be in fastboot.
Click to expand...
Click to collapse
My SDK is working fine for commands such as 'ADB Devices' now but when I go into Fastboot and give the command 'fastboot' it states that it's not recognized! Do you have to have S-Off for this to work?

Well... you start your phone.. by pressing.. Vol down and power.. than connect your phone with usb cable to pc ... open command prompt.. got to your sdk folder "platform-tools' and than enter ADB or Fastboot command..
But when you connect your phone to PC.. check if ADB drivers are installed.. go to device manager and check if your phone is recognised as ADB interface under Android Phone

jhonybravo4u said:
Well... you start your phone.. by pressing.. Vol down and power.. than connect your phone with usb cable to pc ... open command prompt.. got to your sdk folder "platform-tools' and than enter ADB or Fastboot command..
But when you connect your phone to PC.. check if ADB drivers are installed.. go to device manager and check if your phone is recognised as ADB interface under Android Phone
Click to expand...
Click to collapse
Ah, I just looked in my platform-tools folder and there was adb etc. but I could not find fastboot. Where can I download that?
In the device manager, it's under 'Android USB Devices' as 'My HTC' is that ok?

OK, I have the SDK working fine, but when I go to this ( http://ks25738.kimsufi.com/misc/index.php ) website to get the .img file I need I can't figure out my kernel/ROM number - in the settings it says:
Android Version
2.3.4
Baseband Version
32.54.00.32U_5.14.05.17
Kernel Version 2.6.37.6-cyanogenmod-01494-g8dc02ff
[email protected]
Build Number
MIUI.1.6.17
The wesbite states the number should be 10 characters long, anyone know which one the ROM number is?
Thanks

You are once again trying to flash an RUU. Do not do this without first fixing your SD card problems.
fastboot oem enableqxdm 0
and also
fastboot oem eraseconfig
Need more details on where you are at. If you don't fix the issues you have then flashing an RUU could leave you in a much worse situation than you are now, and where you are now is easily fixed!

Parva4 is right.. you should 1st try enabling your sd card....
what you need to do is...
first download adb drivers for your device...
power on your phone into fastboot.. by pressing volume down and power.. connect usb cable to pc.. and in device manager.. update driver to adb driver.. while in hboot.. and than run that fastboot command which Parva4 mentioned.

I sorted it out, thanks to all who helped!
I did the fastboot enableqxd 0 command to unlock the SD card then once that was able to be used I flashed back to a nand backup I had made minutes before I did the flash that went wrong and now it's working fine!

Related

Cannot mount SD card in boot recovery [resolved thanks to mariosraptor]

Hi XDA Community!
Completely bone-headed n00b here (is there any other kind)?
Firstly, a quick background:
HTC Desire, rooted, S-Off, 16 gig Class 4 SD card with 1 gb ext4 partition
I was flashed with a perfectly working Leedroid 2.2f rom, overkill backed up with Clockwork, AmonRa, Titanium, MyBackup Pro, complete SD card backup (you name it, I did it), then wiped and flashed ownhere's Rom because I was running out of app space. The flash was successful then I proceeded to backup ownhere's rom after re-installing all my apps and I think that's where the problem began. I began my first backup with Clockwork via Rom Manager, but was not getting any response, so I rebooted my phone into Clockwork Recovery and backed up ownhere's rom there. After that, I could not turn on my phone.
I'd appreciate if someone could point me in the right direction. As of right now, my phone goes into a vicious boot loop whenever I try to turn it on. I can still get into hboot by holding down the power button and volume down button and then get into Android system recovery (Amon Ra Recovery, build: RA-desire-v2.0.0) by selecting "recovery", but when I try to do a nandroid restore, the error message I get is:
E:Can't mount /dev/block/mmcblk0p1 (or /dev/block/mmcblk0)
(No such file or directory)
E:Can't mount SDCARD:/nandroid/
I've googled many times and have attempted to follow the steps outlined by various tutorials with similar sounding problems, but unfortunately to no avail. I've tried formatting my SD card on my computer, re-partitioning the SD card on my phone (not sure if that was successful), wiping it, attempting to restore it, attempting to flash it, but I keep getting that same error message above in the end.
I certainly don't deserve it after what I've done, but any help would be greatly appreciated! Thanks for having the patience to read.
EDITED: Below are the steps I took to resolve the issue.
First and foremost, I'd like to point out that prior to encountering this problem (or any problem for that matter), I did a very thorough job of backing up my entire phone multiple times through various methods, but it turns out I only really needed a single nandroid backup and mariosraptor's help. Still, better safe than sorry, I say, which is ironic considering what I did to my phone. Ah well.
Anyway, after running into my problem as described in my OP (original post), the following steps were needed to restore functionality to the phone:
1) With the phone turned off, I booted it into Fastboot by either a) holding down volume rocker+power on button, then choosing "fastboot" or b) holding back button+power on button, which takes you straight into "fastboot".
2) Once in fastboot, I connected my phone to my computer via USB cable.
3) I'm not sure if I needed it running or not, but I then ran Android SDK (a program I used back when I first got my phone and was tinkering with rooting and forcing apps to install onto the SD card before I learned about SD card partitioning and AP2SD/AP2SD+ supported roms and now DATA2SD/DATA2EXT). This program can be downloaded here and an example of how it's used is here, but I'm assuming (I know I shouldn't assume, but I can only describe things I've done or have already done) anyone who as gotten this far already has this program and used it before, even with limited knowledge.
4) I then went into my Start Menu in Windows and ran command prompt. The simplest way to run command prompt, I find, is to type "cmd" into the run dialog, then enter.
5) Once command prompt popped up, I typed in cd\ to change the directory to C:\ and then entered in cd android-sdk-windows/tools to open the directory to c:\android-sdk-windows\tools (I just noticed that you enter in /backsplashes, but end up with \forwardslashes, weird!).
6) I then typed in the fastboot commands as outlined by mariosraptor, that is, I entered "fastboot oem enableqxdm 0" pressed enter, let it finish, then typed in "fastboot reboot" and enter. Wait for phone to reboot, could take a while.
I'm hoping for most people those are all the steps needed in order to restore the phone, but in my case, after entering "fastboot oem enableqxdm 0", I received an error saying: "The program can't start because AdbWinApi.dll is missing from your computer. Try reinstalling the program to fix this problem." I was about to re-install when mariosraptor provided me with the AdbWinApi.dll file here. This is rapidshare link so it will expire. My suggestion is to search for it somewhere (google) if you run into the same missing file as me.
My problem actually didn't stop there either. I found my phone was stuck on the boot animation, although I supposed I could've left it even longer just to make sure it wasn't working, but I actually took my battery out to shut the phone down. I then proceeded to do a nandroid restore to a previous backup I had done before I created this whole problem. I did that by booting the phone into recovery by holding down volume rocker+power button, selecting "recovery", then selecting "nandroid backup/restore" and letting the process go through fully, which took quite some time.
Anyway, it's been a long 20 or so hours for me. I'm going to go rest now. Props again to mariosraptor!
in fastboot mode through adb cmd
fastboot oem enableqxdm 0
fastboot reboot
as long as you are S-off you can use fastboot commands and it is recommended that whatever you do from the moment that youre S-off'd you use fastboot and adb for various works on your Desire.
for more fastboot commands in adb just type fatboot
Hey mario, thanks for the quick reply.
I'm currently reading ADB for Dummies to figure out what you're talking about and will get back to you. I know I've used it before when I rooted my phone, but I was just following step-by-step instructions and had no idea what I was doing.
I recall seeing "unknown device" in device manager while my phone was plugged into my computer via USB during one of my recent attempts at fixing my current issue.
PS. I'm on Windows 7.
So I haven't been able to get far. I've noticed all the ADB commands that need to be entered in command prompt require me to have my phone in "USB debugging mode" by going into in Settings>Applications>Development, but I can't even turn on my phone to get there.
Am I missing something from your instructions? Sorry, my knowledge is quite limited.
When you are in Amonra, you are automaticly in "adb mode" so you can ignore that step. You should however install htc sync for the drivers needed.
turn off your phone by removing battery. press the back button+power on. you are in fastboot mode. the correct cmd's are fastboot commands.
like "fastboot reboot-bootloader" w/o the quotes.
ayato kamina said:
So I haven't been able to get far. I've noticed all the ADB commands that need to be entered in command prompt require me to have my phone in "USB debugging mode" by going into in Settings>Applications>Development, but I can't even turn on my phone to get there.
Am I missing something from your instructions? Sorry, my knowledge is quite limited.
Click to expand...
Click to collapse
Gotcha, I was able to get into "fastboot USB" by following your back button+power on (or down volume+power, then selecting fastboot) and connecting a USB cable to from the phone to my computer. I then went into command prompt (cmd) in the start menu. Typed in:
1) cd\
2) cd android-sdk-windows\tools
3) entered in "fastboot oem enableqxdm 0"
I then received the error message: The program can't start because AdbWinApi.dll is missing from you computer. Try reinstalling the program to fix this problem.
That will be my next step is to re-install Android SDK Windows.
Will report back, thanks!
Lennyz1988 said:
When you are in Amonra, you are automaticly in "adb mode" so you can ignore that step. You should however install htc sync for the drivers needed.
Click to expand...
Click to collapse
Thanks for pointing that out, Lenny. I didn't know that. I'm not sure if I have the HTC Sync drivers, but in fastboot mode (as instructed by mario), I checked device manager in properties of My Computer and the unknown device exclamation icon is gone. I see, ADB interface>HTC Bootloader.
http://rapidshare.com/files/380196682/AdbWinApi.dll
donload it from the link and put in tools foder of SDK
mariosraptor said:
http://rapidshare.com/files/380196682/AdbWinApi.dll
donload it from the link and put in tools foder of SDK
Click to expand...
Click to collapse
Phew! Thanks Mario! I was struggling to re-install Android SDK for some reason. A problem with Java SE JDK. *shrugs*
Will continue now....
i hope it helps. i will see more tomorrow. good luck!!!
ayato kamina said:
Phew! Thanks Mario! I was struggling to re-install Android SDK for some reason. A problem with Java SE JDK. *shrugs*
Will continue now....
Click to expand...
Click to collapse
PROGRESS!!
So I'm finally passed the S-off splash screen and am waiting on the boot animation screen. I expect there to be a problem because I've been formatting and partitioning my SD card so much, the card itself may actually be empty at the moment (not sure). I will wait for while and if nothing changes, I'm going to restore my SD card and try again.
Thanks for getting me this far so far, Mario! Much appreciated!
just let see what happens and hopefully it will work again.
ayato kamina said:
PROGRESS!!
So I'm finally passed the S-off splash screen and am waiting on the boot animation screen. I expect there to be a problem because I've been formatting and partitioning my SD card so much, the card itself may actually be empty at the moment (not sure). I will wait for while and if nothing changes, I'm going to restore my SD card and try again.
Thanks for getting me this far so far, Mario! Much appreciated!
Click to expand...
Click to collapse
mariosraptor said:
in fastboot mode through adb cmd
fastboot oem enableqxdm 0
fastboot reboot
as long as you are S-off you can use fastboot commands and it is recommended that whatever you do from the moment that youre S-off'd you use fastboot and adb for various works on your Desire.
for more fastboot commands in adb just type fatboot
Click to expand...
Click to collapse
my phone is connected,drivers are installed and it is available in fastboot. But when I am typing "fastboot oem enableqxdm 0" it returnes: "... FAILED (status malformed (1 bytes))" and nothing happens.
could u help pleas?
mariosraptor said:
just let see what happens and hopefully it will work again.
Click to expand...
Click to collapse
YES! I can finally turn on my phone again! Thanks so much, Mario! You are a genius and thank you for being so patient with me.
This is what happened:
I waited a while and the phone remained stuck on the boot animation so I took the battery out and completely restored all my files onto my partitioned SD card. I tried booting again with similar results so I tried running a nandroid restore to a previous Leedroid rom from Amon Ra Recovery and no longer received the cannot mount message so the restore was finally able to execute and after a lengthy boot process, I'm up and running again!
Thanks again so much! Once more, I could not have done it without your help. I'm going to see how stable it is, but it looks very good. By tomorrow if I'm still up, I will re-edit my first post with the exact steps I took to remedy my particular problem.
May I have your paypal email address?
persianblue said:
my phone is connected,drivers are installed and it is available in fastboot. But when I am typing "fastboot oem enableqxdm 0" it returnes: "... FAILED (status malformed (1 bytes))" and nothing happens.
could u help pleas?
Click to expand...
Click to collapse
Sorry to hear that, persianblue. In light of your problem, I will write the solution right now, although it sounds like a you're getting a different error message than I did after entering the fastboot command. Regardless, I will post the step-by-step instructions because there's no guarantee you did exactly what I did to recover my phone.
I'll have it up shortly.
SOLUTION
copied and pasted from the first post:
Below are the steps I took to resolve the issue.
First and foremost, I'd like to point out that prior to encountering this problem (or any problem for that matter), I did a very thorough job of backing up my entire phone multiple times through various methods, but it turns out I only really needed a single nandroid backup and mariosraptor's help. Still, better safe than sorry, I say, which is ironic considering what I did to my phone. Ah well.
Anyway, after running into my problem as described in my OP (original post), the following steps were needed to restore functionality to the phone:
1) With the phone turned off, I booted it into Fastboot by either a) holding down volume rocker+power on button, then choosing "fastboot" or b) holding back button+power on button, which takes you straight into "fastboot".
2) Once in fastboot, I connected my phone to my computer via USB cable.
3) I'm not sure if I needed it running or not, but I then ran Android SDK (a program I used back when I first got my phone and was tinkering with rooting and forcing apps to install onto the SD card before I learned about SD card partitioning and AP2SD/AP2SD+ supported roms and now DATA2SD/DATA2EXT). This program can be downloaded here and an example of how it's used is here, but I'm assuming (I know I shouldn't assume, but I can only describe things I've done or have already done) anyone who as gotten this far already has this program and used it before, even with limited knowledge.
4) I then went into my Start Menu in Windows and ran command prompt. The simplest way to run command prompt, I find, is to type "cmd" into the run dialog, then enter.
5) Once command prompt popped up, I typed in cd\ to change the directory to C:\ and then entered in cd android-sdk-windows/tools to open the directory to c:\android-sdk-windows\tools (I just noticed that you enter in /backsplashes, but end up with \forwardslashes, weird!).
6) I then typed in the fastboot commands as outlined by mariosraptor, that is, I entered "fastboot oem enableqxdm 0" pressed enter, let it finish, then typed in "fastboot reboot" and enter. Wait for phone to reboot, could take a while.
I'm hoping for most people those are all the steps needed in order to restore the phone, but in my case, after entering "fastboot oem enableqxdm 0", I received an error saying: "The program can't start because AdbWinApi.dll is missing from your computer. Try reinstalling the program to fix this problem." I was about to re-install when mariosraptor provided me with the AdbWinApi.dll file here. This is rapidshare link so it will expire. My suggestion is to search for it somewhere (google) if you run into the same missing file as me.
My problem actually didn't stop there either. I found my phone was stuck on the boot animation, although I supposed I could've left it even longer just to make sure it wasn't working, but I actually took my battery out to shut the phone down. I then proceeded to do a nandroid restore to a previous backup I had done before I created this whole problem. I did that by booting the phone into recovery by holding down volume rocker+power button, selecting "recovery", then selecting "nandroid backup/restore" and letting the process go through fully, which took quite some time.
Anyway, it's been a long 20 or so hours for me. I'm going to go rest now. Props again to mariosraptor!
Click to expand...
Click to collapse
Congrats mate. nice to hear that you are up and running again. this is what the community does. Help each other!!!
mariosraptor said:
Congrats mate. nice to hear that you are up and running again. this is what the community does. Help each other!!!
Click to expand...
Click to collapse
Absolutely! I'm discovering that firsthand thanks to you. Again, I appreciate your help. I had spent soooo much time trying to figure it out on my own and you were able to help me right away.
You sir, are a class act!
So it's been over a full day since my personal debacle and I'm happy to say my phone is still up and running . There has been, however, one abnormality. It's not a huge issue in the long run as I can still use the phone as I normally do, but I've noticed whenever I plug my micro-usb cable into my phone (with the other end either connected to a computer or a power outlet), there is a noticeable delay before it starts charge. Also, when connected to a computer, I'm no longer receiving the prompt for 1) charge only 2) mount sd card 3) sync 4) etc etc.
The icon in the top left that normally pops up doesn't show either when I have it connected to computer. Again, not a big deal in the long run, but obviously it can be a nuisance not being able to transfer files b/t my phone and computer via this method anymore. Not sure if anyone else has encountered this issue. I'm using the same cable, same computer. My next step is to try it on a diff computer, then eventually a different cable and hopefully that might be the issue.

need to flash but phone not detecting SD card

Hi,
I needed to flash a ROM onto my phone (prev using leedroid), however as I was going about this process (after I had backed everything up using clockworkmod recovery, and begun wiping), the phone stopped detecting my SD card
this card had been working fine for well over a year before. now error in recovery is something like E: unable to mount xxxx
it is detected using SD card reader on computer, and I have tried re-partitioning it to no avail
now the phone can boot into recovery and also the rom, but the SD card isnt detected in either, and neither now is the SIM card.
normally I would search extensively for a solution myself before posting, but I have done as much as I can, in my current situation I have no WIFI, only an internet dongle with very slow connection.
currently I assume that there is a problem with the radio but I have not had experience flashing this without using SD card in recovery
also, due to the risks involved with flashing radio, I would prefer to try to flash a new rom first, but again I have no experience flashing a new rom without SD card in recovery.
I have adb installed on my computer but not much experience using it.
Sorry for all this, but I am not the kind of guy who flashes roms regularly, the last time I did it was a while ago, and cant really remember how I rooted in the first place (I think I used unrevoked) - therefore uncertain of S-off status - although not sure what the significance of this is
please help i dont know what to do
thanks
This is what you need to do (instructions I wrote for myself in case I ever broke it again) :-
To gain access to SD card:
Put phone into fastboot mode (back button + power)
In CMD, go to dir C:\Android\android-sdk\Tools
Type: path C:\Android\android-sdk\Platform-tools)
Input "fastboot oem enableqxdm 0"
You'll need the Android SDK and once installed (along with the updated USB drivers that are available in the updates it finds) I discovered that 'Fastboot' was in a different directory to ADB so attempting to run Fastboot failed as it couldn't find ADB. My cure was to create a path to the ADB directory (as listed above). Be sure to change the path and directories to wherever you install them.
Alternatively (and far easier) search for 'Android Flasher' which is available on these forums. This has fastboot and adb installed in the same directory and is a much, much smaller download and run the above command from a CMD prompt from the directory that fastboot and adb reside in wherever you install Android Flasher to. I've never tried it this way but no reason why it shouldn't work and far easier than getting the whole SDK thing!
Yep confirmed, Android Flasher will do it. A quick search should find the program, it's a very small download compared to downloading the Android-SDK (and the Java runtime module it requires). Simply change directory in CMD to c:\your android flasher dir\data directory and run that command from there with the phone plugged in and running fastboot, fixed.
Here you go :- http://forum.xda-developers.com/showthread.php?t=794638&highlight=android+flasher
Ignore the S-Off bit, that's to do with the functions of the flasher itself, we're not actually using that.
thanks so much guys, that sorted the problem right out (used AndroidFlasher)
after reflashing the ROM, the problems with the SIM went away, so no need to flash new radio!
Guys same problem here
I backed up, I changed my sd card to an 32gb, restored but then i had the "Can’t mount /dev/block/mmcblk0p1" problem
I solved the problem with your solution (fastboot oem enableqxdm 0) then full wipe then reinstall rom
But now windows can't see my device. On my phone there is no popup menu to ask me what do i want to do when i connect the usb plug
Also, in recovery, i choose mount USB storage but windows dont see my ds card (4gb or 32gb cards)
What is the problem?
ps
when i connect to windows, device driver installation says: device driver software was not successfully installed.
It also listes "Qualcomm CDMA Technologies MSM No driver found" 3 times
Check if it's working with another sd card.
TouchPaled from Oxygen with Transparent XDA App
iceman1979 said:
Guys same problem here
I backed up, I changed my sd card to an 32gb, restored but then i had the "Can’t mount /dev/block/mmcblk0p1" problem
I solved the problem with your solution (fastboot oem enableqxdm 0) then full wipe then reinstall rom
But now windows can't see my device. On my phone there is no popup menu to ask me what do i want to do when i connect the usb plug
Also, in recovery, i choose mount USB storage but windows dont see my ds card (4gb or 32gb cards)
What is the problem?
ps
when i connect to windows, device driver installation says: device driver software was not successfully installed.
It also listes "Qualcomm CDMA Technologies MSM No driver found" 3 times
Click to expand...
Click to collapse
I'm afraid you have what is known as a USB brick, the fact that it asks for the Qualcomm drivers confirms it. Do a search on the forum, there is a fix for it.
Ah here it is :- http://forum.xda-developers.com/showthread.php?t=691639
Life-Saver.
Thanks
I've given you a 'thanks' also for replying to mine. It's a bad road to go down with the USB brick but it's something that everyone playing with rom's should experience as it educates you so much when things go wrong!
Glad you sorted it m8.
Parva4 said:
This is what you need to do (instructions I wrote for myself in case I ever broke it again) :-
To gain access to SD card:
Put phone into fastboot mode (back button + power)
In CMD, go to dir C:\Android\android-sdk\Tools
Type: path C:\Android\android-sdk\Platform-tools)
Input "fastboot oem enableqxdm 0"
You'll need the Android SDK and once installed (along with the updated USB drivers that are available in the updates it finds) I discovered that 'Fastboot' was in a different directory to ADB so attempting to run Fastboot failed as it couldn't find ADB. My cure was to create a path to the ADB directory (as listed above). Be sure to change the path and directories to wherever you install them.
Alternatively (and far easier) search for 'Android Flasher' which is available on these forums. This has fastboot and adb installed in the same directory and is a much, much smaller download and run the above command from a CMD prompt from the directory that fastboot and adb reside in wherever you install Android Flasher to. I've never tried it this way but no reason why it shouldn't work and far easier than getting the whole SDK thing!
Click to expand...
Click to collapse
you "saved my life" thank you so much
hi,just got a dhd s-on.but its not detecting the s card,tried the above method but i just get waiting for device ?... can get into fastboot etc,but cant get rid of the usb brick.looks like the dhd is stopping on stock sense 3.0
markb63 said:
hi,just got a dhd s-on.but its not detecting the s card,tried the above method but i just get waiting for device ?... can get into fastboot etc,but cant get rid of the usb brick.looks like the dhd is stopping on stock sense 3.0
Click to expand...
Click to collapse
You have a Desire HD. So please ask in the forum for Desire HD and not in the one for the Desire.
MatDrOiD said:
You have a Desire HD. So please ask in the forum for Desire HD and not in the one for the Desire.
Click to expand...
Click to collapse
yep,i have a desire bravo as well,was looking to sort the dhd out,could not find anything on dhd threads... thanks for your help ..

[Q] Houston We Have a Problem ---Almost a Brick

Hi,
Over the last year I have been rooting and flashing roms on both the HTC DZ and the Aria and have not had any real troubles. However...
Recently picked up a used Desire A8181 that was flashed and had CM7 with 2.3.7 G installed with CWM backups but "desired" to flash a newer ROM with either 2.1+3 Sense or Sense 3.5.
So over the course of the last week, been looking at alpharev, hboots and all of the stuff one might need to flash such a ROM. Well today ran into a problem. I cannot tell you exactly what I did but where I am is not a good place.
So, need some help...
1. I can boot into recovery and currently have cwm-4.0.1.4 loaded
2. Using Fastboot I can flash an .img file either a new bravo_alphaspl.img or a recovery-clockwork-2.5.0.7-bravo.img file using AndroidFlasher.exe or using fastboot.exe
3. I cannot get
a. revolutionary.exe to see my phone, it states WAITING FOR DEVICE
b. abd shell or device or any adb command to work
4. I cannot get a stock OTA RUU file to flash and when I do, I get the errors shown in the attached png files.
5. I cannot access my SDCARD and get this error can't mount /SDCARD and along with this the error /dev/block/mmcblk0
I have
- stock hboot
- PVT3 S-OFF
- hboot 6.93.1002
So looking for some tips or trick to get my ROM reloaded which I suspect is related to corrupt storage on the phone?
Anyway, thoughts welcomed.
Thanks,
malloy0
UPDATE...I also reviewed this guide http://forum.xda-developers.com/showthread.php?t=1275632 and many others, NONE addresses the issue of not being able to access the SDCARD. Also, I have 6 different SDCARDs and they all work fine in my DZ. I have also prepd and formated using Gparted and booted via Linux.
malloy0 said:
5. I cannot access my SDCARD and get this error can't mount /SDCARD and along with this the error /dev/block/mmcblk0
Click to expand...
Click to collapse
SD card brick , u can look at this thread
these commands through adb should solve it (u said adb is not finding ur device,make sure u have the drivers installed). i had this sd card issue at least 3-4 times and these 2 lines always saved me
fastboot oem rebootRUU
fastboot oem enableqxdm 0
rayiskon said:
SD card brick , u can look at this thread
these commands through adb should solve it (u said adb is not finding ur device,make sure u have the drivers installed). i had this sd card issue at least 3-4 times and these 2 lines always saved me
fastboot oem rebootRUU
fastboot oem enableqxdm 0
Click to expand...
Click to collapse
Thanks!! Will try in a few days. Busy for work traveling. Not much time to test.
Note on the adb drivers? I assume that given I connect my DZ and my WinPC and it works to access the DZ phone that these drivers mean they are installed? Using XP SP3. Also, I accessed my A8181 yesterday no trouble, so...assume the adb drivers are installed. I do note when the Desire is plugged in, sometimes get the request for the Qualcomm CDMA Technologies MSM (or something like this?) driver, but no luck finding this. So hit cancel and move on. Did not have this issue yesterday.
Ok...on the commands, will try more later.
RE: fastboot commands?
fastboot oem rebootRUU
fastboot oem enableqxdm 0
do I need to have these enableqxdm and rebootRUU files where I have the fastboot.exe file?
Spent way to much time searching and trying to fix myself, time to get some help.
Thanks again.
These are not files, they are just 2 commands to fix the usb brick. So you only need fastboot.exe.
To get the drivers you have to download the Android SDK, but I think that these drivers will work as well.
rayiskon said:
SD card brick , u can look at this thread
these commands through adb should solve it (u said adb is not finding ur device,make sure u have the drivers installed). i had this sd card issue at least 3-4 times and these 2 lines always saved me
fastboot oem rebootRUU
fastboot oem enableqxdm 0
Click to expand...
Click to collapse
WOW! Amazing. I messed with this for hours and hours and did search after search, but did not locate the suggested fix above, but flashed and WAA-LAA!!
It worked like a charm.
fastboot oem rebootRUU
fastboot oem enableqxdm 0
Thank you!

Device not recognized

I have a pretty big problem and need some guided help. My stock samsung usb charger sometimes charges the phone and sometimes does not. Tried multiple different chords and got the same results, sometimes works sometimes does not. So now I am assuming this is an internal hardware problem soo I decided I should flash stock images, unroot and relock the bootloader and here comes the worst problem.... My device is NOT recognized when I connect it to my PC... therefor I can't access adb connection to flash stock images so I can return it to VZW....
Not sure what to do next.. any suggestions would be great...
It sounds like you just don't have the drivers installed. Just install the Samsung drivers here.
mwalt2 said:
It sounds like you just don't have the drivers installed. Just install the Samsung drivers here.
Click to expand...
Click to collapse
I tried that. uninstalled the old ones (that worked for 3 months) reinstalled them again and still no luck..
Do you have any other Android processes running on your cpu? Droid Explorer or alike? Droid Ex **** blocks adb; I had a frustrating few minutes once when adb wouldn't connect to my device until I realized DE was running in the background.
Long shot, but just a thought.
This is actually a common hardware error. See http://code.google.com/p/android/is...ary Stars&groupby=&sort=&id=23789#makechanges and http://forum.xda-developers.com/showthread.php?t=1427539
Basicly you need to buy a new USB charging board.
chuckdz3 said:
and here comes the worst problem.... My device is NOT recognized when I connect it to my PC... therefor I can't access adb connection to flash
Click to expand...
Click to collapse
You mean fastboot
Melhouse said:
This is actually a common hardware error. See http://code.google.com/p/android/is...ary Stars&groupby=&sort=&id=23789#makechanges and http://forum.xda-developers.com/showthread.php?t=1427539
Basicly you need to buy a new USB charging board.
Click to expand...
Click to collapse
Yeah I believe that is what I am going to do, I just have to find the sch-i515 CDMA version because I am finding a lot of GSM versions out there right now.
bk201doesntexist said:
You mean fastboot
Click to expand...
Click to collapse
Sure. My adb command prompt does not recognize my device therefor I cannot execute any commands ei fastboot.
chuckdz3 said:
Sure. My adb command prompt does not recognize my device therefor I cannot execute any commands ei fastboot.
Click to expand...
Click to collapse
fastboot doesnt have anything to do with adb; boot your device into bootloader
'fastboot devices'
do you see your device?
bk201doesntexist said:
fastboot doesnt have anything to do with adb; boot your device into bootloader
'fastboot devices'
do you see your device?
Click to expand...
Click to collapse
I am in the bootloader and don't see 'fastboot devices' or do I see my device. I see the product name, variant, bootloader version, baseband version, etc. Would that be considered 'my device' being recognized and I could actually flash the stock images?
chuckdz3 said:
I am in the bootloader and don't see 'fastboot devices' or do I see my device. I see the product name, variant, bootloader version, baseband version, etc. Would that be considered 'my device' being recognized and I could actually flash the stock images?
Click to expand...
Click to collapse
fastboot is like adb. You need to run it from a command line. You should have had to use it when you installed a custom recovery ('fastboot flash recovery customrecovery.img') or unlocked your phone (ie 'fastboot oem unlock'). fastboot is part of the android sdk (think it's in tools folder, but I moved mine so am not sure).
mwalt2 said:
fastboot is like adb. You need to run it from a command line. You should have had to use it when you installed a custom recovery ('fastboot flash recovery customrecovery.img') or unlocked your phone (ie 'fastboot oem unlock'). fastboot is part of the android sdk (think it's in tools folder, but I moved mine so am not sure).
Click to expand...
Click to collapse
That's what my understanding of what it was too. I'm in the bootloader running a command prompt through windows and for the first time I think it recognized my devices. I ran 'fastboot devices' and a bunch of numbers on one line came up followed by fastboot. So I think my device is recognized and I can flash stock images?
chuckdz3 said:
That's what my understanding of what it was too. I'm in the bootloader running a command prompt through windows and for the first time I think it recognized my devices. I ran 'fastboot devices' and a bunch of numbers on one line came up followed by fastboot. So I think my device is recognized and I can flash stock images?
Click to expand...
Click to collapse
yes, you can download the images for your device from google and flash them to your phone using fastboot if you want. I'm pretty sure that would put you back at stock with an unlocked bootloader.
@op, next time read how to flash/get back to stock before flashing anything. there must be like a dozen of topics in xda about this ****.
bk201doesntexist said:
@op, next time read how to flash/get back to stock before flashing anything. there must be like a dozen of topics in xda about this ****.
Click to expand...
Click to collapse
I know how to. It was just your demeanor and wording/phrasing that had me confused.
I have the same problem, fastboot was working this morning, now after flashing Revolution HD, typing "fastboot devices" in CMD doesnt return anything anything, neither does adb push command which replies failed to copy .... As if the phone doesnt exist or its not attached. Does the phone need to be in clockwork mod? or just boot the phone normally?
Edit: This should do the trick, open CMD in Windows, navigate to your c:\android where you have fastboot and adb stored and type:
:cd %:h
adb kill-server
adb reboot bootloader
brooklynite said:
I have the same problem, fastboot was working this morning, now after flashing Revolution HD, typing "fastboot devices" in CMD doesnt return anything anything, neither does adb push command which replies failed to copy .... As if the phone doesnt exist or its not attached. Does the phone need to be in clockwork mod? or just boot the phone normally?
Edit: This should do the trick, open CMD in Windows, navigate to your c:\android where you have fastboot and adb stored and type:
:cd %:h
adb kill-server
adb reboot bootloader
Click to expand...
Click to collapse
*facepalm*
Make sure USB debugging is turned on.
Sent from my Galaxy Nexus
mentose457 said:
Make sure USB debugging is turned on.
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
*facepalm*
Melhouse said:
*facepalm*
Click to expand...
Click to collapse
Did I say something stupid?
mentose457 said:
Did I say something stupid?
Click to expand...
Click to collapse
debugging has nothing to do with it.
Windows XP absolutely HATES the samsung galaxy nexus.
The don't play along and it's almost impossible to get the drivers (especially MTP) installed correct.
Fortunately I have a W7 BEAST rig at home.. But the work XP pc can't handle the Nexus

[Q] Fastboot cannot find device (Ubuntu/Win7)

Ok, I *have* searched the forums and googled this, but none of the standard solutions seem to work.
I have the Verizon HTC One and successfully ran the rumrunner S-OFF (root, unlocked, etc). Now I want to flash a recovery using fastboot, but no matter what I do, I cannot get "fastboot devices" to show anything (or I get <waiting for device> if I try anything else with fastboot). ADB works fine.
On Ubuntu 11.10:
I downloaded the back-ported android-tools (apt-get install android-tools-fastboot/adb from the ppa:nilarimogard/webupd8 repository).
I tried fastboot as root, and I also tried with a udev rule (SUBSYSTEMS=="usb", ATTRS{idVendor}=="0bb4", MODE="0666").
adb works fine (I used it to reboot in fastboot-usb mode)
I tried different USB ports.
On Windows 7:
I tried both fastboot from the Android SDK and from the "Minimal Tools".
ADB works fine.
I un-installed and re-installed drivers as I plugged in and unplugged my phone into the USB ports.
Note that Windows 7 does complain about the drivers and says that the device is unplugged when it isn't. It seems to timeout when trying to install drivers from the internet
I tried installing and uninstalling HTC Sync, PDANet.
I would prefer if there is a way to make it work in Ubuntu so that I can eliminate the Windows drivers from the equation. Anything obvious that I missed? Does the version of fastboot matter?
Thanks in advance for any suggestions.
neutrino37 said:
Ok, I *have* searched the forums and googled this, but none of the standard solutions seem to work.
I have the Verizon HTC One and successfully ran the rumrunner S-OFF (root, unlocked, etc). Now I want to flash a recovery using fastboot, but no matter what I do, I cannot get "fastboot devices" to show anything (or I get <waiting for device> if I try anything else with fastboot). ADB works fine.
On Ubuntu 11.10:
I downloaded the back-ported android-tools (apt-get install android-tools-fastboot/adb from the ppa:nilarimogard/webupd8 repository).
I tried fastboot as root, and I also tried with a udev rule (SUBSYSTEMS=="usb", ATTRS{idVendor}=="0bb4", MODE="0666").
adb works fine (I used it to reboot in fastboot-usb mode)
I tried different USB ports.
On Windows 7:
I tried both fastboot from the Android SDK and from the "Minimal Tools".
ADB works fine.
I un-installed and re-installed drivers as I plugged in and unplugged my phone into the USB ports.
Note that Windows 7 does complain about the drivers and says that the device is unplugged when it isn't. It seems to timeout when trying to install drivers from the internet
I tried installing and uninstalling HTC Sync, PDANet.
I would prefer if there is a way to make it work in Ubuntu so that I can eliminate the Windows drivers from the equation. Anything obvious that I missed? Does the version of fastboot matter?
Thanks in advance for any suggestions.
Click to expand...
Click to collapse
You can run a fastboot command from terminal emulator. If you can't find the commands, I will send them when I get to a computer tomorrow.
Sent from my One.
Do you have Fastboot turned off in system settings?
Unless I'm mistaken, you need to be sure that's switched off to utilize fastboot mode.
If it's already switched off and you are still having the issue, then ignore this post.
santod040 said:
Do you have Fastboot turned off in system settings?
Unless I'm mistaken, you need to be sure that's switched off to utilize fastboot mode.
If it's already switched off and you are still having the issue, then ignore this post.
Click to expand...
Click to collapse
I have fastboot checked in settings and fastboot commands work... When I'm in fastboot mode.
OP, I have made the simple mistake of not putting it in fastboot mode before. Were you booted into fastboot mode? I.E. reboot into bootloader, with fastboot selected hit the power button and ensure that it says deadbolt at the top? Something really simple that had tripped me up before!
Sent from my HTC6500LVW using XDA Premium 4 mobile app
This is worth a shot, as I've read in previous post. Only plug your HTC One into a usb 2.0 instead of 3.0. What does this mean? If you look inside the usb on your computer and the color you see is blue? Don't use that one. For whatever reason, when using the commands, usb 3.0 doesn't work with the HTC One. If you only have the 3.0 ports... I have nothing.
BygSii said:
This is worth a shot, as I've read in previous post. Only plug your HTC One into a usb 2.0 instead of 3.0. What does this mean? If you look inside the usb on your computer and the color you see is blue? Don't use that one. For whatever reason, when using the commands, usb 3.0 doesn't work with the HTC One. If you only have the 3.0 ports... I have nothing.
Click to expand...
Click to collapse
ADB works fine over USB 3.0 for any Android device if you have the proper drivers installed. If you have a mixture of 2.0 and 3.0 ports, as I do, use the 2.0, as it is more reliable, though slower. I'm using ADB on my device via USB 3.0 as I type this, using Windows 7 x64.
If your motherboard has an Intel chipset, you can try this method to get Fastboot working over USB 3.0, just disregard the download links about making it work on Windows 8, as the drivers were designed for Windows 7. My motherboard has an Asmedia USB 3.0 controller, and I am unable to use the Intel drivers, and thus unable to use Fastboot over USB 3.0, which isn't really a problem for me, as I also have the USB 2.0 ports.
brymaster5000 said:
You can run a fastboot command from terminal emulator. If you can't find the commands, I will send them when I get to a computer tomorrow.
Sent from my One.
Click to expand...
Click to collapse
Oh, you mean directly on the phone? Presumably one could do it from "adb shell" as well? I would be interested to know what the commands are, since typing fastboot in the terminal emulator is not recognized.
[edit]
I found this in the forums:
Code:
su
flash_image recovery path_to_recovery_image.img
I assume that is what you meant.
kdj67f said:
I have fastboot checked in settings and fastboot commands work... When I'm in fastboot mode.
OP, I have made the simple mistake of not putting it in fastboot mode before. Were you booted into fastboot mode? I.E. reboot into bootloader, with fastboot selected hit the power button and ensure that it says deadbolt at the top? Something really simple that had tripped me up before!
Sent from my HTC6500LVW using XDA Premium 4 mobile app
Click to expand...
Click to collapse
So just to be patently clear. To boot into fastboot, I reboot into the bootloader with USB attached, select "fastboot", then it says "fastboot USB" and I select "Reboot", correct? I have never noticed the word "deadbolt". Is there a way to check on the phone that I've booted into fastboot?
I have been using USB 2 ports (tried different ones).
I have fast boot unchecked in my settings.
neutrino37 said:
So just to be patently clear. To boot into fastboot, I reboot into the bootloader with USB attached, select "fastboot", then it says "fastboot USB" and I select "Reboot", correct? I have never noticed the word "deadbolt". Is there a way to check on the phone that I've booted into fastboot?
I have been using USB 2 ports (tried different ones).
I have fast boot unchecked in my settings.
Click to expand...
Click to collapse
Don't click reboot once your phone says "Fastboot USB". That's where you're going wrong.
You say that ADB works on occasion. Trying downloading the newest drivers from this thread. Plug your phone in and type "adb devices". If it displays your phone's serial number and says "device" next to it, you're doing fine. Then type "adb reboot bootloader". It will bring you to where you are able to type fastboot commands. Type "fastboot devices". If it shows your device's serial number and says "fastboot" next to it, then your Fastboot commands will work properly.
neutrino37 said:
Oh, you mean directly on the phone? Presumably one could do it from "adb shell" as well? I would be interested to know what the commands are, since typing fastboot in the terminal emulator is not recognized.
[edit]
I found this in the forums:
Code:
su
flash_image recovery path_to_recovery_image.img
I assume that is what you meant.
Click to expand...
Click to collapse
Open a terminal emulator on your phone then get root access:
su
After that, cd to the location of the .img file: (i.e. if it was on the root of the sd card then...)
cd /sdcard/
Finally, flash the image to the recovery partition:
dd if=recovery.img of=/dev/block/mmcblk0p21 (not sure if this location will be different on this phone..someone else may want to chime in)
Then exit the terminal emulator and reboot.
IceDragon59 said:
Don't click reboot once your phone says "Fastboot USB". That's where you're going wrong.
You say that ADB works on occasion. Trying downloading the newest drivers from this thread. Plug your phone in and type "adb devices". If it displays your phone's serial number and says "device" next to it, you're doing fine. Then type "adb reboot bootloader". It will bring you to where you are able to type fastboot commands. Type "fastboot devices". If it shows your device's serial number and says "fastboot" next to it, then your Fastboot commands will work properly.
Click to expand...
Click to collapse
Thanks, not clicking the reboot made it work with fastboot (even in Win7!). I was confused by the statements about rebooting "into fastboot" and assuming that once it displayed "fastboot USB" I should reboot. Took me 2 seconds to install TWRP once this PEBKAC was resolved .
I would've tried the dd option from the terminal, but I'm glad I didn't have to (have used that wrong once on a Linux system and it was not pleasant!).
Glad you figured it out, even with my typo!
Sent from my HTC6500LVW using XDA Premium 4 mobile app
Commands
brymaster5000 said:
You can run a fastboot command from terminal emulator. If you can't find the commands, I will send them when I get to a computer tomorrow.
Sent from my One.
Click to expand...
Click to collapse
Hi, I have been trying to debrick my tp and I've posted in forums asking basically this question.. seems it goes fine till failed to install/find Fastboot.. would you send me the command? thanks..

Categories

Resources