Hello, for some reason i cannot get my phone into fastboot. The main problem is that my PC with Win10 x64 does not find any device when i plug the USB cable in.
I have read in many forums that i have to discharge the battery so that the red LED blinks and then plug the USB. This is the case, but no device is found by windows...
any tips on how to get the qualcomm thing work so i can use MiFlash to flash an official ROM?
Almost impossible to loose fastboot, what did you do? Have you done this before? Are you sure windows cant find your device? I had a problem that for a few hours after brick my phone, windows didnt recognize my device as Qualcomm device... windows recognized my device as "something I cant remember", and suddenly after I connected my device to wall charger for a few minutes, suddenly apear in my computer as qualcomm device.
probably a dead battery or broquen usb port. try another cable
Related
I tried to replace the battery on my Nexus 5.
powered it down and opened it up. actual swap was done without incident​Now the phone does not recognize neithe of my batteries (old and replacement). I can boot it into bootloader just fine by plugging it in a charger, but the screen will show a battery with a ? in it when trying to boot the phone.
When I plug the phone in my PC, it will only get recognized as Forge HS-USB QDLoader 9008 (COM3) under PORTS in Device Manager. I've tried the diag tool here: and all tests look fine.
Rooted, bootloader unlocked, ElementalX kernel, 5.1.1
Thanks for any help!
I'm wondering if anyone has a Nexus 5 D821 motherboard in working condition that they would like to get rid of. Or if anyone knows of a way to get into Qualcomm 9008 mode from LGE Android Platform USB Serial Port. The phone seems dead, doesnt react to button presses, Vol Up+Vol Down+ Power doesnt change anything, the phone restarts back into LGE Android Platform USB Serial Port mode. No download mode. From what I know my EMMC wasn't dead (passed all the Board Diag Tests). Phone died after I flashed SBL1 with boarddiag (Even though I was told not to...)
There is a guide in general forums.
wangdaning said:
There is a guide in general forums.
Click to expand...
Click to collapse
Any links? From what i know i have tried all of them (LG flash tool, Board diag) I just cant get the phone to show up as anything other than the LGE Android Platform USB Serial Port
Excudent said:
Any links? From what i know i have tried all of them (LG flash tool, Board diag) I just cant get the phone to show up as anything other than the LGE Android Platform USB Serial Port
Click to expand...
Click to collapse
I hard bricked my phone yesterday and was stressing out quite a bit! Luckily I found this guide: http://forum.xda-developers.com/yureka/help/question-qualcomm-download-mode-k-t3068040
Note: I assume that you know what you are doing. Since you know about Qualcomm HS-USB QDLoader 9008 mode, you probably do, but you can do some serious harm with this mode.
Essentially, the gist of the guide comes down to installing the qualcomm drivers so that the phone becomes detected as a Qualcomm HS-USB QDLoader 9008. After this, you can use Boarddiag as you are used to to reflash the partitions. Note that for me, the phone was not in sahara dload mode and Boarddiag would not work. What I had to do was the following (these steps are done after the drivers are properly installed)
Unplug the Nexus 5 from your computer
Open the back cover and remove the 6 top screws holding the other protective cover
Disconnect the battery cable for 5 seconds. Reconnect it after
While holding the volume up and down button, plug it into your computer. It should now be in Sahara download mode and Boarddiag should work.
Let me know how everything goes!
I wanted to change my ROM from a xiaomi.eu ROM to Lineage OS 15.1 https://forum.xda-developers.com/mi-...-aqua-t3667638.
I had already rooted my phone and installed TWRP. I rebooted to TWRP and wiped cache, dalvik cache, data and system.
After that I installed the 8.5.1.0 firmware, that was done successfully. After that I tried to flash lineage-15.1-20180202-UNOFFICIAL-libra.zip in TWRP but I got an error message at an early stage. Eventually I switched off my phone through the menu of TWRP.
This was the last time I've seen my phone alive because no matter what I do, it doesn't respond at all.
I've tried to flash it through XiaoMiFlash, but my computer (nor my Macbook) doens't recognize my phone when I connect it through a USB cable
What to do guys?
Any possibilities that you've fully-drained your battery? Try to left your device charging on standard wall charger for at least 2 hours.
If it still bricked, you might wanna dissassemble the phone and disconnect the battery from the board and start flashing MiUi fastboot rom vie EDL mode.
kopter36 said:
Any possibilities that you've fully-drained your battery? Try to left your device charging on standard wall charger for at least 2 hours.
If it still bricked, you might wanna dissassemble the phone and disconnect the battery from the board and start flashing MiUi fastboot rom vie EDL mode.
Click to expand...
Click to collapse
I've never had any problems with the battery. And when I entered TWRP I saw the battery was 80%. But I'll try to charge my phone for at least 2 hours, just in case.
In order to perform flashing MIUI Fastboot via EDL mode, the computer should recognize the phone when it is connected through USB cable, right? If so, that's not the case with my phone. My computer is saying that an unknown device is connected to it. Do you think this will be different when I remove the battery?
MastaBlasta070 said:
My computer is saying that an unknown device is connected to it.
Click to expand...
Click to collapse
Perhaps the driver is missing? The next step will depend on the registered USB device ID, so please quote it. My Mi4C in emergency download mode displays the following:
Linux, command lsusb:
Code:
Bus 003 Device 003: ID 05c6:9008 Qualcomm, Inc. Gobi Wireless Modem (QDL mode)
or Windows, in Device Manager as Ports (COM & LPT) / Qualcomm HS-USB QDLoader 9008 (COM5):
Code:
USB\VID_05C6&PID_9008
You should see one of these: 9008, 9006, 0002, 0001 or similar.
MastaBlasta070 said:
I've never had any problems with the battery. And when I entered TWRP I saw the battery was 80%. But I'll try to charge my phone for at least 2 hours, just in case.
In order to perform flashing MIUI Fastboot via EDL mode, the computer should recognize the phone when it is connected through USB cable, right? If so, that's not the case with my phone. My computer is saying that an unknown device is connected to it. Do you think this will be different when I remove the battery?
Click to expand...
Click to collapse
Unknown device probably indicated missing driver for the QCom EDL mode as @k23m mentioned above. Try to install the driver first. If you are on Windows 8 and above, you might need to disable driver signature enforcement first.
If all going nicely, MiFlash should recognize your device based on COM port and not device id.
Good night,
Long time ago I been faced an issue, my phone not appear in my pc as usb. I been tryed yet: MTP mode, conect from TWRP, conect in a custom ROM, usb debugging. The notification for changer from charge only to MTP not appear, I alredy tried too: windows 7 and 10, motorola drivers, and nothing. Pleas help!
Note: when I connect the phone via bootloader there's no problem whit it!.
(sorry for my english)
Maybe you can try installing Motorola Device Manager, that installs the required drivers for the phone to e detected as a MTP device.
Also, in device manager, after connecting the device, look out for an entry with a yellow triangle. That indicates a driver problem. If it's there, try removing it by right clicking. Unplug and reconnect the device and let it finish installing the drivers automatically.
It's weird that it works on bootloader though. Does the device only charge while connected to PC (as if plugged into an actual charger) ? Is this the supplied cable or other?
Broadcasted from Zeta Reticuli
Gravemind2015 said:
Maybe you can try installing Motorola Device Manager, that installs the required drivers for the phone to e detected as a MTP device.
Also, in device manager, after connecting the device, look out for an entry with a yellow triangle. That indicates a driver problem. If it's there, try removing it by right clicking. Unplug and reconnect the device and let it finish installing the drivers automatically.
It's weird that it works on bootloader though. Does the device only charge while connected to PC (as if plugged into an actual charger) ? Is this the supplied cable or other?
Broadcasted from Zeta Reticuli
Click to expand...
Click to collapse
Thanks, but I tried and isn't work too... I think there is a weird bug... The phone charge with charger and connect as USB to pc. Think that I will use Google drive and Google photos to backup my files.
And really thank you. :laugh:
Need help. I was using Miracle Box to flash stock ROM, I don't know how but the phone (Micromax E453) is bricked now. I tried to start phone in Meta Mode (swiched off phone connected to PC by holding volume up button), it worked once, then following some tutorials I uninstalled (and checked, Delete the driver software for this device) MTK USB COM driver under port. Since then phone is not turning on and PC is not recognizing the device. Tired changing the USB cable and even tried it on another laptop, but no go. Kindly share what else I can try. PC has Windows 10 64 bit and MTK preloader vcom driver always has yellow exclamation mark (always installs with error code 10). I have disabled driver signature verificiation.
vnandwana said:
Need help. I was using Miracle Box to flash stock ROM, I don't know how but the phone (Micromax E453) is bricked now. I tried to start phone in Meta Mode (swiched off phone connected to PC by holding volume up button), it worked once, then following some tutorials I uninstalled (and checked, Delete the driver software for this device) MTK USB COM driver under port. Since then phone is not turning on and PC is not recognizing the device. Tired changing the USB cable and even tried it on another laptop, but no go. Kindly share what else I can try. PC has Windows 10 64 bit and MTK preloader vcom driver always has yellow exclamation mark (always installs with error code 10). I have disabled driver signature verificiation.
Click to expand...
Click to collapse
Did you have USB debugging enabled in the device's system settings before it got bricked? If not, you might not get it to connect via USB and be recognized.
Sent from my SM-S767VL using Tapatalk
Droidriven said:
Did you have USB debugging enabled in the device's system settings before it got bricked? If not, you might not get it to connect via USB and be recognized.
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
Thank you for your response. Yes, USB debugging was enabled before it got bricked. I was able to successfully see my device when I ran adb -devices command. I was also able to run fastboot commands. Now its completely dead.