Can I downgrade OOS from v10.5.14 to v10.5.11 by simply flashing the full update with a local update? Or is the unbricker the only way to go back to an earlier version?
with past OnePlus devices, I've just used a flash all script. As long as the bootloader is installed, should be able to flash whatever you want to it. I have yet to try on the Nord N10 though. Only got mine today
I am new to OnePlus completely after years of using Moto devices. Thank you for the pointer on flash-all scripts. I found respective articles and unpacked the firmware. I will try the flash in the next days. This is essentially how I updated all my Moto devices before.
Related
Just received a xt1710-01 from ebay and it is in excellent condition. Still on 7.1.1
I currently have a Droid Turbo thats rooted, now I want to do this z2.
Question is where do I start? Links?
Thank you.
Unlock the bootloader (I guess you know how to do so), Flash or boot TWRP and from it flash Magisk. That should be all.
But see if you can get the latest Oreo update to run first. For a while Moto uses a kernel with a buggy implementation of F2FS so you need to flash a module with Magisk in order to get it to work.
Whew, well I managed to unlock the bootloader. This was my first time (virgin).
Is upgrading to Oreo worth it? It's nagging me to do a update now, but I wasn't sure. I love Kitkat on my Turbo so the latest isn't really important to me, but if you feel I should, I will.
Well I have spent about 2 hours reading and d/ling updates and finally Oreo. Still not comfortable doing the rooting till I understand the procedure more.
This looks doable. https://forum.xda-developers.com/z2-play/development/twrp-3-2-0-0-moto-z2-play-albus-t3715660
Dammit! I read instructions to do a full wipe. Blank phone now. Looking on how to reinstall stock rom.
Finally after 2 days I have a rooted Oreo Z2. To may damn different ways to restore a OS and to root out on the net.
... You only have to boot a TWRP image from fastboot and flash Magisk there. That works for any device with unlocked bootloader, you just have to find the fitting TWRP image.
Update: I managed to figure out that the Beta 08 predated the latest stable release 10.0.13, which I also found by searching. Since 10.0.13 is newer than Beta 08, I'm good.
This 7T is making me feel like I haven't spent the last six years reading XDA threads.
So I bought a 1907 converted to global firmware with the bootloader unlocked from Swappa. Now that it's here I find it has the open beta on it (OP7T_02_BETA_08) which I would prefer to roll back to stable. Something tells me there is not yet a roll back zip for this beta but a preliminary search didn't help. So if you know of a zip, tia.
Android 10 introduced a lot of powerful new tools to the Oneplus space and the only one I am familiar with is the fastboot roms (thanks! They're a lifesaver). I have not used the MSM tool, etc. I have never rolled back an OP beta. I can't even find a page about the OP 7T betas, although I assume the seller has the latest one on this phone. I'm ok using one of these tools if I do it now, since I have not yet put any personal data on the device.
As I see it these are my options from most desirable down:
1) Roll back to 10.0.12 or 10.0.13 assuming there is a roll back zip and I have instructions on how to use it.
2) Use a tool that is new to me to roll back.
3) Live with beta and simply root it via the fastboot flash method.
As for rooting the beta, can I use any of the prepatched boot img's here, which was my intention when I thought I was getting global stable? Or is the easiest thing to do just to boot the unofficial twrp and flash the latest Magisk zip (20.4?)? I think that's probably easiest.
So assuming a roll back to stable isn't possible now, and I root the beta by whatever means, how do I get back to stable eventually? I know this has been answered very often but I have never wanted to deal with betas over 3 different OP phones so if you'd indulge me with basic explanations/links I'd appreciate it. Thanks.
Download the OnePlus 7T - Global
Flash from your phone in the system settings then reboot, it will wipe everything after it boots back up go thru the setup quickly and do a factory reset one more time from the settings and your set. After that just download Oxygen Updater and catch up to the current update.
https://oxygenos.oneplus.net/OnePlus7TOxygen_14.O.10_OTA_010_all_2002022101_downgrade_0ab28576e1914b50.zip
Hey, I'm on 210817.036 (Nov. 2021) on an unlocked Pixel 6 Pro.
I was finally able to unlock it today from AT&T and wondering if I should update to the latest Android update before rooting.
Thanks for any advice!
I wouldn't bother, because OTAs take longer than flashing full firmware. i.e. As part of the rooting process, I would go ahead and flash the latest full firmware instead.
SDK Platform Tools
Get the Google USB Driver
Official Google Android Flash Tool
Oh OK! I didn't realize I could flash the full image of a higher version directly over an older version as part of this process. Thank you!
Oh and also I didn't know if patches above Nov. 2021 made things worse or not.
DevanteWeary said:
Oh OK! I didn't realize I could flash the full image of a higher version directly over an older version as part of this process. Thank you!
Oh and also I didn't know if patches above Nov. 2021 made things worse or not.
Click to expand...
Click to collapse
You're welcome!
I never had any issues at all, even with the fingerprint reader, from the end of October when I received mine through the second February patch. Hopefully, yours will be the same way.
At worst, once you unlock the bootloader if you have any issues with how things run, you can always flash any firmware you like. Be careful. You can also accidentally flash the wrong firmware. Coincidentally, I accidentally gave you a link to the official flashing site, which is good for staying stock unrooted, but if you're going to be rooted, I actually recommend the Pixel 6 Pro Factory Images. Just only ever use images that have Raven in the name as flashing the wrong thing can make it so that your phone would be unrecoverable.
Forgive me if I'm repeating anything you already know.
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?
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?