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?

[H930DS][STOCK][OREO]LG V30+ INDIA H930DS20f_00_OPEN_ESA_DS_OP_0517.KDZ

For bootloader unlock purposes, use the H930DS KDZ versions with no later than July 2018 security patch: specifically older 20b at bottom of this post.
Newer firmware is at the top. Look at the names for dates in the title. You can always update to newer firmware later, AFTER bootloader is unlocked. Flashing a newer KDZ will not relock your bootloader. See post #3 for instructions on how to downgrade to earlier firmware for unlocking bootloader.
_________
Yes, LG released ANOTHER ESA 20f KDZ -- but with newer May 2019 security update, enabled Airtel VoLTE -- but REMOVED the LG FM Radio app they had given with the previous ESA 20f with April 2019 security update. If you still want LG FM Radio app, then download from here and install.
H930DS20f_00_OPEN_ESA_DS_OP_0517.KDZ
3.2GB
For H930DS, especially India.
DOWNLOAD LINKS:
* Android File Hosts MIRROR
* LG-Firmwares.com MIRROR
md5: e35b6e89e3c5db5914e2da878e7763c0
TWRP FLASHABLE VERSION:
(thanks to @seadersn!)
https://androidfilehost.com/?fid=6006931924117902994
Flash the "ROM" with latest TWRP. Reflash Magisk immediately afterwards before rebooting to system. It's just stock KDZ but in TWRP-flashable version. Not debloated nor meant to be updated in the future. It's just a very convenient mechanism to have newer stock firmware instead of using dev patched LGUP to flash partitions, etc.
_________
PREVIOUS FIRMWARE
H930DS20f_00_OPEN_ESA_DS_OP_0408.KDZ
3.2GB
For H930DS, especially India.
DOWNLOAD LINKS:
* Android File Hosts MIRROR
md5: 1d36d00dd9a7517b6548394da160997e
TWRP FLASHABLE VERSION:
(thanks to @seadersn!)
https://www.androidfilehost.com/?fid=6006931924117883158
Flash the "ROM" with latest TWRP. Reflash Magisk immediately afterwards before rebooting to system. It's just stock KDZ but in TWRP-flashable version. Not debloated nor meant to be updated in the future. It's just a very convenient mechanism to have newer stock firmware instead of using dev patched LGUP to flash partitions, etc.
_________
PREVIOUS FIRMWARE
H930DS20e_00_OPEN_ESA_DS_OP_0213.KDZ
3.2GB
For H930DS, especially India.
DOWNLOAD LINKS:
* Android File Hosts MIRROR
md5:c7f01795a3a76931e49290439fcb6ed2
TWRP FLASHABLE VERSION:
(thanks to @seadersn!)
https://androidfilehost.com/?fid=1395089523397929907
Flash the "ROM" with latest TWRP. Reflash Magisk immediately afterwards before rebooting to system. It's just stock KDZ but in TWRP-flashable version. Not debloated nor meant to be updated in the future. It's just a very convenient mechanism to have newer stock firmware instead of using dev patched LGUP to flash partitions, etc.
_________
PREVIOUS FIRMWARE
H930DS20c_00_OPEN_ESA_DS_OP_0807.KDZ
3.2GB
For H930DS, especially India.
DOWNLOAD LINKS:
* Android File Hosts MIRROR
md5:63e28b0e7d2cf7df7e666280ad7fe010
TWRP FLASHABLE VERSION:
(thanks to @seadersn!)
https://forum.xda-developers.com/lg-v30/development/rom-fw-lg-joan-h930ds-esa-ind-21c-twrp-t3868182
Flash the "ROM" with latest TWRP. Reflash Magisk immediately afterwards before rebooting to system. It's just stock KDZ but in TWRP-flashable version. Not debloated nor meant to be updated in the future. It's just a very convenient mechanism to have newer stock firmware instead of using dev patched LGUP to flash partitions, etc.
India users may not see the correct letter version of these KDZ images. For some reason India users are one letter behind the other ESA region countries, even when flashing the same KDZ.
_________
PREVIOUS FIRMWARE
USE THESE KDZs BELOW TO TEMPORARILY DOWNGRADE TO FIRMWARE WHICH ALLOWS YOU TO UNLOCK YOUR BOOTLOADER.
Due to changes starting with the July 2018 security patch blocking the WTF bootloader unlock exploit, I've added instructions in post #3 of this thread to use dev patched LGUP to downgrade to earlier versions of India H930DS Oreo KDZ. You can always update to newer firmware AFTER bootloader unlock. Flashing a newer KDZ will not relock your bootloader.
_______________
V20B-IND-XX
INDIA H930DS20b_00_OPEN_ESA_DS_OP_0530.kdz
2.970GB
For H930DS, especially India.
DOWNLOAD LINKS:
* Android File Hosts MIRROR
md5: 9017c5d27208ab19cf0ed6dad652047b
* Mega MIRROR
(Thanks to @tech_infinity. Technically this is 20a India H930DS -- but still works for the bootoloader unlock purpose.)
{
"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"
}
Here's how to flash KDZ:
Since this is official LG firmware for India H930DS, just use LGUP and choose "upgrade" -- to keep apps and data. To prove it's India firmware, your India H930DS will show IND 20B (or whichever letter you choose) after flashing. If it wasn't for India, it would show another region like EU, CIS, AUS, or PHL. Instead it shows IND. India.
To unlock bootloader and root, see this thread. For India H930DS, just substitute this IND H930DS Oreo KDZ.
But just flashing this India KDZ will give you official India Oreo with AI camera and India carrier VoLTE, even without bootloader unlock and root. If you don't wish to unlock bootloader and root, flash 20f at the top. AFTER bootloader unlock and root on early Oreo, you can still update to 20f by flashing the TWRP-flashable zip version + Magisk 18.x. You can update to latest Magisk after successfully rebooting to latest Oreo.
______________
INSTRUCTIONS FOR FLASHING KDZ VIA DEV PATCHED LGUP
1) Go into download mode (power off completely, then hold volume up button while plugging in USB cable)
2) If you are on early Oreo, are not bootloader unlocked/rooted and merely wish to update to latest Oreo, then open patched LGUP and flash 20F KDZ VIA UPGRADE.
It's fairly easy. Most people breeze right through this. But if you have any problems, go through this list:
Make sure you in download mode BEFORE opening the patched LGUP file.
This is at the top of the list as some people forget to do that. The remainder are in no particular order. If that doesn't work,
Try different USB port,
Try different USB cable,
Try different computer.
Reinstall LG mobile drivers.
Reinstall dev patched LGUP again, making sure the files are placed where they need to go (LG Electronics folder, etc).
Reboot the computer.
If you ask for help, that's the list of items we are going to give you anyway.
IF FOR SOME REASON, YOU CANNOT FLASH FROM EARLIER FIRMWARE VIA UPGRADE, then use "DL PARTITION" METHOD:
1) Go into download mode (power off completely, then hold volume up button while plugging in USB cable)
2) open patched LGUP and flash THIS ROM to DL PARTITION. In the pop up box "Select All". Use the attached patched LGUP in this post.
5) DONE.
UPGRADE method lets you keep you data, apps while DL PARTITION METHOD will wipe everything.
1) DOWNLOAD FIRMWARE AND DEV PATCHED LGUP
* Download Oreo KDZ you wish to install -- for bootloader unlock would be H930DS 20b. You can update to more current firmware AFTER unlocking bootloader on early Oreo.
(If you just don't like Pie, then choose the most recent Oreo KDZ, which is IND H930DS 20f at the top.)
* DOWNLOAD THIS DUAL VERSION OF DEV PATCHED LGUP, made by @tecknight:
https://androidfilehost.com/?fid=11410963190603845019
(Or use attached file from bottom of this post. Thanks to @tecknight! Please go here and click the THANK BUTTON!)
_________________
2) INSTALL DEV PATCHED LGUP
0. Uninstall any prior LGUP you have. Uninstall anything like Uppercut, which no longer works and causes conflicts with this Dev Patched LGUP.
1. Extract LGUP_DualMode.zip to a folder on your PC.
2. Browse into the folder and launch LGUP_Store_Frame_Ver_1_14_3.msi.
Follow the prompts to complete the install.
3. In that folder, right click and select "Run as Administrator" on "SetDev.bat" to set LGUP to developer mode
4. Launch LGUP using the desktop shortcut, NOT the Install folder shortcut.
Choose Process : UPGRADE (if you are on earlier firmware), PARTITION DL (all partitions) or REFURBISH
_______________
Not necessary, but putting this next item here just so you know... IF for some reason your phone is acting wonky, usually a Master Reset will fix it. No need to reflash anything, but this procedure below does wipe all data. It will give you "factory fresh" setup on the new KDZ. We use this on purpose over in the Frankenstein thread for US998, but is not usually necessary for this simple Oreo H930DS upgrade to another region H930DS.
MASTER RESET
With your device powered off, press and hold the Power button and Volume Down buttons simultaneously for a few seconds.
When the LG logo appears, quickly release and then re-hold the Power button while keep holding the Volume Down button.
Let go of the buttons when the onscreen menu appears.
When you see the option to Delete all user data (including LG and carrier apps) and reset all settings message prompt, press the Volume Down button to highlight Yes.
Then press the Power button to reset the device.
Wait until the reset is complete then reboot your device. If it’s able to boot up successfully, proceed with the initial setup.
Click to expand...
Click to collapse
_________________________
SETTINGS
I know everyone has their own settings, but for new owners who want a reference point for all the various submenus and customization, I'll share screenshots of my settings. You can always change to what you like.
https://photos.app.goo.gl/NCm643Y7prJhDLaS2

