Develop Bugs

[Q] [HELP] Unable to unlock bootloader in fastboot mode

Hi,
I'm trying to unlock bootloader on my GNex but unfortunately, when i reboot it in fastmode (through adb reboot-bootloader or pressing VOL- , VOL+ and POWER), the device do nothing: It shows an android with "the chest open", in the top of the it shows "START" but any button works and when i try fastboot devices command, i have no response. i try to see if there is any device connected through lsusb, but the device doesn't appears.
It seems to be stuck and the only way to reboot in normal mode is removing the battery.
Anyone could help me?
Thanks,
xekin

More info about:
This is what is shown in fastboot mode:
FASTBOOT MODE
PRODUCT NAME - tuna
VARIANT - maguro
HW VERSION - 9
BOOTLOADER VERSION - PRIMEKK15
BASEBAND VERSION - I9250XXLJ1
CARRIER INFO - NONE
SERIAL NUMBER - 1234123414341
SIGNING - production
LOCK STATE - LOCKED
How can i re-install or re-flash "fastboot mode"? I tried flashing OMAP4440 but nothing happened. I've tried to access to fastboot from win7, win8 and ubuntu. In all of them adb works correctly.

It seems that your bootloader is fine. Reinstall driver and fastboot file, and do the right unlock command.
Sent from my Galaxy Nexus using xda premium

samersh72 said:
It seems that your bootloader is fine. Reinstall driver and fastboot file, and do the right unlock command.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Read closer. OP isn't using Windows. lsusb is a Linux command - plus he stated he already tried under Windows and it worked. Under Windows, it seems OP hasn't told device manager what driver the device should use, WHEN connected in fastboot mode.
OP, search ' android udev rules' then follow instructions. And maybe you're not seeing the device under lsusb because you're not allowed to (yet). In the meantime, you can use 'sudo lsusb' to escalate permissions.
Then, install android SDK and/or update your existing versions.
Still, it's not clear, OP, do your hardware keys work? I mean, can you press up or down, and see the other options like Recovery etc?
Sent from my Nexus

bk201doesntexist said:
Read closer. OP isn't using Windows. lsusb is a Linux command - plus he stated he already tried under Windows and it worked. Under Windows, it seems OP hasn't told device manager what driver the device should use, WHEN connected in fastboot mode.
OP, search ' android udev rules' then follow instructions. And maybe you're not seeing the device under lsusb because you're not allowed to (yet). In the meantime, you can use 'sudo lsusb' to escalate permissions.
Then, install android SDK and/or update your existing versions.
Still, it's not clear, OP, do your hardware keys work? I mean, can you press up or down, and see the other options like Recovery etc?
Sent from my Nexus
Click to expand...
Click to collapse
Thanks for your responses
Actually, I did it lot of times, different drivers version (google, samsung) in diferent OS, but always the same result. In linux I checked that the properly udev config file is set:
cat /etc/udev/rules.d/51-android.rules
SUBSYSTEM=="usb", ATTR{idVendor}=="04e8", MODE="0666", GROUP="plugdev"
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", MODE="0666", GROUP="plugdev"
One for google and the other for samsung,
In bootloader, any button works, It is a bit annoying because, I watched a lot of youtube videos in which the START message changes when UP/DOWN buttons are pushed. (To recovery for example)
Now, after tested with adt included adb/fastboot commands, I'm testing with the command included in ubuntu platform (wiki.ubuntu.com/Touch/Install). But it doesn't work neither
I followed also some tutos about odin (one of them was yours), but it neither recognizes my gnex.

xekin said:
Thanks for your responses
Actually, I did it lot of times, different drivers version (google, samsung) in diferent OS, but always the same result. In linux I checked that the properly udev config file is set:
cat /etc/udev/rules.d/51-android.rules
SUBSYSTEM=="usb", ATTR{idVendor}=="04e8", MODE="0666", GROUP="plugdev"
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", MODE="0666", GROUP="plugdev"
One for google and the other for samsung,
In bootloader, any button works, It is a bit annoying because, I watched a lot of youtube videos in which the START message changes when UP/DOWN buttons are pushed. (To recovery for example)
Now, after tested with adt included adb/fastboot commands, I'm testing with the command included in ubuntu platform (wiki.ubuntu.com/Touch/Install). But it doesn't work neither
I followed also some tutos about odin (one of them was yours), but it neither recognizes my gnex.
Click to expand...
Click to collapse
anyone has this problem? i mean if there is someone who has a gnex which doesn't response when he pushes up,down buttons?it looks like frozen, and the usb doesn't seem to work

