Related
Introduction
This is the bootloader unlock from ZTE. It was provided to me in private email by a ZTE engineer.
Warning
This package is for the USA version of the Axon 7 Mini (tulip) running 7.1.1 b14 firmware. If you are running any other device or firmware version, it may not work.
Note
After some testing, it appears that the Axon 7 Mini is not locked in any way. In other words, apparently neither this package nor tuliptool's unlock are required to flash custom ROMs. The only apparent advantage to flashing this is to get access to fastboot, which provides a way to flash a custom boot and recovery (among other things).
Flashing Instructions
Place axon_mini_unlock.zip on the root of your sdcard.
Reboot into recovery.
Select "Apply update from SD card".
Select axon_mini_unlock.zip.
Usage Instructions
After the package is flashed, you may boot into the bootloader:
adb reboot bootloader
Once in the bootloader, you will see an on-screen menu. Additionally, you may access the typical fastboot commands:
fastboot oem device-info
fastboot oem unlock
fastboot flash ...
... etc ...
Download
axon_mini_unlock.zip
md5: ea8f1a21c8a46b3045d00f17a37fe359
So, after this is done, I can flash TWRP through fastboot and tuliptool is no longer necessary, correct?
Yes, that is correct.
JoeGatto said:
So, after this is done, I can flash TWRP through fastboot and tuliptool is no longer necessary, correct?
Click to expand...
Click to collapse
This package is for the USA version of the Axon 7 Mini (tulip) running 7.1.1 b14 firmware. If you are running any other device or firmware version, it may not work.
Click to expand...
Click to collapse
Is this something your contact mentioned or something that you believe based on your experience?
Any harm in trying it on verdandi/other versions without any risk of bricking?
After some testing, it appears that the Axon 7 Mini is not locked in any way. In other words, apparently neither this package nor tuliptool are required to flash custom ROMs. The only apparent advantage to flashing this is to get access to fastboot.
Click to expand...
Click to collapse
Any way to confirm this is also the case with other versions as well?
Thanks TDM.... you're going to have a lot of Canadians asking about verdandi as it is quite cheap here at the moment. Better get those questions out of the way early. The source is released, same kernel version as the U.S. one with some small differences with drivers (from what I can see) and I am sure that if people know that custom roms are possible on that version (not bootloader locked forever) it would be appreciated.
trpn111 said:
Is this something your contact mentioned or something that you believe based on your experience?
Any harm in trying it on verdandi/other versions without any risk of bricking?
Any way to confirm this is also the case with other versions as well?
Thanks TDM.... you're going to have a lot of Canadians asking about verdandi as it is quite cheap here at the moment. Better get those questions out of the way early. The source is released, same kernel version as the U.S. one with some small differences with drivers (from what I can see) and I am sure that if people know that custom roms are possible on that version (not bootloader locked forever) it would be appreciated.
Click to expand...
Click to collapse
Yeah...verdandi is stuck on Marshmellow. But since it has different hardware it could brick if this is tried.
The ZTE engineer is USA based, he is not on the China development team (read: probably a support engineer). He said: "I attached the unlock update zip package, please try it. It is based on B14 build."
Sorry, that's all I have to go by for "official" information.
I do not want to be responsible for anyone bricking their device, so I cannot claim that this bootloader will work with anything other than a tulip device running 7.1.1 b14.
If you want to try and report back, I'm sure others will appreciate it. But I can't be responsible for the results.
trpn111 said:
Is this something your contact mentioned or something that you believe based on your experience?
Any harm in trying it on verdandi/other versions without any risk of bricking?
Any way to confirm this is also the case with other versions as well?
Thanks TDM.... you're going to have a lot of Canadians asking about verdandi as it is quite cheap here at the moment. Better get those questions out of the way early. The source is released, same kernel version as the U.S. one with some small differences with drivers (from what I can see) and I am sure that if people know that custom roms are possible on that version (not bootloader locked forever) it would be appreciated.
Click to expand...
Click to collapse
Oh, and here is some more information to help you decide...
The volume key combo to enter EDL is handled by aboot (bootloader, eg. the thing we are flashing). This means even if you aren't currently able to use the key combo, you should be able to use it with the new aboot here. And if you can get to EDL, you can never really brick the device.
The volume key combo is detected very early in the aboot code. Like, first thing after basic platform init. So even if this isn't compatible with your device, it's likely we could restore the old aboot (assuming you back it up first, of course).
I'm convinced that the tulip is not locked based on my investigation today. So I have no idea if this aboot is properly signed. If your device is locked and this aboot is not signed properly, the lower boot loader won't load it. I'm not quite sure if that kicks you into EDL or not.
Not sure if that makes the decision easier or harder...
How did you come to the conclusion that tulip is not locked to begin with? If we don't need tuliptool or this aboot, how can I check verdandi if the device is the same 'locked but not really locked' state?
I will have a read about backing up aboot and see what I come up with concerning getting into edl.
So here's the deal...
I initially assumed the bootloader was locked because... well... it's supposed to be. So I found the place in aboot code where it checks the lock flag in the devinfo partition. I used the firehose to write unlocked to that flag. Then I built TWRP, flashed it and it booted. So I assumed everything was working just as I expected.
Today, I flashed the aboot with fastboot support and ran "fastboot oem device-info". It said that my device was locked. So I went to look and, sure enough, my devinfo partition flag was still set. Hmm, that's odd.
So I wrote locked back to the flag. TWRP still booted. Now things are looking pretty suspicious.
But maybe the new aboot doesn't even support locking? So I flashed the original b14 version of aboot and TWRP still booted.
That's pretty hard evidence that aboot is ignoring the lock flag. I don't know what they did -- whether they just removed the code that reads the lock flag or introduced a bug or what.
This does not necessarily mean that the lower layers are unlocked. That is, the lower boot loader may still required a properly signed aboot. I don't know, and I'm not ready to brick my device trying to find out.
trpn111 said:
How did you come to the conclusion that tulip is not locked to begin with? If we don't need tuliptool or this aboot, how can I check verdandi if the device is the same 'locked but not really locked' state?
I will have a read about backing up aboot and see what I come up with concerning getting into edl.
Click to expand...
Click to collapse
Hmm... Looks like this package incompatible with ZTE/P852A11/tulip.
Got error while trying to flash it by stock recovery. Error message says that it is for A12 version of tulip.
Ah, yes, you have the euro model. See the "calling all mini owners" thread, posts #76 and #77.
maestromony said:
Hmm... Looks like this package incompatible with ZTE/P852A11/tulip.
Got error while trying to flash it by stock recovery. Error message says that it is for A12 version of tulip.
Click to expand...
Click to collapse
i get a message saying "cant update from sd card?"
yeshivabachur said:
i get a message saying "cant update from sd card?"
Click to expand...
Click to collapse
Make sure battery level is at least 30% before applying any update. It's a standard protection feature.
JoeGatto said:
Make sure battery level is at least 30% before applying any update. It's a standard protection feature.
Click to expand...
Click to collapse
My battery was 80%+ mine still said can't update from sdcard
Aries2010 said:
My battery was 80%+ mine still said can't update from sdcard
Click to expand...
Click to collapse
Try turning on the OEM unlock setting in developer settings.
JoeGatto said:
Try turning on the OEM unlock setting in developer settings.
Click to expand...
Click to collapse
Thank you so much that worked I appreciate the it . Now I have one more question I have been searching for a way to root stock rom but I can't find any instructions on it. Could you walk me through it or post a link for me if possible? I have the USA mini 7 with B14 firmware
Aries2010 said:
Thank you so much that worked I appreciate the it . Now I have one more question I have been searching for a way to root stock rom but I can't find any instructions on it. Could you walk me through it or post a link for me if possible? I have the USA mini 7 with B14 firmware
Click to expand...
Click to collapse
Rooting the stock ROM will require that you remove verity, so that the OS won't refuse to boot once you've made any changes to the system partition. You'll need to use tuliptool to flash a new boot image, which you can find in this section of the forum. Then, you could either install TWRP through fastboot or using tuliptool.
JoeGatto said:
Rooting the stock ROM will require that you remove verity, so that the OS won't refuse to boot once you've made any changes to the system partition. You'll need to use tuliptool to flash a new boot image, which you can find in this section of the forum. Then, you could either install TWRP through fastboot or using tuliptool.
Click to expand...
Click to collapse
Thank you sir I appreciate it I shall try it tomorrow.
here's a stupid question.... I have only dealt with Samsung devices so, I have trouble understanding any other kind of process that is not Samsung. If a new update comes out while my device is bootloader unlocked can i update it? or will it brick my device?
The "standard" (not Samsung) method of updating via OTA is to ship:
1. Full images of any firmware partitions (rpm, tz, aboot, etc.)
2. Full image of boot.
3. A delta (patch) to system.
Also note that custom recoveries generally do not work with vendor OTA's.
This means that if you wish to apply an OTA, you must first have stock recovery and a completely pristine, unmodified system partition. The rest doesn't matter.
yeshivabachur said:
here's a stupid question.... I have only dealt with Samsung devices so, I have trouble understanding any other kind of process that is not Samsung. If a new update comes out while my device is bootloader unlocked can i update it? or will it brick my device?
Click to expand...
Click to collapse
What does the manufacturer do to the phone to make it un-rootable?
This quote: "Strictly speaking, when we talk about a platform as open as the Android OS, it is almost impossible for a manufacturer to make an ‘un-rootable’ device."
would suggest that most likely the manufacturer is not making the phone un-rootable. So then that would leave the OS, but my 4.2.2 KitKat has and is rooted on other devices.
So who and what is at fault here? Seems to me that if it was software, that would be easy. Find an exploit and root. But if it was that easy then all phones/devices would be rootable.
That brings us back to hardware and the manufacturer.
RealRobD said:
What does the manufacturer do to the phone to make it un-rootable?
This quote: "Strictly speaking, when we talk about a platform as open as the Android OS, it is almost impossible for a manufacturer to make an ‘un-rootable’ device."
would suggest that most likely the manufacturer is not making the phone un-rootable. So then that would leave the OS, but my 4.2.2 KitKat has and is rooted on other devices.
So who and what is at fault here? Seems to me that if it was software, that would be easy. Find an exploit and root. But if it was that easy then all phones/devices would be rootable.
That brings us back to hardware and the manufacturer.
Click to expand...
Click to collapse
It is more a matter of the carriers trying their hardest to prevent us from being able to unlock/root the devices they offer and less a matter of the manufacturer trying to prevent it.. They do this for several reasons. But the main reasons are to prevent security breaches, to protect the information on their customer's devices, to prevent having to repair/replace devices that have been broken due to failed rooting/flashing/modifying attempts and to prevent us from using their devices on another carrier's network.
It is considered to be impossible to make devices that absolutely can't be rooted. They are all vulnerable in some manner, these vulnerabilities are called exploits, it's just a matter of finding the right exploit. When exploits are found, the manufacturer or carrier will patch the exploit and release an update for their devices to apply the patch.
The main thing they do to make devices unrootable is to use a locked bootloader, some even use specific hardware components to prevent unapproved software from booting.
It's a combination of things really, there is not necessarily one certain thing they do to keep us from rooting, because there are many different ways to unlock/root devices, they try their best to account for them all.
Sent from my SM-S767VL using Tapatalk
It is considered to be impossible to make devices that absolutely can't be rooted. They are all vulnerable in some manner, these vulnerabilities are called exploits, it's just a matter of finding the right exploit.
Click to expand...
Click to collapse
Can you direct me to the recommended newbie reading to get my learn on?
My Alcatel onetouch has stumped current one click methods, so it's time to learn and crack this puppy on my own.
RealRobD said:
Can you direct me to the recommended newbie reading to get my learn on?
My Alcatel onetouch has stumped current one click methods, so it's time to learn and crack this puppy on my own.
Click to expand...
Click to collapse
If all one click methods have failed, the only option left is to flash some kind of customized software or methods to modify parts of your boot and/or system partitions. Flashing custom software and modifying boot or system requires the device to have an unlocked bootloader.
This means that your first step is to determine whether or not your device has an unlocked bootloader. If it is unlocked, you can flash/modify the device, if it is locked, you can't flash/modify unless you find a method to unlock the bootloader, then you can flash/modify. Do some searches for methods to check your bootloader status.
If you find that the bootloader is unlocked, then you have a few choices:
1) if you can obtain a copy of your stock firmware then you can use the Magisk rooting method to modify the boot.img from your firmware to create a patched boot.img then flash that boot.img using the appropriate flash tool for your device brand.
2) if you can find a copy of TWRP custom recovery for your specific device model number you can flash the TWRP file using the appropriate flash tool for your device brand.
3) if there is no TWRP for your specific model number, you can build your own version of TWRP if the necessary resources are available for your specific model number.
4) if the necessary resources to build TWRP for your specific model number are not available, you can try finding a TWRP for a similar device with the same exact CPU that your device has and port that TWRP to be compatible with your own device.
Do your own searching and researching about each of these options, the more you read about them, the more you will understand.
Sent from my SM-S767VL using Tapatalk
Droidriven said:
If all one click methods have failed, the only option left is to flash some kind of customized software or methods to modify parts of your boot and/or system partitions. Flashing custom software and modifying boot or system requires the device to have an unlocked bootloader.
This means that your first step is to determine whether or not your device has an unlocked bootloader. If it is unlocked, you can flash/modify the device, if it is locked, you can't flash/modify unless you find a method to unlock the bootloader, then you can flash/modify. Do some searches for methods to check your bootloader status.
If you find that the bootloader is unlocked, then you have a few choices:
1) if you can obtain a copy of your stock firmware then you can use the Magisk rooting method to modify the boot.img from your firmware to create a patched boot.img then flash that boot.img using the appropriate flash tool for your device brand.
2) if you can find a copy of TWRP custom recovery for your specific device model number you can flash the TWRP file using the appropriate flash tool for your device brand.
3) if there is no TWRP for your specific model number, you can build your own version of TWRP if the necessary resources are available for your specific model number.
4) if the necessary resources to build TWRP for your specific model number are not available, you can try finding a TWRP for a similar device with the same exact CPU that your device has and port that TWRP to be compatible with your own device.
Do your own searching and researching about each of these options, the more you read about them, the more you will understand.
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
Can't get past "Waiting on devices" when using
Code:
fastboot oem device-info
.
Device manager shows the phone is connected just fine.
The phone has no manual way to set fast boot, whether it be the buttons or entering numbers on the keypad.
Device recognized.
Code:
fastboot devices
returns nothing. I guess that means it's not in fast boot mode.
Code:
adb reboot bootloader
and
Code:
adb reboot fastboot
only reboots the phone.
On the other hand,
Code:
adb reboot recovery
does work.
RealRobD said:
Can't get past "Waiting on devices" when using
Code:
fastboot oem device-info
.
Device manager shows the phone is connected just fine.
The phone has no manual way to set fast boot, whether it be the buttons or entering numbers on the keypad.
Device recognized.
Code:
fastboot devices
returns nothing. I guess that means it's not in fast boot mode.
Code:
adb reboot bootloader
and
Code:
adb reboot fastboot
only reboots the phone.
On the other hand,
Code:
adb reboot recovery
does work.
Click to expand...
Click to collapse
Your device probably doesn't even have fastboot mode, some carriers remove fastboot from their devices, especially MVNO(subcontracted) networks.
Sent from my SM-S767VL using Tapatalk
Yep, looks like no Fastboot onboard...
galaxys said:
Yep, looks like no Fastboot onboard...
Click to expand...
Click to collapse
If it's just software, why can't it be bypassed, cracked, hacked, blown up etc?
RealRobD said:
If it's just software, why can't it be bypassed, cracked, hacked, blown up etc?
Click to expand...
Click to collapse
If you're asking about what was said about not having fastboot, it is a lack of software, as in, the software is not even there.
If you're asking if the software can be bypassed, it can, the trick is to find the right exploit. That is the problem, a working exploit has not been discovered for this device.
Without fastboot, there is no way to flash custom files such as TWRP or patched boot.img. This means, the only chance of rooting the device is if one of the one-click universal rooting apps or universal PC rooting programs has an exploit that just happens to network on this device.
Sent from my SM-S767VL using Tapatalk
Droidriven said:
If you're asking about what was said about not having fastboot, it is a lack of software, as in, the software is not even there.
If you're asking if the software can be bypassed, it can, the trick is to find the right exploit. That is the problem, a working exploit has not been discovered for this device.
Without fastboot, there is no way to flash custom files such as TWRP or patched boot.img. This means, the only chance of rooting the device is if one of the one-click universal rooting apps or universal PC rooting programs has an exploit that just happens to network on this device.
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
Have any fastboot-less phones in the past been rooted?
If so, do you have any recommended reading as far as exploit hunting is concerned?
Hi community
First Thanks to the people who take time to help, and admin that create that forum. Im always glad to see that s there is still people caring about helping each other
I come to you cause I spent the last 2 days trying to fix my brand new phone.
Brand : Xiaomi
Model : Mi ultra
My Computer : MacBook Air
Problem : "The system has been destroy"
Other problem :
- USB debugging OFF (not able to access to the phone in any way)
- Bootloader Locked
How its happen :
After installing an EU Rom, I re locked the boot loader using Adb... And it crashed.
I tried almost everything you find on internet using a Mac and till now nothing worked.
I tried to unlock the boot loader using ADB, which one the only thing who seems to be working and I got an error message saying that the Miunlocktools was too old ... ?
The token was available, as I already unlock it.
Does anyone know how I can switch ON the debugging mode without accessing my phone, or Unlock the boot loader using my Mac.
It seems there is solution possible but using windows computer, and tbh I will not buy a computer just for that.. for the moment
Thanks in advance to everyone
PS : I will offer 50USD straight in BTC to the one who will provide me the solution that will help me to fix it
Locking / unlocking a phone's bootloader is done by means of Fastboot, not ADB.
ADB & Fastboot are 2 completely different things. Don't confuse them.
AFAIK you can't enable ADB ( USB debugging ) from outside, this can only get enabled from inside ( Android Settings -> Developer options ) unless one creates/provides a flashable, properly signed ZIP that contains the code ( read: update-binary script ) to rewrite device's build.prop file entries accordingly.
BTW: A locked bootloader always tries to run device's Stock ROM.
Thanks for your quick answer. In other word, is it possible ? I am looking for what you say.
If I rewrite it, will I be able to switch it ON then ?
Im not at all a professional , that's my first step in this "world". It seems difficult, I will need to read a lot I think
What do you think about the EDL cable also, do you think it can work ?
thxx
Kayzers0ze said:
What do you think about the EDL cable also, do you think it can work ?
Click to expand...
Click to collapse
IDK.
Never have bricked a phone. And I never owned a Xiaomi device.
locking a bootloader (at least in xiaomi phones )results in the phone being reformatted and the stock rom is installed
also try installing the newest version of miunlock https://en.miui.com/unlock/download_en.html
you might have to wait 7 days or less or more or might not have to
historys said:
locking a bootloader (at least in xiaomi phones )results in the phone being reformatted and the stock rom is installed
also try installing the newest version of miunlock https://en.miui.com/unlock/download_en.html
you might have to wait 7 days or less or more or might not have to
Click to expand...
Click to collapse
Hi
I re locked the boot loader myself so I unlocked it before
Thats the version I have but in the terminal I got a message saying version is too old...
Hello. Looking at different forums for answers on this subject, I've found many people who also want to root their Hot Pepper VLE5 devices. I really want to root this thing, and in most forums instead of answering the question, people point out that this device is cheap and not worth rooting. I have tried ADB root, which returns with something like "cannot root production builds", and so I went to see how to change that. Spoiler, that also requires root. Then I saw the push/pull command and SuperSU tutorial, but once again you need root to do that, and to be honest, why would you put that on your device if you already have root?? I'm not exactly sure about how the twrp and magisk stuff works but from what I've seen those also require some kind of super user access or something. I have unlocked the bootloader with ADB, which is one problem out of the way, but I'm running out of options and need some help with it, if anyone wants to help, that is. I need root on this because it is currently the only device I have, besides a laptop made for Windows Vista running 7 Ultimate on it (I have a better PC, just not with me), and I want to do WiFi pentesting and other things because I'm very interested in cyber security and such and it's becoming difficult to find anymore help with this. I really am not concerned with the specs limiting the usage of the device, I just want a solution and there's many others I have found with the same issue.
Thank you for your time.
Only devices running Android of build type ENG and/or USERDEBUG can get rooted, AFAIK.
Only devices running a properly rooted Android can apply command "adb root" what allows you to write to device's /system partition.
To unlock device's bootloader you have to apply the appropriate Fastboot commands: You can't unlock the bootloader via ADB. At least I never have heard or read that this would be possible.
jwoegerbauer said:
Only devices running Android of build type ENG and/or USERDEBUG can get rooted, AFAIK.
Only devices running a properly rooted Android can apply command "adb root" what allows you to write to device's /system partition.
To unlock device's bootloader you have to apply the appropriate Fastboot commands: You can't unlock the bootloader via ADB. At least I never have heard or read that this would be possible.
Click to expand...
Click to collapse
It allowed me to unlock it with ADB or Fastboot or something I forget, it was something via the command line
PulseJaymes said:
It allowed me to unlock it with ADB or Fastboot or something I forget, it was something via the command line
Click to expand...
Click to collapse
1. https://android.tutorials.how/adb-fastboot-installation/
2.
Unrelated, i just sent a DM to user diplomatic asking/offering a low bounty for sharing their mediatek temp-root exploit... They has already posted for other CPU architectures (incl armv8), but not the armv71, which iiuc is what the VLE5 runs on.
Idk diplomatic hasnt been active in a couple months so we'll see if they respond.
jwoegerbauer said:
Only devices running Android of build type ENG and/or USERDEBUG can get rooted, AFAIK.
Only devices running a properly rooted Android can apply command "adb root" what allows you to write to device's /system partition.
To unlock device's bootloader you have to apply the appropriate Fastboot commands: You can't unlock the bootloader via ADB. At least I never have heard or read that this would be possible.
Click to expand...
Click to collapse
@jwoegerbauer
Thanks for the info.
Sounds like the OP did use Fastboot commands.
Their OP question was on rooting... I have the exact same device, so am wondering:
If I unlocked the bootloader (via Fastboot tool commandline),
Can i then break the stock boot image to either:
A.) replace it (eg. with Lineage OS), and/or
B.) extract and patch the existing stock ROM?
(Note, the mgfr oem does not provide any updates nor firmware images, neither ota nor otherwise of any kind.
So i have to work strictly w what is on the device.
Another Q:
If i replace the stock rom w lineage and cannot backup the stock rom first.... Will i need to worry about drivers for Android (eg. wifi/bluetooth chips, GPU, etc.) ? I'm used to working w windows or linux, is why i ask..)
while I have no experiance with qualcomm devices, the procedure is near identical to mediatek devices, so to back up your system partition just boot into EDL mode and read the flash using a qualcomm flashing tool. Then, unpack the system image throw in a su binary under /system/sbin/ repack it and flash it!
it's optional to then install magisk or supersu for a root manager for security.
That's atleast how I mangled my cellphone and did unspeakable things to the system!
I just got this phone using it as a backup right now till I can fix my other phone so I'm assuming nobody got it rooted?
I found this VLE5 if this helps anybody I haven't tried it yet but I see the VLE5 on there
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.