I have one Moto X 2 , and he it's presenting this problem:
C:\Program Files (x86)\Minimal ADB and Fastboot>mfastboot oem unlock XXXXXXXXXXXXXXXXXXXXX
...
(bootloader) Check 'Enable OEM Unlock' in Developer Options.
FAILED (remote failure)
finished. total time: 0.016s
Yes , I activated USB debugging and also in Rlz Debug " *#*#759#*#* "
Someone could help me ? Thanks!!!
Related
C:\android-tools>fastboot devices
014FDCF003009004 fastboot
C:\android-tools>fastboot oem unlock\
...
FAILED (remote: unsupported command)
finished. total time: 0.003s
Hi,
I have Windows 10 and HiSuite installed.
I successfully unlocked my bootloader of my Honor 7 (EU version, with MM 313 received via OTA).
Most of the fastboot commands fail:
C:\Users\daniel\Desktop>fastboot oem get-bootinfo
...
(bootloader) unlocked
OKAY [ 0.000s]
finished. total time: 0.000s
C:\Users\daniel\Desktop>fastboot getvar all
getvar:all FAILED (remote: Command not allowed)
finished. total time: 0.000s
C:\Users\daniel\Desktop>fastboot getvar version-main
getvar:version-main FAILED (remote: Command not allowed)
finished. total time: -0.000s
C:\Users\daniel\Desktop>fastboot boot twrp_cn.img
downloading 'boot.img'...
OKAY [ 0.844s]
booting...
FAILED (remote: Command not allowed)
finished. total time: 0.844s
The "OEM RELOCK" and "OEM UNLOCK" and also "REBOOT" commands are working.
Do you have any idea what's going wrong?
MarioGirotti said:
Hi,
I have Windows 10 and HiSuite installed.
I successfully unlocked my bootloader of my Honor 7 (EU version, with MM 313 received via OTA).
Most of the fastboot commands fail:
C:\Users\daniel\Desktop>fastboot oem get-bootinfo
...
(bootloader) unlocked
OKAY [ 0.000s]
finished. total time: 0.000s
C:\Users\daniel\Desktop>fastboot getvar all
getvar:all FAILED (remote: Command not allowed)
finished. total time: 0.000s
C:\Users\daniel\Desktop>fastboot getvar version-main
getvar:version-main FAILED (remote: Command not allowed)
finished. total time: -0.000s
C:\Users\daniel\Desktop>fastboot boot twrp_cn.img
downloading 'boot.img'...
OKAY [ 0.844s]
booting...
FAILED (remote: Command not allowed)
finished. total time: 0.844s
The "OEM RELOCK" and "OEM UNLOCK" and also "REBOOT" commands are working.
Do you have any idea what's going wrong?
Click to expand...
Click to collapse
Nothing wrong with you, these commands are just not supported by Huawei bootloader (fastboot)
Damn... I wanted to boot into a custom recovery without flashing it. On Nexus 4 this was possible.
MarioGirotti said:
Damn... I wanted to boot into a custom recovery without flashing it. On Nexus 4 this was possible.
Click to expand...
Click to collapse
Yup, sucks big time, especially when trying to develop something
MarioGirotti said:
Hi,
I have Windows 10 and HiSuite installed.
I successfully unlocked my bootloader of my Honor 7 (EU version, with MM 313 received via OTA).
Most of the fastboot commands fail:
C:\Users\daniel\Desktop>fastboot oem get-bootinfo
...
(bootloader) unlocked
OKAY [ 0.000s]
finished. total time: 0.000s
C:\Users\daniel\Desktop>fastboot getvar all
getvar:all FAILED (remote: Command not allowed)
finished. total time: 0.000s
C:\Users\daniel\Desktop>fastboot getvar version-main
getvar:version-main FAILED (remote: Command not allowed)
finished. total time: -0.000s
C:\Users\daniel\Desktop>fastboot boot twrp_cn.img
downloading 'boot.img'...
OKAY [ 0.844s]
booting...
FAILED (remote: Command not allowed)
finished. total time: 0.844s
The "OEM RELOCK" and "OEM UNLOCK" and also "REBOOT" commands are working.
Do you have any idea what's going wrong?
Click to expand...
Click to collapse
test this command
fastboot oem get-lockstate
and see if the bootloader is really unlocked
^ maybe the green text saying "unlocked" is a hint
fosseperme said:
test this command
fastboot oem get-lockstate
and see if the bootloader is really unlocked
Click to expand...
Click to collapse
I will check this evening when I am back from work also this command
fosseperme said:
test this command
fastboot oem get-lockstate
and see if the bootloader is really unlocked
Click to expand...
Click to collapse
Great:
C:\Users\daniel>fastboot oem get-lockstate
...
FAILED (remote: Command not allowed)
finished. total time: 0.002s
But the bootloader screen itself tells: PHONE Unlocked
MarioGirotti said:
Great:
C:\Users\daniel>fastboot oem get-lockstate
...
FAILED (remote: Command not allowed)
finished. total time: 0.002s
But the bootloader screen itself tells: PHONE Unlocked
Click to expand...
Click to collapse
by the way, on this phone it's...
Code:
fastboot oem get-bootinfo
EDIT: IGNORE ME! You already said that in the OP
Hi
I'm stuck in my Xiaomi MI A3 bootloader, can't boot to recovery and system.
After flashing my stock firmware.
Here is my oem device info
PS C:\platform-tools> ./fastboot oem device-info (bootloader) Verity mode: true
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: false
OKAY [ 0.004s]
Finished. Total time: 0.006s
PS C:\platform-tools> ./fastboot getvar current-slot
current-slot: b
Finished. Total time: 0.004s
Thank you
bgsebiosjr said:
Hi
PS C:\platform-tools> ./fastboot getvar current-slot
current-slot: b
Finished. Total time: 0.004s
Thank you
Click to expand...
Click to collapse
Change current-slot to 'a' and reboot.
PS C:\platform-tools> ./fastboot flashing get_unlock_ability (bootloader) get_unlock_ability: 0
OKAY [ 0.002s]
Finished. Total time: 0.005s
PS C:\platform-tools> ./fastboot flashing unlock FAILED (remote: 'Flashing Unlock is not allowed
')
fastboot: error: Command failed
PS C:\platform-tools> ./fastboot set_active a Setting current slot to 'a' FAILED (remote: 'Slot Change is not allowed in Lock State
')
fastboot: error: Command failed
PS C:\platform-tools>
How can i use EDL?
Sapper Morton said:
Since your bootloader is locked, and there's no proper system.img in slot B, you must change it to slot A; however it's not possible in locked state, first check if it's possible to unlock, by running:
Code:
fastboot flashing get_unlock_ability
If the output is 0, you cannot unlock, and EDL is a must, otherwise, the output will be 1, therefore, unlock is possible, then proceed with the following steps:
Code:
fastboot flashing unlock
Code:
fastboot set_active a
Code:
fastboot flashing lock
As explained above, it's not possible to change slot without unlocking the bootloader.
Click to expand...
Click to collapse
msatyanarayana said:
Change current-slot to 'a' and reboot.
Click to expand...
Click to collapse
PS C:\platform-tools> ./fastboot set_active a Setting current slot to 'a' FAILED (remote: 'Slot Change is not allowed in Lock State
')
fastboot: error: Command failed
PS C:\platform-tools>
Not allowed in Lock State.
Is there any way to oem unlock without going to Debugging Mode -> OEM enable?
I can't boot my system and recovery.
bgsebiosjr said:
Not allowed in Lock State.
Is there any way to oem unlock without going to Debugging Mode -> OEM enable?
I can't boot my system and recovery.
Click to expand...
Click to collapse
EDL mode and authorized Mi account. You should contact your nearest Xiaomi service center or use some online service (you might need to open your phone yourself in such case).
I have been trying to root my device with no luck. I cannot run most fastboot commands
when I run "fastboot getvar all" only one variable is returned
-----------------------------------------------------------------
C:\Windows\system32>fastboot getvar all
all: locked: yes
finished. total time: 0.013s
------------------------------------------------------------------
when I try to unlock, I get the following error
------------------------------------------------------
C:\Windows\system32>fastboot flashing unlock
...
FAILED (remote: Not implemet.)
finished. total time: 0.006s
------------------------------------------------------
Almost all fastboot commands return the above response. I have enabled USB debugging and toggled oem unlocking. I have ran out of options please help. I have even updated my adb_fastboot to the latest release.
Hello, i have a p20 lite that bricked after a night of charging, and I whould like to have some ideas to have informations to understand the problem.
If I press the vol - button and I connect the USB i have the phone into fastboot (Phone locked)
I downloaded the USB driver from here https://forum.xda-developers.com/t/...sb-driver-installer-tool-for-windows.3999445/
and Minimal_ADB_Fastboot_v1.4.3 but I can't have any useful information...
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem get-product-model
...
FAILED (remote: FAIL)
finished. total time: 0.006s
Click to expand...
Click to collapse
fastboot oem get-build-number
...
FAILED (unknown status code)
finished. total time: 0.136s
Click to expand...
Click to collapse
brazoayeye said:
Hello, i have a p20 lite that bricked after a night of charging, and I whould like to have some ideas to have informations to understand the problem.
If I press the vol - button and I connect the USB i have the phone into fastboot (Phone locked)
I downloaded the USB driver from here https://forum.xda-developers.com/t/...sb-driver-installer-tool-for-windows.3999445/
and Minimal_ADB_Fastboot_v1.4.3 but I can't have any useful information...
Click to expand...
Click to collapse
Look here:
https://forum.xda-developers.com/t/...squares-only-able-to-access-fastboot.4226271/
https://forum.xda-developers.com/t/huawei-p20-lite-bricked.4331729/
https://forum.xda-developers.com/t/p20-lite-bootloop.4230037/post-84447333
brazoayeye said:
I downloaded the USB driver from here
Click to expand...
Click to collapse
install Hisuite on a computer and try again with Minimal ADB.
From https://forum.xda-developers.com/t/...squares-only-able-to-access-fastboot.4226271/
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem get-build-number
...
FAILED (unknown status code)
finished. total time: 0.136s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem get-product-model
...
FAILED (remote: FAIL)
finished. total time: 0.136s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar vendorcountry
getvar:vendorcountry FAILED (remote: cannot get vendorcountry in oeminfo)
finished. total time: 0.144s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem oeminforead-CUSTOM_VERSION
...
FAILED (remote: Read oeminfo failed!)
finished. total time: 0.148s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem oeminforead-SYSTEM_VERSION
...
FAILED (remote: Read oeminfo failed!)
finished. total time: 0.145s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem battery_present_check
...
(bootloader) 3326mv
OKAY [ 0.015s]
finished. total time: 0.019s
Click to expand...
Click to collapse
I cannot enter in the recovery
Is there a way to extract data from the phone before trying with erase user data?
Thanks
brazoayeye said:
Is there a way to extract data from the phone before trying with erase user data?
Click to expand...
Click to collapse
Nope bro.
I cannot even erase userdata
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase userdata
erasing 'userdata'...
FAILED (remote: Command not allowed)
finished. total time: 0.016s
Click to expand...
Click to collapse
What should I do to try to unbrick it?
brazoayeye said:
I cannot even erase userdata
What should I do to try to unbrick it?
Click to expand...
Click to collapse
I gave you a link, you didn't read, did you?
IMO it's hardware problem, so board FW won't help you...