Database Develop

Xperia Z fails to unlock bootloader

When I run cmd fastboot.exe -i 0x0fce getvar version I get
version:0.5
finished. total time -0.000s
Click to expand...
Click to collapse
Then I run fastboot.exe -i 0x0fce oem unlock 0xKEY (With my key from Sony) and I get
...
FAILED <remote: command not allowed>
finished. total time: 0.000s
Click to expand...
Click to collapse
How do I fix this to unlock the boot loader?!?!
Bootloader unlock allowed: Yes
Click to expand...
Click to collapse

Hello try using flashtool has a procedure very automatic.

Same result

I already wrote it
Bootloader unlock allowed: Yes
Click to expand...
Click to collapse

i tried

[GUIDE] How to Unlock Bootloader ZC554KL (DO WITH YOUR OWN RISK!)

I realize that our device have the source code on Asus website and the unlock tool haven't been released by Asus. That's maybe a chance for unlocking bootloader and play guessing that our device is just using similarly same method with nexus or other legacy bootloader locking mechanism. Thanks, and blame Asus for that! But, I could stop thinking and doing this and (BAM!) the bootloader unlocked and I'm able to boot patched boot.img with Magisk Manager app.
READ THIS FIRST!
Before you all do this, it's recommended to do factory reset before unlocking bootloader because our device is using force encryption by default. If you didn't reset your device, you will get locked from the start and cannot doing anything even you type password or pin correctly.
PLEASE READ CAREFULLY!
1. Reboot to Bootloader by pressing power + vol up
2. Type fastboot command below:
echo > key.txt
fastboot oem get_unlock_key key.txt
fastboot reboot-bootloader
Click to expand...
Click to collapse
3. Enjoy the freedom of Android experience with annoying verifiedboot caution on the start ( Blame Google for that) but it's not a big problem.
To relock bootloader type this in fastboot (Thanks to @shakalaca for telling that in this thread)
echo > key.txt
fastboot oem reset_unlock_key key.txt
fastboot erase config
fastboot flashing lock
fastboot reboot-bootloader
Click to expand...
Click to collapse
REMEMBER! DO WITH YOUR OWN RISK! I'M NOT RESPONSIBLE FOR WHAT HAPPENS TO YOUR DEVICE AND YOUR LIFE FOR DOING THIS! GOOD LUCK!
PS: I dont have any device to take a shot from my device because this Zenfone was my only device that I have.
To do list:
- Get rid of the caution at startup that reminds our bootloader state
NOTE: This method works only for version below 215. If you're updated to latest firmware. It won't work since Asus update the bootloader. And the bootloader just temporarily unlocked with this method. If device restarted, the bootloader get locked automatically

Не работает
Here's what happens:
C:\adb>fastboot oem get_unlock_key
...
(bootloader) @!
OKAY [ 0.004s]
finished. total time: 0.005s
C:\adb>fastboot oem unlock-go
...
FAILED (remote: unknown command)
finished. total time: 0.004s

aaaaaaziskurnia said:
i realize that our device have the source code on asus website and the unlock tool haven't been released by asus. That's maybe a chance for unlocking bootloader and play guessing that our device is just using similarly same method with nexus or other legacy bootloader locking mechanism. Thanks, and blame asus for that! But, i could stop thinking and doing this and (bam!) the bootloader unlocked and i'm able to boot patched boot.img with magisk manager app.
Read this first!
Before you all do this, it's recommended to do factory reset before unlocking bootloader because our device is using force encryption by default. If you didn't reset your device, you will get locked from the start and cannot doing anything even you type password or pin correctly.
Please read carefully!
1. Reboot to bootloader by pressing power + vol up
2. Type fastboot command "fastboot oem get_unlock_key" then press enter key
3. After that type "fastboot oem unlock-go"then hit enter again
4. Check the bootloader status by rebooting to bootloader back using command "fastboot reboot-bootloader"
5. Enjoy the freedom of android experience with annoying verifiedboot caution on the start ( blame google for that) but it's not a big problem.
Remember! Do with your own risk! I'm not responsible for what happens to your device and your life for doing this! Good luck!
Ps: I dont have any device to take a shot from my device because this zenfone was my only device that i have.
To do list:
- find a hack to relock again the bootloader
- get rid of the caution at startup that reminds our bootloader state
Click to expand...
Click to collapse
you have 2/16 or 3/32 ???

