Develop Bugs

Moto z play (xt1635-03) transformation 64 GB ROM + 3GB RAM

Dear all
There are so many people looking for exactly samething that iam looking for but unfortunately there is not any proper tutorial available.
Could you confirm if there is anyway to install any other ROM on chinese moto z play ? i don't mind if i have to install each OTA manually.
If so could you please guide step by step guide how to perform this?
If there so no any ROM that can work with chinese variant is there any custom ROM that would and support Moto Mods?

You can read my thread: https://forum.xda-developers.com/moto-z-play/help/problem-reteu-firmwares-chinese-t3619235
Briefly:
1) If you unlock your bootloader you will be able to flash full image of any firmware throug fastboot (with ordinary instruction)
2) OTA at the moment can't be installed even manually due to different device name (addison_retcn vs addison)
I'm looking through different ways to fix device name with no luck at the moment (but I am sure it is possible)

freeman_g said:
You can read my thread: https://forum.xda-developers.com/moto-z-play/help/problem-reteu-firmwares-chinese-t3619235
Briefly:
1) If you unlock your bootloader you will be able to flash full image of any firmware throug fastboot (with ordinary instruction)
2) OTA at the moment can't be installed even manually due to different device name (addison_retcn vs addison)
I'm looking through different ways to fix device name with no luck at the moment (but I am sure it is possible)
Click to expand...
Click to collapse
Did you try editing build.prop?

jameelmemon said:
Did you try editing build.prop?
Click to expand...
Click to collapse
I see that you has not even tried to look through my thread (link was provided in previous post). Suggest to do that (espesially the very end) before further questions / discussion

I have gone through almost all threads including your befiore posting or asking you that question
you are referring to
2) target script is probably /device/company_name/device_name/init.device_name.usb.rc
3) there is a string in that script: write /sys/class/android_usb/android0/iProduct ${ro.product.model}
aactualy {ro.product.model} is variable in build.prop so that script (/device/company_name/device_name/init.device_name.usb.rc) from build.prop

Actually, not there. I have pushed build.prop with adb and has not found any signs of "addison_retcn" there
Hovewer AIDA64 (as well as adb once you try to sideload OTA) will display "addison_retcn" so it is somewhere else
I do not thing that script take the name from build.prop as, for example, it also obtains serial number with the same way and it is the first recommendation on recovering serial (in case it is lost during the some flashing procedure) to manually set it in that script

Finally i manage to install 7.1.1
My phone is addison after installing RETAIL version (7.0)
I installed RETAIL version then downloaded ota then installed 7.1.1 OTA from this thread https://forum.xda-developers.com/moto-z-play/how-to/official-android-7-1-1-download-how-to-t3616352
phone should not be locked/encrypted or protected at least i bricked it and it was not booting up.
Now need to change two things those are in bootloader (SKU and ro.carrier) fastboot getvar all

So just install retail version and sideload OTA through ADB?
I see that my phone is encrypted, shall I decrypt it first?
In any case any news on how you managed to boot 7.1.1 are appreciated

Just found ro.carrier comes from kernel and will be taken from kernel each time devices boots up. so we need someone to customize the kernel and add retru or retus to kernel as ro.carrier.
sku i can not change as i am getting error of command is not allowed
can anyone help regarding this?

So what is the result? You have managed to sideload 7.1.1 аnd it is not booting?
Or everything works fine and you tried to change SKU/channel for further updates?

freeman_g said:
Actually, not there. I have pushed build.prop with adb and has not found any signs of "addison_retcn" there
Hovewer AIDA64 (as well as adb once you try to sideload OTA) will display "addison_retcn" so it is somewhere else
I do not thing that script take the name from build.prop as, for example, it also obtains serial number with the same way and it is the first recommendation on recovering serial (in case it is lost during the some flashing procedure) to manually set it in that script
Click to expand...
Click to collapse
freeman_g said:
So just install retail version and sideload OTA through ADB?
I see that my phone is encrypted, shall I decrypt it first?
In any case any news on how you managed to boot 7.1.1 are appreciated
Click to expand...
Click to collapse
Just install fresh retail version then sideload first ota via adb then boot your phone do not complete setup.
then install 7.1.1 then do factory restore then you are good to go
and it have so many great features you can view them here specially camera app

freeman_g said:
So what is the result? You have managed to sideload 7.1.1 аnd it is not booting?
Or everything works fine and you tried to change SKU/channel for further updates?
Click to expand...
Click to collapse
Initally it didn't work and stuck on bootloader unlock warning but later it worked perfect and iam using 7.1.1 and now trying to figure out how we can change sku and channel to get official OTA.
Sku (XT1635-03) is in bootloader but i can't write is with Fastboot, channel (retcn) is in kernel.

Lucky you I still have the same problem
Yesterday I tried to start with flashing stock retail 7.0 (the link you have provided earlier) but due to fact I had already flashed image with April security patch I didn't manage to downgrade bootloader and gpt (security downgrade issue)
Despite this fact phone boots but small OTA with April security patch did not agree to flash for the same reason: wrong name "addison_retcn"
So I believe the problem is in bootliader and I will probably manage to fix it only with full 7.1.1 retail image.

Glad to see you guys are making some progress. I'll try flashing the retail version on my Chinese Z Play. I'm currently on Epsilon rom (stock rooted 7.0) with January patch. Can I flash retail and then the ota?

I woulf suggest the following:
1) At your current firmware install Aida64 and check if you have addison or addison_cn product name in System section. If you see only addison - then you may install retail firmware and OTAs
2) If you still have addison_cn here then try to install retail firmware provided above (bootloader can be upgraded) and then check product name in Aida64 again. If it changed to addison - you can sideload OTAs. If still addison_cn - then you can't

Thanks @freeman_g
Here is a screenshot of AIDA64 on my device: https://imgur.com/gallery/Or2JF
I guess I should be good to go, right?

Yes, should work
What I can't understand why I still with addison_retcn. Probably, will have to wait for full 7.1.1 retail image

