I have tried to unlock my bootloader using fastboot flashing unlock and fastboot flashing unlock_critical, however I get the error message:
Code:
(bootloader) Start unlock flow
FAILED (remote: '
Unlock operation is not allowed
')
fastboot: error: Command failed
I have turned on OEM unlocking in developer settings, and the output of fastboot flashing get_unlock_ability is:
Code:
(bootloader) unlock_ability = 16777216
OKAY [ 0.002s]
Finished. Total time: 0.002s
From that output, the bootloader unlock should work, however, it does not. Please help me.
Related
Hi everyone, I'm done and out of any ideas. Never before have I bricked my phone . Now I don't know what to do. Played before only with Samsung phones, they were waaay easier to play with.
Let me tell you my story:
1. Got P9 Lite with L21C22B120 rom (brand C22 from Poland)
2. No newer version available, decided to debrand / apply newer - flashed L21C432B161 (~3GB update.app), info showed L21C900B161 - need to change oeminfo etc.
3. [SRK Tool ] Unlocked bootloader and installed TWRP
4. [SRK Tool + TWRP] Built Root method via adb sideload failed, so installed SuperSu via TWRP from another source - success
5. [SRK Tool] Flashed oeminfo C432 Europe - success, but after that info showed C432B161 without L21
6. Flashed once more with the same B161 firmware - perfect info L21C432B161 but UI theme and icons got corrupted like that: https://forum.xda-developers.com/p9-plus/help/wrong-icons-c900-to-c432-failed-im-t3490561 and tried to flash mentioned hw_folder with SRK Tool.
7. [TWRP] Played with wipe / factory reset - couldn't boot anymore, TWRP showed "No OS installed" and "unable to mount /data" (it had 0MB, couldn't wipe it)
8. Then RESCUE MODE showed up and still I can't pass by it - exactly like here: https://forum.xda-developers.com/p8lite/help/stuck-rescue-mode-screen-please-help-t3244872 - only fastboot&rescue available.
What I have tried several times:
1. Flashing firmware C432B161 and C432B120 - failure at 5% (incompatibility)
2. Fastboot flash boot.img, recovery.img, system.img and cust.img (extracted from B120 and B161)- success, still rescue mode loop
3. Locking and unlocking bootloader with SRK Tool, flashing stock recovery and TWRP - success, still unable to load any recovery
4. Fastboot flashing FW_hifi.img - FAILED <remote: command not allowed>
Summary:
1. Looped Rescue mode shows: Please update system again, Func no : 8 (hifi image), Error no : 1 (security verify failed)
2. Fastboot&Rescue mode shows: Phone unlocked, FRP Unlock. Fastboot works.
3. Flashing main images doesn't change enything, can't flash corrupted(?) hifi image.
4. Maybe there is something wrong with my Bootloader? Is it truly unlocked? SRK Tool shows bootloader "unlocked" but many of the fastboot commands (i.e. getvar or oem) return "Failed, remote: command not allowed"
Any ideas in any of your clever or experienced heads? Should I try to flash that magical hifi image somehow or to flash some "compatibile" firmware (don't know which one wouldn't return that error).
Tried some fastboot commands, seems like I have found the reason for ROMs incompatibility:
fastboot getvar rescue_version
rescue_version: rescue0.3
finished. total time: 0.071s
fastboot getvar rescue_phoneinfo
rescue_phoneinfo: VNS-C432B161
finished. total time: 0.011s
fastboot oem get-product-model
...
(bootloader) hi6250
OKAY [ 0.011s]
finished. total time: 0.013s
fastboot oem get-psid
...
(bootloader) SN:BUC4C16929(...)
(bootloader) IMEI:863126032(...)
(bootloader) IMEI:863126032(...)
OKAY [ 0.011s]
finished. total time: 0.012s
fastboot getvar vendorcountry
vendorcountry: hw/eu
finished. total time: 0.010s
fastboot oem check-rootinfo
...
(bootloader) old_stat: SAFE
(bootloader) now_stat: SAFE
(bootloader) change_time: 0000000000
(bootloader) Check System: Decode fail
OKAY [ 0.018s]
finished. total time: 0.020s
fastboot oem get-build-number
...
(bootloader) :VNS-C432B161
OKAY [ 0.012s]
finished. total time: 0.013s
fastboot oem device-info
...
FAILED (remote: Command not allowed)
finished. total time: 0.013s
What happened to L21 model in my build and model number? Is it corrupted?
Install os manually via adb mounting boot system and the other two things (i don't remember all and i don't have any link)
You can go to Twrpmeticulus?
Thanks guys! I flashed Meticulus TWRP - still couldn't enter it but accidentally discovered the (weird) way. I could go to it only with USB cable connected to computer and by pressing Vol+, Vol- and Power simultaneously, releasing them upon Huawei Logo. From there (TWRP) I rooted my device (adb sideload SuperSU 2.65), replaced oeminfo file via this tutorial - https://forum.xda-developers.com/huawei-p9lite/how-to/request-oeminfo-c432-p9-lite-t3427386 - and voila, I could finally flash C432B161 ROM without incompatibility error. Problem solved, hifi error gone of course.
I have Moto X play XT1563. It was stuck in a boot loop - moto logo->circle and "erasing"->reboot
Fastboot and ADB works
I tried to flash new firmware (stock image) - failed:
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
based on that and research I decided to unlock bootloader, which ended up with:
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
since phone is unalbe to boot I cannot go to dev options. Is there any way to have it done using adb or fastboot? even low level linux way to change something in the config?
or (easier way) - anyone aware where can I find new Bell firmware? now I have M8936_2020632.44.03.21.57R LUX_BELLCA_CUST
Appreciate any suggestions
Check here
https://github.com/motoxplay/stock
there is a bell firmware but is tagged with a BELL? so, don´t know if will it work
Cheers.
Thanks - checked that before - this one is 6.0.1 and I need 7.1.1
Version NPD26.48-21-1 to be exact
I also tried to boot into custom recovery (.img file from here:
https://forum.xda-developers.com/moto-x-play/orig-development/recovery-twrp-2-8-7-0-t3194656):
fastboot boot boot.img
failed:
downloading 'boot.img'...
OKAY [ 0.401s]
booting...
FAILED (remote failure)
finished. total time: 0.405s
stingu said:
I also tried to boot into custom recovery (.img file from here:
https://forum.xda-developers.com/moto-x-play/orig-development/recovery-twrp-2-8-7-0-t3194656):
fastboot boot boot.img
failed:
downloading 'boot.img'...
OKAY [ 0.401s]
booting...
FAILED (remote failure)
finished. total time: 0.405s
Click to expand...
Click to collapse
Do you have an unlocked bootloader?
Did you try to install TWRP ? It's not bootloader unlocked, is it ?
Bootloader is locked, while trying to unlock it I get:
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
Flashing and booting fails, for stock and TWRP
Not sure does this make sense, but by recovery mode is 7.1.1 and when I check image using fastboot command I get:
(bootloader) ro.build.fingerprint[0]: motorola/lux_retca/lux:6.0.1/MPDS2
(bootloader) ro.build.fingerprint[1]: 4.107-52-3-5/5:user/release-keys
is it possible to have recovery 7.1.1 and system 6.0.1?
Not sure does this make sense, but by recovery mode is 7.1.1 and when I check image using fastboot command I get:
(bootloader) ro.build.fingerprint[0]: motorola/lux_retca/lux:6.0.1/MPDS2
(bootloader) ro.build.fingerprint[1]: 4.107-52-3-5/5:user/release-keys
is it possible to have recovery 7.1.1 and system 6.0.1?
I am trying to unlock Lenovo Tablet TB-7504x but with no success.
--
$ fastboot devices
8SSP69A6NLRAHA2287J00FM fastboot
$ fastboot flashing get_unlock_ability
...
FAILED (remote: unknown command)
finished. total time: 0.003s
$ fastboot oem unlock
...
FAILED (remote: unknown command)
finished. total time: 0.003s
Same issue.No success in unlocking bootloader
I have the same problem.
If you get how to do it please mail me at
[email protected]
Hello,
I can unlock my phone :
fastboot oem device-info
(bootloader) Verity mode: true
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: true
(bootloader) ABL Info: Q-ZE620KLXXXX
OKAY [ 0.008s]
finished. total time: 0.008s
but I don't make TWRP...
For flash it was "good" but it's recovery original with command line
and for boot in TWRP I have :
fastboot boot 'recovery.img'
downloading 'boot.img'...
OKAY [ 0.637s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.638s
I tested 3 TWRP different ones with the same result
Can you help me please ?
Please help me, I have no solution, and I want to put custom rom in my phone.
I have to put TWRP in my phone for custom rom
Ciao!
this error is common on my Asus x00QD when i use stock Android 10, you need to downgrade to 9 !
Please check on the Net for Q-P-UL-ASUS_X00QD-ASUS-16.0615.2002.120-1.1.33-user.zip and push it via SDcard or ADB, then retry with FastBoot
I can't make, when reboot, it was Android 10...
And Asus flash tool does not work, he can't find m'y phone in fastboot and recovery
Hi All,
I am trying to flash Android TV 13 beta 4 ~ to the developer tools adt-3. After flash ... the adt-3 keep reboot. And cna't load the bootloader and OS. when I try to flash the device again ... adt-3 said that FAILED (remote: 'locked device').
I would like to know how to unlock adt-3 !?
ToTo
./fastboot flashing unlock
FAILED (remote: 'unlock_ability is 0, can not unlock')
./fastboot flashing get_unlock_ability
(bootloader) get_unlock_ability: 0
OKAY [ 0.049s]
Finished. Total time: 0.050s
sudo ./flash-all.sh
[sudo] password for toto:
error: no devices/emulators found
FAILED (remote: 'unlock_ability is 0, can not unlock')
fastboot: error: Command failed
FAILED (remote: 'locked device')
fastboot: error: Command failed
Rebooting into bootloader OKAY [ 0.006s]
Finished. Total time: 0.258s
FAILED (remote: 'unlock_ability is 0, can not unlock')
fastboot: error: Command failed
******** Did you mean to fastboot format this ext4 partition?
Erasing 'data' FAILED (remote: 'locked device')
fastboot: error: Command failed
Sending 'bootloader' (1591 KB) FAILED (remote: 'locked device')
fastboot: error: Command failed
Rebooting into bootloader OKAY [ 0.006s]
Finished. Total time: 0.258s
--------------------------------------------
Bootloader Version...: 01.01.220621.133524
Baseband Version.....: N/A
Serial Number........: ACHE0000xxx
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.015s]
Checking 'version-bootloader' OKAY [ 0.014s]
extracting boot.img (16 MB) to disk... took 0.031s
archive does not contain 'boot.sig'
Sending 'boot' (16384 KB) FAILED (remote: 'locked device')
fastboot: error: Command failed
Rebooting into bootloader OKAY [ 0.006s]
Finished. Total time: 0.258s
OKAY [ 0.023s]
Finished. Total time: 0.023s
Rebooting OKAY [ 0.003s]
Finished. Total time: 0.305s
Need help to unlock adt-3
fastboot oem 'setenv lock 10101000;save'
fastboot reboot bootloader
fastboot flashing unlock
Many thanks, I using adt-3. I think oem not working ... many thanks. Here is the result.
./fastboot oem 'setenv lock 10101000;save'
FAILED (remote: 'locked device')
fastboot: error: Command failed
./fastboot flashing unlock
FAILED (remote: 'unlock_ability is 0, can not unlock')
fastboot: error: Command failed
That is the command that is within flash-all.sh for build adt3_gtv-stt1.211025.001.z3-factory-91f7efe7.
It was designed specifically to fix this particular issue/bug with the adt-3.
This problem started before android 12. Read article;
[Update: Fixed] Android TV 12 preview builds for ADT-3 can't be flashed
The first builds of Android TV 12 for Google's own ADT-3 developer device are completely broken, leaving developers unable to install them.
9to5google.com
Yes, I know ... I also go through that issue when I did Android TV 12. Right now I have the issue again. When I was doing Android TV 13 beta 4. Here flash-all.sh come with Android TV 13 beta 4.
if ! [ $($(which ./fastboot) --version | grep "version" | cut -c18-23 | sed 's/\.//g' ) -ge 2802 ]; then
echo "fastboot too old; please download the latest version at https://developer.android.com/studio/releases/platform-tools.html"
exit 1
fi
./adb reboot bootloader || true
if ! ./fastboot flashing unlock ; then
./fastboot oem 'setenv lock 10101000;save' || true
./fastboot reboot bootloader; sleep 3
./fastboot flashing unlock || true
fi
./fastboot erase data
./fastboot flash bootloader bootloader-adt3_gtv-01.01.220621.133524.img
./fastboot reboot bootloader; sleep 3
./fastboot -w --skip-reboot update image-adt3_gtv-trb4.220715.005.zip
./fastboot reboot bootloader; sleep 3
./fastboot flashing lock
./fastboot reboot
But this time ... it is not working
Are you sure that your fastboot version/drivers are new/good?
Within a few days I will try to update mine, in order to see if there are any issues.
Are you familiar with worldcup burn mode?
Obtain worldcup drivers and command line "update" program for your OS.
Once worldcup drivers are installed, hold button, starting from before power is applied, until you have a worldcup usb connection. Then run these commands using the "update" program for worldcup;
update bulkcmd "setenv lock 10100000"
update bulkcmd "saveenv"
Then reboot and see if fastboot works.
./fastboot --version
fastboot version 33.0.3-8952118
Installed as /opt/platform-tools/fastboot
I just upgrade it b4 I do the Android TV 13 Beta 4.
Sorry ... I have no idea of "worldcup burn mode"
Latest Update: The final release of Android 13 for TV is now available.
ADT-3 (Android TV)ADT3-TTT1.220909.001.B7-FACTORY-CA1F5F01.ZIP
ADT-3 (Google TV)ADT3_GTV-TTT1.220909.001.B7-FACTORY-36544A4B.ZIP
but this release ... still no help for the locked adt-3
ToToHayashi said:
Latest Update: The final release of Android 13 for TV is now available.
ADT-3 (Android TV)ADT3-TTT1.220909.001.B7-FACTORY-CA1F5F01.ZIP
ADT-3 (Google TV)ADT3_GTV-TTT1.220909.001.B7-FACTORY-36544A4B.ZIP
but this release ... still no help for the locked adt-3
Click to expand...
Click to collapse
Did you try the update method as suggested by "Deleted member 11959327" ?
To get the tool i recommend the Khadas Git (khadas/utils) then the aml-flash-tool/ is the folder with Amlogic tools
for the update tool its in tools/linux-x86/update