Database Develop

[Q] My phone halfway bricked. Cannot boot and recovery.

I have tried to flash a rom (Android Revolution HD 53.0) for my One. And after I finished flashing, it asked me if I would like to fix root. I pressed yes.
Then the phone go stuck between the boot screen and the recovery screen. It cannot enter the recovery mode (It got a flash of the clockworkmod, but it seems likes some error occurs). And now, I put my phone into Fastboot mode and plug it to my computer. The phone has turned "FASTBOOT USB" but when a use a fastboot command, it says "waiting for device" for a century...
And when my open up the "device manager" on my computer, it can recongnize "my HTC" but it's marked as an unrecongnized device.
I'm using Windows 8.1 on the Lenovo y510p, I think the Win 8.1 is the problem causing this...
I have tried to install the Intel USB 3.0 eXtensible Host Controller Driver as mentioned here, but my USB then goes out of function.
Also, the fastboot won't work even though I manually install the HTC Driver from the device manager.
I have got HTC Sync, ADB and fastboot all installed on the computer. Still got no luck.
Anyway to solve this?

EricLamYP said:
I have tried to flash a rom (Android Revolution HD 53.0) for my One. And after I finished flashing, it asked me if I would like to fix root. I pressed yes.
Then the phone go stuck between the boot screen and the recovery screen. It cannot enter the recovery mode (It got a flash of the clockworkmod, but it seems likes some error occurs). And now, I put my phone into Fastboot mode and plug it to my computer. The phone has turned "FASTBOOT USB" but when a use a fastboot command, it says "waiting for device" for a century...
And when my open up the "device manager" on my computer, it can recongnize "my HTC" but it's marked as an unrecongnized device.
I'm using Windows 8.1 on the Lenovo y510p, I think the Win 8.1 is the problem causing this...
I have tried to install the Intel USB 3.0 eXtensible Host Controller Driver as mentioned here, but my USB then goes out of function.
Also, the fastboot won't work even though I manually install the HTC Driver from the device manager.
I have got HTC Sync, ADB and fastboot all installed on the computer. Still got no luck.
Anyway to solve this?
Click to expand...
Click to collapse
What is your bootloader version? What recovery are you using and what version?
in the meantime I suggest you to use Windows 7 or boot a live ubuntu 12.04 32 bits version cd or bootable flash drive and use fastboot from there.

EricLamYP said:
I have tried to flash a rom (Android Revolution HD 53.0) for my One. And after I finished flashing, it asked me if I would like to fix root. I pressed yes.
Then the phone go stuck between the boot screen and the recovery screen. It cannot enter the recovery mode (It got a flash of the clockworkmod, but it seems likes some error occurs). And now, I put my phone into Fastboot mode and plug it to my computer. The phone has turned "FASTBOOT USB" but when a use a fastboot command, it says "waiting for device" for a century...
And when my open up the "device manager" on my computer, it can recongnize "my HTC" but it's marked as an unrecongnized device.
I'm using Windows 8.1 on the Lenovo y510p, I think the Win 8.1 is the problem causing this...
I have tried to install the Intel USB 3.0 eXtensible Host Controller Driver as mentioned here, but my USB then goes out of function.
Also, the fastboot won't work even though I manually install the HTC Driver from the device manager.
I have got HTC Sync, ADB and fastboot all installed on the computer. Still got no luck.
Anyway to solve this?
Click to expand...
Click to collapse
This fixed fastboot on my windows 8.1 pc
Download this > http://forum.xda-developers.com/attachment.php?attachmentid=2500592&d=1389122072
Easy instructions here > http://forum.xda-developers.com/showthread.php?p=49131915
Use the Old Dirty Solution it works perfectly

clsA said:
This fixed fastboot on my windows 8.1 pc
Download this > http://forum.xda-developers.com/attachment.php?attachmentid=2500592&d=1389122072
Easy instructions here > http://forum.xda-developers.com/showthread.php?p=49131915
Use the Old Dirty Solution it works perfectly
Click to expand...
Click to collapse
so im bout to try this as my phone will not communicate in bootloader. but i have a bigger problem before i get to that. my phone wont stay charged long enough or at all really. i prob dont even have to mess with bootloader if it would charge. so i can plug it in and it flashes red led and empty battery. i can get it into bootloader and then recovery twrp 2.7.0.0 i currently have no os installed but have several on my phone so dont need to mess with adb yet how can i get my phone to stay on long enough to flash a rom ? RUU out of question here because of 30%
i thought twrp was suppose to charge ? but when i get their it wont stay on