xekin said:
Thanks for your responses
Actually, I did it lot of times, different drivers version (google, samsung) in diferent OS, but always the same result. In linux I checked that the properly udev config file is set:
cat /etc/udev/rules.d/51-android.rules
SUBSYSTEM=="usb", ATTR{idVendor}=="04e8", MODE="0666", GROUP="plugdev"
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", MODE="0666", GROUP="plugdev"
One for google and the other for samsung,
In bootloader, any button works, It is a bit annoying because, I watched a lot of youtube videos in which the START message changes when UP/DOWN buttons are pushed. (To recovery for example)
Now, after tested with adt included adb/fastboot commands, I'm testing with the command included in ubuntu platform (wiki.ubuntu.com/Touch/Install). But it doesn't work neither
I followed also some tutos about odin (one of them was yours), but it neither recognizes my gnex.
Click to expand...
Click to collapse
Is your user in group "plugdev"? 'gpasswd -a <user> <group>' as root
Run fastboot with root privileges enabled

bk201doesntexist said:
Is your user in group "plugdev"? 'gpasswd -a <user> <group>' as root
Run fastboot with root privileges enabled
Click to expand...
Click to collapse
Thanks
yep, it doesn't work with my user or root. this is what i see with a dmesg when fastboot mode:
hub 2-0:1.0: connect-debounce failed, port 1 disabled
Click to expand...
Click to collapse
Any idea?

xekin said:
Thanks
yep, it doesn't work with my user or root. this is what i see with a dmesg when fastboot mode:
Any idea?
Click to expand...
Click to collapse
seems to be quite an old bug on Ubuntu (https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.20/+bug/88530)
use another usb port/controller?
are you connecting the device to a USB HUB? More devices connected to the PC?
change usb cables?
try to update your kernel to latest (3.9.x) ?
is this a laptop? try to remove the battery, wait like 10min, turn it on again

same prolem nexus 4
I am having the same problem with my nexus 4 sometimes it connects and then desconnects what can i do ?Please help!! :crying::crying::crying::crying::crying:

xekin said:
More info about:
This is what is shown in fastboot mode:
FASTBOOT MODE
PRODUCT NAME - tuna
VARIANT - maguro
HW VERSION - 9
BOOTLOADER VERSION - PRIMEKK15
BASEBAND VERSION - I9250XXLJ1
CARRIER INFO - NONE
SERIAL NUMBER - 1234123414341
SIGNING - production
LOCK STATE - LOCKED
How can i re-install or re-flash "fastboot mode"? I tried flashing OMAP4440 but nothing happened. I've tried to access to fastboot from win7, win8 and ubuntu. In all of them adb works correctly.
Click to expand...
Click to collapse
did u change your bootloader version?
should be PRIMELC03 from stock.. KK15 was the old version. that why u got this issues. just back to stock version (newest).
try boot to odin bootloader (long press volume down + power button). if your phone can boot to odin then install the odin toolkit (pc)

RSA fingerprint

Hello all,
I have tried on different laptops, with different cables but my pixel c will not show the rsa dialog to allow access for adb/fastboot. I have tried NRT as well but the device cannot be found. The device is running the lastest software version as of 9/18/16

jasonc7649 said:
Hello all,
I have tried on different laptops, with different cables but my pixel c will not show the rsa dialog to allow access for adb/fastboot. I have tried NRT as well but the device cannot be found. The device is running the lastest software version as of 9/18/16
Click to expand...
Click to collapse
I think more detail is required. Device configured correctly? - Developer options - usb debugging enabled (also revoke debugging authorisations causes a request for RSA confirmation on a previously "connected perfectly" device). Guessing you're using Windows - what "adb" driver (if any) is shown in Device Manager

