Database Info

Verizon Bootloader Unlock

Is anyone else working on unlocking the bootloader for verizon pixels? Its clearly possible as people are doing it but but not releasing it publicly. All the other threads on this are locked because people keep trying to offer services outside of XDA. Are there theories on how its being done? Spoofing the verizon IMEI check server? Temp root and modifying a system file?

Quada said:
Is anyone else working on unlocking the bootloader for verizon pixels? Its clearly possible as people are doing it but but not releasing it publicly. All the other threads on this are locked because people keep trying to offer services outside of XDA. Are there theories on how its being done? Spoofing the verizon IMEI check server? Temp root and modifying a system file?
Click to expand...
Click to collapse
I have been poking around on google for a long time checking for Verizon bootloader unlock activity and I noticed that as well. This got me thinking, and while I haven't done a lot of digging to see if my idea if feasible here's what I got. I was thinking to leverage Spectre "https://en.wikipedia.org/wiki/Spectre_(security_vulnerability)" somehow to leak a signature that can then be passed in an api call to unlock the bootloader. If i recall, I think I remember seeing a function in android source somewhere that took a prm specifying unlock/lock and then a signature created by the vendor to allow the unlock. if you could figure out the appropriate offsets in memory, maybe it would be possible? As said, I have not done much research on this but just figured I'd share and see what others thought.

Pixel 2 Verizon unlock bootloader instructions are here below
Unlocking the Bootloader WILL WIPE YOUR DEVICE!! so backup important files.
Install ADB/Fastboot Drivers
Enable Developer Options
Enable USB Debugging in Developer Options
Plug Pixel 2 into PC
Open a Command Prompt window;
In Command Prompt, type adb start-server
and hit ENTER
If you see * daemon started successfully *
continue to next step
In Command Prompt, type adb devices
and hit ENTER
If you see "List of devices attached" as well as "Your Devices Serial Number device or unauthorized"
continue to next step
On Pixel 2 - Allow PC for USB Debugging
In Command Prompt, type adb reboot bootloader
Once your Pixel 2 has rebooted into the bootloader
In Command Prompt, type fastboot flashing lock_critical
and hit ENTER Then follow the instructions on your Pixel 2 to finish Unlocking Bootloader.
Correct on the steps, including the entire discussion found here. https://forum.xda-developers.com/pix...el-2s-t3726294
***PATCHED BY OUT-OF-CYCLE JANUARY UPDATE***
If you have received the OTA patch for your pixel2, and now are on OPM2.171019.016, you will no longer be able to run the command. And downgrade is not available at this time.
As of 1/24/2018 users who have purchased new phones have been able to remove the SIM, refuse internet (WiFi) connection at the initial startup. After completing the initial setup, you can sideload 8.1 to take advantage of the command in the OP. If you connect to the internet with WiFi or with your SIM, chances are high you will receive the update and this method WILL NOT work. To date, there are no other ways to unlock the bootloader on VZW PIX2 other than this method. Instructions to sideload stock OTA's are found here along with the downloads. https://developers.google.com/android/ota Once again, DO NOT USE 8.1.0 (OPM2.171019.016, Jan 2018, Verizon) but instead use 8.1.0 (OPM1.171019.013, Jan 2018) The command is not available on 8.0.
There is also another alternative way which has worked for me this week on Pixel 32GGB Verizon. Its called depixel8. more info can be found @ http://theroot.ninja/depixel8.html
Usage:
Step 1) Install fastboot and adb on your PC, ensure both are working with your Pixel.
Step 2) Run "adb push dePixel8 /data/local/tmp", "adb shell chmod 755 /data/local/tmp/dePixel8" and finally run the program "adb shell /data/local/tmp/dePixel8"
(put the depixel files in the same folder as your ADB/FASTBOOT drivers are where you do your command prompt commands)
Step 3) Wait for the phone to reboot to the bootloader. If it is not rebooting you can try to run various apps until it does, or you may have to reboot and start over.
Step 4) Issue the command "fastboot oem unlock", this will open up the unlock prompt and warning on the screen. You can now unlock. If you get an error, about unlocking not being allowed, start all over again.

