Trouble Unlocking Bootloader on Nexus 4

[jmcudd]

Okay so I've been trying to unlock my bootloader on my new Nexus 4 and haven't had much luck. I've carefully followed the directions on this forum and always get stuck when trying to unlock the bootloader.

Here is what I do.

1. Enable developer mode on the phone with usb debugging
2. Put the phone in FASTBOOT MODE.
3. Connect phone to computer
4. Open a terminal (arch linux with adb and fastboot tools installed)
5. fastboot devices (verify that my device is listed)
6. fastboot oem unlock

Upon entering

fastboot oem unlock

in the terminal I get three dots

...

and on the phone nothing happens. I do not see the expected dialog on the phone, and the phone remains in fastboot. Based on the videos I've seen, I should see the "unlock bootloader" screen pretty much immediately. Nothing happens.

Here is some addtional information about my fastboot mode. Thanks for the help!

FASTBOOT MODE
PRODUCT_NAME - mako
VARIANT -mako 16GB
HW VERSION - rev_11
BOOTLOADER VERSION - MAKOZ10o
SECURE BOOT - enabled
LOCK STATE - locked

 

[2defmouze]

Can you include screenshots of the terminal screen? Need to see the response from
fastboot devices

Followed by
fastboot oem unlock

Sent from my Nexus 4 using Tapatalk 2

 

[greydarrah]

Are you actually typing fastboot oem unlock? Because what you need to type is fastboot-windows oem unlock (assuming your on a windows pc and your using the files from 2def).

 

[RumoredNow]

Are you actually typing fastboot oem unlock? Because what you need to type is fastboot-windows oem unlock (assuming your on a windows pc and your using the files from 2def).

OP says he's on an Arch Linux system...

 

[jmcudd]

Hey guys,

Thanks for the quick responses. I installed adb and fastboot tools through the AUR repo on Arch Linux so the command is just "fastboot". Here is a screenshot of my troubles. It remains like this forever, and the only way I can get it to stop is to reboot my android. Ctrl-C doesn't even kill the process.

Thanks for the help.

 

[greydarrah]

Well, do you have a windows pc you could try it on? I know jack about linux, but it's quick and easy on a pc.

 

[2defmouze]

Hey guys,

Thanks for the quick responses. I installed adb and fastboot tools through the AUR repo on Arch Linux so the command is just "fastboot". Here is a screenshot of my troubles. It remains like this forever, and the only way I can get it to stop is to reboot my android. Ctrl-C doesn't even kill the process.

Thanks for the help.

Hmmm.. that is odd, seems its just not processing the command for some reason. It may be an odd workaround, but I would say try downloading the fastboot file pack I have in the "Unlock and Root" thread and unzip it, then open a terminal within that folder or navigate to it in an open terminal window, and try the commands using that file to run them, so you should enter the commands as follows to tell the terminal to use that file and not the one you have installed to your system:
fastboot-linux devices
fastboot-linux oem unlock

It's kind of a long shot but I just want to see if that will work, as it might be a simple fix. Let me know.

 

[jmcudd]

Same thing. I've tried it on a windows computer as well and have the same experience.

I also decided to try specifying the device.

No Dice. The only other thing that I think it might be is the secure boot is enabled. Would this affect anything?

 

[2defmouze]

Same thing. I've tried it on a windows computer as well and have the same experience.
http://i.imgur.com/OC4zVj2.png

I also decided to try specifying the device.
http://i.imgur.com/w6GYvbp.png

No Dice. The only other thing that I think it might be is the secure boot is enabled. Would this affect anything?

Nah the secure boot thing is like that on every N4, doesn't effect it. You said you tried on another computer as well? Have you tried another usb port? Preferably a rear one.. Or even another usb cable? Sometimes those seemingly innocuous things can make a difference..

While you check that I'll see if I can find anything or anyone else with an idea..

Sent from my Nexus 4 using Tapatalk 2

 

[jmcudd]

I finally got it to work. I tried it on my laptop which is also running arch linux. I installed android-tools from the AUR repo. Then "sudo -i" then "fastboot devices" then "fastboot oem unlock". It worked as expected. I think I might have a udev problem on my other computer, I'm not sure. If I find out any more detailed as to why it didn't work I will post them here. Thanks anyway.

 

[2defmouze]

I finally got it to work. I tried it on my laptop which is also running arch linux. I installed android-tools from the AUR repo. Then "sudo -i" then "fastboot devices" then "fastboot oem unlock". It worked as expected. I think I might have a udev problem on my other computer, I'm not sure. If I find out any more detailed as to why it didn't work I will post them here. Thanks anyway.

Oh crap.. Adding sudo is like so freaking obvious I feel like a fool for not realizing that.. Haha. I'm glad you figured it out though. Yeah fastboot commands on Linux generally require sudo permissions to function. Derp.



Sent from my Nexus 7 using Tapatalk 2

 

[jmcudd]

I preformed the commands as root to no avail on my desktop. It only worked on my laptop.

 

[Hudson Mendes]

What if it doesn't work?
I have run the "sudo -i", "fastboot devices" e "fastboot oem unlock".

Could be important: what I find very interesting is the that I receive no "yes/no" message on my phone.
It simply says "=> FASTBOOT mode..." as in a shell message.
I've also tested other commands and the phone is actually receiving the commands, so the communication is just fine!

I'm still getting the ". . ." that do not ever finish!
Going crazy with this T.T

 

[someguy01234]

Make sure to setup your udev rules.

Put your phone in fastboot mode and follow step 1 from here:
Ubuntu 12.04 - Install Android Tools (ADB, Fastboot, ...)

Also do it when your phone is connected with usb debugging, which has a different value.