Develop Bugs

[Q] Note 3 User - Moving to LG G3 - Please Help?

Dear LG Friends,
Long time XDA member, coming from the Windows Phone days HTC, then to Android HTC, bunch of Samsungs, and am now thinking about the LG space. More specifically moving from the Note 3 (T-Mobile US) running on the AT&T US, to the LG G3.
Before I do, I need some help from you guys. Which variant should I go for? I know my primary choices will be the T-Mobile and the AT&T variants (I believe they are 851 and 850)? Based on what's important to me, below, can you guys advise which variant to get?:
1. Development Support - Which variant has the MOST amount of Custom ROM options, that is on-going and kept current? I am spoiled with the Note 3, which has a massive development support. I have never tried the LG OS/Skin (escaping me what it's called), but if it's anything like the TouchWiz on Samsungs, I think it will be important to have CM/AOSP/AOKP and etc support.
2. This is related to # 1 - But I heard that only T-Mobile has the unlocked Bootloader? However, doing some research, I believe the AT&T and the Verizon and Sprint variants can also be unlocked? Is this true? If so, are they anymore limited than the factory unlocked T-Mobile variant?
3. LTE bands - I will most likely be using the phone on AT&T US, but if development options/support are higher on other variants, I might consider buying those models, even if they are missing some AT&T bands. For the Note 3 - T-Mobile is a Pentaband phone, meaning it had all the bands needed, so it could easily work on AT&T LTE, all the time. The reverse was not true.
And basically that is it. Initial instinct says to go chase the T-Mobile variant, based on my needs above. But please educate me and help me out if I have missed something. Thank you so much in advance!

Any input guys?

ProFragger said:
Any input guys?
1. Development Support - Which variant has the MOST amount of Custom ROM options, that is on-going and kept current? I am spoiled with the Note 3, which has a massive development support. I have never tried the LG OS/Skin (escaping me what it's called), but if it's anything like the TouchWiz on Samsungs, I think it will be important to have CM/AOSP/AOKP and etc support.
Click to expand...
Click to collapse
If you want OTA updates i suggest sticking with the AT&T variant since you have a valid AT&T sim. If you use a AT&T sim in a T-Mobile variant you wont ever get OTA updates and that means missing out on necessary fixes
1. All 3 US Variants are mostly the same, all have CM12 and all the random obscure AOSP roms as well
2. Well unlocked bootloader isnt that fancy it just means theres fastboot mode compared with the other editions where fastboot mode doesnt work properly even if you enable it. It essentially just makes installing TWRP easier since you dont have to root before installing it unlike other variants
Nevertheless Lollipop can be rooted on all US Variants right now really easily. But the only downside to it is that removing custom roms sometimes can be a pain since you have to use a way where it sometimes works and sometimes doesnt

itsbighead said:
If you want OTA updates i suggest sticking with the AT&T variant since you have a valid AT&T sim. If you use a AT&T sim in a T-Mobile variant you wont ever get OTA updates
1. All 3 US Variants are mostly the same, all have CM12 and all the random obscure AOSP roms as well
2. Well unlocked bootloader isnt that fancy it just means theres fastboot mode compared with the other editions where fastboot mode doesnt work properly even if you enable it
Click to expand...
Click to collapse
Hi Friend,
Thanks for your response, this is very helpful!
No OTA is never a thing I consider. Everything that matters to me, is what I listed already.
So, is the development support (new ROMs, updates and etc) the same for all US variants or would you say one variant is particularly more popular?
As for the locked bootloader, I thought you needed an Unlocked bootloader to flash Custom ROMs, no? It seems like "Bump" fixes this for Verizon, Sprint, and AT&T and gets you TWRP on your phone, but do we need to do extra steps everything to the boot.img for non T-Mobile variants? Or is it a one time mod and then regular flashing and Backups with TWRP?
If it's the same for all variants after Bump, then you're right, I will likely stay with an AT&T variant, thanks to that Band 7 LTE.
Thank you again for your help, hopefully more can chime in !

ProFragger said:
Hi Friend,
Thanks for your response, this is very helpful!
No OTA is never a thing I consider. Everything that matters to me, is what I listed already.
So, is the development support (new ROMs, updates and etc) the same for all US variants or would you say one variant is particularly more popular?
As for the locked bootloader, I thought you needed an Unlocked bootloader to flash Custom ROMs, no? It seems like "Bump" fixes this for Verizon, Sprint, and AT&T and gets you TWRP on your phone, but do we need to do extra steps everything to the boot.img for non T-Mobile variants? Or is it a one time mod and then regular flashing and Backups with TWRP?
If it's the same for all variants after Bump, then you're right, I will likely stay with an AT&T variant, thanks to that Band 7 LTE.
Thank you again for your help, hopefully more can chime in !
Click to expand...
Click to collapse
No need for any steps. Its just install TWRP and your on your way to installing whatever rom you want
Unlocked bootloader means that the system doesnt security (consistency) checks on system partitions
For LG G3, its because someone cracked the encryption for the kitkat android bootloader which means people can sign non stock boot.img without having to worry about unlocking the bootloader.

itsbighead said:
No need for any steps. Its just install TWRP and your on your way to installing whatever rom you want
Unlocked bootloader means that the system doesnt security (consistency) checks on system partitions
For LG G3, its because someone cracked the encryption for the kitkat android bootloader which means people can sign non stock boot.img without having to worry about unlocking the bootloader.
Click to expand...
Click to collapse
Gotcha, thanks again mate! Another (hopefully last) question. If I buy G3, where someone had already OTA'd to 5.0+, will I still be able to root it, install TWRP and get KK ROMs, like CM11 or something?
And vice versa, if the phone comes with KK, do I need to patch with Bump and then I can install ROMs?
Thank you again!

ProFragger said:
Gotcha, thanks again mate! Another (hopefully last) question. If I buy G3, where someone had already OTA'd to 5.0+, will I still be able to root it, install TWRP and get KK ROMs, like CM11 or something?
And vice versa, if the phone comes with KK, do I need to patch with Bump and then I can install ROMs?
Thank you again!
Click to expand...
Click to collapse
You can root it but i dont know if installing TWRP will work. I didnt want to try it incase it doesnt work and it runs the factory reset script instead. That happened to me once before
But i would say just to be sure, downgrade back to KitKat to do it
Yeah, if the phone comes with KitKat just root, install TWRP using root permissions and then your on your way

itsbighead said:
You can root it but i dont know if installing TWRP will work. I didnt want to try it incase it doesnt work and it runs the factory reset script instead. That happened to me once before
But i would say just to be sure, downgrade back to KitKat to do it
Yeah, if the phone comes with KitKat just root, install TWRP using root permissions and then your on your way
Click to expand...
Click to collapse
This is helpful, once again bud. So how would I downgrade back to KK? Would I have to run a stock firmware of some sort? In Samsung, he Flash a .Tar file through their flashing tool called the Odin. Would that be similarly done here?

Why can't you update PRL and profile in Lineage and other customs - and can we fix it

So as I've looked into it, it appears that nothing has changed here in the 2-3 years since I last explored this issue. I'm talking about the fact that you can't successfully update PRL and profile on CDMA carriers in LOS and AOSP ROMS. The usual behavior if you even have the option in the UX is that you get a force close. I'd love to understand why this hasn't been addressed.. It's a huge reason someone would stay on stock over AOSP/LOS. I saw someone suggesting a Nexus 5 dev had some success using a couple of APKs including OmaDmclient.apk, and a few threads here and on Reddit talking about how it must've been broken by an AOSP contributor, but in any event it still doesn't work. Isn't this something that the LOS team could fix if they wanted to?

The issue with CDMA is that most of the stuff isn't open source. This is why the aosp source code is targeted to GSM. So I sought this will get fixed any time soon.

Same problem... I think
My neighborhood has excellent Sprint 4G LTE coverage and it's much faster than T-Mobile. I happen to use Ting (which allows you to choose between T-Mobile GSM and Sprint CDMA, although to switch from one to the other costs $20). GSM isn't really an option for me.
Anyway, I used to have this problem with my LG Volt LS740. I could work around it by forcing a PRL and profile update on stock and then flashing to Cyanogenmod.
That phone finally bit the dust. I have now inherited my wife's Moto G 2015 (osprey) XT1548. Really nice phone.... but the issue is, the latest stock I can find is Android 6.0. I can activate the phone and get great 4G LTE on stock, but to flash to Lineage OS 14.1 (or AOSP) I have to wipe the device. I simply can't get it to pick up the 4G LTE service on the custom ROM's (tried both). This is a real problem.
As I understand it (admittedly from reading Wikipedia), the PRL contains an "acquisition table" that prescribes the frequencies/modes that the device will communicate on... so I think that's probably my issue. After doing the prescribed wipes in the ROM installation documentation, flashing the ROM, and booting the device, I think I've lost the PRL somewhere in that process.
Is there some way to retrieve the PRL while the device is on stock and put it back when flashing custom? If the PRL is indeed stored on the R-UIM, should I just remove the R-UIM during the first boot? Maybe I'm wrong and the problem isn't really the PRL.
Any thoughts? Please don't tell me to switch to GSM. The GSM coverage here is just plain bad from both carriers who offer it in my neck of the woods.

I have this same exact question. Ting, N910P note 4 that was originally Sprint, and days-old Lineage 16 / Andorid 9.0 . The latest stock rom is 6.0.1, and works fine. Lineage 16 works 99% fine and I'd really rather use that. But LTE doesn't work. If I force it to use 3G only, it actually all works. data, voice, text, bluetooth, gps… and being Lineage, I don't have to try to surgically remove all the spyware and other crapware without breaking it. It's just not in there in the first place. I'd really rather use that.
I would be fine having to extract things from the stock rom and edit files or whatever if it were at least just known what needed to be done. I'm fine with the fact that Lineage nor anyone else can actually include and redistribute any carrier proprietary stuff.

it should be possible
Has anyone figured this out?
I too have devices on ting, fantastically built devices that run amazingly thanks to a solid construction, the support of many many developers who are craft some of the best ROMs for any device I've ever seen, considering the limited specs of the XT1031s. Fortunately/adequately enough though, they only run on 3G Sprint, Boost originally, moved to Ting for their great rates for FreedomPop customers when they bought them out.
Anyway, currently to get a device on ting, I have to flash the latest 5.1 official stock Boost Mobile Rom with the latest radio baseband and firmware and such. A process thats pretty involved. I'm hoping that I can backup the stock image using TWRP, as when I went through the process of reloading the official image through the individual files via mfastboot, I skipped the logo and recovery files, and since I was able to retain my custom logos for boot and bootloaderunlocked screens, and the recovery, I'm hoping to be able to make an image of the stock ROM, which if at all possible, I'm going to do my best to make as bare bones as possible. May start with flashing the bloatware removed version of stock thats available, then going through and removing basically every app on the phone with the exception of settings and anything to do with phone, phone/carrier services, sim toolkit, etc, so I can have the smallest image possible that could maybe be restored everytime/anytime that I want to update the PRL or Profile. Which it looks like theres a new version of each released at a minimum every 3 months, as I just activated another device this way and there was only an incremental update of the last digit. If this works, great. If it doesn't then I hope that theres an answer to the question in the initial post of this thread;
Is there a way to update the CDMA PRL and Profile on a device that is running a custom ROM? If so, is it something the ROM needs to specifically support or is it something that is possible to do with a bundle of apks? Like sim toolkit and the like?
If its ROM related, are there, or would it be possible to take the necessary components from the stock files and install them in Xposed or Magisk? Or perhaps the buttons in the settings panel of the stock rom simply executes a series of commands that can be executed within a terminal CLI on the custom ROM? I assume that since the custom ROM clearly has access to the 3G radio since I can make and recieve calls, I have data, and text messaging (haven't tried MMS, but I assume it works) so why couldn't it do one more thing and initiate the PRL update?
I assume that even the stock rom doesn't ever touch the PRL or Profile, seeing as they remain even after a user data wipe, and are available for the radio to continue to use with custom roms, which means that the radio chip has to be the one storing the PRL Profile, so I bet that the radio also directly downloads those files from the carrier when asked to do so, and the stock rom must only come into play for the base logicstics of it all such as radio-"is this prl/profile a newer version than the one that i have now?" and phone-"yes, download new, purge old, flash new, tell me when done and leave me alone" Since the radio doesn't have its own processor for those sorts of things perhaps? If thats the case, then that should imply that theres nothing particularly proprietary or licensed, etc, that a rom would explicitly need to have in order to initiate these updates since it would never directly need to touch/see the files, just know that they were updated and what version number they are. What also lends me to believe this is the case is the fact that you can't select to downgrade the prl/profile, rollback, or load one manually, at least not that I can see.
So basically I'm saying that I hope it should be something simple to do. And if it is simple to do, you would think that custom roms would be able to read the carrier correctly too? Right now my new device reads "Boost" still. My previous one when I got it on ting I wanna say actually read ting afterwards. But when I loaded ressurrection remix, I had no cell/data/voice nothing, It just kept asking me for a sim card, which this phone doesnt have at all. When I loaded Lineage, everything cell related work. But can't update prl/profile, and carrier reads as "3G Roming Indicator Off" Which idk why thats the case.
Perhaps I'm missing something
Perhaps custom roms are missing a few somethings.
The only sure thing is that carriers need to just not be so greedy/dumb/uselessly difficult, and make giving them money for service easier, preferably without questions. Or at the very least actually provide some security so all this nonsense is at least worth something in the end to the end user, instead of being done so that they can try to spy on your unencrytped texts and calls to sell to advertisers, and selling access to the higest bidders such as the government and bounty hunters, whilst preventing you from restricting that information.

Software update for Boost Mobile

I got the notification today.

guitardoc64 said:
I got the notification today.
Click to expand...
Click to collapse
Same Here
---------- Post added at 04:13 PM ---------- Previous post was at 04:12 PM ----------
guitardoc64 said:
I got the notification today.
Click to expand...
Click to collapse
have you saved the 66 mb zip ota update ? can you share it

If i install this update, would i still be able to unlock the bootloader and flash custom ROMs ? im on stock ROM.

sidgallup said:
If i install this update, would i still be able to unlock the bootloader and flash custom ROMs ? im on stock ROM.
Click to expand...
Click to collapse
YES

Welp... today i updated stock ROM to the latest version, after that i unlocked bootloader on Motos website, flashed TWRP, installed LineageOS and coudlnt get signal to connect to GSM, then flashed Resurrection Remix and same problem, everything works except calls, signal bars at at 0, no service.
This reminds me of some issues i had years ago and i needed to flash an older modem for calls to work.
Is anyone else having issues after updating to the latest stock ROM version?
EDIT: just confirmed theres something in the latest OTA that blocks GSM funcionality on custom ROMS, i did the exact same proccess with my brother's phone which is the same as mine, Boost E4, but this time without updating the stock ROM, just went directly to unlocking bootloader out of the box and this time is working perfectly.
I need some help now on how to go back to stock ROM and unlock mine.

It is really sneaky for them to do that! Anyone else run into the same problem? I am hoping to use my 1766 with GSM as well. Any luck reverting the changes?

nookin said:
It is really sneaky for them to do that! Anyone else run into the same problem? I am hoping to use my 1766 with GSM as well. Any luck reverting the changes?
Click to expand...
Click to collapse
Follow the instructions in my stock firmware thread here to restore your device to the most current stock Android OS and firmware config. https://forum.xda-developers.com/moto-e4/how-to/firmware-restoring-moto-e4-xt1766-t3820749
However, as far as downgrading your radio firmware, the bootloader (/aboot) has a feature that prevents downgrading. Attempting to downgrade the bootloader will trip a qFuse and hard brick your device. Sprint is notorious for network restricting their devices. They've been doing this for years. Downgrading the Android OS itself is no problem, but downgrading protected firmware partitions is next to impossible.

MotoJunkie01 said:
Follow the instructions in my stock firmware thread here to restore your device to the most current stock Android OS and firmware config. https://forum.xda-developers.com/moto-e4/how-to/firmware-restoring-moto-e4-xt1766-t3820749
However, as far as downgrading your radio firmware, the bootloader (/aboot) has a feature that prevents downgrading. Attempting to downgrade the bootloader will trip a qFuse and hard brick your device. Sprint is notorious for network restricting their devices. They've been doing this for years. Downgrading the Android OS itself is no problem, but downgrading protected firmware partitions is next to impossible.
Click to expand...
Click to collapse
I read the thread but it is not clear to me if this will solve my problem. From what I understand, the latest OTA blocks GSM usage. But I'm not sure if it also prevents me from using it with other MVNO. I don't see a way to edit APN. It lets me select from a list of Sprint APNs but none of them works. No way to edit or add.

nookin said:
I read the thread but it is not clear to me if this will solve my problem. From what I understand, the latest OTA blocks GSM usage. But I'm not sure if it also prevents me from using it with other MVNO. I don't see a way to edit APN. It lets me select from a list of Sprint APNs but none of them works. No way to edit or add.
Click to expand...
Click to collapse
On another CDMA, the difficulty will not be with the device itself, but rather with MEID whitelisting.

MotoJunkie01 said:
On another CDMA, the difficulty will not be with the device itself, but rather with MEID whitelisting.
Click to expand...
Click to collapse
I was able to register Boost Moto E4 with Tello. I can make phone calls but I cannot use any data (same account, so I know there should be data). The behavior is similar to GSM carriers before APN is setup. I am not sure if it is related to the update.

nookin said:
I was able to register Boost Moto E4 with Tello. I can make phone calls but I cannot use any data (same account, so I know there should be data). The behavior is similar to GSM carriers before APN is setup. I am not sure if it is related to the update.
Click to expand...
Click to collapse
Oh okay. That makes things clearer. With Boost Mobile being a Sprint owned subsidiary, and Tello being a Sprint affiliated MVNO, you are correct that with voice being functional, your data connection should likewise work. (Contrary to popular belief, Boost Mobile is not an MVNO and never has been.) I believe that, in your situation, the last OTA is likely not the problem, but rather with your ability -- or lack thereof -- to edit the APN settings. But, on a positive note, with root of the stock OS, using a root file editor can be used to manually modify your apns-config.xml file to add the 4G/LTE data and MMS parameters for Tello. I believe there are also root dependent apps which can edit APN settings.
Since your xt1766 is the Boost Mobile variant, your default APN & telephony parameters are configured specifically for Boost Mobile. I'm making an educated guess that using root permissions to add Tello data and MMS parameters should fix your issue.

Question LE2127 + Microsoft Intune problems

Hi,
First off I'm pretty new to the Forum so I'm just starting to understand some of the existing threads posted here.
My TMO OnePlus 9 Pro was updated to Android 12 back in March and since that time I've been having several issues the primary of which is that Microsoft Intune is no longer able to validate the configuration of my device. This has locked me out of company apps on my phone for the past several months and it's a real pain.
I looked into the issue and from what I can see it seems to be a bug in oxygen OS 12 relating to Android work profile. I have heard that this bug was fixed in later versions of oxygen OS but unfortunately T-Mobile have not made any new version available since March.
I tried converting my device to T-Mobile EU using the MSM tool and, while I was initially successful I wasn't able to get the T-Mobile modem to work on Android 12. I sent reverted back to T-Mobile US using that MSM.
The way I see it I have two options.
1. Wait and/or work with T-Mobile support to get a newer Oxygen OS build pushed to my device.
2. Figure out a way to fix the modem issues I was facing after upgrading to A12 following the EU MSM conversion.
Is there a fix available for the T-Mobile modem in Android 12? Sorry if it's been answered already but I couldn't find details anywhere despite searching. I'm looking for a no-root solution since that defeats the purpose of doing this to get Intune working.

SmartMart92 said:
Hi,
First off I'm pretty new to the Forum so I'm just starting to understand some of the existing threads posted here.
My TMO OnePlus 9 Pro was updated to Android 12 back in March and since that time I've been having several issues the primary of which is that Microsoft Intune is no longer able to validate the configuration of my device. This has locked me out of company apps on my phone for the past several months and it's a real pain.
I looked into the issue and from what I can see it seems to be a bug in oxygen OS 12 relating to Android work profile. I have heard that this bug was fixed in later versions of oxygen OS but unfortunately T-Mobile have not made any new version available since March.
I tried converting my device to T-Mobile EU using the MSM tool and, while I was initially successful I wasn't able to get the T-Mobile modem to work on Android 12. I sent reverted back to T-Mobile US using that MSM.
The way I see it I have two options.
1. Wait and/or work with T-Mobile support to get a newer Oxygen OS build pushed to my device.
2. Figure out a way to fix the modem issues I was facing after upgrading to A12 following the EU MSM conversion.
Is there a fix available for the T-Mobile modem in Android 12? Sorry if it's been answered already but I couldn't find details anywhere despite searching. I'm looking for a no-root solution since that defeats the purpose of doing this to get Intune working.
Click to expand...
Click to collapse
My TMo OP9P LE2127 had updated to OOS12 before I had a chance to root it. I hadn't read enough about it to worry about trying to block the update. Well, I hated OOS12 and I eventually downgraded back to Stock OOS11 and then converted it EU with the MSM tool. Currently running a rooted OOS11.2.10.10 on both slots.
Not once did I have to touch the modem and my 5G works just fine. Everything worked out of the box (aka conversion MSM). My phone is even still SIM locked. I believe others have experienced the same thing with a LE2127 that updated to the stock TMo OOS12 firmware. The modem seems to stick after that upgrade, even after downgrading it back to OOS11.
I've blocked my phone from manually checking for updates and I'm perfectly happy with my phone for the time being. That said, I have not tried updating my phone to any EU versions of OOS12 (C.48 being the latest, I think?).
So, that's my experience, but your mileage may vary.

SmartMart92 said:
Hi,
First off I'm pretty new to the Forum so I'm just starting to understand some of the existing threads posted here.
My TMO OnePlus 9 Pro was updated to Android 12 back in March and since that time I've been having several issues the primary of which is that Microsoft Intune is no longer able to validate the configuration of my device. This has locked me out of company apps on my phone for the past several months and it's a real pain.
I looked into the issue and from what I can see it seems to be a bug in oxygen OS 12 relating to Android work profile. I have heard that this bug was fixed in later versions of oxygen OS but unfortunately T-Mobile have not made any new version available since March.
I tried converting my device to T-Mobile EU using the MSM tool and, while I was initially successful I wasn't able to get the T-Mobile modem to work on Android 12. I sent reverted back to T-Mobile US using that MSM.
The way I see it I have two options.
1. Wait and/or work with T-Mobile support to get a newer Oxygen OS build pushed to my device.
2. Figure out a way to fix the modem issues I was facing after upgrading to A12 following the EU MSM conversion.
Is there a fix available for the T-Mobile modem in Android 12? Sorry if it's been answered already but I couldn't find details anywhere despite searching. I'm looking for a no-root solution since that defeats the purpose of doing this to get Intune working.
Click to expand...
Click to collapse
In order to get the modem working in A12, you have to have root and flash a Magisk module that fixes your build.prop. Unfortunately, your need to be unrooted prevents that from happening.
If you're OK with rooting temporarily, you could modify your build.prop to have "ro.vendor.oplus.radio.multisim.config=ssss" after flashing EU, then unroot afterwards by flashing stock boot.img.

razercortex said:
In order to get the modem working in A12, you have to have root and flash a Magisk module that fixes your build.prop. Unfortunately, your need to be unrooted prevents that from happening.
If you're OK with rooting temporarily, you could modify your build.prop to have "ro.vendor.oplus.radio.multisim.config=ssss" after flashing EU, then unroot afterwards by flashing stock boot.img.
Click to expand...
Click to collapse
Yeah, that could work. Does build.prop need to be updated after each OTA update?

SmartMart92 said:
Yeah, that could work. Does build.prop need to be updated after each OTA update?
Click to expand...
Click to collapse
Shouldn't need to be updated.
Also, you could try unlocking bootloader, rooting, modifying build.prop, unrooting, then relocking bootloader if you're ok with testing. It may/may not work. If it works, then you don't need to modify ever again, at least until a future update touches that file.

If I have no sims detected am I able to flash something to regain sim detection and data?

Question Oneplus 9 pro locate le2125 stock rom

before I root my phone I wanted to ensure I had a good stock rom to load in the event of an issue.
I'm currently running Oxygen OS 11.2LE15AA.
I can't find this exact version and I understand the AA versions are little different than the TMO versions. I believe this is the "global" version. There are some 11.2.xxx.AA versions, but not this specific one.
I investigated getting the image directly off the phone, but it appears you either need to have a rooted phone, or possibly installing TWRP (or other) and creating a backup. Then extract the image files from the backup.
I've rooted phones in the past, the last being my oneplus 3t. things have changed a lot since then. I've been studying up and want to make sure I get this right.
I really would like to have a golden (and trusted) image to fall back on.
Any insights are appreciated.
btw. I have two 9 pro's. my le2125 (cracked screen) i'm testing on, and a brand new le2127 (11.2.44.LE5ACB) I'll root after confirming I can root and restore these. The later is the TMO version.
I was planning on the Magisk root option. Looks like you can do it now without TWRP. I just want to debloat and Xposed. Magisk looks like it might have some interesting options I'll explore. For now I just want to locate a stock rom for 11.2LE15AA.
Thanks in advance.

ericaiken said:
before I root my phone I wanted to ensure I had a good stock rom to load in the event of an issue.
I'm currently running Oxygen OS 11.2LE15AA.
I can't find this exact version and I understand the AA versions are little different than the TMO versions. I believe this is the "global" version. There are some 11.2.xxx.AA versions, but not this specific one.
I investigated getting the image directly off the phone, but it appears you either need to have a rooted phone, or possibly installing TWRP (or other) and creating a backup. Then extract the image files from the backup.
I've rooted phones in the past, the last being my oneplus 3t. things have changed a lot since then. I've been studying up and want to make sure I get this right.
I really would like to have a golden (and trusted) image to fall back on.
Any insights are appreciated.
btw. I have two 9 pro's. my le2125 (cracked screen) i'm testing on, and a brand new le2127 (11.2.44.LE5ACB) I'll root after confirming I can root and restore these. The later is the TMO version.
I was planning on the Magisk root option. Looks like you can do it now without TWRP. I just want to debloat and Xposed. Magisk looks like it might have some interesting options I'll explore. For now I just want to locate a stock rom for 11.2LE15AA.
Thanks in advance.
Click to expand...
Click to collapse
here
OP9Pro - Repository of MSM Unbrick Tools (TMO, EU, GLO, IN)
By using these tools, you accept full responsibility for your actions. Your warranty is void should you run any of these utilities without OnePlus support present. I am not responsible for bricks, fires, nuclear war, etc. If you modified any...
forum.xda-developers.com

ericaiken said:
before I root my phone I wanted to ensure I had a good stock rom to load in the event of an issue.
I'm currently running Oxygen OS 11.2LE15AA.
I can't find this exact version and I understand the AA versions are little different than the TMO versions. I believe this is the "global" version. There are some 11.2.xxx.AA versions, but not this specific one.
I investigated getting the image directly off the phone, but it appears you either need to have a rooted phone, or possibly installing TWRP (or other) and creating a backup. Then extract the image files from the backup.
I've rooted phones in the past, the last being my oneplus 3t. things have changed a lot since then. I've been studying up and want to make sure I get this right.
I really would like to have a golden (and trusted) image to fall back on.
Any insights are appreciated.
btw. I have two 9 pro's. my le2125 (cracked screen) i'm testing on, and a brand new le2127 (11.2.44.LE5ACB) I'll root after confirming I can root and restore these. The later is the TMO version.
I was planning on the Magisk root option. Looks like you can do it now without TWRP. I just want to debloat and Xposed. Magisk looks like it might have some interesting options I'll explore. For now I just want to locate a stock rom for 11.2LE15AA.
Thanks in advance.
Click to expand...
Click to collapse
Apart from the MSM Tools linked by the previous poster, you have all the available stock ROMs listed HERE. Check whether you can find yours there.

Do not use the Indian MSM tool what ever you do. What 11.2.x.x version do you have....?

TheGhost1951 said:
Do not use the Indian MSM tool what ever you do. What 11.2.x.x version do you have....?
Click to expand...
Click to collapse
I have Oxygen OS 11.2LE15AA

TNSMANI said:
Apart from the MSM Tools linked by the previous poster, you have all the available stock ROMs listed HERE. Check whether you can find yours there.
Click to expand...
Click to collapse
thx. per that link
Global devices (LE2125) with build tag LE15AA zips use Google OTA servers, thereby making it impossible to capture full OTA zips under normal circumstances but Android major updates. However, should they be obtained or be posted on support website, they will be added.
and the website only has the latest 11.2.10.10.LE15AA
guess i'm screwed on getting a golden image. This really opens a can of worms for me. LE15AA are they really that special? Is there a know good sub version. I've seen 11.2.1.1.LE15AA images out there.

ericaiken said:
thx. per that link
Global devices (LE2125) with build tag LE15AA zips use Google OTA servers, thereby making it impossible to capture full OTA zips under normal circumstances but Android major updates. However, should they be obtained or be posted on support website, they will be added.
and the website only has the latest 11.2.10.10.LE15AA
guess i'm screwed on getting a golden image. This really opens a can of worms for me. LE15AA are they really that special? Is there a know good sub version. I've seen 11.2.1.1.LE15AA images out there.
Click to expand...
Click to collapse
It also goes on to say
LE2127 units are T-Mobile units running their own version of OxygenOS labelled LE5ACB and lack local update option in Settings --> System --> System Updates and are therefore not supported.
Which is my new replacement, so what does "not supported" mean for rooting it

This is my setup on LE2127 TMO variant. Firmware 11.2.9.9 ( I will stay on this for now because of some issues on A12), unlocked bootloader, rooted with Magisk, TWRP installed and a special script flashed which mounts partitions as R/W. I have complete control of my phone and that is what I expect when it is in fact "my phone" unlike a Galaxy phone that bootloader is unable to be unlocked..... As for a golden firmware to fallback on, are you wanting Global or TMO?