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?

Moto G5+ XT1687 RETUS (U.S. Unlocked Retail) EASY LTE FIX FOR VERIZON USERS IMEI 0 !!

Hello all,
Follow my guide at your own risk. Read everything SUPER carefully to fix your Verizon LTE network connectivity on your US Retail unlocked Motorola G5 Plus.
I am here to save you all from flashing your phone countless times to try to bring back LTE with no EFS backup and no persist backup.
Here is a guide for XT1687 U.S. version of Moto G5+ (potter) that brings back Verizon LTE on STOCK Firmware/Rom and gives you OTA updates after downgrading from custom 8.1 Oreo roms.
I have not been able to relock bootloader, but that is okay. I am on stock firmware with OTA updates working and LTE working again.
Here is what I did:
I went ahead and flashed POTTER_RETAIL_7.0_NPNS25.137-33-5_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml to bring my phone back to stock from OMNI Rom 8.1 Oreo custom rom.
Obviously there is a bug that makes your IMEI 0 and loses all network connectivity after you flash back to stock from Oreo 8.1 64 bit roms on this phone.
1) Download the STOCK firmware/rom for XT1687 I used and extract the files: POTTER_RETAIL_7.0_NPNS25.137-33-5_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
https://mirrors.lolinet.com/firmware/moto/potter/official/RETAIL/POTTER_RETAIL_7.0_NPNS25.137-33-5_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
2.) Install ADB
https://forum.xda-developers.com/showthread.php?t=2588979
3)Extract the firmware to a folder using 7zip or right-click and extract all to folder in windows, then
4.) boot into your Moto G5+ bootloader by holding: Volume Down + Power button
Open a command prompt, copy and paste the following commands after installing ADB & Fastboot, make sure you launch command prompt or change directory to the same directory as the extracted rom files (cd C:/rom files):
You can type in CMD: fastboot devices to see if your device serial number shows up and you are ready to flash, make sure you are in bootloader mode first.
Paste the following commands in cmd prompt:
Code:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
Boot into your new stock rom now and use WIFI to update OTAs:
Make sure USB debugging is enabled > goto settings > click on build number 5 times then go back and goto developer options > usb debugging checked on
Your network connectivity will still be broken until we patch persist file but continue through the whole bootup for stock rom, set it up from new, and install all the OTA updates available through WIFI first.
5.) Install OTA updates over WIFI even though your network connectivity still doesn't work yet. Your IMEI will be 0 and you will have no network access.
Install all OTA updates with WIFI until your phone is on Build number: NPNS25.137-93-10, there is no firmware file to download this build, so it must be updated through OTA on wifi (all OTAs together should be ~300-500mb total).
6.)Download TWRP 3.2.1.0 and flash it using the following command: fastboot flash recovery twrp-3.2.1-0-potter.img:
https://dl.twrp.me/potter/twrp-3.2.1-0-potter.img.html
7.) Go into TWRP > backup > check EFS so it creates a folder in your phone storage TWRP folder, and then copy it into to a folder on your computer for future backups.
8.) Download Persist file linked here and boot phone in bootloader mode, use PC to copy persist file into TWRP folder > Newly created EFS backup folder > Persist file in your phone storage:
Code:
[url="https://nofile.io/f/RuxbqZAQayH/persist.ext4.win"]https://nofile.io/f/RuxbqZAQayH/persist.ext4.win[/url]
9.) TWRP > restore > check EFS backup folder you made earlier with your new persist file in it (should be 193kb for persist file). > restore the backup for EFS & Persist > reboot phone once its done.
10.) Ta-dah! The Verizon LTE network signal should be instantly back after you rebooted your phone into android OS.
Let me know if it worked for you on other versions as well. Everything is at your own risk. It worked for me and I just flashed it today 06/20/2018.
Also, files are from other devs on XDA, just made the guide to highlight the process steps that worked for me.
Screenshots:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

vwfan511 said:
Hello all,
Follow my guide at your own risk. Read everything SUPER carefully to fix your Verizon LTE network connectivity on your US Retail unlocked Motorola G5 Plus.
I am here to save you all from flashing your phone countless times to try to bring back LTE with no EFS backup and no persist backup.
Here is a guide for XT1687 U.S. version of Moto G5+ (potter) that brings back Verizon LTE on STOCK Firmware/Rom and gives you OTA updates after downgrading from custom 8.1 Oreo roms.
I have not been able to relock bootloader, but that is okay. I am on stock firmware with OTA updates working and LTE working again.
........
5.) Install OTA updates over WIFI even though your network connectivity still doesn't work yet. Your IMEI will be 0 and you will have no network access.
Install all OTA updates with WIFI until your phone is on Build number: NPNS25.137-93-10, there is no firmware file to download this build, so it must be updated through OTA on wifi (all OTAs together should be ~300-500mb total).
Click to expand...
Click to collapse
Nice guide, just a little correction: There is in fact a fastboot flashable NPNS25.137-93-10 stock firmware, here's a mirror, it can be found in this thread.
https://drive.google.com/file/d/16Bfp3nVfvKMURAeKagOaOImX-lvJrYBF/view?usp=drivesdk
The source is the Motorola secure cloud (the one where customer service get the firmware) but not everyone was able to download it from there.
Sent from my Moto G5 Plus using XDA Labs