Beside the step by step instructions above here's a video:
ayaskant12 said:
Just to help I made a video on how to upgrade
https://www.youtube.com/watch?v=mKqBK7QrpE0&feature=youtu.be
Click to expand...
Click to collapse

HOW TO (temporarily) DOWNGRADE BACK TO EARLY OREO FOR BOOTLOADER UNLOCK
(or DOWNGRADE TO LAST OREO BECAUSE YOU DON'T LIKE PIE)
1) DOWNLOAD FIRMWARE AND DEV PATCHED LGUP
* Download Oreo KDZ you wish to install -- for bootloader unlock would be H930DS 20b. You can update to more current firmware AFTER unlocking bootloader on early Oreo.
(If you just don't like Pie, then choose the most recent Oreo KDZ, which is 20f at the top.)
* DOWNLOAD THIS DUAL VERSION OF DEV PATCHED LGUP, made by @tecknight:
https://androidfilehost.com/?fid=11410963190603845019
(Or use attached file from bottom of this post. Thanks to @tecknight! Please go here and click the THANK BUTTON!)
_________________
2) INSTALL DEV PATCHED LGUP
0. Uninstall any prior LGUP you have. Uninstall anything like Uppercut, which no longer works and causes conflicts with this Dev Patched LGUP.
1. Extract LGUP_DualMode.zip to a folder on your PC.
2. Browse into the folder and launch LGUP_Store_Frame_Ver_1_14_3.msi.
Follow the prompts to complete the install.
3. In that folder, right click and select "Run as Administrator" on "SetDev.bat" to set LGUP to developer mode
4. Launch LGUP using the desktop shortcut, NOT the Install folder shortcut.
Choose Process : PARTITION DL (all partitions) or REFURBISH
----------------------------
3) DOWNGRADING/UPGRADING ANY LG V30/V30+/V30S TO EARLY OREO KDZ FIRMWARE
1) Go into download mode (power off completely, then hold volume up button while plugging in USB cable)
2) open patched LGUP and flash OREO KDZ to DL PARTITION mode. In the pop up box "Select All". Use the attached patched LGUP in this post.
You can also use REFURBISH mode, if you wish.
3) Master Reset (post 101 of Frankenstein thread)
5) DONE.
It's fairly easy. Most people breeze right through this. But if you have any problems, go through this list:
Make sure you in download mode BEFORE opening the patched LGUP file.
This is at the top of the list as some people forget to do that. The remainder are in no particular order. If that doesn't work,
Try different USB port,
Try different USB cable,
Try different computer.
Reinstall LG mobile drivers on your PC.
Reinstall dev patched LGUP again, making sure the files are placed where they need to go (LG Electronics folder, etc).
REBOOT THE COMPUTER.
If you ask for help, that's the list of items we are going to give you anyway.
WARNING: In LGUP do NOT go messing with modes not mentioned in these instructions. Especially do NOT use Chip Erase.
https://9to5lg.com/lgup-1-15-manual-how-to-unbrick-restore-your-lg-devices-with-lgup/
3) ChipErase: Dangerous, This will erase IMEI/efs, Do not try this if you do not have a NV backup.
Click to expand...
Click to collapse
_________________
4) IF YOU NEED TO UNLOCK BOOTLOADER (with early Oreo), GO READ WTF INSTRUCTIONS
_________________________
SETTINGS
I know everyone has their own settings, but for new owners who want a reference point for all the various submenus and customization, I'll share screenshots of my settings. You can always change to what you like.
https://photos.app.goo.gl/NCm643Y7prJhDLaS2
________________

