Database Info

Unlock Nexus Player

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.

Unlocking the bootloader on the Alcatel Idol 3

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.

Unlock 6.0 Bootlader

I downloaded adb-fastboot-latest_win_linux.zip. Using Ubuntu 12.04, unziped ”adb” and “fastboot”. Went to terminal and change directory to where adb” and “fastboot” where placed. I had no issues with ADB commands, however, I never got a reply from the following command:
Code:
ADB$ fastboot oem get_unlock_data
< waiting for device >
Have not tried from Windows yet. I know there were some issues with MTP after the 6.0 update and my version of Linux (MTP supported on Ubuntu v13 and above). Not sure if this is the issue since ADB commands seemed to work. Any recommendations?
Update: No issue using Windows

MrTooPhone said:
I downloaded adb-fastboot-latest_win_linux.zip. Using Ubuntu 12.04, unziped ”adb” and “fastboot”. Went to terminal and change directory to where adb” and “fastboot” where placed. I had no issues with ADB commands, however, I never got a reply from the following command:
Code:
ADB$ fastboot oem get_unlock_data
< waiting for device >
Have not tried from Windows yet. I know there were some issues with MTP after the 6.0 update and my version of Linux (MTP supported on Ubuntu v13 and above). Not sure if this is the issue since ADB commands seemed to work. Any recommendations?
Update: No issue using Windows
Click to expand...
Click to collapse
Did you execute 'adb reboot bootloader' first? All fastboot command need to be executed with the device in fastboot mode, and need su (sudo) privileges.

In addition to the above, by not prepending './' to your command, you were calling a(n apparently available) system-wide installation that might have been too old to detect the device. It would also help if you would post an lspci so we could see if the device is at least in the correct mode.

acejavelin said:
Did you execute 'adb reboot bootloader' first? All fastboot command need to be executed with the device in fastboot mode, and need su (sudo) privileges.
Click to expand...
Click to collapse
I did 'adb reboot bootloader first, however, I did not do "su" for fast boot command. So "adb" command does not require "su"? I will try "su" fastboot command later and report back.

MrTooPhone said:
I did 'adb reboot bootloader first, however, I did not do "su" for fast boot command. So "adb" command does not require "su"? I will try "su" fastboot command later and report back.
Click to expand...
Click to collapse
Correct, add doesn't require su, fastboot does.
Sent from my MotoG3 using Tapatalk

acejavelin said:
Correct, add doesn't require su, fastboot does.
Sent from my MotoG3 using Tapatalk
Click to expand...
Click to collapse
Tried again with Linux. SU did the trick. Thanks.

Fastboot Issues with Nokia 3

Hey guys, I’ve been trying to turn my old Nokia 3 into a LineageOS device for the last week, mainly as a test before I try it on my main device (a Nokia 8), but I’m not having any luck. I’m trying to follow the steps as described on the board here. While I did have great success installing LOS on an old Samsung Galaxy S5 Neo following the guide on the wiki (wiki.lineageos.org/devices/s5neolte/install), the Nokia 3 is just not having it and I’m running out of ideas. So much for an introduction, let’s get into it …
The device:
Nokia 3—“TA-1020”
Android Version: 8.1.0
USB Debugging is turned on and my laptop has permission.
OEM Unlocking is not available/greyed out in the Dev. Options.
My Laptop:
OS: Windows 10
Nokia USB Drivers are installed.
The Nokia 3 is recognized by the Device Manager, Explorer, and adb.exe.
All commands are used via cmd as administrator from within the adb directory.
The Issues:
“adb devices” finds the device and lists it as “NE… device”—so far so good, I guess, but …
“adb reboot-bootloader” reboots the device, but it does not boot into fastboot mode and instead just reboots normally
“adb devices” after “adb reboot-bootloader” just lists it as “device” again
going into fastboot mode manually by using Power+Volume Up to get into recovery mode works; I then get a black screen with a little “=> FASTBOOT mode…” on the bottom
“adb devices” does no longer find the device, once this black fastboot screen is on
Windows finds the device and lists it in the Device Manager under “ADB Interface” » “Fastboot Device”
“fastboot devices” via cmd does not find the device, however
“fastboot oem unlock” returns “<waiting for device>” and is stuck there until I quit (I tried waiting for about 45 minutes once, but to no avail)
So here I am—stuck. Forget installing LineageOS, it seems like I can’t even unlock the OEM because the device is “invisible.” Does anyone have any suggestions? I would really appreciate the help.