Johann Richter said:
you have 2/16 or 3/32 ???
Click to expand...
Click to collapse
Actually not the size of the rom and ram. But the SOC, I have the msm8937. Check yours pls

aaaaaaziskurnia said:
Actually not the size of the rom and ram. But the SOC, I have the msm8937. Check yours pls
Click to expand...
Click to collapse
I have 8917, no options with this?

Johann Richter said:
I have 8917, no options with this?
Click to expand...
Click to collapse
Try this methods. Because asus share same project named ZC554KL in the source code I've inspected, It's worth to try.

aaaaaaziskurnia said:
Try this methods. Because asus share same project named ZC554KL in the source code I've inspected, It's worth to try.
Click to expand...
Click to collapse
After much suffering, 15 times to unlock the bootloader. Thank you!!!

Johann Richter said:
After much suffering, 15 times to unlock the bootloader. Thank you!!!
Click to expand...
Click to collapse
I've suffering same thing as you in the first but it's unlocked. Good luck and enjoy development

Phone should be unlocked once you've done "fastboot oem get_unlock_key" , you can then verify after "fastboot reboot-bootloader" with on-screen-message.
To lock the phone again:
Code:
echo > key.txt
fastboot oem reset_unlock_key key.txt
fastboot erase config
fastboot flashing lock
fastboot reboot-bootloader
It works on my TW sku ..

shakalaca said:
Phone should be unlocked once you've done "fastboot oem get_unlock_key" , you can then verify after "fastboot reboot-bootloader" with on-screen-message.
To lock the phone again:
It works on my TW sku ..
Click to expand...
Click to collapse
Thanks shalaca, I'll include it to the first Page :good::laugh:

shakalaca said:
Phone should be unlocked once you've done "fastboot oem get_unlock_key" , you can then verify after "fastboot reboot-bootloader" with on-screen-message.
To lock the phone again:
Code:
echo > key.txt
fastboot oem reset_unlock_key key.txt
fastboot erase config
fastboot flashing lock
fastboot reboot-bootloader
It works on my TW sku ..
Click to expand...
Click to collapse
thanks a lot, very useful information
---------- Post added at 09:52 AM ---------- Previous post was at 09:49 AM ----------
On our device there is TWRP?

Johann Richter said:
Phone should be unlocked once you've done "fastboot oem get_unlock_key" , you can then verify after "fastboot reboot-bootloader" with on-screen-message.
To lock the phone again:
thanks a lot, very useful information
---------- Post added at 09:52 AM ---------- Previous post was at 09:49 AM ----------
On our device there is TWRP?
Click to expand...
Click to collapse
Just wait for TWRP. I've got built TWRP but still messed up. Stil investigating.

tks for your guide
can you root with supersu?? or can you send a custom recovery to flash zip file?

Mr Foot said:
can you root with supersu?? or can you send a custom recovery to flash zip file?
Click to expand...
Click to collapse
I suggest using Magisk. Since the stock rom protected /system by selinux. If you doing any modifications in /system , it will result hangs or unbootable device and you should clean flash again.

If someone is interested in building TWRP here's the source: https://github.com/shakalaca/android_device_asus_X00I
I've already built one https://www.androidfilehost.com/?fid=673791459329051335
And currently I don't have the phone on my hand so feel tree to fork/build/test/fix/release TWRP ..

shakalaca said:
If someone is interested in building TWRP here's the source: https://github.com/shakalaca/android_device_asus_X00I
I've already built one https://www.androidfilehost.com/?fid=673791459329051335
And currently I don't have the phone on my hand so feel tree to fork/build/test/fix/release TWRP ..
Click to expand...
Click to collapse
so is he a worker?

Johann Richter said:
so is he a worker?
Click to expand...
Click to collapse
who ? me ?

shakalaca said:
who ? me ?
Click to expand...
Click to collapse
Thanks, it works

shakalaca said:
If someone is interested in building TWRP here's the source: https://github.com/shakalaca/android_device_asus_X00I
I've already built one https://www.androidfilehost.com/?fid=673791459329051335
And currently I don't have the phone on my hand so feel tree to fork/build/test/fix/release TWRP ..
Click to expand...
Click to collapse
I'm already have a device tree written two weeks ago.
https://github.cm/aaaaaaziskurnia/twrp_device_asus_X00ID
But messed up many times so I freshly uploads all the device tree.
I'm still new but I can sure that I'm fast learner. Should we collab?

