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.
Related
A little background info...
I bought a used Nexus 5x and received it running the stock rom with the bootloader unlocked. Not sure if the device was properly unrooted and returned to stock. It was running 7.1.2 out of the box. Also, I took the latest security update a few days ago, before attempting to root. I wanted to do some homework on the device before attempting root. It's been a while since I rooted a device. And wanted to refresh my memory.
When I began the process, I was having trouble getting my windows 7 PC (64) to recognize the device via adb. I did a little reading and found out my driver's needed to be updated. After I updated them the device could now be recognized in adb (yes, I did remember to enable USB debugging). Verified working by returning serial number after typing the adb devices command. So I was confident I could no proceed with flashing TWRP via fastboot.
The problem...
So now that I verified adb working and talking to my device I then typed adb reboot bootloader to access the bootloader (cause I honestly didn't want to disconnect the device and have to press buttons). The device successfully booted into the bootloader. My next step was to type fastboot devices in the command line but this is where the problem I'm having is. The device is not recognized. So I unplugged the device from the PC, opened a new command window in the platform-tools folder where fastboot resides, rebooted the device back into the bootloader, reconnected the device to the PC and attempted the fastboot devices command again and nothing, no device. I execute the command fastboot flash recovery TWRP.xx.xxxx.img and the command window says waiting for device or something like that. I am not sure what steps to take next. I've never had a problem getting a PC to recognize a device in bootloader mode before. I am pretty sure my environments are set up correctly. Is it something with the device? Is there a way to correct this? I'm really lost as to what to do here. I cannot root because I cannot flash custom recovery because I cannot get my PC to recognize the device in fastboot. Please, any help is appreciated. I'm stumped.
Update.
Resolved. Used a different pc with a fresh adb environment. Worked on the first try to flash twrp and super su.
ADB command not recognized
Hi there, i'm facing a similar problem. My 5x went into bootloop. It was on stock. After going through XDA posts, I was preparing to flash stock rom once again to see if that works. So I installed in my Windows 10 - SDK tools / platform. We I used command for ADB the command prompt say device listed, but does not come up with serial number. But when fastboot command is given, it returns with a serial number.
My question is what went wrong? My PC also dose not shows 5x in the explorer, despite installing drivers.
I would also like to know how to enable USB debugging when your phone is bricked?
Looking forward to any suggestions.....thanks upfront....
hello
got the new version of Android (oreo).
I did the installation using adb. Once installed, the phone did not boot. Rebooted on the Google logo.
Now I can not do anything, Because it is not oem unlock and then I can not unlock the device, to flash again.
When using adb, I use adb devices, the device does not show me, but the fastboot devices I use show the serial device.
I searched and searched all the necessary possibilities in this case and did not know the driver, and apparently there was no problem.
Anything I want to do is require oem unlock and when I put this command in adb. It looks like:
FAILED (remote: oem unlock is not allowed).
And I can not do anything.
I have a LG G7 (LM-G710EM) with locked bootloader (stock version: V10h). I can easily enter fastboot mode. When I send the command "fastboot devices" (from a command window running ADB) it returns a list with the serial number of my device. So, it seems to work. But if I run the command "ADB devices" then I receive an empty list.
I don't want to unlock the bootloader. I just want to send specific commands required by some app to work properly without the need to be root. For example BetterBatteryStats requires the ADB command "adb -d shell pm grant com.asksven.betterbatterystats android.permission.DUMP".
I did already in my Moto G5+ with stock 7.0 (locked bootloader) and it worked. Is it possible to do the same in my LG G7 without unlocking the bootloader?
I just ran into a similar issue when giving BBS permissions. The solution that worked for me on my Verizon G7 was to select the USB connection notification then go to Photo Transfer mode. Right after that I got the authorization request on the phone to grant debugging permission to my computer. After that adb devices showed the phone. Hopefully that same tip helps.
ADB doesn't work in fastboot mode.
LameMonster82 said:
ADB doesn't work in fastboot mode.
Click to expand...
Click to collapse
at the end I discovered what was wrong. to enter ADB commands there is no need to enter fastboot mode, just connect the phone (already switched on) to the PC and accept the connection from that PC. Then opening a CMD window, it's enough to type the command "adb devices" and the serial number of the phone appears, telling that the phone is ready to accept adb commands. uhff!!
LG G7 ThinQ ADB devices - nothing appears, no matter what I try (all of the above and some other stuff!) I can only assume that Sprint have had this thing so locked up, even ADB can't help! Any ideas?
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