I'm trying to unlock the bootloader of my One M9 so that I can use Sunshine and get S Off. In the end I'm trying to convert it to the dev version. I've unlocked the bootloaders of my M7 and M8 before this but for some reason it is giving me an error this time. It says "FAILED (remote: unknown command)" every time I try. I've tried with sync manager install and uninstalled. I really have no idea why this is happening. I tried to get the tokens on the M7 and M8 with the same drivers to test them and everything went as usual. Can anyone help me with this?
Thanks
Schmerg said:
I'm trying to unlock the bootloader of my One M9 so that I can use Sunshine and get S Off. In the end I'm trying to convert it to the dev version. I've unlocked the bootloaders of my M7 and M8 before this but for some reason it is giving me an error this time. It says "FAILED (remote: unknown command)" every time I try. I've tried with sync manager install and uninstalled. I really have no idea why this is happening. I tried to get the tokens on the M7 and M8 with the same drivers to test them and everything went as usual. Can anyone help me with this?
Thanks
Click to expand...
Click to collapse
I think you need to be in download mode for the fastboot commands to work.
dratsablive said:
I think you need to be in download mode for the fastboot commands to work.
Click to expand...
Click to collapse
Wow thank you so much. I didn't know I needed to be in download mode.
Much appreciated!
I found that in Download mode I couldn't get the identifier token for some reason. I had to boot into the bootloader then use "fastboot oem rebootRUU" to get into RUU mode. THEN I was able to get the identifier token, but I couldn't flash the Unlock file unless I was in Download mode. A little more convoluted then the M8
navalynt said:
I found that in Download mode I couldn't get the identifier token for some reason. I had to boot into the bootloader then use "fastboot oem rebootRUU" to get into RUU mode. THEN I was able to get the identifier token, but I couldn't flash the Unlock file unless I was in Download mode. A little more convoluted then the M8
Click to expand...
Click to collapse
How do I boot into boot loader? I'm only getting command not found in terminal every time I type in the fast boot command...
elusivepuma said:
How do I boot into boot loader? I'm only getting command not found in terminal every time I type in the fast boot command...
Click to expand...
Click to collapse
easy way is enable developer options on the phone
turn on usb debugging hook phone to PC
from command prompt on PC type adb reboot download
navalynt said:
I found that in Download mode I couldn't get the identifier token for some reason. I had to boot into the bootloader then use "fastboot oem rebootRUU" to get into RUU mode. THEN I was able to get the identifier token, but I couldn't flash the Unlock file unless I was in Download mode. A little more convoluted then the M8
Click to expand...
Click to collapse
Hello there. I am not able to get identifier token both in bootloader and download mode. I tried adb reboot bootloader first, successfully entered in bootloader. After typing fastboot oem_get_identifier_token
stuck in error FAILED (remote : unknown command)
and same as for adb reeboot download mode.
What should i do now?
I have HTC Desire 626s.
Thanks in advance
aashish981 said:
Hello there. I am not able to get identifier token both in bootloader and download mode. I tried adb reboot bootloader first, successfully entered in bootloader. After typing fastboot oem_get_identifier_token
stuck in error FAILED (remote : unknown command)
and same as for adb reeboot download mode.
What should i do now?
I have HTC Desire 626s.
Thanks in advance
Click to expand...
Click to collapse
Command is wrong. Try fastboot oem get_identifier_token
Hi guys,
im trying to unlock to the bootloader. I use the command "fastboot oem get_identifier_token" from the website "htcdev". But i get no token, there is showing following issue:
C:\Fastboot>fastboot oem get_identifier_token
...
(bootloader) [KillSwitch] : /dev/block/bootdevice/by-name/frp
(bootloader) [KillSwitch] Last Byte is 0X00, disable unlock
(bootloader) [KillSwitch] oem unlock Turn Off!
OKAY [ 0.100s]
finished. total time: 0.101s
my htc one m9 please help me
<<<< Identifier Token Start >>>>
1E273FDE078CCB771DFA5E6A826083BF
2D6F6C1A962A39E4A133A5B95214CA0C
F856D703BD183517577291FAB5F6A6B4
5307F3888E6CA0C866411B1072588567
F0D67ED66548E31EA4332612B2DA089C
8A96B3918CC122D63AC944BB7E790F47
490E35E4BF24C7956207A709BF6B33C0
7DD92A84CACAF4487F4DFE44D11A4C9B
1D6366A63326C6DBE442CE57A92CA767
F7F09206F75E6E2B606759953F259B23
2C9D86AFCE30EEAE3021231698C1A624
0DCD40A03C61A8CF4D809BC1DAAB589B
D16914018ADBA0029C8CB95A8C2D6513
F49A75ABE7A574BF288E16C50C98870B
8909B333B14FC6F60F977A301919DF6A
83192A7E07B091DA044374F432BB1B82
<<<<< Identifier Token End >>>>>
send me the Unlock_code.bin for my email.
[email protected]
Related
I'm trying to de-softbrick an Evo3D for an aquaintance, and I've run out of ideas, so any help this forum is willing to offer is muy apreciada.
Info about phone:
UNLOCKED
HBOOT 1.5
S-ON
Phone will not boot to OS. Phone will boot into hboot. Recovery menu does not function, it shows the fastboot menu instead. Selecting Fastboot takes you to the Fastboot menu, which seems to work fine. Factory Reset option takes you to Fastboot menu.
Initially phone seems to load PG86IMG.zip for flashing, but when the blue loading meter fills up, it says "parsing PG86IMG.zip" for a second and then boots me back to the hboot menu, without asking me to install the file. I've tried both the stock rooted and unrooted zips.
Tried plugging the phone into my computer and running the RUU exe. It will not detect the phone, which I'm guessing is because the phone won't boot into the OS. Also, phone does not appear to respond to any adb or fastboot commands (tried doing adb pull and fastboot reboot, neither worked).
EDIT: Now the phone is detected by the RUU, but I get a 155 error code, and the phone says "Security fail!" and "Update fail!"
Again, any help is appreciated.
What happens when you try to run any fastboot command?
xxjrkkrjxx said:
What happens when you try to run any fastboot command?
Click to expand...
Click to collapse
I get < waiting for device > and it just sits there forever.
try this
Enter FASTBOOT
Open command prompt in your computer
Relock your device by typing "fastboot oem lock" , device will reboot.
Enter FASTBOOT again (you will see *** RELOCKED ***)
Apply the RUU.
RUU_Shooter_S_Sprint_WWE_2.08.651.3_Radio_0.97.10. 0808_NV_SPCS_1.31_003_release_219445_signed
http://www.filefactory.com/file/cfd5...445_signed.exe
Your device will be back to stock rom unrooted
Mr.Esp said:
try this
Enter FASTBOOT
Open command prompt in your computer
Relock your device by typing "fastboot oem lock" , device will reboot.
Enter FASTBOOT again (you will see *** RELOCKED ***)
Apply the RUU.
RUU_Shooter_S_Sprint_WWE_2.08.651.3_Radio_0.97.10. 0808_NV_SPCS_1.31_003_release_219445_signed
http://www.filefactory.com/file/cfd5...445_signed.exe
Your device will be back to stock rom unrooted
Click to expand...
Click to collapse
Here's the output of the fastboot oem lock (it's responding to fastboot commands now YAY!):
Code:
C:\android-sdk\platform-tools>fastboot oem lock
...
(bootloader) Lock successfully...
(bootloader) TZ_HTC_SVC_DISABLE ret = 66977136 (0x3FDFD70)
FAILED (status read failed (Too many links))
finished. total time: 0.936s
It does show the phone as relocked now, but right below the pink "***RELOCKED*** I also have ***SECURITY WARNING***. The security warning part seems to go away if I boot into hboot with the sd card removed.
EDIT: RUU worked on the second try after this. Thanks a ton!
I'm having the same issue but the link to the RUU does not work anymore, can anyone repost?
martymania85 said:
I'm having the same issue but the link to the RUU does not work anymore, can anyone repost?
Click to expand...
Click to collapse
http://tinyurl.com/6tauv3b
billdozer357 said:
Here's the output of the fastboot oem lock (it's responding to fastboot commands now YAY!):
Code:
C:\android-sdk\platform-tools>fastboot oem lock
...
(bootloader) Lock successfully...
(bootloader) TZ_HTC_SVC_DISABLE ret = 66977136 (0x3FDFD70)
FAILED (status read failed (Too many links))
finished. total time: 0.936s
It does show the phone as relocked now, but right below the pink "***RELOCKED*** I also have ***SECURITY WARNING***. The security warning part seems to go away if I boot into hboot with the sd card removed.
EDIT: RUU worked on the second try after this. Thanks a ton!
Click to expand...
Click to collapse
Does USB come up next to Fastboot? If so can you reflash CWM?
This phone has never been even mentioned on xda so there is nothing to search for.
Anyways i have gone thru some threads of similar phones and tried some one click root methods. They didnt work.
So i thought i should unlock the bootloader.
Just for the sake of it i tried to boot into recovery and was successful.
Then i started following those htcdev.com instruction which required me to go into the bootloader mode.
But whenever i try doing that it either:
-Remains stuck at htc logo screen (the 1st one and not the bootanimation)
-Boots normally
then i saw that i had to press this button release this after so many seconds and......
so just to be sure that im not making those silly mistakes i tried to go into bootloader thru adb which always remains stuck at the htc splash screen (htc - powered by android).
then i tried to go to recovery but now even that isnt possible.
so in short: i cant get into the bootloader so i cant unlock or root. I cant get into the recovery either. The phone otherwise is working pretty normal. But on trying to get into any modes i remain stuck at the 1st htc screen (and not the bootanimation) and then i have to remove the battery to get it booting normally.
It is HTC Desire 516 Dual sim and is on JB 4.3 (if u needed this)
and finally i got this log from a unlock tool if it makes it easier for you
adb: reboot-bootloader
adb out:
Reboot success!
fastboot: devices
fastboot out: 0123456789ABCDEF fastboot
fastboot: oem lock
fastboot timeout
lock_failed
adb: reboot-bootloader
adb out:
Reboot success!
fastboot: devices
fastboot out: 0123456789ABCDEF fastboot
fastboot: getvar version
fastboot out: version: 0.5
finished. total time: 0.003s
fastboot: getvar version-bootloader
fastboot out: version-bootloader:
finished. total time: 0.003s
fastboot: getvar version-main
fastboot out: version-main:
finished. total time: 0.003s
fastboot: getvar serialno
fastboot out: serialno: 0123456789ABCDEF
finished. total time: 0.003s
fastboot: getvar product
fastboot out: product: MSM8610
finished. total time: 0.003s
fastboot: getvar modelid
fastboot out: modelid:
finished. total time: 0.003s
fastboot: getvar cidnum
fastboot out: cidnum:
finished. total time: 0.003s
fastboot: getvar build-mode
fastboot out: build-mode:
finished. total time: 0.003s
fastboot: getvar boot-mode
fastboot out: boot-mode:
finished. total time: 0.003s
fastboot: getvar security
fastboot out: security:
finished. total time: 0.003s
fastboot: getvar imei
fastboot out: imei:
finished. total time: 0.003s
fastboot: oem get_identifier_token
fastboot timeout
get_device_info_failed
Click to expand...
Click to collapse
pls do help if u can :highfive: :fingers-crossed:
noone? @psych.half suggest anything?
T3snake said:
noone? @psych.half suggest anything?
Click to expand...
Click to collapse
Remove your battery before trying to boot into fastboot.
If you can't remove your battery, go to Settings->Power options And disable fast boot
dummie999 said:
Remove your battery before trying to boot into fastboot.
If you can't remove your battery, go to Settings->Power options And disable fast boot
Click to expand...
Click to collapse
yea tried that..
same result
btw volume up brings up recovery and down brings bootloaderr
is fastboot a different mode or u call bootloader mode and fastboot the same..?
T3snake said:
yea tried that..
same result
btw volume up brings up recovery and down brings bootloaderr
is fastboot a different mode or u call bootloader mode and fastboot the same..?
Click to expand...
Click to collapse
Yes fastboot and bootloader are the same
Have you tried booting into bootloader with "adb reboot bootloader"
Info
You are not alone !
Now can have all the stock files here .
dummie999 said:
Yes fastboot and bootloader are the same
Have you tried booting into bootloader with "adb reboot bootloader"
Click to expand...
Click to collapse
yea both recovery and bootloader isnt accessible by adb
joldisadrian said:
You are not alone !
Now can have all the stock files here .
Click to expand...
Click to collapse
but there are only kernel sources
T3snake said:
yea both recovery and bootloader isnt accessible by adb
Click to expand...
Click to collapse
How do you mean isn't accesible? What do you see when you type those commands? What is the output?
I have this device, and i booted it in fastboot mode successfully. Open ADB and type "adb reboot-bootloader", the phone will reboot and remain stuck in the boot logo (the first). Now open fastboot and type "fastboot devices" and it will be recognized. I can't unlock bootloader, because when i type "fastboot oem get_identifier_token" it remains stuck, and it's so annoying because i want to root this device, can you help me? :crying:
I'm having the same problem. The bootloader is not accessible. I tried all possible root methods but none work. Kinda regretting now buying this phone
dummie999 said:
How do you mean isn't accesible? What do you see when you type those commands? What is the output?
Click to expand...
Click to collapse
As I said it reboots but remains stuck at HTC logo until removal of battery
Sent from my SM-T211 using Tapatalk
AceXer said:
I have this device, and i booted it in fastboot mode successfully. Open ADB and type "adb reboot-bootloader", the phone will reboot and remain stuck in the boot logo (the first). Now open fastboot and type "fastboot devices" and it will be recognized. I can't unlock bootloader, because when i type "fastboot oem get_identifier_token" it remains stuck, and it's so annoying because i want to root this device, can you help me? :crying:
Click to expand...
Click to collapse
So since its stuck and we can't do anything
BTW we had an 110 mb update just a few days ago but since my phone can't get into recovery the final steps don't take place where it goes to recovery and finishes up(in my case it remains stuck at HTC logo so device remains as it was when I boot it normally)
Sent from my SM-T211 using Tapatalk
rakeshz said:
I'm having the same problem. The bootloader is not accessible. I tried all possible root methods but none work. Kinda regretting now buying this phone
Click to expand...
Click to collapse
Well if they gave us an app2sd feature I ccud forgive em a bit.
I contacted the customer service and when I mentioned a stuck up screen they immediately asked if I WS rooting. So maybe htc did it intentionally or maybe some1 fishy intervened or something
Sent from my SM-T211 using Tapatalk
T3snake said:
Well if they gave us an app2sd feature I ccud forgive em a bit.
I contacted the customer service and when I mentioned a stuck up screen they immediately asked if I WS rooting. So maybe htc did it intentionally or maybe some1 fishy intervened or something
Sent from my SM-T211 using Tapatalk
Click to expand...
Click to collapse
Yes, seriously we need the move to sd card feature. The whole reason of having a feature phone without being able to install any apps or big games sucks
rakeshz said:
Yes, seriously we need the move to sd card feature. The whole reason of having a feature phone without being able to install any apps or big games sucks
Click to expand...
Click to collapse
I calculated and found that u can get Max 1.7 GB free (as indicated by the mobile) but if u use mtp or reach 1.5 GB u will not be able to put anything more since there shud always be 200mb free
So we get only 1.5 GB after disabling all the preinstalled apps
Sent from my SM-T211 using Tapatalk
So I'm able to boot into fastboot mode, I'm able to boot into recovery mode. But how can we unlock the bootloader?
AceXer said:
So I'm able to boot into fastboot mode, I'm able to boot into recovery mode. But how can we unlock the bootloader?
Click to expand...
Click to collapse
Go to htcdev.com
If u can get into fastboot mode u can run some commands to get a token paste the token at the place indicated and follow the steps
Sent from my GT-S5282 using Tapatalk
T3snake said:
Go to htcdev.com
If u can get into fastboot mode u can run some commands to get a token paste the token at the place indicated and follow the steps
Sent from my GT-S5282 using Tapatalk
Click to expand...
Click to collapse
Yes, but this device isn't in the list, and when I type (in fastboot mode) "fastboot oem get_identifier_token" it stuck and three dots appear.
All command work, but if i type "oem" after "fastboot" (ex. "fastboot oem command list) it stuck with three dots. Help meeeee pleease!
AceXer said:
Yes, but this device isn't in the list, and when I type (in fastboot mode) "fastboot oem get_identifier_token" it stuck and three dots appear.
All command work, but if i type "oem" after "fastboot" (ex. "fastboot oem command list) it stuck with three dots. Help meeeee pleease!
Click to expand...
Click to collapse
Hi,
I have same device and same problems. I think I tried all solutions I've seen so far. I had HTC wildfire, Motorola XT530, Huawei Ascend G300, HTC Desire X, and I have some expirience rooting, but this phone makes me sick. Just sent an rage mail to HTC, saying that they made great little piece of hardware with software making it almost unusable. So far I tried SuperOneClick, RootGenius and adb root, but nothing works.
FASTBOOT ERROR "FAILED (remote: fastboot is lock, please run oem unlock with valid pa
on ANY fb command i get "FAILED (remote: fastboot is lock, please run oem unlock with valid password)"
ALSO after "fastboot oem unlock" i get:
---
and just a uncloseable shell box that is unresponsive ..iv flashed this device before and same error when any get unlock var or info command any ideas my device is a moto tc700x (is an old symbol\zebra now)
i never put a password in before i flashed my device for IoT and got a freeze during install now i cannot do anything w it even reflash recovery or zips i used previously used before?
any ideas anyone?
metalman1972 said:
on ANY fb command i get "FAILED (remote: fastboot is lock, please run oem unlock with valid password)"
ALSO after "fastboot oem unlock" i get:
---
and just a uncloseable shell box that is unresponsive ..iv flashed this device before and same error when any get unlock var or info command any ideas my device is a moto tc700x (is an old symbol\zebra now)
i never put a password in before i flashed my device for IoT and got a freeze during install now i cannot do anything w it even reflash recovery or zips i used previously used before?
any ideas anyone?
Click to expand...
Click to collapse
You can use "fastboot getvar all" cmd to check whether ur boot loader is locked
I bought the Asus ZenFone 8 Flip with the bootloader unlocked, it is not running a custom ROM. How do I lock the bootloader? Thank you
Try this with fastboot:
fastboot oem lock
However, this won't restore your warranty and you won't receive updates, since surely who has unlocked your device has used the official bootloader unlock tool which registers your serial number
maicol07 said:
Try this with fastboot:
fastboot oem lock
However, this won't restore your warranty and you won't receive updates, since surely who has unlocked your device has used the official bootloader unlock tool which registers your serial number
Click to expand...
Click to collapse
how do I go about something like that? I would only like to be on official software so how will I not be able to receive updates?
Kiribro02 said:
how do I go about something like that? I would only like to be on official software so how will I not be able to receive updates?
Click to expand...
Click to collapse
You won't get OTA updates, but you can still update manually downloading the zip from Asus website.
Unfortunately that's the price if you unlock the device (not only for Asus, a lot of other manufacturers (i.e. Sony) do this too)
maicol07 said:
You won't get OTA updates, but you can still update manually downloading the zip from Asus website.
Unfortunately that's the price if you unlock the device (not only for Asus, a lot of other manufacturers (i.e. Sony) do this too)
Click to expand...
Click to collapse
interesting... So I don't know how to lock the bootloader precisely. So I download the latest firmware from the Asus website, plug the phone into the computer run fastboot then what? Am I missing something?
Kiribro02 said:
interesting... So I don't know how to lock the bootloader precisely. So I download the latest firmware from the Asus website, plug the phone into the computer run fastboot then what? Am I missing something?
Click to expand...
Click to collapse
No, just follow these steps:
Make a backup of your phone!! Unlocking/Locking the bootloader erases all your data partition (so all your stuff will be gone!)
Install ADB on your PC if you don't have it (check how to install it: https://www.xda-developers.com/install-adb-windows-macos-linux/).
Plug in your device via USB with Debug USB setting enabled (in Developer Settings)
Open a terminal prompt on your PC
In the terminal run adb devices. If you see your device I the list then you're fine. Otherwise, you have mistaken something in the previous steps.
Run adb reboot fastboot (or adb reboot bootloader if it doesn't work) to reboot into fastboot mode
Run fastboot oem lock to lock the bootloader
Run fastboot reboot to reboot the system
Your device is now locked!
DISCLAIMER:
I'm not responsible of any data loss, damages and/or bricks you make to your device(s) by following this guide!
Click to expand...
Click to collapse
To update the system when a new version is out, since you won't receive OTAs:
Go to Zenfone 8 Flip support page: https://www.asus.com/Mobile/Phones/ZenFone/Zenfone-8-Flip/HelpDesk_Download/
Choose Android as OS and scroll down to "Firmware"
Download the latest zip
Put it in the internal storage (in the root directory, not inside another folder!)
Two paths:
If you put the zip from PC via USB simply unplug the USB cable
If you downloaded the zip and put it manually via file manager from the phone reboot the system
A notification should pop out, notifying you there is a firmware package to install!
Just follow the notification message and you'll be done!
Hey so I installed adb and ran the phone under fastboot but when I run fastboot oem lock all it says in the windows powershell is < waiting for any device >
Kiribro02 said:
Hey so I installed adb and ran the phone under fastboot but when I run fastboot oem lock all it says in the windows powershell is < waiting for any device >
Click to expand...
Click to collapse
Oh that's an issue I have all the times with Asus devices. There's a simple one-time fix though: just install the official Asus ADB drivers.
Download them from this page (I know it's the smaller Zenfone 8 page, but they work with every Asus device): https://www.asus.com/it/Mobile/Phones/ZenFone/Zenfone-8/HelpDesk_Download/
Choose your windows version (for 10 and 11 choose 8.1)
Download the USB driver
Extract the archive somewhere in your PC
Open Device manager in your PC (search it in start menu) while the phone is connected via USB and in fastboot mode
You'll notice an unknown device with a yellow/orange warning icon at the top of the devices list. Right click on it and choose Update drivers.
Choose "Search driver in the PC" (the second option (don't choose the first one since it searches the driver automatically on Windows update))
Choose the folder you extracted
Click "Next"
Drivers should be installed and fastboot should recognize your device (to test run the command: fastboot devices)
Sorry for the late reply, but I didn't get any notification from XDA
there were two options for drivers android adb and android composite adb drivers I selected the composite one but it doesn't seem like it was installed
Kiribro02 said:
When I try to update the drivers it says that windows was unable to install your and then it says the device.
Click to expand...
Click to collapse
Do you installed the drivers when the phone is in fastboot mode?
Also, I've noticed some steps are not clear (and one is doubled), I'll clean it
Kiribro02 said:
there were two options for drivers android adb and android composite adb drivers I selected the composite one but it doesn't seem like it was installed
Click to expand...
Click to collapse
Try all the two, I don't remember which one works (I think the Composite worked for me), but try also with the other ones
Hi,
I've bought a second hand zenfone 8 flip. After Hard Reset I have to enter the old PIN to continue. The problem is the seller doesn't have the PIN and is not willing to take the phone back. ASUS is not willing to help because I bought it second hand.
I already flashed with raw firmware, but this is still coming up.
Any ideas? Should I start a new thread?
b4rbaar said:
Hi,
I've bought a second hand zenfone 8 flip. After Hard Reset I have to enter the old PIN to continue. The problem is the seller doesn't have the PIN and is not willing to take the phone back. ASUS is not willing to help because I bought it second hand.
I already flashed with raw firmware, but this is still coming up.
Any ideas? Should I start a new thread?
Click to expand...
Click to collapse
Hi, yes you should create a new thread since it's a different topic
It's not working for me, please help:
C:\platform-tools>fastboot devices
M4AIB760******* fastboot
C:\platform-tools>fastboot oem lock
FAILED (remote: 'Command not supported in default implementation')
fastboot: error: Command failed
So, as you can see, the driver is installed correctly as I get an answer from fastboot devices, but then the OEM lock doesn't work.
Are there any other ways to re-lock it?
Thank you!
wyktron said:
It's not working for me, please help:
C:\platform-tools>fastboot devices
M4AIB760******* fastboot
C:\platform-tools>fastboot oem lock
FAILED (remote: 'Command not supported in default implementation')
fastboot: error: Command failed
So, as you can see, the driver is installed correctly as I get an answer from fastboot devices, but then the OEM lock doesn't work.
Are there any other ways to re-lock it?
Thank you!
Click to expand...
Click to collapse
@wyktron can you try this? This worked with my Zenfone 6 some years ago, it might be the same for ZF8 Flip, due to Asus customization:
Bash:
fastboot oem asus-back
maicol07 said:
@wyktron can you try this? This worked with my Zenfone 6 some years ago, it might be the same for ZF8 Flip, due to Asus customization:
Bash:
fastboot oem asus-back
Click to expand...
Click to collapse
@maicol07 thanks for the quick reply, here's what I got:
C:\platform-tools>fastboot oem asus-back
FAILED (remote: 'Command not supported in default implementation')
fastboot: error: Command failed
same error message
wyktron said:
@maicol07 thanks for the quick reply, here's what I got:
C:\platform-tools>fastboot oem asus-back
FAILED (remote: 'Command not supported in default implementation')
fastboot: error: Command failed
same error message
Click to expand...
Click to collapse
Try this one:
Code:
fastboot oem asus-csc_lk
maicol07 said:
Try this one:
Code:
fastboot oem asus-csc_lk
Click to expand...
Click to collapse
@maicol07 seems like any oem command shows this error, here's what I got:
C:\platform-tools>fastboot oem asus-csc_lk
FAILED (remote: 'Command not supported in default implementation')
fastboot: error: Command failed
C:\platform-tools>fastboot oem device-info
FAILED (remote: 'Command not supported in default implementation')
fastboot: error: Command failed
C:\platform-tools>fastboot oem get-sn
FAILED (remote: 'Command not supported in default implementation')
fastboot: error: Command failed
C:\platform-tools>fastboot oem get-imei1
FAILED (remote: 'Command not supported in default implementation')
fastboot: error: Command failed
C:\platform-tools>fastboot oem
fastboot: usage: empty oem command
C:\platform-tools>fastboot flashing lock
FAILED (remote: 'Unrecognized command flashing lock')
fastboot: error: Command failed
at this point, crying is my only option
what else can I try? I can't use key features like google pay because of that
thanks again for your support!
wyktron said:
@maicol07 seems like any oem command shows this error, here's what I got:
C:\platform-tools>fastboot oem asus-csc_lk
FAILED (remote: 'Command not supported in default implementation')
fastboot: error: Command failed
C:\platform-tools>fastboot oem device-info
FAILED (remote: 'Command not supported in default implementation')
fastboot: error: Command failed
C:\platform-tools>fastboot oem get-sn
FAILED (remote: 'Command not supported in default implementation')
fastboot: error: Command failed
C:\platform-tools>fastboot oem get-imei1
FAILED (remote: 'Command not supported in default implementation')
fastboot: error: Command failed
C:\platform-tools>fastboot oem
fastboot: usage: empty oem command
C:\platform-tools>fastboot flashing lock
FAILED (remote: 'Unrecognized command flashing lock')
fastboot: error: Command failed
at this point, crying is my only option
what else can I try? I can't use key features like google pay because of that
thanks again for your support!
Click to expand...
Click to collapse
As mentioned here check if you have enabled Debug USB and OEM unlock in developer options and try to reboot into bootloader (with either fastboot reboot bootloader or adb reboot bootloader)
maicol07 said:
As mentioned here check if you have enabled Debug USB and OEM unlock in developer options and try to reboot into bootloader (with either fastboot reboot bootloader or adb reboot bootloader)
Click to expand...
Click to collapse
@maicol07 there's no OEM unlock in my developer options, only the USB debugging (which is already on)
besides this oem method, is there another way to lock it? perhaps through the zenfone flash tool (I have it installed and it detects my phone, but never used it)
So I got a Lil c100 a couple days ago. It has a screen lock and the recovery mode don't work. Everyone says get it into fastbook amd use that to get to recovery. But the problem is after I get into fastboot the device isn't found. I've installed every USB driver known to man about fastboot or Nokia in general. And yet it still not popping up. Can sb help me?
swiftd3v said:
So I got a Lil c100 a couple days ago. It has a screen lock and the recovery mode don't work. Everyone says get it into fastbook amd use that to get to recovery. But the problem is after I get into fastboot the device isn't found. I've installed every USB driver known to man about fastboot or Nokia in general. And yet it still not popping up. Can sb help me?
Click to expand...
Click to collapse
anything yet?
swiftd3v said:
So I got a Lil c100 a couple days ago. It has a screen lock and the recovery mode don't work. Everyone says get it into fastbook amd use that to get to recovery. But the problem is after I get into fastboot the device isn't found. I've installed every USB driver known to man about fastboot or Nokia in general. And yet it still not popping up. Can sb help me?
Click to expand...
Click to collapse
What do you mean by "the device isn't found"?
wenyendev said:
What do you mean by "the device isn't found"?
Click to expand...
Click to collapse
The error I’m getting is “fastboot: usage: unknown device target recovery”
I am experiencing the EXACT same thing. No matter what box program Im using , nothing works! crazy. Please help. Id be happy with a factory reset. Atleast then I could get past the FRP.
Wow, I have not encountered that error yet.
I could only guess that it might be a problem of recovery.
How did you install your current recovery if not from fastboot?
diamant3 said:
The error I’m getting is “fastboot: usage: unknown device target recovery”
Click to expand...
Click to collapse
you're using fastboot reboot recovery?
Hey any update on this? I can say I've come across the same issue where their seems to either be no recovery or a corrupt one.
One thing I want to point out is (at least with the TracFone) that when I put the device in fastboot, and have wondershare tune go running, it displays the device as a Sony Xperia. The program still isn't able to connect to the device for me to attempt a reboot into recovery. It also reads the device as two other devices.
I'm hoping someone has encountered these findings and may also have a dump of the stock rom.if so I may be able to begin rooting for at least fix the recovery issue.
TaigaDaReck said:
Hey any update on this? I can say I've come across the same issue where their seems to either be no recovery or a corrupt one.
One thing I want to point out is (at least with the TracFone) that when I put the device in fastboot, and have wondershare tune go running, it displays the device as a Sony Xperia. The program still isn't able to connect to the device for me to attempt a reboot into recovery. It also reads the device as two other devices.
I'm hoping someone has encountered these findings and may also have a dump of the stock rom.if so I may be able to begin rooting for at least fix the recovery issue.
Click to expand...
Click to collapse
Also I'm going to use my Linux system to see if I get any results. Let me know if you've tried it as well.
fastboot oem unlock/fastboot flashing unlock has been blocked in the boot loader, only hope for root is another brom exploit like mtkclient or a temp root privilege escalation exploit
luridphantom said:
fastboot oem unlock/fastboot flashing unlock has been blocked in the boot loader, only hope for root is another brom exploit like mtkclient or a temp root privilege escalation exploit
Click to expand...
Click to collapse
Were you able to get fastboot to recognize the device?
Which OS are you testing on if you are?
TaigaDaReck said:
Were you able to get fastboot to recognize the device?
Which OS are you testing on if you are?
Click to expand...
Click to collapse
you need to use a special mtk boot mode script you can download here #101
Code:
computer:~ user$ python3 ~/Downloads/mtk-bootseq.py FASTBOOT /dev/tty.usbmodem14100
b'READYTOO'
Boot sequence sent
computer:~ user$ ~/Downloads/platform-tools/fastboot oem unlock
FAILED (remote: 'unknown command')
fastboot: error: Command failed
computer:~ user$ ~/Downloads/platform-tools/fastboot flashing unlock
FAILED (remote: 'unknown command')
fastboot: error: Command failed
computer:~ user$ ~/Downloads/platform-tools/fastboot oem unlock-go
FAILED (remote: 'unknown command')
fastboot: error: Command failed
testing on android 12, jan5 2022 update build 02US_1_030
luridphantom said:
you need to use a special mtk boot mode script you can download here #101
Code:
computer:~ user$ python3 ~/Downloads/mtk-bootseq.py FASTBOOT /dev/tty.usbmodem14100
b'READYTOO'
Boot sequence sent
computer:~ user$ ~/Downloads/platform-tools/fastboot oem unlock
FAILED (remote: 'unknown command')
fastboot: error: Command failed
computer:~ user$ ~/Downloads/platform-tools/fastboot flashing unlock
FAILED (remote: 'unknown command')
fastboot: error: Command failed
computer:~ user$ ~/Downloads/platform-tools/fastboot oem unlock-go
FAILED (remote: 'unknown command')
fastboot: error: Command failed
testing on android 12, jan5 2022 update build 02US_1_030
Click to expand...
Click to collapse
Hey thanks for the response.
So far I've been able to get the device to read in fastboot but I'm still unable to unlock the bootloader since as your saying it's definitely..."gimped" haha. I'll checkout the script and do some tests to see what I get.
TaigaDaReck said:
Hey thanks for the response.
So far I've been able to get the device to read in fastboot but I'm still unable to unlock the bootloader since as your saying it's definitely..."gimped" haha. I'll checkout the script and do some tests to see what I get.
Click to expand...
Click to collapse
if you're curious you can always reach out to this guy, he's able to get prototype boot loaders and stuff: https://twitter.com/Hikari_Calyx
might even know how to get test points to force it into brom for mtkclient