I've tried to revoke authorizations but nothing happens, and I can access the devices internal storage. However, when I plug the pixel c in, it immediately goes to charging mode and there isn't an mtp button in the storage settings in 7.0 so I can't toggle it on/off. I've also tried enabling/disabling debugging while connected and nothing happens.

I'll assume you have an "adb" driver of some form showing in Device Manager and adb.exe and fastboot.exe in a directory that I'll call "ADB".
Connect the Pixel C and unlock. By default it should have notifications for USB debugging enabled and "USB charging". Adb will work at this stage.
Open a command prompt and change to "ADB" Try the command "adb devices" and it should show your tablet.
Try "adb reboot bootloader" . I expect this command on your PC to fail because it holds no authorisation. But it should trigger:
a) get your tablet to request RSA authorisation
b) start the process of installing the "Android Composite ADB Interface" device driver (under "Android Device" in Device Manager.)
Repeat "adb reboot bootloader" and your tablet should reboot into a "waiting for fastboot command" screen
Try "fastboot devices" should show the tablet and then "fastboot reboot" will restart your tablet.

Pixel c not show up on adb devices list

Flashing Shield 2017

Hi,
Have a Shield 2017 which I'd like to flash to a normal LInux userland rather than Android, however I seem to be failing at the first hurdle, namely ADB and Fastboot.
I have been able to ADB over Ethernet, however when I use ADB and Fastboot over USB I never seem to be able to discover the attached device. I've tried using both macOS and Linux, and have tried a number of USB A-A cables.
I've followed both the nVidia flashing instructions, plus a few from this forum, eg enabling the developer mode, USB debugging, etc. to no avail. These are the steps I've taken.
- Enable Development mode on SATV (click build a number of times)
- Enable ADB over USB on SATV (Settings/Development Options/Toggle USB Debugging)
- Download and install Android SDK tools from the Android SDK pages.
- Plugin USB A-A into the end USB port and my Macbook/Linux box
- Run `adb devices`
At this point I don't get any output.
Code:
[[email protected] ~]# adb devices
List of devices attached
If I connect via Ethernet...
Code:
[[email protected] ~]# adb connect 10.200.1.111
connected to 10.200.1.111:5555
[[email protected] ~]# adb devices
List of devices attached
10.200.1.111:5555 device
Although I can at this point reboot the Shield in fastboot/bootloader mode, with a quick `adb reboot bootloader`, I can't then fastboot, as again fastboot cannot see the device.
Code:
[[email protected] ~]# fastboot devices
On neither my mac nor Linux box, the USB device doesn't seem to be recognised (with lsusb or ioreg), although have tried a couple of new USB 3.0 A-A cables. Wondering if the USB debugging isn't enabling fully for some reason?
Any ideas??
Thanks
Dan

danhawker said:
Hi,
Have a Shield 2017 which I'd like to flash to a normal LInux userland rather than Android, however I seem to be failing at the first hurdle, namely ADB and Fastboot.
I have been able to ADB over Ethernet, however when I use ADB and Fastboot over USB I never seem to be able to discover the attached device. I've tried using both macOS and Linux, and have tried a number of USB A-A cables.
I've followed both the nVidia flashing instructions, plus a few from this forum, eg enabling the developer mode, USB debugging, etc. to no avail. These are the steps I've taken.
- Enable Development mode on SATV (click build a number of times)
- Enable ADB over USB on SATV (Settings/Development Options/Toggle USB Debugging)
- Download and install Android SDK tools from the Android SDK pages.
- Plugin USB A-A into the end USB port and my Macbook/Linux box
- Run `adb devices`
At this point I don't get any output.
Code:
[[email protected] ~]# adb devices
List of devices attached
If I connect via Ethernet...
Code:
[[email protected] ~]# adb connect 10.200.1.111
connected to 10.200.1.111:5555
[[email protected] ~]# adb devices
List of devices attached
10.200.1.111:5555 device
Although I can at this point reboot the Shield in fastboot/bootloader mode, with a quick `adb reboot bootloader`, I can't then fastboot, as again fastboot cannot see the device.
Code:
[[email protected] ~]# fastboot devices
On neither my mac nor Linux box, the USB device doesn't seem to be recognised (with lsusb or ioreg), although have tried a couple of new USB 3.0 A-A cables. Wondering if the USB debugging isn't enabling fully for some reason?
Any ideas??
Thanks
Dan
Click to expand...
Click to collapse
Have you solved your issue? I do not have PC but want to use other android device with Magisk and osm0sis ADB & Fastboot script and I have the same problem...