alray said:
What is your bootloader version? What recovery are you using and what version?
in the meantime I suggest you to use Windows 7 or boot a live ubuntu 12.04 32 bits version cd or bootable flash drive and use fastboot from there.
Click to expand...
Click to collapse
Get no luck on that... The y510p cannot even boot from a USB /___\
But anyway, I have borrowed my fds computer with Win 7 installed. And all works fine now. Thank you very much~~

ac3kill said:
so im bout to try this as my phone will not communicate in bootloader. but i have a bigger problem before i get to that. my phone wont stay charged long enough or at all really. i prob dont even have to mess with bootloader if it would charge. so i can plug it in and it flashes red led and empty battery. i can get it into bootloader and then recovery twrp 2.7.0.0 i currently have no os installed but have several on my phone so dont need to mess with adb yet how can i get my phone to stay on long enough to flash a rom ? RUU out of question here because of 30%
i thought twrp was suppose to charge ? but when i get their it wont stay on
Click to expand...
Click to collapse
Your Phone is broken send it to HTC or take it to a repair shop

[Q] Cannot Boot Into Recovery

I cannot boot the device into Recovery mode. If I attempt to the device stays on the Samsung boot screen. Since I have gotten the device all I have done is rooted the device and it is running android version 2.2
When I put the device into download mode it is not recognised by my computer (tried using Windows 7, 8.1 and 10 build 9926) and Odin (v4.38) does not register that the device has been plugged in. In Device Manager I get Unknown USB Device (Device failed Enumeration). Re-installing drivers and the device does nothing to fix this.
Any assistance with this issue would be welcomed.
~Edit - The device is not booting at all now. It is stick on the Samsung Boot Screen.
~Edit - For some reason putting the device into Download Mode then plugging it into a my laptop and allowing Windows Update to find the drivers worked and allowed ODIN v4.38 to detect the device.
Then by following this guide I was able to flash CWM to my device. After doing this I was able to boot the device normally and I was able to boot it into the custom recovery.

The best way to boot to recovery in case you aren't able to.
The best way to boot to recovery in case you aren't able to is using ADB. Use the command adb reboot recovery and for sure you will either know what the exact problem is, or will be taken to recovery.

Phone not detected

Hello,
I was on 10.0.7 version, rooted with magisk.
I had error while installing 10.0.8 version, then I downloaded 10.0.7 full rom, and used flash_all_except_data.bat.
Then after rebooting, it runs infinitely on loading animation (colors bar).
When I enter in fastboot, fastboot logo is displayed, but pc doesn't recognize phone anymore (fastboot devices show nothing).
[UPDATE]
I managed to boot with wiping data from recovery (Xiaomi stock recovery).
Now I can use the phone, but I don't have wifi (maybe something messed with vendor).
And I can't flash it because it is not recognized in fastboot mode (tried 3 W10 PCs, and 1 W7, it doesn't show in device manager)...
Can you help me ?

This is because the phone presents different device identifiers to the computer in these modes, and different drivers are needed, so it is possible to have proper drivers installed for one mode, but not the other. The fastboot program is simple and will just show the < waiting for device > message forever if drivers are missing. However, the same message may appear if the drivers are installed correctly, but the phone is not in the proper state with fastboot device IDs.
Make sure you aren't using a USB 3.0 port. Trying changing ports. The USB cable might also be the problem.
try using a direct usb 2.0 port on the pc ....
Otherwise reboot everything , erase cache first ?
Fastboot erase cache
or
Keep the phone connected and reboot the recovery , the led should come on then.
Keep the phone connected in the bootloader and reboot the pc.
If the problem still exists the let me know
What's the exact error ? Waiting for device
When the phone is in the bootloader is it recognized as fastboot usb (in red text) and what does the device manager in windows say about a android phone ?