Sorry for the noobie question, but how did you guys with XT1635-03 flash the XT1635-02 firmware? Did you use this script? Did you flash the full rom, including partition, fsg, and modem, no restrictions? I bought my device at Banggood. I know it will come with a shop rom and I would like to install the stock firmware. I want to be prepared when it arrives. Don't want to take the risk of brick it and would like to leave the custom roms for later.

Ok, I have finally found why some people (and myself) have problems with 7.1.1 OTA on xt1635-03
As I mentioned before, OTA just refuses to install mentioning wrong device name (addison_retcn vs addison)
The problem is standard instuction for flashing any firmware with fastboot missing these lines:
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
After flashing these files I saw correct "addison" name in Aida64 and managed to install 7.1.1 OTA on my XT1635-03
People who use RSD Lite did not have such problem as this program use xml file contained both commands (oem and dsp)
It is better to have unlocked bootloader as at first attempt OTA was flashed with some mistake and the phone did not boot. After restoring full image (7.0) with fastboot I managed to sucessfully sideload OTA and now have 7.1.1 on my Chineese device.
Hope this helps

freeman_g said:
Ok, I have finally found why some people (and myself) have problems with 7.1.1 OTA on xt1635-03
As I mentioned before, OTA just refuses to install mentioning wrong device name (addison_retcn vs addison)
The problem is standard instuction for flashing any firmware with fastboot missing these lines:
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
After flashing these files I saw correct "addison" name in Aida64 and managed to install 7.1.1 OTA on my XT1635-03
People who use RSD Lite did not have such problem as this program use xml file contained both commands (oem and dsp)
It is better to have unlocked bootloader as at first attempt OTA was flashed with some mistake and the phone did not boot. After restoring full image (7.0) with fastboot I managed to sucessfully sideload OTA and now have 7.1.1 on my Chineese device.
Hope this helps
Click to expand...
Click to collapse
Awesome, many thanks for sharing. Does this mean you'll receive future OTAs?

rom update WW_ZS660KL_16.0622.1907.33

