My G8 Power had Android 11, I tried to go back to Android 10 via adb, and then when I turned on the phone it died, it doesn't turn on, it doesn't charge, it doesn't go into fastboot mode, does anyone know how to solve it?
Re-flash Stock ROM.
xXx yYy said:
Re-flash Stock ROM.
Click to expand...
Click to collapse
I'm trying, but when I connect the cell phone to the PC and enter the device manager, the cell phone driver has a yellow symbol, as if the driver was badly installed, then blankflash does not recognize my device.
alonek said:
I'm trying, but when I connect the cell phone to the PC and enter the device manager, the cell phone driver has a yellow symbol, as if the driver was badly installed, then blankflash does not recognize my device.
Click to expand...
Click to collapse
Wrong ADB driver used!
Use the Android USB driver provided by OEM.
Where can I download the USB drivers for my device?| Motorola Support US
Visit the customer support page to view user guides, FAQs, bluetooth pairing, software downloads, drivers, tutorials and to get repair and contact us information.Where can I download the USB drivers for my device?
motorola-global-portal.custhelp.com
Related
Hi guys, I need your help.
I installed ClockWorkMod v6.0.1.9. I've done that with wkparts omaptools and fastboot. Any doubt, take a look at this:
http://forum.xda-developers.com/showthread.php?t=2045942
and this:
http://forum.xda-developers.com/showthread.php?t=1978543
Ok, thats fine, it worked. Now, when I boot into recovery mode (Holding VOLDOWN + 3D + Power) I get into ClockWorkMod.
So, I connect the USB cable in order to access the phone via ADB. But, when I look into device manager, there is a unknown device called "LGE COSMO USB Device" and I couldn´t figure out what driver I have to install. I installed LG United Driver and it didn´t work.
Any suggestion? Thks
adrianohck said:
Hi guys, I need your help.
I installed ClockWorkMod v6.0.1.9. I've done that with wkparts omaptools and fastboot. Any doubt, take a look at this:
http://forum.xda-developers.com/showthread.php?t=2045942
and this:
http://forum.xda-developers.com/showthread.php?t=1978543
Ok, thats fine, it worked. Now, when I boot into recovery mode (Holding VOLDOWN + 3D + Power) I get into ClockWorkMod.
So, I connect the USB cable in order to access the phone via ADB. But, when I look into device manager, there is a unknown device called "LGE COSMO USB Device" and I couldn´t figure out what driver I have to install. I installed LG United Driver and it didn´t work.
Any suggestion? Thks
Click to expand...
Click to collapse
Go to device manager and right klick on the unknown device and hit preferences.
there you go to tab details. there look for device instance path.
USB\VID_1004&PID_61FA&MI_04\6&301C001A&6&0004 == ADB
USB\VID_1004&PID_61FA&MI_02\6&301C001A&6&0002 == USB Serial Port
USB\VID_1004&PID_61FA&MI_00\6&301C001A&6&0000 == Platform USB Modem
Download and install LG drivers ala link section and part 1
http://forum.xda-developers.com/showthread.php?p=39269819
troopii said:
Go to device manager and right klick on the unknown device and hit preferences.
there you go to tab details. there look for device instance path.
USB\VID_1004&PID_61FA&MI_04\6&301C001A&6&0004 == ADB
USB\VID_1004&PID_61FA&MI_02\6&301C001A&6&0002 == USB Serial Port
USB\VID_1004&PID_61FA&MI_00\6&301C001A&6&0000 == Platform USB Modem
Click to expand...
Click to collapse
hi troopii,
i did that. here, i can see this:
USB\VID_1004&PID_D001\2CD00004000000010910D4D11800F00C
What does that mean? Is it ADB?
What am I suposed to do with this number?
Could you help me?
adrianohck said:
hi troopii,
i did that. here, i can see this:
USB\VID_1004&PID_D001\2CD00004000000010910D4D11800F00C
What does that mean? Is it ADB?
What am I suposed to do with this number?
Could you help me?
Click to expand...
Click to collapse
hmm looks interessting, i think you dont have a p920.
ok try a different way.
deactivate on your phone usb debugging.
plug your phone to the pc.
now you should have 2 unkown devices. one cdc serial and one lg cosmo usb device.
that lg cosmo usb device that you now see is Platform USB Modem.
now look at that device instance path and take a note.
now activate usb debugging again. plug phone to pc.
now you should have 3 unkown devices. one cdc serial and two lg cosmo usb device.
look again at the device instance path and if the current matches your note, you have found the "Platform usb modem" again. install driver for it
the other one should be the "android sooner singel adb interface".should be the same also in recovery.
gl
troopii said:
hmm looks interessting, i think you dont have a p920.
ok try a different way.
deactivate on your phone usb debugging.
plug your phone to the pc.
now you should have 2 unkown devices. one cdc serial and one lg cosmo usb device.
that lg cosmo usb device that you now see is Platform USB Modem.
now look at that device instance path and take a note.
now activate usb debugging again. plug phone to pc.
now you should have 3 unkown devices. one cdc serial and two lg cosmo usb device.
look again at the device instance path and if the current matches your note, you have found the "Platform usb modem" again. install driver for it
the other one should be the "android sooner singel adb interface".should be the same also in recovery.
gl
Click to expand...
Click to collapse
But I can´t desactivate USB debugging because I can´t access android in normal mode. I only can access android on Recovery Mode (ClockWorkMod).
I need to install some kind of driver to access the phone using ADB while in ClockWorkMod. I guess this is possible (I read this at http://forum.xda-developers.com/wiki/ClockworkMod_Recovery).
The problem is: when i connect the phone on PC while in ClockWorkMod there is a device called "LGE COSMO USB Device" and i didn´t find any driver that match.
drastic00 said:
Download and install LG drivers ala link section and part 1
http://forum.xda-developers.com/showthread.php?p=39269819
Click to expand...
Click to collapse
Hi,
I installed this two drivers:
LGUnitedMobileDriver_S497CA20_WHQL_ML_Ver_1.0
LGUnitedMobileDriver_S497MA20_WHQL_ML_Ver_1.0
Is that correct?
None of them worked. When I go to device manager, there is still a device called "LGE COSMO USB Device".
Read and follow all details carefully and it will work. You will need to change port to 41 as well as force omap4430 driver to install so it stops blinking.
drastic00 said:
Read and follow all details carefully and it will work. You will need to change port to 41 as well as force omap4430 driver to install so it stops blinking.
Click to expand...
Click to collapse
Hi drastic00, I really appreciate your help and attention.
Let me try to explain my problem: I can´t turn on the phone in normal mode and, of course, I can´t follow your steps. The phone is locked, there is a password to unlock the screen. So, I can´t desactivate the USB debugging because I do not have access to Android.
The only way I have to boot the phone is in recovery mode (ClockWorkMod). But, I need to access the device to copy the data. And it is possible to do that using ClockWorkMod and ADB. The problem is: when I boot my cell phone into recovery mode (now on screen I see the options of clockworkmod) and plug the usb cable, then there is device "lge cosmo usb device" and i can´t access the phone via ADB. I typed "adb devices" and the answer was nothing...
None of the driver install steps require phone to be booted; all driver install steps require battery to be out of the phone. So why can you not install drivers?
drastic00 said:
None of the driver install steps require phone to be booted; all driver install steps require battery to be out of the phone. So why can you not install drivers?
Click to expand...
Click to collapse
I installed all the drivers. When I connect the phone of my friend (a p920 too), it works fine! I can also access his phone using ADB.
Solution found
Thank you guys, I find the solution.
Thanks verry much for manekineko. See:
http://forum.xda-developers.com/showthread.php?t=2028598
It worked when I installed PdaNet+ drivers:
http://pdanet.co/a/
Thanks at all.
Hm. New one on me but good to know.
Hello! Im new here
The thing is that I bought a bricked OPO today hoping that I could fix it. I've been like 4-5hrs straight trying and nothing!
The real problem is that my OPO is not being recognized by my computer. (Im running Windows 8.1)
When I connect it to the PC the device vibrates but no sound, I go to device manager and it's not there (not as QHSUSB_BULK, not as UNKNOWN DEVICE, not as nothing, it just dont exist)
I installed the Samsung drivers, OnePlusRestoreTool, Bacon Root ToolKit, OnePlus One Toolkit and nothing seem to work...
I tried to get it into FastBoot mode but it ony vibrates every 10 consecutive seconds I hold the vol up + pwr button and NOTHING happen, screen remain black and no sound by my PC recognizing the device...
I tried alternate USB, alternate cable and nothing...
If you guys can help me that would be awesome!
Thanks, and sorry for my bad english.
Maximuseml said:
Hello! Im new here
The thing is that I bought a bricked OPO today hoping that I could fix it. I've been like 4-5hrs straight trying and nothing!
The real problem is that my OPO is not being recognized by my computer. (Im running Windows 8.1)
When I connect it to the PC the device vibrates but no sound, I go to device manager and it's not there (not as QHSUSB_BULK, not as UNKNOWN DEVICE, not as nothing, it just dont exist)
I installed the Samsung drivers, OnePlusRestoreTool, Bacon Root ToolKit, OnePlus One Toolkit and nothing seem to work...
I tried to get it into FastBoot mode but it ony vibrates every 10 consecutive seconds I hold the vol up + pwr button and NOTHING happen, screen remain black and no sound by my PC recognizing the device...
I tried alternate USB, alternate cable and nothing...
If you guys can help me that would be awesome!
Thanks, and sorry for my bad english.
Click to expand...
Click to collapse
Hi mate, am in exact same situation as yours.
Did you have any luck fixing it?
Maximuseml said:
Hello! Im new here
The thing is that I bought a bricked OPO today hoping that I could fix it. I've been like 4-5hrs straight trying and nothing!
The real problem is that my OPO is not being recognized by my computer. (Im running Windows 8.1)
When I connect it to the PC the device vibrates but no sound, I go to device manager and it's not there (not as QHSUSB_BULK, not as UNKNOWN DEVICE, not as nothing, it just dont exist)
I installed the Samsung drivers, OnePlusRestoreTool, Bacon Root ToolKit, OnePlus One Toolkit and nothing seem to work...
I tried to get it into FastBoot mode but it ony vibrates every 10 consecutive seconds I hold the vol up + pwr button and NOTHING happen, screen remain black and no sound by my PC recognizing the device...
I tried alternate USB, alternate cable and nothing...
If you guys can help me that would be awesome!
Thanks, and sorry for my bad english.
Click to expand...
Click to collapse
1st of all uninstall QHSUSB_BULK this driver,after this download qualcomm 9008 driver google it and install this driver then you can connect your #bacon it going to detected and dont forgot this process has to be done test mode and refer thia thread also http://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732
sid_844 said:
1st of all uninstall QHSUSB_BULK this driver,after this download qualcomm 9008 driver google it and install this driver then you can connect your #bacon it going to detected and dont forgot this process has to be done test mode and refer thia thread also http://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732
Click to expand...
Click to collapse
First of all thanks for your reply.
I have seen this thread but as you can see to uninstall the old driver I need to:
' Go to Device Manager, right click on the bricked USB device (QHSUSB_BULK or Qualcomm HS-USB QDLoader 9008) and go to Properties, click on Driver, then select Uninstall. Check the box to remove driver files, if prompted...'
But the device is not seen by the device manager.
Someone suggested in an other thread that I need just to press (not hold) power + volume button.
I will try that and let you know.
By the way what is 'test mode'?
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.
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.
Hi guys, long story short.
Installed Android 12 Beta, wanted to go back, tried to go back the the oxygen updater = phone fully bricked.
I can start the mobile with the first android start-up screen coming to live then it dies, I can access fastboot with vol up+down+power pressed but I can't do anything more.
I tried EVERYTHING to get MSMDownload tool to recognize my mobile but it does not, I don't think EDL mode is working for me.
Any ideas? I've read all the threads here I think and nothing works.
Couldn't connect to msm op9 global. /Now connecting. !
Ive uploaded signed Qualcomm driver's I found that install on windows and don't turn on test mode. These work. Then afterwards toggle USB options with device plugged in PC ,change from charging to PTP and let it automatically install drivers...
forum.xda-developers.com
mattie_49 said:
Couldn't connect to msm op9 global. /Now connecting. !
Ive uploaded signed Qualcomm driver's I found that install on windows and don't turn on test mode. These work. Then afterwards toggle USB options with device plugged in PC ,change from charging to PTP and let it automatically install drivers...
forum.xda-developers.com
Click to expand...
Click to collapse
I've actually tied that, does not work. I cannot get the Qualcomm to show in my device manager at all, the only thing I get is when I go to fastboot I get the Android Bootloader Interferance to show.