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?
Related
Think I may be officially bricked ... tried to sideload the OTA this morning with no luck (looped at Google splash screen). So I flashed the 5.0.1 images and went about my day. Came home and flashed the 5.1 images and looped at the Google splash again ... continued to tinker and play. Long story short, in my idiocy I oem locked. Now I can't flash any .img files cause I am locked, can't unlock because I can't boot into Android and uncheck the stupid box in dev options and trying to sideload the ota .zip again yields: "/dev/block/platform/msm_sdcc.1/by-name/system has been removed R/W; reflash device to reenable OTA updates E:Error in sideload/package.zip (Status 7)" ...
At this point I think I am screwed!! Any suggestions would be GREATLY appreciated!
Can you not get into fastboot and try to OEM unlock that way?
Xaikar said:
Can you not get into fastboot and try to OEM unlock that way?
Click to expand...
Click to collapse
I can get into fastboot but get this when I try to unlock
C:\Android\sdk\platform-tools>fastboot oem unlock
...
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
finished. total time: 0.000s
C:\Android\sdk\platform-tools>
And of course I cannot check that because I cannot boot into Android
So it currently says device locked?
Xaikar said:
So it currently says device locked?
Click to expand...
Click to collapse
10-4
I can get into stock recovery, but I don't know of anything to flash with the stock recovery and adb sideloading 5.1 isn't working
http://androidforums.com/threads/guide-how-to-flash-a-nexus-factory-image-manually.706533/
There's a thread about this over at the Nexus 9 help forum. Might want to check there.
Xaikar said:
http://androidforums.com/threads/guide-how-to-flash-a-nexus-factory-image-manually.706533/
Click to expand...
Click to collapse
Can't flash the images while locked, thanks though
ChristianJay said:
There's a thread about this over at the Nexus 9 help forum. Might want to check there.
Click to expand...
Click to collapse
Ah, thanks! Any idea which section?
Edit: Found it!
YankInDaSouth said:
Ah, thanks! Any idea which section?
Click to expand...
Click to collapse
http://forum.xda-developers.com/nexus-9/help/warning-locking-bootloader-disabling-t2951312
Have you tried booting TWRP from fastboot? Maybe then you could install a ROM to boot into android.
fastboot boot recovery recovery.img
WugFresh Nexus Root Toolkit
Try the "Flash Stock + Unroot" option. It should take you back to square 1.
ajjames01 said:
Have you tried booting TWRP from fastboot? Maybe then you could install a ROM to boot into android.
fastboot boot recovery recovery.img
Click to expand...
Click to collapse
Custom recovery isn't currently on the device ...
Dusty Rhodes said:
WugFresh Nexus Root Toolkit
Try the "Flash Stock + Unroot" option. It should take you back to square 1.
Click to expand...
Click to collapse
Tried that too ... but the .img's cannot be flashed while locked, keeps failing
If you have TWRP on the device can you adb push a ROM to it and flash it so you can boot android and tick the "enable OEM unlock" box.
ajjames01 said:
If you have TWRP on the device can you a ROM to it and flash it so you can boot android and tick the "enable OEM unlock" box.
Click to expand...
Click to collapse
I don't have TWRP, sorry that was a typo. It's stock recovery as I was trying to go fully stock 5.1 ...
@YankInDaSouth
Did you try booting twrp and not flashing it and go from there?
Fastboot boot recovery twrp.img
when Google decided to add the "OEM Lock" checkbox they should have committed to every Nexus device also having SD card capability, not only for the convenience that SD cards bring but also to be able to load the images that way in the event of a catastrophe.
But I guess forcing everyone into buying cloud storage is the new modus operandi.
Try the following commands, one after the other:
fastboot format userdata
fastboot format cache
fastboot reboot-bootloader
fastboot oem unlock (if it works, great, if not, go to the next one below)
fastboot reboot
efrant said:
Try the following commands, one after the other:
fastboot format userdata
fastboot format cache
fastboot reboot-bootloader
fastboot oem unlock (if it works, great, if not, go to the next one below)
fastboot reboot
Click to expand...
Click to collapse
Still get the message about checking the box in dev options ...
Not sleeping tonight huh bro? I know the feeling when this **** happens, it sucks. I think someone will come up with a work around, a lot of brains around here.
Sent from my Nexus 9 using XDA Free mobile app
Hi guys
I want to install android 8 (emuı or custom rom) but the oreo twrp doesnt installing, ı tried every time and show an error, how to fix this thing?
kadirc5 said:
Hi guys
I want to install android 8 (emuı or custom rom) but the oreo twrp doesnt installing, ı tried every time and show an error, how to fix this thing?
Click to expand...
Click to collapse
You must give more info so that anyone can understand your problem. Which steps did you follow, which error is it...??? BTW better post it in its right thread (Oreo flashing guide)
CarlosAG10 said:
You must give more info so that anyone can understand your problem. Which steps did you follow, which error is it...??? BTW better post it in its right thread (Oreo flashing guide)
Click to expand...
Click to collapse
First part, is the twrp installation on the fastboot mode. I wrote this code > fastboot flash recovery_ramdisk recovery_ramdisk.img and pressed enter
Sending... Ok
Writing...
FAİLED
kadirc5 said:
First part, is the twrp installation on the fastboot mode. I wrote this code > fastboot flash recovery_ramdisk recovery_ramdisk.img and pressed enter
Sending... Ok
Writing...
FAİLED
Click to expand...
Click to collapse
Try sending command "fastboot devices". Does a number appear? In that case, check your recovery_ramdisk img and directory
CarlosAG10 said:
Try sending command "fastboot devices". Does a number appear? In that case, check your recovery_ramdisk img and directory
Click to expand...
Click to collapse
Yes, shows a number
How can ı check?
kadirc5 said:
Yes, shows a number
How can ı check?
Click to expand...
Click to collapse
Download the files again and make sure you are correctly using fastboot
since you rebranded the device, you should unlock the bootloader again. fastboot doesn't allow running command with a locked bootloader
fastboot oem unlock yourcodehere
Striike said:
since you rebranded the device, you should unlock the bootloader again. fastboot doesn't allow running command with a locked bootloader
fastboot oem unlock yourcodehere
Click to expand...
Click to collapse
Im gonna try at the weekend thanks
Hello,
Im trying to relock my bootloader again, did i just have to use the "fastboot oem lock" command? Because i read it somewhere that i have to flash stock rom before locking the bootloader, if yes can someone give me the link for stock rom and how to flash it, FYI when unlocking im only using "fastboot oem unlock' command, not doing "fastboot unlock critical blablabla".
Any help would be appreciated, thank you
as far as i know, you need to flash stock bootloader of your current android build then uninstall magisk (if you have it) and just use fastboot oem unlock and you're done (note! backup all your data cause it will make a full wipe)
DiesFrae said:
as far as i know, you need to flash stock bootloader of your current android build then uninstall magisk (if you have it) and just use fastboot oem unlock and you're done (note! backup all your data cause it will make a full wipe)
Click to expand...
Click to collapse
I stopped after unlock bootloader only, i didnt root it at all, so you mean after flash just run fastboot oem lock command?
prayogasp said:
I stopped after unlock bootloader only, i didnt root it at all, so you mean after flash just run fastboot oem lock command?
Click to expand...
Click to collapse
Then you don't need to flash anything at all. Just run fastboot oem lock command.
prayogasp said:
I stopped after unlock bootloader only, i didnt root it at all, so you mean after flash just run fastboot oem lock command?
Click to expand...
Click to collapse
[email protected] said:
Then you don't need to flash anything at all. Just run fastboot oem lock command.
Click to expand...
Click to collapse
Exactly, you don't need to flash anything. Just put phone into fastboot and run fastboot oem lock
[email protected] said:
Then you don't need to flash anything at all. Just run fastboot oem lock command.
Click to expand...
Click to collapse
DiesFrae said:
Exactly, you don't need to flash anything. Just put phone into fastboot and run fastboot oem lock
Click to expand...
Click to collapse
Will it wipe data again just like unlocking?
Yes. It will wipe your data. Please becareful.
Oh. Please sure that you have back to original boot image before relock or your device will brick.
Hi, can someone provide stock boot image for 10.0.1.0 build (Android 9.0)
av2032 said:
Hi, can someone provide stock boot image for 10.0.1.0 build (Android 9.0)
Click to expand...
Click to collapse
https://sourceforge.net/projects/xioami/files/Mi A2/
ckpv5 said:
https://sourceforge.net/projects/xioami/files/Mi A2/
Click to expand...
Click to collapse
Can I simply flash boot_a boot.img / boot_b boot.img and then do
fastboot oem lock?
av2032 said:
Can I simply flash boot_a boot.img / boot_b boot.img and then do
fastboot oem lock?
Click to expand...
Click to collapse
I never relock bootloader .. what I know is you must have fully stock ROM installed then only advisable to lock bootloader. Never do on rooted stock & custom ROM.
Maybe someone else can advise you better.
ckpv5 said:
I never relock bootloader .. what I know is you must have fully stock ROM installed then only advisable to lock bootloader. Never do on rooted stock & custom ROM.
Maybe someone else can advise you better.
Click to expand...
Click to collapse
I have fully stock ROM. Done it anyway... restoring from Google backup right now. Thanks.
Can anyone provide stock boot img for 10.0.3
---------- Post added at 04:55 AM ---------- Previous post was at 04:10 AM ----------
Can I use 10.0.2 boot image for 10.0.3
av2032 said:
I have fully stock ROM. Done it anyway... restoring from Google backup right now. Thanks.
Click to expand...
Click to collapse
Did you lose data after relocking? I mean lock bootloader causes a data wipe like unlocking?
prayogasp said:
Hello,
Im trying to relock my bootloader again, did i just have to use the "fastboot oem lock" command? Because i read it somewhere that i have to flash stock rom before locking the bootloader, if yes can someone give me the link for stock rom and how to flash it, FYI when unlocking im only using "fastboot oem unlock' command, not doing "fastboot unlock critical blablabla".
Any help would be appreciated, thank you
Click to expand...
Click to collapse
here is the link for fastboot rom
https://forum.xda-developers.com/mi-a2/how-to/fastboot-xiaomi-mi-a2-fastboot-images-t3824849
for your sugestion, if your device is arb2, flash 9690 fastboot rom.
saran, jika masih arb2, flash ke rom 9690..ane pas pertama beli mia2, dapet rom 9690 arb 2..
alibr said:
Did you lose data after relocking? I mean lock bootloader causes a data wipe like unlocking?
Click to expand...
Click to collapse
Yes... it erases everything
Lock while using miui
Can I relock my bootloader while using official MIUI rom?
Aside from
Fastboot oem lock
Do i need this?
fastboot flashing lock
fastboot flashing lock_critical
amnher said:
Aside from Fastboot oem lock
Do i need this?
fastboot flashing lock
fastboot flashing lock_critical
Click to expand...
Click to collapse
"Fastboot oem lock" seems to be depreciated for Mi A2, better use "fastboot flashing lock" instead of "OEM unlock" (though probably these are still equivalent).
And yes, full unlock is achieved when after general unlock you are unlocking critical (once more approve on phone, once more user data erased).
For your information. I've just bricked my Redmi 10S with stock ROM with the command ""Fastboot oem lock" :-(
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
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.