LG has now released firmware with post-July 2018 security patch for India H930DS (August 2018, but more will come) to prevent you from unlocking your bootloader. If you have installed any such firmware or your phone has come with that firmware, you will NEED to temporarily downgrade to the 20b KDZ in post #1 (which has safe June 2018 security patch) to unlock bootloader.
After you unlock the bootloader, then you can update to back to latest firmware. At that point LG can't block you from unlocking YOUR bootloader because it's already unlocked! You don't have to install TWRP or root immediately, but since you have an unlocked bootloader, why not? Point is, to get your bootloader unlocked so you CAN at some point install TWRP and root if you wish.
Instructions for downgrading using dev patched LGUP are in post #1 of this thread, as well as dev patched LGUP attached to that post.

Hi, I have rooted my H930DS (V20b-GLOBAL-COM), if i wanted to flash one of the latest version, for example, V21d-OPEN-HK). Can i just flash using Patched LGUP via UPGRADE? Do i need to flash TWRP again?

kongming said:
Hi, I have rooted my H930DS (V20b-GLOBAL-COM), if i wanted to flash one of the latest version, for example, V21d-OPEN-HK). Can i just flash using Patched LGUP via UPGRADE? Do i need to flash TWRP again?
Click to expand...
Click to collapse
This is more a general question than India KDZ for ESA region, but I'll post the answer over in the CIS H930DS KDZ thread too...
__________
1) If you flash your KDZ via UPGRADE option with dev patched LGUP, you will temporarily keep your data but will have to reinstall TWRP again -- and flash the no encryption, no root check files + Magisk. You are basically returning it to stock, with LG encryption enabled again. So, you will have to wipe again anyway to get TWRP back.
2) If you flash with DL Partition method, BUT UNcheck the recovery partitions, you will keep TWRP. Flash all partitions except for recovery. Then, just boot to TWRP via fastboot commands (like when you first unlocked bootloader). Reflash no encryption, no root check files + Magisk. You are one step ahead because you still have TWRP.
After that you can use a TWRP backup to restore data or you can use Titanium Backup to restore all apps + data.
This is going to be a decision you will need to make every time LG releases a new "update" for your region, especially if it's only a "security" patch update and no other fixes, and if there's no corresponding TWRP flashable zip ("stock" image ROM), like from @westwood24 or other devs.
Once you get a rhythm going, you can install update and restore apps + data in minimal time. But every time a new update comes out (every two or three months, for the next three years) you'll have to decide whether it's worth the effort to do this or if you want to wait until the NEXT update.

