Switch from OB6 to 10.0.2 - OnePlus 7 Pro Questions & Answers

I'm really suffering with battery life on Open Beta 6 so I want to switch to 10.0.2, but the question is how?
I've found downgrade packages to Android 9, but I haven't found a similar package for 10.0.2

As you've likely found. Can't be done directly (yet). Back to Pie, then up to stock 10

Yes, that's what I ended up doing, back to pie then upgrade to Q

Related

OOS 9.0.9 needed before updating to Android 10 (FYI)

I was having a bunch of issues updating my phone. I kept receiving a System Update Installation Failed error. I tried local using the zip downloaded directly from OnePlus support and it wouldn't work. It said that there was no update available when trying to use the update setting. Long story short...it just wasn't working. I then proceeded to use the MSM Tool to completely erase and reset the phone. STILL wouldn't work. I randomly came across someone saying you needed OxygenOS 9.0.9 before 10..tried it and it worked perfectly. Sigh.
I wanted to save someone else the hassle and document it here with the error I was receiving. Good luck! I got OOS 9.0.9 HERE if anyone needs it and I'm allowed to link.
@bam099
Thanks for sharing the link for 9.0.9
Out of interest which version were you upgrading from and which version MSM tool were you trying?
My OP6 is still on 9.0.8 as I've not had the inclination to go through the hassle of a full reset to restore to factory (BL is unlocked, TWRP is installed, was rooted but got rid of that due to constant hassle with banking apps detecting root and magisk hide not working for all my bank apps)
Now that 11 is released as stable I'm probs going to to the full return to factory stock and then upgrade straight to 11 (once the early adopters have found the first bugs and OP patch them ) but if 9.0.9 was needed to update to 10.x.x I guess the same will be needed for 11.
Surprisingly I took a little bit of notes so I could go back if I wanted to (and I wouldn't waste time searching for issues like this weird 9.0.9 thing I found). I was on 9.0.6 (Build Number A6003_22_190528).
I would imagine that 9.0.9 is going to be needed to get to 11 (I'm on 11 now but I went from 10 so I'm not positive about what is required).
If you download the stock ROM for 9.0.9 can't you upgrade it? I THINK TWRP can flash the update but I'm sure there's some kind of an issue with an unlocked BL and upgrading via the stock app.
I don't recall what version of the MSM tool I used...I was frustrated at that point and not taking notes haha. I keep remembering 4.0.4 so if that sounds right for MSM then that's what I used. But I think any of the ones you see on a guide would work. Good luck with it!

Question Is there a guide on how to downgrade to android 11 and one ui 3.1 after Android 12 and one ui 4 garbage?

Looking to revert back to android 11 and need to know what to do to not brick my phone.
Currently have an unlocked galaxy s21 plus, Odin is installed and so is a 4 file firmware package for Android 11..
I have USB debugging checked and most things backed up before I perform a factory reset..
Is there anything else that I'm missing, am I completely wrong? Sorry, it's been a long time since I've done anything like this
As long as it wasn't a OTA upgrade that also updated the bootloader version you should be able to roll back.
Make sure all critical data is redundantly backed up. Verify it's all there and readable.
So did you succeed in this?
Edit: It's downgradeable ez pz. Just download the latest Android 11 and flash via Odin. I have the Exynos version.
0rigin said:
So did you succeed in this?
Edit: It's downgradeable ez pz. Just download the latest Android 11 and flash via Odin. I have the Exynos version.
Click to expand...
Click to collapse
But what if the bootloader was updated? Maybe Snapdragon is different
JeffATL said:
But what if the bootloader was updated? Maybe Snapdragon is different
Click to expand...
Click to collapse
Probably. On the N10+'s snaps apparently it's not so you can roll back from 12 to 11 but no further. I'm still running Pie and 10 on my N10+'s and will not upgrade either.
blackhawk said:
Probably. On the N10+'s snaps apparently it's not so you can roll back from 12 to 11 but no further. I'm still running Pie and 10 on my N10+'s and will not upgrade either.
Click to expand...
Click to collapse
11 is the best iteration out of all mentioned, so I recommend you upgrade to that at least. 12 was a beta testing software, but 13 is again a step in the right direction and OneUI 5 is really becoming a powerhouse. Now if only they got rid of the bloatware, but that's also easier than ever to manage nowadays.
JeffATL said:
But what if the bootloader was updated? Maybe Snapdragon is different
Click to expand...
Click to collapse
You'll have more luck finding answers in the S21 Ultra section. Can't remember the exact bootloader versions, but if it's one of the later ones, you won't be able to revert. Android 12 is a piece of trash.
0rigin said:
11 is the best iteration out of all mentioned, so I recommend you upgrade to that at least. 12 was a beta testing software, but 13 is again a step in the right direction and OneUI 5 is really becoming a powerhouse. Now if only they got rid of the bloatware, but that's also easier than ever to manage nowadays.
Click to expand...
Click to collapse
I doubt that as cpu cycle sucking scoped storage is fully active on 11 and above. On Android 9 and 10* it isn't. Not willing to risk screwing up 2 fast, stable, clean running machines that are fulfilling their mission by changing the firmware. To hell with global elitist Google's disinformation and hype Gookill... I see you
Not vaxing my N10+'s either☠
Bloatware is easy to stop from at boot up on stock Samsung's with Package Disabler (not on Playstore). Fastest and easiest solution.
*haven't used my N10+ Android 10 much so I need to do a comparison with my other one loaded with Pie. Will a 2 5+ yo Pie load beat out a freshly loaded and configured Q load? Q seems to get slightly worse SOT, so far, but I need to play with it more as it may not be fully dialed in yet.
My oldest N10+/N975U/Pie runs like a bat out of hell. It's current load is 2.5+yo. It is my most stable platform of any OS in the last 18 years.

Question Anyone get OxygenOS 12.0.0 to install?

I downloaded it. Went to local upgrade, installed it.
Went to Magisk and did install to inactive slot like normal. And it reboots. Then a small bootloop for a second. Then goes straight back to normal. Like I never installed anything.
Any thoughts?
I tried to root by patching new boot.img but get bootloop which not fixed except after msmdownload tool
All data wiped
Root OnePlus 9, 9 Pro, 9R Android 12 ColorOS 12 via Magisk
Thi guide will show you how to root the OnePlus 9, OnePlus 9 Pro, and OnePlus 9R running ColorOS 12 Android 12 via Magisk Patched Boot.img
www.droidwin.com
The temporary root method at the end of this page worked for me on A12 stable
illusiveairforce said:
I downloaded it. Went to local upgrade, installed it.
Went to Magisk and did install to inactive slot like normal. And it reboots. Then a small bootloop for a second. Then goes straight back to normal. Like I never installed anything.
Any thoughts?
Click to expand...
Click to collapse
Same here. If you dont install magisk to the inactive slot it will go through and you will be in oos12. Problem with mine, it wont read my flaking sim card. Tried it 5x all same problem. Also, every reboot, your dpi goes back to 360 lmao.
I patched boot.img by canary magisk and it is working good, but no option for safetynet passing
sbute said:
Root OnePlus 9, 9 Pro, 9R Android 12 ColorOS 12 via Magisk
Thi guide will show you how to root the OnePlus 9, OnePlus 9 Pro, and OnePlus 9R running ColorOS 12 Android 12 via Magisk Patched Boot.img
www.droidwin.com
The temporary root method at the end of this page worked for me on A12 stable
Click to expand...
Click to collapse
I used this guide but patched with magisk 23.0. still have all my modules and passing safety net. Using latest stable magisk 23.0 righteous. Thank you for this. I tried for 3 days killing my device flashing boot img. At least I know my downloaded msm tool works. On latest A12 build out for the global op9
I wouldnt recommend it tbh if its your only phone. Its buggy AH.
mattie_49 said:
I used this guide but patched with magisk 23.0. still have all my modules and passing safety net. Using latest stable magisk 23.0 righteous. Thank you for this. I tried for 3 days killing my device flashing boot img. At least I know my downloaded msm tool works. On latest A12 build out for the global op9
Click to expand...
Click to collapse
Would you or anyone else mind sharing the boot img for the OnePlus 9: OOS/Android 12 ?
I have the Global / NA version.
It would be greatly appreciated!
Zethiel said:
Would you or anyone else mind sharing the boot img for the OnePlus 9: OOS/Android 12 ?
I have the Global / NA version.
It would be greatly appreciated!
Click to expand...
Click to collapse
I have on my PC I will upload soon. Away from it currently. You really need 3 partitions to make work. Boot,vendor_boot,vbmeta
Geesh the battery is so much better on A12 after debloating how I see fit. Passing safety net, all banking apps working and still using old modules !! Score
mattie_49 said:
I have on my PC I will upload soon. Away from it currently. You really need 3 partitions to make work. Boot,vendor_boot,vbmeta
Click to expand...
Click to collapse
That would be greatly appreciated Sir!
0p9 partitions..A 12 - Google Drive
drive.google.com
All three are in here. Make sure to use magisk 23.0 to patch boot and vendor boot so you don't loose modules and magisk hide. Then you disable verity before boot with vb_meta img. You have to do from sdk platform tools folder though. Will not work just putting in a folder on desktop and pulling cmd window from there. Enjoy , follow the above guide to a T
Zethiel said:
That would be greatly appreciated Sir
Click to expand...
Click to collapse
infamousvincci said:
I wouldnt recommend it tbh if its your only phone. Its buggy AH.
Click to expand...
Click to collapse
Only issue I have is no advanced reboot menu what-so-ever. Battery is much better,stable af,modem is better as well. I would recommend .
File above edited. Correct images
mattie_49 said:
File above edited. Correct images
Click to expand...
Click to collapse
Thanks a lot for the files Mattie.
My experience with OOS 12 so far has been a nightmare, and I'm not even rooted.
For the record:
I was coming from OOS 11 not the latest version previous to OOS 12, rooted, pretty much stable but I felt the phone pretty slow in comparison to other (Long story short, I got a brand new OnePlus 8 I bought almost a year ago but couldn't get my hands on it, so after getting tired of waiting for it, bought the OP9).
My OP8 is not rooted, doesn't have the bootloader unlocked, and it's miles faster than my OP9 with about the same apps installed with the exception of the apps that require root.
So, since my OP9 was feeling slow in comparison, I decided to go at OOS 12 to see how it went. First experience was bad, the phone kept hanging, didn't read the SIM correctly at first, so I read someone that was suggesting to do a factory reset to fix some issues.
I did a factory reset, deleted everything on the phone to start OOS 12 from zero, and the phone keeps hanging, specially when I get phone calls via Whatsapp or other apps, and less but still some problems with "answering incoming phone calls".
At this point I rather try to downgrade to OOS 11 and sit this one out for a long while.
I thought about rooting OOS 12, but being honest, having root is not going to make the phone more stable or anything. I guess I'll do give it a try at OOS 12 in 3-6months after a couple of updates, maybe other versions are better.
Zethiel said:
Thanks a lot for the files Mattie.
My experience with OOS 12 so far has been a nightmare, and I'm not even rooted.
For the record:
I was coming from OOS 11 not the latest version previous to OOS 12, rooted, pretty much stable but I felt the phone pretty slow in comparison to other (Long story short, I got a brand new OnePlus 8 I bought almost a year ago but couldn't get my hands on it, so after getting tired of waiting for it, bought the OP9).
My OP8 is not rooted, doesn't have the bootloader unlocked, and it's miles faster than my OP9 with about the same apps installed with the exception of the apps that require root.
So, since my OP9 was feeling slow in comparison, I decided to go at OOS 12 to see how it went. First experience was bad, the phone kept hanging, didn't read the SIM correctly at first, so I read someone that was suggesting to do a factory reset to fix some issues.
I did a factory reset, deleted everything on the phone to start OOS 12 from zero, and the phone keeps hanging, specially when I get phone calls via Whatsapp or other apps, and less but still some problems with "answering incoming phone calls".
At this point I rather try to downgrade to OOS 11 and sit this one out for a long while.
I thought about rooting OOS 12, but being honest, having root is not going to make the phone more stable or anything. I guess I'll do give it a try at OOS 12 in 3-6months after a couple of updates, maybe other versions are better.
Click to expand...
Click to collapse
I have the correct msm tool for device. This is the forward route for you. Takes you to 11.4. Stock A11
Does anyone else have the issue of their touchscreen not functioning when they install the A12 update? Ive tried installing twice and both times my screen would not register any touches only the volume and power buttons functioned?
EDIT: NVM I MSM'd back to stock and upgraded to OOS 12 before unlocking the bootloader.
Zethiel said:
Thanks a lot for the files Mattie.
My experience with OOS 12 so far has been a nightmare, and I'm not even rooted.
For the record:
I was coming from OOS 11 not the latest version previous to OOS 12, rooted, pretty much stable but I felt the phone pretty slow in comparison to other (Long story short, I got a brand new OnePlus 8 I bought almost a year ago but couldn't get my hands on it, so after getting tired of waiting for it, bought the OP9).
My OP8 is not rooted, doesn't have the bootloader unlocked, and it's miles faster than my OP9 with about the same apps installed with the exception of the apps that require root.
So, since my OP9 was feeling slow in comparison, I decided to go at OOS 12 to see how it went. First experience was bad, the phone kept hanging, didn't read the SIM correctly at first, so I read someone that was suggesting to do a factory reset to fix some issues.
I did a factory reset, deleted everything on the phone to start OOS 12 from zero, and the phone keeps hanging, specially when I get phone calls via Whatsapp or other apps, and less but still some problems with "answering incoming phone calls".
At this point I rather try to downgrade to OOS 11 and sit this one out for a long while.
I thought about rooting OOS 12, but being honest, having root is not going to make the phone more stable or anything. I guess I'll do give it a try at OOS 12 in 3-6months after a couple of updates, maybe other versions are better.
Click to expand...
Click to collapse
if you are looking for performance, look into kernels and/or just use a kernel manager.
out of all the Roms I've tried (all but the latest havok release) crDroid is the best performance option I get from a ROM on O09. that piared with optional GApps and frequent OTA updates, its the best thing out so far. the OTA even works perfectly at retaining root without any user input. (but do a backup before reboot, its still technically a dirty flash so play safe)
sbute said:
Root OnePlus 9, 9 Pro, 9R Android 12 ColorOS 12 via Magisk
Thi guide will show you how to root the OnePlus 9, OnePlus 9 Pro, and OnePlus 9R running ColorOS 12 Android 12 via Magisk Patched Boot.img
www.droidwin.com
The temporary root method at the end of this page worked for me on A12 stable
Click to expand...
Click to collapse
I don't want to get too off-topic, but figured I'd save a MSM wipe to some people, I can confirm this works, but only using the latest version of Magisk (v24), temporary boot will not work with v23 (the last one with MagiskHide), it caused Qualcomm crashdump and no recovery or fastbootd.
If anyone looks into other root spoofing solutions with the newer version v24, from Magisk settings use Zygisk, select apps using Enforced Denylist, and Universal SafetyNet Fix, there is also Shamiko, which I haven't tested personally.
From my own experience, DenyList+Universal SafetyNet fix+Selinux Switch if you need to switch between permissive and enforced Selinux are enough. Apps won't get to know there is root, safetynet is passed, and selinux checks are passed (that one took me a long while to figure out)

Downgrading from UI 4.0 to UI 3.1 - is it possible at all?

As soon as I've updated my phone to Android 12, is there any way to roll back to Android 11? I'm talking about stock UI 4.0. Unfortunately, if you are on Android 12 - there's no easy way to re-install a copy of Android 11 stock ROM. Flashing via Odin doesn't go through. Some people say that you need to go to a Samsung Service Center. I can't believe it! I'm sure there must be a fix for that. Of course, it's possible to play around with really high possibility to permanently brick the phone. I'm talking about reformatting partitions and flashing a pit file...
If the bottled version is higher on Android 12, it probably is, then you can't downgrade. In the build number, I believe it's the 5th number from the right might want to check that it with Google. If the new firmware has a higher number there NO going back...
robotov said:
As soon as I've updated my phone to Android 12, is there any way to roll back to Android 11? I'm talking about stock UI 4.0. Unfortunately, if you are on Android 12 - there's no easy way to re-install a copy of Android 11 stock ROM. Flashing via Odin doesn't go through. Some people say that you need to go to a Samsung Service Center. I can't believe it! I'm sure there must be a fix for that. Of course, it's possible to play around with really high possibility to permanently brick the phone. I'm talking about reformatting partitions and flashing a pit file...
Click to expand...
Click to collapse
Yes, it's possible, and I've done it.
robotov said:
As soon as I've updated my phone to Android 12, is there any way to roll back to Android 11? I'm talking about stock UI 4.0. Unfortunately, if you are on Android 12 - there's no easy way to re-install a copy of Android 11 stock ROM. Flashing via Odin doesn't go through. Some people say that you need to go to a Samsung Service Center. I can't believe it! I'm sure there must be a fix for that. Of course, it's possible to play around with really high possibility to permanently brick the phone. I'm talking about reformatting partitions and flashing a pit file...
Click to expand...
Click to collapse
I confirm that I also downgraded from Android 12 / One UI 4.0 (January 1 patch) to Android 11 / One UI 3.1 (November 1 patch) without problems. There were several aspects of the new version that were bothering me a lot, now I'm happy both versions are binary 3, but it will cease to be in the following versions for sure...
Hi can you help me with guidelines to upgrade to android 12? I'm using Note 20 ultra n985f/ds. It was previously a Live demo unit but is now fully functional on android 10. My csc is OXM WWD... looking forward to your help
Also I'd like to know which is better, should I just change my csc so I can receive the push for update via OTA or just follow a guideline for flashing with Odin, thanks in advance

Question [HELP]Fat fingered OOS12 OTA update on rooted stock OOS11 and now I have no touch input.

Hello all,
I ****ed up, what I feel is big time?
I accidentally fat fingered the "install and restart" button for an OTA update for OOS12 on my rooted stock OOS11. From what I learned during my research phase of rooting my OP9, that's a big no no and can cause a lot of problems. When the phone booted back up I have no touch input at all. I have a mouse plugged into my phone and can use the phone that way and I am currently backing up as much as I can in the event I have to wipe my phone.
My question is, can I just dirty flash the previous OOS11 image I was running to go back to before the OOS12 OTA got applied? Just wanted to get the general consensus before I ruin my **** further.
I'm running stock recovery, stock OOS11.2.4.4 with Magisk, MagiskHide and not much else.
Much appreciated!
To my what i know you have to downgrade from 12 to 11 ect. I managed to get to global.
I messed up, and updated mine to 12. and from what i learned. my touch screen did not work due to the fact my update was for a global 9 pro, Not my oneplus 9-tmobile version. In the end I had to use the india msm tool to get back to working
warglock said:
Hello all,
I ****ed up, what I feel is big time?
I accidentally fat fingered the "install and restart" button for an OTA update for OOS12 on my rooted stock OOS11. From what I learned during my research phase of rooting my OP9, that's a big no no and can cause a lot of problems. When the phone booted back up I have no touch input at all. I have a mouse plugged into my phone and can use the phone that way and I am currently backing up as much as I can in the event I have to wipe my phone.
My question is, can I just dirty flash the previous OOS11 image I was running to go back to before the OOS12 OTA got applied? Just wanted to get the general consensus before I ruin my **** further.
I'm running stock recovery, stock OOS11.2.4.4 with Magisk, MagiskHide and not much else.
Much appreciated!
Click to expand...
Click to collapse
I would def recommend just MSM back to stock 11.2.4.4, I was in your same situation before and I always had the touchscreen issues if I was rooted when I upgraded to OOS12. I think I tried flashing back to 11 and just ended up soft bricking my device and having to MSM anyway. Also like the commenter said above I had to use the Indian MSM but Ive been able to use the Global MSM now with no issues so if thats what your're on Id recommend trying that one first and only using the Indian MSM if that one gives you errors.
So I'm running into this same problem and absolutely can not upgrade to OOS12. Each time, by display will not respond to touch. I went back to 11 via MSM (HAD TO USE OP9 Pro INDIA) because OP screwed something up with these phones.
I have tried multiple ways, went back to OOS 11, installed latest OOS 11 without root. Locked bootloader, Installed latest OOS 11 twice via system update to make sure everything was clean. Installed OOS 12 update and same problem.
Same problem here.....
I have installed the msm india and then the official android 11 for OP 9. After that the OP9 runs on Android 11. After that i have closed the bootloader and try the msm with the eu rom and i gets the "device not match image" error. Maybe i have the new rom for op9 installed and the productnumber is still on op9p ? Now i am going back to a custom rom. is there an option to get the fully working camera on a custom rom?
DerBaLu841 said:
Same problem here.....
I have installed the msm india and then the official android 11 for OP 9. After that the OP9 runs on Android 11. After that i have closed the bootloader and try the msm with the eu rom and i gets the "device not match image" error. Maybe i have the new rom for op9 installed and the productnumber is still on op9p ? Now i am going back to a custom rom. is there an option to get the fully working camera on a custom rom?
Click to expand...
Click to collapse
To get back to the correct ROM, boot to TWRP and flash the signed full zip to each slot.

Categories

Resources