melendi said:
Have you solved your issue? I do not have PC but want to use other android device with Magisk and osm0sis ADB & Fastboot script and I have the same problem...
Click to expand...
Click to collapse
Do you have a nvidia gamepad?

gengt said:
Do you have a nvidia gamepad?
Click to expand...
Click to collapse
Yes and I had already been in fastboot but on another android device with osm0sis ADB & Fastboot script there are no fastboot devices listed.

scrcpy issues

Hello xda'ers
I have the Xiaomi Redmi Note 8, however I want to use the scrcpy github . com / Genymobile / scrcpy utility it says it cannot detect the phone.
ADB Setup and its drivers have been correctly installed.
USB debugging has been enabled in the phone.
But the ADB cannot detect the phone.
It still is not working, so I went into the phone, developer options and go to USB Debugging, Security settings, and toggle that on, but it asks for a Mi Account?, which I do not have.
Please help.

Might as well sign up for that Mi account, because you need the (security settings) toggle turned on if you want to control the device via scrcpy. What does it tell you when you enter the command adb devices ? Did you get the popup asking for confirmation on whether you want to allow the PC to access debugging when you connected the phone via USB? Also make sure MTP/PTP/whatever else isn't turned on.

It's odd, executing adb devices gave an unauthorized message on the computer console, but the security confirmation never appeared on the phone up until some hours ago. I authorized the connection and voila I can now see the phone's screen on desktop PC via scrcpy, however.....
The screen just freezes, I mean, I cannot interact with it on the computer. If I unblock the phone manually and interact with it, the screen refreshes properly on the desktop, alas this is an issue with scrcpy not with the phone or ADB. Maybe I should file a bug or search their site?

Again, you have to enable the (security settings) toggle in your developer options if you want to control your device from the computer. This is mentioned on the Readme on scrcpy GitHub already.

Found solution:
1. Enable USB debugging
2. Run any terminal as root
3. setprop persist.security.adbinput 1
. That's all, nothing else is required

Question adb/fastboot wont recognize my device.

Okay so first off:
- Chinese Variant with OxygenOS installed
- OEM unlocking enabled
- Im on linux
will output the devices and I can successfully run ``adb reboot bootloader`` when in bootloader, running ``fastboot devices`` no devices show up, i tried installing the oneplus adb drivers which ended with no change.
however, doing ``adb reboot fastboot`` and then ``fastboot devices`` it succeeds, now trying ``fastboot flashing unlock`` returns with:
FAILED (remote: 'Unrecognized command flashing unlock')
fastboot: error: Command failed
Click to expand...
Click to collapse
i read in another post that i may need to try ``fastboot oem unlock`` or ``fastboot oem unlock-go`` both of which return:
FAILED (remote: 'Command not supported in default implementation')
fastboot: error: Command failed
Click to expand...
Click to collapse
So im kind of at a loss here of what to do.... any ideas?
UPDATE:
Thanks to these three posts I was able to get it working:
adb/fastboot wont recognize my device.
Okay so first off: - Chinese Variant with OxygenOS installed - OEM unlocking enabled - Im on linux will output the devices and I can successfully run ``adb reboot bootloader`` when in bootloader, running ``fastboot devices`` no devices show up...
forum.xda-developers.com
adb/fastboot wont recognize my device.
Okay so first off: - Chinese Variant with OxygenOS installed - OEM unlocking enabled - Im on linux will output the devices and I can successfully run ``adb reboot bootloader`` when in bootloader, running ``fastboot devices`` no devices show up...
forum.xda-developers.com
adb/fastboot wont recognize my device.
Okay so first off: - Chinese Variant with OxygenOS installed - OEM unlocking enabled - Im on linux will output the devices and I can successfully run ``adb reboot bootloader`` when in bootloader, running ``fastboot devices`` no devices show up...
forum.xda-developers.com

