This is how you unlock the bootloader (warning!!!! This will erase everything you have on your device!)
1. adb reboot fastboot
2. fastboot oem unlock(x2. It will prompt you to enter it again to confirm)
Awesome. First thing I'm going to do out of the box.
Sent from my Oneplus One with Tapatalk Pro.
peppy6582 said:
This is how you unlock the bootloader (warning!!!! This will erase everything you have on your device!)
1. adb reboot fastboot
2. fastboot oem unlock(x2. It will prompt you to enter it again to confirm)
Click to expand...
Click to collapse
And don't forget, to put device in fastboot, press and hold button that is located on the bottom of the player, plug in the power cord and hold until led light flashes repeatedly.
Fastboot
On Ubuntu, ADB is not ever seeing my NP. I can get it in fastboot mode with the button, and my USB devices enumerate (2 different ones), but ADB never shows it connected.
Code:
[376711.228958] usb 3-2.4: new high-speed USB device number 12 using xhci_hcd
[376711.246426] usb 3-2.4: New USB device found, idVendor=18d1, idProduct=4ee0
[376711.246436] usb 3-2.4: New USB device strings: Mfr=2, Product=3, SerialNumber=4
[376711.246441] usb 3-2.4: Product: fugu
[376711.246445] usb 3-2.4: Manufacturer: Android
[376711.246450] usb 3-2.4: SerialNumber: 13737740
[376772.269599] usb 3-2.4: USB disconnect, device number 12
[376773.252023] usb 3-2.4: new high-speed USB device number 13 using xhci_hcd
[376773.282912] usb 3-2.4: New USB device found, idVendor=8086, idProduct=0a2c
[376773.282919] usb 3-2.4: New USB device strings: Mfr=2, Product=1, SerialNumber=3
[376773.282923] usb 3-2.4: Product: MOOREFIELD
[376773.282926] usb 3-2.4: Manufacturer: INTEL
[376773.282943] usb 3-2.4: SerialNumber: <redacted>
Ahh, I forgot I had to enable USB debugging in the developer menu. The dev menu is enabled by clicking "Build" a handful of times from the "About" menu.
figured it out : windows , device manager , let me choose driver , selected ADB TESTING INTErFACE , all is good. hope this helps others,.
================================================================================================================
using windows 8 , holding down bottom button i get to fastboot , when i run "fastboot devices" i get nothing , when run adb devices i get " emulator-5554 device " ( that was bluestacks ) i had to end task . but still no luck. when i run "fastboot devices" i get nothing , when run adb devices i get nothing
i double checked developer mode , all good , windows 8 calls it FUGU , , in control panel . if i run 'fastboot oem unlock" all i get is "waiting for device "
what step did i miss? any help appreciated./.
I have the same problems running Linux Mint 17.
"adb shell" works OK when booting normally.
"sudo fastboot devices" shows nothing in bootloader/fastboot mode, and no other fastboot commands work. Also see:
<6>[84128.968111] usb 1-5: new high-speed USB device number 55 using ehci-pci
<6>[84129.106293] usb 1-5: New USB device found, idVendor=18d1, idProduct=4ee0
<6>[84129.106305] usb 1-5: New USB device strings: Mfr=2, Product=3, SerialNumber=4
<6>[84129.106313] usb 1-5: Product: fugu
<6>[84129.106319] usb 1-5: Manufacturer: Android
<6>[84129.106324] usb 1-5: SerialNumber: DA4D....
I'm itching for root to explore more.
fastboot problem is due to need for new fastboot.
I've attached the Linux version in my updated SDK. Windows version is in SDK on Google site somewhere I guess.
Just thought that I'd point out that holding down the button on the bottom of the device while plugging in will load the bootloader...just another way to get there is all.
bsara said:
Just thought that I'd point out that holding down the button on the bottom of the device while plugging in will load the bootloader...just another way to get there is all.
Click to expand...
Click to collapse
And one that doesn't require a working adb connection first.
Device not found
Trying to unlock Nexus Player but getting error, device not found. I enable USB debugging in the Developer menu and turn on developer by hitting Build in About menu.
I am using a windows 7 computer and i get the following when i try to unlock,
C:\Program Files\Android\android-sdk\platform-tools>adb reboot fastboot
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
C:\Program Files\Android\android-sdk\platform-tools>adb reboot fastboot
error: device not found
C:\Program Files\Android\android-sdk\platform-tools>
dreadprinz said:
Trying to unlock Nexus Player but getting error, device not found. I enable USB debugging in the Developer menu and turn on developer by hitting Build in About menu.
I am using a windows 7 computer and i get the following when i try to unlock,
C:\Program Files\Android\android-sdk\platform-tools>adb reboot fastboot
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
C:\Program Files\Android\android-sdk\platform-tools>adb reboot fastboot
error: device not found
C:\Program Files\Android\android-sdk\platform-tools>
Click to expand...
Click to collapse
The command is "adb reboot-bootloader" not "fastboot"
Also, double check that you have the latest platform tools installed from the SDK manager.
Just go straight into the bootlloader by holding the button as you plug it in, then wait for the light as BSaras post states . No driver needed
volwrath said:
Just go straight into the bootlloader by holding the button as you plug it in, then wait for the light as BSaras post states . No driver needed
Click to expand...
Click to collapse
Very good point...though you will still need the latest version of the android SDK platform tools for fastboot to detect the player.
bsara said:
Very good point...though you will still need the latest version of the android SDK platform tools for fastboot to detect the player.
Click to expand...
Click to collapse
I don't think so.
I haven't upgraded mine in quite a while and fastboot had no problem seeing the player. I am updating my sdk platform tools as we speak.
But then again I guess they are fairly new since I updated them to play with my google watch
Device not found
I tried the command "adb reboot-bootloader" still got error device not found .
I think i have the latest platform tools Revision 23.0.5.
Try this:
After you unlock Developer options,
Go into Developer options
You will see "Enable OEM unlock" make sure that is checked then you should be able to proceed
vitald2 said:
Try this:
After you unlock Developer options,
Go into Developer options
You will see "Enable OEM unlock" make sure that is checked then you should be able to proceed
Click to expand...
Click to collapse
Hmm I don't see Enable oem unlock anywhere.
vitald2 said:
Try this:
After you unlock Developer options,
Go into Developer options
You will see "Enable OEM unlock" make sure that is checked then you should be able to proceed
Click to expand...
Click to collapse
Maybe i am missing something here, but i don't see "Enable OEM unlock" anywhere.
dreadprinz said:
I tried the command "adb reboot-bootloader" still got error device not found .
I think i have the latest platform tools Revision 23.0.5.
Click to expand...
Click to collapse
You've listed the version of you "Android SDK Tools" not the "Android SDK Platform-tools" (which is found right below it in the SDK manager). At any rate, you probably are having a driver issue (I'm assuming that you're using Windows). I personally can't help you much there since I use Ubuntu, but this tool for Nexus devices might help: http://www.wugfresh.com/nrt. I know that the Player isn't listed there...but with that tool you can install the generic drivers...perhaps it will fix things for you.
Also, as stated before, you can (for the time being) just hold down the button on the bottom of the device while you plug in the device and it will boot into the bootloader (I.E. fastboot mode). Then run "fastboot devices" to see if anything shows up, if not...I would keep looking into the driver instructions on the tool I listed above. Also, to ensure that adb is seeing your device, you can also run "adb devices". Also, make sure that no other android devices that have USB debugging enabled are plugged in while you run your command, otherwise it won't succeed because it won't know which device to pick...or just run "adb -s [DEVICE_ID] reboot-bootloader" where [DEVICE_ID] is the id listed when running adb devices. Good luck.
And that "Enable OEM unlock" stuff is not true...just ignore it. Once in fastboot, you'll just need to run "fastboot oem unlock" twice in a row for the unlock to occur.
Related
Ok, total noob here. I've been trying to get CWM on my TF700. I have Windows7 64 bit. I plug in either the tablet alone or docked, using any combination of USB2.0 dedicated charge/comm cable, USB3.0 dedicated charge/Comm cable and usb 2.0 and usb3.0 ports. The computer finds the "fastboot device" (usb2.0 port) or the AsUsTeK Fastboot device (USB3.0 port). It shows up in my devices list as an unknown type, but the drivers appear to be loaded correctly since the computer sees the devices and calls it the "Fastboot Device". I've tried the "ADB devices" and the "Fastboot Devices" commands but my tablet is never found (the command never returns the device string) and issuing the fastboot command to flash the CWM recovery just sits there waiting for the device. I'm lost. Can anyone give me a clue?
SDK
Washedman said:
Ok, total noob here. I've been trying to get CWM on my TF700. I have Windows7 64 bit. I plug in either the tablet alone or docked, using any combination of USB2.0 dedicated charge/comm cable, USB3.0 dedicated charge/Comm cable and usb 2.0 and usb3.0 ports. The computer finds the "fastboot device" (usb2.0 port) or the AsUsTeK Fastboot device (USB3.0 port). It shows up in my devices list as an unknown type, but the drivers appear to be loaded correctly since the computer sees the devices and calls it the "Fastboot Device". I've tried the "ADB devices" and the "Fastboot Devices" commands but my tablet is never found (the command never returns the device string) and issuing the fastboot command to flash the CWM recovery just sits there waiting for the device. I'm lost. Can anyone give me a clue?
Click to expand...
Click to collapse
You have downloaded the sdk from google yes??Put the .exe is the right place??Opened you CMD window with admin rights???
lj50036 said:
You have downloaded the sdk from google yes??Put the .exe is the right place??Opened you CMD window with admin rights???
Click to expand...
Click to collapse
To the best of my knowledge (slim, I AM a noob, after all) I would say yes to all the above. The only thing I would question would be which .exe and which place? I still have a problem with reading peoples minds...
fastboot/adb
Washedman said:
To the best of my knowledge (slim, I AM a noob, after all) I would say yes to all the above. The only thing I would question would be which .exe and which place? I still have a problem with reading peoples minds...
Click to expand...
Click to collapse
Fastboot.exe/adb.exe in the root of your local hard drive
lj50036 said:
Fastboot.exe/adb.exe in the root of your local hard drive
Click to expand...
Click to collapse
No, I didn't place them in the root. I created a folder in the root called Android (for the ADB files) and Fastboot for the fastboot files. I opened the command line and CD to the appropriate folder for the fastboot. For the ADB.exe, I added a path statement in the environment variables as suggested. I can type in either command and the computer will recognize it and give the all the command structure, so I would assume that is operating correctly, yes?
Washedman said:
No, I didn't place them in the root. I created a folder in the root called Android (for the ADB files) and Fastboot for the fastboot files. I opened the command line and CD to the appropriate folder for the fastboot. For the ADB.exe, I added a path statement in the environment variables as suggested. I can type in either command and the computer will recognize it and give the all the command structure, so I would assume that is operating correctly, yes?
Click to expand...
Click to collapse
Yes that is great. With the tablet in fasboot mode type
fastboot devices what is the outcome of this
lj50036 said:
Yes that is great. With the tablet in fasboot mode type
fastboot devices what is the outcome of this
Click to expand...
Click to collapse
Nothing. It returns no string, letters or numbers. Blank. I tried every combination of ports and cables and drivers. Getting a bit frustrated.
I had a similar problem with flashing a custom recovery on the tf700 as well (mainly because of the dock), so let me share with you a few pointers that may help you fix this (it certainly helped in my case):
1. Never do any flashing, adb or fastboot with the tablet docked, especially when flashing recovery: I spent three hours scratching my head figuring out why I couldn’t flash the recovery (fastboot stuck at sending file), only to find out that everything worked perfectly when I removed the dock. In my opinion, the dock makes things unpredictable, so do everything with the dock.
2. As for adb and fastboot, you should just start setting up from scratch as it is always easier than troubleshooting for errors. After unlocking the bootloader using ASUS tool, what I suggest you should do are as below:
a. Uninstall COMPLETELY your current adb/fastboot drivers and install Universal Naked Driver 0.73 (http://forum.xda-developers.com/showthread.php?t=2513339). Take note of the warning in red on how to uninstall existing adb driver.
b. Also take note that you actually need 2 sets of drivers, 1 for adb and 1 for fastboot (which are both included in the Universal Naked Driver). When you connect your tablet with Android running to your PC, you are installing driver for adb. With the driver properly installed, “adb devices” command will work and give you the list of connected devices to your PC through Windows’ CMD. Please also Google or search xda for adb files (no need to download the whole Android SDK just to get those adb files).
c. After successfully installing adb driver, you can manually reboot your tablet into fastboot mode through the button combo (power + volume down) with the tablet still connected to your PC. By then, your Device Manager should have another device listed as fastboot device. Again, follow the steps in the link to uninstall and reinstall fastboot driver. With this set up, you should be able to run “fastboot devices” command.
d. With fastboot, you can now flash a custom recovery. As a side note, since all this flashing custom recovery and ROM can potentially brick your tablet, after you have finished fixing adb/fastboot and get your ROM running, I strongly suggest you follow this link to obtain nvflash (http://forum.xda-developers.com/showthread.php?t=2455925) and make your tablet unbrickable. I actually did this before flashing a custom ROM, but I honestly don’t know if the timing makes any difference.
So after a lot of headache and messing with drivers, 3 machines, 1 grumpy wife and staying up until 4am. I figured the issue wasn't the drivers. But the version of ADB and Fastboot which I was trying to use. That and the USB hub I was trying to go through.
The way I solved the issue was to install the tools and drivers from the following thread and to plug directly into a USB port rather than a USB hub:
http://forum.xda-developers.com/showthread.php?t=2588979
On the "Any root ability for this phone" thread there have been instructions to unlock the bootloader spread over several pages of posts. I've collected them here (and followed this set of steps to unlock mine):
(1) Get/install Alcatel USB driver if Windows. (no need for Mac). From here:
http://54.247.87.13/softwareupgrade/Driver/ALCATEL_ADB_ Driver Qualcomm_ADB.rar
(2) Set USB debugging on in Developer settings (if these are not exposed, go to Settings/About Phone/Build number, and tap 7 times.)
(3) Plug in USB cable to phone and computer. Tap on USB icon in notifications panel; select MTP (file transfer) mode. ADB seems to recognize phone in either MTP or PTP mode; I don’t know if PTP mode will also work..
(4) "adb reboot-bootloader" to reboot into bootloader; then
(5) "fastboot -i 0x1bbb devices" should show the device (may need “sudo” in front of fastboot for linux).
"fastboot -i 0x1bbb oem device-info" shows device info including bootloader status (e.g. locked).
(6) "fastboot -i 0x1bbb oem unlock" to unlock the bootloader; after this you should get, for device info,
Device unlocked: true
(7) To reboot normally: "fastboot -i 0x1bbb reboot"
Putting the phone into "cdrom mode" which is one of the 4 choices along with mtp, ptp etc will cause the phone to mount like a cd and it provides the needed alcatel usb drivers for windows without a need for downloading anything.
Ubuntu based linux users will need to install the packages android-tools-adb and android-tools-fastboot.
famewolf said:
Putting the phone into "cdrom mode" which is one of the 4 choices along with mtp, ptp etc will cause the phone to mount like a cd and it provides the needed alcatel usb drivers for windows without a need for downloading anything.
Ubuntu based linux users will need to install the packages android-tools-adb and android-tools-fastboot.
Click to expand...
Click to collapse
Thanks for that clarification. And I can add that Mac users can get adb and fastboot from Google's android studio site, developer.android.com/tools/studio/, and as noted in the o.p., no special usb driver is needed.
As the title says.
I'm trying to unlock the bootloader on my XZs so I can root it.
My device is listed normally when turned on w/ the command window, but in fastboot mode it disappears and when I try a command, an error comes up saying ""error: no device/emulator found". (see attached image)
As far as I'm concerned, I have all the necessary drivers, I've tried on another PC, the result is always the same.
And when I try to change the drivers (Via Device Manager>Update Driver>Browse My Computer...>Let me pick...>Have Disk...)
I get yet another error saying "The folder you specified doesn't contain a compatible software driver for your device..."
Can someone please give me a solution. This has been asked before on XDA by someone else (that thread has no replies). It seems it's always us little guys with actual problems which need solving who get little to no help at all here.
Reinstall driver again.
It doesn't work. The problem is I want to install the Google USB drivers for my Xperia phone but Windows 10 will not let me and driver signing seems to be impossible to disable (currently typing this on my laptop while it's in test mode).
1. Turn off your phone. Boot in to fastboot mode and plug the cable. After your heard the sound from the computer for new device found. Go to device manager look to usb S1 device. Reinstall driver by manual choose (do not search) from the menu with the name is Android Google. When prompt for install. Choose install anyway. After successful install driver, please check status from flashtool to make sure your device show connected in fastboot.
2. Change the usb port. Sometimes you get problem with usb port 2.0 and 3.0
Hope you can fix it asap.
Nothing by the name of 'Android Google' appears in the menu when selecting new drivers.
I clicked on 'S1boot Fastboot' under 'other devices' in Device Manager and clicked on update driver
>Browse Computer
>Let me pick
- and then there's something similar called 'Android Device' but no 'Android Google' so I click on that
- then I get three options:
Android ADB Interface Version 11.0.0.0
Android Bootloader Interface Version 11.0.0.0
Android Composite ADB Interface Version 11.0.0.0
None of them worked when I tried.
I think the solution is to have the phone on, with USB debugging enabled, connect via USB to PC, test your adb devices again, if all good, go ahead and
Rich (BB code):
adb reboot fastboot
This is because some phones use Fastbootd (notice the d..).
Just got a pixel 3a, it's running android 9. I want to unlock the bootloader. I'm following one of the popular root guides on this forum. I can't seem to get adb or fastboot to find my device.
Installed ADB applications from https://developer.android.com/studio/releases/platform-tools.html
Turned on developer options in phone, turned on USB debugging, plugged in phone.
Wasn't prompted for device authorization from phone.
Changed USB connection mode to PTP.
I have tried all USB connection modes, I verified the cable used to connect the pc to the pone is a data cable as I can transfer data when the phone usb mode is set to file transfer, ptp, or midiInstalled adb/phone device driver using https://developer.android.com/studio/run/win-usb
Still no debugging authorization prompt, but device manager lists the phone under 'Android Device' as 'Android Composite ADB Interface'.
'adb devices' doesn't list anything, tried 'adb kill-server', 'adb start-server', and 'adb usb'
'adb devices' doesn't list anything
reboot phone into fastboot by shutting down and holding power+volDown
'fastboot devices' doesn't list anything
Rebooted my pc, rebooted the phone, retried everything.
I'm at a loss, any suggestions?
Yea I've had some issues with adb/fastboot on windows as well. Sometimes it just won't detect the device, rebooting into my Linux install finds it instantly though. I haven't looked into how to fix it yet though as I can always just reboot to Linux. If you're on a version of windows that supports WSL, perhaps you should try that?
Sent from my Google Pixel 3a XL using XDA Labs
I have LE2110. In Settings I've enabled "OEM Unlocking" and also "USB Debugging".
I also instsalled the proper USB drivers but think they are unecessary regardless.
I boot into Fastboot & connect to laptop withofficial USB cable.
From the folder where I installed Android SDK Platform Tools I open command prompt.
Type in fastboot oem unlock and it says 'waiting for devices'.
I've rebooted everything, tried a few times over several days but always same result.
Phone works perfect, no issues otherwise.
Any tips what to try next or possibly what I'm doing wrong?
Thank you
I have a global unlocked 9. I had to use this to unlock bl. Open your command window from this after it installs,make sure to add shortcut to desktop when installing. Then run unlock command. Worked for me back in April when I bought device.
"minimal_adb_fastboot_v1.4.3_setup.exe | by shimp208 for Utilities" https://androidfilehost.com?fid=746010030569952951
For me, I installed every driver while being in testsigning on ("bcdedit /set testsigning on" in cmd as administrator then reboot) and then I rebooted, turned testsigning off, rebooted again then it worked.
100 percent driver issue. Just reinstall the correct drivers and you'll be good to go.
Can you try to install this app on your computer and then try? pdanet this installs also the drivers for your phone. Otherwise try searching on the forum for the correct drivers.
Before any command you should try and see if your device is connected by doing in command prompt: fastboot devices
dotuletz said:
Can you try to install this app on your computer and then try? pdanet this installs also the drivers for your phone. Otherwise try searching on the forum for the correct drivers.
Before any command you should try and see if your device is connected by doing in command prompt: fastboot devices
Click to expand...
Click to collapse
Plus you can reboot edl through adb.