Hi,
My phone is soft bricked, stuck in charging icon, but it responds to adb and fastboot. I tried unlocking and flash from fastboot - no luck.
USB debugging is not enabled in the device, maybe that is preventing it from flashing.
Any help, please.
Thanks,
Related
When I connect my HTC Desire through USB cable to my laptop, my laptop wait a while then pop a windows which says USB Device Not Recognised. My device just got the orange light lit up but there is no response other than that i.e. no menu pops up to choose "charge only, disk drive" whatsoever.
It worked just two days ago before I reflash a new ROM (RCMixHD 3.6.1).
During the flash, the SD card was not recognised too so I tried to get it work by using "fastboot oem enableqxdm 0" as instructed by one post named "USB brick/rickrolled/b0rked -> FIXED!" on MoDaCo.
But I did not flash the update.zip as required cos my problem was fixed before this step.
Can anyone help me fix this problem? Waiting online
USB debugging still enabled?
What result from either adb or fastboot?
Code:
fastboot devices
adb devices
FASTBOOT shows "FASTBOOT USB", Bootloader also gives me "HBOOT USB PLUG", I think the USB cable is fine.
stringer7 said:
USB debugging still enabled?
What result from either adb or fastboot?
Code:
fastboot devices
adb devices
Click to expand...
Click to collapse
I tried the two commands in cmd, I copy down what it gives me
E:\SDK\Tools> adb devices
List of devices attached
E:\SDK\Tools> fastboot devices
HT05HPL12963 fastboot
E:\SDK\Tools>
Ok so the fastboot result means you can connect to PC.
What happens if you connect your device whilst it's booted up with USB debugging enabled? Enable this prior to connecting in settings>applications>development.
Hi thanks for the help, I managed to unbrick the USB brick. But now even though I'm able to connect to my laptop, the adb devices still doesn't give me any device. In device manager, I got an "ADB" with yellow exclamation mark under “Other Devices”, just cannot get the right driver for it. Could it be due to the USB brick?
I wanted to update my ROM, so I downloaded the newest version of Hason2000's Toolkit and was ready to flash the boot.img.
I plug my phone in; both my phone and computer recognizes the connection. I notice that USB Debugging is required so I enable it.
Problem? The computer stop recognizing my phone, the phone sees the connection just fine.
I tried updating the drivers (several times), I tried installing the driver on another computer, no go. Turning off the USB Debugging fixes the problem, but then I can't flash the kernel.
My ROM is IceColdJelly 2.5.1 (old I know), any ideas? :crying:
Metaception said:
I wanted to update my ROM, so I downloaded the newest version of Hason2000's Toolkit and was ready to flash the boot.img.
I plug my phone in; both my phone and computer recognizes the connection. I notice that USB Debugging is required so I enable it.
Problem? The computer stop recognizing my phone, the phone sees the connection just fine.
I tried updating the drivers (several times), I tried installing the driver on another computer, no go. Turning off the USB Debugging fixes the problem, but then I can't flash the kernel.
My ROM is IceColdJelly 2.5.1 (old I know), any ideas? :crying:
Click to expand...
Click to collapse
You should be in fastboot to flash a boot.img.
USB debugging has no effect on fastboot.
Tigerlight said:
You should be in fastboot to flash a boot.img.
USB debugging has no effect on fastboot.
Click to expand...
Click to collapse
Hason2000's All-In-One Toolkit needs USB Debugging to work, it appears to just automate the fastboot commands so I assumed doing it manually would be the same.
I guess I will try it after I DL the files needed, but I still don't understand why USB Debugging stops my computer from seeing the phone.
Metaception said:
Hason2000's All-In-One Toolkit needs USB Debugging to work, it appears to just automate the fastboot commands so I assumed doing it manually would be the same.
I guess I will try it after I DL the files needed, but I still don't understand why USB Debugging stops my computer from seeing the phone.
Click to expand...
Click to collapse
Yes the toolkit uses ADB to automate the reboot into fastboot mode.
And my understanding is that enabling USB Debugging changes the drivers required so that you can access the ADB interface.
I rooted and installed my first ROM using the toolkit, idk y it's different now.
I will try to flash via fastboot and then ask in the toolkit thread as well since these driver are the ones that the came with the toolkit.
EDIT: Whhhhooaa, did it! Cheers for fastboot
Metaception said:
Hason2000's All-In-One Toolkit needs USB Debugging to work, it appears to just automate the fastboot commands so I assumed doing it manually would be the same.
I guess I will try it after I DL the files needed, but I still don't understand why USB Debugging stops my computer from seeing the phone.
Click to expand...
Click to collapse
If you want adb usb drivers, i prefer to install moborobo from Moborobo.com.
Start application,
Plug your device with usb debugging on.
and it will do the work.
Whenever i boot to the bootloader, then plug phone into computer, it doesn't change to fastboot usb mode
Are you using the usb cable that came with the phone?
If you plug in the phone first, can you adb reboot to bootloader?
Is usb debugging enabled in developer options?
If USB debugging is on in your settings than wile in hboot just volume up or down to reboot fastboot.
It's done that for me and that's what I did
Usb debugging has no effect in the boot loader.
Can't you just select fastboot from the boot loader menu?
ashyx said:
Usb debugging has no effect in the boot loader.
Click to expand...
Click to collapse
I was actually just reading on another post, USB Debugging is needed for adb, but not fastboot.
Never really thought about it that much, I had assumed like jball that you need USB Debugging for both adb and fastboot.
redpoint73 said:
I was actually just reading on another post, USB Debugging is needed for adb, but not fastboot.
Never really thought about it that much, I had assumed like jball that you need USB Debugging for both adb and fastboot.
Click to expand...
Click to collapse
Usb debugging has no effect outside of the os. Adb can be used in recovery regardless of usb debugging.
ashyx said:
Usb debugging has no effect outside of the os. Adb can be used in recovery regardless of usb debugging.
Click to expand...
Click to collapse
Well look at that. For some reason, I thought you can use adb in bootloader, but I just tried it and it didn't work. And like you said, only in OS and recovery; and whether USB debugging is selected or not does not affect adb use in recovery. Fastboot likewise doesn't need USB debugging; and phone obviously needs to be in fastboot mode.
We are all learning on XDA
Hello, I need help with my watch. USB debugging is not enabled and I cannot get pass bootloader because of it and PC does not recognize the device. I tried installing PDAdriver and sdk tools but no luck with them. Is there anyway to fix this bootloop (stuck at spinning dots)?
Edit - While in bootloader, PC recognize the watch as unknown device and i cannot update the driver.
Editx2 - Could it be because the usb charger is not oem?
I'm trying to unlock my Swift's bootloader. I've enabled OEM unlocking and USB debugging in settings, and I've also installed adb and fastboot to my computer. However, when I plug my phone into it, all it does is charge. Using 'adb devices' doesn't bring up my phone, and no popup window comes up on my phone either. I can't even find it on Device Manager. What should I do to get it working?
Edit: Turns out the USB cable I was using only supported charging. I plugged in the standard Wileyfox cable and everything's working again. Problem solved!