[GUIDE] Unlock/Lock Nexus S Bootloader - Nexus S General

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?

Related

[GUIDE] Unlock bootloader for Nexus S

[*] shutdown the phone
[*]hold down volume up + power
[*]Now you are in the standard recovery mode
[*]assuming you have 2.3 SDK installed with fastboot (Google around for that info..), now on terminal/windows
or Windows cmd depending on OS type "fastboot devices" to check your device can be seem via USB
[*]assuming you device is seen via fastboot devices, now type "fastboot oem unlock"
[*]accept...and new bootloader is unlocked...
[*]now we need a custom recovery from clockworkmod or amon_ra, and we'll be good to go
Credit goes to gandalf44
Seems like a lot of people are having issues with the amd64 driver from the 2.3 SDK. Here's a workaround:
Go to the PdaNet homepage and download the Windows 7 x64 version of the PC software Download PdaNet
Make sure your phone is not connected to the computer. Install the app from PdaNet. Ignore the warning about HTC sync if you get it, that doesn't matter for what we're doing.
At the end of the PdaNet install, you'll be prompted to connect your phone. Make sure USB debugging is on, and connect to a high speed (as in not through a hub) USB port.
Follow the prompts and accept the unverified driver warning. Let it finish, then reboot your phone into fastboot mode -- power off, then hold volume UP and power.
Open the device manager in Windows (right click My Computer, properties, choose Device Manager from the list on the left.
Find the Android 1.0 entry, with the yellow exclamation mark beside it. Right click and choose to update the driver.
Select to search your computer for the driver manually, and point it at C:\Program Files (x86)\PdaNet for Android\. You will see a warning about an unknown/unsigned driver for sure this time, accept it.
When it finishes, at the command prompt (in the sdk\tools\ directory) type
Code:
fastboot devices
you should now see your Nexus S listed.
Credit to Gbhil
Thank you for this information
So easy??? Lol!!! The only reason i asume somebody could take that phone is this...
The really OPEN SOURCE ....
That was easy and fast.
We can't flash files through the stock recovery?
I dont understand..I did everything you stated but I dont get the option to type anything.
just a fyi. fastboot oem lock will relock the bootloader!!
pimpkogan69 said:
I dont understand..I did everything you stated but I dont get the option to type anything.
Click to expand...
Click to collapse
You need to type it into the command prompt on the computer, not on your phone.
Any way to root without doing this?
someone help please before i lose my mind...
Downloaded sdk 2.3 and usb drivers. Updated drivers works in windows fine but at boot-loader screen usb wont work and in device manager it shows android 1.0 driver needed
im lost drivers i downloaded threw SDK manager wont go im not sure if im supposed to force a driver?
im on win7x64
Jr33 said:
just a fyi. fastboot oem lock will relock the bootloader!!
Click to expand...
Click to collapse
Can anyone confirm this? This would be freakin awesome!
You just unlocked the bootloader, this didn't root the device. You need to get a custom recovery
demo23019 said:
someone help please before i lose my mind...
Downloaded sdk 2.3 and usb drivers. Updated drivers works in windows fine but at boot-loader screen usb wont work and in device manager it shows android 1.0 driver needed
im lost drivers i downloaded threw SDK manager wont go im not sure if im supposed to force a driver?
im on win7x64
Click to expand...
Click to collapse
if you are in fastboot mode right cick on android 1.0 and update manually choose the driver and select android bootloader interface. good luck
Pierrot94200 said:
You just unlocked the bootloader, this didn't root the device. You need to get a custom recovery
Click to expand...
Click to collapse
Technically, it's not rooted, but in essence, we all know that once the bootloader is unlocked, we can fastboot flash a custom recovery. And from there, we can flash custom roms or just the su and superuser.apk into the stock rom from recovery. So yea, it is kind of rooted.
DOHCtor said:
Can anyone confirm this? This would be freakin awesome!
Click to expand...
Click to collapse
I can confirm that fastboot oem lock does re-lock it.
crazifyngers said:
if you are in fastboot mode right cick on android 1.0 and update manually choose the driver and select android bootloader interface. good luck
Click to expand...
Click to collapse
yea just found it thanks
Seems I can't update my Android 1.0 device driver.... I've updated everything in my SDK 2.3 but keep getting this ... Hmmmm
demo23019 said:
someone help please before i lose my mind...
Downloaded sdk 2.3 and usb drivers. Updated drivers works in windows fine but at boot-loader screen usb wont work and in device manager it shows android 1.0 driver needed
im lost drivers i downloaded threw SDK manager wont go im not sure if im supposed to force a driver?
im on win7x64
Click to expand...
Click to collapse
had same problem use this link
http://forum.xda-developers.com/showpost.php?p=6819751&postcount=4
Yes you need to force the driver install
Pierrot94200 said:
You just unlocked the bootloader, this didn't root the device. You need to get a custom recovery
Click to expand...
Click to collapse
Well once a custom recovery is available then the puzzle is complete.

[Fixed] Can't unroot nexus

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

[Q] Used fastboot oem-off-mode charge 0, now won't charge

So I am installing the Nexus 7 in my car as the head unit, but am now stuck with this issue.
I unlocked, and rooted the device, and used the fastboot oem off-mode-charge 0 command and it worked.
Anytime the Nexus 7 receives power it turns on.
However the device battery died completely and now when I plug it in to charge, the screen stays black, buttons do nothing, and eventually it boots up, but immediatley powers off as the battery is at 0 % and has the red ! mark.
I can't even use the fastboot command to reverse it since the device can't stay on.
What the heck can I do?
Type the reverse command and it will say "waiting for device". Connect your device and booting into bootloader even for a split second should push the command.
Username invalid said:
Type the reverse command and it will say "waiting for device". Connect your device and booting into bootloader even for a split second should push the command.
Click to expand...
Click to collapse
That's what I thought and I tried it, but nothing happened. It stayed in bootloader for about a minute but the command prompt stayed at waiting for device.
I'm not 100% sure but I think I used Nexus Root Toolkit to go back to the stock rom, which would have unrooted the device.
Which also means debugging is not active.
Does it need to be rooted and debug active to be able to push?
I know the bootloader still says unlocked.
@Username invalid
Yes, but will the command be executed before the device dies again?
---------- Post added at 09:46 AM ---------- Previous post was at 09:44 AM ----------
When you're in bootloader, you don't need debugging enabled since the fastboot protocol comes into play, not ADB (which requires debugging to be enabled). Root is also unnecessary. At least that's what I have learnt in the past 5 months I have had this.
Jeremi1023 said:
That's what I thought and I tried it, but nothing happened. It stayed in bootloader for about a minute but the command prompt stayed at waiting for device.
I'm not 100% sure but I think I used Nexus Root Toolkit to go back to the stock rom, which would have unrooted the device.
Which also means debugging is not active.
Does it need to be rooted and debug active to be able to push?
I know the bootloader still says unlocked.
Click to expand...
Click to collapse
No, you do not need be rooted or have USB debugging enabled to use Fastboot. What Android Bootloader Interface driver version do you have installed on your computer? Did you check by typing "fastboot devices" if your device is being recognized?
sgt. meow said:
@Username invalid
Yes, but will the command be executed before the device dies again?
Click to expand...
Click to collapse
There is not enough time for me to set debugging on before the device dies. It stays on for maybe 5 seconds at the home screen then powers off.
Is there a way I could charge the battery a little bit bypassing the Nexus?
Can I splice in the pos and neg of the usb charger to the pos and neg of the battery?
I'd highly discourage the battery direct charging bit.
Username invalid said:
No, you do not need be rooted or have USB debugging enabled to use Fastboot. What Android Bootloader Interface driver version do you have installed on your computer? Did you check by typing "fastboot devices" if your device is being recognized?
Click to expand...
Click to collapse
I'm not sure at all.
I used the R3 Nexus 7 Superboot to push the original command. I had downloaded fastboot from somewhere else, and put it in the Superboot folder to get it to push the command.
By the way sorry for taking so long to reply in between. Since I am a new user, I have to wait the 5 minutes in between posts.
Jeremi1023 said:
That's what I thought and I tried it, but nothing happened. It stayed in bootloader for about a minute but the command prompt stayed at waiting for device.
I'm not 100% sure but I think I used Nexus Root Toolkit to go back to the stock rom, which would have unrooted the device.
Which also means debugging is not active.
Does it need to be rooted and debug active to be able to push?
I know the bootloader still says unlocked.
Click to expand...
Click to collapse
Since your device was able to stay in bootloader for a minute, did you check if it was being recognized by your computer?
Username invalid said:
Since your device was able to stay in bootloader for a minute, did you check if it was being recognized by your computer?
Click to expand...
Click to collapse
I am assuming it was, as Windows chimed in as soon as the device had enough juice to turn on.
Jeremi1023 said:
I am assuming it was, as Windows chimed in as soon as the device had enough juice to turn on.
Click to expand...
Click to collapse
Try booting into bootloader again then typing "fastboot devices". Also go to your computer Device Manager > Android Devices > Android Bootloader Interface > Properties.
Username invalid said:
Try booting into bootloader again then typing "fastboot devices". Also go to your computer Device Manager > Android Devices > Android Bootloader Interface > Properties.
Click to expand...
Click to collapse
I will do that and let you know what I see.
Just gotta wait for the thing to turn on. It's very random right now.
Okay, I was able to get into bootloader, and I I did "fastboot devices" and nothing came up.
Also checked device manager and no Android or anything like it in there.
Username invalid said:
Try booting into bootloader again then typing "fastboot devices". Also go to your computer Device Manager > Android Devices > Android Bootloader Interface > Properties.
Click to expand...
Click to collapse
I see that it is coming up as unknown device under the USB section
I have tried the Nexus toolkit guide for installing the drivers to no avail.
When I try to update the drivers for "unknown device" and go to the path where they are, windows said the best drivers are already installed.
Jeremi1023 said:
I see that it is coming up as unknown device under the USB section
I have tried the Nexus toolkit guide for installing the drivers to no avail.
When I try to update the drivers for "unknown device" and go to the path where they are, windows said the best drivers are already installed.
Click to expand...
Click to collapse
http://d-h.st/kDu
Username invalid said:
http://d-h.st/kDu
Click to expand...
Click to collapse
Even with those drivers, Windows still says the best ones are installed and refuses to use them.
Jeremi1023 said:
Even with those drivers, Windows still says the best ones are installed and refuses to use them.
Click to expand...
Click to collapse
Uninstall your current one first.
Username invalid said:
Uninstall your current one first.
Click to expand...
Click to collapse
What I have done is use Nexus Toolkit to uninstall, like it says, anything having to do with nexus, google, samsung, etc. I reboot the computer, wait for the tablet to turn on for a few seconds and then windows chimes in and says the usb device malfunctioned and could not be installed. It shows up in device manager as Unknown Device, and when I try to update the drivers, it says they are updated and won't use the ones I chose.
Have I not fully uninstalled the old ones?
Jeremi1023 said:
What I have done is use Nexus Toolkit to uninstall, like it says, anything having to do with nexus, google, samsung, etc. I reboot the computer, wait for the tablet to turn on for a few seconds and then windows chimes in and says the usb device malfunctioned and could not be installed. It shows up in device manager as Unknown Device, and when I try to update the drivers, it says they are updated and won't use the ones I chose.
Have I not fully uninstalled the old ones?
Click to expand...
Click to collapse
I'm not sure. I stopped using the toolkit and do pretty much everything I need now through ADB. Do you have another computer you can use?
Username invalid said:
I'm not sure. I stopped using the toolkit and do pretty much everything I need now through ADB. Do you have another computer you can use?
Click to expand...
Click to collapse
Yeah I have a desktop I could try it on.
I've never plugged the Nexus in to the desktop, so it should be a complete clean install of drivers.
If Windows recognizes the nexus on the desktop, what should I do?
Do I need to uninstall anything it may install on its own?
I figure I will end up installing the drivers you previously provided.

Cannot get past "adb devices" command line

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!

[HELP]Device not detecting in fastboot mode

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

Categories

Resources