MpandAUS said:
Pixel 2 Verizon unlock bootloader instructions are here below
Click to expand...
Click to collapse
dePixel8 is patched in Android 7.1.1 and newer.

lock bootlooader without power button
How can i relock my bootloader without use of my power button its broken

Keetoowah said:
How can i relock my bootloader without use of my power button its broken
Click to expand...
Click to collapse
Are you rooted?

Keetoowah said:
How can i relock my bootloader without use of my power button its broken
Click to expand...
Click to collapse
I personally recommend not relocking your bootloader. If you aren't on pure stock it will give you problems and even if you are on pure stock, an unlocked bootloader is a devices most powerful recovery tool and OTAs have been known to fail on occasion and other problems you would want to recover from can occur.
As to the answer to your question, if you can boot the device normally at all then you can turn on adb debugging and from there open an adb shell and use adb reboot bootloader to get to fastboot mode and then use fastboot oem lock I believe

KittyRgnarok said:
I personally recommend not relocking your bootloader. If you aren't on pure stock it will give you problems and even if you are on pure stock, an unlocked bootloader is a devices most powerful recovery tool and OTAs have been known to fail on occasion and other problems you would want to recover from can occur.
As to the answer to your question, if you can boot the device normally at all then you can turn on adb debugging and from there open an adb shell and use adb reboot bootloader to get to fastboot mode and then use fastboot oem lock I believe
Click to expand...
Click to collapse
Thank I've decided to have the power button repaired at my own expence since I have a Verizon Pixel 2 with an unlocked bootloader. The replacement they sent me wasn't unlockable. The unlocked bootloader with TWRP and root are well worth the price of the power button.

Keetoowah said:
Thank I've decided to have the power button repaired at my own expence since I have a Verizon Pixel 2 with an unlocked bootloader. The replacement they sent me wasn't unlockable. The unlocked bootloader with TWRP and root are well worth the price of the power button.
Click to expand...
Click to collapse
How much was the replacement button and installation by the way, I'm rather curious

getting back on track, it looks like someone claims to be able to OEM unlock after getting the April OTA? Can anyone support or contradict this claim? https://www.reddit.com/r/GooglePixel/comments/89rnoa/google_pixel_verizon_oem_unlock/

Anyone managed to root lg k51?

I can't find anything definitive about whether it's rootable or not

Same here i tried every root app possible and failed.

just unlock bootloader and flash twrp
after that flash latest magisk zip hope it will work

Bhanu8082 said:
just unlock bootloader and flash twrp
after that flash latest magisk zip hope it will work
Click to expand...
Click to collapse
No need to flash TWRP: Booting into it is sufficient.

Bhanu8082 said:
just unlock bootloader and flash twrp
after that flash latest magisk zip hope it will work
Click to expand...
Click to collapse
How did you unlock the bootloader?

sCriptKittY1987 said:
How did you unlock the bootloader?
Click to expand...
Click to collapse
simple , go to about phone and try to find build number,
after you find build number tap on it until it says you are in developer mode
after that head on to developer option (it may be inside about phone section or above about phone section) turn on the option which says allow oem unlock. then,
just reboot to recovery mode either by pressing volume up or volume down key with power button.
after you enter recovery connect usb cable and open command prompt in pc and make sure that lg device drivers are installed on your pc also make sure you have adb and fastboot installed.
ok, after all this type command
adb devices
if any thing shows us then you have successfully connected your device.
after it type
adb reboot bootloader
then your mobile should restart and show fastboot mode in screen
type command
fastboot oem unlock
and done your bootloader is unlocked.

Bhanu8082 said:
just unlock bootloader and flash twrp
after that flash latest magisk zip hope it will work
Click to expand...
Click to collapse
Where did you find a tarp img for the LG k51?

sCriptKittY1987 said:
Where did you find a tarp img for the LG k51?
Click to expand...
Click to collapse
tarp image????? just follow the tutorial.

