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
I posted a thread on this, commented on a couple other threads, posted on Reddit, and I simply cannot get straight answers across the board. All the feedback I'm getting is different. I am willing to PayPal friends and family $5 to the first person that can answer my questions with links to sources just so I can ensure the information I'm getting is correct. I haven't rooted a phone since my 1st Gen Moto X so I'm out of the loop, but have a understanding of everything.
I have a GM1915 OnePlus 7 Pro that is T-Mobile SIM unlocked. I followed the tutorials HERE and HERE to flash the global firmware and all went well. Only issue I had was my SIM was being detected but no service, so I did an OTA update to 10.0.3 and my service is working fine now. Here are where my questions begin:
1. Now that I have installed the international firmware I don't need to get a bootloader unlock from T-Mobile/OnePlus, correct? I can just use the OEM unlock option and unlock via fastboot?
I have had people tell me I am good to enable OEM unlocking and use fastboot oem unlock, others have told me I still need to request a unlock, others tell me to downgrade to SP3. I just need a straightforward answer: Can I use OEM unlocking or do I need to request an unlock from OnePlus?
2. I know bootloader/root can sometimes cause certain applications to not function, but I've also read Magisk has a setting to correct this. I'm mainly just concerned with Google Pay, is there a method for it to still function with root?
Again, I've had some people tell me I can't use Google Pay, Netflix, or anything like that at all, others tell me Magisk Hide and SafetyNet will fix this issue. I also had an individual state "However, recent changes coming might thwart this.". Again, can I use Google Pay or can't I?
3. Part of me would actually like to use the phone stock for a week or so to see if I even feel like I need root access. I am currently on OS 10.0.3, if I update to the newest OS (looks like 10.3.1 is the newest) will I still be able to root with Magisk and flash TWRP? I would assume yes since you can do an OTA update and keep Magisk, but I just wanted to verify.
So if I update to 10.3.1 can I still follow the same tutorial listed under question 1 and it will work? Doesn't the most recent version of TWRP/Magisk support 10.3.1? Or will I need to use MSM and go back to 9.5.X (can't remember the exact version, but it's the OS it puts you on when you follow the steps for international firmware flashing)? Can I even go back to 9.5.X after updating to 10.3.1? I see release notes for TWRP that state is now have Android Q support but I just want to ensure it's compatibile with 10.3.1 or whatever the newest OS is.
Code:
mauronofrio matarrese
2019-08-18T15:04:57Z
Upload New Blobs for Android Q
I know regardless my phone is going to get wiped, I just want to be prepared on what I need to do if I decide to root.
I don't need links to tutorials, there are plenty of them and I understand how flashing TWRP and Magisk works, I just need my above questions answered with sources. I have searched around for a couple days and cannot get straight forward answers for any of these. First to answer every question with sources I'll send $5 PayPal.
ThisIsCheez said:
I posted a thread on this, commented on a couple other threads, posted on Reddit, and I simply cannot get straight answers across the board. All the feedback I'm getting is different. I am willing to PayPal friends and family $5 to the first person that can answer my questions with links to sources just so I can ensure the information I'm getting is correct. I haven't rooted a phone since my 1st Gen Moto X so I'm out of the loop, but have a understanding of everything.
I have a GM1915 OnePlus 7 Pro that is T-Mobile SIM unlocked. I followed the tutorials HERE and HERE to flash the global firmware and all went well. Only issue I had was my SIM was being detected but no service, so I did an OTA update to 10.0.3 and my service is working fine now. Here are where my questions begin:
1. Now that I have installed the international firmware I don't need to get a bootloader unlock from T-Mobile/OnePlus, correct? I can just use the OEM unlock option and unlock via fastboot?
I have had people tell me I am good to enable OEM unlocking and use fastboot oem unlock, others have told me I still need to request a unlock, others tell me to downgrade to SP3. I just need a straightforward answer: Can I use OEM unlocking or do I need to request an unlock from OnePlus?
2. I know bootloader/root can sometimes cause certain applications to not function, but I've also read Magisk has a setting to correct this. I'm mainly just concerned with Google Pay, is there a method for it to still function with root?
Again, I've had some people tell me I can't use Google Pay, Netflix, or anything like that at all, others tell me Magisk Hide and SafetyNet will fix this issue. I also had an individual state "However, recent changes coming might thwart this.". Again, can I use Google Pay or can't I?
3. Part of me would actually like to use the phone stock for a week or so to see if I even feel like I need root access. I am currently on OS 10.0.3, if I update to the newest OS (looks like 10.3.1 is the newest) will I still be able to root with Magisk and flash TWRP? I would assume yes since you can do an OTA update and keep Magisk, but I just wanted to verify.
So if I update to 10.3.1 can I still follow the same tutorial listed under question 1 and it will work? Doesn't the most recent version of TWRP/Magisk support 10.3.1? Or will I need to use MSM and go back to 9.5.X (can't remember the exact version, but it's the OS it puts you on when you follow the steps for international firmware flashing)? Can I even go back to 9.5.X after updating to 10.3.1? I see release notes for TWRP that state is now have Android Q support but I just want to ensure it's compatibile with 10.3.1 or whatever the newest OS is.
Code:
mauronofrio matarrese
2019-08-18T15:04:57Z
Upload New Blobs for Android Q
I know regardless my phone is going to get wiped, I just want to be prepared on what I need to do if I decide to root.
I don't need links to tutorials, there are plenty of them and I understand how flashing TWRP and Magisk works, I just need my above questions answered with sources. I have searched around for a couple days and cannot get straight forward answers for any of these. First to answer every question with sources I'll send $5 PayPal.
Click to expand...
Click to collapse
Firstly I can't give you a reputable source, and I don't want any money. I actually recently bought a Renewed Oneplus 7 Pro from amazon when it was 420, its the Black 8GB 256GB T-Mobile GM1915 model. So here is what I found out , and currently running Ill post some pics to show you
1. If you followed the guides above exactly and everything went smoothly your pefectly fine to use OEM Unlock, it basically installs a version of the firmware that doesn't check for a boot loader unlock token. I had originally requested one as well than found this nifty guide and it worked amazingly.
2. Yes it will work perfectly fine with Magisk, just use the Hide Magisk , it will resintall under a new name. Than you can even go further and use magisk hide to hide it from each app independently. As for google pay I have mine setup and it worked fine. I haven't actually been able to go into store and use it as we are very closed off in home now, but It allowed me to add my card fine, verify with my bank and all that good stuff. As for netflix yes it will work but since you unlocked bootloader you lose the Widevine DRM L1 certification and thus can't watch in HDR anymore. It still works fine though and honestly looks alright to me.
3. I had updated my T-Mobile OS all the way to latest version forget what it was at the moment, and than I did the tutorial to unlock the bootloader and flash twrp/magisk/rom. It worked out perfectly fine so you should be fine as well. What I would do is use the tutorial above unlock bootloader, because that version of the OS doesn't check for unlock token, than flash a stock Global rom 10.3.2 is avaliable now. and enjoy it for awhile and when your ready install a custom rom and magisk.
I'll add some pictures of things you asked about. Sadly I can't show my model number in system due to rom but i showed it connected to my pc.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Kireyev said:
Firstly I can't give you a reputable source, and I don't want any money. I actually recently bought a Renewed Oneplus 7 Pro from amazon when it was 420, its the Black 8GB 256GB T-Mobile GM1915 model. So here is what I found out , and currently running Ill post some pics to show you.
[/HIDE]
Click to expand...
Click to collapse
This was more than helpful, and a first hand account. I know you said that you didn't want any money but I am prepared to send it, if you don't want it I will donate to a charity of your choice.
3. I had updated my T-Mobile OS all the way to latest version forget what it was at the moment
Click to expand...
Click to collapse
When you say this, did you update your firmware OTA on the T-Mobile firmware, or the Global/International firmware using OTA? I don't want to skip any incremental updates and cause issues so I might update using OTA to the newest it provides than use Oxygen Updater to get to 10.3.2. As long as I can be on the newest firmware and still unlock my bootloader and flash TWRP I'm fine. I mainly got this phone because it ticks every feature box I want and it can be rooted, but I'm up for using it stock for a while to see if I even want root.
Edit: I reread you post and think I looked over something about unlocking the bootloader. So the specific version of the firmware you flash to to swap to the international firmware doesn't require an unlock token, so if I wanted to use the OEM unlock I'd need to be back on that version, but if I wanted to unlock after I update to 10.3.2 I'd need to request a token. Am I understanding that correctly?
ThisIsCheez said:
This was more than helpful, and a first hand account. I know you said that you didn't want any money but I am prepared to send it, if you don't want it I will donate to a charity of your choice.
When you say this, did you update your firmware OTA on the T-Mobile firmware, or the Global/International firmware using OTA? I don't want to skip any incremental updates and cause issues so I might update using OTA to the newest it provides than use Oxygen Updater to get to 10.3.2. As long as I can be on the newest firmware and still unlock my bootloader and flash TWRP I'm fine. I mainly got this phone because it ticks every feature box I want and it can be rooted, but I'm up for using it stock for a while to see if I even want root.
Click to expand...
Click to collapse
It was the T-Mobile firmware. 10.0.3 version. I had done it before I was even thinking about unlocking bootloader and flashing. Than when I saw the custom ROMS + Kernels where you can gain massive performance gains or optimize battery like mad I was sold on it. Plus the ugly t-mobile boot screens annoyed me. It is an amazing phone and prices can be had at its a steal. Also their is a TWRP that lets you dual boot and use shared data partition. So you could have one boot as a custom ROM, and another as stock and have the data shared in a common partition. Get a little of both ^_^
Like I have two profiles and one is more performance / battery Optimized
This other was more for fun on seeing how far I can push scores I am bored during this lockdown lol
Kireyev said:
It was the T-Mobile firmware. 10.0.3 version. I had done it before I was even thinking about unlocking bootloader and flashing. Than when I saw the custom ROMS + Kernels where you can gain massive performance gains or optimize battery like mad I was sold on it. Plus the ugly t-mobile boot screens annoyed me. It is an amazing phone and prices can be had at its a steal. Also their is a TWRP that lets you dual boot and use shared data partition. So you could have one boot as a custom ROM, and another as stock and have the data shared in a common partition. Get a little of both ^_^
Like I have two profiles and one is more performance / battery Optimized
This other was more for fun on seeing how far I can push scores I am bored during this lockdown lol
Click to expand...
Click to collapse
Thanks for all the replies. Would you care to answer this question below? And if you do not want the cash what charity would you like it donated to?
Edit: I reread you post and think I looked over something about unlocking the bootloader. So the specific version of the firmware you flash to to swap to the international firmware doesn't require an unlock token, so if I wanted to use the OEM unlock I'd need to be back on that version, but if I wanted to unlock after I update to 10.3.2 I'd need to request a token. Am I understanding that correctly?
ThisIsCheez said:
Thanks for all the replies. Would you care to answer this question below? And if you do not want the cash what charity would you like it donated to?
Edit: I reread you post and think I looked over something about unlocking the bootloader. So the specific version of the firmware you flash to to swap to the international firmware doesn't require an unlock token, so if I wanted to use the OEM unlock I'd need to be back on that version, but if I wanted to unlock after I update to 10.3.2 I'd need to request a token. Am I understanding that correctly?
Click to expand...
Click to collapse
You know I am honestly not sure on this part, I did the bootloader unlock right after I followed that tutorial with the MSM tool. I am pretty sure its just the t-mobile firmware that blocks you from doing OEM unlock with out token. Not the global. But one way to find out be enable OEM unlock in developer settings, and run the fastboot oem unlock cmd. See if it works. If not you have your answere and will have to go back to other version. If you want you can always relock bootloader. I would test this but as I've already unlocked , re-locking and unlocking probably not give proper answer. But if you want I can install 10.3.3 lock bootloader and try to unlock it again lol.
EDIT: a test in sues.
Kireyev said:
You know I am honestly not sure on this part, I did the bootloader unlock right after I followed that tutorial with the MSM tool. I am pretty sure its just the t-mobile firmware that blocks you from doing OEM unlock with out token. Not the global. But one way to find out be enable OEM unlock in developer settings, and run the fastboot oem unlock cmd. See if it works. If not you have your answere and will have to go back to other version. If you want you can always relock bootloader. I would test this but as I've already unlocked , re-locking and unlocking probably not give proper answer. But if you want I can install 10.3.3 lock bootloader and try to unlock it again lol.
EDIT: a test in sues.
Click to expand...
Click to collapse
So I tried fastboot oem unlock after updating to 10.3.1 and it asked me if I wanted to unlock without prompting for an unlock token. I didn't choose the option to unlock, I kept it locked, but I think if I can get that far I should be able to unlock without a token on 10.3.1
ThisIsCheez said:
So I tried fastboot oem unlock after updating to 10.3.1 and it asked me if I wanted to unlock without prompting for an unlock token. I didn't choose the option to unlock, I kept it locked, but I think if I can get that far I should be able to unlock without a token on 10.3.1
Click to expand...
Click to collapse
I can confirm now officially. After locking my bootloader, using MSM tool to go back to T-Mobile updating to 10.0.3 and trying to unlock bootloader it wouldn't work as I thought.
When using the MSM tool to go to international version and updating all the way to 10.3.2, it worked perfectly fine. So you can be on global rom and not worry about being able to unlock bootloader later due to updates Very awesome can get on global rom and not compromise bootloader so can have all security in place
Kireyev said:
I can confirm now officially. After locking my bootloader, using MSM tool to go back to T-Mobile updating to 10.0.3 and trying to unlock bootloader it wouldn't work as I thought.
When using the MSM tool to go to international version and updating all the way to 10.3.2, it worked perfectly fine. So you can be on global rom and not worry about being able to unlock bootloader later due to updates Very awesome can get on global rom and not compromise bootloader so can have all security in place
Click to expand...
Click to collapse
You are the GOAT. Not only does this help me but hopefully some other members of the community that wish to update and try stock before unlocking the bootloader.
Kireyev said:
I can confirm now officially. After locking my bootloader, using MSM tool to go back to T-Mobile updating to 10.0.3 and trying to unlock bootloader it wouldn't work as I thought.
When using the MSM tool to go to international version and updating all the way to 10.3.2, it worked perfectly fine. So you can be on global rom and not worry about being able to unlock bootloader later due to updates Very awesome can get on global rom and not compromise bootloader so can have all security in place
Click to expand...
Click to collapse
Just as verification that I wasn't using the PayPal reward as a ploy to get someone to respond and bail, Kireyev declined payment so I made a donation to ExtraLife in his name. Thanks again for your help to me and the community.
https://www.extra-life.org/index.cfm?fuseaction=donorDrive.participant&participantID=408732
Kireyev said:
I can confirm now officially. After locking my bootloader, using MSM tool to go back to T-Mobile updating to 10.0.3 and trying to unlock bootloader it wouldn't work as I thought.
When using the MSM tool to go to international version and updating all the way to 10.3.2, it worked perfectly fine. So you can be on global rom and not worry about being able to unlock bootloader later due to updates Very awesome can get on global rom and not compromise bootloader so can have all security in place
Click to expand...
Click to collapse
hey thank you both for this thread but admittedly i am a little lost and i really do not want to brick this device, ive rooted devices in the pas, some even requiring hardware modifications to do so. but i just want to make sure i do everything right
im on a sim unlocked t-mobile 10.0.3.gm31cb right now
what are the exact steps i need to follow to unlock bootloader, and get on the latest rom ?
Outta said:
hey thank you both for this thread but admittedly i am a little lost and i really do not want to brick this device, ive rooted devices in the pas, some even requiring hardware modifications to do so. but i just want to make sure i do everything right
im on a sim unlock
Click to expand...
Click to collapse
If you follow the main guide on xda exactly you're going be fine. Once on global your essentially done because than you can flash a twrp through fastboot and install any rom, kernel you want. As well as magisk. The most important part is that msm guide. Now if you want to be more official get an unlock token and do it the regular way through fastboot with the unlock token. It took about a week in a half to get mine. But the msm guide works perfectly. Also I've gotten my device stuck in multiple fastboot loops and stuff their is always a way back.
Kireyev said:
If you follow the main guide on xda exactly you're going be fine. Once on global your essentially done because than you can flash a twrp through fastboot and install any rom, kernel you want. As well as magisk. The most important part is that msm guide. Now if you want to be more official get an unlock token and do it the regular way through fastboot with the unlock token. It took about a week in a half to get mine. But the msm guide works perfectly. Also I've gotten my device stuck in multiple fastboot loops and stuff their is always a way back.
Click to expand...
Click to collapse
Exactly which guide, at least 5 have been discussed lol what are the exact steps to take to go from stock be tmo to bootloader unlocked and rooted on latest stock rom.
I also don't mind sending you a monetary gift for your help. Thanks in advanced.
Outta said:
Exactly which guide, at least 5 have been discussed lol what are the exact steps to take to go from stock be tmo to bootloader unlocked and rooted on latest stock rom.
I also don't mind sending you a monetary gift for your help. Thanks in advanced.
Click to expand...
Click to collapse
This guide
https://forum.xda-developers.com/oneplus-7-pro/help/how-to-convert-tmobile-op7-to-t3935947
Once you follow this you will be off TMobile stock and on global stock. Here you can choose to unlock bootloader or not. You don't need to root and install twrp to be on global rom. Just basically do the msm guide than. Update through the oxygen updater app to latest.
Kireyev said:
This guide
https://forum.xda-developers.com/oneplus-7-pro/help/how-to-convert-tmobile-op7-to-t3935947
Once you follow this you will be off TMobile stock and on global stock. Here you can choose to unlock bootloader or not. You don't need to root and install twrp to be on global rom. Just basically do the msm guide than. Update through the oxygen updater app to latest.
Click to expand...
Click to collapse
just bricked my phone at this part:
3) Hold both volume buttons for 5 seconds then plug in the USB cable. OR In ADB type "adb reboot edl".
phone turned off and wont turn back on, any idea what tro do now?
Outta said:
just bricked my phone at this part:
3) Hold both volume buttons for 5 seconds then plug in the USB cable. OR In ADB type "adb reboot edl".
phone turned off and wont turn back on, any idea what tro do now?
Click to expand...
Click to collapse
Yep your in download mode, its not bricked no worries. just hold volume up and power button for awhile you well feel a vibrate and than it will reboot
Kireyev said:
If you follow the main guide on xda exactly you're going be fine. Once on global your essentially done because than you can flash a twrp through fastboot and install any rom, kernel you want. As well as magisk. The most important part is that msm guide. Now if you want to be more official get an unlock token and do it the regular way through fastboot with the unlock token. It took about a week in a half to get mine. But the msm guide works perfectly. Also I've gotten my device stuck in multiple fastboot loops and stuff their is always a way back.
Click to expand...
Click to collapse
Kireyev said:
Yep your in download mode, its not bricked no worries. just hold volume up and power button for awhile you well feel a vibrate and than it will reboot
Click to expand...
Click to collapse
Thanks again, saved, do you have any idea what my issue is, why isn't msm seeing my device? Adb does..
Outta said:
Thanks again, saved, do you have any idea what my issue is, why isn't msm seeing my device? Adb does..
Click to expand...
Click to collapse
strange all you really need do is hook it up to pc, enable usb debugging which u've done. type adb reboot edl, wait for it and have msm open and it should connect. My only thing to suggest would be try another cable or another port on the pc. sometimes i've also noticed fastboot can be odd for me and I have to reboot the computer for it to notice my phone . I'd suggest try those things. Did you check your system model and see if it was the 1915 model with the GM31CB?
dont know if you got it or not but heres link to the commands https://droidfeats.com/unlock-bootloader-oneplus-7-pro-t-mobile/
Sorry for making another thread so soon, but I've got new issues now. TL;DR, I'm just trying to get my Moto G7 Power to detect my sim card at *all* anymore. I've been told that installing an OTA will make the phone detect the sim card again, but... I can't re-lock my bootloader.
I've spent pretty much all day looking for ways to re-lock it, but not a single one has worked. I always get the same "Still waiting for signed boot.img" message, even when I try fixes that worked for others. At this point, I give up on trying to re-lock. I just rooted using a guide here and connected to WiFi.
The next best thing would be for me to find another way to install OTAs. I've heard Magisk used to be able to hide your bootloader status and let you do that, but can't anymore, so...
1. Is there a way for me to install official android updates manually? If so, how?
2. If there is, *where* do I find the updates?
T-Mobile [PCO29.114-54-2]
XT1955-5
Tsukomasi said:
Sorry for making another thread so soon, but I've got new issues now. TL;DR, I'm just trying to get my Moto G7 Power to detect my sim card at *all* anymore. I've been told that installing an OTA will make the phone detect the sim card again, but... I can't re-lock my bootloader.
I've spent pretty much all day looking for ways to re-lock it, but not a single one has worked. I always get the same "Still waiting for signed boot.img" message, even when I try fixes that worked for others. At this point, I give up on trying to re-lock. I just rooted using a guide here and connected to WiFi.
The next best thing would be for me to find another way to install OTAs. I've heard Magisk used to be able to hide your bootloader status and let you do that, but can't anymore, so...
1. Is there a way for me to install official android updates manually? If so, how?
2. If there is, *where* do I find the updates?
T-Mobile [PCO29.114-54-2]
XT1955-5
Click to expand...
Click to collapse
Retus one u need to flash do u have the bat file? Try flashing the modem non -hlos.bin in fastboot mode
You can install OTAs with unlocked bootloader, but you'll need to unroot your device first
Sorry for being 2 weeks late, but you look like you're in the exact same position I once was. Flashing an official update for my channel, available at https://mirrors.lolinet.com/firmware/moto/ocean/official/ was what solved it for me, for whatever reason. (my SIM also wasn't recognized at all, nor did I have any IMEIs outside of bootloader. Also, the option to enable OEM unlocking never became available to me, despite instantly being available when I solved it)
We're technically able to install OTAs with unlocked bootloaders? But for some reason mine throws up an error at step 3/6 every time, so I'm dependant on Lolinet to install them.
On relocking bootloader, you had to re-flash boot.img, run the command 3 times, re-flash and run the command again or something, I was also going to try that on one of my threads, but since I couldn't enable OEM unlocking.
Hyoretsu said:
Sorry for being 2 weeks late, but you look like you're in the exact same position I once was. Flashing an official update for my channel, available at https://mirrors.lolinet.com/firmware/moto/ocean/official/ was what solved it for me, for whatever reason. (my SIM also wasn't recognized at all, nor did I have any IMEIs outside of bootloader. Also, the option to enable OEM unlocking never became available to me, despite instantly being available when I solved it)
We're technically able to install OTAs with unlocked bootloaders? But for some reason mine throws up an error at step 3/6 every time, so I'm dependant on Lolinet to install them.
On relocking bootloader, you had to re-flash boot.img, run the command 3 times, re-flash and run the command again or something, I was also going to try that on one of my threads, but since I couldn't enable OEM unlocking.
Click to expand...
Click to collapse
Every OTA zip first verifies your entire system by checksums. Is there any modified partition the verifier fails and the update process ends with an error.
WoKoschekk said:
Every OTA zip first verifies your entire system by checksums. Is there any modified partition the verifier fails and the update process ends with an error.
Click to expand...
Click to collapse
Probably my Magisk then, but meh
MOD Edit: check post #25#25 before you proceed.
craznazn said:
This thread was created before I made the MSM conversion, hence the confusion. Probably could be locked now.
And if the OP is still reading this, for your own good don't mess with modemst1/2/persist unless you really know what you're doing.
Click to expand...
Click to collapse
As title suggests, I am trying to convert from the T-Mobile software to Global or EU. Have already read the threads claiming you can just flash the firmware that you want and everything will work fine as long as you also flash the T-Mobile carrier, modem, modemst1, and modemst2 images. However, there is no local upgrade option in settings, so I decided to go the manual route by downloading full zip, using payload dumper and flashing all required partitions, including the T-Mobile modem partitions and whatnot. Well, in terminal when trying to flash certain ones, I get the error:
FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed
So I basically just reboot, nothing seems changed and I still have a working phone. What gives? I'm coming from the OnePlus 7 Pro and although had my ups and downs (generally forgetting a step or making small mistakes) it was a fairly easy experience and I could usually just retrace my steps or do some research on forums and figure it out. This time I have looked through so many forums here and on other sites but I can't figure out what's going on.
Details:
Phone is fully functional as of right now
Running 11.2.2.2 (T-Mobile) attempting to convert to 11.2.4.4 (EU)
Had mobbdeep network unlock for me, then requested unlock token from OnePlus, flashed unlock_code.bin, unlocked Bootloader
Successfully rooted with Magisk, although failed SafetyNet so installed latest canary build and everything is working flawlessly now
Can't local upgrade, can't flash via Fastboot, no TWRP available for this device, is there anything that I am missing? or another way that I can flash full update or partitions?
I know I may seem impatient, but I've seen so many others say they already converted to global, and it's working after flashing necessary modem and carrier partitions. Just wondering EXACTLY how they were able to do it, when I followed exact steps from these threads and I've done this sort of thing so many times in the past it is downright frustrating at this point. I've also contacted OnePlus to see if there is an MSM tool available for this device and they sort of made it seem that there was and said my concern will be escalated and I will get a response via email within 24 hours (fingers crossed).
My next steps will be to re-lock the bootloader and start from scratch. After that, I guess my only recourse is to wait for TWRP or MSM tool and official guide for converting to global ROM. Thanks in advance for any and all clarifications.
Side Note: Already tried fastboot flashing unlock_critical command and similar ones, always returns message saying already unlocked. And the conversion guide I was following was from this thread: https://forum.xda-developers.com/t/tmo-eu-global-the-way-i-did-it.4264883/
Certain partitions need to be flashed from the bootloader fastboot, not fastbootd.
Either way, there is no going back to the T-Mobile firmware as there's no unbrick tool yet.
Don't do this.
lrod55 said:
As title suggests, I am trying to convert from the T-Mobile software to Global or EU. Have already read the threads claiming you can just flash the firmware that you want and everything will work fine as long as you also flash the T-Mobile carrier, modem, modemst1, and modemst2 images. However, there is no local upgrade option in settings, so I decided to go the manual route by downloading full zip, using payload dumper and flashing all required partitions, including the T-Mobile modem partitions and whatnot. Well, in terminal when trying to flash certain ones, I get the error:
FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed
So I basically just reboot, nothing seems changed and I still have a working phone. What gives? I'm coming from the OnePlus 7 Pro and although had my ups and downs (generally forgetting a step or making small mistakes) it was a fairly easy experience and I could usually just retrace my steps or do some research on forums and figure it out. This time I have looked through so many forums here and on other sites but I can't figure out what's going on.
Details:
Phone is fully functional as of right now
Running 11.2.2.2 (T-Mobile) attempting to convert to 11.2.4.4 (EU)
Had mobbdeep network unlock for me, then requested unlock token from OnePlus, flashed unlock_code.bin, unlocked Bootloader
Successfully rooted with Magisk, although failed SafetyNet so installed latest canary build and everything is working flawlessly now
Can't local upgrade, can't flash via Fastboot, no TWRP available for this device, is there anything that I am missing? or another way that I can flash full update or partitions?
I know I may seem impatient, but I've seen so many others say they already converted to global, and it's working after flashing necessary modem and carrier partitions. Just wondering EXACTLY how they were able to do it, when I followed exact steps from these threads and I've done this sort of thing so many times in the past it is downright frustrating at this point. I've also contacted OnePlus to see if there is an MSM tool available for this device and they sort of made it seem that there was and said my concern will be escalated and I will get a response via email within 24 hours (fingers crossed).
My next steps will be to re-lock the bootloader and start from scratch. After that, I guess my only recourse is to wait for TWRP or MSM tool and official guide for converting to global ROM. Thanks in advance for any and all clarifications.
Side Note: Already tried fastboot flashing unlock_critical command and similar ones, always returns message saying already unlocked. And the conversion guide I was following was from this thread: https://forum.xda-developers.com/t/tmo-eu-global-the-way-i-did-it.4264883/
Click to expand...
Click to collapse
Curious, do you have the stock T-Mobile oneplus9 regular boot.img you can share ? I am looking to try several things on my end but I forgot to backup that img file. Thank you in advance.
inspron said:
Curious, do you have the stock T-Mobile oneplus9 regular boot.img you can share ? I am looking to try several things on my end but I forgot to backup that img file. Thank you in advance.
Click to expand...
Click to collapse
I should still have the boot.img I backed up from stock 11.2.2.2 (T-Mobile). I'll attach it here when I get off work
LLStarks said:
Certain partitions need to be flashed from the bootloader fastboot, not fastbootd.
Either way, there is no going back to the T-Mobile firmware as there's no unbrick tool yet.
Don't do this.
Click to expand...
Click to collapse
+1 . I myself love flashing things and have the unlocked op9. Just got in mail and unlocked and rooted this evening. I however will not be flashing anything but magisk updates till an msm tool is available for us to use.
inspron said:
Curious, do you have the stock T-Mobile oneplus9 regular boot.img you can share ? I am looking to try several things on my end but I forgot to backup that img file. Thank you in advance.
Click to expand...
Click to collapse
This should be the stock boot.img from the 11.2.2.2 T-Mobile build. Named it that way so as to not confuse it with stock boot image from 11.2.4.4 (EU)
boot(old).img (Google Drive link)
mattie_49 said:
+1 . I myself love flashing things and have the unlocked op9. Just got in mail and unlocked and rooted this evening. I however will not be flashing anything but magisk updates till an msm tool is available for us to use.
Click to expand...
Click to collapse
Will heed your guys' warnings. Just was super curious (and confused) as to how others were able to get it to work
Following in case there is a breakthrough. I hate the locked T-Mobile BS. And all I want to be able to do is stay awake while charging. My 6 did it no problem. But this thing is making me mad.
jaed.43725 said:
Following in case there is a breakthrough. I hate the locked T-Mobile BS. And all I want to be able to do is stay awake while charging. My 6 did it no problem. But this thing is making me mad.
Click to expand...
Click to collapse
You know the unlocked global version works with carrier sims. I'm on verizon . Bought the unlocked 9 popped the verizon sim in and everything works perfect. Vvm/5g everything. And unlocked to my liking
mattie_49 said:
You know the unlocked global version works with carrier sims. I'm on verizon . Bought the unlocked 9 popped the verizon sim in and everything works perfect. Vvm/5g everything. And unlocked to my liking
Click to expand...
Click to collapse
Yes, I am very aware of that. The issue is I have the T-Mobile version because I got if 1/2 off with a trade in. Will this warrant a trade after I pay it off? Maybe. But I would rather just put on Lineage OS if that becomes possible.
lrod55 said:
As title suggests, I am trying to convert from the T-Mobile software to Global or EU. Have already read the threads claiming you can just flash the firmware that you want and everything will work fine as long as you also flash the T-Mobile carrier, modem, modemst1, and modemst2 images. However, there is no local upgrade option in settings, so I decided to go the manual route by downloading full zip, using payload dumper and flashing all required partitions, including the T-Mobile modem partitions and whatnot. Well, in terminal when trying to flash certain ones, I get the error:
FAILED (remote: 'Flashing is not allowed for Critical Partitions
')
fastboot: error: Command failed
So I basically just reboot, nothing seems changed and I still have a working phone. What gives? I'm coming from the OnePlus 7 Pro and although had my ups and downs (generally forgetting a step or making small mistakes) it was a fairly easy experience and I could usually just retrace my steps or do some research on forums and figure it out. This time I have looked through so many forums here and on other sites but I can't figure out what's going on.
Details:
Phone is fully functional as of right now
Running 11.2.2.2 (T-Mobile) attempting to convert to 11.2.4.4 (EU)
Had mobbdeep network unlock for me, then requested unlock token from OnePlus, flashed unlock_code.bin, unlocked Bootloader
Successfully rooted with Magisk, although failed SafetyNet so installed latest canary build and everything is working flawlessly now
Can't local upgrade, can't flash via Fastboot, no TWRP available for this device, is there anything that I am missing? or another way that I can flash full update or partitions?
I know I may seem impatient, but I've seen so many others say they already converted to global, and it's working after flashing necessary modem and carrier partitions. Just wondering EXACTLY how they were able to do it, when I followed exact steps from these threads and I've done this sort of thing so many times in the past it is downright frustrating at this point. I've also contacted OnePlus to see if there is an MSM tool available for this device and they sort of made it seem that there was and said my concern will be escalated and I will get a response via email within 24 hours (fingers crossed).
My next steps will be to re-lock the bootloader and start from scratch. After that, I guess my only recourse is to wait for TWRP or MSM tool and official guide for converting to global ROM. Thanks in advance for any and all clarifications.
Side Note: Already tried fastboot flashing unlock_critical command and similar ones, always returns message saying already unlocked. And the conversion guide I was following was from this thread: https://forum.xda-developers.com/t/tmo-eu-global-the-way-i-did-it.4264883/
Click to expand...
Click to collapse
you flash from bootloader (fastboot) or from fastbootd
FAILED (remote: 'Flashing is not allowed for Critical Partitions this is when you flash in fastboot
only fastbootd can flashh all partition
jaed.43725 said:
Following in case there is a breakthrough. I hate the locked T-Mobile BS. And all I want to be able to do is stay awake while charging. My 6 did it no problem. But this thing is making me mad.
Click to expand...
Click to collapse
You know there's a specific option under the development settings called 'stay awake', right?
TheKnux said:
You know there's a specific option under the development settings called 'stay awake', right?
Click to expand...
Click to collapse
I can not select it. It is greyed out for some reason.
TheKnux said:
You know there's a specific option under the development settings called 'stay awake', right?
Click to expand...
Click to collapse
On the T-Mobile version it is not selectable.
jaed.43725 said:
On the T-Mobile version it is not selectable.
Click to expand...
Click to collapse
Yeah that's BS because I definitely selected it while I was backing up my data before I converted from T-Mobile firmware.
jaed.43725 said:
On the T-Mobile version it is not selectable.
Click to expand...
Click to collapse
I'm on t-mobile version i can select it as well. Pretty sure everything in developers options is selectable. Some don't stick for whatever reason.
Ya, I don't know what this things deal is. But as soon as I get the ability to flash to international I'm doing it.
Where is the guide for flashing a OnePlus 9 from T-Mobile to International?
Btw for everyone following this thread, its an easy to miss step, but if you follow the guides for converting, all you have to do is go into fastboot and then use command “fastboot reboot fastboot”. This apparently puts you in fastbootd (never had to use this before, I would just use commands and flash stuff from bootloader screen but whatever) where you can then flash the needed partitions. Also, no hate to the guy who posted the recent conversion thread but it is super unorganized and a little too easy to miss that step, as well as MAKE SURE you read through the .bat file they provided because it is NOT correct. They have some typos in there so it wasn’t working for me at first. It’s a pain in the ass but I highly recommend going through each command, copy/paste, and read it to make sure there’s no typos then hit enter or you will run into errors like I did. Good luck
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.