MIN313 said:
This is because the phone presents different device identifiers to the computer in these modes, and different drivers are needed, so it is possible to have proper drivers installed for one mode, but not the other. The fastboot program is simple and will just show the < waiting for device > message forever if drivers are missing. However, the same message may appear if the drivers are installed correctly, but the phone is not in the proper state with fastboot device IDs.
Make sure you aren't using a USB 3.0 port. Trying changing ports. The USB cable might also be the problem.
try using a direct usb 2.0 port on the pc ....
Otherwise reboot everything , erase cache first ?
Fastboot erase cache
or
Keep the phone connected and reboot the recovery , the led should come on then.
Keep the phone connected in the bootloader and reboot the pc.
If the problem still exists the let me know
What's the exact error ? Waiting for device
When the phone is in the bootloader is it recognized as fastboot usb (in red text) and what does the device manager in windows say about a android phone ?
Click to expand...
Click to collapse
In fastboot mode nothing shows in device manager, with 3 different cables, with 4 different computers (3x W10, 1xW7).

I tried connecting with a live cd of CentOS.
Same results, adb connect when phone is started, but when I go in fastboot mode nothings shows in lsusb or dmesg...
Looks like the phone doesn't connect to pc in fastboot, very very strange...

Can't unlock bootloader, due to can't connect to fastboot

Hi guys,
I want to unlock the bootloader to flash a new recovery image and to flash lineageos on my device.
But connection to fastboot will not be established whatever approach I follow.
Stock Android is updated to the last version through update function.
I followed instruction on lineageos.org and on Sony side for my device to unlock bootloader,
I installed XZ2 device driver,
I used several versions of adb and fastboot (old and new versions)#
I tried Windows 7 prof. 32 bit, 64 bit, Windows 10 64 bit Prof.
I tried USB 2 and USB 3.0 ports
Don't know anymore what I should do to get things done.
If my XZ2 is running in normal Android mode, I'm able to access the internal memory via file explorer as well as
adb devices and
adb reboot bootloader is working.
Result: LED is almost not on, maybe one can detect a little bit of blue color and screen ist black.
Then
fastboot devices or
fastboot print-pit
will not give any answer. :-(
Does anyone have a good idea to proceed before I just give up?
Many thanks in advance
Illo

strange.
had the same issues with Windows 10. had to disable Win10 driver signature enforcement to install the correct Fastboot drivers for the Xz2.
So if it doesn't work in Windows 7 either you seem to have a different problem.

A. Try using different cable
B. Install 15sec adb installer
C. Reinstall the driver again after "adb reboot bootloader"
i had the same issue and tried various method. The thing that did for me was A. Weird, since the working cable was a cheap bundle one..

[SOLVED] Windows drivers for Honor 4X (Che2-L11). Not detected in bootloader mode

Hi
I'm trying to flash TWRP on my CHe2-L11 via adb but it gets stuck at < Waiting for any device >.
I read somewhere that is because Windows lacks the necesary drivers (although Che2-L11 is listed as "MTP" in the devices connected to my computer).
Where can I find the necessary drivers for Win10?
Thanks a lot
Best,
-a-

OK, I made a little progress I think. I'm not sure my issue is actually related to windows drivers but maybe I'm wrong.
Here's the deal:
When my phone is booted and connected to my PC,
adb device
spits up something : the phone is detected. Now after running
adb reboot bootloader
the phones reboots into bootloader mode (and displays the info that the bootloader is unlocked. But from now on,
adb device
in windows CLI outputs nothing : the phone is no longer detected.
Plus now the phone shows up as an unnknown device (fastboot2.0) in windows device manager. So? Missing driver I guess? Windows can not automatically find drivers for this...
Then it make sense that I cannot flash the custom recovery until the phone is detected again.
What should I do to have my phone detected in Windows while it is in bootloader mode?
Thanks a lot
-a-

Running windows update found a driver for
Google Android Bootloader Interface
However, ADB still cannot detect it
EDIT: Actually it works! Even though
adb devices
would not list anything when the phone was in bootloader mode, I was able to flash twrp
Problem solved!