Wolfcity said:
Nice guide, just a little correction: There is in fact a fastboot flashable NPNS25.137-93-10 stock firmware, here's a mirror, it can be found in this thread.
https://drive.google.com/file/d/16Bfp3nVfvKMURAeKagOaOImX-lvJrYBF/view?usp=drivesdk
The source is the Motorola secure cloud (the one where customer service get the firmware) but not everyone was able to download it from there.
Sent from my Moto G5 Plus using XDA Labs
Click to expand...
Click to collapse
thanks but the link is dead there, know anywhere else to get it? and there the same for ATT and verizon right?

vonwap said:
thanks but the link is dead there, know anywhere else to get it? and there the same for ATT and verizon right?
Click to expand...
Click to collapse
Hmm, I've just tried the link and it works - I'm downloading the NPNS25.137-93-10 stock ROM as I write this from that provided Google Drive link.
As for the AT&T or Verizon versions, I'm not sure (though I think that retus devices on Verizon may have NPNS25.137-93-10, someone with a US device would be better suited to comment). Also, if I recall, devices on Verizon were on a different update path, from NPN25.137-33 to NPN25.137-35 (March 2017 security patch), then to NPN25.137.43-5 (May 2017 security patch), then to NPN25.137-83 (Aug 2017 security patch) before NPN25.137-93 (Nov 2017 security patch), then you should also get NPNS25.137-93-4 (Jan 2018 security patch), NPNS25.137-93-8 (March 2018 security patch), then NPNS25.137-93-10 (April 2018 security patch).
I would also caution against downgrading to NPNS25-137-33-5 (May 2017 security patch), as described in the guide, if your stock firmware was updated to a version newer than the May 2017 security patch. The reason being that if you have a device with a newer stock firmware previously flashed to it, downgrading to the May 2017 firmware may go okay, but you run the risk of hard bricking your device (as installing old OTA updates overwrites your bootloader, which is still present from the newer stock firmware). If your device was previously on the May 2017 stock security patch or older, you may not risk a hard brick but downgrading comes with risks.
Thus, it's probably best to attempt to flash NPNS25.137-93-10 for EU, US and Asia devices or NPNS25.137-92-10 for Brazil and Indian devices to avoid a downgrade.

vonwap said:
thanks but the link is dead there, know anywhere else to get it? and there the same for ATT and verizon right?
Click to expand...
Click to collapse
The link should be working as you see above in the post of @echo92 who has also answered your question as good as I could, maybe better.
I'm also not sure about the firmware path. 33-5 was May security patch here too but as you can see on the screenshot below August 2017 security patch was 33-11, at least here in Europe.
I'm pretty sure that there's no difference in the latest Verizon or AT&T firmwares but as @echo92 said, maybe a US user knows more about that (if you want to be 100% sure about that).
Imo if you go with the latest 93-10 (April security patch) firmware you should be on the safe side as a US user. Firmwares ending on 92-x are for India,Brasil and Asia Pacific, they should work but you won't receive any OTA updates as the updates pushed in the US an Europe search for 93-x firmwares.
Try the link again, maybe in a different browser.
If you can't download it at all I will mirror it on another hoster. Just send me a PM.
Sent from my Moto G5 Plus using XDA Labs

Wolfcity said:
The link should be working as you see above in the post of @echo92 who has also answered your question as good as I could, maybe better.
I'm also not sure about the firmware path. 33-5 was May security patch here too but as you can see on the screenshot below August 2017 security patch was 33-11, at least here in Europe.
I'm pretty sure that there's no difference in the latest Verizon or AT&T firmwares but as @echo92 said, maybe a US user knows more about that (if you want to be 100% sure about that).
Imo if you go with the latest 93-10 (April security patch) firmware you should be on the safe side as a US user. Firmwares ending on 92-x are for India,Brasil and Asia Pacific, they should work but you won't receive any OTA updates as the updates pushed in the US an Europe search for 93-x firmwares.
Try the link again, maybe in a different browser.
If you can't download it at all I will mirror it on another hoster. Just send me a PM.
Sent from my Moto G5 Plus using XDA Labs
Click to expand...
Click to collapse
thanks worked with firefox, Ima try and get my VoLTe back on x1687? flashed to pixle 4g works but just left b/c scared to mess it up again. backed up my efs though. what is the persist ?