Hi @ChazzMatt I recently bought a second hand LG V30 + model number H930DS running stock android 8.0 the software version is V20c-AME-XX, I want to unlock bootloader , root and install custom ROMs , where should I start because I'm new to LG, I know I have to downgrade to V20b to be able to unlock the bootloader, but before I unlock the bootloader should I backup anything in case I want to re-lock the bootloader, because previously I owned an Xperia Z5 where before unlocking the bootloader the developer advised us to backup TA partition before unlocking , is there such a thing here on LG?

Bronnel said:
Hi @ChazzMatt I recently bought a second hand LG V30 + model number H930DS running stock android 8.0 the software version is V20c-AME-XX, I want to unlock bootloader , root and install custom ROMs , where should I start because I'm new to LG, I know I have to downgrade to V20b to be able to unlock the bootloader, but before I unlock the bootloader should I backup anything in case I want to re-lock the bootloader, because previously I owned an Xperia Z5 where before unlocking the bootloader the developer advised us to backup TA partition before unlocking , is there such a thing here on LG?
Click to expand...
Click to collapse
I know what you're referring to -- when you bootloader unlock Sony phones certain propietary features stop working. That does not happen with LG. Unlocked bootloader on stock firmware, you do not lose any functionality.
I even mention that at the top in my WTF instructions. Print those out, read them carefully.
Then, if you ever wish to relock bootloader, just make sure you're on full stock (no TWRP) and fastboot OEM lock.
You have India H930DS or another?

ChazzMatt said:
I know what you're referring to -- when you bootloader unlock Sony phones certain propietary features stop working. That does not happen with LG. Unlocked bootloader on stock firmware, you do not lose any functionality.
I even mention that at the top in my WTF instructions. Print those out, read them carefully.
Then, if you ever wish to relock bootloader, just make sure you're on full stock (no TWRP) and fastboot OEM lock.
You have India H930DS or another?
Click to expand...
Click to collapse
Thank you I appreciate your answer my bro, I have H930DS on the box it says ARE region which stands for Mid. East/Africa (AE/United Arab Emirates)
have downloaded this for ARE region is this correct?
H930DS20b_00_OPEN_AME_DS_OP_0530.kdz
LG H930DS

Bronnel said:
Thank you I appreciate your answer my bro, I have H930DS on the box it says ARE region which stands for Mid. East/Africa (AE/United Arab Emirates)
have downloaded this for ARE region is this correct?
H930DS20b_00_OPEN_AME_DS_OP_0530.kdz
LG H930DS
Click to expand...
Click to collapse
Yes, that sounds right. I was just curious because you were posting in the India KDZ thread. I have a CIS KDZ thread for non-India H930DS variants, but your region specific (for your phone) is even better.

ChazzMatt said:
Yes, that sounds right. I was just curious because you were posting in the India KDZ thread. I have a CIS KDZ thread for non-India H930DS variants, but your region specific (for your phone) is even better.
Click to expand...
Click to collapse
Thank you sir, now I'm ready to do this I'm following every single word on your post, thank you very much for all the things you've done that's just amazing tutorial

mesaralam said:
Hello, done flash with india kdz. By my security patch is 1june 2018... Note can i expect latest security patch from software updates straight away from phone? Par advise. My phone is India LG v30+ h930ds
Click to expand...
Click to collapse
Do you have an India H939DS and you flashed June firmware so you can bootloader unlock and root? If so, have you done that?
Do you have ANOTHER region's H930DS and you specifically wanted India H930DS firmware for stuff like Jio VoLTE?
I can answer better if I know why you flashed the June firmware...
This link is the latest India firmware currently released and has August security patch. Also, another update should be coming before end of November.
You can flash either one (August or the upcoming one) with LGUP and after that, you should receive India OTA updates IF
* your IMEI matches India H930DS variant
* you are full stock, without TWRP custom recovery.
However, if you are flashing India firmware on an H930DS from another region (like Hong Kong), then you will probably have to keep manually flashing India updates. My experience has been that OTA updates seem to be tied to IMEI, but I there may be exceptions.
If you have TWRP recovery and are rooted -- even with an India H930DS -- you won't be able to install OTA (partial image updates), since you are not 100% stock. You will have flash full image KDZ or flash a TWRP-flashable version which some devs are making. We already have US998, H930, VS996 TWRP-flashable updates. Surely someone soon will start making them for India H930DS?
I almost never take partial image OTA, even back when I was not rooted. I flash full image KDZ. Now that I have TWRP and am rooted, I have to update via KDZ or TWRP flashable version of the KDZ.