rom update WW_ZS660KL_16.0622.1907.33
Remember, You're on your own from here. Follow the steps carefully, and patiently. If something breaks or blows up - You're on your own.
- This guide only applies to ASUS ROG II (SKU : ZS660KL)
* Ensure to log out from your Google Account Signed in on the device. If you forget this step, Later on, you'll be locked at first boot due to Google's FRP.
* Do not attempt this on x86/32bit operating systems. Some users have reported bricking issues due to RAW flasher not supporting 32bit Operating Systems.
* Download the WW (International ROM) file at the end of this post (This is if you're coming from CN Rom to International Rom)
* Extract all contents as is to your C: Drive
* (Refer to attached image for the file list)
* Connect the Phone to the PC in Fastboot Mode - Using the Black Type-C Port on the Side of the Device (Not the Charging port on the bottom)
https://drive.google.com/file/d/1eS8in5E_5KboRFa6mZZvkw0VtZoACPmO/view?fbclid=IwAR0YStZ160ny5bzMS_JwyCICvYSx1w63HtShUJHnvUCjdKu31vSEBF-QPc8[/URL]

Alternative download link:
For general user: Mediafire
For China user: BaiduYun(Pass: s3cy)

Is this same ways to change from CN to WW before? Just klik flash.cmd? ( forgot the name )

andixxx81 said:
Is this same ways to change from CN to WW before? Just klik flash.cmd? ( forgot the name )
Click to expand...
Click to collapse
yep.
Just run the flashall_AFT.cmd

KanadeTi said:
yep.
Just run the flashall_AFT.cmd
Click to expand...
Click to collapse
Ok sir..thx for update.
But still no update Via OTA

andixxx81 said:
Ok sir..thx for update.
But still no update Via OTA
Click to expand...
Click to collapse
Refer to this thread: https://forum.xda-developers.com/rog-phone-2/how-to/ota-update-converted-to-ww-t3967665

lufermax said:
rom update WW_ZS660KL_16.0622.1907.33
Remember, You're on your own from here. Follow the steps carefully, and patiently. If something breaks or blows up - You're on your own.
- This guide only applies to ASUS ROG II (SKU : ZS660KL)
* Ensure to log out from your Google Account Signed in on the device. If you forget this step, Later on, you'll be locked at first boot due to Google's FRP.
* Do not attempt this on x86/32bit operating systems. Some users have reported bricking issues due to RAW flasher not supporting 32bit Operating Systems.
* Download the WW (International ROM) file at the end of this post (This is if you're coming from CN Rom to International Rom)
* Extract all contents as is to your C: Drive
* (Refer to attached image for the file list)
* Connect the Phone to the PC in Fastboot Mode - Using the Black Type-C Port on the Side of the Device (Not the Charging port on the bottom)
https://drive.google.com/file/d/1eS8in5E_5KboRFa6mZZvkw0VtZoACPmO/view?fbclid=IwAR0YStZ160ny5bzMS_JwyCICvYSx1w63HtShUJHnvUCjdKu31vSEBF-QPc8[/URL]
Click to expand...
Click to collapse
Does the patched root image work on this update?

Any idea what changes there are? Is it worth wiping?

lufermax said:
rom update WW_ZS660KL_16.0622.1907.33
Remember, You're on your own from here. Follow the steps carefully, and patiently. If something breaks or blows up - You're on your own.
- This guide only applies to ASUS ROG II (SKU : ZS660KL)
* Ensure to log out from your Google Account Signed in on the device. If you forget this step, Later on, you'll be locked at first boot due to Google's FRP.
* Do not attempt this on x86/32bit operating systems. Some users have reported bricking issues due to RAW flasher not supporting 32bit Operating Systems.
* Download the WW (International ROM) file at the end of this post (This is if you're coming from CN Rom to International Rom)
* Extract all contents as is to your C: Drive
* (Refer to attached image for the file list)
* Connect the Phone to the PC in Fastboot Mode - Using the Black Type-C Port on the Side of the Device (Not the Charging port on the bottom)
https://drive.google.com/file/d/1eS8in5E_5KboRFa6mZZvkw0VtZoACPmO/view?fbclid=IwAR0YStZ160ny5bzMS_JwyCICvYSx1w63HtShUJHnvUCjdKu31vSEBF-QPc8[/URL]
Click to expand...
Click to collapse
xxBrun0xx said:
Any idea what changes there are? Is it worth wiping?
Click to expand...
Click to collapse
Version WW-16.0622.1907.33
2019/09/092.2 GBytes
ZS660KL software Image:WW_V16.0622.1907.33, This software is only available to customers of WW version to update and use the
improved project:
1. Add three ROG dynamic wallpapers
2. Bright core evolution theme supports dynamic tablecloth effect
3. Correction can not open Wi -Fi hotspot problem

So I put the full WW update zip on my phone, phone said "update detected, tap to update". I click the notification, and get "update failed" right away. Phone is a Tencent edition converted to WW when I bought it, so bootloader is still locked. Any ideas how to update?

xxBrun0xx said:
So I put the full WW update zip on my phone, phone said "update detected, tap to update". I click the notification, and get "update failed" right away. Phone is a Tencent edition converted to WW when I bought it, so bootloader is still locked. Any ideas how to update?
Click to expand...
Click to collapse
It was mentioned in one of the other threads, the Tencent Version still identifies itself as needing the CN rom therefore we can't get OTA updates.
With that said, I think you have to flash each raw update via PC.
Someone correct me if I'm wrong.

mzahiri said:
It was mentioned in one of the other threads, the Tencent Version still identifies itself as needing the CN rom therefore we can't get OTA updates.
With that said, I think you have to flash each raw update via PC.
Someone correct me if I'm wrong.
Click to expand...
Click to collapse
Doesn't that wipe the phone?

xxBrun0xx said:
Doesn't that wipe the phone?
Click to expand...
Click to collapse
I think it does.
Sadly I don't think this phone will have enough development to warrant scripted methods of updating the OS.
If someone ever figures out how to change the device fingerprint to match a WW rom, then we can get the WW OTA.

No it doesn't wipe I just updated mine using the raw over the initial WW rom. We'll have to manually flash ourselves using the new raw files each time to update

Do we need to re-lock the bootloader after flashing?

innosquall said:
Do we need to re-lock the bootloader after flashing?
Click to expand...
Click to collapse
Locked or unlocked it doesn't matter, however root doesn't work yet for the update

xxBrun0xx said:
So I put the full WW update zip on my phone, phone said "update detected, tap to update". I click the notification, and get "update failed" right away. Phone is a Tencent edition converted to WW when I bought it, so bootloader is still locked. Any ideas how to update?
Click to expand...
Click to collapse
https://forum.xda-developers.com/rog-phone-2/how-to/guide-convert-cn-to-ww-rom-26-08-t3961042

zed011 said:
No it doesn't wipe I just updated mine using the raw over the initial WW rom. We'll have to manually flash ourselves using the new raw files each time to update
Click to expand...
Click to collapse
I wish I had seen this thread before wiping my phone to flash latest CN to test OTA, then realising the CN ROM is a pile of steaming horse crap :laugh:

I found full list of changes in this update
-Added three ROG live wallpapers
-Light Luminous Core theme supports live wallpaper effect
-Fixed the issue where occasionally can not turn on WiFi hotspot
-ROG Lighting Armor Case supports "Activate the Force" sound effects, such as alarm, ringtone, notification sound etc.
-Added Netflix shortcut
-Improved the preview lag issue in camera portrait mode
-Optimized camera parameters
-Optimized the flow of switching to the classic Pixel-like system style in setup wizard
-Optimized edge touch suppression effect
-Fixed AirTrigger's force level adjustment issue
-Fixed the issue where video or system sound occasionally cannot be played
-Fixed the occasional system restart issue in "MLTD (ミリシタ) "
-Fixed the issue where the phone screen app will appear quickly on the external screen when launching/leaving a portrait-only app on TwinView Dock II

zed011 said:
No it doesn't wipe I just updated mine using the raw over the initial WW rom. We'll have to manually flash ourselves using the new raw files each time to update
Click to expand...
Click to collapse
Do we actually need to log out if our Google account before attempting? Thanks!

Question Pixel 6 Pro Flash able Firmwares

Can someone send me.a direct link to all Firmwares for the pixel 6 pro that I can flash stock Firmwares that is. I need the official Firmwares for all countries

Is this what you are looking for
https://developers.google.com/android/ota

Or the full firmwares https://developers.google.com/android/images, and the December ones that they removed from there Alternate links to December full factory images for .017, .016.A1 & A4, and OTAs for .017 & .016.A1 available.

I'm december FW without bug. If i want to clean flash the next FW what i must to do.
Can i wipe system in recovery or i must use adb/fastboot command ?

Vincent_40 said:
I'm december FW without bug. If i want to clean flash the next FW what i must to do.
Can i wipe system in recovery or i must use adb/fastboot command ?
Click to expand...
Click to collapse
You'll be able to use Official Google Android Flash Tool or the full factory image zip which as always would be available at Pixel 6 Pro Factory Images. Either will fully wipe your device. I don't have firsthand experience with Official Google Android Flash Tool so I don't know if it wipes by default but I know it can or has an option to if it's not default. The full factory images at Pixel 6 Pro Factory Images, without modification, always fully wipes the phone. Make sure and update SDK Platform Tools every month (sometimes earlier version Platform Tools doesn't work correctly and update the Google USB Driver if you're using Windows.

Ok thx i'll try to clean flash with next update with flash tool.
Hope Twrp will be released soon.

Vincent_40 said:
Hope Twrp will be released soon.
Click to expand...
Click to collapse
I wouldn't hold my breath or take any bets on that. So far without TWRP hasn't held anything back.

roirraW edor ehT said:
I wouldn't hold my breath or take any bets on that. So far without TWRP hasn't held anything back.
Click to expand...
Click to collapse
Yeah, about a month or two ago bigbiff said he was working on TWRP for Android 12 in general, but it would be a while. Honestly, haven't used it since the Nexus days. Really haven't missed it at all and probably wouldn't use it even when/if it does come out.

I'm on january security patch and I'd unlock the bL without disable the DM-Verity verification.
Can i root with last Magisk canary directly or do i need to disable DM-Verity ?
Last point, my play protect is uncertified, but it's not important

Vincent_40 said:
I'm on january security patch and I'd unlock the bL without disable the DM-Verity verification.
Can i root with last Magisk canary directly or do i need to disable DM-Verity ?
Last point, my play protect is uncertified, but it's not important
Click to expand...
Click to collapse
Yes, you can root with Canary Magisk 23016 without disabling verity & verification.

Ok i'll try
Thx for your reply

Question Steps to root

I have a WW version of ROG Phone 6. I have had it since mid-July.
Previously, I had ROG 2 but it died on me unexpectedly and I switched to Pixel 6, which was very underwhelming. I pre-ordered ROG 6 as soon as it became available.
I have not seen a concise guide to rooting ROG 6. I think it should be the same as ROG 2 but just in case, I read guide to rooting ROG 5.
Are the steps to rooting ROG 6 the same as ROG 5?
Asus ROG phone 5: unlock bootloader and root guide
Asus rog phone 5 guide note: you follow this guide on your own responsibility. also You should note that unlocking via the official Asus app will void warranty and blacklist the device for future otas. bootloader unlock: ! note that unlocking...
forum.xda-developers.com
Thank you!

I sure hope so. . . I cant find much material online but I'm going to try to just run this tool from asus https://rog.asus.com/phones/rog-phone-6-model/helpdesk_download/ and then flash magisk via recovery.
Sorry extract boot.img move it to phone, patch it with magisk and then run
Code:
fastboot flash boot magisk_patched.img
and that should do it. Although you may want/need to flash the official files first by running the flashall_AFT.cmd file.
Found this all on https://forum.xda-developers.com/t/...e-6-can-be-used-for-cn-ww-converting.4474383/ and https://forum.xda-developers.com/t/...-guide-you-should-read.4474241/#post-87255303

It worked for me without even needing to flash the full firmware (you'd have to, to switch versions though) let me know if you need help. the guides I linked might be overkill.
Just
1.) Fully update on phone.
2.) Install apk to unlock bootloader from my first link
3.) reboot to fastboot and run the command I gave above. (after extracting the boot.img from payload.bin and patching it, although the last link includes one prepatched that may work)

leathan said:
It worked for me without even needing to flash the full firmware (you'd have to, to switch versions though) let me know if you need help. the guides I linked might be overkill.
Just
1.) Fully update on phone.
2.) Install apk to unlock bootloader from my first link
3.) reboot to fastboot and run the command I gave above. (after extracting the boot.img from payload.bin and patching it, although the last link includes one prepatched that may work)
Click to expand...
Click to collapse
Thank you for replying.
I read the guide about "flashall_AFT". I think the guy needed to do that because he was converting CN to WW. So, I think you are right in that the guide might be overkill since my phone is WW.
Thank you for taking time to outline the steps. The steps you outlined seems the same as for ROG 5. Glad to know that ASUS is consistent on this.
ROG 6 is the first phone that I ever pre-ordered. Usually, I buy phones when there are already guides on rooting. So, I am a bit nervous on rooting ROG 6 since there is not dedicated and concise guide yet.