I meant TWRP recovery . After you've unlocked the bootloader where did you get a custom recovery to flash for the LG k51. From what I saw on Team Wins website, there isn't one.

Bhanu8082 said:
simple , go to about phone and try to find build number,
after you find build number tap on it until it says you are in developer mode
after that head on to developer option (it may be inside about phone section or above about phone section) turn on the option which says allow oem unlock. then,
just reboot to recovery mode either by pressing volume up or volume down key with power button.
after you enter recovery connect usb cable and open command prompt in pc and make sure that lg device drivers are installed on your pc also make sure you have adb and fastboot installed.
ok, after all this type command
adb devices
if any thing shows us then you have successfully connected your device.
after it type
adb reboot bootloader
then your mobile should restart and show fastboot mode in screen
type command
fastboot oem unlock
and done your bootloader is unlocked.
Click to expand...
Click to collapse
When I typed fastboot oem unlock I get a reply saying <waiting for any device>

sCriptKittY1987 said:
When I typed fastboot oem unlock I get a reply saying <waiting for any device>
Click to expand...
Click to collapse
I doubt that's going to work, but let me know if it does. Carriers and manufacturers use a variety of sophisticated security schemes like requiring lengthy codes that only they can provide, etc to purposely make it very difficult to unlock bootloaders. Tmobile gave me a K51 for free. They apparently feel the have to pay for it by spying on me. I bought a moto g7 plus unlocked for $117 directly from Moto and put Lineage on it, no gapps Would love to use thie k51 though if anyone figures it out because it's more waterproof and bigger battery.

mgsgta3 said:
I can't find anything definitive about whether it's rootable or not
Click to expand...
Click to collapse
Whether device's bootloader is unlockable / device's Android is root-able or not you easily can find out by means of ABB:
Code:
adb shell "getprop ro.oem_unlock_supported"
If returned value is 1, then it's supported otherwise it's not.

sCriptKittY1987 said:
Where did you find a tarp img for the LG k51?
Click to expand...
Click to collapse
and let me guess my doofus luck im guessing no way to unlock it with out a P.C. like nuttin at all?

Absolutely no of the crap above works at all in any capacity especially sprint. Generic postings like hold volume down and power also doesn't work to go into fastboot so if you guys are following the advice of some of these guys don't because you'll drop more money on a new phone then you will unlocking it some variants verizon is one I think you have to call LG I know I spent 6 hrs on the phone with "tech support" aka "jokes with a screen to read from" to FINALLY get into touch with an engineer who told me the only way "NOW" to unlocked the bootloader is in his office which means it has to be depot to be unlocked which as of this moment lg is not doing that WILL change in the future that was 12/03/2020. Even running external adb with kali linux to hack it broke the bootloader and sends you into an infinite reboot loop

jwoegerbauer said:
Whether device's bootloader is unlockable / device's Android is root-able or not you easily can find out by means of ABB:
Code:
adb shell "getprop ro.oem_unlock_supported"
If returned value is 1, then it's supported otherwise it's not.
Click to expand...
Click to collapse
This returns no value on a locked bootloader because even with Dev. Opt. Enables its still read only until bootloader is unlocked this is verified on two carriers k51's sprint and att. However it is unlockable we haven't found it and/or LG has not added this service to their site which is where you will get the info needed for the unlocked.

Oh my. You know you need to do all this from a computer, right? Can't do it in an Android terminal because fastboot commands are only valid in a phone's bootloader environment. And if you didnt know that then rooting and all of the dangers that come with it just isnt for you. But yes, it's rootable. So here you go anyway.
Reboot the phone to download mode.
Install LG's K51 usb drivers, and install adb and fastboot, on your computer.
Open a command prompt and type: fastboot oem unlock
If it does anything other than pat you on the back and tell you it's proud of you and how well you follow instructions, then go back and follow the effing instructions.
Otherwise, type: fastboot reboot.
Download magisk manager.
Do the magisk manager.
Use the LG flash tool on your computer to flash what you just did when you did the magisk manager.
And presto, you're rooted. Or I successfully left out enough info and you dont know how to use Google, leaving your device still not rooted. And thank god for that.