blarkh said:
Hey guys, I’ve been trying to turn my old Nokia 3 into a LineageOS device for the last week, mainly as a test before I try it on my main device (a Nokia 8), but I’m not having any luck. I’m trying to follow the steps as described on the board here. While I did have great success installing LOS on an old Samsung Galaxy S5 Neo following the guide on the wiki (wiki.lineageos.org/devices/s5neolte/install), the Nokia 3 is just not having it and I’m running out of ideas. So much for an introduction, let’s get into it …
The device:
Nokia 3—“TA-1020”
Android Version: 8.1.0
USB Debugging is turned on and my laptop has permission.
OEM Unlocking is not available/greyed out in the Dev. Options.
My Laptop:
OS: Windows 10
Nokia USB Drivers are installed.
The Nokia 3 is recognized by the Device Manager, Explorer, and adb.exe.
All commands are used via cmd as administrator from within the adb directory.
The Issues:
“adb devices” finds the device and lists it as “NE… device”—so far so good, I guess, but …
“adb reboot-bootloader” reboots the device, but it does not boot into fastboot mode and instead just reboots normally
“adb devices” after “adb reboot-bootloader” just lists it as “device” again
going into fastboot mode manually by using Power+Volume Up to get into recovery mode works; I then get a black screen with a little “=> FASTBOOT mode…” on the bottom
“adb devices” does no longer find the device, once this black fastboot screen is on
Windows finds the device and lists it in the Device Manager under “ADB Interface” » “Fastboot Device”
“fastboot devices” via cmd does not find the device, however
“fastboot oem unlock” returns “<waiting for device>” and is stuck there until I quit (I tried waiting for about 45 minutes once, but to no avail)
So here I am—stuck. Forget installing LineageOS, it seems like I can’t even unlock the OEM because the device is “invisible.” Does anyone have any suggestions? I would really appreciate the help.
Click to expand...
Click to collapse
You need to have fatboot drivers to be able to see your device in fastboot. I had the same problem with it connecting to adb devices but not to fastboot devices. I downloaded the driver on this thread https://forum.xda-developers.com/no...-bootloader-nokia-3-pie-t4012285#post82382141 which also shows how to unlock the bootloader. You will not be allowed to flash lineage without unlocking the bootloader first.

Waiting for Device Error

i want to root https://www.xda-developers.com/root/
when i try
Code:
fastboot flash boot /path/to/magisk_patched.img
im stuck at
< waiting for device >
when i try
adb devies
it show my device
but when i boot to fastboot in my phone
i try
fastboot devices
didn't show fastboot devices
i use
15 seconds ADB Installer​https://www.droidthunder.com/adb-drivers/#Method_1_Using_15_seconds_ADB_Installer
what should i do ??

if youre on windows, have you installed the driver provided by your manufacturer? Or did you run command prompt as administrator?
if youre on linux, did you execute adb/fastboot with root permissions?
Also make sure you use the official plaform tools: https://developer.android.com/studio/releases/platform-tools

MLPIR said:
if youre on windows, have you installed the driver provided by your manufacturer? Or did you run command prompt as administrator?
if youre on linux, did you execute adb/fastboot with root permissions?
Also make sure you use the official plaform tools: https://developer.android.com/studio/releases/platform-tools
Click to expand...
Click to collapse
im on windows i have already install mtp driver also run cmd as admin in the platform-tools folder still not show the devices.

chatofking said:
im on windows i have already install mtp driver also run cmd as admin in the platform-tools folder still not show the devices.
Click to expand...
Click to collapse
Is your usb properly plugged in and working? (Both on the computer and phone)

yes as you can see
it work on adb devices but not fastboot devices.
Code:
D:\platform-tools>adb devices
List of devices attached
WGWWINQGT8NBJVB6 device
Code:
D:\platform-tools>fastboot devices
what should i do ??

Run this command sequence
Code:
adb devices
adb reboot fastboot
fastboot devices

xXx yYy said:
Run this command sequence
Code:
adb devices
adb reboot fastboot
fastboot devices
Click to expand...
Click to collapse
did you mean
Code:
adb reboot bootloader

xXx yYy said:
Run this command sequence
Code:
adb devices
adb reboot fastboot
fastboot devices
Click to expand...
Click to collapse
thank it worked now
it show fastboot mode instead fastboot in my phone
D:\platform-tools>fastboot devices
WGWWINQGT8NBJVB6 fastboot

can i ask one more question i got this message
when i
D:\platform-tools>fastboot flash boot D:\platform-tools/magisk_patched-25100_1VYTU.img
it show
Code:
Sending 'boot' (98304 KB) FAILED (remote: 'Download is not allowed on locked devices')
fastboot: error: Command failed
what should i do ??