Hello good nights to all, my question is this i have a g4 plus moto (xt1641) which they gave me, the problem is only on the led does not show that this charging, when reading in forums that stay in a brick, but not i could find a solution, i saw videos on youtube that explain how to leave this but the problem is that my pc (with windows 10) does not recognize the device, already install the drivers of motorola and the tutorials and still does not recognize nothing, someone else has happened this or any way to leave and to be able to operate my device, feel if it is a repost and also for my bad english and for writing in capital letters i had not realized.
Are you using a high quality USB data cable, or preferably the original cable that came with the device, and are you connecting to a USB 2.0 port? Also, do you have driver signature enforcement disabled on your Windows 10 PC? Without signature enforcement disabled, the fastboot drivers may not load. Does your computer detect that you've connected the device too (i.e. do you see the device appear in Device Manager, even if it's unrecognised)? Do you have another computer to test with?
Well. First time you must install all need drivers. Second time if your computer does not see it, try another usb or another computer or go to my computer - manage - device manager - maybe usb ports or something, your phone must see as qualcomm driver. If it is not there your comouter must go to test mode on or then off, see only for this reason next topic https://forum.xda-developers.com/moto-g4-plus/help/solved-unbrick-hard-bricked-dead-t3585016
Third time you must check your comouter test mode on or off must see your phone as qualcomm driver, try both time. When you will be test mode on or off restart your computer and then connect to cable. If your phone is not died, it must seen as qualcomm driver (first time maybe computer will say many times Usb do not recognize or something, this is good news, then you try that your phone seen as qualcomm driver)
Fourth time if it happens, you must see this tipic
https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761
Fifth time you must install adb mininal and fastboot. Then go to c disk, program files and see folder same name and copy this folder to desktop
Sixth time download april security patch files. If it is as .zip, please archive it and copy files to desktop folder adb mininal and fastboot https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
Seventh time go to instructions of again this topic (install blankfish.bat and etc)
https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761 (go to desktop folder adb and minimal fastboot, press shift and right mouse click, choose open powershall here and wait then for 2-3 minutes) then type in run commands, first 3 you must see up as write bootloader and next many commands you must see down side of this topic
Main is that your computer must read your phone even first time, usb not recognized or somthing, it is good news yellow sign (wait for about 3-4 minutes when you connect your phone) or see in computer > manage > device manager it must be as qualcomm driver. Also need to see you white light that your phone is charging or see computer that it is not dead. If battery is low try charge your phone for 30 minutes
Related
Wonder if anyone on here can help or if they've had a similiar issue.
My phone will connect to HTC sync no worries and i can drag drop files etc when i select the disk drive option...
but i'm trying to flash a custom rom and install the clockwork recovery image, the issue i have is in fastboot usb mode my Laptop is not recognising the phone being plugged in, if i leave the phone in Hboot and connect the usb it says its looking for a driver but fails to install properly even if i download and direct windows to the driver it still says it can't install, any suggestions i'm stuck at the moment cause without being able to get the laptop to recognise the phone i can't get the android interface to kick in (if that makes sense)
Running windows vista..
Thanks
wakers said:
Wonder if anyone on here can help or if they've had a similiar issue.
My phone will connect to HTC sync no worries and i can drag drop files etc when i select the disk drive option...
but i'm trying to flash a custom rom and install the clockwork recovery image, the issue i have is in fastboot usb mode my Laptop is not recognising the phone being plugged in, if i leave the phone in Hboot and connect the usb it says its looking for a driver but fails to install properly even if i download and direct windows to the driver it still says it can't install, any suggestions i'm stuck at the moment cause without being able to get the laptop to recognise the phone i can't get the android interface to kick in (if that makes sense)
Running windows vista..
Thanks
Click to expand...
Click to collapse
Have you got Android SDK installed on your PC, Im sure the driver is in there...android .1.0 driver I think..
Without Android SDK you cant use fastboot flash for clockwork image..
I have...
I tried about a dozen times yesterday to get windows to accept the drivers in the Android SDK folder and it wouldn't..
Today first time its actually installed them ? But when i plug the phone in it still doesn't bring up the android terminal interface.
In device manager it is showing the phone as android bootloader interface, but the pc isn't doing anything, is there a way to open up the interface if it doesn't automatically ?
I've tried the exe files in the Android SDK folder inc the emulator.exe and a terminal screen briefly appears (less than a second) then goes...
This is beginning to do my head in LOL...
Did you install and launched HTC sync? It should install all the necessary drivers.
f.
Sent from The Galactic Empire using the Dark Side of The Force
wakers said:
I have...
I tried about a dozen times yesterday to get windows to accept the drivers in the Android SDK folder and it wouldn't..
Today first time its actually installed them ? But when i plug the phone in it still doesn't bring up the android terminal interface.
In device manager it is showing the phone as android bootloader interface, but the pc isn't doing anything, is there a way to open up the interface if it doesn't automatically ?
I've tried the exe files in the Android SDK folder inc the emulator.exe and a terminal screen briefly appears (less than a second) then goes...
This is beginning to do my head in LOL...
Click to expand...
Click to collapse
Ok try this.... shut phone down, boot (volume down and power button) selected fastboot so it turns red, put the files into android-sdk-windows\tools. i-e the clockwork image and fastboot files
Plug usb cable in.
In "windows search program files" type cmd
now type cd c:\android-sdk-windows (unless you placed the android sdk somewhere else!!)
type cd tools
Type fastboot-windows flash recovery recovery-clockwork-2.5.1.2-ace-modaco-r2.img
When done type fastboot-windows reboot
You should now have CWM.
Now I know you may have tried this but It would help to find out what happens if you haven't already do so.
EDIT ...I also ask this because my laptop doesn't do anything either when I plug in usb cable in fastboot mode..im on windows 7....
Just trying to help...
Really appreciate the reply.
I got a "cannot load" Error.
I think its down to a driver for my phone when in the fastboot mode.
Whats might shed some light on something for someone with a bit more windows/android knowledge than myself is
When the phone is in Fastboot USB mode in Device manager the phone is listed as Android Bootloader interface but when i type into cmd "adb devices" nothing is listed.
When the phone is switched on normally and syncing with HTC sync in device manager the phone is listed as "my htc" and when i type adb devices in cmd, the message adb server is out of date killing...
then daemon is started and the device shows in my list ?
But HTC sync stops working ?
And the internet on my laptop stops working bizarrly.
I'm really scratching my head now lol
I'm thinking it must be something to do with not having the correct driver for Fastboot USB mode ?
Finally sorted it, had to remove the phone from device manager and delete the driver.
Then went into programs and features and removed everything to do with HTC.
Re-Installed HTC Sync
which also reinstalled HTC drivers
Plugged the phone in let windows select the driver and instead of showing in device manager as Android Bootloader Interface it showed as My HTC Sync and worked first time, not sure what happened but sure glad thats finally sorted..
Rixsta really appreciate the advice...
Cheers
I already have my samsung usb and android modem drivers installed. but everytime i plug my phone in with usb debugging on, the "Found New Hardware" window keeps popping up, why?
im not sure, but it could be the problem to why it always says "waiting for device" on superoneclick
My day job is pc tech, I have seen this a few times but going to follow the steps, first give me some info
Which version of windows?
32 or 64 bit?
How proficient are you at driver maint. *add and removeal ov drivers*
When did this start?
windows xp - 32 bit - and im pretty proficient at maintenance. i think its always been like this.
Ok, Do you always use the same USB port? and have you tried a different cable? and have you tried it on other computers? if so did it do the same thing there?
First we got to get rid of the drivers on the pc.
http://download.cnet.com/DriverMax/3000-18513_4-10572602.html
This is a free program that has a few nice features but most important is that it can tell you the name of the files that are used as drivers. After you install and register (its free, they just want to know who you are.. name, email, that kind of stuff) there will be an entry on the right side called "Installed Drivers Report". Make sure you phone is connected before you click this as it scans active drivers. it will generate a report you can scroll through and find any samsung driver entrys. Write down those file names, we will need them in a moment.
Go to device manager and remove the device there. Windows XP was kinda lame about device removal it did not actually remove the device just broke the connection. Vista and 7 give you the option to actually delete the files which make this easier. Since your on XP after the devices have all been removed UNPLUG your phone from the PC then start a search for those files in the Windows directory. Delete (or move) those files and the rerun the driver install program from here
http://forum.xda-developers.com/showthread.php?t=728929
After that it may setup and find new hardware a few times. Mine did it 3 since there are multiple different methods it can connect with and each uses differnet hardware. Also each time you use a differnt USB port it sees it as new device in a new location so it also goes through new hardware setup again.
Report back and let me know if this helped any.
okay thanks for the quick response. i will try it when I have time and ill get back to you. first, imma try it on a different computer.
also, when its plugged in and i open device manager, theres 3 yellow exclamation marks, one on the android modem, device, and in the "OTHER devices" section, the USB controllers. if that means anything.
just turn off usb debugging... and it will stop. turn it back on if you need to use it for something.
I'm using the Asus Google Nexus ToolKit V3.8.2 (donated version).
With my first N7 I was able to unlock and root.
Now I exchanged it against the N7 3G (HSPA+). I was able to unlock the device and able to install the bootloader 3.34. But root does not work. I think it is because ADB does not recognize the tablet.
What happens:
1.) the start screen of the ToolKit does not show the serial in the adb device list (If I restart the tablet in fastmode it list the serial in fastmode device list)
2.) if I start the Root and the ToolKit wants to reboot in Fastboot Mode it says "Waiting for adb Mode".
3.) If I restart on my own in Fastboot Mode and start the Root procedure then it reboots the device and says "Procedure will continue in 20 seconds Waiting for USB debugging to be enabled". It does not help to re-activate the usb debugging mode and it doesn't help to re-connect the usb cable.
4.) I started cmd and changed to the "Google Nexus 7 ToolKit" folder to call "adb-toolkit devices". But it does not show any device. adb-toolkit kill-server and start-server doesn't help. usb reconnect doesn't help.
P.S. As I'm a new member I'm not able to post inside the official support thread, sorry.
It could be a driver issue on the pc..
try this
download a pc app called usbdview . Do a google search to find it..
Run the program on the pc without the nexus plugged in. Delete all adb/ usb devices that you do not have physically plugged into your computer.
Plug in the nexus 7 refresh the list . Delete what ever comes up for the nexus 7..
Reboot the computer WITH the nexus not connected..
Install the NEXUS DRIVERS.. plug in the nexus and the computer should find the device as if its the first time used.
Try you tool kit again...
Sometimes when adb is started and stopped if there are several versions Windows can be confused and not stop the right driver but start a older version instead VERY Common windows usb issue. This works with any USB Trouble shooting for devices not just Android...
Good LUCK ..
It's pretty obvious that you need to install the correct drivers for the Nexus 7 HSPA+.
I'm not the lowest of the low, but I am the slowest of the slow.
exglynco said:
It's pretty obvious that you need to install the correct drivers for the Nexus 7 HSPA+.
I'm not the lowest of the low, but I am the slowest of the slow.
Click to expand...
Click to collapse
The nexus drives are a One driver for all Nexus Devices... This should only be a issue if there are multiple copies of usb adb in the windows registry . The usb drivers need to be removed then re installed or will just create more conflict. Usb Is NOT SO PLUG AND PLAY as it was intended.. Sometimes just plugging a usb device from one usb port to another in some computers can cause windows to install another copy of the driver. This is mostly on systems with a usb hub then a usb 2.o hub on a different port.. and so on.
I Use my notebook with several android devices . I often have issues with
erica_renee said:
It could be a driver issue on the pc..
Click to expand...
Click to collapse
This could it be. But I found a very simple solution:
stackoverflow.com/a/11991653/318765
When the Nexus 7 is plugged in there is a persistent notification that indicates "CONNECT AS / Media Device (MTP)". In this state adb devices will not show the Nexus, or undoubtedly any other device. Not exactly obvious, but if you select the second option "Camera (PTP)" the device is available for debugging (the lesson is ignore the camera, and focus on the protocol PTP).
This choice is persistent, and I'm guessing that with a band new device it will connect as MTP until told otherwise.
Click to expand...
Click to collapse
Hi,
I've received a couple of days ago two Onplus 5.
They both work great but when I try to connect them to my desktop, they get detected as "qualcomm hs-usb diagnostics 900e" by windows 10 that states the USB device is not recognised.
The issue is reproduced on a laptop, although it did get picked up once by the laptop, only to fail on a second attempt with the same device name "qualcomm hs-usb diagnostics 900e" after I installed the driver provided by Oneplus.
I read on the forum that "qualcomm hs-usb diagnostics 900e" is normally related to Bricked phone issues, which is not my case and I don't know what to do to resolve this.
I also tried to activate the USB debug mode on the phone, but this didn't change the problem.
My windows are all up to date and my phones as well (running Android 7.1.1, OxygenOS 4.5.2)
Has anyone experienced this issue with that phone or any other?
I would greatly appreciate some help and I thank you in advance for reading this and offering advice.
Unplug phone, restart windows.
Go to settings / about phone / press build number 5-6 time (don't remember exactly how many times) to enable developer options
turn on USB debugging
select USB configuration MTP (media transfer protocol)
plug it in
Install drivers
And now on you should have it working every time you plug it to your laptop.
dcrnic said:
Unplug phone, restart windows.
Go to settings / about phone / press build number 5-6 time (don't remember exactly how many times) to enable developer options
turn on USB debugging
select USB configuration MTP (media transfer protocol)
plug it in
Install drivers
And now on you should have it working every time you plug it to your laptop.
Click to expand...
Click to collapse
Thanks dcrnic, I must have skipped a step with the debugging mode because your procedure did the trick.
Is this a normal process to have to go to Dev mode and Debug mode to be able to connect to a PC?
Thanks again for your help!:good:
Win 10 do not recognize device as it is so new. Probably in the future this will be solved on Windows end.
I found online link for drivers
https://drive.google.com/file/d/0B-LgkimFUEksbjRCY1BkWnduVW8/view?usp=sharing
Moderators
Please delete ... Today forum is so slow, and it do double posting for some reason even I press reply just once.
Thank you.
FIXED: Use stock op5 cable. The other cable that gave me issues works just fine for op2.
The phone used to be seen by win10, but since oem unlock and superSU, the computer at work doesn't recognize it. Ran the 4.5.2 update with same results. I noticed that in Developer Options -> Select USB configurations charging is selected and greyed out. Going in selecting anything else returns is to Charing.
Device Manager > Find the phone > Right click > Update drivers (or something like that) > Select driver from Computer > Select "MTP USB Device" Enjoy
I'm having the same issue. If I manage to get it to connect to the PC, then after I unplug and plug it again it gives the same not recognised balloon. It only seems to work with USB Debugging On
I ended up using the original op5 cable and it recognizes the phone right away.The cable that didn't work for op5 is not stock, but worked perfectly fine for op2.
Same issue
Even I'm facing the exact same issue on my op5
dcrnic said:
Win 10 do not recognize device as it is so new. Probably in the future this will be solved on Windows end.
I found online link for drivers
https://drive.google.com/file/d/0B-LgkimFUEksbjRCY1BkWnduVW8/view?usp=sharing
Click to expand...
Click to collapse
The drivers are on the phone, they're mounted as a drive when you plug the phone in? They even add ADB tools when you install them, they're in C:\Program Files (x86)\OnePlus USB Drivers and the ADB tools are in the Android folder within there.
djsubterrain said:
The drivers are on the phone, they're mounted as a drive when you plug the phone in? They even add ADB tools when you install them, they're in C:\Program Files (x86)\OnePlus USB Drivers and the ADB tools are in the Android folder within there.
Click to expand...
Click to collapse
Yes, they are on the phone, but computer need to recognize device to see it. It does not, so the drivers on the phone are useless in this case.
I compared this to my ZTE Axon 7. If you choose "Charge only" the Axon 7 is recognized as a USB input device. This should also happen for our OP5 but the driver (which btw. is a windows standard driver) does not contain PID 900E and also does not like to have it forced to a USB input device.
The Axon 7's PID is F006.
However, the real issue is when Windows decides to use Qualcomm's HS USB Diagnostic Interface driver which seems to give even more trouble (at least for me). When I tried to switch to MTP this would not work and my Windows 10 hung itself up when rebooting or shuting down. For now I just disabled the "Unknown device" to prevent such things from happening. Charging still works this way and the phone is correctly recognized when changing to MTP.
If you are facing the same issue, disconnect the Oneplus 5 from your PC, reboot the PC and after that launch the device manager. You need to enable hidden devices in the view menu of the device manager to see disconnected devices. Now remove the device "Qualcomm HS USB Device Interface" and also choose to uninstall the driver itself. After that you can connect your device again and it should pop up as "Unknown device". Then simply disable the device.
Regarding the drivers from Oneplus: this package is lacking a driver for the device we are seeing (VID_05C6&PID_900E).
Does anyone know if the latest update (OxygenOS 4.5.5 update) addresses this issue? It says the following as one of the bug fixes:
"To restore connectivity to a Windows 10 PC, please turn off USB debugging prior to the upgrade"
aa_chow said:
Does anyone know if the latest update (OxygenOS 4.5.5 update) addresses this issue? It says the following as one of the bug fixes:
"To restore connectivity to a Windows 10 PC, please turn off USB debugging prior to the upgrade"
Click to expand...
Click to collapse
Worked for me, only remember to Uncheck usb debugging BEFORE the update....
Hmm, didn't work for me, same behavior as before the update...Qualcomm HS-USB as soon as phone is plugged in...USB debug was off.
Sent from my ONEPLUS A5000 using Tapatalk
try changing port (and remember to restart the pc)
Just got my phone today. It updated to 4.5.5 immediately. All I did was connect it to the computer (windows 10) and everything works.
bricky23 said:
Just got my phone today. It updated to 4.5.5 immediately. All I did was connect it to the computer (windows 10) and everything works.
Click to expand...
Click to collapse
It worked the first time too, but not the second time...at that point connected detected as Qualcomm HS-USB Diagnostic, and computer won't shut down.
And yes I installed it a few time, and it works the first time connecting, but not the second time around.
Sent from my ONEPLUS A5000 using Tapatalk
I don't have my OP5 yet, but I had a very similar and difficult experience with my OP3 when I first received it on Windows 10 Pro. On top of installing the proper drivers, I also had to go into Device Manager and run some steps (I'm going off on memory so they may not be entirely accurate). The root cause is driver signature check enforced in Windows 8+. So by going into Device Manager and seeing "kedacom USB driver", right click and find the oneplus USB driver you installed above and also need to disable the driver signature enforcement (in windows 10 go to advanced startup settings, reboot and choose (I think) #7 then reboot). Then plug in the phone usb go to device mgr right click on kedacom USB driver and choose the oneplus driver.
I don't have all the steps in the right order but it should fix your issue.
My phone wasn't showing up in Windows Device Manager when I connected the phone to my PC via USB cable. I had deleted then reinstalled the USB drivers so I thought that was the issue. Still, I was able to issue ADB commands to my phone and when I switched to bootloader mode the phone DID show up in Windows Device Manager as Android Device --> Android ADB Interface. Also, when I switched to EDL mode the Qualcomm chip showed up as Ports --> Qualcomm HS-USB QDLoader 9008.
Then later on, when my phone was still connected to the PC I happened to take a look at the USB Preferences. They seem to default to "no data transfer". But when I selected "File Transfer" as the option, suddenly my phone showed up in the Device Manager as Portable Devices --> OnePlus <model number>. Connected with the File Transfer setting turned on, I still seem to be able to issue ADB commands to the phone.
You might want to uninstall that driver from the PCI Encryption/Decryption Controller and install the one from your chipset vendor instead. It is part of your motherboard, not anything to do with your phone or adb
Masamune3210 said:
You might want to uninstall that driver from the PCI Encryption/Decryption Controller and install the one from your chipset vendor instead. It is part of your motherboard, not anything to do with your phone or adb
Click to expand...
Click to collapse
Thank you, Masamune, that's a good point. I don't know how it got messed up in the first place --it had the yellow warning triangle right from the start, even before I did anything with it. But clearly it's important and I need to get it fixed. I'll figure out the chipset vendor, as you suggested, and go from there. Much appreciation for the reminder, kind sir.
No Problem, Who knows with Windows what could have caused it, maybe a feature update blew the driver away for some reason. There are a myriad of things that it could have been