Ive been learning from xda for some time now. Bricked a few phones in my learning curve and tonight i had my first success with my g7, and wrighting this on my new k51. This is my first post and I think that was pretty rude of you to say. This is supposed to be a place to learn, share knowledge, and help those who are less educated. Not look down on people and say crap like that. If he wants to learn even if it takes a couple bricked phones to do it, let him. Either give him the proper procedures or dont say nothing at all. How long did it take you? How many phones? Its taking me quit a while but i am finaly getting somewhere. Keep with it guy. Dont let this dude, or any one else for that matter, bring you down.

Kenwoodquality69 said:
Ive been learning from xda for some time now. Bricked a few phones in my learning curve and tonight i had my first success with my g7, and wrighting this on my new k51. This is my first post and I think that was pretty rude of you to say. This is supposed to be a place to learn, share knowledge, and help those who are less educated. Not look down on people and say crap like that. If he wants to learn even if it takes a couple bricked phones to do it, let him. Either give him the proper procedures or dont say nothing at all. How long did it take you? How many phones? Its taking me quit a while but i am finaly getting somewhere. Keep with it guy. Dont let this dude, or any one else for that matter, bring you down.
Click to expand...
Click to collapse
Yo Ken,
So your K51 rooted?
If so, maybe you could provide a step by step?

I haven't done this yet but is it verified working? I did a google search came across the method to do the unlocking but it showed it was a failed project?

TexasPride said:
I haven't done this yet but is it verified working? I did a google search came across the method to do the unlocking but it showed it was a failed project?
Click to expand...
Click to collapse
O lord i hope this isnt true

Moto One 5G Ace root guide

Prerequisites:
Your G 5G/One 5G has bootloader unlocked
LMSA installed
ADB is up to date
Your phone battery should be at least 60%
Your phone is wiped during bootloader unlock process
It's recommended to run LMSA rescue in order to have build version up to date, and you will get required boot.img for patching. Observe the ROM download process, and when it's close to finishing, go to the folder link on the bottom right, and go to ROM files. It's recommended to copy entire .zip file to download folder, and make sure you get boot.img and copy to the phone (set USB mode to file transfer) Download folder, and set USB mode to charging after it's done
Install Magisk Manager and update to the latest, and patch boot.img.
Change USB to file transfer and get patched_boot.img back to host computer
Open command, and go to ADB folder
Reboot the phone to bootloader
Code:
adb reboot bootloader
Code:
fastboot flash boot
Press spacebar once, and drag and drop patched boot to command window and press enter
Before doing restoration, make sure you do the following
1. Setup Magisk Manager and enable Magisk Hide and Systemless Hosts. You will be prompted to run "environmental setup" and the phone reboots during process. Check CTS and it should pass
2. Wipe Google Play Store
3. Reboot and install AdAway
4. Reboot again
5. Restore your phone
You should be able to install Netflix but you will lose L1
Update: you need these additional steps in Magisk to pass
1. Install latest riru in Magisk
2. Download and install Safetynet fix https://github.com/kdrag0n/safetynet-fix
Your phone will reboot twice

Apparently the us version is not able to be rooted as the bootloader cannot be unlocked . Device not supported for bootloader unlock according to the portal.

Can anyone confirm that this bootloader is locked and cannot be unlocked? Anyone else have the US unlocked version and went to the motorola portal and tried to unlock theirs with the same results?

swes013 said:
Apparently the us version is not able to be rooted as the bootloader cannot be unlocked . Device not supported for bootloader unlock according to the portal.
Click to expand...
Click to collapse
You can not trust the official supported unlock list, it's never been complete.
You can check if the device's CID is eligible for unlocking, and if the OEM unlocking is greyed out you cannot.
If the CID is good and OEM can be toggled, you need to request the unlock code to be sure.