ChazzMatt said:
...
We already have US998, H930, VS996 TWRP-flashable updates. Surely someone soon will start making them for India H930DS?
...
Click to expand...
Click to collapse
this will be available this evening (it's 5pm now here in germany) @JohnFawkes will take over the USA variants, actual and future twrp flashable zip versions, i'll do europe and india then. if there's a need for another region, pls contact either me or JohnFawkes via pm :good:

hmm, written too early: the india version uses different offsets or in general is constructed another way, all my tools can extract the kdz, but not the dz... looks like not possible atm for this particular file, but i'll investigate more later :good:
example:
Code:
[email protected]:~/Schreibtisch/kdztools-master$ ./undz -f kdzextracted/H93021c_00.dz -x
[!] Error: Value supposed to be zero in field "reserved5" is non-zero (0x5900)
i would need a tester

H930DS20c_00_OPEN_ESA_DS_OP_0807.KDZ now posted, as well as link to @seadersn TWRP-flashable "ROM" (KDZ in TWRP flashable file form). This continues the TWRP-flashable KDZ tradition which has been available for US998 and Europe H930, to update easily to newer stock firmware using TWRP. He's gallantly expanding to other variants.
Please go to his thread to thank him and even donate. He's putting a lot of effort into making TWRP flashable KDZ for our phones.
See top of post #1.

This ISN'T the India update (so you'll still your phone software showing up as GLOBAL-COM). The correct India firmware is H930DS20b_00_OPEN_ESA_DS_OP_0808.kdz
You can find it here: https://lg-firmwares.com/downloads-file/16226/H930DS20b_00_OPEN_ESA_DS_OP_0808.kdz
Not sure if this helps. Jio wasn't working on the other firmware. (No VOLTE). Just in India for a visit and was trying to use a Jio SIM.
Also, does anyone know why the network type doesn't show up when the phone is roaming? (No H/H+/LTE etc)

Yes, it is "correct" India update. All ESA are ESA. I'll argue you all day long on that.
We proved it MONTHS ago with the first ESA Oreo 20A. So please STOP trying to mislead people.
You can either flash this KDZ via LGUP or flash the TWRP FLASHABLE ZIP file via TWRP.
Either will work. But for people that are rooted, flashing via TWRP is an easy way to update.
Thank @seadersn for that, and he's going to continue to do it for us.
The security patch date is the only thing that is updated in this build.
djpeesh said:
This ISN'T the India update (so you'll still your phone software showing up as GLOBAL-COM). The correct India firmware is H930DS20b_00_OPEN_ESA_DS_OP_0808.kdz
You can find it here: https://lg-firmwares.com/downloads-file/16226/H930DS20b_00_OPEN_ESA_DS_OP_0808.kdz
Not sure if this helps. Jio wasn't working on the other firmware. (No VOLTE). Just in India for a visit and was trying to use a Jio SIM.
Also, does anyone know why the network type doesn't show up when the phone is roaming? (No H/H+/LTE etc)
Click to expand...
Click to collapse

Mate,
I'm not looking to argue so you're on your own if you want to argue all day.
It was a simple point that if you want OTAs and VoLTE to work, install this version. I gain nothing from flogging the correct version. You're free to download whatever you like. The KDZ you've uploaded is unfortunately the Indonesian version. The KDZ I've linked to is the Indian version. Yes, both are ESA and likely the same theres a difference and that needs to be pointed out.
Anyway, I've got it working so I'm out. Also, the Indian version of the software tells me my network type (H/H+/LTE) even while roaming.
ChazzMatt said:
Yes, it is "correct" India update. All ESA are ESA. I'll argue you all day long on that.
We proved it MONTHS ago with the first ESA Oreo 20A. So please STOP trying to mislead people.
You can either flash this KDZ via LGUP or flash the TWRP FLASHABLE ZIP file via TWRP.
Either will work. But for people that are rooted, flashing via TWRP is an easy way to update.
Thank @seadersn for that, and he's going to continue to do it for us.
The security patch date is the only thing that is updated in this build.
Click to expand...
Click to collapse
Sent from my SM-G965F using Tapatalk

it may be that parts of the OP partition are changed for india, but the rom itself indeed should be working for phil, india and indonesia. i will check the differences in a week or two, atm our house is being rebuilt, no time for android stuff atm -.+

