I've been trying for awhile now to unlock the bootloader on my AGM M5. It is running on a simplified Android 8.1. I've enabled USB debugging and have enabled Bootloader Unlocking in settings. ADB works fine but I cannot get the bootloader to unlock when I run the following commands.
C:\platform-tools>adb reboot bootloader
C:\platform-tools>fastboot oem unlock
...
FAILED (remote: unknown command)
finished. total time: 0.000s
C:\platform-tools>fastboot flashing unlock
...
FAILED (remote: unknown command)
finished. total time: -0.000s
I've tried running them from several different devices. Windows 7, Windows 10, and Raspberry Pi. But they all gave me very similar results.
If someone could give me some help it would be great. I'll mention right here that my ending goal is to install Postmarket OS. So if this is totally an unnecessary step please let me know. The reason for this step was I was trying to get a boot.img from the device and I wanted to install TWRP. But I was running up against every direction it tried and all my research was yielding very little as it seems that my M5 is not a very popular device.
Related
So 10 hours ago I decided I wanted to root my phone to install some apps and maybe even a cool ROM.
I read that the first step is to unlock the bootloader. I have trying my hardest to do this first step for 10 hours.
I've read 4-5 different tutorials twice on xda.
My phone is:
HTC One A9(hiae), bought in Sweden
hTc download mode
*** LOCKED ***
htc_hiaeuhl PVT S-ON
LK-1.0.0.000
[email protected]
OpenDSP-7.8.2.00197-8952_1228
OS-1.56.401.70
Jan 22 2016....
I have tried the normal way through htcdev.com even had the Unlock_code.bin at one point. But I had to reinstall all drivers twice to get it.
I have tried using the WinDroid Toolkit, no better than the manual way.
I got my hard earned token ID through both ways.
I find that every time I want to use fasstboot to send over a file i.e. "fastboot flash recovery twrp.img" hTc download mode is stuck at Start download, like I need to confirm it but can't because the command failed. The same goes for the Unlock_code.bin, can't send it over.
Code:
C:\adb>fastboot devices
HT5AVBE04449 fastboot
C:\adb>fastboot flash unlocktoken Unlock_code.bin
target didn't report max-download-size
sending 'unlocktoken' (0 KB)...
FAILED (command write failed (Unknown error))
finished. total time: 0.003s
I can get past this next problem temporarily by reinstalling all drivers, tedious.
Code:
C:\adb>fastboot oem get_identifier_token
...
FAILED (command write failed (Unknown error))
finished. total time: 5.002s
Possible problems:
hTc download mode: I need to accept the download before fastboot give up, instant.
Win10: Bad OS for this?
USB connectors: Not enough power? Some other USB devices don't work here normally.
HTC Sync Manager: I've not bother installing the software.
Solution
I've made it;
I'm not sure if I was in the real download mode at the time, but that might have been it.
Also this time I redid everything, deleted all the drivers correctly and installed via Universal Naked Drivers
Hello,
Did you check OEM unlocking to allow the bootloader to be unlocked in Settings/Developper options (hidden by default, appears when you tap Build number 10x in Setting/About/ Software information/More/ Build number) ?
ouioui01 said:
Hello,
Did you check OEM unlocking to allow the bootloader to be unlocked in Settings/Developper options (hidden by default, appears when you tap Build number 10x in Setting/About/ Software information/More/ Build number) ?
Click to expand...
Click to collapse
For my phone it is 8 taps and yes. Every time I start a new Android I do a OEM unlock.
But I might be correct to change USB connector.
So I've pretty much hit a wall. I have unlocked bootoader, and everytime I try to enter into factory resetting via volume + power button, it'll boot into "your device is booting now..." and it'll stay there. Same thing if I try to do it via the settings.
Whenever I try to install custom recovery or anything, I get this message.
C:\adb>fastboot flash recovery TWRP-CN.img
target reported max download size of 471859200 bytes
sending 'recovery' (29218 KB)...
OKAY [ 0.789s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.804s
I've tried all sorts of twrp files. My phone has locked me out of changing anything from adb commands it seems. How do I fix this?
My FRP is also locked, if that matters. I've tried to delete all accounts from my phone, as well as the "find my phone" option.
I'm on Anroid 7, EMUI 5.
C:\Users\amira\AppData\Local\Android\sdk\platform-tools>adb reboot bootloader
C:\Users\amira\AppData\Local\Android\sdk\platform-tools>fastboot devices
73QDU16B22001173 fastboot
C:\Users\amira\AppData\Local\Android\sdk\platform-tools>fastboot format userdata
FAILED (remote: Command not allowed)
C:\Users\amira\AppData\Local\Android\sdk\platform-tools>fastboot format cache
FAILED (remote: Command not allowed)
OEM is greyed out in the developer settings, I can't activate it or decative.
Try the unlock command again for the bootloader. This worked for me even when it was unlocked before
TomboIa said:
Try the unlock command again for the bootloader. This worked for me even when it was unlocked before
Click to expand...
Click to collapse
C:\Users\amira\AppData\Local\Android\sdk\platform-tools>fastboot oem unlock 1031871703372236
...
FAILED (remote: Command not allowed)
finished. total time: 0.020s
Same thing. It doesn't allow me.
Zebieok said:
C:\Users\amira\AppData\Local\Android\sdk\platform-tools>fastboot oem unlock 1031871703372236
...
FAILED (remote: Command not allowed)
finished. total time: 0.020s
Same thing. It doesn't allow me.
Click to expand...
Click to collapse
Dont share your unlock key here, and are you sure that was your bootloader unlock keys.
Frp lock means your bootloader is locked.
FRP lock is a security action, for remove them you must boot a device and remove all google accounts.
Unfortunately this casw happened to me, when i want factory reset my phone, his dead and i cant boot it again just fastboot work but FRP LOCK activate and i cant flash any thing, give error command not allowed, in last i have to go to repair services, and they do this with hard box (maybe chimera or sigma.. Or other).
If you can boot your device you can do any thing, but if your device get bootloop go to services center.
Hi,
I'v got used Razer phone today with Oreo 8.1, tried to unlock boot but it failed. Commands I've ran so far (debug and oem unlock both on)
adb reboot bootloader
got the download mode
android bootloader interface version 11 driver from google.
fastboot -i 0x1532 devices
xxx40xxxx fastboot (xx are numbers)
then
fastboot -i 0x1532 flashing unlock
...
FAILED (command write failed (No error))
finished. total time: 0.004s
on the phone download mode words disappeared and no driver appear in the PC
also tried another root method with posted here in XDA for Oreo but still not working.
Please I need help as I bought the phone to root and enjoy it
Majed
NeverMind, used another laptop and i was able to do it... I think AMD has some usb filters or something
This is a Pixel 3 (just to be clear). I have unlocked my bootloader successfully. I have installed the latest factory images (not OTA). I have re-allowed USB debugging. Downloaded the latest TWRP (twrp-3.3.0-0-blueline.img), and the zip (twrp-pixel3-installer-blueline-3.3.0-0.zip) placed the zip on the phone in the downloads folder. I reboot to bootloader. I open Win 10 command prompt (ADB and Fastboot is in PATH). Change directory to where TWRP img is saved. I type "fastboot boot twrp-3.3.0-0-blueline.img" I see:
Sending 'boot.img' (65536 KB) OKAY [ 0.286s]
Booting OKAY [ 3.407s]
Finished. Total time: 4.618s
My phone reboots but boots into system, not into TWRP.
I assume it is a NOOB mistake... I have looked at https://twrp.me/google/googlepixel3.html, and https://forum.xda-developers.com/pixel-3/development/twrp-3-2-3-0-pixel-3-t3861622, and https://www.xda-developers.com/google-pixel-3-unlock-bootloader-root-magisk/
Not sure what to do next as I would like to root. Any input would be appreciated.
Android 10 has no TWRP support for Pixel.
So how do I root the first time? Load an old factory image and then fastboot the TWRP image? Everything seems to say the same instructions, which I have tried to follow.
a_wolfie said:
So how do I root the first time? Load an old factory image and then fastboot the TWRP image? Everything seems to say the same instructions, which I have tried to follow.
Click to expand...
Click to collapse
Read the guide. Nothing to do with TWRP. https://forum.xda-developers.com/pixel-3/how-to/guide-patching-boot-img-magisk-canary-t3964359
fastboot oem unlock
...
FAILED (remote: unknown cmd.)
finished. total time: 0.007s
Have anxone a idia
QuentinAP said:
fastboot oem unlock
...
FAILED (remote: unknown cmd.)
finished. total time: 0.007s
Have anxone a idia
Click to expand...
Click to collapse
Did you enable "OEM unlocking" in settings? If "OEM unlocking" is grayed out, you probably have a Verizon or other variant that cannot be boot loader unlocked.
Oem is unlock
QuentinAP said:
Oem is unlock
Click to expand...
Click to collapse
Make sure you are using the latest Android Platform Tools from https://developer.android.com/studio/releases/platform-tools
Try different USB cables and different USB ports, or even a different computer. USB 2.0 ports seem to work better than 3.0 ports. Don't use any USB hubs or adapters.
Ich habe die neueste Version
Why are you trying to run "fastboot oem unlock"? That is only for older Pixel 2 XLs. What are you trying to do?
QuentinAP said:
fastboot oem unlock
...
FAILED (remote: unknown cmd.)
finished. total time: 0.007s
Have anxone a idia
Click to expand...
Click to collapse
Android 11 flashen custom rom
i have a gigaset gs 195
QuentinAP said:
Android 11 flashen custom rom
i have a gigaset gs 195
Click to expand...
Click to collapse
Sorry, I know nothing about that phone. This is a Pixel 3 forum. Try to find a forum for that phone or for the custom rom. Good luck.
Hello guys I tried to unlock bootloader but when I use the command fastboot oem unlock I get this error
...
FAILED (remote: Command not allowed)
finished. total time: 0.040s
Does anyone know how to fix it or can someone help me ?
(And yes I have enabled in dev setting unblock oem and USB debugging)