sd_shadow said:
You can not trust the official supported unlock list, it's never been complete.
You can check if the device's CID is eligible for unlocking, and if the OEM unlocking is greyed out you cannot.
If the CID is good and OEM can be toggled, you need to request the unlock code to be sure.
Click to expand...
Click to collapse
Well I have enabled developer settings. In that I have enabled usb debugging as well as oem unlocking. I tried to unlock the bootloader. No joy. I talked to a moto rep who said in a chat it was not available for unlock at this time according to the list. The usual B.S.

swes013 said:
Well I have enabled developer settings. In that I have enabled usb debugging as well as oem unlocking. I tried to unlock the bootloader. No joy. I talked to a moto rep who said in a chat it was not available for unlock at this time according to the list. The usual B.S.
Click to expand...
Click to collapse
Correction Folks I got it. Apparently I had bad format. Sorry.

swes013 said:
Apparently the us version is not able to be rooted as the bootloader cannot be unlocked . Device not supported for bootloader unlock according to the portal.
Click to expand...
Click to collapse
Mine is US unlocked version and rooted

Okay so I have been down the road and back again folks. I now have my Moto one 5g ace fully bootloader unlocked as well as Magisk root installed and my root explorer and titanium backup are being granted Super user permissions. Yes Finally. Now If anyone and I mean anyone needs help or has a issue please message me. i have created a list of fastboot commands in order specific to the Moto one ace 5g that WILL RESTORE THE FACTORY IMAGES IN PROPER ORDER FOR THE ROM. FORGIVE ME i AM STILL NEEDING TO MAKE A FLASH ALL.BAT FOR THIS. HOWEVER, IT WORKS FLAWLESSLY IF DONE INDIVIDUALLY TO RESTORE YOUR ONE ACE 5G BACK TO STOCK. So I am a very happy One ace 5g owner with unlocked bootloader and, Root privilege's. Now awaiting some further development for the Recovery image and some custom Roms from some Developers smarter than Me. Ha Ha Ha. So for now I wait. I will update if i get the Flash all.bat file accomplished.
Thanks to XDA for their years of instruction and direction.

swes013 said:
Okay so I have been down the road and back again folks. I now have my Moto one 5g ace fully bootloader unlocked as well as Magisk root installed and my root explorer and titanium backup are being granted Super user permissions. Yes Finally. Now If anyone and I mean anyone needs help or has a issue please message me. i have created a list of fastboot commands in order specific to the Moto one ace 5g that WILL RESTORE THE FACTORY IMAGES IN PROPER ORDER FOR THE ROM. FORGIVE ME i AM STILL NEEDING TO MAKE A FLASH ALL.BAT FOR THIS. HOWEVER, IT WORKS FLAWLESSLY IF DONE INDIVIDUALLY TO RESTORE YOUR ONE ACE 5G BACK TO STOCK. So I am a very happy One ace 5g owner with unlocked bootloader and, Root privilege's. Now awaiting some further development for the Recovery image and some custom Roms from some Developers smarter than Me. Ha Ha Ha. So for now I wait. I will update if i get the Flash all.bat file accomplished.
Thanks to XDA for their years of instruction and direction.
Click to expand...
Click to collapse
That's why you have original ROM or boot in order to revert.
Should everything get messed up, you can fully restore with LMSA rescue (data will be wiped during process)

mingkee said:
That's why you have original ROM or boot in order to revert.
Should everything get messed up, you can fully restore with LMSA rescue (data will be wiped during process)
Click to expand...
Click to collapse
FYI I DID NOT USE LMSA TO RESTORE I USED FASTBOOT. HENCÈ THE POST THAT SAID IF ANYONE WANTED HELP OR HIT A ROADBLOCK OR SNAGS PER SAY TO MESSAGE ME. THANKS. I COULD NOT USE LMSA AFTER ATTEMPTING THE PROCESS YOU STATED. WHEN I DID YOURS EXACTLY I GOT A BOOT UP WITH A DISABLED TOUCHSCREEN. HERE TO HELP. THANKS AGAIN