djpeesh said:
Mate,
I'm not looking to argue so you're on your own if you want to argue all day.
It was a simple point that if you want OTAs and VoLTE to work, install this version. I gain nothing from flogging the correct version. You're free to download whatever you like. The KDZ you've uploaded is unfortunately the Indonesian version. The KDZ I've linked to is the Indian version. Yes, both are ESA and likely the same theres a difference and that needs to be pointed out.
Anyway, I've got it working so I'm out. Also, the Indian version of the software tells me my network type (H/H+/LTE) even while roaming.
Click to expand...
Click to collapse
We proved Jio VoLTE works and that India LG help app is installed with ESA KDZ. It says India! And has India Jio Volte. You can't argue with that.
That's why all ESA KDZ is titled as just ESA.
Due to bureaucratic bumbling LG India released Oreo like two months after Phillipines and Indonesia, but they're are all part of ESA and all share the same KDZ. People found they could download the Philippines/Indonesia Oreo and have "India" with Jio VoLTE and LG India app even before LG India have them Oreo. It's INDIA KDZ when installed on India SIM card. Or Philippines when installed on Philippines, or Indonesia when installed on Indonesia.
There's no difference. LG has several KDZ regions like that, where two or three countries share one KDZ and parts are installed depending on what country carrier you have. Adaptble installation.
When India LG finally released Oreo, we proved it was the same KDZ as the ESA ALREADY RELEASED -- but one letter behind since they didn't want to admit their incompetence.
So, for this most recent I took the LATEST letter ESA KDZ because we proved it's really all the same -- same build number, everything.

Safe STOCK Oreo by Fastboot FULL flash!

Safe STOCK Oreo by Fastboot FULL flash:
download file from my gdrive: https://drive.google.com/open?id=1XWoaudSHAhQMWi3Au4wmtf2QaCrhugoD
Now to what matters...
Important!!! Only for RETAIL versions AMERICAS with working band base ending in ¨R¨, also for people who DID NOT mess up with persist and EFS...otherwise it is likely to loose IMEI...also....working for previous BRICKED devices that need to use Moto Z bootloader, but only RETAIL AMERICAS versions.
Anything else, please read and follow this post here: https://forum.xda-developers.com/g5-plus/how-to/moto-g5-plus-fastboot-flash-stock-oreo-t3848433
download and unzip file.
extract ROM folder and copy within very same folder the adb fastboot oreo g5+ folder and content extracted in same folder all together.
before going on, make sure you have motorola latest drivers installed, found in ADDONS, adbz folder, motorola device manager.
restart phone in bootloader, connect to laptop.
run file with name OREO G5 PLUS DE CERO.bat (spanish whatever), once done, unplug and restart phone.
should delay a few moments and go into setup.
additionally, you may want to install latest TWRP 3231 found in RECOVERIEZ folder.
additionally, you may want to flash motorola boot logo found in BOOT LOGOZ folder, to prevent the unlocked phone boring screen.
additionally, you may want to flash Magisk 17.1 in ROOTZ folder, only Magisk file, nothing else.
additionally, you may want to flash Kernels like Extended or EX found in KERNELZ folder.
some apps in APPZ folder that I use.
in REVIVALZ you may find files to bring bricked phone to life, but that is another history you may need to find out by reading posts.
in ADBz you can find extra folders for CMD commands.
This tuto is for knowledgeable people.
I have my device working fine in official stock again, however........BOOTLOADER STAYS FOR MOTOZ, meaning, you cannot take OTAS, reason for which locking Bootloader is unnecesary, recommended that once TWRP3231 is flashed, you may backup averything, all partitions, remember this is the last backup for official STOCK we will have from Motonovo.
For further updated official releases, just flash as regular in adb-cmd.
Ciao Babies!!!

Iam uploading my special Bricked moto Z Loader Stock Oreo TWRP Moto G5+ for those who may need it, ciao!!!

Thank you very much, I just followed your method, very fast and clean, thank you I got Oreo on my phone!

SowilM said:
Thank you very much, I just followed your method, very fast and clean, thank you I got Oreo on my phone!
Click to expand...
Click to collapse
Happy to help brother!

So this will work for european users who did not break their persist?

Fabiuz99 said:
So this will work for european users who did not break their persist?
Click to expand...
Click to collapse
As far as i Know only for retail americas but you can try on your own and let us know

Battery performance is for fully happy and satisfied OVERWHELMING

will it work for indian version
will it work for indian version
---------- Post added at 06:48 PM ---------- Previous post was at 06:00 PM ----------
prnv1312 said:
will it work for indian version
Click to expand...
Click to collapse
thnks alot man

can i update my moto g5 plus build number NPNS25.137-93-14 rooted with this?
LLegion said:
Safe STOCK Oreo by Fastboot FULL flash:
download file from my gdrive: https://drive.google.com/open?id=1XWoaudSHAhQMWi3Au4wmtf2QaCrhugoD
Now to what matters...
Important!!! Only for RETAIL versions AMERICAS with working band base ending in ¨R¨, also for people who DID NOT mess up with persist and EFS...otherwise it is likely to loose IMEI...also....working for previous BRICKED devices that need to use Moto Z bootloader, but only RETAIL AMERICAS versions.
Anything else, please read and follow this post here: https://forum.xda-developers.com/g5-plus/how-to/moto-g5-plus-fastboot-flash-stock-oreo-t3848433
download and unzip file.
extract ROM folder and copy within very same folder the adb fastboot oreo g5+ folder and content extracted in same folder all together.
before going on, make sure you have motorola latest drivers installed, found in ADDONS, adbz folder, motorola device manager.
restart phone in bootloader, connect to laptop.
run file with name OREO G5 PLUS DE CERO.bat (spanish whatever), once done, unplug and restart phone.
should delay a few moments and go into setup.
additionally, you may want to install latest TWRP 3231 found in RECOVERIEZ folder.
additionally, you may want to flash motorola boot logo found in BOOT LOGOZ folder, to prevent the unlocked phone boring screen.
additionally, you may want to flash Magisk 17.1 in ROOTZ folder, only Magisk file, nothing else.
additionally, you may want to flash Kernels like Extended or EX found in KERNELZ folder.
some apps in APPZ folder that I use.
in REVIVALZ you may find files to bring bricked phone to life, but that is another history you may need to find out by reading posts.
in ADBz you can find extra folders for CMD commands.
This tuto is for knowledgeable people.
I have my device working fine in official stock again, however........BOOTLOADER STAYS FOR MOTOZ, meaning, you cannot take OTAS, reason for which locking Bootloader is unnecesary, recommended that once TWRP3231 is flashed, you may backup averything, all partitions, remember this is the last backup for official STOCK we will have from Motonovo.
For further updated official releases, just flash as regular in adb-cmd.
Ciao Babies!!!
Click to expand...
Click to collapse
can i update my moto g5 plus build number NPNS25.137-93-14 rooted with this? june security update