Wolfcity said:
The link should be working as you see above in the post of @echo92 who has also answered your question as good as I could, maybe better.
I'm also not sure about the firmware path. 33-5 was May security patch here too but as you can see on the screenshot below August 2017 security patch was 33-11, at least here in Europe.
I'm pretty sure that there's no difference in the latest Verizon or AT&T firmwares but as @echo92 said, maybe a US user knows more about that (if you want to be 100% sure about that).
Imo if you go with the latest 93-10 (April security patch) firmware you should be on the safe side as a US user. Firmwares ending on 92-x are for India,Brasil and Asia Pacific, they should work but you won't receive any OTA updates as the updates pushed in the US an Europe search for 93-x firmwares.
Try the link again, maybe in a different browser.
If you can't download it at all I will mirror it on another hoster. Just send me a PM.
Sent from my Moto G5 Plus using XDA Labs
Click to expand...
Click to collapse
Confusingly, the US series of firmwares seemed to be on different update paths until recently, when Motorola wisely appeared to unify them. The US equivalent of the 33-11 Aug 2017 update for EU/Brazil (and India?), as you posted, was NPN25.137-83, which was a follow on from either NPNS25.137-33-5 (May 2017) or NPNS25.137-35-5 or NPN25.137.43-5 (depending on which US network you were on). Needless to say, it got messy with regards to firmware updates...
But yes, I concur with you that the NPNS25.137-93-10 firmware should be a safe bet (especially as it's currently the latest firmware we have available anyway).

vonwap said:
thanks worked with firefox, Ima try and get my VoLTe back on x1687? flashed to pixle 4g works but just left b/c scared to mess it up again. backed up my efs though. what is the persist ?
Click to expand...
Click to collapse
It's a part of the nandroid backup.
persist.img is "persist" which contains data which shouldn't be changed after the device shipped, for example: calibration data of chips(wifi, bt, camera, etc.), certificates and other security related files. I heard it should contain the IMEI too but I'm not sure about that. You can't back it up with the official TWRP but with some unofficial versions, take a look here: https://forum.xda-developers.com/g5-plus/how-to/psa-efs-persist-t3807240
There are persist files uploaded here on XDA but it's a very hacky way as you have to use a file from the Moto G4 with side effects like yellowish photos.
Check the related threads.
Sent from my Moto G5 Plus using XDA Labs

Hmm sort of worried b/c im on att not sure if it makes a difference. Ill try and report back.

Wolfcity said:
Imo if you go with the latest 93-10 (April security patch) firmware you should be on the safe side as a US user. Firmwares ending on 92-x are for India,Brasil and Asia Pacific
Click to expand...
Click to collapse
Just a correction to the above, Asia Pacific (retapac) uses the 93 series as well.

NZedPred said:
Just a correction to the above, Asia Pacific (retapac) uses the 93 series as well.
Click to expand...
Click to collapse
Ok, thx for the info. So the 92-x firmware is only for India and Brazil.
Sent from my Moto G5 Plus using XDA Labs

Dont use if on any other carrier than verizon
Don't use this if you are not on verizon, I flashed this thinking it would fix some issues I was having with camera on my XT1687 and cricket wireless but now my imei is 0 and unrecoverable. If some on has a presist file and using cricket or att please share so I can see if that will help get LTE and IMEI back.

What firmware rom did you flash?
Did you follow guide and flash persist in TWRP that I linked to? Are you coming from custom Oreo rom?
When you flash back to stock from Oreo roms you will automatically lose IMEI and network connectivity.
Persist file is linked in first post :good::
Code:
https://www23.zippyshare.com/v/13MfpRhg/file.html
TWRP recovery needs to be flashed again after you flash the stock firmware.
You need to make an EFS backup in TWRP Recovery to create the EFS folder in your phone storage, after you finish flashing stock rom.
The persist.img backup needs to be restored in TWRP after you place it in your newly created EFS folder in your TWRP folder on phone storage.
Restore persist.img in TWRP after flashing stock firmware, you should not be flashing firmware only. Persist.img is what gives you your LTE network signal and IMEI back.
Let me know if you have further issues.

vwfan511 said:
Did you follow guide and flash persist in TWRP that I linked to? Are you coming from custom Oreo rom?
When you flash back to stock from Oreo roms you will automatically lose IMEI and network connectivity.
Persist file is linked in first post :good::
Code:
https://www23.zippyshare.com/v/13MfpRhg/file.html
TWRP recovery needs to be flashed again after you flash the stock firmware.
You need to make an EFS backup in TWRP Recovery to create the EFS folder in your phone storage, after you finish flashing stock rom.
The persist.img backup needs to be restored in TWRP after you place it in your newly created EFS folder in your TWRP folder on phone storage.
Restore persist.img in TWRP after flashing stock firmware, you should not be flashing firmware only. Persist.img is what gives you your LTE network signal and IMEI back.
Let me know if you have further issues.
Click to expand...
Click to collapse
Yep flashed presist file in link along with efs after rolling back to the firmware version you recommend, even went back to the the one prior to that after losing IMEI. Whatever I did screwed me up big time. Was able to get 3G back on stock but still no IMEI number. Really not sure what changed or went differently this time compared to other times that I've followed similar steps with no problems but whatever it was has caused me to lose 4G and IMEI completely without being able to recover it by flashing Oreo ROMs. Ohhh well I'll be keeping my eye out on deals at best buy now lol.

Wolfcity said:
Nice guide, just a little correction: There is in fact a fastboot flashable NPNS25.137-93-10 stock firmware, here's a mirror, it can be found in this thread.
https://drive.google.com/file/d/16Bfp3nVfvKMURAeKagOaOImX-lvJrYBF/view?usp=drivesdk
The source is the Motorola secure cloud (the one where customer service get the firmware) but not everyone was able to download it from there.
Sent from my Moto G5 Plus using XDA Labs
Click to expand...
Click to collapse
tuxattack80 said:
Yep flashed presist file in link along with efs after rolling back to the firmware version you recommend, even went back to the the one prior to that after losing IMEI. Whatever I did screwed me up big time. Was able to get 3G back on stock but still no IMEI number. Really not sure what changed or went differently this time compared to other times that I've followed similar steps with no problems but whatever it was has caused me to lose 4G and IMEI completely without being able to recover it by flashing Oreo ROMs. Ohhh well I'll be keeping my eye out on deals at best buy now lol.
Click to expand...
Click to collapse
Try flashing Omni rom.. when I lost mine it wasn't working on other Oreo roms and PixelExperience was forceclosing nonstop, couldn't even get it to boot.
Code:
[URL="http://dl.omnirom.org/potter/"]http://dl.omnirom.org/potter/[/URL]
. My IMEI and 3g came back on Omni, then went back to stock and flashed persist..
Also make sure your TWRP is fully updated to 3.2.1.0, wipe cache dalvik...etc

vwfan511 said:
Try flashing Omni rom.. when I lost mine it wasn't working on other Oreo roms and PixelExperience was forceclosing nonstop, couldn't even get it to boot.
Code:
[URL="http://dl.omnirom.org/potter/"]http://dl.omnirom.org/potter/[/URL]
. My IMEI and 3g came back on Omni, then went back to stock and flashed persist..
Also make sure your TWRP is fully updated to 3.2.1.0, wipe cache dalvik...etc
Click to expand...
Click to collapse
okay thanks i'll give it a shot

Does anyone have a different way to get the persist file. The little zippy thing wants to have me downloading other crap that i dont want??

this worked fine for me on att, coming from google pixle oreo with working efs, restored my efs and this persists,
but my bootloader still says "ID: bad key" not sure if it matters. should i relock my boot loader? or not worry

Archangel said:
Does anyone have a different way to get the persist file. The little zippy thing wants to have me downloading other crap that i dont want??
Click to expand...
Click to collapse
Here's a mirror link for you:
https://nofile.io/f/RuxbqZAQayH/persist.ext4.win
https://nofile.io/g/ZH3emEjoBxxnId89k5DfprKEpe4Ikpis5p85S8edrSibxiLtMzbfYNS0tAx9qE4Q/persist.ext4.win/
Click to expand...
Click to collapse
Reuploaded for you on a different mirror as zippyshare has ads/bs now.

vonwap said:
this worked fine for me on att, coming from google pixle oreo with working efs, restored my efs and this persists,
but my bootloader still says "ID: bad key" not sure if it matters. should i relock my boot loader? or not worry
Click to expand...
Click to collapse
Relocking bootloader may not be possible unless you're on the latest firmware, I haven't relocked mine yet.
I am waiting for official Oreo update to go ahead and try... you can try the relock commands with the latest OTA firmware file.. but I can't guarantee it will work.

XZ1 Compact - Pie to Oreo downgrade

Hi all,
I'm in need of some guidance with regards to a downgrade that I'd like to perform.
About 1 week ago the phone updated itself OTA. I don't remember which version was last before this update .. but what I remember is that the download was quite consistent (over 1G) and then the update took a while. Everything went by without any errors, but at the end I got Android Pie ... and I don't like it.
Reading through the forums I found that flashing a Xperia is doable .. with the right care and tools. So I started to get acquainted with newflasher and Xperifirm - but for now not connecting the phone and / or trying anything and here are the questions for anyone who might guide me a bit:
1. the phone is warranty (about 4-5 months old in fact). I believe the latest firmware that it was running with Oreo was 47.1.A.16.20-R6B. Reference = h**ps://xpericheck.com/cda/1310-4373. I don't see that version in Xperifirm => how can I get access to it for re-flashing?
2. as far as I read, I don't need to root it or unlock the boot loader. Just flashing would be enough to go back one firmware "edition".
3. backing up user data does not interest me so much. I have a list of all apps that are currently installed and within a few hours of tinkering I could get them all re-installed.
4. Would the process of downgrading be visible afterwards? - i.e. warranty would be "bye-bye", right?
.. any other comment / note / reference or observation is highly appreciated.
Best wishes!

metalik said:
Hi all,
I'm in need of some guidance with regards to a downgrade that I'd like to perform.
About 1 week ago the phone updated itself OTA. I don't remember which version was last before this update .. but what I remember is that the download was quite consistent (over 1G) and then the update took a while. Everything went by without any errors, but at the end I got Android Pie ... and I don't like it.
Reading through the forums I found that flashing a Xperia is doable .. with the right care and tools. So I started to get acquainted with newflasher and Xperifirm - but for now not connecting the phone and / or trying anything and here are the questions for anyone who might guide me a bit:
1. the phone is warranty (about 4-5 months old in fact). I believe the latest firmware that it was running with Oreo was 47.1.A.16.20-R6B. Reference = h**ps://xpericheck.com/cda/1310-4373. I don't see that version in Xperifirm => how can I get access to it for re-flashing?
2. as far as I read, I don't need to root it or unlock the boot loader. Just flashing would be enough to go back one firmware "edition".
3. backing up user data does not interest me so much. I have a list of all apps that are currently installed and within a few hours of tinkering I could get them all re-installed.
4. Would the process of downgrading be visible afterwards? - i.e. warranty would be "bye-bye", right?
.. any other comment / note / reference or observation is highly appreciated.
Best wishes!
Click to expand...
Click to collapse
There is a post in different thread that should answer all of your questions. I couldn't write it better myself, so here you go https://forum.xda-developers.com/xperia-xz1-compact/development/help-t3889845/post78673359
I hope it helps.

Hello,
Thanks for the quick reply.
For sure it confirms my understanding of the process.
Would there by any chance to find my Oreo 8 previous firmware (47.1.A.16.20) but for my "Customized DE" version?
It intrigued me that Xperifirm has just the latest one.

metalik said:
Hello,
Thanks for the quick reply.
For sure it confirms my understanding of the process.
Would there by any chance to find my Oreo 8 previous firmware (47.1.A.16.20) but for my "Customized DE" version?
It intrigued me that Xperifirm has just the latest one.
Click to expand...
Click to collapse
I don't think there will be any difference between customised DE and customised UK, there will be VoLTE and fingerprint enabled.
If you have to start asking other xda users for historical firmware then you can't guarantee its validity.
All the firmwares on Xperiafirm are direct from Sony servers.

Didgesteve said:
I don't think there will be any difference between customised DE and customised UK, there will be VoLTE and fingerprint enabled.
If you have to start asking other xda users for historical firmware then you can't guarantee its validity.
All the firmwares on Xperiafirm are direct from Sony servers.
Click to expand...
Click to collapse
I secured the Oreo firmware (customized UK) and the Pie firmware (customized DE) .. using xperifirm. I downloaded Pie just to have the current release that's running on the phone nearby, in case any of my attempts go bad and I'd need to restore it.
By chance, I have for about 2 weeks the possibility to have a non-branded original "Customized UK" XZ1c. As far as I've seen, there 1 app only that's different compared with my original customized DE. I might flash this one to Oreo and back to Pie ... just to learn the process ... and only afterwards to get to work on mine.
I also took my time to look around the web before jumping into flashing.
There are topics which I don't quite grasp yet .. like DRM .. or attest keys.
The thing is that I don't want to break anything in doing this downgrade to Oreo. I don't need to root it, to unlock the boot loader, to break any X-Reality or other functionality. I'm truly amazed by the battery life, btw: I get 3 1/2 days plus with Stamina activated non-stop. The phone is very snappy even with Stamina ... and that's another issue: by downgrading, I wouldn't like to ruin anything of the battery management internal apps / features.
Another thing is this: i don't intend to preserve any data. Whatever I have as apps, currently, will be backed-up and re-installed from scratch + restore of personal data.
I'm now at the point of going through:
1. flashing with flash tool + xperifirm
OR
2. flashing with newflasher.
Basically, I'm trying to understand what the differences (risks) are and what's the safest to use.
Any advice from the XDA community is welcome on this one.
Best wishes,

@metalik download the firmware with xperifirm and from settings select to decrypt/decompress (don't remember how it is). Then delete all .ta files from the folder and persist*.sin (to avoid losing android attest keys and flash with newflasher.
Flashtool has some problems with newer phone models so it's not recommended for xz1c.

the right question would be, how to get the latest security patches but staying with oreo?

vofferz said:
@metalik download the firmware with xperifirm and from settings select to decrypt/decompress (don't remember how it is). Then delete all .ta files from the folder and persist*.sin (to avoid losing android attest keys and flash with newflasher.
Flashtool has some problems with newer phone models so it's not recommended for xz1c.
Click to expand...
Click to collapse
gentlemen,
your input is highly appreciated.
aside from the persist*.sin and all .ta files .. should I take care of anything else?
P.S. I followed this tutorial (link) and it clearly indicates that warranty would not be voided if I would attempt such a re-flashing. Is it true?
P.S. the last question in the thread remains valid: how to apply the upcoming patches on top of Oreo? .. can those be obtained and flashed in a similar way? ... I doubt it would be a good approach because Sony is supposed to take the Google patches and make sure they integrate properly in their Android customization ...

metalik said:
I secured the Oreo firmware (customized UK) and the Pie firmware (customized DE) .. using xperifirm. I downloaded Pie just to have the current release that's running on the phone nearby, in case any of my attempts go bad and I'd need to restore it.
By chance, I have for about 2 weeks the possibility to have a non-branded original "Customized UK" XZ1c. As far as I've seen, there 1 app only that's different compared with my original customized DE. I might flash this one to Oreo and back to Pie ... just to learn the process ... and only afterwards to get to work on mine.
I also took my time to look around the web before jumping into flashing.
There are topics which I don't quite grasp yet .. like DRM .. or attest keys.
The thing is that I don't want to break anything in doing this downgrade to Oreo. I don't need to root it, to unlock the boot loader, to break any X-Reality or other functionality. I'm truly amazed by the battery life, btw: I get 3 1/2 days plus with Stamina activated non-stop. The phone is very snappy even with Stamina ... and that's another issue: by downgrading, I wouldn't like to ruin anything of the battery management internal apps / features.
Another thing is this: i don't intend to preserve any data. Whatever I have as apps, currently, will be backed-up and re-installed from scratch + restore of personal data.
I'm now at the point of going through:
1. flashing with flash tool + xperifirm
OR
2. flashing with newflasher.
Basically, I'm trying to understand what the differences (risks) are and what's the safest to use.
Any advice from the XDA community is welcome on this one.
Best wishes,
Click to expand...
Click to collapse
First take a screenshot of your current keystore status by typing this in the dialler *#*#7378423#*#*, then go to Service tests or Service info -> Security
I used newflasher since it's the last updated software for flashing.
Extract your ftf if required, put only the required files to downgrade in newflasher's folder. For me I only used kernel, system, userdata and cache.
Boot to flash mode, flash using newflasher, reboot and done! Make sure your keystore is intact by comparing the status of all keys with your screenshot.
I've used this method to downgrade temporarily, get temp root, backup my TA partition and then go back to current firmware. All keys intact.

metalik said:
gentlemen,
your input is highly appreciated.
aside from the persist*.sin and all .ta files .. should I take care of anything else?
P.S. I followed this tutorial (link) and it clearly indicates that warranty would not be voided if I would attempt such a re-flashing. Is it true?
P.S. the last question in the thread remains valid: how to apply the upcoming patches on top of Oreo? .. can those be obtained and flashed in a similar way? ... I doubt it would be a good approach because Sony is supposed to take the Google patches and make sure they integrate properly in their Android customization ...
Click to expand...
Click to collapse
I would flash everything else but the .ta and persist*.sin to ensure it works as intended with all files from the firmware you're using. Of course that resets all your userdata, but I guess a downgrade would require that anyway.
Warranty should be just fine - you're still just using official Sony firmware without any modifications to the device or system.
I don't think it will be possible to stay in official Oreo fw with locked bootloader and get recent security patches.
Sony will most probably implement the new patches only into the latest fw version - and that's Pie.
And if someone would make a custom rom with the latest patches on Oreo, you won't be able to install it with a locked bootloader.

Hello again,
what's the impact of flashing persist*.sin ... I believe that's connected with the attest keys, right?
Later edit: I downgraded from Customized DE Pie to Customized UK Oreo. I used newflasher, deleted all *.ta from the root & boot folder ... but by mistake I forgot about the one small persist*.sin file.
Long story short: yes, leaving persist*.sin file in the folder and flashing with newflasher destroyed the Attest keys (I get them as NOT provisioned).
The phone seems to work without problems nevertheless. I re-flashed to an older Customized DE Pie and got the last valid OTA update. Going back to Customized UK Oreo did remove everything from the Service Tests > Security (it showed "none"). But on that the Xperia Companion did the trick (software repair). So it's back on the initial Customized UK Oreo - just attest key shows NOT provisioned ... so
Lessons learned: /*.ta + /persist*.sin + /boot/*.ta must be removed before flashing with newflasher.

Hey, sorry to bring up this old thread but I don't suppose you still have a copy of 16.20? I've been looking for a working copy of it everywhere and I'm getting desperate

Joecalone said:
Hey, sorry to bring up this old thread but I don't suppose you still have a copy of 16.20? I've been looking for a working copy of it everywhere and I'm getting desperate
Click to expand...
Click to collapse
Hey,
sorry for the late reply ...
I kept everything that I (historically) downloaded with Xperifirm ...
I just checked and one folder is this "G8441_Customized UK_1310-6856_47.1.A.16.20_R18B" ... about 2.55 GB in size.
the content of fwinfo.xml is this:
<?xml version="1.0" encoding="utf-8"?>
<fwinfo>
<project>Lilac</project>
<product>Xperia XZ1 Compact</product>
<model>G8441</model>
<market>United Kingdom</market>
<operator>Customized UK</operator>
<swId>1307-7511</swId>
<swVer>47.1.A.16.20</swVer>
<cda>1310-6856</cda>
<cdfVer>R18B</cdfVer>
<fsVar>GENERIC</fsVar>
</fwinfo>
and update.xml is this:
<?xml version="1.0" encoding="utf-8"?>
<UPDATE>
<SYSTEMPARTITIONIMAGE>partition.zip</SYSTEMPARTITIONIMAGE>
<BOOT>boot.zip</BOOT>
<NOERASE>appslog_X-FLASH-ALL-C93B.sin</NOERASE>
<NOERASE>diag_X-FLASH-ALL-C93B.sin</NOERASE>
<NOERASE>ssd_X-FLASH-ALL-C93B.sin</NOERASE>
<NOERASE>Qnovo_X-FLASH-ALL-C93B.sin</NOERASE>
<FACTORY_ONLY>persist_X-FLASH-ALL-C93B.sin</FACTORY_ONLY>
<NOERASE>userdata_X-FLASH-CUST-C93B.sin</NOERASE>
<SIMLOCK>simlock.ta</SIMLOCK>
<NOERASE>cust-reset.ta</NOERASE>
<NOERASE>master-reset.ta</NOERASE>
<RESETNONSECUREADB>reset-non-secure-adb.ta</RESETNONSECUREADB>
<NOERASE>reset-wipe-reason.ta</NOERASE>
</UPDATE>
in a nutshell: I can zip the folder and find a way to send it to you.
Best regards,

Joecalone said:
Hey, sorry to bring up this old thread but I don't suppose you still have a copy of 16.20? I've been looking for a working copy of it everywhere and I'm getting desperate
Click to expand...
Click to collapse
I have my copy of 16.20 and related firmware. They are all Generic Latin America versions.

Xperia XZ1 Compact 47.1.A.16.20 Firmware Search
metalik said:
in a nutshell: I can zip the folder and find a way to send it to you.
Click to expand...
Click to collapse
Shahnewaz said:
I have my copy of 16.20 and related firmware. They are all Generic Latin America versions.
Click to expand...
Click to collapse
Great! I have also been searching desperately for a G8441 47.1.A.16.20 firmware. The country doesn't matter.
If either of you are able to send a zip, I would love to host it on my drive for anyone else who comes looking.

@cynthi4 Customized NOBA (nordic/baltic) latest Oreo: http://aeitis.org/xz1c/
It's downloaded and decrypted via xperifirm and zipped.
I'll keep it there for a while, but might remove soon.

cynthi4 said:
Great! I have also been searching desperately for a G8441 47.1.A.16.20 firmware. The country doesn't matter.
If either of you are able to send a zip, I would love to host it on my drive for anyone else who comes looking.
Click to expand...
Click to collapse
Here you go:
https://bigboidrive.duckdns.org/nextcloud/s/ZW4FQmqBE8Dfcp2

Hello, I just got a xz1c and I'm on 47.1.a.2.281. I haven't updated because of reported battery drain issues. Should I stick with this? Do you recommend pie at all? If not, what's the most stable build you'd recommend?

moist_line said:
Hello, I just got a xz1c and I'm on 47.1.a.2.281. I haven't updated because of reported battery drain issues. Should I stick with this? Do you recommend pie at all? If not, what's the most stable build you'd recommend?
Click to expand...
Click to collapse
Unless you have any specific issues with Oreo or see some advantage with upgrading to Pie, I wouldn't. I am not a big fan of Pie and went through this downgrade to 47.1.A.16.20 to avoid it. If you're interested in custom ROMs, I am running LineageOS 15.1 on my xz1c and it's been great!

That's strange. Being still happy with my locked device, I've always regretted switching to pie so today I actually did the whole process to restore Oreo: downloaded the latest Costumized NOBA oreo the user few posts above linked, deleted *persist.sin and every *.ta files in the folder (even the one inside boot folder), run newflasher and then reboot. Too bad I found stock camera broken
I re-checked multiple times searching for those *.ta files to be sure to avoid this issue, but that's it: I got Oreo but now I have lost stock camera and who knows what else.
Does it mean I've lost those functionality forever? Is there any way to restore stock camera? Happy to see this thread still active

Question How to root T-Mobile OnePlus 9 Proo

Can someone please point me in the direction to Unlock Bootloader and Root the OnePlus 9 Pro T-Mobile Version? I had the Global US Unlocked OnePlus 8 Pro and it was simple. Thank you in advance!

How To: Unlock the T-Mobile Bootloader
Hello all, this is a quick and simple guide to unlocking your T-Mobile locked bootloader. Just a reminder: unlocking the bootloader will wipe your data. The instructions here will apply to all T-Mobile OnePlus devices. Unlock your SIM. Some...
forum.xda-developers.com

Have u received token from tmo

Alright, my bootloader is unlocked now, but I'm not sure how to root at this point. My software version is 11.2.2.2.LE54CB. I can't find that last part (LE54CB) anywhere for download, so I'm not sure where to get my boot.img from. Anybody have some ideas?

Since there's no TWRP for this phone (yet), you have to get the boot.img file and use Magisk to directly patch it. I'm about to embark down this path, I got the T-Mobile version, also on 11.2.2.2 and I just got the bootloader unlocked. Now I need to root it.

glitchsys said:
Since there's no TWRP for this phone (yet), you have to get the boot.img file and use Magisk to directly patch it. I'm about to embark down this path, I got the T-Mobile version, also on 11.2.2.2 and I just got the bootloader unlocked. Now I need to root it.
Click to expand...
Click to collapse
Please let me know if you find a way. I'm super hesitant because of this other thread but I'm not willing to stop using my rooted OP7pro until my 9 is rooted.

I'm about to use https://forum.xda-developers.com/t/...ot-image-and-apply-root-to-the-phone.4263811/ djsubterrain's guide. Seems straight-forward.
1. I downloaded the Payload_Dumper program
2. I grabbed the official ROM from OnePlus's support site (https://www.oneplus.com/support/softwareupgrade/details?code=PM1617074857015) which is the same version my phone is already running.
3. I unzipped the OnePlus9ProOxygen_22.O.05_OTA_0050_all_2103242259_3611e0858f954e7d.zip file I got from OnePlus and there is a payload.bin file
I have to reboot out of linux and into my Windows partition in order to do the next part. But the Payload_Dumper program is supposed to extract a "boot.img" file from the payload.bin; I copy the boot.img file to my phone, into a temporary directory or whatever, and I use the Magisk application on my phone (which can be installed even if not rooted) to patch the boot.img file. I can then use fastboot to flash that image file. (Fastboot Boot rooted_boot.img) and after I reboot, I should, in theory, be rooted.
Since I didn't touch the stock recovery, I should also, in theory, be able to accept OTA updates pushed to my phone. Just normally an OTA update would "unroot" your phone, but guide has a "To retain root access after ROM/OTA update" section that I'm sure to try out next time an update is available. Worst case scenario though, the OTA update unroots me and I have to grab the new version from OnePlus's support site and go through the procedure again to extract the boot.img, patch it on the phone then flash it.

hmm. technically my phone is currently on "11.2.2.2.LE5ACB" and the one on OnePlus's support site is "11.2.2.2.LE15AA"
So there is a slight difference. Meh, should be ok. Worst case scenario I have to flash the entire "11.2.2.2.LE15AA "from OnePlus and I get T-Mobile De-Bloated.

Yeah, I had the exact same hesitation. I'm sorely curious to see how it goes for you. Because I have the OTA for the global rom, and I'm about to use the payload dumper. But if you're a step ahead of me, I'm happy to wait and see if it works for you.

jfsat said:
Yeah, I had the exact same hesitation. I'm sorely curious to see how it goes for you. Because I have the OTA for the global rom, and I'm about to use the payload dumper. But if you're a step ahead of me, I'm happy to wait and see if it works for you.
Click to expand...
Click to collapse
Happy to report it worked just fine. I was able to grab the boot.img from the "11.2.2.2.LE15AA" file on OnePlus's support site. I was able to use Magisk to patch the boot.img file. Then moment of truth..
"fastboot boot 11.2.2.2.LE15AA_patched_boot.img"
And my phone booted just fine. And it was now (temporarily) rooted. I was able to then go back into Magisk and direct-install root. Then reboot.
Magisk confirmed I'm still rooted.
So to all those curious, the boot.img from OnePlus Stock 11.2.2.2.LE15AA works fine on the T-Mobile 11.2.2.2.LE5ACB version.
I may look into using OOM or something to try and force-flash 11.2.2.2.LE5ACB onto my phone and completely De-T-Mobile this phone. I suspect I'll get OTA updates faster from OnePlus than I will from T-Mobile.

so I flashed to global coming from T-Mobile to global 11.2.2.2.
Everything went well. Until I system updated to 11.2.4.4. I realize now it didn't switch to full update and installed the incremental instead. After reboot I no longer have service.sim card is detected but again no service. Don't all the basics, so hopefully someone can help...

ryantf420 said:
so I flashed to global coming from T-Mobile to global 11.2.2.2.
Everything went well. Until I system updated to 11.2.4.4. I realize now it didn't switch to full update and installed the incremental instead. After reboot I no longer have service.sim card is detected but again no service. Don't all the basics, so hopefully someone can help...
Click to expand...
Click to collapse
How did you flash from T-Mobile's 11.2.2.2.LE5ACB over to the Global/USA 11.2.2.2.LE15AA ? The instructions say to put the zip file on the "sdcard" and then go to the update section and do a manual update. However T-Mobile conveniently removed that manual update option. So I was thinking I'd need to use msmtool or something to flash it.
Also you installed the AA version of the ROM, right? That's the U.S (not international) version, but it's generic, not T-Mobile modified. That's the one we should be flashing over our T-Mobile phones, converting them to the U.S Generic version, not the international version. AFAIK the U.S version isn't running 11.2.4.x yet, so not sure why you would get an OTA prompt about 11.2.4.x unless you'd flashed (again, how did you do this?) the international version and not the U.S version.

glitchsys said:
How did you flash from T-Mobile's 11.2.2.2.LE5ACB over to the Global/USA 11.2.2.2.LE15AA ? The instructions say to put the zip file on the "sdcard" and then go to the update section and do a manual update. However T-Mobile conveniently removed that manual update option. So I was thinking I'd need to use msmtool or something to flash it.
Also you installed the AA version of the ROM, right? That's the U.S (not international) version, but it's generic, not T-Mobile modified. That's the one we should be flashing over our T-Mobile phones, converting them to the U.S Generic version, not the international version. AFAIK the U.S version isn't running 11.2.4.x yet, so not sure why you would get an OTA prompt about 11.2.4.x unless you'd flashed (again, how did you do this?) the international version and not the U.S version.
Click to expand...
Click to collapse
flashing like always... unpack payload.bin and flash imgs files... but for some reason I have no service but sim card says tmo.... I've flashed back to stock global and problem still exist.. Also it says unable to find networks manually.. no service. this sucks 7series was so much easier..

ryantf420 said:
flashing like always... unpack payload.bin and flash imgs files... but for some reason I have no service but sim card says tmo.... I've flashed back to stock global and problem still exist.. Also it says unable to find networks manually.. no service. this sucks 7series was so much easier..
Click to expand...
Click to collapse
Using fastboot to flash the img files? There's liike 34 img files. (abl.img, aop.img, bluetooth.img, boot.img, cpucp.img, ..., ..., xbl.img, xbl_config.img). You flashed all 34?
If you're still having problems, I'm rooted and am on the stock 11.2.2.2.LE5ACB from T-Mobile. I can dd up certian partitions and provide them to you if you need. It may help you get back to stock.

glitchsys said:
Using fastboot to flash the img files? There's liike 34 img files. (abl.img, aop.img, bluetooth.img, boot.img, cpucp.img, ..., ..., xbl.img, xbl_config.img). You flashed all 34?
If you're still having problems, I'm rooted and am on the stock 11.2.2.2.LE5ACB from T-Mobile. I can dd up certian partitions and provide them to you if you need. It may help you get back to stock.
Click to expand...
Click to collapse
yes yes please that would help

Rooting is simple. Once your boot loader is unlocked head over to the thread on how to unlock the boot loader. He posted a patched boot IMG for T-Mobile. Flash it in fast boot restart open open magisk manager click direct install it will detect your boot IMG is patched it installs and reboot.

MurphSAN84 said:
How To: Unlock the T-Mobile Bootloader
Hello all, this is a quick and simple guide to unlocking your T-Mobile locked bootloader. Just a reminder: unlocking the bootloader will wipe your data. The instructions here will apply to all T-Mobile OnePlus devices. Unlock your SIM. Some...
forum.xda-developers.com
Click to expand...
Click to collapse

ryantf420 said:
flashing like always... unpack payload.bin and flash imgs files... but for some reason I have no service but sim card says tmo.... I've flashed back to stock global and problem still exist.. Also it says unable to find networks manually.. no service. this sucks 7series was so much easier..
Click to expand...
Click to collapse
Flash your tmobile modem over global.

Where to get tmo modem img?

ryantf420 said:
Where to get tmo modem img?
Click to expand...
Click to collapse
You were supposed to back your's up prior to conversion...

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?