Need advice. My goal is to flash GSI ROM onto this thing. The treble app says it is supported. (type A)
However, the usual commands for unlocking bootloader seem to indicate it is either already unlocked but not telling me or locked and not unlockable..?
This is a unisoc SC9863a
baseband: FM_BASE_18B_W19.08.1_P11 | SC9863a_modem | 04-26-2019 MARLIN2_17A_RLS1_W19.17.7 | sharkl3_cm4 | 04-28-2019
kernel: 4.4.147+ (20190703)
build number: PPR1 180610.011
android: 9 pie
WIKO/W-V800-EEA/W-V800
9/PPR1.180610.011/08018
unrooted > MTK-su and several oneroot options not working (although they might on oreo if I can find the factory rom)
OEM unlocking enabled in developer options
In fastboot you get:
fastboot flashing unlock > FAILED (remote: Not implemet.)
fastboot oem unlock > FAILED (remote: unknown cmd.)
fastboot oem get_unlock_data > FAILED (remote: unknown cmd.)
fastboot flashing unlock_critical > FAILED (remote: Not implement.)
I tried following this process: (from here (Mod Edit: Link removed)
./fastboot oem get_identifier_token
./signidentifier_unlockbootloader.sh XXXXXXXXXXXXXXX rsa4096_vbmeta.pem signature.bin
./fastboot flashing unlock_bootloader signature.bin
last command returns with: "downloading 'unlock_message'...
OKAY [ 0.001s]
unlocking bootloader...
FAILED (remote: Unlock bootloader fail.)
finished. total time: 0.104s"
additional questions:
Can I just flash a certain recovery somehow?
Do I have to try something complicated like this: (Mod Edit: Link removed)
Have you got root on your view 3 lite?
go0 said:
In fastboot you get:
fastboot flashing unlock > FAILED (remote: Not implemet.)
fastboot oem unlock > FAILED (remote: unknown cmd.)
fastboot oem get_unlock_data > FAILED (remote: unknown cmd.)
fastboot flashing unlock_critical > FAILED (remote: Not implement.)
Click to expand...
Click to collapse
Indicates the FastBoot implemented in device's bootloader doesn't support these subcommands. Obviously OEM/Carrier doesn't want that device's bootloader gets unlocked.
anonym6x6 said:
Have you got root on your view 3 lite?
Click to expand...
Click to collapse
If oreo exists for this and you know where to get it, let me know and I'll try.
If I can get root, what would you recommend trying to unlock bootloader?
jwoegerbauer said:
Indicates the FastBoot implemented in device's bootloader doesn't support these subcommands. Obviously OEM/Carrier doesn't want that device's bootloader gets unlocked.
Click to expand...
Click to collapse
OK...
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
I tried to restore and reinstall ROM in numerous ways, including adb, fastboot and sdcard. I even tried Funky Huawei.
Currently I can get to eRecovery and to TWRP. Fastboot works without problem. But that's about it, boot sometimes goes to Lineage boot splash, which I used prior the Magisk update.
Thanks for help in advance
Here is info from fastboot:
fastboot oem get-product-model:
<bootloader> CMR-AL09
fastboot getvar vendorcountry:
vendorcountry: hw/eu
fastboot oem get-build-number:
(bootloader) :CMR-AL09 8.0.0.122(C432)
fastboot getvar rescue_enter_recovery:
getvar:rescue_enter_recovery FAILED (remote: FAIL:need all image flashed!)
fastboot oem oeminforead-system_version
FAILED (remote: The reason of failed input oem_nv_item error!)
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).
Hello, I've been struggling with this for hours and nothing seems to be working.
I have a Motorola DROID RAZR XT912 running Android 4.1.2 JB, it's already rooted but I'm attempting to unlock the bootloader using this guide.
I've installed the Android SDK as well as the latest USB Drivers.
I enter my mobile device into "AP Fastboot Flash Mode (S)" by holding power + volume down.
I plug my device into my laptop, the phone says "USB Connected".
I open a terminal in Windows 11 in my SDK tools directory [C:\Users\FOS11\AppData\Local\Android\Sdk\platform-tools]
I use the command "fastboot devices" to test if fastboot is working and detecting my device.
It properly returns with "014FFB290D006013 fastboot"
I attempt to use the command "fastboot oem get_unlock_data"
It returns with an error:
"FAILED (remote: 'unsupported command')
fastboot: error: Command failed"
I have followed the guide exactly up to this point with no errors, I have not found any forum or guide saying anything about this error, I must be missing something very simple, right? please let me know if any additional information is needed.
some moto/lenovo do not require unlock code. such old device maybe isn't even locked. just curious what happen for?
Code:
fastboot flashing get_unlock_ability
fastboot flashing unlock
fastboot oem unlock
fastboot getvar all
could be also possible it's non-unlockable bootloader (not intended by manufacturer, unofficial methods might exist)
"Your device is NOT eligible for bootloader unlock if the CID value returned is one of these: 0x0001, 0x0002, 0x0004, 0x0005, 0x0006, 0x0008, 0x000A, 0x000F, 0x0010, 0x0011"
aIecxs said:
some moto/lenovo do not require unlock code. such old device maybe isn't even locked. just curious what happen for?
Code:
fastboot flashing get_unlock_ability
fastboot flashing unlock
fastboot oem unlock
fastboot getvar all
could be also possible it's non-unlockable bootloader (not intended by manufacturer, unofficial methods might exist)
"Your device is NOT eligible for bootloader unlock if the CID value returned is one of these: 0x0001, 0x0002, 0x0004, 0x0005, 0x0006, 0x0008, 0x000A, 0x000F, 0x0010, 0x0011"
Click to expand...
Click to collapse
"fastboot flashing get_unlock_ability"
returns
"FAILED (remote: 'unsupported command')
fastboot: error: Command failed"
"fastboot flashing unlock"
returns
"FAILED (remote: 'unsupported command')
fastboot: error: Command failed"
"fastboot oem unlock"
returns
"(bootloader) fastboot oem unlock disabled!
FAILED (remote: '')
fastboot: error: Command failed"
"fastboot getvar all"
returns
"getvar:all FAILED (remote: 'unsupported command')
Finished. Total time: 0.000s"
Additional info: phone has no SIM card inserted (Not sure if this is useful)
(bootloader) fastboot oem unlock disabled!
probably means this bootloader cannot unlocked.
But last cmd shouldn't fail.. try special mfastboot.exe or more recent platform-tools
Code:
fastboot getvar unlocked
fastboot getvar securestate
fastboot getvar sku
fastboot getvar cid
or just try if unlocked by doing something invasive (does not harm on cache)
Code:
fastboot oem fb_mode_set
fastboot format cache
fastboot oem fb_mode_clear
aIecxs said:
(bootloader) fastboot oem unlock disabled!
probably means this bootloader cannot unlocked.
But last cmd shouldn't fail.. try special mfastboot.exe or more recent platform-tools
Code:
fastboot getvar unlocked
fastboot getvar securestate
fastboot getvar sku
fastboot getvar cid
or just try if unlocked by doing something invasive (does not harm on cache)
Code:
fastboot oem fb_mode_set
fastboot format cache
fastboot oem fb_mode_clear
Click to expand...
Click to collapse
Using your attached platform-tools version,
'mfastboot.exe' is not recognized as an internal or external command,
operable program or batch file.
fastboot getvar unlocked
returns
unlocked: no
fastboot getvar securestate & fastboot getvar sku
returns
FAILED (remote: 'unsupported command')
fastboot getvar cid
returns
cid: 2
fastboot oem fb_mode_set
returns
OKAY [ 0.016s]
fastboot format cache
returns
FAILED (remote: 'protocol error')
fastboot oem fb_mode_clear
returns
OKAY [ 0.016s]
Additional info: phone was rooted with a tool called "RAZR Blade"
Thank you for your help so far.
cid: 0x0002 "Your device is NOT eligible for bootloader unlock"
Frequently Asked Questions - Motorola Razr [XT912, XT910, XT908] (2015)
Frequently Asked Questions Motorola Razr [XT912, XT910, XT908] This a short list of frequently asked questions in this device forum and the answers often given as a response. It should serve as a starting point for gathering knowledge and...
forum.xda-developers.com
hi, i received other error, xt-2239-16 moto e22i,
C:\Users\Rosaly\Desktop\platform-tools>fastboot getvar unlocked
unlocked: no
Finished. Total time: 0.000s
C:\Users\Rosaly\Desktop\platform-tools>fastboot getvar securestate
getvar:securestate FAILED (remote: 'Unknown variable')
Finished. Total time: 0.016s
C:\Users\Rosaly\Desktop\platform-tools>fastboot getvar securestate
getvar:securestate FAILED (remote: 'Unknown variable')
Finished. Total time: 0.000s
C:\Users\Rosaly\Desktop\platform-tools>fastboot getvar sku
getvar:sku FAILED (remote: 'Unknown variable')
Finished. Total time: 0.016s
C:\Users\Rosaly\Desktop\platform-tools>fastboot getvar cid
getvar:cid FAILED (remote: 'Unknown variable')
Finished. Total time: 0.016s
C:\Users\Rosaly\Desktop\platform-tools>fastboot oem fb_mode_set
FAILED (remote: 'Unable to open fastboot HAL')
fastboot: error: Command failed
C:\Users\Rosaly\Desktop\platform-tools>
C:\Users\Rosaly\Desktop\platform-tools>fastboot format cache
FAILED (remote: 'Invalid partition')
fastboot: error: Command failed
C:\Users\Rosaly\Desktop\platform-tools>fastboot oem fb_mode_clear
FAILED (remote: 'Unable to open fastboot HAL')
fastboot: error: Command failed
i m not read cid, could be help me, please.
tks
Rocha
I ran the command in the title and now I can't get out of fastboot and can't get into fastbootd.
I am an amateur and don't even know what this command means. I just wanted to install LineageOS on my xiaomi redmi note 10 je with GSI. I tried to install the downloaded img file for GSI with the command fastboot flash system lineage-19.1-202206130-UNOFFICIAL-arm64_bvS.img but it didn't work. How do I get it to work with MIUI or whatever it is for now? Please.
In case you're wondering, I got the above GSI file from https://sourceforge.net/projects/andyyan-gsi/files/lineage-19.x/
i_plevra said:
I ran the command in the title and now I can't get out of fastboot and can't get into fastbootd.
I am an amateur and don't even know what this command means. I just wanted to install LineageOS on my xiaomi redmi note 10 je with GSI. I tried to install the downloaded img file for GSI with the command fastboot flash system lineage-19.1-202206130-UNOFFICIAL-arm64_bvS.img but it didn't work. How do I get it to work with MIUI or whatever it is for now? Please.
In case you're wondering, I got the above GSI file from https://sourceforge.net/projects/andyyan-gsi/files/lineage-19.x/
Click to expand...
Click to collapse
hello ... if you are currently on fastboot mode and your pc can detect it then you can use MiFlash Tool to install MIUI again...
if you have adb & fastboot (and drivers) installed run fastboot devices with the phone connected , if your phone is recognized then go ahead
one question ... your phone came with Global MIUI or other MIUI Region? (India , EEA , Indonesia , etc)
and please DO NOT RUN commands that you don't know about.. fastboot erase commands are common to hard brick phones
you must ask before running any command
if your pc have all the drivers , i assume u have it coz u ran the command . for gsi , u need to disable vbmeta 1st , later you can flash and boot the los18/19.1 gsi . fastboot.exe --disable-verity --disable-verification flash vbmeta vbmeta.img get vbmeta.img through official MIUI fastboot rom.
alonsoj636 said:
hello ... if you are currently on fastboot mode and your pc can detect it then you can use MiFlash Tool to install MIUI again...
if you have adb & fastboot (and drivers) installed run fastboot devices with the phone connected , if your phone is recognized then go ahead
one question ... your phone came with Global MIUI or other MIUI Region? (India , EEA , Indonesia , etc)
and please DO NOT RUN commands that you don't know about.. fastboot erase commands are common to hard brick phones
you must ask before running any command
Click to expand...
Click to collapse
This smartphone is a Japan-only model for a company called au, but probably a global version is available. The size is a little different but the base is redmi note 10 5g I just checked and it seems to be 5g I'm not confident I'll use miflash. It's a hassle to borrow a phone from a family member, stick a sim in it and have to receive an authentication SMS.
pihpih95 said:
if your pc have all the drivers , i assume u have it coz u ran the command . for gsi , u need to disable vbmeta 1st , later you can flash and boot the los18/19.1 gsi . fastboot.exe --disable-verity --disable-verification flash vbmeta vbmeta.img get vbmeta.img through official MIUI fastboot rom.
Click to expand...
Click to collapse
I tried your command but the result was this (vbmeta.img I used of this site tentatively https://note.com/nuilpointer/n/n8edba9a7bc49)
fastboot --disable-verity --disable-verification flash vbmeta /Users/miyaharaiam/Downloads/xiaomi-iris-XIG02-MIUI-V12.5.12.0.RKRJPKD-ota-with-repacked-super/vbmeta.img
Rewriting vbmeta struct at offset: 0
Sending 'vbmeta' (8 KB) OKAY [ 0.004s]
Writing 'vbmeta' FAILED (remote: 'Flashing is not allowed in Lock State')
fastboot: error: Command failed
and the below too.
fastboot oem device-info
(bootloader) Verity mode: true
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: true
OKAY [ 0.001s]
Finished. Total time: 0.001s
I am confused why is not unlocked....
now I can't use Windows for some reasons so am using m1 mac, this pc can't use the miflash so am trying GSI boot in a while
i_plevra said:
I tried your command but the result was this (vbmeta.img I used of this site tentatively https://note.com/nuilpointer/n/n8edba9a7bc49)
fastboot --disable-verity --disable-verification flash vbmeta /Users/miyaharaiam/Downloads/xiaomi-iris-XIG02-MIUI-V12.5.12.0.RKRJPKD-ota-with-repacked-super/vbmeta.img
Rewriting vbmeta struct at offset: 0
Sending 'vbmeta' (8 KB) OKAY [ 0.004s]
Writing 'vbmeta' FAILED (remote: 'Flashing is not allowed in Lock State')
fastboot: error: Command failed
and the below too.
fastboot oem device-info
(bootloader) Verity mode: true
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: true
OKAY [ 0.001s]
Finished. Total time: 0.001s
I am confused why is not unlocked....
Click to expand...
Click to collapse
big problem...
your device is locked which means that flashing anything (vbmeta , recovery) or use MiFlash Tool will not be possible because unlocked bootloader is compulsory
i_plevra said:
I tried your command but the result was this (vbmeta.img I used of this site tentatively https://note.com/nuilpointer/n/n8edba9a7bc49)
fastboot --disable-verity --disable-verification flash vbmeta /Users/miyaharaiam/Downloads/xiaomi-iris-XIG02-MIUI-V12.5.12.0.RKRJPKD-ota-with-repacked-super/vbmeta.img
Rewriting vbmeta struct at offset: 0
Sending 'vbmeta' (8 KB) OKAY [ 0.004s]
Writing 'vbmeta' FAILED (remote: 'Flashing is not allowed in Lock State')
fastboot: error: Command failed
and the below too.
fastboot oem device-info
(bootloader) Verity mode: true
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: true
OKAY [ 0.001s]
Finished. Total time: 0.001s
I am confused why is not unlocked....
Click to expand...
Click to collapse
do you still have mi recovery, or only have fastboot?
LR7875 said:
do you still have mi recovery, or only have fastboot?
Click to expand...
Click to collapse
if mi recovery means the recovery mode, fastboot reboot recovery and fastboot reboot bootloader just make appear the fastboot display.
i_plevra said:
if mi recovery means the recovery mode, fastboot reboot recovery and fastboot reboot bootloader just make appear the fastboot display.
Click to expand...
Click to collapse
and does fastboot oem unlock or fastboot oem unlock_critical work
LR7875 said:
and does fastboot oem unlock or fastboot oem unlock_critical work
Click to expand...
Click to collapse
both were same result.
fastboot oem unlock_critical
FAILED (remote: 'Token Verify Failed, Reboot the device
')
fastboot: error: Command failed
have u apply to unlock bootloader through official method ?
i_plevra said:
both were same result.
fastboot oem unlock_critical
FAILED (remote: 'Token Verify Failed, Reboot the device
')
fastboot: error: Command failed
Click to expand...
Click to collapse
https://forum.xda-developers.com/t/...oken-verify-failed-reboot-the-device.4300755/ this is for redmi note 10 pro but is worth to read. maybe it can help