ausaras said:
Thank you for replying.
I read the guide about "flashall_AFT". I think the guy needed to do that because he was converting CN to WW. So, I think you are right in that the guide might be overkill since my phone is WW.
Thank you for taking time to outline the steps. The steps you outlined seems the same as for ROG 5. Glad to know that ASUS is consistent on this.
ROG 6 is the first phone that I ever pre-ordered. Usually, I buy phones when there are already guides on rooting. So, I am a bit nervous on rooting ROG 6 since there is not dedicated and concise guide yet.
Click to expand...
Click to collapse
Your good, just proceed as normal, I already got LSPosed, Zygisk+safteynet and all the goodies running. I see why you preordered this thing, its an absolute beast!! I am in love with it.
I wasn't even aware these phones existed but when I saw them and saw ASUS releases bootloader unlock publicly I instantly bought one as in general that's the main thing needed for rooting.
If you need any help It only took me about 15 minutes to root everything without using the guides at all as like you said it was pretty standard process. Like I said I extracted and patched the boot myself but just to potentially save time as I'm almost positive the patched image in the last link will work, and if it does not you can just reflash the one from the OTA.zip.
Good luck! (if you decide to root it will work fine)

leathan said:
Your good, just proceed as normal, I already got LSPosed, Zygisk+safteynet and all the goodies running. I see why you preordered this thing, its an absolute beast!! I am in love with it.
I wasn't even aware these phones existed but when I saw them and saw ASUS releases bootloader unlock publicly I instantly bought one as in general that's the main thing needed for rooting.
If you need any help It only took me about 15 minutes to root everything without using the guides at all as like you said it was pretty standard process. Like I said I extracted and patched the boot myself but just to potentially save time as I'm almost positive the patched image in the last link will work, and if it does not you can just reflash the one from the OTA.zip.
Good luck! (if you decide to root it will work fine)
Click to expand...
Click to collapse
I rooted my phone over the weekend. It went well.
Now, I am wondering how to update firmware. I know I need to download the full firmware from ASUS website and then place it in the root directory.
Should I flash back the stock boot.img and then update firmware?
Or, just simply flash the firmware update and then go through the whole extract boot.img from firmware, patch in Magisk, and then flash patched boot.img in fastboot?

ausaras said:
I rooted my phone over the weekend. It went well.
Now, I am wondering how to update firmware. I know I need to download the full firmware from ASUS website and then place it in the root directory.
Should I flash back the stock boot.img and then update firmware?
Or, just simply flash the firmware update and then go through the whole extract boot.img from firmware, patch in Magisk, and then flash patched boot.img in fastboot?
Click to expand...
Click to collapse
You should be done. I just fully updated and then rooted and set up my phone.
The firmware flash would have been to swap over to CN or WW. If you do that then yes you would re-factory reset + re flash stock boot.img. Then afterwards repeat the boot.img patch to obtain root + repeat setting up your safteynetfix + any other magisk modules.

