I am following all instructions on htcdev.com
I get the following error.
C:\android>fastboot oem get_identifier_token
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.009s]
finished. total time: 0.009s
Can anyone offer help????????????
I haven't seen that particular errror, but I'll offer what help I can.
Have you installed the htc drivers? If not you can download them from this post:
http://forum.xda-developers.com/showpost.php?p=20780879&postcount=1
You may want to make sure that HTC sync isn't running when you're trying to unlock. From my experience, it has been known to interfere.
hope this helps.
Also, not sure if you did this or not...(I did, but check and make sure you don't)
When copying and pasting the token id after you adb the get token id command make sure you don't copy the INFO text preceding each line. That may have mucked it up
I am an idiot. I misspelled the command it is identifier not indentifier
Related
Unlocking Your Nexus Q
To unlock your device
1. cd to platform-tools
2. Reboot to the bootloader - adb reboot bootloader
3. Unlock your device* (with fastboot tool type): fastboot oem unlock
*You will have to accept and erase all the user data on the tablet.
*You must run this as sudo in Linux
Credits to FadedLite (very similar steps)
Figuring out the rooting next
If you just need "su"....
1. Download su from your busybox installation from say Galaxy Nexus.
2. Download the modified clockworksmod for Nexus Q that this guy put together:
bliny.net/blog/post/How-to-Root-Nexus-Q-%28Temporarily%29.asp
3. Boot into that recovery image will give you write access to /system
4. adb push su into /system/xbin/su
Did you already have your nexus Q in debug mode? I do not have the slider button on my Nexus 7 to put it into debug mode. It's not recognized in "adb devices" or "fastboot devices"
EDIT ***
I found out that the USB Debugging menu in the Nexus Q app shows up when you turn on Developer Options in the Settings > Developer Options menu of Jellybean on the Nexus 7. You might want to test this as well on your variety of devices.
Just me that thinks this thing needs google TV?
nevermind it worked now
Stuck in oem unlock
hi, I hope there's still someone reading this, but I'm stuck in the oem unlock part can anybody help me? here's the output of my terminal
Code:
sh-3.2# fastboot oem unlock
...
(bootloader) oem unlock requested:
(bootloader) Unlocking forces a factory reset and could
(bootloader) open your device up to a world of hurt. If you
(bootloader) are sure you know what you're doing, then accept
(bootloader) in 5 seconds via 'fastboot oem unlock_accept'.
OKAY [ 0.025s]
finished. total time: 0.025s
sh-3.2# fastboot oem unlock_accept
...
(bootloader) oem unlock_accept ignored, not pending
FAILED (remote: oem unlock not requested)
finished. total time: 0.007s
thanks in advance.
took me a few tries to get it but it needs to be entered within five seconds of the first command
enriquealo said:
hi, I hope there's still someone reading this, but I'm stuck in the oem unlock part can anybody help me? here's the output of my terminal
Code:
sh-3.2# fastboot oem unlock
...
(bootloader) oem unlock requested:
(bootloader) Unlocking forces a factory reset and could
(bootloader) open your device up to a world of hurt. If you
(bootloader) are sure you know what you're doing, then accept
(bootloader) in 5 seconds via 'fastboot oem unlock_accept'.
OKAY [ 0.025s]
finished. total time: 0.025s
sh-3.2# fastboot oem unlock_accept
...
(bootloader) oem unlock_accept ignored, not pending
FAILED (remote: oem unlock not requested)
finished. total time: 0.007s
thanks in advance.
Click to expand...
Click to collapse
I tried to unlock my Q last night and no matter how fast I did it, I couldn't get past this screen.
silfa718 said:
I tried to unlock my Q last night and no matter how fast I did it, I couldn't get past this screen.
Click to expand...
Click to collapse
the easiest way, assuming you are running windows, is to enter the comands once, and then just use the up arrow key to do it again. also, you may want to be sure its not already unlocked "fastboot getvar unlocked" will return "yes" if unlocked
Hi there,
I'm having a bit of trouble relocking my bootloader. I've tried numerous times
using Hasoons toolkit but always get the following message.
< waiting for device >
...
(bootloader) Lock successfully...
(bootloader) TZ_HTC_SVC_DISABLE ret = 134086000 (0x7FDFD70)
FAILED (status read failed (Too many links))
finished. total time: 0.975s
C:\Users\Gary\Desktop\Amaze_All-In-One_Kit_V5.1\data>
Thanks,
Gary
It always gives me that message at the command prompt, just make sure the htc drivers are installed properly, which it sounds like they already are. It's relatively easy to do this without hansoons toolkit too, just download a adb_fastboot zip, extract the folder(such as the desktop), then run the following commands in command prompt
cd /path/to/adb/and/fastboot
fastboot oem lock
or for mac users
cd /path/to/adb/and/fastboot
./fastboot-mac oem lock
I really think you already got it all locked up tho, just boot into bootloader and read the the top line
I'm new at this so please bear with me, detailed explanations are most helpful.
My end goal is to edit the "build.prod" file in the /vendors directory without rooting the phone.
What steps have I taken so far:
On the Huawei Mate 10 Pro:
* Enabled Developer Options and set the following
- OEM Unlocking = enable
- USB debugging = enable
- verify apps over USB = disable
* Installed Andorid SDK and upaded my $PATH in windows appropriately.
* From powershell:
adb devices (device is found)
adb reboot bootloader (this puts the phone in "FASTBOOT&RESCUE MODE")
fastboot boot c:\xxxxx\twrp-3.2.1-0-blanc.img
Downloading 'boot.img' OKAY [ 0.232s]
booting FAILED (remote: Command not allowed)
fastboot flash recovery_ramdisk c:\xxxxx\twrp-3.2.1-0-blanc.img
Sending 'recovery_ramdisk' (8622 KB) OKAY [ 0.195s]
Writing 'recovery_ramdisk' FAILED (remote: Command not allowed)
fastboot boot c:\xxxxx\twrp_bla_alp_0.7.img
Downloading 'boot.img' OKAY [ 0.548s]
booting FAILED (remote: Command not allowed)
fastboot flash recovery_ramdisk c:\xxxxx\twrp_bla_alp_0.7.img
Sending 'recovery_ramdisk' (23542 KB) OKAY [ 0.599s]
Writing 'recovery_ramdisk' FAILED (remote: Command not allowed)
This is where I obtained the two twrp files:
twrp.me/huawei/huaweimate10pro.html
mega.nz/#!Zhc3mboB!OpMvPzMUAGPehDiqihi_gu6LViEltVECSIR743-KgrI
What am I doing wrong? Detailed steps would be appreciated since I have a learning curve, thank you.
ikolbyi said:
I'm new at this so please bear with me, detailed explanations are most helpful.
My end goal is to edit the "build.prod" file in the /vendors directory without rooting the phone.
What steps have I taken so far:
On the Huawei Mate 10 Pro:
* Enabled Developer Options and set the following
- OEM Unlocking = enable
- USB debugging = enable
- verify apps over USB = disable
* Installed Andorid SDK and upaded my $PATH in windows appropriately.
* From powershell:
adb devices (device is found)
adb reboot bootloader (this puts the phone in "FASTBOOT&RESCUE MODE")
fastboot boot c:\xxxxx\twrp-3.2.1-0-blanc.img
Downloading 'boot.img' OKAY [ 0.232s]
booting FAILED (remote: Command not allowed)
fastboot flash recovery_ramdisk c:\xxxxx\twrp-3.2.1-0-blanc.img
Sending 'recovery_ramdisk' (8622 KB) OKAY [ 0.195s]
Writing 'recovery_ramdisk' FAILED (remote: Command not allowed)
fastboot boot c:\xxxxx\twrp_bla_alp_0.7.img
Downloading 'boot.img' OKAY [ 0.548s]
booting FAILED (remote: Command not allowed)
fastboot flash recovery_ramdisk c:\xxxxx\twrp_bla_alp_0.7.img
Sending 'recovery_ramdisk' (23542 KB) OKAY [ 0.599s]
Writing 'recovery_ramdisk' FAILED (remote: Command not allowed)
This is where I obtained the two twrp files:
twrp.me/huawei/huaweimate10pro.html
mega.nz/#!Zhc3mboB!OpMvPzMUAGPehDiqihi_gu6LViEltVECSIR743-KgrI
What am I doing wrong? Detailed steps would be appreciated since I have a learning curve, thank you.
Click to expand...
Click to collapse
Installing TWRP is the easiest thing in the world. If you're having trouble, you don't know what you're doing. You lack experience. Take care, there's brick there's no way to recover
Enviado de meu BLA-L29 usando o Tapatalk
ChaseRxx said:
Installing TWRP is the easiest thing in the world. If you're having trouble, you don't know what you're doing. You lack experience. Take care, there's brick there's no way to recover
Enviado de meu BLA-L29 usando o Tapatalk
Click to expand...
Click to collapse
"Installing TWRP is the easiest thing in the world. If you're having trouble, you don't know what you're doing. "
- The reason for the post asking for help.
"You lack experience. Take care, there's brick there's no way to recover"
- Why bother post an insult, silence would have been more professional.
ikolbyi said:
"Installing TWRP is the easiest thing in the world. If you're having trouble, you don't know what you're doing. "
- The reason for the post asking for help.
"You lack experience. Take care, there's brick there's no way to recover"
- Why bother post an insult, silence would have been more professional.
Click to expand...
Click to collapse
GL!
Enviado de meu BLA-L29 usando o Tapatalk
ikolbyi said:
I'm new at this so please bear with me, detailed explanations are most helpful.
My end goal is to edit the "build.prod" file in the /vendors directory without rooting the phone.
What steps have I taken so far:
On the Huawei Mate 10 Pro:
* Enabled Developer Options and set the following
- OEM Unlocking = enable
- USB debugging = enable
- verify apps over USB = disable
* Installed Andorid SDK and upaded my $PATH in windows appropriately.
* From powershell:
adb devices (device is found)
adb reboot bootloader (this puts the phone in "FASTBOOT&RESCUE MODE")
fastboot boot c:\xxxxx\twrp-3.2.1-0-blanc.img
Downloading 'boot.img' OKAY [ 0.232s]
booting FAILED (remote: Command not allowed)
fastboot flash recovery_ramdisk c:\xxxxx\twrp-3.2.1-0-blanc.img
Sending 'recovery_ramdisk' (8622 KB) OKAY [ 0.195s]
Writing 'recovery_ramdisk' FAILED (remote: Command not allowed)
fastboot boot c:\xxxxx\twrp_bla_alp_0.7.img
Downloading 'boot.img' OKAY [ 0.548s]
booting FAILED (remote: Command not allowed)
fastboot flash recovery_ramdisk c:\xxxxx\twrp_bla_alp_0.7.img
Sending 'recovery_ramdisk' (23542 KB) OKAY [ 0.599s]
Writing 'recovery_ramdisk' FAILED (remote: Command not allowed)
This is where I obtained the two twrp files:
twrp.me/huawei/huaweimate10pro.html
mega.nz/#!Zhc3mboB!OpMvPzMUAGPehDiqihi_gu6LViEltVECSIR743-KgrI
What am I doing wrong? Detailed steps would be appreciated since I have a learning curve, thank you.
Click to expand...
Click to collapse
Check for all drivers and also is your bootloader unlocked cuz it says there remote: Command not allowed that probably means that something is probably blocking it on the phone side
LLoTE said:
Check for all drivers and also is your bootloader unlocked cuz it says there remote: Command not allowed that probably means that something is probably blocking it on the phone side
Click to expand...
Click to collapse
Settings -> Developer options -> OEM unlocking (Allow the bootloader to be unlocked) -> checked on.
Am I missing something else?
If I try the following command in fastboot I receive the following error:
fastboot oem unlock
FAILED (remote: check password failed!)
Finished. Total time: 0.005s
ikolbyi said:
Settings -> Developer options -> OEM unlocking (Allow the bootloader to be unlocked) -> checked on.
Am I missing something else?
If I try the following command in fastboot I receive the following error:
fastboot oem unlock
FAILED (remote: check password failed!)
Finished. Total time: 0.005s
Click to expand...
Click to collapse
Welp
---------- Post added at 03:31 PM ---------- Previous post was at 03:30 PM ----------
ikolbyi said:
Settings -> Developer options -> OEM unlocking (Allow the bootloader to be unlocked) -> checked on.
Am I missing something else?
If I try the following command in fastboot I receive the following error:
fastboot oem unlock
FAILED (remote: check password failed!)
Finished. Total time: 0.005s
Click to expand...
Click to collapse
You need to first unlock the bootloader it's not as simple as that search online how to unlock it
LLoTE said:
Welp
---------- Post added at 03:31 PM ---------- Previous post was at 03:30 PM ----------
You need to first unlock the bootloader it's not as simple as that search online how to unlock it
Click to expand...
Click to collapse
okay - steps?
ikolbyi said:
okay - steps?
Click to expand...
Click to collapse
Search on YouTube or on google idk how exactly my friend had a mate 10 pro i didnt
LLoTE said:
Search on YouTube or on google idk how exactly my friend had a mate 10 pro i didnt
Click to expand...
Click to collapse
That's my problem - either the steps don't apply to the Hauewei Mate 10 Pro or the individuals posting skip steps and I'm unable piece together the missing information.
ikolbyi said:
That's my problem - either the steps don't apply to the Hauewei Mate 10 Pro or the individuals posting skip steps and I'm unable piece together the missing information.
Click to expand...
Click to collapse
Yea man post are really disinformational im sorry ill ask my friend how he unlocked it
LLoTE said:
Yea man post are really disinformational im sorry ill ask my friend how he unlocked it
Click to expand...
Click to collapse
Thank you. I'm new at this and learning.
ikolbyi said:
That's my problem - either the steps don't apply to the Hauewei Mate 10 Pro or the individuals posting skip steps and I'm unable piece together the missing information.
Click to expand...
Click to collapse
look at this one
Toggling OEM unlocking in developer options is not enough, as that simply enables the ability to unlock your bootloader within fastboot. You need to retrieve a bootloader unlock code either directly from Huawei or a third party. I believe there is a guide for it in the guides sub-forum.
LLoTE said:
look at this one
Click to expand...
Click to collapse
I did't need to download the tool but the second half the video answered my questions. I was able to obtain the 'key' from Huawei outlined in the video then in fastboot mode:
"adb oem unlock <the key from Huawei>"
And it unlocked my bootloader reformatting it. Now step 2 - editing the file.
ikolbyi said:
I did't need to download the tool but the second half the video answered my questions. I was able to obtain the 'key' from Huawei outlined in the video then in fastboot mode:
"adb oem unlock <the key from Huawei>"
And it unlocked my bootloader reformatting it. Now step 2 - editing the file.
Click to expand...
Click to collapse
And how will you edit it? You'll root the phone or?
LLoTE said:
And how will you edit it? You'll root the phone or?
Click to expand...
Click to collapse
Now that the boot loader is unlocked, I edited the /vendor/build.prop file using this method:
with phone in fastboot mode (from laptop computer connected to phone via USB , phone in developer mode)
adb reboot bootloader
Next step was to install TWRP:
fastboot flash recovery_ramdisk c:\xxxxx\twrp-3.2.1-0-blanc.img
fastboot reboot (immediately unplug phone from USB and hold down the high volume button until you see Huawei logo)
When in TWRP manually mount /vendor then reconnected device to USB connected to computer.
executed the following commands:
adb pull /vendor/build.prop C:\downloads\build.prop
/vendor/build.prop: 1 file pulled. 0.1 MB/s (4065 bytes in 0.026s)
adb push C:\downloads\build.prop /vendor/build.prop
C:\downloads\build.prop: 1 file pushed. 0.2 MB/s (4097 bytes in 0.018s)
it worked. I added the line "ro.config.hw_volte_dyn=false"
reboot and it came up with the feature.
Your missing piece helped me get this completed, thank you LLoTE
ikolbyi said:
Now that the boot loader is unlocked, I edited the /vendor/build.prop file using this method:
with phone in fastboot mode (from laptop computer connected to phone via USB , phone in developer mode)
adb reboot bootloader
Next step was to install TWRP:
fastboot flash recovery_ramdisk c:\xxxxx\twrp-3.2.1-0-blanc.img
fastboot reboot (immediately unplug phone from USB and hold down the high volume button until you see Huawei logo)
When in TWRP manually mount /vendor then reconnected device to USB connected to computer.
executed the following commands:
adb pull /vendor/build.prop C:\downloads\build.prop
/vendor/build.prop: 1 file pulled. 0.1 MB/s (4065 bytes in 0.026s)
adb push C:\downloads\build.prop /vendor/build.prop
C:\downloads\build.prop: 1 file pushed. 0.2 MB/s (4097 bytes in 0.018s)
it worked. I added the line "ro.config.hw_volte_dyn=false"
reboot and it came up with the feature.
Your missing piece helped me get this completed, thank you LLoTE
Click to expand...
Click to collapse
No problem man
Hello there,
To prevent spam, you must have a higher post count in order to make a new thread in this development section.�But feel free to make new thread in the non-development sections like General, Q&A, etc. Thanks for your understanding!
Click to expand...
Click to collapse
To prevent spam on the XDA forums, ALL new users prevented from posting outside links in their messages. After approximately 10 posts, you will be able to post outside links. Thank you for understanding!
Click to expand...
Click to collapse
So I post here, sorry if it's not a good idea.
I have bought a AUS Zenfone M1 Pro, reference X00TD. I want to use LineageOS in it, it's supported (https:// wiki.lineageos.org/devices/X00TD/ => I cannot post with links, see message above).
I use Ubuntu 18.04 64 bits, up-to-date.
I follow these steps, I unlock successfully the phone, with the apk of Asus :
Code:
$ fastboot oem device-info
(bootloader) Verity mode: true
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: true
(bootloader) Bootloader version: ZB601KL-0x01-20190216132609
OKAY [ 0.001s]
Finished. Total time: 0.001s
(I don't know why there is "ZB601KL" reference, Lineage website says X00TD.
But I'm stuck in unlocking the bootloader. I run the command :
Code:
fastboot flash recovery <recovery_filename>.img
I see the message "sending recovery (58108 kb)" with some space before the cursor, but nothing else happens. This command never ends, because after a long while, I see this :
$ fastboot flash recovery twrp-3.2.3-0-X00TD-20180814.img
Sending 'recovery' (58108 KB) FAILED (remote: 'unknown command')
fastboot: error: Command failed
Click to expand...
Click to collapse
I tried with the last version (to my knowledge) of TWRP : twrp-3.3.1-0-X00T-20190526.img
I also tried with others versions, with links found here and in others places :
- twrp-3.2.3-0-X00TD-20180814.img
- twrp-3.2.3-0-X00T-20180902.img
- twrp-3.2.2-1-X00TD-20180727.img
I have the same issue with each image.
The command :
Code:
fastboot device
returns well an id of the phone, so it's well recognized.
I tried with and without sudo command.
Here I don't know what I can do to solve this. I hope you can help me.
Thank you for your hekp !
I'm still looking for help
When I try to use the Unlock Tool by Xiaomi, it just tells me "Request parameter error". I've tried multiple other methods thru adb, they all dont work for me. Can anyone help me here?
Tried "fastboot oem unlock" which resulted in this
FAILED (remote: Token Verify Failed, Reboot the device
)
finished. total time: 0.011s
then tried "fastboot oem unlock_critical" which resulted in
FAILED (remote: Token Verify Failed, Reboot the device
)
finished. total time: 0.013s
Merowo12 said:
When I try to use the Unlock Tool by Xiaomi, it just tells me "Request parameter error". I've tried multiple other methods thru adb, they all dont work for me. Can anyone help me here?
Tried "fastboot oem unlock" which resulted in this
FAILED (remote: Token Verify Failed, Reboot the device
)
finished. total time: 0.011s
then tried "fastboot oem unlock_critical" which resulted in
FAILED (remote: Token Verify Failed, Reboot the device
)
finished. total time: 0.013s
Click to expand...
Click to collapse
It can help you: https://c.mi.com/thread-2262302-1-0.html
https://c.mi.com/thread-1857937-1-1.html
https://forum.xda-developers.com/t/cant-unlock-request-parameter-error.4009589/