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.
Related
Dear all, thanks in advance to anyone who will take the time to read about my issue.
Yesterday I connected my Oneplus 2 (stock) to the laptop because I wanted to download my pictures, the phone has been recognized correctly but, as soon as I set on the phone the MTP the phone freezed.
I tried to reboot but all I had was just a vibration, no recovery, no fastboot, nothng.
I did a bit of searching and I found an unbrick guide (MSM8994DownloadTool.exe), although the procedure arrived correctly to the end, the phone rebooted in fastboot mode with a complete black screen.
I connected to my PC and I tried some fastboot commands and they worked:
fasboot devices
fastboot oem device-info
Since fastboot was working I tried to unlock the bootloader to install TWRP and then proceed with the ROM.
Unfortunately the command fastboot oem unlock FAILED (remote: oem unlock is not allowed)
Now I am stuck in this situation, since being the unlock not allowed, I can't flash anything.
Any suggestion?
Francesco
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.
So I screwed up and neglected to flash copypartitions-AB.zip and now my g7 play is stuck in a locked fastboot.
I have tried this thread, pulled out an old laptop with Windows 7 32-bit for it. https://forum.xda-developers.com/t/...der-stuck-in-fastboot-unable-to-boot.3917792/
LMSA doesn't detect the phone. So I try RSD Lite, and I get "Failed flashing process. 2/29 oem fb_mode_set - > Phone returned FAIL."
Try XML to BAT converter, it spits out a bunch of "permission denied" or "invalid partition name" errors.
Tried to unlock this locked bootloader, start with "fastboot oem get_unlock_data" and it spits out "read datablock error". So I just tried to use the same unlock key I used before installing Arrow OS, but it says "<bootloader> feature disabled".
Afterwards I tried this thread: https://forum.xda-developers.com/t/need-a-loader-file-to-unbrick-moto-g7.3938342
I made my sdcard, put it inside the phone and booted it up to the same exact thing, nothing actually changed. I realized after this I needed to be in EDL mode for it, and I can't find any fastboot command to access EDL mode. I tried a modified fastboot that said it would let me reboot to EDL mode, but it just threw an unknown command error.
Found this thread: https://forum.xda-developers.com/t/ultimate-guide-how-to-unbrick-your-moto-g6-plus.3862927/ except I downloaded the blankflash for g7 play from lolinet.com. But the blankflash just hangs on "waiting for device". Tried on Windows 7, Windows 10 and Linux. So now I'm just stumped on this. Does anyone have any suggestions to fix my g7 play?
EDIT: For anyone having this issue, I fixed it. There actually IS a command to enter EDL mode- "fastboot oem blankflash". No mention of it in the blankflash thread unfortunately but I finally found it. You can probably use either the blankflash method or loader method. Though I still couldn't get blankflash to work on Windows 10, it worked on a Linux Mint live usb
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