Business
Jobs
  • About Us
  • Solutions
    • Job Postings
      Post your job and receive qualified candidates in 48h.
    • Candidate Assessments
      500+ technical and psychological tests, plus anti-fraud.
    • Headhunting
      Tailor-made executive search from start to finish.
    • Payroll + EOR
      Payroll dispersal and EOR across 15+ LATAM countries.
  • Pricing
  • Jobs

0

834
Views
Unable to unlock Android bootloader via Fastboot on Ubuntu 12.04 - waiting for device

I am trying to unlock my Nexus 7 (2012)'s bootloader running Android 5.1.1 on Ubuntu 12.04 (Desktop).

I am able to communicate & send commands to the device using adb (USB-Debugging on Nexus turned on - Android SDK & Fastboot tool installed on Ubuntu):

niq@vb-ubuntu:~$ Android/Sdk/platform-tools/adb devices
List of devices attached
015d2a4ffb401e0c    device

and the following command does the expected job aswell:

niq@vb-ubuntu:~$ Android/Sdk/platform-tools/adb reboot bootloader

After setting my tablet to fastboot mode I can communicate with it using the fastboot commands:

niq@vb-ubuntu:~$ sudo fastboot devices
015d2a4ffb401e0c    fastboot

However when I now try to unlock the device's bootloader, that is when I run into troubles, first try does the following:

niq@vb-ubuntu:~$ sudo fastboot oem unlock
...

When I open another terminal now and try it another time I get the infamous "waiting for device" message displayed in my terminal:

niq@vb-ubuntu:~$ sudo fastboot oem unlock
< waiting for device >

Same thing happens when I login as root rather than using sudo. And also doesn't make a difference if I use this command (also results in waiting for device):

niq@vb-ubuntu:~$ sudo fastboot oem get_identifier_token
< waiting for device >

My Ubuntu clearly is able to talk to the tablet and execute commands on the device, why is it not possible to unlock the bootloader given that it is recognised and all the other commands work seamlessly?

Another thing I tried:

niq@vb-ubuntu:~$ lsusb -v | grep Google
Couldn't open device, some information will be missing
Bus 001 Device 004: ID 18d1:4e40 Google Inc. 
  idVendor           0x18d1 Google Inc.
  iManufacturer           1 Google, Inc

/etc/udev/rules.d/11-android.rules:

UBSYSTEMS=="usb", ATTRS{idVendor}=="18d1", MODE="0640", OWNER="mbp"

and finally:

niq@vb-ubuntu:~$ sudo service udev stop
udev stop/waiting
niq@vb-ubuntu:~$ sudo service udev start
udev start/running, process 2424

Am I missing something here?

over 4 years ago · Santiago Trujillo
2 answers
Answer question

0

I believe the issue here is with the device being locked by the carrier. Check the "OEM-Locking" under developer setting, if it greyed out then you will not be able to unlock the bootloader.

I just tried it on my Pixel 4a that is carrier locked to Verizon and had no success just 3 dots ... after executing the oem unlock command, same story as yours.

From what I read online - Phone needs to have OEM-Locking turned on, meaning phone must be unlocked by the carrier. If OEM-Locking is greyed means phone is locked by the carrier and bootloader cannot be unlocked.

over 4 years ago · Santiago Trujillo Report

0

I had the same problem but I was able to solve it. Android version 5.1 running on Ubuntu 14.04.

In the terminal type:

~$  adb reboot bootloader.

then:

sudo fastboot oem unlock

Hope it works.

over 4 years ago · Santiago Trujillo Report
Answer question
Find remote jobs

Discover the new way to find a job!

Top jobs
Top job categories
Business
Post vacancy Pricing Sales
Legal
Terms and conditions Privacy policy
© 2026 PeakU Inc. All Rights Reserved.
Andres GPT
Show me some job opportunities
There's an error!