Related
Hello,
I received my oneplus 9 pro (global) the other day, and it's been working great. I rooted it no problem with a boot image I found on xda, and patched it using magisk manager. However, whenever I try to download the newest update, it fails every time. The first time it says that it's paused, and that it will continue whenever you press resume. I press resume, and then it says a problem occurred.
I tried to delete the .OTA folder, but it's no where to be found. I also tried to factory reset, as well as flashing the unpatched boot image, but it did not work.
Here's the link as to where I found the global boot image
[GUIDE] [Magisk] [Unlock / ROOT / Keep Root] OOS 13.1.0.500
Different variants of Magisk that are available for use : Magisk Variant Stable / Beta / Canary Release Official Android / OOS OOS 11 and above Maintainer topjohnwu Project Link GitHub Zygisk No...
forum.xda-developers.com
if it is not the right version, or if there's a way to restore the original boot image, please let me know!
Andrew8578 said:
Hello,
I received my oneplus 9 pro (global) the other day, and it's been working great. I rooted it no problem with a boot image I found on xda, and patched it using magisk manager. However, whenever I try to download the newest update, it fails every time. The first time it says that it's paused, and that it will continue whenever you press resume. I press resume, and then it says a problem occurred.
I tried to delete the .OTA folder, but it's no where to be found. I also tried to factory reset, as well as flashing the unpatched boot image, but it did not work.
Here's the link as to where I found the global boot image
[GUIDE] [Magisk] [Unlock / ROOT / Keep Root] OOS 13.1.0.500
Different variants of Magisk that are available for use : Magisk Variant Stable / Beta / Canary Release Official Android / OOS OOS 11 and above Maintainer topjohnwu Project Link GitHub Zygisk No...
forum.xda-developers.com
if it is not the right version, or if there's a way to restore the original boot image, please let me know!
Click to expand...
Click to collapse
Same here, was literally just googling for help.
vibrantliker said:
Same here, was literally just googling for help.
Click to expand...
Click to collapse
As far as I know, you can't take an OTA (incremental update) with either an unlocked bootloader or root. Not sure which of these is the actual culprit. I'm on the Global version (AA) and just flashed the full BA update. All is working well, only downside is that Dolby Atmos doesn't have the equalizer on the EU (BA) version. Everything else including 5G is working as it should, just like on previous versions of the OnePlus devices I've had (3T, 5, 6T, 7Pro and 8Pro).
zoman7663 said:
As far as I know, you can't take an OTA (incremental update) with either an unlocked bootloader or root. Not sure which of these is the actual culprit. I'm on the Global version (AA) and just flashed the full BA update. All is working well, only downside is that Dolby Atmos doesn't have the equalizer on the EU (BA) version. Everything else including 5G is working as it should, just like on previous versions of the OnePlus devices I've had (3T, 5, 6T, 7Pro and 8Pro).
Click to expand...
Click to collapse
I'm from the US, so I don't know if the network band will be the same, if so as good on the BA version.
If anything, i'll just wait for the official Global release on their website. It's just infuriating to see something that annoys me get fixed, such as the white navigation bar in split screen, and not being able to update.
Andrew8578 said:
I'm from the US, so I don't know if the network band will be the same, if so as good on the BA version.
If anything, i'll just wait for the official Global release on their website. It's just infuriating to see something that annoys me get fixed, such as the white navigation bar in split screen, and not being able to update.
Click to expand...
Click to collapse
I'm in the USA and the bands (TMobile) work fine. No difference that I can see on this device or previous using the BA builds until the AA builds get going. Every OnePlus device has been this way for me.
Andrew8578 said:
I'm from the US, so I don't know if the network band will be the same, if so as good on the BA version.
If anything, i'll just wait for the official Global release on their website. It's just infuriating to see something that annoys me get fixed, such as the white navigation bar in split screen, and not being able to update.
Click to expand...
Click to collapse
You may not want to hold your breath on that one. For whatever reason, oneplus does not release full OTA zips for AA half the time. (WTF ONEPLUS). Because of this, I long since started flashing BA over my global phone. As the gentleman said up above, it works absolutely perfectly.
zoman7663 said:
As far as I know, you can't take an OTA (incremental update) with either an unlocked bootloader or root. Not sure which of these is the actual culprit. I'm on the Global version (AA) and just flashed the full BA update. All is working well, only downside is that Dolby Atmos doesn't have the equalizer on the EU (BA) version. Everything else including 5G is working as it should, just like on previous versions of the OnePlus devices I've had (3T, 5, 6T, 7Pro and 8Pro).
Click to expand...
Click to collapse
can I just flash the BA version on top of my current rom (AA) and not lose anything? I just got done reinstalling everything, and it was a pain. I don't want to do this a 3rd time, if I can avoid it.
I never had any issues with rooting/being unlocked and updating on my previous OnePlus phones... this is a new one for me.
On 8t I had to use EU..google is who releases OTAs for all variants except EU, which is still directly from oneplus. Rooting broke OTAs for me as well on any other rom besides EU...also I have 9pro, which I local updated to EU zip b4 flashing magisk_boot.img and I already received new update since rooting and all is good.
I just flashed BA on top on my current rom via system update (you have to click the cog wheel top right and put the OTA zip on your root directory)
Nothing changed and the navigation bar in split screen is indeed fixed, meaning this is the latest version.
Thanks again for letting me know about this!
zoman7663 said:
As far as I know, you can't take an OTA (incremental update) with either an unlocked bootloader or root. Not sure which of these is the actual culprit. I'm on the Global version (AA) and just flashed the full BA update. All is working well, only downside is that Dolby Atmos doesn't have the equalizer on the EU (BA) version. Everything else including 5G is working as it should, just like on previous versions of the OnePlus devices I've had (3T, 5, 6T, 7Pro and 8Pro).
Click to expand...
Click to collapse
zoman7663 said:
I'm in the USA and the bands (TMobile) work fine. No difference that I can see on this device or previous using the BA builds until the AA builds get going. Every OnePlus device has been this way for me.
Click to expand...
Click to collapse
I'd be careful about flashing an international build for a global variant as EU regulations could be stricter, and most times are, with respect to signal strength, emissions, and other factors. Might work fine now, but there are different variants for a reason and one specific to the EU for a reason (laws are vastly different).
bulletbling said:
I'd be careful about flashing an international build for a global variant as EU regulations could be stricter, and most times are, with respect to signal strength, emissions, and other factors. Might work fine now, but there are different variants for a reason and one specific to the EU for a reason (laws are vastly different).
Click to expand...
Click to collapse
Noted, thanks for the info.
So best way then is to unroot and hope that the problem is not because of the bootloader? What's the safest way to unroot these phones. I'm on AA version (I'm new to One Plus, previously used Pixel 2 XL)
drmorrowa2 said:
So best way then is to unroot and hope that the problem is not because of the bootloader? What's the safest way to unroot these phones. I'm on AA version (I'm new to One Plus, previously used Pixel 2 XL)
Click to expand...
Click to collapse
What I want to know too!
drmorrowa2 said:
So best way then is to unroot and hope that the problem is not because of the bootloader? What's the safest way to unroot these phones. I'm on AA version (I'm new to One Plus, previously used Pixel 2 XL)
Click to expand...
Click to collapse
To unroot, go into magisk and click uninstall. Do know that I have tried this already and system update still won't go through. It appears it's being picky about the bootloader being unlocked I think. This is weird because on my OnePlus 7 pro, I did not have this issue and all I had to do was go to Magisk, uninstall ---> restore images, then do the OTA, and then have Magisk install to second slot, and then I would go back to system update, allow it to reboot, and I would still be rooted.
bulletbling said:
To unroot, go into magisk and click uninstall. Do know that I have tried this already and system update still won't go through. It appears it's being picky about the bootloader being unlocked I think. This is weird because on my OnePlus 7 pro, I did not have this issue and all I had to do was go to Magisk, uninstall ---> restore images, then do the OTA, and then have Magisk install to second slot, and then I would go back to system update, allow it to reboot, and I would still be rooted.
Click to expand...
Click to collapse
geez, I hope we don't have to relock and unlock for every update. I guess for the time being, there's no reason to be unlocked, but when custom ROM's start rolling out, that's going to be a major headache. I wonder if/when the updates are posted on One Plus website, will the updates work, or will root/unlock still prevent it?
I really want that update as I'm reading it made the battery much better. What to do!
I'm curious. so for a brand new phone why are you guys rooting it? It is not loaded with bloat ware (at least as much as samsung fpr example.) there are no custom roms yet, and oneplus is pushing updates to fix bugs. I think I'll wait till custom roms show up and then consider rooting.
TPXX said:
I'm curious. so for a brand new phone why are you guys rooting it? It is not loaded with bloat ware (at least as much as samsung fpr example.) there are no custom roms yet, and oneplus is pushing updates to fix bugs. I think I'll wait till custom roms show up and then consider rooting.
Click to expand...
Click to collapse
I root only for Viper4android but I'd like to unroot and relock bootloader again if it means I can get the updates.
I never reverse this process though. What are the best steps?
vibrantliker said:
I root only for Viper4android but I'd like to unroot and relock bootloader again if it means I can get the updates.
I never reverse this process though. What are the best steps?
Click to expand...
Click to collapse
My last rooting experience was on an S7. Afraid I can't help you with this one.
Hi
I dont have signal on my cellular now after the updating...
There is a Temporary fix until the next update ?
I have the same problem. I can't even downgrade
New version 22.0.0.0 and no signal bug. Omfg
Having trouble since open beta 1 in receiving and placing calls, crazy what 1+ is releasing
12 sounds is shaky at best
12 stable managed to brick my phone almost.
Had to use all sort of tricks to get out of Crashdump Mode. But you can get out.
Anyway. It's a mess.
I have network but the whole OS feels SO unbaked. My phone is stuck in 60hz most of the time. Apps, functionality is missing. Things we've had in OOS. It's crap, I am sorry I'm going to say it like that.
This is a DOWNGRADE.
I wonder how 1+'s forums will look like after people storm it.
Anyway. You can downgrade with MSMTool, but it will wipe your data and you start from the stock OS.
Guess you can download latest OOS11, and Local Upgrade via System Update and disable update.
That's my plan at least.
You can also try using custom roms, but I am unsure about their stability (yet).
I'm still hoping they will release 12.0.0.1 this night
Jomsha said:
Hi
I dont have signal on my cellular now after the updating...
There is a Temporary fix until the next update ?
Click to expand...
Click to collapse
Same issues here
Indian version
Eslam.hanafy said:
Same issues here
Indian version
Click to expand...
Click to collapse
Ob2 did that already. No sim if 5g is turned on..Gonna root later, no big deal
Jomsha said:
Hi
I dont have signal on my cellular now after the updating...
There is a Temporary fix until the next update ?
Click to expand...
Click to collapse
try this method i posted in a thread, and let me know..
OOS 12.0.0 Stable Update Cellular Network Fix
Hi, As you may know most of us is having this issue after the OOS 12.0.0 Stable Update, Cellular Network lost, No Signal, Outgoing call, and SMS. The below method worked at least for me, let me know if worked with anyone of you please. Please...
forum.xda-developers.com
h8Aramex said:
12 stable managed to brick my phone almost.
Had to use all sort of tricks to get out of Crashdump Mode. But you can get out.
Anyway. It's a mess.
I have network but the whole OS feels SO unbaked. My phone is stuck in 60hz most of the time. Apps, functionality is missing. Things we've had in OOS. It's crap, I am sorry I'm going to say it like that.
This is a DOWNGRADE.
I wonder how 1+'s forums will look like after people storm it.
Anyway. You can downgrade with MSMTool, but it will wipe your data and you start from the stock OS.
Guess you can download latest OOS11, and Local Upgrade via System Update and disable update.
That's my plan at least.
You can also try using custom roms, but I am unsure about their stability (yet).
Click to expand...
Click to collapse
How did you get into edl mode running A12?
My network doesn't work on OOS12 stable for some reason. I spent 2 days flashing different oos12 builds (eu, global, indian) to try to see if the network comes back, tried literally everything but no luck
Very disappointed. Had to come back to OOS11. Everything works perfectly, except the fact that I'm not running the latest android version on my flagship 9 Pro.
Read my post here. And back through a few others.
jruizdesign said:
I was getting the same issue, but flashing a different variant of your current c.44 should do the trick.
Ex: I have a LE2127 (TMO), I converted with a11 to use LE2123(EU) software updates. When android 12 hit my phone wouldn't give me data on the 2123 update, so I had to download the LE2125(global/NA) update and flash using the the system update app that was so generously given in the following post:
Post in thread '[TMO] 9 PRO MODEM RETENTION' https://forum.xda-developers.com/t/tmo-9-pro-modem-retention.4292445/post-86328243
I don't know what software or model your phone is now, so I am NOT suggesting you switch if you are not already on 2123 or 2125. Those two are interchangeable without problem so it should be fine
Click to expand...
Click to collapse
I don't know anything about the Indian variant so I'm not sure if the same fixed will work.
But I can tell you I have tried every msm tool and almost every possible variant an no matter what goes wrong there has been a fix here in the these forums already.
Currently running lastest c.44 global LE2125 A12 on my TMo LE2127 model device with ZERO bugs so far. Data works flawlessly
khanboy619 said:
My network doesn't work on OOS12 stable for some reason. I spent 2 days flashing different oos12 builds (eu, global, indian) to try to see if the network comes back, tried literally everything but no luck
Very disappointed. Had to come back to OOS11. Everything works perfectly, except the fact that I'm not running the latest android version on my flagship 9 Pro.
Click to expand...
Click to collapse
Did you read the data retention thread and msm using the given tool in that thread ONLY? If you use that msm tool, the take the local update to 11.2.9.9 then update the your variant of C44 you should have no issues.
jruizdesign said:
Did you read the data retention thread and msm using the given tool in that thread ONLY? If you use that msm tool, the take the local update to 11.2.9.9 then update the your variant of C44 you should have no issues.
Click to expand...
Click to collapse
Are you sure about this?? Because I flashed OOS12 by first flashing OS 11.2.8.8 through MSM tool and then updating to android 12.
Do you think flashing 11.2.9.9 will actually work, because I'll have to through the hastle of downgrading and then updating again. (As I'm running 11.2.10.10 atm)
The help is much appreciated.
h8Aramex said:
12 stable managed to brick my phone almost.
Had to use all sort of tricks to get out of Crashdump Mode. But you can get out.
Anyway. It's a mess.
I have network but the whole OS feels SO unbaked. My phone is stuck in 60hz most of the time. Apps, functionality is missing. Things we've had in OOS. It's crap, I am sorry I'm going to say it like that.
This is a DOWNGRADE.
I wonder how 1+'s forums will look like after people storm it.
Anyway. You can downgrade with MSMTool, but it will wipe your data and you start from the stock OS.
Guess you can download latest OOS11, and Local Upgrade via System Update and disable update.
That's my plan at least.
You can also try using custom roms, but I am unsure about their stability (yet).
Click to expand...
Click to collapse
The easiest way to crashdump after this update is trying to flash your modem files like you would of you of on a11.
jruizdesign said:
The easiest way to crashdump after this update is trying to flash your modem files like you would of you of on a11. Easy fix with msm to stock and try again
Click to expand...
Click to collapse
khanboy619 said:
Are you sure about this?? Because I flashed OOS12 by first flashing OS 11.2.8.8 through MSM tool and then updating to android 12.
Do you think flashing 11.2.9.9 will actually work, because I'll have to through the hastle of downgrading and then updating again. (As I'm running 11.2.10.10 atm)
The help is much appreciated.
Click to expand...
Click to collapse
No 11.2.10.10 you get the same result no need to downgrade.
Amd4life said:
How did you get into edl mode running A12?
Click to expand...
Click to collapse
Same way you would in android 11.
Make sure the phone is completely off. Hold volume up and volume down buttons, and plug it in.
Make sure you already have the msm tool fully opened and ready to click enum.
As soon as you plug it in it should say ok ok in the tool, click enum then start.
I stress that point to do it quickly because it will fail with different errors if it's not done quick enough after the device is plugged in.
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?
Hello everyone,
I have a problem. I tried installing Nameless ROM on my OnePlus 9 Pro with no success. After that I reflashed my phone using MsmTool. Than I've updated it do 11.2.10.10 and later to C.47. But when I installed C.47 phone rebooted to recovery and when I selected reboot It wouldn't boot. Don't know what I'm doing wrong. My bootloader is locked.
Which phone version do you have?
luckylui said:
Which phone version do you have?
Click to expand...
Click to collapse
You mean software version or phone model?
Right now I'm on 11.2.10.10
My phone model is LE2120
skrubxgt said:
You mean software version or phone model?
Right now I'm on 11.2.10.10
My phone model is LE2120
Click to expand...
Click to collapse
Phone model.
So, I'd try it this way..
Since you are already on 11.2.10.10, I'd unlock the bootloader. (It'll wipe the device)
Download Oxygen Updater and download the stock versions through their.
Local update through your phone settings.
Once you are on A12 I'd follow the steps to installing Nameless.
My phone model is 2127 and I'm running Pixel Experience with no issues.
luckylui said:
Phone model.
So, I'd try it this way..
Since you are already on 11.2.10.10, I'd unlock the bootloader. (It'll wipe the device)
Download Oxygen Updater and download the stock versions through their.
Local update through your phone settings.
Once you are on A12 I'd follow the steps to installing Nameless.
My phone model is 2127 and I'm running Pixel Experience with no issues.
Click to expand...
Click to collapse
Oxygen Updater shows C.47 is available, should I install it?
Yes, download it and local update through the phone settings.
Keep in mind you will need to unlock your bootloader in order to flash a custom Rom.
luckylui said:
Yes, download it and local update through the phone settings.
Keep in mind you will need to unlock your bootloader in order to flash a custom Rom.
Click to expand...
Click to collapse
Well it didn't work, local update wouldn't allow me to install it.
skrubxgt said:
Well it didn't work, local update wouldn't allow me to install it.
Click to expand...
Click to collapse
I wonder if you need to unlock the bootloader and root? I can't test it out unfortunately since I'm on the Pixel Rom :/
luckylui said:
I wonder if you need to unlock the bootloader and root? I can't test it out unfortunately since I'm on the Pixel Rom :/
Click to expand...
Click to collapse
I wonder why I can't install official update, when I installed C.47 it just bootloops. Tried installing Global, India and EU builds but after all it is the same situation.
skrubxgt said:
I wonder why I can't install official update, when I installed C.47 it just bootloops. Tried installing Global, India and EU builds but after all it is the same situation.
Click to expand...
Click to collapse
Yeah, that is very weird.
I wonder if something with your phones partitions got messed up, but I would figure doing an MSM restoration would bring everything back.
luckylui said:
Yeah, that is very weird.
I wonder if something with your phones partitions got messed up, but I would figure doing an MSM restoration would bring everything back.
Click to expand...
Click to collapse
Tried restoring it using MsmTool, still nothing
I have exactly the same problem, except my device is a LE2123. Running the stock version that came out of the box. 11.2.10.10.LE15BA. down load and install seem to be ok, but at the point to reboot the device loop several times and then recovers to 11.2.10.10....
If you guys are going custom Rom, I would just go ahead and install the custom Rom. Looks like the firmware will carry over once you transition. Maybe that'll work out better than updating to the next available stock firmware.
luckylui said:
If you guys are going custom Rom, I would just go ahead and install the custom Rom. Looks like the firmware will carry over once you transition. Maybe that'll work out better than updating to the next available stock firmware.
Click to expand...
Click to collapse
Yea, if you want a custom ROM, just do it and follow the instructions to the letter....
TheGhost1951 said:
Yea, if you want a custom ROM, just do it and follow the instructions to the letter....
Click to expand...
Click to collapse
I have the 2127 Tmo model and was on C.19 version. Downloaded and installed Pixel Experience Rom which is C.62 and it works fine. But, I have heard C.19 is pretty much C.62 and Pixel Rom you can install it on any version.. not sure about Nameless though. Worst case scenario is you would have to MSM back (which I know is a pain) but, I guess gotta try whatever works.
luckylui said:
I have the 2127 Tmo model and was on C.19 version. Downloaded and installed Pixel Experience Rom which is C.62 and it works fine. But, I have heard C.19 is pretty much C.62 and Pixel Rom you can install it on any version.. not sure about Nameless though. Worst case scenario is you would have to MSM back (which I know is a pain) but, I guess gotta try whatever works.
Click to expand...
Click to collapse
Hi my friend, I am on TMO with Model LE2127 running stock 11.2.9.9 and happy as a Lark. I got rid of bloatware, full root with partitions mounted as R/W, custom bootanimation and custom systemwide font. With just Magisk Root, you are not fully rooted. And stock OOS 12 is squirrelly anyway. The latest is not always the greatest.....hope you are having a great day! TheGhost!
To me, the main reason for root on any smartphone is to be able to customize it anyway you like without having to go and find this module or that module for Magisk. I tried the custom font module for Magisk and it was not systemwide. The way I am rooted, even the keys on the keyboard are changed to the custom font I have installed....if you don't have complete control of your phone, you are not truly rooted!
TheGhost1951 said:
Hi my friend, I am on TMO with Model LE2127 running stock 11.2.9.9 and happy as a Lark. I got rid of bloatware, full root with partitions mounted as R/W, custom bootanimation and custom systemwide font. With just Magisk Root, you are not fully rooted. And stock OOS 12 is squirrelly anyway. The latest is not always the greatest.....hope you are having a great day! TheGhost!
Click to expand...
Click to collapse
Hello, TheGhost! Glad to see an old timer on the forums from many moons ago! We've seen it all and still learning till this day as technology develops. Totally agree with ya and it sure does make a difference once you take full control of your phone. That's why Android will always be my go to! Cheers to ya!!
luckylui said:
Hello, TheGhost! Glad to see an old timer on the forums from many moons ago! We've seen it all and still learning till this day as technology develops. Totally agree with ya and it sure does make a difference once you take full control of your phone. That's why Android will always be my go to! Cheers to ya!!
Click to expand...
Click to collapse
You bet my friend,
I had a similar problem on my 9 with the C.48 ROM. I ended up MSM back to stock, unlocked the bootloader, then took the OTAs and it downloaded the full ones. All those flashed fine, then it got stuck at C.60 and said I was up to date so I had to grab the C.62 full India OTA and flashed that and now I'm back up to date.
I'm assuming based on the version and model that you're running the EU ROM? If so, grab Oxygen Updater and download the full OTA of C.62 from it (turn on advanced setting so you can select incompatible images, select EU full). Take that and copy to PC. Download Fastboot Enhance, reboot to fastbootd (adb reboot fastboot). Double click when it shows your device, go to partitions page. Search cow and select and delete each one you find there individually (you just keep searching cow after you delete each one, no idea why the program wasn't designed to just let you select all of them at once and delete them, maybe it's a safety design for dumb people). Then click flash payload.bin and choose the C.62 zip file you downloaded and it will flash to your phone. Reboot to system and you should be good to go.
Fastboot Enhance doesn't have all the checks that the regular updater does so as long as it's a full OTA and it's not corrupted, it should flash fine.
If you screw anything up, it's time to MSM again. Annoying but that's how it goes with these frustrating OnePlus devices.
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?