Related
My Atrix is recognized by my computer under normal circumstances and when it's in RSD. But it is not recognized when in fastboot mode; I have reinstalled drivers, reflashed sbf, and unlocked phone. The very first step of rooting keeps giving me "waiting for devices", because phone is not recognized by computer.
I've been stuck here for 2 days now, reading, researching and I have come up with nothing. Any help would be greatly appreciated.
Please list the steps you follow from beginning up till the point you get the "waiting for devices" message.
Are you booted into fastboot on the phone? Are you using the Android SDK fastboot implementation or moto-fastboot? Do you have fastboot in your PATH or have you cd'd into the directory where you've extracted the fastboot package?
Having a similar issue... not my first go around on this model. I have been unlocked and the whole 9 yards...
I went back to locked stock 4.5.91 (to make sure I still could) successfully. Today I went through the usual manual and auto unlock methods and RSD mode will not work. I have the most recent drivers from Motorola. I tried alternate usb cables... I have the Flash Interface driver installed (3.2.11).
I launch RSD protocol but nothing happens on my PC and RSD Lite does not show device info....
Could Motorola have done this recently? Or is there an older RSD driver someone can point me to to try? My current one is 5-2011.
EDIT: Fastboot no go as well.... not trying to hijack just may be the same problem... I am going to factory again and give it a second go... ADB Devices does not see the phone either
what worked for me at least was reboot computer, reinstall motodriver helper or whatever its called, and plug in phone. it will say on the bottom left "installing drivers", then "drivers succesfully installed". then do fastboot. sometimes even when you install motodrivers, windows does not recognize it so it has to say "installing drivers" at bottom right. then try fastboot. at least thats what worked for me.
Dell2 said:
My Atrix is recognized by my computer under normal circumstances and when it's in RSD. But it is not recognized when in fastboot mode; I have reinstalled drivers, reflashed sbf, and unlocked phone. The very first step of rooting keeps giving me "waiting for devices", because phone is not recognized by computer.
I've been stuck here for 2 days now, reading, researching and I have come up with nothing. Any help would be greatly appreciated.
Click to expand...
Click to collapse
Not sure if it matters on the drivers..but i had the same issue yesterday. I had the "waiting for device" as well...
i had installed the wrong drivers. I had the 32 when i needed the 64. After installing the right ones..my device was recognized.
ethantarheels123 said:
what worked for me at least was reboot computer, reinstall motodriver helper or whatever its called, and plug in phone. it will say on the bottom left "installing drivers", then "drivers succesfully installed". then do fastboot. sometimes even when you install motodrivers, windows does not recognize it so it has to say "installing drivers" at bottom right. then try fastboot. at least thats what worked for me.
Click to expand...
Click to collapse
Tried that as well earlier... not sure where I am going at this point
defnow said:
Not sure if it matters on the drivers..but i had the same issue yesterday. I had the "waiting for device" as well...
i had installed the wrong drivers. I had the 32 when i needed the 64. After installing the right ones..my device was recognized.
Click to expand...
Click to collapse
Pretty sure I installed 64 but maybe I better double check...
I just started over completely, figured it out . Thanks for help guys, I can try out Alien3 now.
I confess my main problem was boneheadiness, I kept putting phone in fastboot mode(kinda sorta). When
fastboot came up I would connect phone to my computer, I never hit volume up to actually select fastboot.
I been kicking my computer for 2 days, I shudda kicked my dang self.
I am still stuck...
PC will not identify phone in RSD or fastboot. I have tried all drivers I can find, have uninstalled and reinstalled all software, the drivers install in each mode but RSD or the official moto software upgrade will not ID the phone when connected...
Anyone have an idea what to do? I have locked an unlocked this thing once before the 4.5.91 update and again after. I used the official Motorola Software Updater to "update" back to locked stock and have had this issue ever since then....
halfevildruid said:
I am still stuck...
PC will not identify phone in RSD or fastboot. I have tried all drivers I can find, have uninstalled and reinstalled all software, the drivers install in each mode but RSD or the official moto software upgrade will not ID the phone when connected...
Anyone have an idea what to do? I have locked an unlocked this thing once before the 4.5.91 update and again after. I used the official Motorola Software Updater to "update" back to locked stock and have had this issue ever since then....
Click to expand...
Click to collapse
Have you tried the moto-fastboot package?
mysticdrew said:
Have you tried the moto-fastboot package?
Click to expand...
Click to collapse
been reading about this, everything I read wants the img files and I have all sbf. Thing is I can not unlock my bootloader...
I was able to root through fastboot with no issues so it is ok, but I will be d*&$^d if I can get rsd running so I can unlock... it's not like this is new to me I have unlocked this thing twice before...
I just trying this to solve on my computer (Asus G51), but nothing I can do, reinstalling drivers, RSD Lite, nothing helped to solve this problem...so I went to another one computer (Acer) and I did it without any problem, install RSD Lite then drivers, unlock my bootloader at first time...I don't know where's the problem is, but I want know it
I am trying to relock my phone and install the newest RUU to get the firmware updates and I have hit a wall.
When I plug in my phone everything is peachy when its booted up and running. When I reboot into fastboot and plug in the phone it is not being recognized by my computer. I have made sure that while booted debugging is on, charge only, and everything is just as it was when I rooted(besides a different ROM). The phone isn't showing up anywhere, not in device manager and not in the devices/printers area. It will however still power the phone as it will stay on even if I pull the battery. I am running Windows 7 64. Any help would be greatly appreciated.
Also I have tried uninstalling and installing the phone drivers in device manager and restarting everything over and over, nothing is working.
Frosstyx said:
I am trying to relock my phone and install the newest RUU to get the firmware updates and I have hit a wall.
When I plug in my phone everything is peachy when its booted up and running. When I reboot into fastboot and plug in the phone it is not being recognized by my computer. I have made sure that while booted debugging is on, charge only, and everything is just as it was when I rooted(besides a different ROM). The phone isn't showing up anywhere, not in device manager and not in the devices/printers area. It will however still power the phone as it will stay on even if I pull the battery. I am running Windows 7 64. Any help would be greatly appreciated.
Also I have tried uninstalling and installing the phone drivers in device manager and restarting everything over and over, nothing is working.
Click to expand...
Click to collapse
the problem might be from usb cable.
try another one if you have.
Got it, I believe it was a driver issue, but I went through several things so not sure what finally worked...
Alright so up until 2-3 days ago my phone was working normal and fine. The. The other morning I wake up and my phone has a black screen no backlight, and is unresponsive. So I pulled the battery, restarted it, wouldn't get passed the boot animation without freezing.
Wiped it and installed a newer cm13 nightly I had, same issue. Played around flashing bootstacks and sometimes can get it too boot but then it seems gapps killed it (flashed them before booting). Restored a old 5.1 ROM and that worked some, went to upgrade and then its broke again.
Have completly wiped the internal SD and reflashed the 35b bootstack and varying cm13s and still nothing.
Plz hlp lol
Start fresh - use LG Flash Tool 2014 on a Windows PC to flash the 10B KDZ, re-root with the Stump app, install TWRP with TWRP Manager, then go from there.
roirraW "edor" ehT said:
Start fresh - use LG Flash Tool 2014 on a Windows PC to flash the 10B KDZ, re-root with the Stump app, install TWRP with TWRP Manager, then go from there.
Click to expand...
Click to collapse
That was my idea too, but i'm unable to get the flash tool to work. I've tried two different sets of drivers but the LGE android MTP device always fails even manually selecting it. On 2 different computers too. Is there something I'm doing wrong? I ran the adb script they list, installed the drivers, and ran the flash tool as a admin and from the utility. I'm kinda out of ideas.
I thought I had remembered seeing something about changing the com prt to 41 which I did and it worked, but I have some kind of bootloop going now haha
So i changed to the stock battery and now it's working better. Restarts much less but still does occasionally. Read that changing the battery fixes this issues but I have the restart with the stock battery and also the extended zero lemon. There has to be something hardware wise that'.s the issue
Mythbuster74 said:
That was my idea too, but i'm unable to get the flash tool to work. I've tried two different sets of drivers but the LGE android MTP device always fails even manually selecting it. On 2 different computers too. Is there something I'm doing wrong? I ran the adb script they list, installed the drivers, and ran the flash tool as a admin and from the utility. I'm kinda out of ideas.
Click to expand...
Click to collapse
This is the only driver you need.
http://www.lg.com/us/support-mobile/lg-LGVS985
Install it, reboot the PC, put the phone into Download mode connected to a USB 2.0 port with the original USB cable. The first time you connect to a different USB port it can take up to 10 minutes to load the driver. Check in Device Manager under modem. Once it's listed there, you're good to go.
Flash the 10B KDZ with LG Flash Tool 2014 in CSE mode. This'll wipe your internal storage again. Ignore any error dialogs LG Flash Tool 2014 displays. Don't click any buttons in the error dialogs, just move them out of your way if you have to. 99.9% of the time the phone will be flashed within 10 minutes.
Hello all.
I have hit a problem with my Hisense c20. I rooted using kingoroot and everything seemed to work fine. SuperUser was installed and working as it should. The phone then ran flat so I plugged it in and booted but it just hung on the SMART powered by android screen. So I restarted again into recovery mode and cleared system cache. Rebooted again but same thing. So tried again but with the wipe user data option. Still just hangs there. I then decided to try flash a stock rom via needrom. I followed the instructions but cannot seem to get the phone to be visible as a com port on Windows 7 64 bit. I have tried different cables and USB ports and reinstalled drivers countless times. Please could anyone assist me on getting this phone to be seen as a com port so I can flash it with QFIL.
Kind regards
Ryan
Ok so i managed to figure this out on my own. Basically what i did was plugged phone into pc while holding volume + and power. Phone showed up as Hisense in device manager, along with ADB device and USB composite device. I then right clicked on Hisense and uninstalled driver. Then i downloaded QCDLoader drivers and manually installed the driver via Have disk option and made sure to select the 9006 port driver package from the qcser.inf driver package. Once that was installed the phone was detected as a COM port. I then went into eMMC software download program in QPST and set the phone to download mode. Then back to device manager and saw QHUSB unidentified device. Right clicked that and went through same procedure as the 9006 driver except selecting the QCDLoader option instead of 9006 package. Phone then allowed me to flash Stock rom and was unbricked after a cache clear and system wipe. Took 3 days to figure it out but it worked. If anyone reading this is struggling with the same problem, let me know and i can go into more depth to try help. Really late and about to head off to bed.
Kind regards
Ruan
Need a file *qcn. or backup NV backup ?
Who has the opportunity to give?
[email protected]
[email protected]
RuanRex said:
Ok so i managed to figure this out on my own. Basically what i did was plugged phone into pc while holding volume + and power. Phone showed up as Hisense in device manager, along with ADB device and USB composite device. I then right clicked on Hisense and uninstalled driver. Then i downloaded QCDLoader drivers and manually installed the driver via Have disk option and made sure to select the 9006 port driver package from the qcser.inf driver package. Once that was installed the phone was detected as a COM port. I then went into eMMC software download program in QPST and set the phone to download mode. Then back to device manager and saw QHUSB unidentified device. Right clicked that and went through same procedure as the 9006 driver except selecting the QCDLoader option instead of 9006 package. Phone then allowed me to flash Stock rom and was unbricked after a cache clear and system wipe. Took 3 days to figure it out but it worked. If anyone reading this is struggling with the same problem, let me know and i can go into more depth to try help. Really late and about to head off to bed.
Kind regards
Ruan
Click to expand...
Click to collapse
Hi Ruan. You haven't found a custom recovery?
Hi Guys,
I might have ****ed up something,
I was on B131-SP1, rooted with magisk, I wanted to install B137, so I ran the magisk uninstall, repacked the B137 update, and ran the OTA.bat, everything went ok.
I wanted a fresh install, so I went in the recovery and wiped data.
To get root back I booted the phone in fastboot, and ran the magisk installer, and it asked to disconnect the phone and boot in to recovery,
everything ok, booted the phone in to recovery, and when I connected the phone I got a error on Windows that the device malfunctioned.
And since then also when I'm in fastboot the system won't recognize the phone anymore.
When the phone is on, I can run adb commands without problems.
I've tired everything, uninstalling and reinstalling drivers, Hisuite, other USB ports....
When I wiped the system, before flashing magisk again, I forgot to enable USB debugging and OEM unlock in developer settings, (tho BL was unlocked from before).
When I connect the phone in recovery, it shows in Windows as a failed mass storage device.
In fastboot I got to the point to have the right driver (Android bootloader interface) shown up, but it fails to start.
Anyone has a clue of what is happening?
I freaked out for a while thinking I might have done something wrong.
Turned out that Windows is the problem, since adb and fastboot are both working well on Ubuntu.
Luinwethion said:
I freaked out for a while thinking I might have done something wrong.
Turned out that Windows is the problem, since adb and fastboot are both working well on Ubuntu.
Click to expand...
Click to collapse
There is a regfile fix in mankindtws hwota thread, see if that one helps.
Or you could Google how to completely uninstall drivers, then reinstall minimal adb & fastboot.
ante0 said:
There is a regfile fix in mankindtws hwota thread, see if that one helps.
Or you could Google how to completely uninstall drivers, then reinstall minimal adb & fastboot.
Click to expand...
Click to collapse
Thanks, I found this register hack, and also made sure to reinstall all drivers from 0 but somehow Windows still refuses to recognize my phone.
I guess a reinstall is the best way of solving it. Or using Ubuntu from now on....
Luinwethion said:
Thanks, I found this register hack, and also made sure to reinstall all drivers from 0 but somehow Windows still refuses to recognize my phone.
I guess a reinstall is the best way of solving it. Or using Ubuntu from now on....
Click to expand...
Click to collapse
I ran into this also and I un-installed HiSuite, then re-installed it and after that in device manager set up drivers as seen in screen copy in attachement.
I also refer to this page for more info: https://www.dc-unlocker.com/huawei-mate-10-fastboot-usb-device-not-recognised-fix
Luinwethion said:
Hi Guys,
I might have ****ed up something,
I was on B131-SP1, rooted with magisk, I wanted to install B137, so I ran the magisk uninstall, repacked the B137 update, and ran the OTA.bat, everything went ok.
I wanted a fresh install, so I went in the recovery and wiped data.
To get root back I booted the phone in fastboot, and ran the magisk installer, and it asked to disconnect the phone and boot in to recovery,
everything ok, booted the phone in to recovery, and when I connected the phone I got a error on Windows that the device malfunctioned.
And since then also when I'm in fastboot the system won't recognize the phone anymore.
When the phone is on, I can run adb commands without problems.
I've tired everything, uninstalling and reinstalling drivers, Hisuite, other USB ports....
When I wiped the system, before flashing magisk again, I forgot to enable USB debugging and OEM unlock in developer settings, (tho BL was unlocked from before).
When I connect the phone in recovery, it shows in Windows as a failed mass storage device.
In fastboot I got to the point to have the right driver (Android bootloader interface) shown up, but it fails to start.
Anyone has a clue of what is happening?
Click to expand...
Click to collapse
Hi, I have the same problem after upgrading to 137 version. If the phone is on works with debug usb, also in fastboot mode works. Only in recovery mode windows doesn't find driver. Have you solved?
AntoRei said:
Hi, I have the same problem after upgrading to 137 version. If the phone is on works with debug usb, also in fastboot mode works. Only in recovery mode windows doesn't find driver. Have you solved?
Click to expand...
Click to collapse
So I reinstalled my PC from scratch, and I could get adb working, but no fastboot, so I ended up using Linux live flash drive.
Luinwethion said:
So I reinstalled my PC from scratch, and I could get adb working, but no fastboot, so I ended up using Linux live flash drive.
Click to expand...
Click to collapse
You can use this guide with linux?
https://forum.xda-developers.com/mate-10/how-to/guide-mate-10-flash-oreo-update-package-t3716814