swes013 said:
Okay so I have been down the road and back again folks. I now have my Moto one 5g ace fully bootloader unlocked as well as Magisk root installed and my root explorer and titanium backup are being granted Super user permissions. Yes Finally. Now If anyone and I mean anyone needs help or has a issue please message me. i have created a list of fastboot commands in order specific to the Moto one ace 5g that WILL RESTORE THE FACTORY IMAGES IN PROPER ORDER FOR THE ROM. FORGIVE ME i AM STILL NEEDING TO MAKE A FLASH ALL.BAT FOR THIS. HOWEVER, IT WORKS FLAWLESSLY IF DONE INDIVIDUALLY TO RESTORE YOUR ONE ACE 5G BACK TO STOCK. So I am a very happy One ace 5g owner with unlocked bootloader and, Root privilege's. Now awaiting some further development for the Recovery image and some custom Roms from some Developers smarter than Me. Ha Ha Ha. So for now I wait. I will update if i get the Flash all.bat file accomplished.
Thanks to XDA for their years of instruction and direction.
Click to expand...
Click to collapse
Could you please post the CA combo data for your variant?

Went to try out this phone, had no idea would be able to root it, was just looking for a basic phone with a decent display and battery. Thanks for the guide @mingkee! My first device borked on the LMSA update, it broke the wifi on it. Returned for a new phone, unlocked the BL and this one working just fine. Nice and rooted and no more ads.

What's the CA combo data exactly.?

swes013 said:
What's the CA combo data exactly.?
Click to expand...
Click to collapse
Its the carrier aggregation configuration for the different bands supported by the hardware and ths software of the phone. It usually differs by region for the same phone model.
The following site is a good reference point for this information.
https://cacombos.com/

swes013 said:
What's the CA combo data exactly.?
Click to expand...
Click to collapse
Its the carrier aggregation configuration for the different bands supported by the hardware and ths software of the phone. It usually differs by region for the same phone model.
The following site is a good reference point for this information.
https://cacombos.com/

Reporting that bootloader unlock works PERFECTLY on the MetroPCS variant. But don't format the string yourself, use the Moto Data Scrub Tool they have on the unlock page. If you do it yourself it will come up error.

swes013 said:
Okay so I have been down the road and back again folks. I now have my Moto one 5g ace fully bootloader unlocked as well as Magisk root installed and my root explorer and titanium backup are being granted Super user permissions. Yes Finally. Now If anyone and I mean anyone needs help or has a issue please message me. i have created a list of fastboot commands in order specific to the Moto one ace 5g that WILL RESTORE THE FACTORY IMAGES IN PROPER ORDER FOR THE ROM. FORGIVE ME i AM STILL NEEDING TO MAKE A FLASH ALL.BAT FOR THIS. HOWEVER, IT WORKS FLAWLESSLY IF DONE INDIVIDUALLY TO RESTORE YOUR ONE ACE 5G BACK TO STOCK. So I am a very happy One ace 5g owner with unlocked bootloader and, Root privilege's. Now awaiting some further development for the Recovery image and some custom Roms from some Developers smarter than Me. Ha Ha Ha. So for now I wait. I will update if i get the Flash all.bat file accomplished.
Thanks to XDA for their years of instruction and direction.
Click to expand...
Click to collapse
Please Post the Commands for the Restore from Factory image as they are slightly different than the G series prior to 2019. Thanks.

swes013 said:
FYI I DID NOT USE LMSA TO RESTORE I USED FASTBOOT. HENCÈ THE POST THAT SAID IF ANYONE WANTED HELP OR HIT A ROADBLOCK OR SNAGS PER SAY TO MESSAGE ME. THANKS. I COULD NOT USE LMSA AFTER ATTEMPTING THE PROCESS YOU STATED. WHEN I DID YOURS EXACTLY I GOT A BOOT UP WITH A DISABLED TOUCHSCREEN. HERE TO HELP. THANKS AGAIN
Click to expand...
Click to collapse
My touchscreen is indeed fronzen after boot.img flash. Please again, post the commands. It is much appreciated.