shakalaca said:
who ? me ?
Click to expand...
Click to collapse
Good day, which firmware do you use?

Hot to unbrick MiA2

Hi Friends.
I have MiA2 unlocked and bricked.
It starts only in twrp and fastboot mode
Can anyone help me to unbrick?
Thanks

https://forum.xda-developers.com/showpost.php?p=77302899&postcount=4

Writing devcfg_a failed
Flashing is not allowed forum critical partition

b1gb1ng said:
Writing devcfg_a failed
Flashing is not allowed forum critical partition
Click to expand...
Click to collapse
fastboot flashing unlock_critical

b1gb1ng said:
Hi Friends.
I have MiA2 unlocked and bricked.
It starts only in twrp and fastboot mode
Can anyone help me to unbrick?
Thanks
Click to expand...
Click to collapse
https://en.miui.com/thread-3052407-1-1.html

Daha3ker said:
fastboot flashing unlock_critical
Click to expand...
Click to collapse
when I launch this command it is not recognised, I just have a list of commands in fastboot
what should I do?

fastboot -w
Be warned, it will wipe your device.

Sift said:
fastboot -w
Be warned, it will wipe your device.
Click to expand...
Click to collapse
I still have the same problem command "fastboot flashing unlock_critical" is not recognised and if I try to flash any img I receive the error message "Flashing is not allowed for critical partitions"

Grooverit said:
I still have the same problem command "fastboot flashing unlock_critical" is not recognised and if I try to flash any img I receive the error message "Flashing is not allowed for critical partitions"
Click to expand...
Click to collapse
You need to download newest adb.
https://dl.google.com/android/repository/platform-tools-latest-windows.zip

minnuss said:
You need to download newest adb.
https://dl.google.com/android/repository/platform-tools-latest-windows.zip
Click to expand...
Click to collapse
well, I updated the newest adb, now the command seems to work, but after "fastboot flashing unlock_critical" I still have this:
PS C:\android-sdk\platform-tools> fastboot flashing unlock_critical
OKAY [ 0.034s]
Finished. Total time: 0.035s
PS C:\android-sdk\platform-tools> fastboot oem device-info
(bootloader) Verity mode: true
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: false
OKAY [ 0.007s]
Finished. Total time: 0.008s
no unlock why?
---------- Post added at 03:26 PM ---------- Previous post was at 02:55 PM ----------
it was my erorr, sorry
thanks for the advice, I unlocked and than flashed stock rom after booting in edl mode
I still have to check if I still have bootloader unlocked as I get advise on start screen

Grooverit said:
I still have to check if I still have bootloader unlocked as I get advise on start screen
Click to expand...
Click to collapse
Yes it is still all unlocked.
And if you wish to thanks someone on this forum, use the thanks button in the down right corner of the post that helped you. :good:

You should visit Xiaomi service centre. They will unbrick your phone without any charge.

unlock_critical

Guys I'm in June update I already enabled camera2api in March then I closed my bootloader for getting my mobile serviced under warranty but now I can't able to unlock_critical after unlocking bootloader some one tell me that is it essential to unlock_critical to flash stock ROM in future or I can skip this step to do other flashing stuffs ...

Sivakumar$ said:
Guys I'm in June update I already enabled camera2api in March then I closed my bootloader for getting my mobile serviced under warranty but now I can't able to unlock_critical after unlocking bootloader some one tell me that is it essential to unlock_critical to flash stock ROM in future or I can skip this step to do other flashing stuffs ...
Click to expand...
Click to collapse
I think you have to unlock critical.

mariosenta said:
I think you have to unlock critical.
Click to expand...
Click to collapse
Thanks I also wanted to I'll do further flashing after unlock critical I'll reinstall all ADB and use the latest platform tool and tell you the result

I still got this same error

Sivakumar$ said:
I still got this same error
Click to expand...
Click to collapse
What error? You have to select what to do next. Type "w" and hit enter to erase all

mariosenta said:
What error? You have to select what to do next. Type "w" and hit enter to erase all
Click to expand...
Click to collapse
After erasing do I need to type the command unlock_critical