LLegion said:
Safe STOCK Oreo by Fastboot FULL flash:
download file from my gdrive: https://drive.google.com/open?id=1XWoaudSHAhQMWi3Au4wmtf2QaCrhugoD
Now to what matters...
Important!!! Only for RETAIL versions AMERICAS with working band base ending in ¨R¨, also for people who DID NOT mess up with persist and EFS...otherwise it is likely to loose IMEI...also....working for previous BRICKED devices that need to use Moto Z bootloader, but only RETAIL AMERICAS versions.
Anything else, please read and follow this post here: https://forum.xda-developers.com/g5-plus/how-to/moto-g5-plus-fastboot-flash-stock-oreo-t3848433
download and unzip file.
extract ROM folder and copy within very same folder the adb fastboot oreo g5+ folder and content extracted in same folder all together.
before going on, make sure you have motorola latest drivers installed, found in ADDONS, adbz folder, motorola device manager.
restart phone in bootloader, connect to laptop.
run file with name OREO G5 PLUS DE CERO.bat (spanish whatever), once done, unplug and restart phone.
should delay a few moments and go into setup.
additionally, you may want to install latest TWRP 3231 found in RECOVERIEZ folder.
additionally, you may want to flash motorola boot logo found in BOOT LOGOZ folder, to prevent the unlocked phone boring screen.
additionally, you may want to flash Magisk 17.1 in ROOTZ folder, only Magisk file, nothing else.
additionally, you may want to flash Kernels like Extended or EX found in KERNELZ folder.
some apps in APPZ folder that I use.
in REVIVALZ you may find files to bring bricked phone to life, but that is another history you may need to find out by reading posts.
in ADBz you can find extra folders for CMD commands.
This tuto is for knowledgeable people.
I have my device working fine in official stock again, however........BOOTLOADER STAYS FOR MOTOZ, meaning, you cannot take OTAS, reason for which locking Bootloader is unnecesary, recommended that once TWRP3231 is flashed, you may backup averything, all partitions, remember this is the last backup for official STOCK we will have from Motonovo.
For further updated official releases, just flash as regular in adb-cmd.
Ciao Babies!!!
Click to expand...
Click to collapse
will it work on a latin american one? xt1680 currently on npn25.137-92 november patch unlocked bootloader. This is not my daily driver. If the flash of this oreo rom doesnt work, can i just reflash my npn25.137-92 firmware back? or will that not work?

carloandreaguilar said:
will it work on a latin american one? xt1680 currently on npn25.137-92 november patch unlocked bootloader. This is not my daily driver. If the flash of this oreo rom doesnt work, can i just reflash my npn25.137-92 firmware back? or will that not work?
Click to expand...
Click to collapse
I am friom mexico and my phone is working perfect...is your question anserred alwearu...can not go back to nouhat

will it work for indian version XT1686

LLegion said:
Safe STOCK Oreo by Fastboot FULL flash:
I have my device working fine in official stock again, however........BOOTLOADER STAYS FOR MOTOZ, meaning, you cannot take OTAS, reason for which locking Bootloader is unnecesary, recommended that once TWRP3231 is flashed, you may backup averything, all partitions, remember this is the last backup for official STOCK we will have from Motonovo.
Click to expand...
Click to collapse
Can you please clarify the above info. I have a U.S. x1687 that is still stock nougat that I'd like to upgrade to Oreo (since Motonovo screwed everyone with the August security update and lots of us are experiencing major battery drain issues!) . I'd like to remain completely stock if at all possible. Any way to update with the Moto G5+ bootloader?

carloandreaguilar said:
will it work on a latin american one? xt1680 currently on npn25.137-92 november patch unlocked bootloader. This is not my daily driver. If the flash of this oreo rom doesnt work, can i just reflash my npn25.137-92 firmware back? or will that not work?
Click to expand...
Click to collapse
nvrpayretail said:
Can you please clarify the above info. I have a U.S. x1687 that is still stock nougat that I'd like to upgrade to Oreo (since Motonovo screwed everyone with the August security update and lots of us are experiencing major battery drain issues!) . I'd like to remain completely stock if at all possible. Any way to update with the Moto G5+ bootloader?
Click to expand...
Click to collapse
You need bootloader open and yess you can flash safely it ks stock and battery is workimg awesome