i'm not familiar with OnePlus or Linux...
but what version of adb & fastboot are you employing? And/or I've seen this kind of issue happen (randomly) because of an usb cord issue, of all things -- I wonder if it's a Google Pixel thing, but you never know...

simplepinoi177 said:
i'm not familiar with OnePlus or Linux...
but what version of adb & fastboot are you employing? And/or I've seen this kind of issue happen (randomly) because of an usb cord issue, of all things -- I wonder if it's a Google Pixel thing, but you never know...
Click to expand...
Click to collapse
Android Debug Bridge version 1.0.41
Version 33.0.3p2-android-tools
I've attempted different cables and ports and still have this issue.

Try on Windows

ikram.senguen said:
Try on Windows
Click to expand...
Click to collapse
If I could avoid installing an entire operating system (VM or straight on hardware) that would be preferable.

limepot said:
Android Debug Bridge version 1.0.41
Version 33.0.3p2-android-tools
I've attempted different cables and ports and still have this issue.
Click to expand...
Click to collapse
I'm unsure if OnePlus prefers its own type of platform tools (as I've just recently learned that certain manufactured devices have their own preferred ways of getting adb & fastboot), but if your device can/prefer the same as Google Pixels, you should be if you can -- or try, if you haven't -- using Google's/Android's official platform tools from the developer site; there's a Linux version (which is what triggered my thought on this as that is your setup) and, although it caused great issue for Pixel's (or A/B devices, i imagine), version is updated to r34.0.2 . Maybe the latest updated version might work where yours isn't...
just a thought...
*although much of this is out of my league, again as I am not familiar with OnePlus or Linux...

simplepinoi177 said:
I'm unsure if OnePlus prefers its own type of platform tools (as I've just recently learned that certain manufactured devices have their own preferred ways of getting adb & fastboot), but if your device can/prefer the same as Google Pixels, you should be if you can -- or try, if you haven't -- using Google's/Android's official platform tools from the developer site; there's a Linux version (which is what triggered my thought on this as that is your setup) and, although it caused great issue for Pixel's (or A/B devices, i imagine), version is updated to r34.0.2 . Maybe the latest updated version might work where yours isn't...
just a thought...
*although much of this is out of my league, again as I am not familiar with OnePlus or Linux...
Click to expand...
Click to collapse
thanks! ill give it a try.

limepot said:
thanks! ill give it a try.
Click to expand...
Click to collapse
doesnt seem to make a difference here unfortunately.

limepot said:
Okay so first off:
- Chinese Variant with OxygenOS installed
- OEM unlocking enabled
- Im on linux
will output the devices and I can successfully run ``adb reboot bootloader`` when in bootloader, running ``fastboot devices`` no devices show up, i tried installing the oneplus adb drivers which ended with no change.
however, doing ``adb reboot fastboot`` and then ``fastboot devices`` it succeeds, now trying ``fastboot flashing unlock`` returns with:
i read in another post that i may need to try ``fastboot oem unlock`` or ``fastboot oem unlock-go`` both of which return:
So im kind of at a loss here of what to do.... any ideas?
Click to expand...
Click to collapse
On windows computer, disable driver signature, and you should see a watermark in lower right corner of home screen that states test mode, then install the latest op USB drivers. Make sure to uninstall the old op USB driver first. Then reboot, disable driver signature signing, the reboot computer again. Then start you adb and fastboot commands.

TheGhost1951 said:
limepot said:
Okay so first off:
- Chinese Variant with OxygenOS installed
- OEM unlocking enabled
- Im on linux
....
So im kind of at a loss here of what to do.... any ideas?
Click to expand...
Click to collapse
On windows computer, disable driver signature, and you should see a watermark in lower right corner of home screen that states test mode, then install the latest op USB drivers. Make sure to uninstall the old op USB driver first. Then reboot, disable driver signature signing, the reboot computer again. Then start you adb and fastboot commands.
Click to expand...
Click to collapse
Too bad OP stated he's she's not on windows, but on Linux...

simplepinoi177 said:
Too bad OP stated he's not on windows, but on Linux...
Click to expand...
Click to collapse
tried windows just now (she) same issue, although i did not try their suggestion, i will have to attempt that.