ausaras said:
I rooted my phone over the weekend. It went well.
Now, I am wondering how to update firmware. I know I need to download the full firmware from ASUS website and then place it in the root directory.
Should I flash back the stock boot.img and then update firmware?
Or, just simply flash the firmware update and then go through the whole extract boot.img from firmware, patch in Magisk, and then flash patched boot.img in fastboot?
Click to expand...
Click to collapse
Hi, I am sorry the last answer I gave you was just wrong. I totally forgot when we root we wont get automatic OTA updates. Which for me is a really good thing anyway. But to get the OTA updates we need to download the firmware files from ASUS website. The same place we downloaded the unlock app but its under firmware. Download every WW firmware and put them one by one in order from oldest to newest on the /sdcard and boot up and it will detect an update. I'm pretty sure we cannot just skip to the latest update like we can with custom rom otas so I am going in order.
I left root, and when done updating will again patch the boot.img and flash it over.
Over the weekend I helped a guy root and set up safteynet and if it helps others I might just write up a tutorial.
Cheers!

Hi! Thank you very much for sharing and helping. I have Tencent edition, from CN to WW, but a couple of things don't work properly:
- Android Auto does not communicate with my car (phone detected and bluetooth connected) bit app stops.
- Gboard voice dictation does not work (google assistant yes)
Country is WW. Safetynet passed. Play certified.
..I followed your guide.
I flashed the posted xda raw throuh fastboot and the the Magisk patched .img
When I tried TO apply latest updates (160) the Same message error appeared.
There is spmething strage (or are least I think It strage):
When I start in "fastboot" (black screen with capital text single line) my device isn'r recognized by PC. Then I switch to "recovery" and then to "fastboot" and a menu (several lines) with title "fastbootd" appears and the phone is recognized by PC (fastboot devices). If I choose bootloader the first screen appears.
I tried to reflash the raw but either the phone isn't recognized or a message appears on the cmd window showing "not rog 6" (more or less) and stops. But the phone is recognized everywhere as rog6...
I miss my broken rog2, it was much easier to root
Do you have any idea what's going on? Or when the twrp boot will be released so that I can brutally flash any zip?

i need fastboot driver for win 64

Anyone know if I root my phone following these instructions, will it factory reset or wipe my data partition? Sorry it's been a while since I rooted any phone, and I am excited about going this route

can anyone provide the patched boot image to have root? Tried looking and asking in other areas but no luck. Or is there a way to patch a bot image that contains root already?

Question What is the simplest way to convert LE2127 (US T-Mobile) to non-TMO image?

I read multiple threads about converting LE2127 to EU/NA, and there appears to be many ways to do it, but I don't understand why I would take one way or another. And which steps are required and in what circumstances. All guides cover "how" but barely ever "why" or "when". Therefore, please help me here, and help in my very specific case:
Circumstances:
SIM is already unlocked
I will have unlock.bin in a couple days
I'm on LE2127_11_C.21
I want the latest OnePlus-provided OxygenOS
Given these circumstances:
What is the simplest way to convert LE2127 (US T-Mobile) to non-TMO image with Magisk root?
Does it matter whether I go for LE2123 / EU image, or LE2125 / global image? If it does, what are the consequences of going for one or the other?

Nowaker said:
I read multiple threads about converting LE2127 to EU/NA, and there appears to be many ways to do it, but I don't understand why I would take one way or another. And which steps are required and in what circumstances. All guides cover "how" but barely ever "why" or "when". Therefore, please help me here, and help in my very specific case:
Circumstances:
SIM is already unlocked
I will have unlock.bin in a couple days
I'm on LE2127_11_C.21
I want the latest OnePlus-provided OxygenOS
Given these circumstances:
What is the simplest way to convert LE2127 (US T-Mobile) to non-TMO image with Magisk root?
Does it matter whether I go for LE2123 / EU image, or LE2125 / global image? If it does, what are the consequences of going for one or the other?
Click to expand...
Click to collapse
Sim unlock is not a requirement for this device but it's good you have it already.
Using the Tmo->Eu conversion bypasses the need for unlock.bin but again, it's good that you have that coming as well.
The simplest way is to use the Tmo->Eu MSM conversion tool and then Oxygen Updater over to global if you want to do that instead of stay on Eu. Either way, using the conversion tool is the way.
From my current understanding, the only real functional difference from Eu vs Global is the latest update speed. I've read that Global was getting the latest updates first. Others report they're available on Eu also and the app was caching old results. I can't be sure on that as I stayed on Eu and I stay on Android 11 (11.2.10.10) but that's what I've read. Hopefully someone else will have additional information on any technical differences. I've been fine using Eu on Tmo/USA.
Since you're interested in going to the latest version, Oos13, you won't need to flash the modem back in as that was fixed for oos13.
You should definitely backup your efs and modemst1/2 partitions before you do anything else.
Open MSM, press F8, select the partitions you want to backup, password is "oneplus". Press read back and they will be stored in C:\ root.
It is advised to unlock bootloader on Android 11 before updating to any other version. I unlocked bootloader and rooted with Magisk on A11 right away. Using the MSM tool to readback boot_a and adb push it onto device. Then having magisk apk patch that boot_a. In my case, by unlocking bootloader and then taking OTA, I retain L1 drm. If I take OTA and then unlock bootloader, I lose L1 drm.
Temp unroot, take the OTA, magisk install to inactive slot, repeat until you're at the firmware you want. Check replies at the back end of this thread: https://forum.xda-developers.com/t/...7-to-eu-via-msm-no-unlock-bin-needed.4272837/
for which OTA route others are taking to get to oos13

To convert your physical T-Mobile sim to an e sim
Go to the home screen. to open the menu, swipe up on the screen.
scroll to the right, choose settings
scroll down choose connections.
choose a sim card manager.
choose sim 1.
choose convert to eSIM
chooses OK.

