Not my first rodeo. I've rooted and used custom ROMs with every Android device I've owned since the HTC One back however long ago.
Most recent experience with Nexus 6P and Pixel XL.
Sister gave me a Nexus 5X to set up for dad, I'm trying to unlock the device to put the most current, clean, compatible version of stock Android on the device.
I had a huge problem getting the device to even register ADB/Fastboot. Now the phone is present in fastboot and adb devices, but it won't take any commands of any kind.
Preparatory steps:
-Developer options have OEM bootloader unlock enabled
-USB debugging enabled
-Device set to file transfer
-Running admin Powershell window
-Device is visible in fastboot and adb
Even though the device is visible I've been unable to bring it online.
All the following commands fail with "write to device failed (unknown error)":
-adb kill-server/start-server/connect serialort
-adb reboot bootloader
-adb reconnect offline
-fastboot flashing unlock
-fastboot oem unlock
-fastboot reboot bootloader
Thanks for the help.
Related
Hello,
I recently got a new Nexus 5X, I enabled USB Debugging and I tried using the CMD and it worked fin with commands like:
adb devices
adb reboot bootloader
However, once I boot into bootloader, I can't use any of the commands such as:
fastboot boot "C:\USERS\Path\To\TWRP.img"
it just gives this error:
downloading 'boot.img'...
OKAY [ 0.612s]
booting...
FAILED (remote: unlock device to use this command)
finished. total time: 0.627s
I installed the drivers so USB Debugging works on my PC. However USB Debugging doesn't work when I am in bootloader.
The only reason I want to do this is because I want to be able to enable "Multi Window" mode with out having a rooted device as I want to play games that don't allow a device to be rooted.
Thanks.
Your boot loader is locked by default that's why you get the rather helpful error output: "(remote: unlock device to use this command)" Always read error outputs and try to understand them .
What you'll have to do is to unlock your device , the great thing is that you have a Nexus phone so it will be easy.
Step 1: Go to settings -->> Developers options -->> OEM unlocking toggle it to ON.
Step 2: Reboot your device to fastboot mode
Step 3: Use the command
Code:
fastboot oem unlock
(This will wipe your device so back up your important files)
Step 4: Fastboot command will work now all of them be careful this freedom comes with responsibilities! You can easily soft brick your device.
A small consideration all the information I just gave you is easy to find! The search function on XDA is great and the pinned threads are gold :good:. It will also increase your understanding of the methods used and your device :highfive:
Xacky said:
Your boot loader is locked by default that's why you get the rather helpful error output: "(remote: unlock device to use this command)" Always read error outputs and try to understand them .
What you'll have to do is to unlock your device , the great thing is that you have a Nexus phone so it will be easy.
Step 1: Go to settings -->> Developers options -->> OEM unlocking toggle it to ON.
Step 2: Reboot your device to fastboot mode
Step 3: Use the command
Code:
fastboot oem unlock
(This will wipe your device so back up your important files)
Step 4: Fastboot command will work now all of them be careful this freedom comes with responsibilities! You can easily soft brick your device.
A small consideration all the information I just gave you is easy to find! The search function on XDA is great and the pinned threads are gold :good:. It will also increase your understanding of the methods used and your device :highfive:
Click to expand...
Click to collapse
Is this basically making the device rooted?
No, you are simply unlocking the bootloader so changes can be made. You won't be rooted until you have installed SuperSU. This is a good guide that will tell you everything: http://forum.xda-developers.com/nexus-5x/general/guides-how-to-guides-beginners-t3206930
I'm trying to unlock boot loader on my device but, when I reboot into boot loader I don't get an option for "fast boot". The options I do get are to reboot, reboot in download mode, reboot in boot loader, reboot in recovery, and shut down. Any ideas or maybe any precursors I've missed?
fastboot (and adb) needs to be installed and running from your PC, you reboot in to the phones bootloader then from a command prompt or terminal on your pc you issue fastboot commands to your phone which is connected by USB.
No luck
upperdecker said:
fastboot (and adb) needs to be installed and running from your PC, you reboot in to the phones bootloader then from a command prompt or terminal on your pc you issue fastboot commands to your phone which is connected by USB.
Click to expand...
Click to collapse
C:\Users\Delprete>adb reboot downloader
adb server is out of date. killing...
* daemon started successfully *
error: device '(null)' not found
is all I got. I downloaded and installed fastboot to the pc. The directions that I'm following from HTCDEV.com say to reboot into download mode and then load fastboot from the phone.
Use the adb and fastboot from here http://forum.xda-developers.com/showthread.php?t=2317790
Make sure you have usb debugging and oem unlocking enabled in developer options of your phone.
Once in download mode send the fastboot commands from your pc
So I've decided to root and customize my Z2 Force and want to unlock the bootloader to get TWRP installed. All device side settings are correct (USB Debug, OEM unlock etc.) in developer mode. ADB commands are working fine as I can see my SN when using ADB Devices command. I then reboot to the bootloader through ADB (adb reboot bootloader) and it works fine and my Z2 boots into the bootloader. Then I try to get the unlock code (fastboot oem unlock) and I get a message after trying to run the command: access denied. I started my CMD window using run as admin - no help. Installed ADB all over again with new generic drivers and moto drivers - no help.
I don't understand why I'm getting this message. I've unlocked and rooted all my phones over the years but they've all been HTC. Never messed with a moto phone like this before. I bought this phone directly through moto and it's suppose to be a carrier unlocked version. Anyone think this is a permalocked bootloader version - MODEL:XT1789-04 TYPE:M29E2
Any help is appreciated.
I am trying to flash the LineageOS on my Redmi Note 5 Pro (whyred). Initially, I used Windows 10 for the Xiaomi Unlock Tool. However, the Xiaomi Unlock Tool did not detect my device. So, I used this tool https://www.xiaomitool.com/V2/ to unlock my bootloader and it unlocked instantly. Now, I am using Ubuntu 21.04 (I am more comfortable using the command line here) (with android-tools-adb and android-tools-fastboot packages installed) to try to flash TWRP first.
When I connect my device, adb devices can recognise it. Then I use adb reboot bootloader to enter into fastboot. Now, fastboot devices can recognise it too. The screen of the phone shows the fastboot icon.
But, the problem comes here. I use fastboot flash recovery twrp.img and I get this error
FAILED (Write to device failed (No such device))
Click to expand...
Click to collapse
Now, when I use fastboot devices again. I don't see my device. Another change I see is press any key to shutdown written on the top left corner of the screen of my phone.
USB debugging, USB debugging security, OEM debugging are all enabled. Bootloader is unlocked (as I see in the settings). The phone is updated to latest MIUI version supported officially. And I used the same laptop and method to flash TWRP in a Redmi 3S (land) some time back.
(Posted the same question on android.stackexchange.com also) (https://android.stackexchange.com/questions/238996/redmi-note-5-pro-unable-to-flash-twrp)
Something else I experienced is that after randomly trying to get this right again and again, the command fastboot flash recovery twrp.img did not terminate or fail and got stuck.
So, this was a duplicate. I used the 5th method here and it worked for me. https://forum.xda-developers.com/t/everything-about-anti-roll-back-whyred.3816219/
I've been trying to unlock the Bootloader for this day and seems that my Honor 9X (4 GB RAM, 128 GB Storage with one SIM and one SD Card Slot) can't get past the bootloader unlock. Since I wanted to change the ROM due to upcoming Harmony OS Update that might happen anytime. Plus, it would be easier for me if there was an official TWRP Support, but even the creators behind the project does not even offer an official build for it.
I am not an expert at coding the TWRP for my device itself, and I am not a Windows User since I changed the primary OS to Linux (to Ubuntu 20.04). Can't install HiSuite (even with wine, for some reason) and even with an unlock code, I cannot unlock the bootloader.
Here is what I tried so far:
Reboot the device into the Bootloader by using ADB (my easiest way)
Check if Fastboot recognized the device
Ran fastboot flashing unlock, fastboot oem unlock (my short unlock code), fastboot oem unlock
Restarted Fastboot multiple times using fastboot reboot-bootloader
For every command, Fastboot showed me either "invalid command" or "command not allowed". I don't know if I am doing anything wrong, but for some reason, Fastboot gives me an error if there is some command included with the words "oem" or "flash(-ing)". Tried wiping user data and cache with Fastboot and even this is a problem. Any command that might manipulate my phone won't let me perform the task that I want my phone to do.
Is my phone bootloader protected, or what is the issue that I cannot unlock it nor modify any contents?
I might address that using ADB from Recovery is not an option from me. Starting recovery (from ADB and the boot combination) and checking with ADB if the device is found. Nothing. Going into eRecovery changed only a bit, but ADB recognized my device this time. When my phone is in eRecovery, ADB finds the device, but it is unauthorized, meaning I cannot perform any tasks. If I don't get to know what this issue is causing, then I'll throw my phone out of the window.
BeChris100 said:
I've been trying to unlock the Bootloader for this day and seems that my Honor 9X (4 GB RAM, 128 GB Storage with one SIM and one SD Card Slot) can't get past the bootloader unlock. Since I wanted to change the ROM due to upcoming Harmony OS Update that might happen anytime. Plus, it would be easier for me if there was an official TWRP Support, but even the creators behind the project does not even offer an official build for it.
I am not an expert at coding the TWRP for my device itself, and I am not a Windows User since I changed the primary OS to Linux (to Ubuntu 20.04). Can't install HiSuite (even with wine, for some reason) and even with an unlock code, I cannot unlock the bootloader.
Here is what I tried so far:
Reboot the device into the Bootloader by using ADB (my easiest way)
Check if Fastboot recognized the device
Ran fastboot flashing unlock, fastboot oem unlock (my short unlock code), fastboot oem unlock
Restarted Fastboot multiple times using fastboot reboot-bootloader
For every command, Fastboot showed me either "invalid command" or "command not allowed". I don't know if I am doing anything wrong, but for some reason, Fastboot gives me an error if there is some command included with the words "oem" or "flash(-ing)". Tried wiping user data and cache with Fastboot and even this is a problem. Any command that might manipulate my phone won't let me perform the task that I want my phone to do.
Is my phone bootloader protected, or what is the issue that I cannot unlock it nor modify any contents?
I might address that using ADB from Recovery is not an option from me. Starting recovery (from ADB and the boot combination) and checking with ADB if the device is found. Nothing. Going into eRecovery changed only a bit, but ADB recognized my device this time. When my phone is in eRecovery, ADB finds the device, but it is unauthorized, meaning I cannot perform any tasks. If I don't get to know what this issue is causing, then I'll throw my phone out of the window.
Click to expand...
Click to collapse
Huawei removed oem unlock comands in emui 10