Hello Guyz . after i followed step by step this guide and when i reached at the fastboot oem unlock command and choose with the buttons of my phone "Unlock it" , i remove the battery as it says but i gest this error :
(bootloader) Showing Options on Display.
(bootloader) Use device keys for selection.
(bootloader) Bootloader is unlocked now.
FAILED (status read failed (Too many links))
finished. total time: 220.523s
somebody knows whats should i do? :/
Sorry for my english . I 've searched evrywhere for a solution but nothing....
rawpman said:
Hello Guyz . after i followed step by step this guide and when i reached at the fastboot oem unlock command and choose with the buttons of my phone "Unlock it" , i remove the battery as it says but i gest this error :
(bootloader) Showing Options on Display.
(bootloader) Use device keys for selection.
(bootloader) Bootloader is unlocked now.
FAILED (status read failed (Too many links))
finished. total time: 220.523s
somebody knows whats should i do? :/
Sorry for my english . I 've searched evrywhere for a solution but nothing....
Click to expand...
Click to collapse
Wait did you pull the battery while you were unlocking or after you got error?
Sent from my LG-P880 using xda app-developers app
rawpman said:
Hello Guyz . after i followed step by step this guide and when i reached at the fastboot oem unlock command and choose with the buttons of my phone "Unlock it" , i remove the battery as it says but i gest this error :
(bootloader) Showing Options on Display.
(bootloader) Use device keys for selection.
(bootloader) Bootloader is unlocked now.
FAILED (status read failed (Too many links))
finished. total time: 220.523s
somebody knows whats should i do? :/
Sorry for my english . I 've searched evrywhere for a solution but nothing....
Click to expand...
Click to collapse
Download this:
http://www.4shared.com/rar/HFf4newq/LGO4X-UNLOCK-BOOTLOADER.html
Instructions are inside
rawpman said:
Hello Guyz . after i followed step by step this guide and when i reached at the fastboot oem unlock command and choose with the buttons of my phone "Unlock it" , i remove the battery as it says but i gest this error :
(bootloader) Showing Options on Display.
(bootloader) Use device keys for selection.
(bootloader) Bootloader is unlocked now.
FAILED (status read failed (Too many links))
finished. total time: 220.523s
somebody knows whats should i do? :/
Sorry for my english . I 've searched evrywhere for a solution but nothing....
Click to expand...
Click to collapse
You did all alright, but LG does not want you to unlock, in other words your phone can not be unlocked at the moment...
Try: adb reboot oem unlock - phone on debug on, if you get red letters in top left corner LGE security...no unlock...
Did the job for 234-XXX now after reflash it is EUR-XXX...
nedooo said:
You did all alright, but LG does not want you to unlock, in other words your phone can not be unlocked at the moment...
Try: adb reboot oem unlock - phone on debug on, if you get red letters in top left corner LGE security...no unlock...
Did the job for 234-XXX now after reflash it is EUR-XXX...
Click to expand...
Click to collapse
i tried as you said adb reboot oem unlock but i dont get such tiny letters... after i tried it i checked Bootloader Unlock Check but says : Lock .
Maybe it's not my time to unlock it
the thing is it seems that the bootloader does unlock if you use the chinese kdz but the issue must be with android software not recognising it, i was on 23400 (not unlockable) and i found that the chinese kdz reported that the bootloader was unlocked, now i had the problem when trying to use unsecure boot and custom recovery so it seemed like it was still locked, now i found out the hard way that it was unlocked according to the hardware as i erased my bootloader and in the process bricked my phone
i think the problem with android recognising it is too do with something in the odm side of things,not being changed appropiatly
RuedasLocas said:
Download this:
http://www.4shared.com/rar/HFf4newq/LGO4X-UNLOCK-BOOTLOADER.html
Instructions are inside
Click to expand...
Click to collapse
I've tried this but I'm stuck at: <waiting for device>
deownagee said:
I've tried this but I'm stuck at: <waiting for device>
Click to expand...
Click to collapse
Need to install the drivers "CT_HsPhone_General_Drivers", they're inside of the folder.
If it doesn't works, don't touch the cmd window, unplug the phone and pluggit again, try all the ways.
Be creative. I had the same problem in CN V20A (also cause I didn't follow the tutorial...) but I made it.
RuedasLocas said:
Need to install the drivers "CT_HsPhone_General_Drivers", they're inside of the folder.
If it doesn't works, don't touch the cmd window, unplug the phone and pluggit again, try all the ways.
Be creative. I had the same problem in CN V20A (also cause I didn't follow the tutorial...) but I made it.
Click to expand...
Click to collapse
i was enough creative to install linux to my pc and do the whole procces on linux! And guess what: Bootloader status : Unlock ! :victory:
deownagee said:
I've tried this but I'm stuck at: <waiting for device>
Click to expand...
Click to collapse
It used to be my problem also. LMAO..
I finally succesfully unlock my phone using HTC fastboot driver.
When I got waiting for device message, I went to device manager, update fastboot driver with HTC one fastboot driver. Then my phone shows option to unlock it or not.
Sent from my LG-P880 using xda app-developers app
Related
Hey everyone,
so i tried to run a RUU for GingerBread on my incredible s and forgot to do "fastboot oem lock"
i ran the ruu and it told me error code 155 and i facepalmed myself -.-
and now i seem to be inable to access recovery NOR bootloader...
i cant even start my Phone up
the only thing it shows is a black screen with hTC on it and in the 4 corners a white triangle with "!" in it...
Can someone help me with reverting back to STOCK GB rom without root etc. s-on etc.
because i want to sell this Phone (no i dont :/) to buy a hTC One X+ and i need the stock stuff for that
NOTE: i *had* BlackRose s-off
Another note: computer recognises my Phone in fastboot mode so i can use fastboot commands but not adb
EDIT: now i get code 152 image update error...
EDIT2: I am able to get into bootloader... only thing it shows is:
*** BlackRose ***
VIVO PVT SHIP S-OFF RL
HBOOT-2.03.0000
RADIO-3831.19.00.19_M
eMMC-boot
and some date...
RUU (in orange)
Parsing . . . [downloaded ZIP]
[1] BOOTLOADER -Bypassed
[2] BOOT -OK
[3] RECOVERY -OK
[4] SYSTEM -OK
[5] SPLASH1 -OK
[6] USERDATA -OK
[7] TP -Bypassed
[8] TP -Bypassed
[9] TP -OK
[10] RADIO_V2 -Fail-UZ
[11] RADIO_CUST -OK
Image unzipping fail!
Update fail!
HELP PLEASE
SOLUTION: Delete the RUU, Download it again, and try again, if still nothing, try again, and still nothing, leave a comment!!!
Thanks if i helped u!!!
oziboy said:
Hey everyone,
so i tried to run a RUU for GingerBread on my incredible s and forgot to do "fastboot oem lock"
i ran the ruu and it told me error code 155 and i facepalmed myself -.-
and now i seem to be inable to access recovery NOR bootloader...
i cant even start my Phone up
the only thing it shows is a black screen with hTC on it and in the 4 corners a white triangle with "!" in it...
Can someone help me with reverting back to STOCK GB rom without root etc. s-on etc.
because i want to sell this Phone (no i dont :/) to buy a hTC One X+ and i need the stock stuff for that
NOTE: i *had* BlackRose s-off
Another note: computer recognises my Phone in fastboot mode so i can use fastboot commands but not adb
EDIT: now i get code 152 image update error...
EDIT2: I am able to get into bootloader... only thing it shows is:
*** BlackRose ***
VIVO PVT SHIP S-OFF RL
HBOOT-2.03.0000
RADIO-3831.19.00.19_M
eMMC-boot
and some date...
RUU (in orange)
Parsing . . . [downloaded ZIP]
[1] BOOTLOADER -Bypassed
[2] BOOT -OK
[3] RECOVERY -OK
[4] SYSTEM -OK
[5] SPLASH1 -OK
[6] USERDATA -OK
[7] TP -Bypassed
[8] TP -Bypassed
[9] TP -OK
[10] RADIO_V2 -Fail-UZ
[11] RADIO_CUST -OK
Image unzipping fail!
Update fail!
HELP PLEASE
Click to expand...
Click to collapse
Run Blackrose Tool and there is an option for uninstalling Blackrose HBOOT. That will give you Stock HBOOT 1.13.0000 and then run latest RUU.
072665995 said:
Run Blackrose Tool and there is an option for uninstalling Blackrose HBOOT. That will give you Stock HBOOT 1.13.0000 and then run latest RUU.
Click to expand...
Click to collapse
Thanks for yor quick reply, i cant boot into my phoneo enable debugging thus i got no adb
andthe tool is stuck at "waiting for device" :/ it has to be with fastboot :/
oziboy said:
Thanks for yor quick reply, i cant boot into my phoneo enable debugging thus i got no adb
andthe tool is stuck at "waiting for device" :/ it has to be with fastboot :/
Click to expand...
Click to collapse
What does it say when you enter recovery?
072665995 said:
What does it say when you enter recovery?
Click to expand...
Click to collapse
Can't enter bootloader,boot up device and i get a black screen with silver HTC in it with some triangle with ! in it
so cant enter recovery to tell ya ://
I tried some ways to get back to s-on but without success :/
oziboy said:
Can't enter bootloader,boot up device and i get a black screen with silver HTC in it with some triangle with ! in it
so cant enter recovery to tell ya ://
I tried some ways to get back to s-on but without success :/
Click to expand...
Click to collapse
So how do fastboot commands work? You have to be in bootloader to access fastboot....
Are you pressing volume down and power?
072665995 said:
So how do fastboot commands work? You have to be in bootloader to access fastboot....
Are you pressing volume down and power?
Click to expand...
Click to collapse
Yeah i know is kinda weird how i get to fastboot, idk neither
i just press power button and my pc recognises my Phone in fastboot state
and i am able to use *almost* all fastboot commands such as fastboot flash blahblah and fastboot reboot-bootloader and blahblah
if i start up, again, i still get a black screen with silver HTC letters on it
after hitting power button NO SINGLE button is being recognised by the Phone itself
oziboy said:
Yeah i know is kinda weird how i get to fastboot, idk neither
i just press power button and my pc recognises my Phone in fastboot state
and i am able to use *almost* all fastboot commands such as fastboot flash blahblah and fastboot reboot-bootloader and blahblah
if i start up, again, i still get a black screen with silver HTC letters on it
after hitting power button NO SINGLE button is being recognised by the Phone itself
Click to expand...
Click to collapse
when you try fastboot reboot bootloader, that still lands you to nothing?
072665995 said:
when you try fastboot reboot bootloader, that still lands you to nothing?
Click to expand...
Click to collapse
Yes i tried that already
But the worst thing is that i can run the RUU but i keep on getting error 152 system image thingy if thats fixed then i guess this whole thingy here will be installed
only thing i need is to RELOCK my bootloader but i cant use fastboot oem lock, the argument "lock" isnt recognised
Guys please help :crying:
I need to sell this Phone
EDIT: see this
c:\ADB>fastboot oem lock
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.000s]
finished. total time: 0.000s
and this
c:\ADB>fastboot flash hboot hboot.img
sending 'hboot' (1024 KB)...
OKAY [ 0.686s]
writing 'hboot'...
(bootloader) image update is bypassed!
OKAY [ 0.125s]
finished. total time: 0.811s
EDIT2: oh and on my Phone screen when i plug it out it shows on bootloader: "Can not roll back hboot"
I guess my Phone is stuck in RUU mode? (when it was flashing the stuff)
Is it possible that some of the files in my RUU were corrupt?
I downloaded the RUU with some "pauses" and "resumes"
imma redownload the RUU now... hope it works :/
p.s. my hboot id 2.03.blahblah... shouldnt it be 6.blahblah for BlackRose?
so blackrose is uninstalled?!
oziboy said:
Guys please help :crying:
I need to sell this Phone
EDIT: see this
c:\ADB>fastboot oem lock
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.000s]
finished. total time: 0.000s
and this
c:\ADB>fastboot flash hboot hboot.img
sending 'hboot' (1024 KB)...
OKAY [ 0.686s]
writing 'hboot'...
(bootloader) image update is bypassed!
OKAY [ 0.125s]
finished. total time: 0.811s
EDIT2: oh and on my Phone screen when i plug it out it shows on bootloader: "Can not roll back hboot"
I guess my Phone is stuck in RUU mode? (when it was flashing the stuff)
Is it possible that some of the files in my RUU were corrupt?
I downloaded the RUU with some "pauses" and "resumes"
imma redownload the RUU now... hope it works :/
p.s. my hboot id 2.03.blahblah... shouldnt it be 6.blahblah for BlackRose?
so blackrose is uninstalled?!
Click to expand...
Click to collapse
with Blackrose, my bootloader 2.03
DuffyBank said:
with Blackrose, my bootloader 2.03
Click to expand...
Click to collapse
Uhm... how do you mean?
oziboy said:
Uhm... how do you mean?
Click to expand...
Click to collapse
sorry, meant hboot 2.03
Hey i still didn't give up and im still awaiting help meanwhile sitting the whole day on the pc to search for any solutions :/
guys please help me out of this it has been 3 days and im TIRED of it
i have to do it with a nokia now (
Any link to a froyo or ICS RUU is appreciated too :d
oziboy said:
Hey i still didn't give up and im still awaiting help meanwhile sitting the whole day on the pc to search for any solutions :/
guys please help me out of this it has been 3 days and im TIRED of it
i have to do it with a nokia now (
Any link to a froyo or ICS RUU is appreciated too :d
Click to expand...
Click to collapse
Can you please say what it says in your bootloader now?
In all honesty, if you can't access the bootloader, you're pretty much f**ked :/
Your last hope is recovery and trying blackrose tool there
072665995 said:
Can you please say what it says in your bootloader now?
In all honesty, if you can't access the bootloader, you're pretty much f**ked :/
Your last hope is recovery and trying blackrose tool there
Click to expand...
Click to collapse
Well, that was definately a way to put it xD
But yes. If you can't access bootloader, you may have problems.
Sent from my Nexus 5
oh well, F*** then cuz i cant Access bootloader properly to choose recovery from it
i m going to try few more things,
1. do it via sdcard and fllash it
2. remove radio.img from the OTA and flash it since it gives an error
i can Access bootloader but when i do that, my bootloader shows me
***BlackRose***
some information...
and then it shows in orange "RUU"
i cant Access anthing from it and when i plug charger back in it goes into RUU mode
i know what my problem is, but i cant find any solutions, "fastboot oem lock" is an unrecognised command... does it have to do with something about htcdev.com?
OMG TY FOR ALL UR HELP GUYS my phones fixed and is on GB 2.3.3 now ummm
my RUU was just corrupt -_- i ran a new one NOW I HAVE STOCK, ty all so much
THE VIVO IS BACK ALIIIIVE
oziboy said:
OMG TY FOR ALL UR HELP GUYS my phones fixed and is on GB 2.3.3 now ummm
my RUU was just corrupt -_- i ran a new one NOW I HAVE STOCK, ty all so much
THE VIVO IS BACK ALIIIIVE
Click to expand...
Click to collapse
nvm wat we said about u being fked
Sent from my Nexus 5
LamboBull said:
nvm wat we said about u being fked
Sent from my Nexus 5
Click to expand...
Click to collapse
lol xD
To the users keep on having code 152, please delete the RUU and download it again!!!
since thats how i fixed it xD :highfive:
I followed all the instructions for rooting my device but there must have been something I missed. Here is what I did:
Developer Options - USB Debugging and OEM Unlock enabled
Downloaded and installed android-sdk-windows as specified in this tutorial
Followed all steps to reach "fastboot oem unlock" in the cmd prompt
Once that is entered, it prompts me to unlock bootloader on the phone. When I try to proceed with the unlock, the cmd prompt replies with the following:
(bootloader) Device state transition will erase userdata.
(bootloader) Are you sure you want to continue this transition?
(bootloader)
(bootloader) Press POWER key to continue.
(bootloader) Press VOL UP or VOL DOWN key to cancel state transition.
(bootloader) State transition confirmed!
(bootloader) Please select 'YES' on screen if you want to continue...
(bootloader) Unlocking bootloader...
(bootloader) Not supported command in current status!
FAILED (remote failure)
finished. total time: 17.525s
When I try to reboot the device, it displays "your device is corrupt. It can't be trusted." at which point it either turns off on its own or immediately after touching a button.
Please let me know what other information you need to help. Thank you!!
tooabstract788 said:
........., it displays "your device is corrupt. It can't be trusted."
Click to expand...
Click to collapse
That's because you unlocked the m-bootloader. Your device is normal, but Google doesn't want us to unlock/root. Ignore it and flash a rom. Start here http://forum.xda-developers.com/showthread.php?t=3059493
NLBeev said:
That's because you unlocked the m-bootloader. Your device is normal, but Google doesn't want us to unlock/root. Ignore it and flash a rom. Start here http://forum.xda-developers.com/showthread.php?t=3059493
Click to expand...
Click to collapse
Thanks! I'm able to flash a rom by putting the phone in bootloader and using cmd prompt, correct? Am I to extract the rom files in my "android-sdk-windows" folder?
tooabstract788 said:
Thanks! I'm able to flash a rom by putting the phone in bootloader and using cmd prompt, correct? Am I to extract the rom files in my "android-sdk-windows" folder?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=3068327
Here is info you need,
Hi everybody, I have a little question regarding my P10.
The model of my phone is VTR-L09C521B101
Is there a way to flash this phone with VTR-L09C432 version?
or i need to flash with same model version (VTR-L09C521)?
Thnks
Yes, it is possible to 'rebrand'. The procedure is explained in the Mate 9 forum. It is not so easy and involves unlocking the bootloader.
Updating can be done with the Firmware Finder (Playstore).
M1chiel said:
Yes, it is possible to 'rebrand'. The procedure is explained in the Mate 9 forum. It is not so easy and involves unlocking the bootloader.
Updating can be done with the Firmware Finder (Playstore).
Click to expand...
Click to collapse
thanks for the answer!!
regarding bootloader, the phone shows this:
PHONE RELOCKED
FRP LOCK
ADB shows me that the phone is unlocked, the problem is when I try to send something to phone it shows:
Error Remote command not allowed.
any ideas?
thanks!
I've tried to reword the mate 9 instructions for the p10 here: https://forum.xda-developers.com/p10/help/rebrand-firmware-finder-t3685951
As for adb, what command are you trying? Do you see your phone if you type ADB Devices?
Quintman said:
I've tried to reword the mate 9 instructions for the p10 here: https://forum.xda-developers.com/p10/help/rebrand-firmware-finder-t3685951
As for adb, what command are you trying? Do you see your phone if you type ADB Devices?
Click to expand...
Click to collapse
Quintman, no the phone is not listed with adb devices command. I can only enter with fastboot.
Let me paste the commands that I have tried:
C:\adb>fastboot devices
WPG7N17320000978 fastboot
C:\adb>fastboot oem get-bootinfo
...
(bootloader) unlocked
OKAY [ 0.001s]
finished. total time: 0.001s
C:\adb>fastbot oem lock <my_unlock_code>
...
FAILED (remote: Command not allowed)
finished. total time: 0.016s
C:\adb>fastboot oem unlock <my_unlock_code>
...
FAILED (remote: Command not allowed)
finished. total time: 0.016s
C:\adb>fastboot oem relock <my_unlock_code>
...
FAILED (remote: stat not match)
finished. total time: 0.016s
The Strange thing is that in the phone shows PHONE RELOCKED, not unlocked as ADB shows.
Since I uploaded boot img of another version (C432) full OTA, could this be the problem? in this case what can I do?
thanks for your help!!
Could this be happening because of FRP Lock?, none of the software I have tried (DC-phoenix, chimera and Unlocker v2) worked. Im this close to throw this f*ckin phone to trash u.u
fmm1977 said:
Could this be happening because of FRP Lock?, none of the software I have tried (DC-phoenix, chimera and Unlocker v2) worked. Im this close to throw this f*ckin phone to trash u.u
Click to expand...
Click to collapse
edit: just found this in another thread "FRP Lock occurs when the phone has a firmware mismatch and or oem unlocking is not on in developer options"
Hmm, i've just checked my phone and in fastboot it says PHONE Locked, and FRP Unlock. I think that may be your issue. What exactly did you do to flash your phone with the other version? put an UPDATE.APP into a \Dload folder and 3 button update?
is your phone booting (guessing not). my guess is that you need to get a hold of your stock firmware file an flash that first.
Quintman said:
edit: just found this in another thread "FRP Lock occurs when the phone has a firmware mismatch and or oem unlocking is not on in developer options"
Hmm, i've just checked my phone and in fastboot it says PHONE Locked, and FRP Unlock. I think that may be your issue. What exactly did you do to flash your phone with the other version? put an UPDATE.APP into a \Dload folder and 3 button update?
is your phone booting (guessing not). my guess is that you need to get a hold of your stock firmware file an flash that first.
Click to expand...
Click to collapse
Ok, this is what I've done step by step:
1.- With the unlock code provided by huawei, I have unlocked my phone (my version is VTR-L09C521B101 stock)
2.- Once unlocked, I have downloaded another ROM version (VTR-L29C605B151) in the web page says this rom is for latin america), so with the Huawei Update Extractor, I have extracted all files.
3.- Via ADB/FASTBOOT, I sent the files to my phone, boot.img first and then the others. (big big mistake!)
4.- Rebooted the phone, and then keeps restarting at huawei logo.
5.- Seeing that it did´t worked, what I did was to lock the phone again thinking to send it to Huawei (at this point the phone shows as "unlocked" via fastboot commands, however when I start the phone in fastboot mode, in the screen shows "PHONE RELOCKED, FRP LOCK"
6.- Sent to huawei's service, they said that they cannot fix my phone because it was tampered/rooted.
7.- Right now all I need to fix my phone is to LOCK/UNLOCK again in order to rebrand it to L29 version, since the original stock rom dont exist (not as FULL OTA).
And that´s what I did so far my friend.
Questions:
1.- Is there a way to connect to my phone and change the oem info file? or something?
2.- Do I need to wait the stock rom to be released in order to reflash via Dload method?
3.- What if the stock ROM version of my phone is never released?
thank you for your answer my friend!!
Hmm ok. I am just not sure on your step 3, I've never heard of a method that involves a boot.img... what I would suggest, is to try and download the stock firmware files (need the larger full ota files), extract the update.app file and put on sd card in \dload.
Then hold down both volume up and down and power (3 button method)
It will try and flash the stock image back to the phone.
I just tried the Dload method and nothing happened (always stuck in 5%), now im going to try to use a smaller memory card (mine is 64 Gb). lood
U have disconnected the USB cable when u try 3 button update
berka38 said:
U have disconnected the USB cable when u try 3 button update
Click to expand...
Click to collapse
Yes sr!!
Hello, I'm trying to follow This guide and This one to unlock the bootloader with no luck.
This is what I get:
Code:
C:\Minimal ADB and Fastboot>fastboot devices
ZY322MF6XP fastboot
C:\Minimal ADB and Fastboot>fastboot oem get_unlock_data
...
FAILED (remote: unknown command)
finished. total time: 0.000s
I updated drivers and adb and fastboot with no luck.
Any help?
Edit: I have a Moto G6 Plus in RETLA channel with the march security patch.
I'd double check that Allow OEM Unlock in dev options is actually on
ZeroPoke said:
I'd double check that Allow OEM Unlock in dev options is actually on
Click to expand...
Click to collapse
Tried it with it on and off twice!
Angelelz said:
Tried it with it on and off twice!
Click to expand...
Click to collapse
Same thing happened to me. When you get your unique identifier find an online generator and then paste that into the Motorola website, worked for me.
H0LT3R said:
Same thing happened to me. When you get your unique identifier find an online generator and then paste that into the Motorola website, worked for me.
Click to expand...
Click to collapse
Yeah, can't get the unique identifier though, that particular command is not working for me. Anyone have any idea why?
Hi,
For Working this command "Fastboot oem get_unlock_data"
First you need to remove or delete your phone's SCREEN LOCKS like your fingerprint, face-unlock, pattern or password etc... And keep on NONE option in lock screen. After all above procedure done than, You run that commend "Fastboot oem get_unlock_data". After runing thant command, You will not get "FAILED (remote: unknown command)"
It will work 200%.
PRUTHVIRAJ S VASUDEV said:
It will work 200%.
Click to expand...
Click to collapse
no. it doesnt.
It depends on your fastboot version. Please check "fastboot --version" and post it here.
---------- Post added at 03:49 AM ---------- Previous post was at 03:44 AM ----------
...or try "fastboot oem help". This option will show you whether this command is available.
hi!
i have same problem.
product: Lenovo TB-7504x
fastboot getvar info:
warranty: yes
unlocked: no
secure: yes
kernel: lk
product: WT98997_LTEROW
version-preloader: 0.1.00
version: 0.5
PS: Allow OEM Unlock in developer options is actually on
Also having this issue trying to root my LG G6; I successfully set up adb, fastboot, and started up into bootloader, but it keeps returning the failed/unknown command error when I try to do any further steps. "fastboot devices" shows up correctly but "fastboot oem device-info", device-id, "fastboot flash recovery twrp.img", all keep failing
renforrest-EX said:
Also having this issue trying to root my LG G6; I successfully set up adb, fastboot, and started up into bootloader, but it keeps returning the failed/unknown command error when I try to do any further steps. "fastboot devices" shows up correctly but "fastboot oem device-info", device-id, "fastboot flash recovery twrp.img", all keep failing
Click to expand...
Click to collapse
same
Did you try another USB port? Some users reported that USB 3.0 did not work but 2.0.
I would be willing to bet this is happening on devices that are not allowed to be unlocked. Like those purchased from a phone company.
its been a week since i'm trying on my htc 10, but getting the same error, i tried,
- delete the drivers and re-install
- delete sync manager
- enabled debug & oem unlock
- done reset factory for the phone
- change USB ports and cables
- tried 3 latops
nothing works, sometimes i'll just the error "waiting for any phone" and other times "FAILED (remote: unknown command)"
Angelelz said:
Hello, I'm trying to follow This guide and This one to unlock the bootloader with no luck.
FAILED (remote: unknown command)
finished. total time: 0.000s[/CODE]
I updated drivers and adb and fastboot with no luck.
Try fastboot oem unlock first, then fastboot oem get_unlock_data
Any help?
Edit: I have a Moto G6 Plus in RETLA channel with the march security patch.
Click to expand...
Click to collapse
Try fastboot oem unlock first then fastboot oem get_unlock_data
I'm following a tutorial and obviously got stuck and the very same step as you did. And presumably you are following a tutorial, too.
1. Go to Security Settings and remove device lock (PIN, fingerprint, whatever you are using) and set it to NONE.
2. Go to Developer Settings and Unlock Bootloader. (If you skip step 1., you'll be asked to unlock your device here, but find that the Unlocking failed afterwards. Hence, go to step 1. and remove the lock first.)
3. fastboot oem unlock
Done. (Bootloader is unlocked now. Confirm via boot to fastboot mode (Volume down + Power button))
fastboot oem get_unlock_data is probably removed (deprecated) and maybe you don't even need a key from the manufacturer to unlock anymore.
gelignite said:
maybe you don't even need a key from the manufacturer to unlock anymore.
Click to expand...
Click to collapse
You still need a key to unlock the bootloader for the first time! When it's locked with status "flashing_locked" you don't need a key for it.
Is it a brand new device...?
WoKoschekk said:
You still need a key to unlock the bootloader for the first time! When it's locked with status "flashing_locked" you don't need a key for it.
Is it a brand new device...?
Click to expand...
Click to collapse
If that question refers to my post: I have a Moto E4 (XT1762). Bought it like half a year ago to tinker around with. I started it, ran all updates available and set a device lock (here: PIN).
Today I finally found the time to get started with lineageos and followed the guide at: rootmygalaxy.net (download-and-install-lineage-os-16-on-motorola-moto-e4-android-9-0-pie)
I got stuck at the error the OP had. (This lead me here.)
In my case I got past the error by doing the steps mentioned in my first post, i.e.
1. started the device (normal boot) and got rid of the device lock (PIN in my case), enabled USB debugging, enabled bootloader unlocking
2. powered off the device and started it again in fast boot mode (volume down + power button)
3. On computer / in terminal: fastboot oem unlock (without any key from the manufacturer)
The device showed a confirmation dialog. (Volume up: Yes, Volume down: No)
Code:
[email protected]:~/downloads/lineageos/Android_SDK_platform_tools/platform-tools$ ./fastboot oem unlock
(bootloader) Start unlock flow
OKAY [ 9.657s]
Finished. Total time: 9.667s
Now in fast boot screen I see Device Status: unlocked
I just wanted to share my experiences from today's struggles and maybe it'll help the OP.
gelignite said:
If that question refers to my post: I have a Moto E4 (XT1762). Bought it like half a year ago to tinker around with. I started it, ran all updates available and set a device lock (here: PIN).
Today I finally found the time to get started with lineageos and followed the guide at: rootmygalaxy.net (download-and-install-lineage-os-16-on-motorola-moto-e4-android-9-0-pie)
I got stuck at the error the OP had. (This lead me here.)
In my case I got past the error by doing the steps mentioned in my first post, i.e.
1. started the device (normal boot) and got rid of the device lock (PIN in my case), enabled USB debugging, enabled bootloader unlocking
2. powered off the device and started it again in fast boot mode (volume down + power button)
3. On computer / in terminal: fastboot oem unlock (without any key from the manufacturer)
The device showed a confirmation dialog. (Volume up: Yes, Volume down: No)
Code:
[email protected]:~/downloads/lineageos/Android_SDK_platform_tools/platform-tools$ ./fastboot oem unlock
(bootloader) Start unlock flow
OKAY [ 9.657s]
Finished. Total time: 9.667s
Now in fast boot screen I see Device Status: unlocked
I just wanted to share my experiences from today's struggles and maybe it'll help the OP.
Click to expand...
Click to collapse
Moto E4 is a developer's device without a locked bootloader. I thought you were talking about a Moto G6.
Baronstragen said:
Try fastboot oem unlock first then fastboot oem get_unlock_data
Click to expand...
Click to collapse
fastboot oem unlock worked for me
My screen keep on showing "System Has Been Destroyed". The best I can do is to be at fastboot. When in fastboot mode I try to unlock the phone using CMD yet unsuccessfull. I can't get into developer option because it's stuck at "System Has Been Destroyed" screen.
Here's the message after input "fastboot oem device-info"
(bootloader) Verity mode: true
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: false
OKAY [ 0.011s]
Finished. Total time: 0.015s
Have you flashed a rom with miflashtool? Probably you've not unchecked "clean all and lock".
I think you're phone is hard bricked
Sounds like hard brick indeed. Check this out: https://forum.xda-developers.com/showpost.php?p=80029403&postcount=22
overcustom said:
Have you flashed a rom with miflashtool? Probably you've not unchecked "clean all and lock".
I think you're phone is hard bricked
Click to expand...
Click to collapse
I have tried to flashed a rom with miflash tool. I've checked clean all only. And it showed "error FAILED (remote : Erase is not allowed in Lock State)".
Brays88 said:
I have tried to flashed a rom with miflash tool. I've checked clean all only. And it showed "error FAILED (remote : Erase is not allowed in Lock State)".
Click to expand...
Click to collapse
It means bootloader was already Locked.
On which rom were you before?
overcustom said:
It means bootloader was already Locked.
On which rom were you before?
Click to expand...
Click to collapse
I've forgot which rom i've been. Any idea how to unlock the bootloader?
Brays88 said:
I've forgot which rom i've been. Any idea how to unlock the bootloader?
Click to expand...
Click to collapse
Unfortunately you have to flash a rom using EDL mode with an authorized account, hard brick is a very awful thing.
Thats why you need to read before doing anything with your phone. Almost every thread has flashing guides and all say that you have to unlock bootloader first to flash with miflash or to flash with twrp to avoid hardbricks. Edl is the way to go, good luck mate
ef1x said:
Thats why you need to read before doing anything with your phone. Almost every thread has flashing guides and all say that you have to unlock bootloader first to flash with miflash or to flash with twrp to avoid hardbricks. Edl is the way to go, good luck mate
Click to expand...
Click to collapse
i m having same problem this morning after OTA update!!! my systeme was unlocked and everything goes well, they asked my to update i said yes as ever, but now i have screen Systeme as been Destroyed, i did everythings that i know but nothings worked, i m always blocked because any method i used to flash said can't flash, bootloader locked... WHO the [email protected]#K LOCKED MY BOOTLOADER,,,,, please help i m crying now, it's a 800 $phone useless now, my wife gonna killed me!!!! LOL