I am trying to unroot my Nexus S and relock the boot loader. I've followed multiple guides and tried them on different computers (mac & windows). Every time I am supposed to type in "fastboot oem lock" and every time the command prompt just says waiting for device and nothing happens
I've installed the usb drivers from the android SDK so I'm lost as to why this is happening
I'm running the I9020T on Wind
Fix: Turns out it was just a driver issue, following these instructions got it working for me
Part 1 - Drivers
1 - Download Android SDK
2 - Unzip & launch "SDK Manager.exe"
3 - Cancel the first popup & go to "Available packages" > "Third party Add-ons" > "Google Inc."
4 - Select "Google USB Driver package" & click "Install Selected"
5 - Once you're finished go to your SDK installation "extras\google\usb_driver" dir
6 - (MOD EDIT: Ignore this step for i9020A models) Open "android_winusb.inf" and add the following lines to both "[Google.NTx86]" and "[Google.NTamd64]" sections :
;
;Google Nexus S GT-i9023
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_4E20
Click to expand...
Click to collapse
as described here [SOLVED] Google Android USB drivers - Nexus S SCLCD GT-i9023 not recognized
7 - Turn Off your SNS
8 - Make sure the SNS is connected to the PC via the USB cable
9 - Boot the SNS into the Bootloader Interface, by holding Volume UP & Power button
It reads LOCK STATE - LOCKED
Open Device Manager (or run devmgmt.msc) make sure you don't see this problem (windows failed to identify the SNS and install the correct drivers)
10 - Do a right click and select Update Driver Software
11 - Select Brose my computer for driver software
12 - Point it to your Android SDK installation "extras\google\usb_driver" dir
13 - Make sure to CLICK "Let me pick from a list of device drivers on my computer"
14 - Then from the list 3 choices select Android Bootloader Interface
15 - If it's installed properly it should show up like this (reboot is not required)
NOTE: if you encounter problems like question marks, unknown drivers, or exclamation marks eve after you have installed the drivers, download and try the USBDeview 32/64 to remove and uninstall all the junk USB devices from your computer/registry
Click to expand...
Click to collapse
Turn on usb debug inside the os.
Then do adb reboot bootloader
Once in bootloader do fastboot oem lock
Hope this helps
Sent from my Nexus S 4G using XDA
Unfortunately i've tried that, nothing happens after I enter fastboot lock
Once you unlocked your bootloader you can not lock it again.
Tom Foolery said:
Unfortunately i've tried that, nothing happens after I enter fastboot lock
Click to expand...
Click to collapse
Do you have a custom recovery installed? Did you try a different usb cable?
1. connect the USB cable directly to USB port on the laptop/desktop; dont connect via monitor USB or extension
2. Open device manager and check if the device is detected as ADB; you need to have the drivers installed
3. perform "fastboot oem lock"
or
Follow the step by step instructions here
zonesan said:
Once you unlocked your bootloader you can not lock it again.
Click to expand...
Click to collapse
Not true, i've done it...as have many others...
gullu101 said:
Not true, i've done it...as have many others...
Click to expand...
Click to collapse
Thanks very much, I always thought we can't lock back the bootloader.
gsrdemon said:
1. connect the USB cable directly to USB port on the laptop/desktop; dont connect via monitor USB or extension
2. Open device manager and check if the device is detected as ADB; you need to have the drivers installed
3. perform "fastboot oem lock"
Click to expand...
Click to collapse
I've tried these steps and I used the guide from nexusshacks but it didn't work.
Do you have a custom recovery installed? Did you try a different usb cable?
Click to expand...
Click to collapse
Although it probably didn't work because before I started the tutorial I installed a ROM which removed Clockwork recovery. I'm going to reroot my phone and try again from the beginning.
Edit: wait that's a lie, I did this a week ago so I'm not 100% sure what I did now, but I'm pretty sure I used the ROM from the guide
I've tried flashing a new recovery but I get the same "waiting for device" message
This makes me think it's a usb issue. I've been having usb issues for a while now, I've tried different cords and different computers. Is there any options I have left.
EDIT: Now I'm almost 100% sure the only thing standing in my way is the USB problems.
Try installing pdanet and using their drivers. Although i doubt this will work as im almost sure that the fastboot drivers arent the same as the adb drivers. Try disconnecting ng and reconnecting your phone on usb once you boot into bootloader.
Sent from my Nexus S 4G using XDA
Related
Most of you already know how to perform this procedure, but for those that don't, its simple.
NOTE: Unlocking your bootloader will perform a factory reset
Unlock Bootloader:
1. Open command prompt
2. Type 'adb reboot bootloader'
3. Type 'fastboot oem unlock'
4. Use volume keys to select 'yes, unlock bootloader'
5. Use power button to select option
6. Done!
Lock Bootloader:
1. Open command prompt
2. Type 'adb reboot bootloader'
3. Type 'fastboot oem lock'
4. Done!
Is there an icon, like there was with the padlock on the nexus one, after you unlock it?
SphericalPuma said:
Is there an icon, like there was with the padlock on the nexus one, after you unlock it?
Click to expand...
Click to collapse
On the Nexus S, you can do fastboot oem lock and it's like it never happened.
Where are you getting the Nexus drivers? When I select the USB driver folder in the SDK (fully updated) it just tells me that no drivers were found.
Ha, I just saw this. Great.
[REF] "fastboot oem lock" will lock the device back
at least the bootloader screen shows it can be locked back.
not tried really locked my customized kernel yet.
will update after trying
I can confirm this.
So you can lock the bootloader back after you unlock it? COOL
Sent from my T-Mobile G1 using XDA App
This is good
If I type fastboot devices I get the "unable to locate componant" error which says "this application has failed to start because AdbWinApi.dll was not found. Re-installing the application may fix the problem".
GrandMstrBud said:
If I type fastboot devices I get the "unable to locate componant" error which says "this application has failed to start because AdbWinApi.dll was not found. Re-installing the application may fix the problem".
Click to expand...
Click to collapse
update to the latest sdk
Nexus 1 said:
update to the latest sdk
Click to expand...
Click to collapse
I do have the latest. I don't see any USB drivers in the package but it does show up as an android ADB device. Now I'm trying it on my laptop and it will not find any USB drivers so it's showing up as unknown device.
Sent from my Nexus S using XDA App
Google USB Drivers are in the SDK manager under third-party, I had the same problem as you
SphericalPuma said:
Google USB Drivers are in the SDK manager under third-party, I had the same problem as you
Click to expand...
Click to collapse
I found those but those do not seem to work. When the phone is powered on it does show an ADB device but when in fastboot mode the drivers I downloaded do not work. So I need some samsung drivers or something for this?
TheBiles said:
Where are you getting the Nexus drivers? When I select the USB driver folder in the SDK (fully updated) it just tells me that no drivers were found.
Click to expand...
Click to collapse
Same thing here
GrandMstrBud said:
Same thing here
Click to expand...
Click to collapse
I have the same problem too. The drivers installed fine for the device in normal mode. But once I go into fastboot, it is displayed as an "Android 1.0", with the yellow icon in the device manager.
Attempting 'fastboot oem unlock' it just stays there waiting for a device...
you need to manually install driver using "have disk".
TheBiles said:
Where are you getting the Nexus drivers? When I select the USB driver folder in the SDK (fully updated) it just tells me that no drivers were found.
Click to expand...
Click to collapse
If you are having issues with the stock usb drivers, then try this:
http://forum.xda-developers.com/showthread.php?p=9861928#post9861928
vespid said:
If you are having issues with the stock usb drivers, then try this:
http://forum.xda-developers.com/showthread.php?p=9861928#post9861928
Click to expand...
Click to collapse
The part about installing PDAnet does fix the Android 1.0 driver problem, for me anyways. Once you get fastboot working, it seems fine to uninstall the program since it is still working for me.
The latest driver is version 4. You can open up the SDK Manager and download it. Look under available packages (I think that's what its called).
SphericalPuma said:
Is there an icon, like there was with the padlock on the nexus one, after you unlock it?
Click to expand...
Click to collapse
Yes. I've never had the Nexus One before, but the padlock icon did appear once I did the fastboot oem unlock.
So once we have clockwork recovery installed and rooted can we lock the bootloader with no problems?
I have followed Heisenbergs instructions to the letter but when I issue the adb devices command it just returns the string "list of devices" and that's it. Fastboot devices doesn't work either.
So I'm stuck at the start. Can anyone help me? From what I can tell I may need drivers but I'm new to this so I don't know.
I can give anyone more info if they need it.
I believe part of the instructions are to install the Platform Tools, which should include drivers. Try running the SDK Manager and updating or installing the drivers again. Also ensure you have USB Debugging ON in your Developer settings and OEM Unlocking enabled. Lastly, tap the notification in your shade about the USB connection (I think it defaults to Charging Only) and change it to various modes. Mine seems to only work on PTP mode. When you run the adb devices command you will need to authorize the connection on the phone end the first time by clicking OK so make sure the screen is on and unlocked so you can see it.
Hope this helps.
peckaldee said:
I have followed Heisenbergs instructions to the letter but when I issue the adb devices command it just returns the string "list of devices" and that's it. Fastboot devices doesn't work either.
So I'm stuck at the start. Can anyone help me? From what I can tell I may need drivers but I'm new to this so I don't know.
I can give anyone more info if they need it.
Click to expand...
Click to collapse
u enable OEM Unlock under developer settings?
You enable USB debugging?
Me personally do not get any strings of data returned when im on fastboot
i open CMD, run ADB DEVICES, get message saying the port is opening, and then listing devices... which is empty
but i am able to flash anything i want using fastboot....
try this command and see if it works after that... fastboot reboot-bootloader
it should reboot bootloader for u.. thats a easy way to know its responding to u
Is the device showing properly in the Device Manager when it's connected to your system?
hEaTLoE said:
Is the device showing properly in the Device Manager when it's connected to your system?
Click to expand...
Click to collapse
It shows up in windows explorer as "Nexus 6p" when I plug in the USB cable.
I have USB debugging and unlock bootloader checked in settings.
My fastboot devices command returns nothing.
peckaldee said:
It shows up in windows explorer as "Nexus 6p" when I plug in the USB cable.
I have USB debugging and unlock bootloader checked in settings.
My fastboot devices command returns nothing.
Click to expand...
Click to collapse
Did you change the USB mode? Mine shows in Explorer as you described but won't work in ADB/Fastboot until I change it to PTP.
fury683 said:
Did you change the USB mode? Mine shows in Explorer as you described but won't work in ADB/Fastboot until I change it to PTP.
Click to expand...
Click to collapse
Yeah I tried every option. Nothing.
The instructions say the fastboot devices command should return my serial number and it does not.
When booted into the bootloader one it tells me on one line phone LOCKED and on another line says download mode DISABLED.
Don't know if this has anything to do with my problems but I still cannot get a return on the fastboot devices command in order to proceed with the unlock command of "fastboot flashing unlock"
remember that u need latest fastboot for this to work.
did u updated the SDK manager to the latest? i had to do that in order to work for 6P
chaco81 said:
remember that u need latest fastboot for this to work.
did u updated the SDK manager to the latest? i had to do that in order to work for 6P
Click to expand...
Click to collapse
I'm using sdk manager revision 24.4.1
peckaldee said:
I have followed Heisenbergs instructions to the letter but when I issue the adb devices command it just returns the string "list of devices" and that's it. Fastboot devices doesn't work either.
So I'm stuck at the start. Can anyone help me? From what I can tell I may need drivers but I'm new to this so I don't know.
I can give anyone more info if they need it.
Click to expand...
Click to collapse
I had the same issue ,it was down to when I plugged the phone into the PC for the first time,it installed the Google.USB driver ,but it didn't install the driver for the adb interface,I had to download it from Google and install it manually
I also had the same issue, I had an old Clockworkmod generic driver that I was using for my Samsung Galaxy S5 installed.
Go to Device manager (either type it in the start menu, or: right click This PC, click manage, and click device manager), plug in your unlocked Nexus 6P phone and watch for a new item to pop up. If it says android something, uninstall it. I had to uninstall 3 times, then reinstall the drivers from the SDK before it would work.
I used the skipsoft toolkit to install the fb drivers; worked for me. http://forum.xda-developers.com/nex...ol-skipsoft-android-toolkit-nexus-6p-t3234159
but like others said, you may have to manually remove any that are already installed in windows, although I think that is one of the options in the toolkit.
mbonus said:
I used the skipsoft toolkit to install the fb drivers; worked for me. http://forum.xda-developers.com/nex...ol-skipsoft-android-toolkit-nexus-6p-t3234159
but like others said, you may have to manually remove any that are already installed in windows, although I think that is one of the options in the toolkit.
Click to expand...
Click to collapse
This worked. Now my commands in terminal are working correctly. thanks all for the help
Got A device to pop up under the command adb devices, but nothing under fastboot devices. Any tips? Had to follow the skipsoft instructions to install adb/fastboot devices. Yes USB Debugging is on and the OEM unlocking is set to allow..
Christ I'm retarded. Sorry boys, thought my phone was in the bootloader when I was trying this command LOL
Same problem
peckaldee said:
When booted into the bootloader one it tells me on one line phone LOCKED and on another line says download mode DISABLED.
Don't know if this has anything to do with my problems but I still cannot get a return on the fastboot devices command in order to proceed with the unlock command of "fastboot flashing unlock"
Click to expand...
Click to collapse
I'm having the same problem. Did you ever figure out what was wrong?
mbonus said:
I used the skipsoft toolkit to install the fb drivers; worked for me. http://forum.xda-developers.com/nex...ol-skipsoft-android-toolkit-nexus-6p-t3234159
but like others said, you may have to manually remove any that are already installed in windows, although I think that is one of the options in the toolkit.
Click to expand...
Click to collapse
Solved my problem as well. Thanks!
MSM8994DownloadTool.exe Won't Work For Me
I need help.
My phone is stuck on the fastboot screen, meaning I can only Power if off and into Fastboot (using the Vol+ and Power buttons). Other than that, it does nothing. I cannot get into the OS at all, which means I can't enable USB debugging or anything. Fastboot recognizes my device, which is a OnePlus Two), but ADB won't, nor will my Windows 7 PC as a USB device. With that in mind, I followed all the steps in the posted guide. I get all the way to running the "MSM8994DownloadTool.exe" and nothing happens. Its as if the Recovery Tool doesn't even see my device. So, I'm really stuck and don't know what to do.
For clarity, here's exactly what I did (see below). I get all the way to Section B, Step 2 and that's where it breaks down. There's no different line, and no process ever runs, even after waiting 30 minutes. I ran the tool as Administrator, but still no luck. Can anyone help me? Just as additional info, my Mac also does not recognize my OPT as a USB device. Also, I tried my backup USB-C cable from the OEM, with the same results.
A. Install the Certificates followed by the Qualcomm drivers.
1. Restart your computer with Driver Signature Enforcement Disabled (Advanced Startup) Let me Google it For You
2. Open the folder "qc" and install the Test Certificate in the following Stores: Trusted Root, Trusted Publisher, Third-Party Root and Personal
3. Run the Qualcomm setup wizard (also located in the qc folder)
4. When completed, restart your PC again with Driver Signature Enforcement Disabled (Advanced Startup)
5. Turn off your phone and disconnect the USB cable from the phone.
6. Hold vol-up and plug in the USB(Do not press Power button). The screen will stay black but you will hear a sound from windows that a device is attached.
7. The driver should now automatically install. If not, go to device manager and right click "Unknown Device" and click "Update Driver" Search up the QC folder and press ok. The driver should now install. (Got the RELINK issue? Take a look here: http://forum.xda-developers.com/show...1&postcount=46)
B. Flashing Process
1. Open the OnePlus2_14_A.11_151211 folder and open "MSM8994DownloadTool.exe"
2. Look if your phone is detected in the list. everything is Chinese but you will see one row with different chinese text from the rest within the list. If not, recheck if driver is detected in Device Manager (If not, go back to Step A - Line 4).
I think you have a bad download, try downloading it again and download the 3.0.2 version if you can.
Phil01234 said:
MSM8994DownloadTool.exe Won't Work For Me
I need help.
My phone is stuck on the fastboot screen, meaning I can only Power if off and into Fastboot (using the Vol+ and Power buttons). Other than that, it does nothing. I cannot get into the OS at all, which means I can't enable USB debugging or anything. Fastboot recognizes my device, which is a OnePlus Two), but ADB won't, nor will my Windows 7 PC as a USB device. With that in mind, I followed all the steps in the posted guide. I get all the way to running the "MSM8994DownloadTool.exe" and nothing happens. Its as if the Recovery Tool doesn't even see my device. So, I'm really stuck and don't know what to do.
For clarity, here's exactly what I did (see below). I get all the way to Section B, Step 2 and that's where it breaks down. There's no different line, and no process ever runs, even after waiting 30 minutes. I ran the tool as Administrator, but still no luck. Can anyone help me? Just as additional info, my Mac also does not recognize my OPT as a USB device. Also, I tried my backup USB-C cable from the OEM, with the same results.
A. Install the Certificates followed by the Qualcomm drivers.
1. Restart your computer with Driver Signature Enforcement Disabled (Advanced Startup) Let me Google it For You
2. Open the folder "qc" and install the Test Certificate in the following Stores: Trusted Root, Trusted Publisher, Third-Party Root and Personal
3. Run the Qualcomm setup wizard (also located in the qc folder)
4. When completed, restart your PC again with Driver Signature Enforcement Disabled (Advanced Startup)
5. Turn off your phone and disconnect the USB cable from the phone.
6. Hold vol-up and plug in the USB(Do not press Power button). The screen will stay black but you will hear a sound from windows that a device is attached.
7. The driver should now automatically install. If not, go to device manager and right click "Unknown Device" and click "Update Driver" Search up the QC folder and press ok. The driver should now install. (Got the RELINK issue? Take a look here: http://forum.xda-developers.com/show...1&postcount=46)
B. Flashing Process
1. Open the OnePlus2_14_A.11_151211 folder and open "MSM8994DownloadTool.exe"
2. Look if your phone is detected in the list. everything is Chinese but you will see one row with different chinese text from the rest within the list. If not, recheck if driver is detected in Device Manager (If not, go back to Step A - Line 4).
Click to expand...
Click to collapse
I've bricked my op2 a while ago. I'm a real noob so I don't know if it will work but have you installed the adb mac drivers or try "fastboot continue" while in fastboot. Just don't give up and keep try. You have absolutely nothing to lose.
chintu1234 said:
I think you have a bad download, try downloading it again and download the 3.0.2 version if you can.
Click to expand...
Click to collapse
Thank you very much. I have the latest version, but still nothing. I don't know if this has anything to do with it, but my OPT wasn't being recognized as a USB device even before I screwed up. That leads me to believe my OPT USB is maybe not functional. ADB doesn't recognize it at, nor will the MP...DownloadTool.exe. I'm guessing it is just hard-bricked since I have no other way (besides USB) to interface with the device.
Phil01234 said:
Thank you very much. I have the latest version, but still nothing. I don't know if this has anything to do with it, but my OPT wasn't being recognized as a USB device even before I screwed up. That leads me to believe my OPT USB is maybe not functional. ADB doesn't recognize it at, nor will the MP...DownloadTool.exe. I'm guessing it is just hard-bricked since I have no other way (besides USB) to interface with the device.
Click to expand...
Click to collapse
Try connecting your OPT to some other guys pc and see, it may be because of your pc's end that its not getting connected.
And if the same thing happens with a different pc then yeah your usb port or something is fried. Try going to service center if the same thing happens again.
I had installed Moto drivers and also enabled the usb debugging but my my device is not showing in fastboot mode.
Seriously need help.
Thank you.
Just to clarify, when you reboot your device into the bootloader (fastboot), if you type the command 'fastboot devices' (without quotes) in ADB, you get nothing showing up in the device list?
Which Moto drivers are you using, what device do you have and are you issuing the commands via minimal ADB or another ADB command tool?
echo92 said:
Just to clarify, when you reboot your device into the bootloader (fastboot), if you type the command 'fastboot devices' (without quotes) in ADB, you get nothing showing up in the device list?
Which Moto drivers are you using, what device do you have and are you issuing the commands via minimal ADB or another ADB command tool?
Click to expand...
Click to collapse
I am using Motorola device manager drivers and using minimal adb tools
When I type command mfastboot devices nothing shows.
And I am trying to flash TWRP recovery it's saying waiting for device
Robinson#2 said:
I am using Motorola device manager drivers and using minimal adb tools
When I type command mfastboot devices nothing shows.
And I am trying to flash TWRP recovery it's saying waiting for device
Click to expand...
Click to collapse
Turn on your phone and run " adb devices " then see if it's getting connected in power on mode or not.. if not then try to install Adb Drivers..
Tried with ADB drivers still not working. I think its a driver problem how to reset drivers in Windows 10 machine
Robinson#2 said:
Tried with ADB drivers still not working. I think its a driver problem how to reset drivers in Windows 10 machine
Click to expand...
Click to collapse
It's same as you do in other Windows, go to "Device Manager" you will find device related name in that Tree,
Uninstall it and update again..
____Mdd said:
It's same as you do in other Windows, go to "Device Manager" you will find device related name in that Tree,
Uninstall it and update again..
Click to expand...
Click to collapse
Tried that but didn't worked
Robinson#2 said:
Tried that but didn't worked
Click to expand...
Click to collapse
Is it same computer that you used to unlock?
Had it worked to get unlock data and for unlocking..?
____Mdd said:
Is it same computer that you used to unlock?
Had it worked to get unlock data and for unlocking..?
Click to expand...
Click to collapse
Yes it's the same computer I used to unlock bootloader and flashed stock nougat with fastboot method 3 months back.
Robinson#2 said:
Yes it's the same computer I used to unlock bootloader and flashed stock nougat with fastboot method 3 months back.
Click to expand...
Click to collapse
If installing drivers again, use of different USB port, different data cable don't work then better to use different PC..
____Mdd said:
If installing drivers again, use of different USB port, different data cable don't work then better to use different PC..
Click to expand...
Click to collapse
I am going to try with a bootable pendrive with linux mint.
Robinson#2 said:
Tried with ADB drivers still not working. I think its a driver problem how to reset drivers in Windows 10 machine
Click to expand...
Click to collapse
If you're on Windows 10 with an UEFI firmware, I recall you need to disable driver signature enforcement if you wish to use fastboot. Credit to: https://forum.xda-developers.com/showpost.php?p=70792544&postcount=2028
Hopefully it'll work with the Linux distro though
echo92 said:
If you're on Windows 10 with an UEFI firmware, I recall you need to disable driver signature enforcement if you wish to use fastboot. Credit to: https://forum.xda-developers.com/showpost.php?p=70792544&postcount=2028
Hopefully it'll work with the Linux distro though
Click to expand...
Click to collapse
This was very helpful. Took me hours to find it but glad I did. On to step 2. lol How I was able to fix not being able to load anything in fastboot was this.
1. I right clicked on the Motorola_Mobile_Drivers_64bit.msi and selected uninstall. Repair did nothing.
2. Rt click view properties of Motorola_Mobile_Drivers_64bit.msi.
3. On the general tab I noticed it was blocked so I unblocked it.
4. Then switched to Compatibility tab.
5. Selected run compatibility mode, any previous version of windows.
--This stops the version checker
6. Hit apply save and ran it.
MrTwigglesworth said:
This was very helpful. Took me hours to find it but glad I did. On to step 2. lol How I was able to fix not being able to load anything in fastboot was this.
1. I right clicked on the Motorola_Mobile_Drivers_64bit.msi and selected uninstall. Repair did nothing.
2. Rt click view properties of Motorola_Mobile_Drivers_64bit.msi.
3. On the general tab I noticed it was blocked so I unblocked it.
4. Then switched to Compatibility tab.
5. Selected run compatibility mode, any previous version of windows.
--This stops the version checker
6. Hit apply save and ran it.
Click to expand...
Click to collapse
Bro i didi not detecting please help
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?