Sivakumar$ said:
After erasing do I need to type the command unlock_critical
Click to expand...
Click to collapse
https://forum.xda-developers.com/mi-a2/how-to/how-to-enabling-cam2-gcam-android-t3868766 you have very simple guide how to unlock bootloader in this tread. Please read it and folow the guide.

Sivakumar$ said:
After erasing do I need to type the command unlock_critical
Click to expand...
Click to collapse
After "fastboot -w" again my storage is erased but i can't able to do "unlock_critical" i tried even locking ny BL again but after oem unlovk i cant do critical unlock it always show me bunch of commands

Need Help - LLD-AL10 ........... Recovery Issue

I had installed LOS 8.1 on my phone with some chinese recovery few years back (may be 2018)......... working great.
Now i uninstalled Magisk ..............
Now I have Pretoria https://forum.xda-developers.com/t/...e-unofficial-twrp-3-2-1-0-12-05-2018.3789306/ installed .......... which is stuck on very first page.
i Want to reinstall MAgisk which needs TWRP
I have tried to flash new twrp in fastboot ........ but every time.......... error shows ............. command not allowed.
so guide me

kdark said:
command not allowed.
Click to expand...
Click to collapse
make sure you have both FRP and bootloader unlocked

-Alf- said:
make sure you have both FRP and bootloader unlocked
Click to expand...
Click to collapse
FRP is locked

how to revert to stock rom?

kdark said:
how to revert to stock rom?
Click to expand...
Click to collapse
A. Use eRecovery
B. Flash full stock FW using dload method

-Alf- said:
A. Use eRecovery
B. Flash full stock FW using dload method
Click to expand...
Click to collapse
i dont think erecovery is working bcoz twrp is flashed

kdark said:
twrp is flashed
Click to expand...
Click to collapse
How did you install it? Over Recovery or over eRecovery?

-Alf- said:
How did you install it? Over Recovery or over eRecovery?
Click to expand...
Click to collapse
dont remember coz it was in 2018........ but in erecovery ...... it only show reboot option

kdark said:
. it only show reboot option
Click to expand...
Click to collapse
I'm not sure I fully understand you... There is no Recovery or eRecovery which shows only one option.

-Alf- said:
I'm not sure I fully understand you... There is no Recovery or eRecovery which shows only one option.
Click to expand...
Click to collapse
if i boot to recovery from phone ........... it goes to TWRP {which is stuck} ........ otherwise erecovery shows only reboot option

-Alf- said:
I'm not sure I fully understand you... There is no Recovery or eRecovery which shows only one option.
Click to expand...
Click to collapse
give me fastboot commands to flash both twrp and erecovery

kdark said:
give me fastboot commands to flash both twrp and erecovery
Click to expand...
Click to collapse
maybe you meant to say "give me please"...
Google it.

-Alf- said:
maybe you meant to say "give me please"...
Google it.
Click to expand...
Click to collapse
plz

in fastboot mode run commands :
fastboot oem get-build-number
fastboot oem get-product-model
fastboot getvar vendorcountry
fastboot oem oeminforead-CUSTOM_VERSION
fastboot oem oeminforead-SYSTEM_VERSION
and post the results.
Some might fail, so don't worry about it.

-Alf- said:
in fastboot mode run commands :
fastboot oem get-build-number
fastboot oem get-product-model
fastboot getvar vendorcountry
fastboot oem oeminforead-CUSTOM_VERSION
fastboot oem oeminforead-SYSTEM_VERSION
and post the results.
Some might fail, so don't worry about it.
Click to expand...
Click to collapse
LLD-AL10 8.0.0.160(C675)
(bootloader) LLD-AL10
vendorcountry: hw/in
FAILED (remote: 'The reason of failed input oem_nv_item error!')
fastboot: error: Command failed
(bootloader) :LLD-AL10 8.0.0.160(C675CUSTC675D2)

FRP still locked?
Try to perform factory reset in fastboot mode, run command
fastboot erase userdata
Then try reboot TWRP and flash this file:
https://mega.nz/file/Q1dzQAqK#VGEZOvTalbDWow8epmN6ht7XNc9VH-4rapKtqU_3Y3A
FRP status will change to Unlock.