Articul8Madness said:
Please Post the Commands for the Restore from Factory image as they are slightly different than the G series prior to 2019. Thanks.
Click to expand...
Click to collapse
The flash commands are included in the flashfile.xml, which should always be referred to because the commands do change from time to time.
I suggest using the online flash file convertor.
Then copy the commands to a text file, save, rename the file extension to .bat
done you have your own flashall.bat
only exception is if your device uses the new fastbootd mode.

sd_shadow said:
The flash commands are included in the flashfile.xml, which should always be referred to because the commands do change from time to time.
I suggest using the online flash file convertor.
Then copy the commands to a text file, save, rename the file extension to .bat
done you have your own flashall.bat
only exception is if your device uses the new fastbootd mode.
Click to expand...
Click to collapse
Well I definitely have an issue since I can't use the touchscreen I can't boot into fastboot right now or reboot the phone manually.
Update for the challenged: Hold the power button with the up volume rocker for forced reboot.

Question TMobile OP9 bootloader unlock process stuck

Hello,
I am trying to convert Tmobile OP9 to Global version and I am stuck at a basic step of getting the oem unlock code when trying to unlock the bootloader.
Details:
1. got my network unlocked from mobbdeep couple of weeks back.
2. Under Settings > "Network Unlock" status shows as unlocked
3. Installed the latest SDK as I am following the guide here to get the bootloader unlocked. When I boot in fastmode and run the oem command it stays at "waiting for device" and returns nothing.
Code:
fastboot oem get_unlock_code
When I run this, device list shows empty
Code:
adb devices
- Enabled USB debugging and stay awake options is checked from what I read on few posts
- When I restart the phone normally and then run "adb devices" it shows my phone listed
- Working on windows machine
What am I doing wrong here ?
TIA !!
PS: attached image shows the device state as Locked

If your phone is SIM unlocked, follow the instructions to convert from T-Mo to global.
Then you'll have the normal OEM unlock in dev options. Then you can just do the fastboot oem unlock and call it good.
Much easier and you don't have to deal with the token. It worked well for me.

I have the global version, not TMobile, so this might not apply
But I had a similar issue with fastboot not recognizing my device, the solution is disabling driver signing in windows and manually updating the driver in device manager
Check the "root OnePlus9" thread.. on page 8 at the bottom there's a guide on how to do it

Superguy said:
If your phone is SIM unlocked, follow the instructions to convert from T-Mo to global.
Then you'll have the normal OEM unlock in dev options. Then you can just do the fastboot oem unlock and call it good.
Much easier and you don't have to deal with the token. It worked well for me.
Click to expand...
Click to collapse
Thanks for your response.
I tried that earlier assuming the same but it asked me to first flash the unlock token for which I am following the steps
I was however able to get the device listed after manually uninstalling/installing adb drivers

avid_droid said:
Check in device manager. If you have the yellow triangle on your phone in device manager just download android composite driver and update it through device manager/browse computer/ select unzipped folder and click OK.
Might be the issue
Click to expand...
Click to collapse
That was indeed the issue. I manually uninstalled and installed the drivers which helped and I can now see the device listed and also got the oem unlock code successfully.
I have submitted the form with Tmobile for the unlock token, hopefully that should do it.
Thanks !

This thread was helpful as well. Thanks !

cass89 said:
I have the global version, not TMobile, so this might not apply
But I had a similar issue with fastboot not recognizing my device, the solution is disabling driver signing in windows and manually updating the driver in device manager
Check the "root OnePlus9" thread.. on page 8 at the bottom there's a guide on how to do it
Click to expand...
Click to collapse
This thread was helpful as well. Thanks !

