Related
I've tried the latest revision Android USB drivers from the SDK platform updater. I've tried PDANet and the Universal Naked Drivers.
Basically, ADB works great, but as soon as I "adb reboot bootloader", my Win7x64 says "USB Device Not Recognised".
I've already gone into device manager and tried manually updating the driver to the various ones I've downloaded. I've also tried "uninstalling" the driver and reinstalling it, but it keeps coming up as unknown device.
When I type "fastboot devices", nothing shows up (obviously).
What am I doing wrong?
Ozzah said:
I've tried the latest revision Android USB drivers from the SDK platform updater. I've tried PDANet and the Universal Naked Drivers.
Basically, ADB works great, but as soon as I "adb reboot bootloader", my Win7x64 says "USB Device Not Recognised".
I've already gone into device manager and tried manually updating the driver to the various ones I've downloaded. I've also tried "uninstalling" the driver and reinstalling it, but it keeps coming up as unknown device.
When I type "fastboot devices", nothing shows up (obviously).
What am I doing wrong?
Click to expand...
Click to collapse
Same thing happening with me, i want to re-lock my bootloader but when i am in bootloader mode windows does not want to recognize the device, i have tried everything too.
Did you install the correct drivers?
When connected and in the bootloader open the device manager in windows. You should see "android 1.0" near the top.
Update that driver. It should work.
Sent from my Nexus 7 using xda premium
Ozzah said:
I've tried the latest revision Android USB drivers from the SDK platform updater. I've tried PDANet and the Universal Naked Drivers.
Basically, ADB works great, but as soon as I "adb reboot bootloader", my Win7x64 says "USB Device Not Recognised".
I've already gone into device manager and tried manually updating the driver to the various ones I've downloaded. I've also tried "uninstalling" the driver and reinstalling it, but it keeps coming up as unknown device.
When I type "fastboot devices", nothing shows up (obviously).
What am I doing wrong?
Click to expand...
Click to collapse
Hey, As i said earlier i was having the same problem...try switching your usb cable then try. That is what fixed my problems.
ive done all mentioned above, even tried 3 different cables, no luck, anyone have suggestions
I dont know about what you want to do, but if you want to root and unlock use the wugfresh took kit. Its the bomb and as soon as I figure out where I can thank him and give a big kudos I will give thanks.
Sent from my Nexus 7 using xda app-developers app
I could be wrong, but I don't think adb works from bootloader, but the fastboot command should. I think you can also use Google's Composite ADB Interface driver too for it (I can't reboot my N7 atm or else I'd find out).
I don't have any other android-related drivers on my system either, only Google's USB driver from the SDK. I'm also on Windows 8, but I would assume Google's USB driver would work fine on Windows 7 too.
Also certain USB filter drivers may cause issues too, such as libusb, or even AMD's USB filter driver (however, I had no problems). Or if you want to wipe out any/specific USB drivers, I recommend getting: http://www.nirsoft.net/utils/usb_devices_view.html
i want to unlock my bootloader but when i connect my nexus 7 to pc and use the command abd devices nexus 7 does not show up i tried installing this http://forum.xda-developers.com/showthread.php?t=1766220 but the install failed. Plz help as i can not unlock my bootloader
stranger97 said:
i want to unlock my bootloader but when i connect my nexus 7 to pc and use the command abd devices nexus 7 does not show up i tried installing this http://forum.xda-developers.com/showthread.php?t=1766220 but the install failed. Plz help as i can not unlock my bootloader
Click to expand...
Click to collapse
You need to enable USB debugging ...
Go to settings
Then go to about tablet
Then tap on build number aprox5 of 6 times ... You will see a toast notification the will say "you are now a developer"
Now try to what you tried to do before
Sent from my Nexus 7 using xda premium
You also will be unlocking the bootloader with fastboot commands, not adb.
ok i fixed it the usb degugging was already enabled. Just downloaded the drivers from asus website and now it is showing up in adb
Mods close the thread
I want to unlock my bootloader of moto g4 plus but there is many hurdles which I face.
First I switch on USB debugging and OEM unlocking ,then I installed minimal adb and fast boot.exe setup and move folder to c directory,than I connect my mobile in bootloader mode and login to Motorola page and download moto device manager ,than I go to minimal adb/fast boot folder and click shift+ right click and open command prompt and type fast boot devices but I show one comment,<where my device> now what to do?
keval3492 said:
I want to unlock my bootloader of moto g4 plus but there is many hurdles which I face.
First I switch on USB debugging and OEM unlocking ,then I installed minimal adb and fast boot.exe setup and move folder to c directory,than I connect my mobile in bootloader mode and login to Motorola page and download moto device manager ,than I go to minimal adb/fast boot folder and click shift+ right click and open command prompt and type fast boot devices but I show one comment,<where my device> now what to do?
Click to expand...
Click to collapse
I recommend to follow this guide https://forum.xda-developers.com/mo...de-root-moto-g4-plus-supersu-android-t3587918
When your device isn't recognized by your pc you need to check if any firewall, antivirus or the driver signature verification prevents your device from being recognized. Also make sure that you reboot your pc after the installation of the Motorola drivers.
Thanks man !! But in thread which you send is not help me untill I unlock my phone.
keval3492 said:
Thanks man !! But in thread which you send is not help me untill I unlock my phone.
Click to expand...
Click to collapse
Sure, in the first step: https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a otherwise please explain where you stuck when it's not the drivers?
In folder called mfastboot I click shift+ right click for open command prompt window.at this time my phone is connected with PC in bootloader mode and I installed moto device manager from moto website.
According to step 3( for unlocking bootloader in moto website) I type in command prompt fastboot oem get_unlock_data and press enter but I found this-<waiting for device>.
So, what can I do???
keval3492 said:
In folder called mfastboot I click shift+ right click for open command prompt window.at this time my phone is connected with PC in bootloader mode and I installed moto device manager from moto website.
According to step 3( for unlocking bootloader in moto website) I type in command prompt fastboot oem get_unlock_data and press enter but I found this-<waiting for device>.
So, what can I do???
Click to expand...
Click to collapse
Type "fastboot devices" when connected to the PC. If it shows your serial number of your phone then ok. If not, problems I mentioned before should be checked at your end.
I enter fastboot devices and again it shown <where my device> ,I reboot PC and also check but again it shown <where my device>.
My friend suggest that Motorola driver not installed properly ,so uninstall it first and install again ,and go to device manager and if yellow mark is shown then definitely driver is not installed ,but he not give any further information about it , because he didn't know. It shows , fastboot Athens 16_mps with yellow mark in device manager .
keval3492 said:
I enter fastboot devices and again it shown <where my device> ,I reboot PC and also check but again it shown <where my device>.
My friend suggest that Motorola driver not installed properly ,so uninstall it first and install again ,and go to device manager and if yellow mark is shown then definitely driver is not installed ,but he not give any further information about it , because he didn't know. It shows , fastboot Athens 16_mps with yellow mark in device manager .
Click to expand...
Click to collapse
Have you checked firewall and antivirus to be disabled?
You can also provide the whole console output here to get better overview of your errors :good:
Actually I don't have PC / laptop ,so for unlocking bootloader I was go to my friend' home and use laptop of him and there is disable firewall as you mentioned.
So ,now I am at my home ,so actually I can't show you actual process of laptop ,I was telling you what is happening to me ,if any solution is find then I will go to his house ,and process unlocking bootloader.
keval3492 said:
Actually I don't have PC / laptop ,so for unlocking bootloader I was go to my friend' home and use laptop of him and there is disable firewall as you mentioned.
So ,now I am at my home ,so actually I can't show you actual process of laptop ,I was telling you what is happening to me ,if any solution is find then I will go to his house ,and process unlocking bootloader.
Click to expand...
Click to collapse
Oh, nice to know...
Unless you did not provide an console output its hard to help. Additional you need to make sure that "fastboot devices" displays the serial number, if it doesn't, you need to check firewall, driver signature verification, antivirus etc etc on the PC of your friend.
It's a common problem and the things to check by your end are the same and everything I've seen and read it's cause of the mentioned problems. Maybe your friend has something wrong configured or whatever.
keval3492 said:
Actually I don't have PC / laptop ,so for unlocking bootloader I was go to my friend' home and use laptop of him and there is disable firewall as you mentioned.
So ,now I am at my home ,so actually I can't show you actual process of laptop ,I was telling you what is happening to me ,if any solution is find then I will go to his house ,and process unlocking bootloader.
Click to expand...
Click to collapse
In addition to strongst's helpful replies which I concur with (device signature enforcement on Windows 10 is a common issue, as it may stop you from installing the fastboot driver, and thus your device won't be loaded. Disable driver enforcement if you can and it doesn't void the laptop warranty), are you using the original Motorola USB cable or a high quality USB data cable? Also, try another USB port if you can.
For information, I've attached the Device Manager screenshot of my device, booted into the bootloader, and connected via the original USB cable to a USB 2.0 port. You'll note it's loaded as an Android Device via the Motorola ADB Interface (from the Motorola Device Manager software https://motorola-global-en-roe.custhelp.com/app/answers/detail/a_id/89881 ). Your device, loaded as fastboot athene_16mp suggests it's a driver issue.
Furthermore, if you want to unlock your bootloader, you'll need a computer to flash TWRP and may be useful having a computer around for troubleshooting/reverting back to stock Motorola firmware.
Just for curiosity sake I hope you changed the connection from charging to file transfer and switched on usb debugging. Cuz otherwise all what is needed already said by others. :/
Whenever I go to my friend's house and use his laptop to unlock my bootloader I will give you screen shot of display which causes problem for me to unlock my bootloader,thanks sir!!!!! And how to know that any anti virus ,firewall and other things you mentioned is stop me to install moto drivers?
Ayan Uchiha Choudhury said:
Just for curiosity sake I hope you changed the connection from charging to file transfer and switched on usb debugging. Cuz otherwise all what is needed already said by others. :/
Click to expand...
Click to collapse
Yes this is the basic for any unlocking bootloader process which I already done , switch on OEM unlocking,usb debugging,file transfer etc.thanks for it.
echo92 said:
In addition to strongst's helpful replies which I concur with (device signature enforcement on Windows 10 is a common issue, as it may stop you from installing the fastboot driver, and thus your device won't be loaded. Disable driver enforcement if you can and it doesn't void the laptop warranty), are you using the original Motorola USB cable or a high quality USB data cable? Also, try another USB port if you can.
For information, I've attached the Device Manager screenshot of my device, booted into the bootloader, and connected via the original USB cable to a USB 2.0 port. You'll note it's loaded as an Android Device via the Motorola ADB Interface (from the Motorola Device Manager software https://motorola-global-en-roe.custhelp.com/app/answers/detail/a_id/89881 ). Your device, loaded as fastboot athene_16mp suggests it's a driver issue.
Furthermore, if you want to unlock your bootloader, you'll need a computer to flash TWRP and may be useful having a computer around for troubleshooting/reverting back to stock Motorola firmware.
Click to expand...
Click to collapse
Yes!! My device is loaded with fastboot Athens 16_mps and I used original data cable(USB cable) from Motorola(which I receive when I purchased my device moto g4 plus),so how to disable driver enforcement as you mentioned!!I
I downloaded originally moto drivers from moto device and also install minimal adb/fastboot .exe setup. Thanks in advance.
keval3492 said:
Yes!! My device is loaded with fastboot Athens 16_mps and I used original data cable(USB cable) from Motorola(which I receive when I purchased my device moto g4 plus),so how to disable driver enforcement as you mentioned!!I
I downloaded originally moto drivers from moto device and also install minimal adb/fastboot .exe setup. Thanks in advance.
Click to expand...
Click to collapse
Tutorials for disabling driver enforcement can be found through a Google search (e.g. here's a link : https://www.drivethelife.com/window...e-enforcement-on-windows-10-8-7-xp-vista.html ) Of course, ask your friend before attempting this, as this allows you and anyone else to install and run unsigned drivers (including the fastboot drivers).
Okk thanks bro
So it is a safe driver(moto device manager)? Because if my friend ask me !!
keval3492 said:
So it is a safe driver(moto device manager)? Because if my friend ask me !!
Click to expand...
Click to collapse
You download it directly from motorola website? Why it should not be safe
Yes I downloaded from Motorola website ,it is also safe ,so why any PC not installed moto driver directly!!!!and gives fastboot _ Athens 16 mp s
Hey Guys,
i tried to Root my Moto E4 but Unfortunally i cant get Fastboot to work under Windows 10 Home 64 Bit on Both my Notebook and my PC. I installed The Motorola Device Manager (Since it comes with drivers) and installed ADB and Fastboot but once i Reboot into Fastboot Mode it wont Recognize it for flashing. The CMD Just Says Waiting for Device. I have expierience with Rooting other Phones but i never had this much Trouble getting Fastboot to work properly. Would be awesome if u could show me a Solution to this since i really want a Custom Rom.
Gesendet von meinem SM-A300FU mit Tapatalk
There's no trick, it just works. I have Windows 10 64 bit as well and no issues. Maybe you need to update your platform tools (adb and fastboot). Using old ones can be a problem.
What command are you issuing? Just fastboot devices ?
Make sure you're not using a USB 3.0 port on your computer.
madbat99 said:
There's no trick, it just works. I have Windows 10 64 bit as well and no issues. Maybe you need to update your platform tools (adb and fastboot). Using old ones can be a problem.
What command are you issuing? Just fastboot devices ?
Make sure you're not using a USB 3.0 port on your computer.
Click to expand...
Click to collapse
Few other thoughts:
- try a different cable; a cable that works for charging and adb communication may not work with fastboot
- avoid external hubs if possible
- be sure to reboot both devices after switching drivers if communication isn't immediately established
Marc_Xperia said:
Hey Guys,
i tried to Root my Moto E4 but Unfortunally i cant get Fastboot to work under Windows 10 Home 64 Bit on Both my Notebook and my PC. I installed The Motorola Device Manager (Since it comes with drivers) and installed ADB and Fastboot but once i Reboot into Fastboot Mode it wont Recognize it for flashing. The CMD Just Says Waiting for Device. I have expierience with Rooting other Phones but i never had this much Trouble getting Fastboot to work properly. Would be awesome if u could show me a Solution to this since i really want a Custom Rom.
Gesendet von meinem SM-A300FU mit Tapatalk
Click to expand...
Click to collapse
When you say you booted to fastboot what do you mean ?
Did use adb and your phone was recognized and then you issued adb command or what method are you using ....
You need to ensure you establish USB debugging connection first & grant authorization ...once link with authorization has been established run adb ...from adb check if recognized run command to boot to fastboot
So start from the top && go down
ARE YOU CERTAIN YOU USED CORRECT METHOD TO TURN OFF DRIVER VERIFICATION ON WINDOWS 10 && YOUR DRIVER ACTUALLY INSTALLED
Last noteworthy point ... when unlocking my motoE4 I had to boot to bootloader ONLY to use fastboot NOT "FASTBOOT"
Hold power + volume button
Excellent troubleshooting from our community. OP has not come back yet to confirm, ask another question, or simply a thanks. (Maybe he got it) Hopefully he gets it sorted.
Maybe the junior members underestimate just how quick and helpful our little community can be.
@Marc_Xperia Do not forget to install AndroidBootloaderInterface Driver Software. *android_winusb.inf*
Thats what my Problem is. I installed the Latest Android Studio, i have gone to SDK Manager. Installed the Android 7.1 Files and USB Drivers and this happens everytime i want to unlock my BL. And yes i disabled Driver Signing on Windows 10. I call it Fastboot Mode since im Used to Xperias so im Sorry i confused anyone.
Marc_Xperia said:
Thats what my Problem is. I installed the Latest Android Studio, i have gone to SDK Manager. Installed the Android 7.1 Files and USB Drivers and this happens everytime i want to unlock my BL. And yes i disabled Driver Signing on Windows 10. I call it Fastboot Mode since im Used to Xperias so im Sorry i confused anyone.
Click to expand...
Click to collapse
When you authorize your adb connection do you tick or select always allow connections from this device ...the fact that your device is listed as *unauthorised* is a clear indication in your previous attempts you didn't authorize to "allways allow connections" from this device
#result _when you reboot authorization is revoked
Enter bootloader mode the old skool way using your buttons..
# MAKE SURE TO SELECT "ALLOW OEM UNLOCK OPTION IN DEVELOPS settings
1.AUTHORIZE TO "ALWAYS ALLOW CONNECTIONS FROM THIS DEVICE"
2.enter bootloader using hardware keys
3.plug in usb
4.run fastboot devices to force fastboot to start deamon ...
5.once fastboot can see your device run oem unlock
6.DO NOT USE USB 3 port so try different USB ports on pc
7. Alternatively use a live USB of Ubuntu minimal to do the job
--- doesn't seem like driver problem if adb can see your device
See if that works
KevMetal said:
When you authorize your adb connection do you tick or select always allow connections from this device ...the fact that your device is listed as *unauthorised* is a clear indication in your previous attempts you didn't authorize to "allways allow connections" from this device
#result _when you reboot authorization is revoked
Enter bootloader mode the old skool way using your buttons..
# MAKE SURE TO SELECT "ALLOW OEM UNLOCK OPTION IN DEVELOPS settings
1.AUTHORIZE TO "ALWAYS ALLOW CONNECTIONS FROM THIS DEVICE"
2.enter bootloader using hardware keys
3.plug in usb
4.run fastboot devices to force fastboot to start deamon ...
5.once fastboot can see your device run oem unlock
6.DO NOT USE USB 3 port so try different USB ports on pc
7. Alternatively use a live USB of Ubuntu minimal to do the job
--- doesn't seem like driver problem if adb can see your device
See if that works
Click to expand...
Click to collapse
I did all of that. Next Problem when i boot the device with Vol Down + Power and select meta mode. I will get only the Motorola Logo or a Normal Reboot into System. I set everything up in Developer Settings. Enabled Debugging and Allow Bootloader Unlock.
Marc_Xperia said:
I did all of that. Next Problem when i boot the device with Vol Down + Power and select meta mode. I will get only the Motorola Logo or a Normal Reboot into System. I set everything up in Developer Settings. Enabled Debugging and Allow Bootloader Unlock.
Click to expand...
Click to collapse
Why select meta mode ? When you are in bootloader you use your volume keys to navigate between meta, recovery& factory reset & meta and you use your power key to select different modes ...what do you want to do in meta mode ?
When you are in bootloader you are essentially in fastboot mode too so it isn't necessary to choose any of the other options unless you are trying to get into recovery which is pointless if you haven't flashed custom recovery yet ..
I Succeded. I Booted into Bootloader with ADB and took a look at Device Manager to install the Driver Properly.
i followed this guide https://forum.xda-developers.com/moto-e4/how-to/guide-unlock-moto-e4-bootloader-unique-t3654275.
Thank you for all of your Replys.
Moto e4 magisk manger trying to instal magisk hide props config says install failed
happymedium22026 said:
Moto e4 magisk manger trying to instal magisk hide props config says install failed
Click to expand...
Click to collapse
Download manually and flash inside recovery yourself
Safety net says the response is invalid does that affect ny device being rooted
happymedium22026 said:
Safety net says the response is invalid does that affect ny device being rooted
Click to expand...
Click to collapse
No it doesn't. That's an error in magisk manager when you hide the manager app itself. Just use a different safetynet checker app if you want to check safetynet.
Why are you posting this stuff in this thread?
I have my phone on bootloader mode, and "Android Bootloader Interface" is listed there. Even if I install the Samsung driver of the same name, it still says "no drivers are installed for this device". Fastboot commands won't work even though adb works perfectly fine
AOSP100 said:
I have my phone on bootloader mode, and "Android Bootloader Interface" is listed there. Even if I install the Samsung driver of the same name, it still says "no drivers are installed for this device". Fastboot commands won't work even though adb works perfectly fine
Click to expand...
Click to collapse
Update: Replacing the Google drivers (ADB, bootloader, etc) with Samsung ones in device manager broke everything so I had to reinstall the Samsung USB drivers, and uninstall platform-tools and the Google drivers through Android Studio
Adb/fastboot drivers work with Samsung drivers, not against.
Install both, don't set a preferred driver.
After that connect your phone while it's active on the main OS, the Samsung drivers will then properly install for your device.
Once the set-up is finished, boot into fastboot and plug your phone in using USB.
You computer should install generic drivers or specified bootloader drivers.
ninjasinabag said:
Adb/fastboot drivers work with Samsung drivers, not against.
Install both, don't set a preferred driver.
After that connect your phone while it's active on the main OS, the Samsung drivers will then properly install for your device.
Once the set-up is finished, boot into fastboot and plug your phone in using USB.
You computer should install generic drivers or specified bootloader drivers.
Click to expand...
Click to collapse
The driver issue was fixed by turning USB debugging back on, as I forgot to after I tested the validity of that done to death method to enable the OEM unlocking option, of setting the clock a week back and all, which my prediction was right of it being complete garbage. ADB now detects my device again and I'm able to reboot into the bootloader, but fastboot still does absolutely nothing
AOSP100 said:
The driver issue was fixed by turning USB debugging back on, as I forgot to after I tested the validity of that done to death method to enable the OEM unlocking option, of setting the clock a week back and all, which my prediction was right of it being complete garbage. ADB now detects my device again and I'm able to reboot into the bootloader, but fastboot still does absolutely nothing
Click to expand...
Click to collapse
Yeah, sadly the a205u will probably never get root or custom ROMs. We have an extremely small chance since Samsung promised two major updates for the A20.
Either way, https://forum.xda-developers.com/android/software/tool-universal-fastboot-adb-tool-t3475832/amp/
Has the fastboot drivers if you haven't tried that one yet.
.