LLegion said:
You need bootloader open and yess you can flash safely it ks stock and battery is workimg awesome
Click to expand...
Click to collapse
Sorry, I still a bit confused. The text I quoted says "bootloader stays MotoZ". If I install this update, as is, will my bootloader be MotoZ or remain Moto G5+?
Thanks...

I have the US version (retus), bootloader unlocked, nougat 7.0 with August patch (NPNS25. 137-93-18). Can I use this method safely? Thanks

I do not know what else to say...just flash as edpalined if phone breaks then unbrick it reading other tutos sorry pals but seems you are not reading enough

No risk no Win buddies

Hi, great write up! I like how your zip is a one stop shop. I used the included Moto G5+ toolkit to flash the stock Oreo zip which worked perfectly. I down graded to stock 7.1 from custom 9.0 however I'm noticing while on official Oreo whenever I reboot the device it will TWRP loop back into recovery and the only way to get back in the system is to go to bootloader and boot to system. Anyone else had this happen and fix it?
XT1867
OC.92 bootloader (unlocked)
TWRP 3.2.3.1

JohnSmith8786 said:
Hi, great write up! I like how your zip is a one stop shop. I used the included Moto G5+ toolkit to flash the stock Oreo zip which worked perfectly. I down graded to stock 7.1 from custom 9.0 however I'm noticing while on official Oreo whenever I reboot the device it will TWRP loop back into recovery and the only way to get back in the system is to go to bootloader and boot to system. Anyone else had this happen and fix it?
XT1867
OC.92 bootloader (unlocked)
TWRP 3.2.3.1
Click to expand...
Click to collapse
Do no flash from twrp but from runnimg the batch file oreo desde cero and it will flash the recobery as well to the oreo stock and thats it.buddie

No Baseband No Wifi and No imei

ok so my phone is a tmo moto z2 force and i have no base band wifi it says all info like the imei meid and such are not there
heres what i did i was trying to root the phone and i accidentally flashed the wrong boot.img on to the device but i had a backup on that img on my pc so i just re-flashed it and it broke everything so i thought well i will just download a flashall and do it that way i did and it just broke more the problem was is i only had a backup on the boot.img ifi had a backup i would just flash that but i dont so i guess im sol if someone has a flashall for the latest TMO firmware you will be my god

https://forum.xda-developers.com/z2-force/how-to/how-to-return-to-stock-sprint-t3694783

41rw4lk said:
https://forum.xda-developers.com/z2-force/how-to/how-to-return-to-stock-sprint-t3694783
Click to expand...
Click to collapse
i dont think this will work i think i have tried this exact one with no avail

As long as you didn't flash pie and lose your baseband that way, you can fix it.
If you're on stock just go to recovery and do a factory reset from there, it should bring your baseband back. However, if you've flashed a modem from a firmware not intended for your phone, then you need to reflash the correct firmware then recovery, factory reset. If you flashed pie not intended for your phone, you might be out of luck depending on what variant you have.

41rw4lk said:
As long as you didn't flash pie and lose your baseband that way, you can fix it.
If you're on stock just go to recovery and do a factory reset from there, it should bring your baseband back. However, if you've flashed a modem from a firmware not intended for your phone, then you need to reflash the correct firmware then recovery, factory reset. If you flashed pie not intended for your phone, you might be out of luck depending on what variant you have.
Click to expand...
Click to collapse
i know i didnt flash pie but i honestly dont know what im doing because i haven't ever messed with motos before i dont know what version of firmware was on it originally

NovaPlayzGames said:
i know i didnt flash pie but i honestly dont know what im doing because i haven't ever messed with motos before i dont know what version of firmware was on it originally
Click to expand...
Click to collapse
you can test different firmwares depending of your variant, even is not recomended ,look at the box phone the company and settings of your phone

hello friends, i have a problem, i have a z2 force, with android 8.0.0, retbr software channel, security patch from january 1, 2018, installed version number is opxs27.109-34-4.
In fastboot mode I have baseband not found, I have BL: MBM-3.0-nash_retail-641a15b-180105, in product and variant I have: Nash radio2 64GB PVT and lastly I have Flashing_locked, can anyone help me with which firmware I can try to recover the cell phone ?
Note: no data band and no wifi

fallcaoalves said:
hello friends, i have a problem, i have a z2 force, with android 8.0.0, retbr software channel, security patch from january 1, 2018, installed version number is opxs27.109-34-4.
In fastboot mode I have baseband not found, I have BL: MBM-3.0-nash_retail-641a15b-180105, in product and variant I have: Nash radio2 64GB PVT and lastly I have Flashing_locked, can anyone help me with which firmware I can try to recover the cell phone ?
Note: no data band and no wifi
Click to expand...
Click to collapse
Stick to one thread or create your own, posting the same problem in 20 different threads won't help you in any way.

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...