avid_droid said:
If going for root and conversion,don't forget to use partitions manager to back up persist.img and modemst1,modemst2.
Can't stress that enough. This is my second oneplus device messed up in a 3 week time period
Click to expand...
Click to collapse
I will definitely.
I remember doing the same process for OP6T. Some users had mentioned about the issues surfacing and that helped o go back to stock
That reminds, like 6T are there any known issues post converting ?
I remember play services weren't functioning fine as well as there was no google pay. My corporate apps also didnt install due to missing security certificates.
Same applies for OP9 as well ?

FRNK8 said:
I will definitely.
I remember doing the same process for OP6T. Some users had mentioned about the issues surfacing and that helped o go back to stock
That reminds, like 6T are there any known issues post converting ?
I remember play services weren't functioning fine as well as there was no google pay. My corporate apps also didnt install due to missing security certificates.
Same applies for OP9 as well ?
Click to expand...
Click to collapse
You might want to backup your modem partition just in case you want to try the T-Mobile modem. I've heard reports the the AA modem works great, and also that the AA modem sucks, so YMMV

craznazn said:
You might want to backup your modem partition just in case you want to try the T-Mobile modem. I've heard reports the the AA modem works great, and also that the AA modem sucks, so YMMV
Click to expand...
Click to collapse
Hey thanks for the heads up. I will
Would infact first go through the conversion steps to go back to Tmo just incase things go south.

avid_droid said:
If going for root and conversion,don't forget to use partitions manager to back up persist.img and modemst1,modemst2.
Can't stress that enough. This is my second oneplus device messed up in a 3 week time period
Click to expand...
Click to collapse
craznazn said:
You might want to backup your modem partition just in case you want to try the T-Mobile modem. I've heard reports the the AA modem works great, and also that the AA modem sucks, so YMMV
Click to expand...
Click to collapse
Following the guide here, I just performed the bootloader unlock successfully. Per your suggestion, I want to backup the modem files before I proceed any further.
I cant seem to recollect how do I backup the modem files when I did the same conversion for OP6T. Can you please guide me here before I proceed with the next steps.
I tried installing the partitions backup but it wont allow me without root. I vaguely remember that I hadn't rooted my device the last time while backing up these files or is root needed ?
TIA !

You need to root. Rooting is fine and won't affect your modem. While you are there, back up persist, modemst1, modemst2, modem_a, and modem_b. _a and _b should be different versions and you can pick and choose which one you might want to use (or stick with AA)

craznazn said:
You need to root. Rooting is fine and won't affect your modem. While you are there, back up persist, modemst1, modemst2, modem_a, and modem_b. _a and _b should be different versions and you can pick and choose which one you might want to use (or stick with AA)
Click to expand...
Click to collapse
Can you help me with the steps to root ? Just want to be careful while doing so.
I saw some posts but that was related to the Tmobile OP9Pro(in my case its its Tmo Op9). The boot images were different so I didnt try to play around.
Thanks !

Just try to fastboot boot a magisk patched img and see if it works.
Try https://forum.xda-developers.com/t/root-oneplus-9.4253651/
Don't flash anything, just go to fastboot
Code:
fastboot boot patched_boot.img

craznazn said:
Just try to fastboot boot a magisk patched img and see if it works.
Try https://forum.xda-developers.com/t/root-oneplus-9.4253651/
Don't flash anything, just go to fastboot
Code:
fastboot boot patched_boot.img
Click to expand...
Click to collapse
Okay did this step.
Downloaded an copied stock image and the boot_patched image provided on the link and copied to my phones internal storage
Also as next step said, rebooted the phone
- went to Magisk app > install > selected boot_patched.img from internal storage
- phone restarted
- When I open the partitions backup app it still shows "device is not rooted" warning
What step did I miss ?

FRNK8 said:
That was indeed the issue. I manually uninstalled and installed the drivers which helped and I can now see the device listed and also got the oem unlock code successfully.
I have submitted the form with Tmobile for the unlock token, hopefully that should do it.
Thanks !
Click to expand...
Click to collapse
do you have a link for the driver I'm having the same problem

How To Guide WARNING: Read BEFORE Locking Bootloader

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.