limepot said:
tried windows just now (she) same issue, although i did not try their suggestion, i will have to attempt that.
Click to expand...
Click to collapse
What type of USB port are you using? I was having all kinds of issues with adb and fastboot and it turned out to be because my computer doesn't have any USB 2.0 ports. I found two potential solutions, one of which was to get a hub with USB 2.0 ports, and the other was to change some settings in windows 10. If your computer doesn't have a USB 2.0 port you could try using a hub with USB 2.0 ports, or you could do some searching to see if there's a workaround for your Linux distro like there is for windows.

Masterchief87 said:
What type of USB port are you using? I was having all kinds of issues with adb and fastboot and it turned out to be because my computer doesn't have any USB 2.0 ports. I found two potential solutions, one of which was to get a hub with USB 2.0 ports, and the other was to change some settings in windows 10. If your computer doesn't have a USB 2.0 port you could try using a hub with USB 2.0 ports, or you could do some searching to see if there's a workaround for your Linux distro like there is for windows.
Click to expand...
Click to collapse
i tried on various different ports, i tried on 2.1 and 3 so far no luck.
ive been spending way too much time trying to install windows and ended up being able to on an old laptop so im going to try the windows suggestions (this laptop has only 2.0 ports), that ive seen so far.

Are your fastboot drivers upto date? When you connect your device to pc in fastboot, try searching in the drivers for adb,bootloader,or smth named driver. If not there then your device will probably be in the "others" driver tab with an exclamation mark.

TheGreatBumBum said:
Are your fastboot drivers upto date? When you connect your device to pc in fastboot, try searching in the drivers for adb,bootloader,or smth named driver. If not there then your device will probably be in the "others" driver tab with an exclamation mark.
Click to expand...
Click to collapse
again, linux, i just installed the drivers on my newly installed windows machine, just installed drivers anyways.

limepot said:
again, linux, i just installed the drivers on my newly installed windows machine, just installed drivers anyways.
Click to expand...
Click to collapse
Oh yeah sorry bout that, just want to tell you windows is a bit buggy. I had to install the fastboot drivers every 5-10 minutes.Dunno why,Dunno how.

Back to basics, use only the motherboard/rear ports. Some phones are picky about the cable, you might need to use a factory cable. Does the computer see the phone at all? If not you don't have the right drivers.
Also 'adb reboot fastboot' "working" doesn't mean it worked.
In simple terms, the command will work but it must return a device ID below it and should trigger the phone to trust the PC.
Command order on Windows is:
adb devices
adb reboot fastboot
"whatever the Oneplus Unluck command is" some phones have different ones for different models.

TheGhost1951 said:
On windows computer, disable driver signature, and you should see a watermark in lower right corner of home screen that states test mode, then install the latest op USB drivers. Make sure to uninstall the old op USB driver first. Then reboot, disable driver signature signing, the reboot computer again. Then start you adb and fastboot commands.
Click to expand...
Click to collapse
Okay after taking a lot of time this was indeed the solution, thankyou!

Linux systems oftentimes have issues due to udev rules and missing group memberships of your user. For example on arch you can install android-udev and add the user to the adbusers group. I don't know if there are any packages for debian based distros, but I think they use the plugdev goup for udev rules.
The following gh repo is a good place to start:
GitHub - M0Rf30/android-udev-rules: Android udev rules list aimed to be the most comprehensive on the net
Android udev rules list aimed to be the most comprehensive on the net - GitHub - M0Rf30/android-udev-rules: Android udev rules list aimed to be the most comprehensive on the net
github.com

der_akinator said:
Linux systems oftentimes have issues due to udev rules and missing group memberships of your user. For example on arch you can install android-udev and add the user to the adbusers group. I don't know if there are any packages for debian based distros, but I think they use the plugdev goup for udev rules.
The following gh repo is a good place to start:
GitHub - M0Rf30/android-udev-rules: Android udev rules list aimed to be the most comprehensive on the net
Android udev rules list aimed to be the most comprehensive on the net - GitHub - M0Rf30/android-udev-rules: Android udev rules list aimed to be the most comprehensive on the net
github.com
Click to expand...
Click to collapse
This is incredibly helpful thankyou.