Brief description of the problem: Somehow got a USB-brick (phone as a USB-device not recognized in the PC, and do not switch into HBOOT USB mode or FASTBOOT USB whe connected to PC)
Device / model: HTC Desire HD
Operating System and Firmware: Android ICS Sabsa Prime 7 (custom roooted, unlocked through htcdev.com)
What was done: Tried to go the way of brick recovery through 'fastboot oem enableqxdm 0'
Ran into a problem: because of PC does not see the phone, respectively, it can not install the HBOOT-driver (Android Bootloader Interface Driver) on Windows 7 x64. Well, as a result, without the driver I failed to restore the usb-brick.
Please help to recover from a brick! Maybe there is another way recovery?
+1
Sent from my borthwickator running hummleflug.
Did you find the solution?
xumuk37 said:
Did you find the solution?
Click to expand...
Click to collapse
Sorry, still not
Related
Hi all,
Looking for some help with my Desire Z, it suddenly stopped reading any SD cards. I've tried with multiple cards, verified them to be working on other phones.
It's running:
Latest CWM
ROM Manager v4.4.0.7
CoreDroid ROM
Here's the info from the bootloader screen:
Code:
VISION PVT ENG S-OFF
HBOOT-0.84.2000 (PC1011000)
MICROP-0425
RADIO-26.02.01.15_M2
eMMC-boot
Sep 8 2010,15:56:38
I've tried using the:
Code:
fastboot oem enableqxdm 0
and then
fastboot oem eraseconfig
method to see if that would fix the problem, but fastboot just hangs saying:
< waiting for device >
Click to expand...
Click to collapse
I also tried going back to stock using the RUU installer but it reboots the phone to the screen with the silver & black HTC logo, hangs for a bit on the 'Waiting for bootloader.....' message then gives this error:
ERROR [171]: USB CONNECTION ERROR
The ROM Update Utility cannot connect to your Android phone. Please check that the USB cable is connected properly between the PC and your Android phone.
Click to expand...
Click to collapse
As well as this my phone does not show up in My Computer & I am unable to set USB mode to Disk Drive as the phone doesn't think it has a card.
Any ideas on what I can do before I bin it and buy a new phone?
Thanks.
Do you already check the driver for your device? Maybe need to reinstall the driver. Try to reinstall the htc sync.
Sent from my HTC Vision using XDA App
Don't think it's a driver issue as nothing changed on the PC and my GF's Sensation is working fine on it.
Amy result if u perform adb devices? If no devices detected, check usb debugging & just try to reinstall the driver.
Sent from my HTC Vision using XDA App
All ADB commands are working fine.
I am trying to get ADB to work so I can do the unlock bootloader. ADB recognizes my phone while booted up with usb debugging enabled, but when I reboot to fastboot, it does not recognize it.
I've tried different drivers, uninstalling and reinstalling.... no luck.....
Is there anyone that is knowledgeable in this area to assist me? Is there any kind of IRC channel available to get real-time answers?
Please help,
Thanks,
Bob
i am in the same boat. Using windows 7(64 bit). Cannot get the phone recognized in boot loader mode.
diablonyc2 said:
i am in the same boat. Using windows 7(64 bit). Cannot get the phone recognized in boot loader mode.
Click to expand...
Click to collapse
Yeah, im on 7 64 bit also..... i've tried disabling digital driver thing at bootup...
device manager see its just fine.... I can access it with adb while the phone is booted up.... as soon as I reboot to fastboot screen the phone cannot be seen by adb devices..... still shows up just fine with no ! in device manager....
... is there anyway to push a stock image and load a factory stock image from the stock recovery? says it needs to be in /cache folder.... i tried pushing a stock image there but it tells me access is denied.... i tried enabling root.... says root not available on production builds..... im lost....
I just tried it on my xp machine and it worked just fine..... weird.. something with 7 64 bit? i tried pda net drivers, samsung, samsung naked 1.7.... all said they were working fine....
adb is for android or recovery
fastboot is for bootloader
adb won't recognise the device when it's in fastboot mode.
Try:
Code:
fastboot devices
And you don't need adb to unlock the bootloader, the command is:
Code:
fastboot oem unlock
So not entirely sure why you're chasing adb...
I am in the same boat, what happens for me is that fastboot doesnt even recognize the device. So all in all I can't oem unlock my device.
Using win7 64bit
j1mmyg88 said:
I am in the same boat, what happens for me is that fastboot doesnt even recognize the device. So all in all I can't oem unlock my device.
Using win7 64bit
Click to expand...
Click to collapse
The usual recommendation (and what worked for me) is to install PDANet first, just for the drivers. Then fastboot will see your device. You can remove PDANet afterwards and the drivers will remain.
copkay said:
The usual recommendation (and what worked for me) is to install PDANet first, just for the drivers. Then fastboot will see your device. You can remove PDANet afterwards and the drivers will remain.
Click to expand...
Click to collapse
fyi - this is what I did, with 64 bit windows 7 - the driver install didn't complete 'til I actually connected the GN in fastboot mode, then win7 installed the driver and I was able to run fastboot successfully.
I'm on:
AlphaRev Oxygen r2
Bravo PVT1 SHIP S-Off
HBOOT-6.93.1002
RADIO-5.09.05.30_2
Clockworkmod 2.5.0.7
After installing Oxygen r2 HBOOT and Oxygen 2.3.2 I get this message "USB Device not recognized" whenever I'm trying to connect my phone to the pc using a suitable USB cable. Tried two cables (they both work fine on a different HTC Desire): no luck.
Tried to connect using adb fastboot commands. No luck, when the phone is in fastboot mode I also get the message "USB Device not recognized". The other HTC Desire connects without any trouble.
Most of the unbrick tutorials use fastboot commands. Which unfortunately I can't use.
I was thinking about using RMD recovery. But I can't flash this recovery, because I can't connect via USB using fastboot mode. Is there a way to safely install the RMD recovery without the use of adb/fastboot.
Any thoughts how i can solve this usb brick without the use of fastboot.
4ext recovery has a usb unbrick function included in it, search 4ext on the playstore. I dont know if the unbrick works cause ive never used it but its worth a try.
Try flashing recovery via PB99IMG way?
lin.dewayne said:
Try flashing recovery via PB99IMG way?
Click to expand...
Click to collapse
Both will do the trick. You just need the android.txt found in the rom.zip from your RUU.
Roscobigfoot said:
4ext recovery has a usb unbrick function included in it, search 4ext on the playstore. I dont know if the unbrick works cause ive never used it but its worth a try.
Click to expand...
Click to collapse
This is the easier option though, install the app from market, or find it on the dev page.
Roscobigfoot said:
4ext recovery has a usb unbrick function included in it, search 4ext on the playstore. I dont know if the unbrick works cause ive never used it but its worth a try.
Click to expand...
Click to collapse
Tried the 4ext option. Did a usb brick fix. Unfortunately this didn't help. How can I tell the difference between a usb brick and a broken micro-usb connector? Because I may have have one or the other.
Read in another thread that if you can enable bluetooth, then you don't have a usb brick. Is this right? Because my bluetooth is working as far as I can tell. But my problem description (see above) is still "there".
omron2010 said:
Tried the 4ext option. Did a usb brick fix. Unfortunately this didn't help. How can I tell the difference between a usb brick and a broken micro-usb connector? Because I may have have one or the other.
Read in another thread that if you can enable bluetooth, then you don't have a usb brick. Is this right? Because my bluetooth is working as far as I can tell. But my problem description (see above) is still "there".
Click to expand...
Click to collapse
Any chance there is a pc system/driver problem? or phone hardware problem?
lin.dewayne said:
Any chance there is a pc system/driver problem? or phone hardware problem?
Click to expand...
Click to collapse
Well. I have here another HTC Desire (with Oxygen Rom en Oxygen r2 HBOOT) and it connects perfectly to this PC (tried laptop as well).
It could be a hardware problem. But as I wrote earlier, maybe it's a problem causes by flashing new HBOOT and/or rom. But... how can I tell if its one or the other.
Just to be clear my symptoms are:
- when connecting my phone (regardless if in normal mode, fastboot mode or recovery usb storage mode) Windows 7 gives me the message "USB Device not recognized").
- I can enable bluetooth
- I can't use fastboot commands (because of USB connection problem in fastboot mode as well)
- I can use my SD card in normal mode (using android)
omron2010 said:
Well. I have here another HTC Desire (with Oxygen Rom en Oxygen r2 HBOOT) and it connects perfectly to this PC (tried laptop as well).
It could be a hardware problem. But as I wrote earlier, maybe it's a problem causes by flashing new HBOOT and/or rom. But... how can I tell if its one or the other.
Just to be clear my symptoms are:
- when connecting my phone (regardless if in normal mode, fastboot mode or recovery usb storage mode) Windows 7 gives me the message "USB Device not recognized").
- I can enable bluetooth
- I can't use fastboot commands (because of USB connection problem in fastboot mode as well)
- I can use my SD card in normal mode (using android)
Click to expand...
Click to collapse
Can confirm that there is not a misc overwrite issue.
Sounds like a hardware problem.
I have a prob with my Desire like this, in fastboot windows does not find the device at all.... however when i plug in my one x every thing is ok
I made a bizare mistake trying to flash mod for menu button on odexed htc stock rom. Now I am stucked on HTC ONE logo.Device is unlocked by htcdev.com. I can flash/access custom recovery through fastboot but I have nothing on sdcard of the device. Also I am having problems with adb recognizing the device. I have tried all the currently available recovery images and in only one (Doom version) there is an option to mount usb mass storage but the computer (Win7 x86, htc drivers) doesn`t recognize it. Tried to flash Stock RUU, got Unknown Error 155.
Does anyone have an idea how to make it work or at least with adb conectivity problem, mount of usb storage... anything that might help?
Thank you all in advance
UPDATEroblem solved, the trick was to relock the bootloader in order to install stock RUU. BTW, I am trying to resolve this for 2 days, and i have found the solution on this same forum (that I searched at least 1.000.000 times) only couple of minutes after posting the problem.
I need help getting out of this never ending misery. I'm stuck with my unlocked Desire HD, no ROM, and no idea how to get one working. I can't even get back to stock.
I've been looking for solutions for a week now, but it seems the combination of S-ON, no USB debugging and an unlocked bootloader makes most of them undoable.
I am able to get into boot loader, and the currently installed 4eXT recovery.
See attached file for bootloader screen.
Can anyone help me get my phone to work again? Either by a custom ROM or HTC stock; whatever.
Thanks.
What is the problem? What happens when you install a ROM? If you get stuck on the splash screen read my signature.
bananagranola said:
What is the problem? What happens when you install a ROM? If you get stuck on the splash screen read my signature.
Click to expand...
Click to collapse
It gets stuck on the HTC loading screen or on the black screen directly after depending on what I install. Don't I need USB debugging to use fastboot? I'm only getting < waiting for device > when flashing via fastboot.
My device is not listed when using adb devices.
SageNTitled said:
It gets stuck on the HTC loading screen or on the black screen directly after depending on what I install. Don't I need USB debugging to use fastboot? I'm only getting < waiting for device > when flashing via fastboot.
My device is not listed when using adb devices.
Click to expand...
Click to collapse
No. ADB is not fastboot. Access fastboot from the hboot menu. Details in the link in my signature.
bananagranola said:
No. ADB is not fastboot. Access fastboot from the hboot menu. Details in the link in my signature.
Click to expand...
Click to collapse
Yes, I did read your thread. But it doesn't work since it's not getting a connection to the device.
See attached image.
So you're booting into hboot, navigating to fastboot with your volume keys, and selecting it with the power key? If so, and fastboot still isn't getting a connection, I have no idea. Maybe check your cable or your USB port connectivity.
bananagranola said:
So you're booting into hboot, navigating to fastboot with your volume keys, and selecting it with the power key? If so, and fastboot still isn't getting a connection, I have no idea. Maybe check your cable or your USB port connectivity.
Click to expand...
Click to collapse
Yes. It does say FASTBOOT USB and I can see the device in the Device Manager. I also have the Android SDK Tools as well as the Google USB Driver installed.
I always thought you needed USB debugging on on the phone to get access to the phone's system folders.
SageNTitled said:
Yes. It does say FASTBOOT USB and I can see the device in the Device Manager. I also have the Android SDK Tools as well as the Google USB Driver installed.
I always thought you needed USB debugging on on the phone to get access to the phone's system folders.
Click to expand...
Click to collapse
No, USB debugging (aka ADB) is separate from fastboot. ADB kicks in when you boot the ROM. Fastboot is from the bootloader. Fastboot doesn't access the system's individual folders. It's used to flash entire images.
Not to worry, for I have solved the problem. I was apparently missing a driver that didn't get installed since I was missing USB debugging mode when installing adb and fastboot on my PC.
Going into Device Manager and manually looking up the HTC driver solved it.
Thanks for your time.
Out of interest, did your PC have VMWare Workstation installed? Because on Windows 7 and 8 people are having issues with Android drivers with it installed
Sent from my Desire HD using Tapatalk 2
humzaahmed155 said:
Out of interest, did your PC have VMWare Workstation installed? Because on Windows 7 and 8 people are having issues with Android drivers with it installed
Click to expand...
Click to collapse
No, I did not have that installed.