Related
hello, im new in this forum.
i have a mi mix 2s and i wanted to unlock it. mi unlock tool said: device already unlocked..
so I started the flash tool with a global and I think i forgot to switch from "clean all and lock" to "clean all"
so the phone booted in the recovery and said "this version cant be installed on this device"
now I cant do anything...i tried with
- Xiaomi Tool (doesnt works because of usb debugging isnt enabled)
-xiaomi unlock tool says i have to sign in to my account on the device
-Xiomi flash tool (Erase boot error), i tried the official gloabl and china
-adb mode knows my device but no flashing
A friend says there is now software on it. but i dont know
I CAN go to fastboot and i can go to the recovery 3.0
PLS help me! Thank you so much
Try to flash twrp, do factory reset with encryption. Then flash rom with adb sideload
If you have the XE model (which is the Chinese model) and locked your bootloader after flashing the Global ROM your phone is bricked. The Chinese model can't boot up the Global ROM with a locked bootloader. If that's what you did I don't think there is a solution. You need to unlock the bootloader again but if the unlock tool doesn't work I don't know of another option with these phones.
jhs39 said:
If you have the XE model (which is the Chinese model) and locked your bootloader after flashing the Global ROM your phone is bricked. The Chinese model can't boot up the Global ROM with a locked bootloader. If that's what you did I don't think there is a solution. You need to unlock the bootloader again but if the unlock tool doesn't work I don't know of another option with these phones.
Click to expand...
Click to collapse
There was a case like this in the miui forum. The guy there contacted xiaomi support and with their help he could unlock the bootloader without signing in
@sidofido
Do I need usb Debugging for your method?
Usb Debugging does not works
@Flatric
Okay so I send an email to the Support.
Thank you very much, Im happy for every answer
sidofido said:
Try to flash twrp, do factory reset with encryption. Then flash rom with adb sideload
Click to expand...
Click to collapse
Bootloader is locked.
Gesendet von meinem MIX 2S mit Tapatalk
Flatric said:
There was a case like this in the miui forum. The guy there contacted xiaomi support and with their help he could unlock the bootloader without signing in
Click to expand...
Click to collapse
That's apparently true but there were also at least a half dozen people who contacted Xiaomi Support after reading that and reported that they received no help. They are currently trying to get the name of the specific support person who unlocked the bootloader.
That doesnt Sound good... Where can I get Support? I Used [email protected], is that the right way?
Xiaomi98 said:
That doesnt Sound good... Where can I get Support? I Used [email protected], is that the right way?
Click to expand...
Click to collapse
There are threads about this issue on the MIUI Forum. Someone else said today that Xiaomi Support bound his account to his device which allowed him to use the Unlock Tool. It seems to be very hit or miss in regards to getting somebody in support who understands the issue. You should really go to the Xiaomi Forum for the MI Mix 2S. Only Xiaomi can help you and you will get better information there regarding this issue.
I want to flash my Mix 2s from Android P back to Miui 9.5. I purchased the phone with P already installed, does anyone know how I can flash it successfully? I am new at this. my phone says unlocked underneath the xiaomi name when I turn it on so I think its unlocked bootloader? but its not rooted any help would be greatly appreciated
jhs39 said:
There are threads about this issue on the MIUI Forum. Someone else said today that Xiaomi Support bound his account to his device which allowed him to use the Unlock Tool. It seems to be very hit or miss in regards to getting somebody in support who understands the issue. You should really go to the Xiaomi Forum for the MI Mix 2S. Only Xiaomi can help you and you will get better information there regarding this issue.
Click to expand...
Click to collapse
You might be able to fix your issue by flashing the ROM using the MI PC Suite Beta program. That program allows you to flash a ROM when the bootloader is locked but I don't know much about it. Someone in a similar situation as you claimed he got his phone running again using that program.
http://en.miui.com/thread-2943351-1-1.html
---------- Post added at 10:55 PM ---------- Previous post was at 10:42 PM ----------
liquiem said:
I want to flash my Mix 2s from Android P back to Miui 9.5. I purchased the phone with P already installed, does anyone know how I can flash it successfully? I am new at this. my phone says unlocked underneath the xiaomi name when I turn it on so I think its unlocked bootloader? but its not rooted any help would be greatly appreciated
Click to expand...
Click to collapse
Using the MI Flash Tool on your computer is probably the easiest way. Download the latest stable ROM if you want to go back to MIUI 9.5. You need the MI Flash version that ends in extension tgz--not the fastboot version which is a zip file. Uncompress the tgz file, put your phone in fastboot mode and connect it to your computer, open the MI Flash Tool on your computer with administrative access. It should detect your phone. If it doesn't I think there is a refresh button. After your phone is detected point the program to the location of the uncompressed ROM folder. Before you flash look at the options at the very bottom. The default will relock your bootloader so you might want to change that. When you hit flash the tool does everything automatically and returns your phone to stock MIUI.
So..... Miui Support says I have to go to the seller....
The guy in miui forum who solved said, he just tried the latest unlock tool and it works.
I Tried lots of Tools, the latest too and it doesnt Work.
So my Phone is destroyed now?
Xiaomi98 said:
So..... Miui Support says I have to go to the seller....
The guy in miui forum who solved said, he just tried the latest unlock tool and it works.
I Tried lots of Tools, the latest too and it doesnt Work.
So my Phone is destroyed now?
Click to expand...
Click to collapse
Maybe contact them again and hope for a different support person...
Xiaomi98 said:
So..... Miui Support says I have to go to the seller....
The guy in miui forum who solved said, he just tried the latest unlock tool and it works.
I Tried lots of Tools, the latest too and it doesnt Work.
So my Phone is destroyed now?
Click to expand...
Click to collapse
hi, any success?
Hello I formated the flash of my redmi 6 using sp flash tool and now my bootloader is locked sadly when I tried to unlock it my sim is not working due to no imei soo does anyone know how to fix this issue. Soo does anyone have a way to repair the imei.
i still cant do it
Nobody knows how to fix
IMEI REPAIR REDMI 6 LOCKED BOOTLOADER
Soo I recently Had a problem explained here https://forum.xda-developers.com/t/help-i-formated-the-flash-by-mistake-using-spflash-tool-and-now-my-bootloader-is-locked-and-i-have-no-imei.4271955/ And I found a fix Requirements-- 1) Mtk-SU Easy...
forum.xda-developers.com
THIS IS THE FIX FOR THIS ISSUE
DO NOT LOCK THE BOOTLOADER WHILE ROOTED!
When locking the bootloader while rooted, the boot image will fail verification and the system will fail to boot. You cannot flash a stock boot image with a locked bootloader.
Locking the bootloader will not fix most issues. It will allow you to use apps that check for an unlocked bootloader without the need for any additional modification. That is the ONLY benefit.
If you still want to lock your bootloader, make sure you can say yes to each of the following:
1. Have you restored the stock boot.img / vendor_boot.img and the phone functions normally?
Spoiler: Restore Stock Boot
Boot / DTBO Images [Root / Stock] - 5 / Pro / Ultimate (NOT S)
These images are NOT built from source. These are the stock images from the firmware provided by Asus that are extracted with payload dumper and uploaded without modification. 18.0840.2202.231 18.0840.2201.226 18.0840.2112.211...
forum.xda-developers.com
Follow the instructions in the thread above.
Use only the boot and vendor_boot images.
Do NOT flash any images that end with "-magisk.img"
2. Have you made a backup of everything you do not want to lose when wiping the phone?
Spoiler: Make a Backup
The sdcard is part of the internal storage and is cleared by a factory reset
Copy everything you want to keep to a computer or USB-C storage device
Apps and settings can be backed up by enabling the Google Backup option
Open Settings
Select Google
Select Backup
Select Back up now
Wait for the backup to complete
3. Have you flashed raw firmware and made sure the phone and updates function normally?
Spoiler: Flash Raw Firmware
RAW Firmware Collection and Guide
All fastboot / adb commands require using the side USB-C port https://developer.android.com/studio/releases/platform-tools.html#download Make sure you have fastboot installed Add platform tools to PATH (post 2) Make a backup of anything...
forum.xda-developers.com
Follow the instructions in the thread above.
If you perform a wipe, you may skip step 4.
4. Have you performed a factory reset and made sure the phone functions normally?
Spoiler: Factory Reset
Open Settings
Select System
Select Reset options
Select Erase all data (factory reset)
Follow the instructions
Once you have verified all of the above requirements, you are now ready to lock the bootloader.
Spoiler: Lock Bootloader
From the bootloader (volume up + power):
Code:
fastboot oem asus-csc_lk
Reserved for QA information
I don't want to spread false information here, but here is a question post I created recently with two replies showing me contacting the help center (two different agents) confirming that I can use the app more than once to unlock the device's bootloader: https://forum.xda-developers.com/t/...nlock-relock-for-asus-rog-phone-5-5s.4367047/ . @Andrologic also confirms the case there for global (EU) version. I have a feeling that for the Tencent version it is because the sellers lock it on a wrong official ROM, or wrong ROM in general, e.g. global ROM, and therefore it confuses the unlock app. I am surprised the device did not even get hard bricked from locking on not the original ROM. By the way, I have contacted the help center of the US store, but I have a feeling it should work on the global (EU) version as well.
falhumai96 said:
I don't want to spread false information here, but here is a question post I created recently with two replies showing me contacting the help center (two different agents) confirming that I can use the app more than once to unlock the device's bootloader: https://forum.xda-developers.com/t/...nlock-relock-for-asus-rog-phone-5-5s.4367047/ . @Andrologic also confirms the case there for global (EU) version. I have a feeling that for the Tencent version it is because the sellers lock it on a wrong official ROM, or wrong ROM in general, e.g. global ROM, and therefore it confuses the unlock app. I am surprised the device did not even get hard bricked from locking on not the original ROM. By the way, I have contacted the help center of the US store, but I have a feeling it should work on the global (EU) version as well.
Click to expand...
Click to collapse
Based on new information, it does seem possible to repair the issues caused by converting.
That said, this guide is still quite relevant. After all, most of the issues people were having were caused by unlocking the bootloader, converting, rooting, and locking the bootloader. The warning for possibility of not being able to unlock have been removed, but the info about restoring to stock before locking has been left.
I send mine in for a motherboard repair I was rooted and everything I unrooted installed stock firmware and locked the bootloader again once I got the phone back I unlocked the bootloader once again and I am rooted again
chairman011 said:
I send mine in for a motherboard repair I was rooted and everything I unrooted installed stock firmware and locked the bootloader again once I got the phone back I unlocked the bootloader once again and I am rooted again
Click to expand...
Click to collapse
@chairman011 what variant of the phone it is (e.g. CN or WW or US, ...etc.)? Also, when they returned it to you and you were able to unlock it again, was it on the original firmware (or any version in its lineage (i.e. not a ROM that's not original))?
If by using ASUS unlock utility one was able to oneself unlock the boot-loader once, then is it safe to say that (after relocking it) it'd be possible to unlock it again?
nexusnerdgeek said:
If by using ASUS unlock utility one was able to oneself unlock the boot-loader once, then is it safe to say that (after relocking it) it'd be possible to unlock it again?
Click to expand...
Click to collapse
Some people have reported that you can't unlock the bootloader again after relocking, using the official "Unlock Device App", but I suspect it is an OS mismatch. This issue has only been observed on Tencent (CN) version with global ROM. Have anyone been able to unlock->relock->unlock on the same version of the phone, but not relocking while on the global ROM (i.e. relocking while on stock CN ROM)?
I am surprised the phone did not hard brick. Usually, and this is a general case in almost all Android phones with bootloader unlock capability, when you relock on a different ROM your phone hard bricks. Always restore to original ROM before relocking. Can people with Tencent (CN) phones with global ROM and locked bootloader flash the original CN ROM without unlocking the bootloader? If so, can you test the "Unlock Device App" to see if it works while on the CN (official) ROM? I gotta a feeling it might work in that situation.
falhumai96 said:
Some people have reported that you can't unlock the bootloader again after relocking, using the official "Unlock Device App", but I suspect it is an OS mismatch. This issue has only been observed on Tencent (CN) version with global ROM. Have anyone been able to unlock->relock->unlock on the same version of the phone, but not relocking while on the global ROM (i.e. relocking while on stock CN ROM)?
I am surprised the phone did not hard brick. Usually, and this is a general case in almost all Android phones with bootloader unlock capability, when you relock on a different ROM your phone hard bricks. Always restore to original ROM before relocking. Can people with Tencent (CN) phones with global ROM and locked bootloader flash the original CN ROM without unlocking the bootloader? If so, can you test the "Unlock Device App" to see if it works while on the CN (official) ROM? I gotta a feeling it might work in that situation.
Click to expand...
Click to collapse
It's an identification mismatch. It's similar to when you throw your SIM card in a different phone and your carrier lists you as having a different phone. Based on the information that has been discovered, it would appear that CN to WW conversions were wiping out the stuff that makes your device your device.
twistedumbrella said:
It's an identification mismatch. It's similar to when you throw your SIM card in a different phone and your carrier lists you as having a different phone. Based on the information that has been discovered, it would appear that CN to WW conversions were wiping out the stuff that makes your device your device.
Click to expand...
Click to collapse
So, basically the bootloader unlock for tencent devices will always locked unless asus uodate their unlock app or has their been another way around it yet?
The unlock app should unlock the bootloader at least once. Unlocking it a second time has mixed results.
Hi there, can you guys help me? I'm one of those unlucky ones who got my phone corrupted and won't boot anymore due to the boot loader. is there a way to fix this?? I've got an ROG phone 5s 16/512 on android12.
Hope you guys can help me! I know you guys have amazing brain cells than me when it comes to these things lol
Oh! and my rog is not the china version thanks
0v3rkill said:
Hi there, can you guys help me? I'm one of those unlucky ones who got my phone corrupted and won't boot anymore due to the boot loader. is there a way to fix this?? I've got an ROG phone 5s 16/512 on android12.
Hope you guys can help me! I know you guys have amazing brain cells than me when it comes to these things lol
Oh! and my rog is not the china version thanks
Click to expand...
Click to collapse
TYou should be able to RAW flash yourself out of it if a factory reset doesn't work. This does happen when re-locking the WW.
Andrologic said:
TYou should be able to RAW flash yourself out of it if a factory reset doesn't work. This does happen when re-locking the WW.
Click to expand...
Click to collapse
Hi there mate, thanks heaps for taking time.on my post. how do i do that? can you send me a link of the step by step guide? again thanks
0v3rkill said:
Hi there mate, thanks heaps for taking time.on my post. how do i do that? can you send me a link of the step by step guide? again thanks
Click to expand...
Click to collapse
Below post from the help guide (credits to the contributors) has links to RAW firmware packages. You just need any one of the WW packages. Download it and with your device in bootloader mode, run one of the .bat flash scripts that you'll find in the RAW package. The version doesn't matter, you can simply update to the latest firmware once you're back up.
RAW Firmware Collection and Guide
All fastboot / adb commands require using the side USB-C port https://developer.android.com/studio/releases/platform-tools.html#download Make sure you have fastboot installed Add platform tools to PATH (post 2) Make a backup of anything...
forum.xda-developers.com
Andrologic said:
Below post from the help guide (credits to the contributors) has links to RAW firmware packages. You just need any one of the WW packages. Download it and with your device in bootloader mode, run one of the .bat flash scripts that you'll find in the RAW package. The version doesn't matter, you can simply update to the latest firmware once you're back up.
RAW Firmware Collection and Guide
All fastboot / adb commands require using the side USB-C port https://developer.android.com/studio/releases/platform-tools.html#download Make sure you have fastboot installed Add platform tools to PATH (post 2) Make a backup of anything...
forum.xda-developers.com
Click to expand...
Click to collapse
Hi there, I did follow and did the raw setup it did got me through the boot loop. However, its stuck on the system start up updating screen and stays in 0%.
Darn i thought im already dead! i didn't even know how i fixed it hahahaha! but its working now successfully downgraded to android 11 because its the only firmware i found and managed to make it work again combination of alot of research in google and here xda. working 100% imei two of them, finger print and sn are all intact. thanks guys
For these few reasons I have to give up root & lock the boot-loader: 1. Financial apps stop working from time to time causing much grief; 2. I've used root functionality precisely for nothing for a year I've had it; 3. It was getting all too complicated to keep up with it all.
(The original intention for unlocking/rooting was to get some sort of unofficial VoLTE and VoWiFi for the mobile operator of my choice; however, it didn't help. Then a newer firmware implemented VoLTE and VoWiFi! So my impatience, admittedly couldn't be known at that point in time, backfired.)
I've nothing to preserve on the phone, due to having a Moto G 5G backup phone. I only had it working with adb & fastboot in my Linux laptop (up to date Fedora 36). I had no working Windows laptop then. But I do now. However, adb on Windows says the device is "unauthorised" (as expected); fastboot in it doesn't list the device. So I might be limited to my Linux laptop only. The phone was previously working on the last A11 WW firmware fine.
I've tried to follow the steps from the original post of this thread. First one worked with vendor_boot, dtbo & boot images (used only 18.0840.2202.231 versions of them). Second N/A. With third step, flash_raw_and_wipe_data.sh fails by core dumping.
Right now, the phone boots to fastbootd & not further. Any help is much appreciated.
(I think I'm inching towards fully bricking this phone. I'm not there yet, but getting closer . It'd be nice to get it working again without root & with locked boot loader. Any help is much appreciated.)
This is where I'm at while executing step 3 of the initial guide in this post:
When powered on, in the usual boot loader unlocked warning page, it prompts for power key to be pressed to continue.
(Here if power switch is not pressed within 30 odd seconds, phone powers down automatically.)
Once power key is pressed, it lands in boot loader. Selecting Start, it goes back to boot loader. I think this is called a boot loop.
While in boot loader, selecting "Recovery mode", it progresses to "Android Recovery". Here selecting "Enter fastboot" appears to take it furthest in the booting process of landing at "Android Fastboot".
(The version info showed in Fastboot -- 18.0840.2202.231-0 -- matches with the last A11 update I downloaded from Asus website & had it installed late March this year.)
I don't think it can boot any further at the state that it's in now.
I think this is where it needs a raw firmware to be flashed. This step keeps core-dumping in my Linux laptop when trying to use WW_ZS673KS_18.0840.2106.83_M3.13.24.40-ASUS_1.1.92_Phone-user.raw file that was linked in the original post. This version appears to be quite old. Could the version mismatch between what the phone was running recently (18.0840.2202.231) and the raw file (18.0840.2106.83) cause the core-dump issue? IOW, would somebody have a link for 18.0840.2202.231 raw file please?
I couldn't use my work Windows laptop due to an issue I cannot overcome (installation of driver needed for the phone is somehow blocked in it). So, soon I'll try it from a personal Windows laptop of my neighbor. Let's see if it can progress any further with the help of Windows platform.
In the meantime, I can appreciate to be informed about any tips and tricks such as if this is something that the phone cannot be recovered from. Or even somebody highly skilled would like to help me to achieve a fully functional phone (with bootloader locked please) for a fair compensation. Please let me know. Thanks for any guidance.
nexusnerdgeek said:
This is where I'm at while executing step 3 of the initial guide in this post:
When powered on, in the usual boot loader unlocked warning page, it prompts for power key to be pressed to continue.
(Here if power switch is not pressed within 30 odd seconds, phone powers down automatically.)
Once power key is pressed, it lands in boot loader. Selecting Start, it goes back to boot loader. I think this is called a boot loop.
While in boot loader, selecting "Recovery mode", it progresses to "Android Recovery". Here selecting "Enter fastboot" appears to take it furthest in the booting process of landing at "Android Fastboot".
(The version info showed in Fastboot -- 18.0840.2202.231-0 -- matches with the last A11 update I downloaded from Asus website & had it installed late March this year.)
I don't think it can boot any further at the state that it's in now.
I think this is where it needs a raw firmware to be flashed. This step keeps core-dumping in my Linux laptop when trying to use WW_ZS673KS_18.0840.2106.83_M3.13.24.40-ASUS_1.1.92_Phone-user.raw file that was linked in the original post. This version appears to be quite old. Could the version mismatch between what the phone was running recently (18.0840.2202.231) and the raw file (18.0840.2106.83) cause the core-dump issue? IOW, would somebody have a link for 18.0840.2202.231 raw file please?
I couldn't use my work Windows laptop due to an issue I cannot overcome (installation of driver needed for the phone is somehow blocked in it). So, soon I'll try it from a personal Windows laptop of my neighbor. Let's see if it can progress any further with the help of Windows platform.
In the meantime, I can appreciate to be informed about any tips and tricks such as if this is something that the phone cannot be recovered from. Or even somebody highly skilled would like to help me to achieve a fully functional phone (with bootloader locked please) for a fair compensation. Please let me know. Thanks for any guidance.
Click to expand...
Click to collapse
Confirm that you can send fastboot commands to the device. It's a prerequisite for flashing the original boot img back or doing a RAW flash if boot looped. That's the very first step you need sorted and confirmed. Sounds like you may not be in the right Fastboot mode. The RAW version doesn't matter too much as long as it's in line with your device version, you just need it to get back up and can upgrade normally to other versions.
Hi,
I have unlocked my rog 5s using official app.
I did some playing with roms and installed official firmware by flashing RAW firmware.
I have locked the device using below command.
fastboot oem asus-lock
Now that my phone is in unlocked Rog phone list, I am not getting any updates nor Asus Unlock app is working.
I want to unlock my phone again and install some GSI roms as I officially don't get any updates from ASUS.
Any help is appreciated........
Maybe by changing the device rom and fingerprint back to Chinese version and hoping that the unlock tool will pick it up as a good match - Guess being that your phone is a CH>WW convert and not an original Global/WW version from factory.
Re-locking converted devices is a bad idea. It's posted and warned about so many times in this forum by other CN device owners...
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.