I want to unlock the bootloader of my phone using the unofficial method. I reboot my phone into fastboot mode using "adb reboot bootloader" and plug my phone to my laptop. Fastboot detects my devices, however, when I try to execute any command, for example "fastboot reboot", the command hangs. There is no output and I can't send a SIGINT signal to it either by pressing Ctrl+C. It should actually reboot my phone instead of hanging. Also, sometimes my phone would just display "Press any key for shutdown" right after I plug it to the laptop (similar to what's happening here). I tried running same commands on my old Zenfone Selfie (Z00T, ZD551KL) on fastboot and they work fine, I could even flash a custom recovery with no issues.
My system parameters:
Processor is Intel Core i5-8250U.
Operating system is Ubuntu 20.04 LTS.
ADB and fastboot versions are 1:8.1.0+r23-5ubuntu2 each.
My phone's firmware is PKQ1.WW_Phone-16.2017.1912.060-20191125
So far I've tried:
Changing the cable I use to connect my phone with my laptop. No results.
Changing the port I connect my device to from USB 3.1 to USB 2.0. No results.
Using a different fastboot version (the one that came with the unofficial bootloader unlock method). Nothing either.
Using a Windows 10 virtual machine, connecting my phone to it and executing fastboot commands there. No results either.
Updating my phone's firmware to 087, also Pie version. No results either.
Updating my phone to the beta version of Q, 438. No results.
Unplugging the phone during the process of command hanging and then plugging it back. Results vary. Sometimes it takes exactly 3.02 seconds and it does nothing, sometimes it would display the aforementioned "Press any key for shutdown" message.
Executing the command on my laptop and then plugging my phone in. Same as the previous point.
Executing "fastboot oem device-info" instead, using a method described in the previous point. It says "FAILED (remote: unknown command)"
Rebooting my phone to fastboot mode with Volume Up + Power and through recovery mode. No results.
Any idea what could be the issue and how do I solve it? Since ASUS stopped supporting our device, I would really like to unlock the bootloader of my phone so I could install custom ROMs.
Thank you for your time.
Related
I have adb and fastboot set up on my laptop, I just recently put Ubuntu back on here and just finished setting up my sdk and such a couple hours ago. I know its set up fine because adb works and I am getting fastboot output from my terminal, but its not reading my device. if I just type fastboot, the help will come up, and when i prompt for devices I get nothing, I have tried three different cables. Any ideas? fastboot tends to be unreliable for me in the past more so than adb. I just don't know what I can do now.. I am on the NS4G 4.0.4 leak and I'm trying to flash CWM and root so I really need fastboot
You are in the bootloader right?
Phone Off --> Vol. Up + Power simultaneously --> "fastboot devices"
yeah I am. I did it on my other NS4G on windows just yesterday and had no problem with it but I hate booting into windows unless I have to. Just trying to get it working on ubuntu
I'm currently attempting to root my atrix but I've come across a problem that I can't seem to be able to solve through googling or otherwise.
I'm using the tutorial stickied on the Atrix homepage labelled [HOWTO MAY16].
I got as far as step 8 and my phone passed the sbf flash using RSD lite but continuing on with the process to step 13 where it is asking me to type "fastboot oem unlock" into cmd I get an error message telling me that cmd is waiting for my device but nothing seems to happen.
I've tried reinstalling drivers (64 bit), restarting computer, restarting phone, trying different leads/usb sockets with no change to my result.
The exact thing that I'm doing with cmd is to navigate to the platform-tools folder, open adb, open flashboot and then attempt fastboot oem unlock.
Additional information:
UK Orange Atrix 4G running 3.4.4
using IHOP sbf file
running windows 7 64-bit, using the 64-bit drivers.
Do you have access to win 7 or xp? Win 8 is really new and possibly that could be the problem. Worth a shot.
pre4speed said:
Do you have access to win 7 or xp? Win 8 is really new and possibly that could be the problem. Worth a shot.
Click to expand...
Click to collapse
Ops, typo. I'm running Windows 7 64-bit. I'll edit my post when xda allows me to.
Unlock
Enter the bootloader program by powering off the phone, Hold the volume down key and the power at the same time. The phone will be in the bootloader program when it powers up, use the volume down key to scroll through bootloader menu options. the second option will be fastboot program. Select the fastboot option with the volume up key, this will enter the fastboot mode of operation. Connect the phone to the PC via USB cable. Enter the directory where the fastboot program resides on the PC. Type the Fastboot oem unlock command. If sucessful a message will display on PC retuned by the phone. Reboot phone and unlocked will display in the upper left corner of the phones display. Continue to follow the original post, flash recovery, root phone, flash custom ROM. Happy Flashing, Enjoy! :fingers-crossed:
fdaconta said:
Enter the bootloader program by powering off the phone, Hold the volume down key and the power at the same time. The phone will be in the bootloader program when it powers up, use the volume down key to scroll through bootloader menu options. the second option will be fastboot program. Select the fastboot option with the volume up key, this will enter the fastboot mode of operation. Connect the phone to the PC via USB cable. Enter the directory where the fastboot program resides on the PC. Type the Fastboot oem unlock command. If sucessful a message will display on PC retuned by the phone. Reboot phone and unlocked will display in the upper left corner of the phones display. Continue to follow the original post, flash recovery, root phone, flash custom ROM. Happy Flashing, Enjoy! :fingers-crossed:
Click to expand...
Click to collapse
I just gave it another try and it gets stuck after I type fast boot oem unlock. I definitely have the right directory but I still get stuck here. Cmd just tells me it's waiting for my device and stops there. I think it's a driver issue after a bit of googling but the official drivers aren't working. This socks.
I had a similar problem with my device not showing up. There wasn't really a big fix for it but I just waited longer before trying to execute the command. I'm not sure if you're experiencing the same thing I did but when it couldn't detect my device it just hadn't been recognized by the computer yet. Make sure your drivers are working (connect usb and select every option on the pull down menu and are sure the device gets installed). After that do the same thing as before for fastboot but make sure you securely plug it in and wait for the computer to detect your phone before you move forward
Sent from my MB860 using xda app-developers app
Hi,
I ran into a problem with my Nexus 4, the plan was to unlock the bootloader using my mac and fastboot. (used this as information but didn't follow it step by step, youtube.com/watch?v=fHZJ2f6JLw0)
I turned off the phone and went into the bootloader with volume down + power button. From here i used "fastboot devices" to secure that i was able to communicate with the phone. My device showed up together with an error message saying "ERROR: could not get pipe properties nexus 4".
Before doing any more i wanted to understand what this message meant so I searched the web without any success. I booted up my android, turned on usb debugging and used "adb devices". This time only my devices showed up and no error messages. I used the "adb reboot boatloader" to access the bootloader once again.
I still had the same error message with "flashboot devices" as before.
From here i didn't do anything more, I may have disconnected the usb from the computer while the terminal window was open and the phone in bootloader but without running any command from fastboot.
So I didn't run "fastboot oem unlock" or anything else.
I turned off the phone and tried to access the bootloader one more time with the volume down + power button. It didn't respond to this any more and nothing happened, the device just stayed turn off.
I turned on the phone and tried to use adb to access the bootloader but now when running the "adb devices" it just responds "-bash: adb: command not found".
I have tried to restore the phone thru the android setting meny without any success. The phone is working fine without any problem except i cant access the bootloader or use adb.
So I desperately need help from you guys. :crying:
Have any of you heard of this problem before?
Regards Rasmus
I have to change my statement.
Actually I succeeded rooting and installing CWM recovery using a win7 computer together with Nexus4 toolkit.
The issue i have right now is that i can't start the device into bootloader using volume and power buttons.
To access bootloader i have to go thru the toolkit and this can be an issue in case i flash a bad rom or kernel and can access android usb debugging.
Is it possible to restore the bootloader?
rallanand said:
The issue i have right now is that i can't start the device into bootloader using volume and power buttons.
Click to expand...
Click to collapse
Are you holding the down volume and pressing the power button?
What OS is the computer that you are using? If you have reset the device, make sure that USB debugging is checked again. I know it sounds dumb, but a lot of times it's the simplest things we forget. Once you factory reset your device, it resets everything.
If you are on Windows 7, make sure you are starting the command prompt from the same location your adb is installed. If you are on Ubuntu or another Linux distro, please let me know which one. This seems like it should be an easy fix for you, but a little more info is needed. Thanks!
Hi all you good people, I have a nexus 4 with a bootloop also additional problems are:
1. Im a complete novice and can only do things with simple instructions (sorry!)
2. No debugging mode was enabled
3. I only have a Mac
4. The Mac is not showing the device with the android transfer app and also I've tried a few things in terminal - but again comes up with device not found.
I can get to the Postboot mode by pressing the power/volume buttons so thats okay, on that screen it says: SECURE BOOT - enabled & LOCK STATE -locked
I have tried all the clear cache/restore factory on the recovery screen and taken the battery out for a while but to no avail.
thanks in advance!
You should unlock the bootloader and then flash a stock Google image. Unlocking the bootloader will wipe all data on the phone.
First thing would be to at least get the phone to recognize fastboot commands. Not sure if this will help: http://forum.xda-developers.com/showthread.php?t=1917237
audit13 said:
You should unlock the bootloader and then flash a stock Google image. Unlocking the bootloader will wipe all data on the phone.
First thing would be to at least get the phone to recognize fastboot commands. Not sure if this will help: http://forum.xda-developers.com/showthread.php?t=1917237
Click to expand...
Click to collapse
Thankyou that is really helpful how ever when I type in: ./adb devices it dosnt list any devices including my phone, if I try a command such as:
./fastboot oem unlock
it just hangs on: "waiting for device"
The USB cable is good as I tried it with another device - could it be a damaged USB female socket on the device itself?
thanks
Adb commands will not work when the phone is in fastboot mode.
With the phone connected and in fastboot mode, type "fastboot devices" and press enter. It should return your phone's serial number. If not, try different USB cables and USB ports.
audit13 said:
Adb commands will not work when the phone is in fastboot mode.
With the phone connected and in fastboot mode, type "fastboot devices" and press enter. It should return your phone's serial number. If not, try different USB cables and USB ports.
Click to expand...
Click to collapse
Thanks when you say 'fastboot' mode - how do I get it in that mode?
audit13 said:
Adb commands will not work when the phone is in fastboot mode.
With the phone connected and in fastboot mode, type "fastboot devices" and press enter. It should return your phone's serial number. If not, try different USB cables and USB ports.
Click to expand...
Click to collapse
is there a command line I can input for fastboot?
nexus4uk said:
is there a command line I can input for fastboot?
Click to expand...
Click to collapse
Fastboot mode is when you boot into the bootloader where it said secure boot enabled.
Sent from my Nexus 4 using XDA Labs
To enter fastboot mode on the phone, power off the phone, press and hold volume up + volume down + power at the same time.
audit13 said:
To enter fastboot mode on the phone, power off the phone, press and hold volume up + volume down + power at the same time.
Click to expand...
Click to collapse
Thanks tried this - and and nothing came up with the command 'fastboot devices' - thanks anyway
If nothing comes up when executing the command, that tells me the drivers are not installed or the connection between the phone and computer is not good.
HI
How can I install the drivers on a mac? thanks
This may help: http://forum.xda-developers.com/android/general/adb-fastboot-binaries-os-x-inclusive-t2941205
I know there are instructions (which I am following) and a similar thread (which doesn't provide a solution). Anyway, I am following the instructions and I'm stuck at the command for detecting fastboot devices. The command window shows nothing, not my serial number or an error message. The Fastboot Protocol option on the tablet's menu just loops back to the same menu. I followed all the instructions (undetailed as they are) correctly, but on the fastboot device step I am stuck. I can't use the CyanogenMod links anymore because they're down. Other websites only give me steps I've already done or don't apply to this.
Basically, I just want to know how to make my PC detect my tablet so I can then wipe and flash the images. I want to downgrade because some apps just don't work correctly with 2.0 and I don't really want to wait for an eventual fix (which may or may not fix all the app issues).
I should mention that I can detect the adb device when it's on normally ( I type adb devices and it shows up). But when i reboot into bootloader and type adb or fastboot devices it isn't detected, and when I try to use fastboot protocol (either before or after connecting) it doesn't do anything.
Had the same issue with fastboot myself. If you are running Windows 10, that could be the problem. The ususal about checking different USB ports etc. also applies.
The drivers are most important. The naked usb drivers seemed to help me the most. Also, if you are going to change the usb drivers you have, reboot between changes. Fastboot can be challenging, but you are on the right tack.