Thank you @Appreciative for explaining this. I'm very appreciative of your help.
Global/EU thing is now clear to me. Speaking of unlocking the bootloader, I have more to ask.
Appreciative said:
It is advised to unlock bootloader on Android 11 before updating to any other version.
Click to expand...
Click to collapse
So I'm already on LE2127_11_C.21 which is the latest version available to me. I'm actually unsure what OxygenOS version it is. "About device" says Android 12, security update November 5, 2022. There is no indication what OOS version it is anywhere in the settings. Is it OOS 12 or OOS 13?
Anyway, I upgraded all the way to LE2127_11_C.21 after I received the phone. Should I downgrade to the original OOS11 ? And how, given full OTA images for LE2127 are nowhere to be found?
Should I follow the instructions in OP9Pro - Repository of MSM Unbrick Tools (TMO, EU, GLO, IN)? Like I said before, all guides cover "how" but barely ever "why" or "when", and that one is no different.
Appreciative said:
In my case, by unlocking bootloader and then taking OTA, I retain L1 drm. If I take OTA and then unlock bootloader, I lose L1 drm.
Click to expand...
Click to collapse
Why is it important? What are the consequences of losing?

Nowaker said:
Thank you @Appreciative for explaining this. I'm very appreciative of your help.
Global/EU thing is now clear to me. Speaking of unlocking the bootloader, I have more to ask.
So I'm already on LE2127_11_C.21 which is the latest version available to me. I'm actually unsure what OxygenOS version it is. "About device" says Android 12, security update November 5, 2022. There is no indication what OOS version it is anywhere in the settings. Is it OOS 12 or OOS 13?
Anyway, I upgraded all the way to LE2127_11_C.21 after I received the phone. Should I downgrade to the original OOS11 ? And how, given full OTA images for LE2127 are nowhere to be found?
Should I follow the instructions in OP9Pro - Repository of MSM Unbrick Tools (TMO, EU, GLO, IN)? Like I said before, all guides cover "how" but barely ever "why" or "when", and that one is no different.
Why is it important? What are the consequences of losing?
Click to expand...
Click to collapse
Android 12 shipped by OnePlus is oos12. Same for 11/13 and any other. All oos12 is android 12 but not all android 12 is oos. For all OnePlus devices, it's OOS (or ColorOS).
(To make this more confusing, OnePlus for some reason, labels the oos12 packages as _11_C.xx but it's not Android 11. That is why most of the forum mentions them by C.xx and for oos13, F.xx)
You are on oos12.
Follow the conversion thread, you won't need that thread you posted unless you brick and want to go back to stock Tmo firmware to start over again clean. The one I posted is the one you'll use.
When you use the MSM tool, you'll automatically go back to Android 11 early version. It's advised to unlock bootloader from Android 11 for two reasons. One is what I mentioned about my situation. I lose L1 drm by unlocking right after the msm conversion tool but I regain L1 drm after taking the OTA to 11.2.10.10. The other reason is for people without their unlock token. You've already submitted to OnePlus website so this may not affect you. For those who converted to Eu to bypass the unlock.bin token from OnePlus, they NEED to unlock the bootloader on A11 because the bypass is gone/fixed in Android 12/13. They require the unlock.bin if they didn't unlock bootloader in A11.
After you do the MSM Eu->Tmo tool (https://forum.xda-developers.com/t/...7-to-eu-via-msm-no-unlock-bin-needed.4272837/), you will be on Android 11, OOS11, 11.2.3.3 - You can unlock the bootloader there without the token or wait for your token and unlock it later.
After you MSM, you'll start in a clean Android/OOS 11 state. Then you get oxygen updater from play store and update to oos12 and then oos13.
Looking in the back pages of the thread above, you will see which route people take to get there. I BELIEVE it is to take the local upgrade to C.65 (oos12) and then F.16 (oos13).
Losing L1 drm is typically from losing Device Certification. When that happens, google pay, Netflix, Disney+ and other apps that require certification may not work at all or diminished.
If you get to oos13 and have lost L1 drm, do not panic, you have some options to get it back since you'll be rooting along the way. The standard approach is using USNF (universal safetynet fix) module in Magisk. There is a thread a few posts down that's labeled wrong, it's labeled as a question but it's a how-to GooglePay/cts passing (https://forum.xda-developers.com/t/oos13-gpay-cts-profile-fix-for-unlocked-bootloader.4525423/)

Thanks again, @Appreciative!
Appreciative said:
When you use the MSM tool, you'll automatically go back to Android 11 early version. It's advised to unlock bootloader from Android 11 for two reasons.
Click to expand...
Click to collapse
So by you saying that, it means I can use the MSM tool you linked without having to unlock the bootloader beforehand. Is that correct?
Appreciative said:
After you MSM, you'll start in a clean Android/OOS 11 state. Then you get oxygen updater from play store and update to oos12 and then oos13.
Click to expand...
Click to collapse
And then I should be able to pick NA or EU, and it won't really matter, right? Since after I MSM the phone, it identifies itself as LE2125 while previously it was LE2127?
Appreciative said:
Losing L1 drm is typically losing Device Certification. When that happens, google pay, Netflix, Disney+ and other apps that require certification may not work at all or diminished.
Click to expand...
Click to collapse
Ah. The SafetyNet, ctsProfile, and all that stuff. I didn't know it also goes by L1 DRM name. Thanks for clarifying.
Appreciative said:
Temp unroot, take the OTA, magisk install to inactive slot, repeat until you're at the firmware you want. Check replies at the back end of this thread: https://forum.xda-developers.com/t/...7-to-eu-via-msm-no-unlock-bin-needed.4272837/
Click to expand...
Click to collapse
I think everything is clear to me to the point of MSMing the phone, which turns it into LE2123 (EU). Can you confirm these are the steps to get there?
1. Starting from LE2127_11_C.21 (current firmware - OOS12 / Android 12 / T-Mobile)
2. Use the MSM TMo->EU conversion tool which downgrades the phone to Android 11, OOS11, 11.2.3.3, identified as LE2123 (EU)
3. Unlock bootloader.
But now what? When and how exactly do I do things with Magisk? I did the extract-boot.img-patch-and-flash process multiple times on OnePlus 8, OnePlus 8T, OnePlus 9 Pro (Global). It's easy. But it appears things get tricky here on OP9P LE2127 T-Mobile version, so I'd like some clarification.
Am I supposed to patch boot.img with Magisk App? But what do I extract the boot.img from at this stage?

Nowaker said:
Thanks again, @Appreciative!
So by you saying that, it means I can use the MSM tool you linked without having to unlock the bootloader beforehand. Is that correct?
And then I should be able to pick NA or EU, and it won't really matter, right? Since after I MSM the phone, it identifies itself as LE2125 while previously it was LE2127?
Ah. The SafetyNet, ctsProfile, and all that stuff. I didn't know it also goes by L1 DRM name. Thanks for clarifying.
I think everything is clear to me to the point of MSMing the phone, which turns it into LE2123 (EU). Can you confirm these are the steps to get there?
1. Starting from LE2127_11_C.21 (current firmware - OOS12 / Android 12 / T-Mobile)
2. Use the MSM TMo->EU conversion tool which downgrades the phone to Android 11, OOS11, 11.2.3.3, identified as LE2123 (EU)
3. Unlock bootloader.
But now what? When and how exactly do I do things with Magisk? I did the extract-boot.img-patch-and-flash process multiple times on OnePlus 8, OnePlus 8T, OnePlus 9 Pro (Global). It's easy. But it appears things get tricky here on OP9P LE2127 T-Mobile version, so I'd like some clarification.
Am I supposed to patch boot.img with Magisk App? But what do I extract the boot.img from at this stage?
Click to expand...
Click to collapse
To be clear, L1 drm is a separate thing from Safetynet and CTS. L1 dropping to L3 is a result of "insecure device". When you unlock the bootloader, the device is detected as modified. That state fails safetynet. A byproduct of that is DRM drops down to L3. L3 means apps like Netflix will only work in SD quality, if at all. Some apps won't even open or show up in play store when device is not certified. L1/L3/Safetynet/cts aren't exactly interchangeable even tho I kinda made it sound that way. Just in the context that when you are not passing safetynet, a byproduct is you lose L1 drm, because of the device certification not passing.
Yes, you can use the MSM conversion tool without the bootloader being unlocked.
MSM Tmo->Eu conversion tool.
Unlock bootloader.
Download Oxygen Updater in play store.
Root with Magisk.
I pull my boot image using the MSM tool readback as mentioned above, after the conversion and before I take the OTA.
MSM->F8->boot_a and see it in C:
Then I adb push C:\boot_a.img to /sdcard/
Magisk patch the just-pushed boot image.
Temp boot that boot image with:
fastboot boot boot magisk-patched-boot.img
That will temporarily boot you with root. You have to finish the magisk install from here.
Then I reboot and ensure phone is rooted properly.
I download the OTA and let it install. Do not let it reboot after the OTA is finished. You need to go back to magisk and temp unroot by pressing "uninstall magisk" and choose "restore images". Then choose the option for 'flash to other slot OTA'.
This information is based on me going from 11 early to 11 later. There may be some changes for 12/13 that someone else can chime in on.
Alternatively, you can wait to root until later.
Things really aren't tricky on this model. It's actually pretty smooth with the conversion tool. * At least for 11 in my experience. Someone else will have to help you more for 12->13 as I haven't done that. My oxygen updater currently shows release version LE2123_11_F.72 (Eu) or LE2125_11_F.17 (global)
Both of which are oos13. I don't know if it's possible to jump from 11 to 13. I've only read reports of going to 12 and then 13 but I don't read much of 12/13 as I'm staying on 11

Appreciative said:
To be clear, L1 drm is a separate thing from Safetynet and CTS. L1 dropping to L3 is a result of "insecure device". When you unlock the bootloader, the device is detected as modified. That state fails safetynet. A byproduct of that is DRM drops down to L3. L3 means apps like Netflix will only work in SD quality, if at all. Some apps won't even open or show up in play store when device is not certified. L1/L3/Safetynet/cts aren't exactly interchangeable even tho I kinda made it sound that way. Just in the context that when you are not passing safetynet, a byproduct is you lose L1 drm, because of the device certification not passing.
Click to expand...
Click to collapse
OK, cool. So after following the guide, I still should look "secure" for everything, right? On my old OnePlus 9 Pro LE2125, I'm passing SafetyNet, and my GPay works - even though I have Magisk and root. (And use my old phone via `scrcpy` because I broke its display lol)
Appreciative said:
I pull my boot image using the MSM tool readback as mentioned above, after the conversion and before I take the OTA.
MSM->F8->boot_a and see it in C:
Then I adb push C:\boot_a.img to /sdcard/
Magisk patch the just-pushed boot image.
Temp boot that boot image with:
fastboot boot boot magisk-patched-boot.img
That will temporarily boot you with root. You have to finish the magisk install from here.
Then I reboot and ensure phone is rooted properly.
I download the OTA and let it install. Do not let it reboot after the OTA is finished. You need to go back to magisk and temp unroot by pressing "uninstall magisk" and choose "restore images". Then choose the option for 'flash to other slot OTA'.
Click to expand...
Click to collapse
OK, sounds good. Thank you.
Just to clarify: by saying "download the OTA", do you mean using the system-provided update tool, or are we talking about downloading LE2125_11_F.16 from Oxygen Updater?
You also made me learn about "install to inactive slot" - https://topjohnwu.github.io/Magisk/ota.html. I wasn't aware it existed. I applied any OTA updates in the past manually. Download full OTA, extract boot.img, patch it with Magisk, flash OTA and patched boot. Like a fresh install. Also explains why I barely ever upgraded.

Nowaker said:
OK, cool. So after following the guide, I still should look "secure" for everything, right? On my old OnePlus 9 Pro LE2125, I'm passing SafetyNet, and my GPay works - even though I have Magisk and root. (And use my old phone via `scrcpy` because I broke its display lol)
OK, sounds good. Thank you.
Just to clarify: by saying "download the OTA", do you mean using the system-provided update tool, or are we talking about downloading LE2125_11_F.16 from Oxygen Updater?
You also made me learn about "install to inactive slot" - https://topjohnwu.github.io/Magisk/ota.html. I wasn't aware it existed. I applied any OTA updates in the past manually. Download full OTA, extract boot.img, patch it with Magisk, flash OTA and patched boot. Like a fresh install. Also explains why I barely ever upgraded.
Click to expand...
Click to collapse
Well that's where we can both be unsure. I've read that you should go to 12 (c.xx) and then 13 (f.xx) using Oxygen Updater. However, I used the built in system updater ota to get from 11.2.3.3 to 11.2.10.10 myself. I believe you are supposed to use the oxygen updater apk from play store to get to 13 but for that ... someone else will have to clarify exactly which way to get to 12/13. It is for sure covered in this forum, I just have no reason to remember it as I'm staying on 11.
Even if you decide to root later instead of earlier on and Magisk uninstall each time, you can use MSM to readback the boot image and send it over for patching. It's not a big hassle.
After the conversion, you won't have mobile service until you either get to oos13 or flash the modem (modem_a/b not modemst1/2) back in . Don't panic if you see no signal right after Eu conversion is my point

OK, cool. So after following the guide, I still should look "secure" for everything, right?
Click to expand...
Click to collapse
Either way, you should install USNF magisk module and clear cache of google apps to get or stay device certified. That is outlined in the thread I linked above for oos13.
This device has a lot of pros. We can have root and unlocked bootloader, pass safetynet and retain L1 drm, doesn't require sim unlock to unlock bootloader (only needs minor bypass for the OEM unlocking the toggle), unlock.bin bypass with Crazazn's conversion tool, ability to flash over to other firmware regions, and good custom rom and mod support

Appreciative said:
Either way, you should install USNF magisk module and clear cache of google apps to get or stay device certified.
Click to expand...
Click to collapse
For the record - my current One Plus 9 Pro LE2125 (not the new one LE2127 I just purchased) has Android 11, OOS 11.2.7.7.LE15AA. It's rooted and passes all SafetyNet and stuff, and I don't have any extra Magisk modules.
Are you saying it's upgrading to newer versions of Android / OxygenOS that enhances security, and requires us to use extra Magisk modules to hide the fact our bootloader is unlocked?

Nowaker said:
For the record - my current One Plus 9 Pro LE2125 (not the new one LE2127 I just purchased) has Android 11, OOS 11.2.7.7.LE15AA. It's rooted and passes all SafetyNet and stuff, and I don't have any extra Magisk modules.
Are you saying it's upgrading to newer versions of Android / OxygenOS that enhances security, and requires us to use extra Magisk modules to hide the fact our bootloader is unlocked?
Click to expand...
Click to collapse
I'm not saying that but it's probably a fair deduction. I had the same experience as you when I took OTA to 11.2.10.10, I was certified still. Prior to that (11.2.3.3.), I was not certified when bootloader unlocked. I keep usnf module installed just for extra assurance. Although, in some cases on our devices, it will be required to pass safetynet. There's a whole thread-in-thread on the hit&miss nature of some people losing certification and others keeping it, supposedly on the same exact set ups. Then I experienced it myself on the 10T. It sounds like it's more necessary on oos13 but I can't be sure.
As a side note, I'm still very tempted to try oos13. I've heard it's really smooth on this phone. Please let me know how you feel about it. Especially in comparison to oos11

Appreciative said:
As a side note, I'm still very tempted to try oos13. I've heard it's really smooth on this phone. Please let me know how you feel about it. Especially in comparison to oos11
Click to expand...
Click to collapse
I will. I'm collecting information on all the steps, before I start doing it. I think I'm ready but it's also a matter of available time to sit down and do it. With busy life, I don't know if it's going to be tomorrow, or some evening next week.
Note however I'm a pretty non-standard Android user. I keep thing my way. I always use Nova Launcher - which automatically keeps a lot of new features away for me. I may not really experience any difference once my things are in. All I really care about is AdAway and Vanced for stress-free experience, a fully functional Android Auto for driving, Google Photos and Nextcloud for photo backups, and that's about it.

Nowaker said:
I will. I'm collecting information on all the steps, before I start doing it. I think I'm ready but it's also a matter of available time to sit down and do it. With busy life, I don't know if it's going to be tomorrow, or some evening next week.
Note however I'm a pretty non-standard Android user. I keep thing my way. I always use Nova Launcher - which automatically keeps a lot of new features away for me. I may not really experience any difference once my things are in. All I really care about is AdAway and Vanced for stress-free experience, a fully functional Android Auto for driving, Google Photos and Nextcloud for photo backups, and that's about it.
Click to expand...
Click to collapse
I've read Android Auto is broken after Android 11, not sure what fixes are available however. I've read tons of people having issues with AA after upgrade to 12. Not OnePlus specific, I've read about samsung, Realme, asus rog and others all not connecting after Android 11. I think it might be something to do with AA going away. May be something to look into before heading to 13 if it's a must-have for you.
I have AA set up as well. The only issue is when I do screen2auto, to get the icon in my headunit to open s2a, I must uninstall AA update, connect to my car, then upgrade back to latest AA. Then I'm able to cast/mirror my screen to my navigation screen. The kids like to watch youtube videos and whatnot while we are on the road. Or, if they bring their tablets, I use VPN Hotspot for bypassing the Tmo throttle of 600kbps on hotspot connected devices. They can youtube their choice for the rest of the ride. (Playing iSpy, find the colored car, count the diesel trucks etc only lasts for about 15 mins)
I also use Vanced. I tried ReVanced but it started glitching my screen out. I'll give them some time to fix their bugs before I head over to it. It's kinda cool because you can (must) patch in/out the features you want on whatever youtube apk you want. It's still a bit early based on the bugs I experienced but I am sure it'll get better over time

Appreciative said:
That will temporarily boot you with root. You have to finish the magisk install from here.
Then I reboot and ensure phone is rooted properly.
I download the OTA and let it install. Do not let it reboot after the OTA is finished. You need to go back to magisk and temp unroot by pressing "uninstall magisk" and choose "restore images". Then choose the option for 'flash to other slot OTA'.
Click to expand...
Click to collapse
I'm not sure if this works for the 9 pro (I'm researching conversion of a t-mo model that I'm thinking of ordering ATM) but on my 7T I always take the option to download the full update image (usually like ~2GB) and install to the inactive slot, then you just inatall magisk to the inactive before rebooting. That lets you skip the uninstall bit and allows you to roll back to the current rooted state if there're any problems with the update. It's a bigger download than an OTA patch but it's fewer steps altogether.