I cannot relock asus zenfone5 lite (zc600kl)
At asus homepage, i download app "version unlock tool"
And i install, I ran a program
Then the following message will pop up each the phone booting.
Your device softeare csn't be checked for corruption.
Please lock the bootloader.
So i wish relock my phone, asus zenfone5 lite (zc600kl)
Please let mo know How to relock asus zenfone5 lite (zc600kl)
Thank you. have a nice day.
You unlock bootloader with the official apk, so you cannot relock it, and moreover, like it's explain when you install the official apk for unlocking bootloader, your warranty is now void. I remember it was written when i unlocked bootloader on my zenfone 3 with the official asus apk.
siberflyers said:
You unlock bootloader with the official apk, so you cannot relock it, and moreover, like it's explain when you install the official apk for unlocking bootloader, your warranty is now void. I remember it was written when i unlocked bootloader on my zenfone 3 with the official asus apk.
Click to expand...
Click to collapse
Thank you for your reply.
I want to relock my zenfone.
When I boot up the phone, I get the same sentence.
It is not related to the warranty of the phone.
This is Korea, not the place where the asus phone is regularly distributed, but it does not repair the trouble in Korea asus.
Knowing this, I bought the phone.
I just want to keep that sentence no more when the phone boot.
When relocking again, the sentence seems to be rattling and asking questions.
I want to know how to relock.
I am also looking for an original recovry and boot img that fits this phone.
If I can save those files, I think relock is possible.
Or I would like to find a way in this phone that this phrase can be paved.
Thank you.
I will read your writing carefully.
purundl said:
Thank you for your reply.
I want to relock my zenfone.
When I boot up the phone, I get the same sentence.
It is not related to the warranty of the phone.
This is Korea, not the place where the asus phone is regularly distributed, but it does not repair the trouble in Korea asus.
Knowing this, I bought the phone.
I just want to keep that sentence no more when the phone boot.
When relocking again, the sentence seems to be rattling and asking questions.
I want to know how to relock.
I am also looking for an original recovry and boot img that fits this phone.
If I can save those files, I think relock is possible.
Or I would like to find a way in this phone that this phrase can be paved.
Thank you.
I will read your writing carefully.
Click to expand...
Click to collapse
You can not get rid of the message, even if you relock the boot loader.
Help unlock bootloader zenfone 5q (x017da)
I don't have a high enough post count to start my own thread, but this is the closest related thread I could find. If I should post this somewhere else, please advise.
I tried the official unlock bootloader apk and I keep getting an error message. It says it is an unknown error message and it may be a network issue. I tried troubleshooting on the zentalk forum. They asked for my Imei number and then told me the servers are fine that I'd be using and I would need to have support perform "Imei checking". Support had no idea what that meant. The zentalk support person suggested I ask for help here as they can not provide any additional assistance.
I've looked and using adb and fastboot I can get my phone into fastboot, but then after echo>key.txt I try:
fastboot oem get_unlock_key key.txt
FAILED (remote: 'unknown command')
fastboot: error: Command failed
My goal with unlocking the bootloader is to try to enable gcam and hopefully improve the camera capabilities.
Does anyone have a suggestion on what steps to unlock the bootloader? I don't believe there is any way to use gcam without unlocking the bootloader first, but I'd there is a way to do that, I'd appreciate some direction.
Thanks.
Related
Hey everyone,
I got my new Honor 8 and as with my previous OnePlus One I just need root.
It's not that complicated to find descriptions how to unlock the bootloader (and loose the warranty), relock it and even get the "locked" status again without (https://forum.xda-developers.com/showpost.php?p=70177996&postcount=7) and with DC Unlocker (https://www.dc-unlocker.com/how-to-lock-bootloader-from-relocked-to-locked) in case I understood everything right.
But the important qustion of course is if one (for example Huawei) can see that its relocked. So first, what does it say if you get the status over the command prompt? And even if it's "locked" there is there any other way you can see?
I don't expect a warranted answer but maybe someone who is firm with android coding or what ever can at least say what he thinks?
Thanks a lot!
If you relock it with a fastboot command then yeah. But if you use a rollback package to return to emui 4.1, everything gets wiped in a way that makes the bootloader status "locked"
Could please someone at least check the first question with his unlocked phone?
Edit: Didn't see your reply and don't now how to delete mine... Thanks anyway!
sysak said:
If you relock it with a fastboot command then yeah. But if you use a rollback package to return to emui 4.1, everything gets wiped in a way that makes the bootloader status "locked"
Click to expand...
Click to collapse
That means after unlocking bootloader and relock bootloader with these steps, i have back my warranty?
Sorry for my bad english..
Silencer3007 said:
That means after unlocking bootloader and relock bootloader with these steps, i have back my warranty?
Sorry for my bad english..
Click to expand...
Click to collapse
As far as i know yeah, unless there is some secret way for them to know it. If you unlock the bootloader with a code and then lock it again it will show the bootloader status as "relocked" in fastboot mode, indicating that the device was tampered with in the past. But the "locked" status you get in the rollback process is the same as on a phone that was never modified. I found this "trick" accidentally when restoring a bricked phone using the rollback package and think it's pretty handy.
sysak said:
As far as i know yeah, unless there is some secret way for them to know it. If you unlock the bootloader with a code and then lock it again it will show the bootloader status as "relocked" in fastboot mode, indicating that the device was tampered with in the past. But the "locked" status you get in the rollback process is the same as on a phone that was never modified. I found this "trick" accidentally when restoring a bricked phone using the rollback package and think it's pretty handy.
Click to expand...
Click to collapse
Not sure if u'll read this. When I was stuck in the same issue somewhere around July 2017 I was devastated and thought if I were to relock my bootloader how to do so without it saying relocked (If you do it by fastboot it will 100% say so). I tried the rollback method on seeing this and u sure r right. It says LOCKED and looks as though my phone was never tampered with ?.
I came across this thread researching abt something and though I'd thank you!
Sent from my Honor 8 using XDA Labs
Hello,
I messed with my Pixel phone and now I feel it bricked. It was working fine until I update it to 8.0 Oreo. Then I rooted it using magisk.
Later, I decided to re-lock my bootloader, which was really a big mistake. I did re-lock it using the following command:
fastboot oem lock
It showed me if I lock my bootloader, it would wipe everything. I hit yes.
After that, this issue started, my phone won't start, as soon as the google logo shows up, it restarts and does the same thing everytime.
I tried to install the factory image, "sailfish" for Pixel 8.1.0, using the following command:
flash-all
it gave me an error message. It said I need to unlock the bootloader.
Of course, I tried to unlock the bootloader using the following command:
fastboot flashing unlock
It also gave me an error message, it said:
FAILED (remote: oem unlock is not allowed)
I don't know what else should I do. I tried to find a solution for my problem, but there is no clear answer.
One of the common solution is to enable the USB debugging/OEM unlocking from the developer settings. But, again, I can't even turn on my phone and use it normally.
The only thing that I can access to is the bootloader screen.
There are several threads which state "hey don't try relocking your bootloader for any reason" for a reason. You CANNOT relock these phones with ANY custom firmware or modifications. Your phone is bricked. You can try talking to Google and they /may/ rma your phone but there is 0 guarantee especially given that you did something that is a known feature and is intended to brick the phone. Can't hurt to try though
KittyRgnarok said:
There are several threads which state "hey don't try relocking your bootloader for any reason" for a reason. You CANNOT relock these phones with ANY custom firmware or modifications. Your phone is bricked. You can try talking to Google and they /may/ rma your phone but there is 0 guarantee especially given that you did something that is a known feature and is intended to brick the phone. Can't hurt to try though
Click to expand...
Click to collapse
You are totally right. I'll contact them to RMA my phone.
hamooz92 said:
You are totally right. I contact them to RMA my phone.
Click to expand...
Click to collapse
Good luck. Update the thread with the results cuz I'm curious if they will rma a phone bricked like that
So today i decided to downgrade from V10.2.1.0.PEEMIXM to V10.0.11.0.PEEMIFH because i was having serious battery issues on V10.2.1.0.
I should have looked into it more carefully but nope, my dumb ass decided to install the older ROM version via the Updater in Settings and it bricked my device in the process.
Now my device is stuck on boot with the message "The system has been destroyed. Press power button to shutdown".
I have the global version with the bootloader locked. The only thing i have access to now is fastboot.
Any ways i can recover from this? Any help is greatlyyy appreciated.
You can try to unlock bootloader with fastboot mode, but i'm not sure that works because the system has been destroyed and your account has been destryed too. I think, the best for you, is to send it in warranty for repair. I have bricked a Redmi Note 4 like that and even with the test point method, he has never work again.
boxof said:
So today i decided to downgrade from V10.2.1.0.PEEMIXM to V10.0.11.0.PEEMIFH because i was having serious battery issues on V10.2.1.0.
I should have looked into it more carefully but nope, my dumb ass decided to install the older ROM version via the Updater in Settings and it bricked my device in the process.
Now my device is stuck on boot with the message "The system has been destroyed. Press power button to shutdown".
I have the global version with the bootloader locked. The only thing i have access to now is fastboot.
Any ways i can recover from this? Any help is greatlyyy appreciated.
Click to expand...
Click to collapse
If you can find the fastboot version of the ROM you were on before downgrading just flash it with miflash
Azev said:
You can try to unlock bootloader with fastboot mode, but i'm not sure that works because the system has been destroyed and your account has been destryed too. I think, the best for you, is to send it in warranty for repair. I have bricked a Redmi Note 4 like that and even with the test point method, he has never work again.
Click to expand...
Click to collapse
Fortunately for me i was able to unlock the bootloader. Likely because i registered my device since i first got it (about 1 month now), so i think i must have met the wait time requirement and it was fine that i couldn't access the system.
Mackay53 said:
If you can find the fastboot version of the ROM you were on before downgrading just flash it with miflash
Click to expand...
Click to collapse
I tried miflash the first time with my bootloader still locked but miflash refused to work with a locked bootloader.
So i tried again with my bootlocker unlocked and it worked as expected.
Lesson learnt. All is well again and i'm able to keep my bootloader locked with the "flash_all_lock" option.
Thank you so much for all the help!
boxof said:
Fortunately for me i was able to unlock the bootloader. Likely because i registered my device since i first got it (about 1 month now), so i think i must have met the wait time requirement and it was fine that i couldn't access the system.
I tried miflash the first time with my bootloader still locked but miflash refused to work with a locked bootloader.
So i tried again with my bootlocker unlocked and it worked as expected.
Lesson learnt. All is well again and i'm able to keep my bootloader locked with the "flash_all_lock" option.
Thank you so much for all the help!
Click to expand...
Click to collapse
I am very sorry for reviving this thread, but if it's possible, can I ask you how you had managed to unlock the bootloader through fastboot? Now I am facing a similar situation to the one you once did, where my phone is stuck with the error message "The system has been destroyed" with a locked bootloader, and the only thing I have access to is Fastboot. I will greatly appreciate it if you could take some time to help me out because I have tried looking everywhere on xda forums and yours seems like the only one that is very similar to what I am currently facing now. Thanks so much.
nsynsy said:
I am very sorry for reviving this thread, but if it's possible, can I ask you how you had managed to unlock the bootloader through fastboot? Now I am facing a similar situation to the one you once did, where my phone is stuck with the error message "The system has been destroyed" with a locked bootloader, and the only thing I have access to is Fastboot. I will greatly appreciate it if you could take some time to help me out because I have tried looking everywhere on xda forums and yours seems like the only one that is very similar to what I am currently facing now. Thanks so much.
Click to expand...
Click to collapse
Unless you have got unlock permission and linked phone to account you can't unlock.
Unlock like how you would normally - put the phone into fastboot, connect it to your PC, and run the mi unlock tool. For this to work, hopefully you have associated your device to a mi account and have met the unlock requirements ie. surpassed the waiting period. Otherwise you're out of luck as there is no other ways (that i know of) to register the device now as you can't get into the system.
As a last resort you can try opening up the back of the phone and flash new firmware using the test point if unlocking is not possible. I'm not sure how or where the testing point is located exactly, but it's a possible solution that i found while researching when my device was bricked. Good luck!
nsynsy said:
I am very sorry for reviving this thread, but if it's possible, can I ask you how you had managed to unlock the bootloader through fastboot? Now I am facing a similar situation to the one you once did, where my phone is stuck with the error message "The system has been destroyed" with a locked bootloader, and the only thing I have access to is Fastboot. I will greatly appreciate it if you could take some time to help me out because I have tried looking everywhere on xda forums and yours seems like the only one that is very similar to what I am currently facing now. Thanks so much.
Click to expand...
Click to collapse
u say u can only access to fastboot..
How about pressing volume up and power button? can u enter in stock mi recovery with mi assistant options?
Does anyone know the command to relock bootloader? I flashed the raw firmware but every command I tried to relock failed. I need to make a warranty claim but can't until the bootloader is relocked.
Commands I have tried but failed:
fastboot oem lock
fastboot oem asus-csc_lk ( taken from ROG Phone 2 forums)
Code:
fastboot oem asus-back
fastboot reboot (if it doesn't reboot on it's own)
Thank you! Worked perfectly. You rock!
aleksander002 said:
Code:
fastboot oem asus-back
fastboot reboot (if it doesn't reboot on it's own)
Click to expand...
Click to collapse
Nice to hear it
Just remember you won't get FOTAs anymore because Asus is blacklisting unlocked phone's IMEI.
I wonder if there's a way to fake-send the IMEI to Asus when doing the unlocking process.
I don't know how exactly the bootloader is being unlocked but something tells me the unlock code is generated with the use of IMEI/SN. Wrong phone IDs = wrong key, however this is only my speculation.
I did the above command and now it says the deivce is corrupt and can't be trusted and will not boot. No press start to continue message. Can you please help me or guide me to unbrick this phone? Thank you.
P.S. I guess following the guide-unbricking-zs630kl can help? Thank you.
Edit: Nevermind. Followed that guide and unbricked it myself.
cdudeman said:
Thank you! Worked perfectly. You rock!
Click to expand...
Click to collapse
Were you able to claim the warranty? Did you do the official(Download from ASUS site) or unofficial bootloader unlock?
amgreenhawk said:
I did the above command and now it says the deivce is corrupt and can't be trusted and will not boot. No press start to continue message. Can you please help me or guide me to unbrick this phone? Thank you.
P.S. I guess following the guide-unbricking-zs630kl can help? Thank you.
Edit: Nevermind. Followed that guide and unbricked it myself.
Click to expand...
Click to collapse
Did you do the official(Download from ASUS site) or unofficial bootloader unlock?
niwdle said:
Did you do the official(Download from ASUS site) or unofficial bootloader unlock?
Click to expand...
Click to collapse
I did it officially, downloaded from ASUS website for unlocking.
amgreenhawk said:
I did the above command and now it says the deivce is corrupt and can't be trusted and will not boot. No press start to continue message. Can you please help me or guide me to unbrick this phone? Thank you.
P.S. I guess following the guide-unbricking-zs630kl can help? Thank you.
Edit: Nevermind. Followed that guide and unbricked it myself.
Click to expand...
Click to collapse
After you unbricked the phone, was the bootloader re-locked? Also, were you able to successfully file a warranty claim or return the phone? tnx
titilate said:
After you unbricked the phone, was the bootloader re-locked? Also, were you able to successfully file a warranty claim or return the phone? tnx
Click to expand...
Click to collapse
He has bricked it while locking the bootloader, so yeah, it will be locked. Warranty will depend on where you live. If you'll have faulty motherboard, they'll probably replace it for free but technically this is mandatory action only in the EU because just unlocking can't be considered as warranty void. Of course until they prove you that you bricked it.
I executed some commands, but root did not succeed
fastboot flash boot /path/to/magisk_patched_[random_strings].img
fastboot flash vbmeta --disable-verity --disable-verification vbmeta.img
I also couldn't achieve root.
I submitted a bug report on github.
IIRC patching init_boot.img is required for A13 devices (not boot.img as it was previously)
Did not succeed
and yes, I tried twice unlocking with the Asus unlock app
ACiDC0re said:
Did not succeed
and yes, I tried twice unlocking with the Asus unlock app
Click to expand...
Click to collapse
It literally tells you that device is locked. Do you get "g.co/ABH" screen during powering on the device?
If so, try in fastbootd ("adb reboot fastboot" or "fastboot reboot fastboot")
That worked
fastboot mode did the trick
Thank you!
download firmware from Asus
unpack the payload with payload-dumper
copy init_boot.img to phone
patch init_boot.img in magisk
copy magisk_patched.img back to PC
reboot phone to fastboot mode (adb reboot fastboot)
flash patched img: fastboot.exe flash init_boot magisk_patched.img
profit!
ACiDC0re said:
That worked
fastboot mode did the trick
Thank you!
download firmware from Asus
unpack the payload with payload-dumper
copy init_boot.img to phone
patch init_boot.img in magisk
copy magisk_patched.img back to PC
reboot phone to fastboot mode (adb reboot fastboot)
flash patched img: fastboot.exe flash init_boot magisk_patched.img
profit!
Click to expand...
Click to collapse
Thank you very much.
aaa.bbb111222 said:
It literally tells you that device is locked. Do you get "g.co/ABH" screen during powering on the device?
If so, try in fastbootd ("adb reboot fastboot" or "fastboot reboot fastboot")
Click to expand...
Click to collapse
Thank you very much.
Hi !!
I'm having problems with unlocking the bootloader (tencent version)
with the latest software installed (WW-33.0820.0810.121)
using the Unlock Device App Asus provides on their website on the newest version (1.0.0.7)
giving me an error when I try to unlock the bootloader "Failed to unlock your device please try again later."
how did ya'll unlocked it??
Eran Sadgan said:
Hi !!
I'm having problems with unlocking the bootloader (tencent version)
with the latest software installed (WW-33.0820.0810.121)
using the Unlock Device App Asus provides on their website on the newest version (1.0.0.7)
giving me an error when I try to unlock the bootloader "Failed to unlock your device please try again later."
how did ya'll unlocked it??
Click to expand...
Click to collapse
FYI I believe the ASUS bootloader unlocking server is currently down / malfunctioning and haven't gotten a good answer from their technical support. I'm currently receiving the same error and here are some links to forums posts experiencing the same behavior.
https://forum.xda-developers.com/t/asus-unlock-app-not-working.4582229/
Asus Unlock Tool not working on Zenfone 9
Recently received an Asus Zenfone 9 and the Asus Unlock App is returning "Failed to unlock your device, please try again later.[24802]" when attempting to unlock the bootloader. While running logcat I also see the following HTTP output: 05-03 10:43:50.133 28231 943 I ViseLog ...
zentalk.asus.com
Official Unlock tool not working for Zenfone 7
After downloading official Unlock tool from ASUS Website amd attempting to unlock my ZenFone 7 device. I keep getting error: Failed to unlock your device. Please try again later [24802] Can admins clarify if it is temporary issue with unlock server or unlocking has been disabled permanently?
zentalk.asus.com
Lost fingerprint and entire screen lock, does anyone have a way to fix it?
jstys92 said:
FYI I believe the ASUS bootloader unlocking server is currently down / malfunctioning and haven't gotten a good answer from their technical support. I'm currently receiving the same error and here are some links to forums posts experiencing the same behavior.
https://forum.xda-developers.com/t/asus-unlock-app-not-working.4582229/
Asus Unlock Tool not working on Zenfone 9
Recently received an Asus Zenfone 9 and the Asus Unlock App is returning "Failed to unlock your device, please try again later.[24802]" when attempting to unlock the bootloader. While running logcat I also see the following HTTP output: 05-03 10:43:50.133 28231 943 I ViseLog ...
zentalk.asus.com
Official Unlock tool not working for Zenfone 7
After downloading official Unlock tool from ASUS Website amd attempting to unlock my ZenFone 7 device. I keep getting error: Failed to unlock your device. Please try again later [24802] Can admins clarify if it is temporary issue with unlock server or unlocking has been disabled permanently?
zentalk.asus.com
Click to expand...
Click to collapse
After doing some research I understand that on the Tencent Version of the phone the sellers unlock and relock Bootloader after changing from CC to WW so they mess up bootloader.
It seems that the only way of unlocking the bootloader is using EDL, which I'm scared to use b/c I don't want to brick my new Rog phone 7 -_-
Can someone with the global version verify that using the unlock tool Asus provides works on their device?
Eran Sadgan said:
After doing some research I understand that on the Tencent Version of the phone the sellers unlock and relock Bootloader after changing from CC to WW so they mess up bootloader.
It seems that the only way of unlocking the bootloader is using EDL, which I'm scared to use b/c I don't want to brick my new Rog phone 7 -_-
Can someone with the global version verify that using the unlock tool Asus provides works on their device?
Click to expand...
Click to collapse
I'm also hoping to get some confirmation because I'm experiencing issues with the Unlock Tool on the zenfone 9, not the ROG phone so I don't think the issue you mentioned above applies in that case. Maybe there's multiple variables but I believe the asus servers are down until someone says that the Unlock Tool is working for them.
jstys92 said:
I'm also hoping to get some confirmation because I'm experiencing issues with the Unlock Tool on the zenfone 9, not the ROG phone so I don't think the issue you mentioned above applies in that case. Maybe there's multiple variables but I believe the asus servers are down until someone says that the Unlock Tool is working for themmy
Click to expand...
Click to collapse
My previous phone was the Zenfone 9, and I unlocked it using the Asus unlock tool that is provided on their website and successfully rooted it.
Are there several editions to the Zenfone like the Rog or is there only a global version?
if there's only a global version that probably means their servers are down.
Eran Sadgan said:
My previous phone was the Zenfone 9, and I unlocked it using the Asus unlock tool that is provided on their website and successfully rooted it.
Are there several editions to the Zenfone like the Rog or is there only a global version?
if there's only a global version that probably means their servers are down.
Click to expand...
Click to collapse
I've previously had success on the zenfone 9 as well, its only as recent as this week that the bootloader unlock tool is not working. ASUS support has responded saying their servers "were down for maintenance and to try again" but nothing has been fixed up to this point. I'm not sure if it's broken for everyone currently and if they've purposefully disabled it or it's just malfunctioning.
jstys92 said:
I've previously had success on the zenfone 9 as well, its only as recent as this week that the bootloader unlock tool is not working. ASUS support has responded saying their servers "were down for maintenance and to try again" but nothing has been fixed up to this point. I'm not sure if it's broken for everyone currently and if they've purposefully disabled it or it's just malfunctioning.
Click to expand...
Click to collapse
Yep,
Hope that the bootloader can be unlocked on the tencent version once the servers are back up.
Certainly will work with the zenfone 9.
hi anyone need to root his rog phone 7 pleass send me on telegram @aborem89
Converted CN>WW devices will not pass validation on the ASUS servers because the device region fingerprint has been changed and doesn't match. Only known way short off trying through EDL methods is to do a full reverse to CN and try to unlock before converting to WW again. This has been the case with all the previous ROG devices (and probably Zen models too) that I know of...
Can anyone make a step by step video on how to change the rom from cn - ww(global) thank-you
20 days later,the Asus unlocking server is still down and Asus didnt answered or told us anything. Does anyone have any new updates from Asus,or someone that works at Asus,maybe you can answer us here. Im starting to get tired of keep trying every few hours to unlock it and get the same error over and over,I need root acces.