Hi.
i got this phone from a friend, and he said it was broken (didn't say how) and it didn't turn on.
when i plugged it into my computer with a normal usb cable, it showed the phone as "Forge HS-USB QDLoader 9008 (COM4)"
iv'e tried to boot in fastboot and recovery, but the only thing that happens is that it reconnects in the same mode.
iv'e also tried to use fastboot flash anyways, but it didn't worked. same goes for adb.
if any of you have a answer to this (that don't innvoles a jtag or any box or cable like that) i'll appriciate it
(PS. Im new to this forum)
problem solved, thx guys
my damn usb cable was the reason why fastboot did not change to fastboot usb
new cable, no probs
yay!!!!
hope anybody can help me....
my Google NexusOne is not running any rom
if i start the phone its starting 1-3 secs as normal than it stucks by the anDROID logo...
but if i start into the bootloader mode/fastboot - i can`t start recovery cause the phone restarts after that in the bootloader mode.´again...
if i plug in the usb cable - theres only FASTBOOT MODE but not the fastboot-mode USB
with the result that i can`t flash any boot.img or custom rom by adb/fastboot console
if i want to do anything by ADB-console/cmd-console the computer can`t not find my devices
who can help me....thx so many for your attention....
Hello everyone I am a new user
I have an old redmi 4A stuck on boot logo but recovery and fastboot are working I want to flash TWRP via fastboot but in my PC it is showing USB not recognised or unknown device in universal serial bus category and showing code 43 error in properties I have installed original ADB drivers for this device what to do please help me driver signature enforcement is also disabled what to do
just try a bunch of drivers, someone wil work, or reboot your pc.
so I can connect my bricked phone to a Windows PC by shorting the test points. But the device (Qualcomm HS-USB QLoader xxx) also keeps on disappearing in Device Manager. In most cases, the device only shows up in Device Manager for 1 second and disappears immediately.
Any ideas on how to fix?
Thanks
edit1: tried on a laptop running Windows 10 and another laptop running Windows 7.
edti2: My phone is stuck in a bootloop. I cannot even get it to boot into fastboot mode.
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...