Related
Hi there,
Sorry for the noob(ish) question but I've lost base some time ago and now I thought I might look into getting the phone updated if possible.
This is European 034 dual-SIM version, Oreo 1.30.401.2, unlocked bootloader, running Magisk now.
I did some research through the forums (spent whole evening on this) and only got confused. I'm not looking for spoonfeeding, just clear answer what should be my path if I want to get the Pie - is it worth on U12+ btw?
I'm familiar more or less with cli and adb, twrp are no news to me as well.
Many thanks
doc
first step, flash RUU Oreo on your device.This provedure erases everything, all files, twrp too.
Then search update from settings and install updates up to Pie.
So install,if you want,twrp magisk ecc...
When somebody will release Ruu Pie, we could skip previous procedure
I will update you about my last night. I have tried to update the phone but I've flashed the Exodus rom instead of Imagine.
Took me most of the night and morning to get it back up and running - the fix was to use force update script I found on 4pda. Im running rooted Pie now.
Hi Team,
On the latest OOS 10.3.2. Have done multiple resets, downgraded using msm tool to OOS 5.1.3 and then manually updating them. Factory reset done a couple of times.
Anyone can help?
Currently running Magisk 20.4, bootloader unlocked.
Same here
I even tried using msmtool and even installing custom rom still no luck in fixing this issue . Most irritating part about this is not able to use auto rotate .
Possible Fix
Hey! I made an account today to hopefully help youins. I was also struggling with this issue, and I couldn't find anyone with a working solution. After trying resets and full msm tool restores of different android versions (I tried the standard 5.1.5, 9.0.0, and 10.3.2), I figured out my issue and fixed it.
For me, I would do an msm to android 8 (5.1.5). This is the link on the main forum for " [TOOL] MsmDownloadTool V4.0 International (Oxygen OS 5.1.5)" by Fivegates. (I would link it, but I don't know if that's allowed or not.) After doing the reset, Everything worked! However, after letting the phone update to 9.0.9 by it's self with the update tool in settings, I would lose the ability to use wifi. After forcing the next update to 10.3.2, I would lose the gyro and Prox sensor again. I then tried the msm tool from a different site that went straight to 10.3.2 ... No dice. Same issue. So, I figured that the phone needed one of the updates between 5.1.5 and 9.0.9. I started trying some updates between, and here was my final process to get back up and running! (it took a while. haha)
FIX
1. MSM tool to 5.1.5 by following the MsmDownloadTool post from fivegates. (This will wipe all data and re-lock bootloader.)
2. After phone boots, run through set-up, but don't let phone update.
3. Download the full OTA for Oneplus 6, version 9.0.0. It can be found in an xda post, or elsewhere. Again, don't know if I can link anything.)
4. Put the zip on your Oneplus and use the updater in settings to preform an update from local storage. (You tap the top right corner menu and select local upgrade.)
5. Once updated to 9.0.0, let the phone do the next two updates. At the time of this guide, the first will be to 9.0.9 , and the second to 10.3.2.
6. After that, I had a working gyro and Prox sensor on 10.3.2. From there, I unlocked the bootloader, booted twrp, and carried on my rom installs like normal.
I hope this helps!
oldmanz said:
Hey! I made an account today to hopefully help youins. I was also struggling with this issue, and I couldn't find anyone with a working solution. After trying resets and full msm tool restores of different android versions (I tried the standard 5.1.5, 9.0.0, and 10.3.2), I figured out my issue and fixed it.
For me, I would do an msm to android 8 (5.1.5). This is the link on the main forum for " [TOOL] MsmDownloadTool V4.0 International (Oxygen OS 5.1.5)" by Fivegates. (I would link it, but I don't know if that's allowed or not.) After doing the reset, Everything worked! However, after letting the phone update to 9.0.9 by it's self with the update tool in settings, I would lose the ability to use wifi. After forcing the next update to 10.3.2, I would lose the gyro and Prox sensor again. I then tried the msm tool from a different site that went straight to 10.3.2 ... No dice. Same issue. So, I figured that the phone needed one of the updates between 5.1.5 and 9.0.9. I started trying some updates between, and here was my final process to get back up and running! (it took a while. haha)
FIX
1. MSM tool to 5.1.5 by following the MsmDownloadTool post from fivegates. (This will wipe all data and re-lock bootloader.)
2. After phone boots, run through set-up, but don't let phone update.
3. Download the full OTA for Oneplus 6, version 9.0.0. It can be found in an xda post, or elsewhere. Again, don't know if I can link anything.)
4. Put the zip on your Oneplus and use the updater in settings to preform an update from local storage. (You tap the top right corner menu and select local upgrade.)
5. Once updated to 9.0.0, let the phone do the next two updates. At the time of this guide, the first will be to 9.0.9 , and the second to 10.3.2.
6. After that, I had a working gyro and Prox sensor on 10.3.2. From there, I unlocked the bootloader, booted twrp, and carried on my rom installs like normal.
I hope this helps!
Click to expand...
Click to collapse
your the best man i can finally use other ROMs again
my fix was to use oneplus 7 port on my 6 but it was annyoing me
oldmanz said:
Possible Fix
Hey! I made an account today to hopefully help youins. I was also struggling with this issue, and I couldn't find anyone with a working solution. After trying resets and full msm tool restores of different android versions (I tried the standard 5.1.5, 9.0.0, and 10.3.2), I figured out my issue and fixed it.
For me, I would do an msm to android 8 (5.1.5). This is the link on the main forum for " [TOOL] MsmDownloadTool V4.0 International (Oxygen OS 5.1.5)" by Fivegates. (I would link it, but I don't know if that's allowed or not.) After doing the reset, Everything worked! However, after letting the phone update to 9.0.9 by it's self with the update tool in settings, I would lose the ability to use wifi. After forcing the next update to 10.3.2, I would lose the gyro and Prox sensor again. I then tried the msm tool from a different site that went straight to 10.3.2 ... No dice. Same issue. So, I figured that the phone needed one of the updates between 5.1.5 and 9.0.9. I started trying some updates between, and here was my final process to get back up and running! (it took a while. haha)
FIX
1. MSM tool to 5.1.5 by following the MsmDownloadTool post from fivegates. (This will wipe all data and re-lock bootloader.)
2. After phone boots, run through set-up, but don't let phone update.
3. Download the full OTA for Oneplus 6, version 9.0.0. It can be found in an xda post, or elsewhere. Again, don't know if I can link anything.)
4. Put the zip on your Oneplus and use the updater in settings to preform an update from local storage. (You tap the top right corner menu and select local upgrade.)
5. Once updated to 9.0.0, let the phone do the next two updates. At the time of this guide, the first will be to 9.0.9 , and the second to 10.3.2.
6. After that, I had a working gyro and Prox sensor on 10.3.2. From there, I unlocked the bootloader, booted twrp, and carried on my rom installs like normal.
I hope this helps!
Click to expand...
Click to collapse
Thank you kind person. For more than two months I tried to return the phone to normal operation and all to no avail. So I came across your post and now my phone is full again. Thank you very much.
oldmanz said:
Possible Fix
Hey! I made an account today to hopefully help youins. I was also struggling with this issue, and I couldn't find anyone with a working solution. After trying resets and full msm tool restores of different android versions (I tried the standard 5.1.5, 9.0.0, and 10.3.2), I figured out my issue and fixed it.
For me, I would do an msm to android 8 (5.1.5). This is the link on the main forum for " [TOOL] MsmDownloadTool V4.0 International (Oxygen OS 5.1.5)" by Fivegates. (I would link it, but I don't know if that's allowed or not.) After doing the reset, Everything worked! However, after letting the phone update to 9.0.9 by it's self with the update tool in settings, I would lose the ability to use wifi. After forcing the next update to 10.3.2, I would lose the gyro and Prox sensor again. I then tried the msm tool from a different site that went straight to 10.3.2 ... No dice. Same issue. So, I figured that the phone needed one of the updates between 5.1.5 and 9.0.9. I started trying some updates between, and here was my final process to get back up and running! (it took a while. haha)
FIX
1. MSM tool to 5.1.5 by following the MsmDownloadTool post from fivegates. (This will wipe all data and re-lock bootloader.)
2. After phone boots, run through set-up, but don't let phone update.
3. Download the full OTA for Oneplus 6, version 9.0.0. It can be found in an xda post, or elsewhere. Again, don't know if I can link anything.)
4. Put the zip on your Oneplus and use the updater in settings to preform an update from local storage. (You tap the top right corner menu and select local upgrade.)
5. Once updated to 9.0.0, let the phone do the next two updates. At the time of this guide, the first will be to 9.0.9 , and the second to 10.3.2.
6. After that, I had a working gyro and Prox sensor on 10.3.2. From there, I unlocked the bootloader, booted twrp, and carried on my rom installs like normal.
I hope this helps!
Click to expand...
Click to collapse
Thanks a lot man !!!!
Following your steps, the automatic brightness and also the automatic screen rotation works for me again.
Thank you @oldmanz
Hey, I'm trying to update my phone, and when I start downloading the update the process bar proceeds for about one second and then i get "installation problem" error in the update screen.
Any idea why?
I'm using OnePlus 8T (KB2003) on Oxygen OS 11.0.9.9.KB05AA, Trying to update to Oxygen OS 11.0.10.10.KB05AA.
My phone is rooted, but I have updated in the past, and everything worked fine.
You will have to restore the stock 11.0.9.9 boot image before you can install the 11.0.10.10 update. The update checks the status of the current system before starting the update process to make sure it's fully stock.
There's various threads on how to update if you're rooted.
The thing is, I updated this phone with root already several times.
After rechecking I noticed that before I restored images like you said.
I guess I just forgot this part.
Anyways, thank you very much!
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)
I have an LE2115. I tried to update install CRdroid, and during the process the guide required an upgrade to firmware F18.
I was already on the newest (F20 I think) firmware, so I figured a small roll back would be needed. I downloaded F18 from the CRdroid firmware link, and when it was run it ended up bricking the phone. Annoying, but I didn't think it the end of the world.
To unbrick it I downloaded the MSM global 11.2.10.10 and flashed the phone with A11 (11.2.10.10). I was able to get back into the phone, and everything seemed ok at first glance.
The problem is now I can't install any updates to get it back to android 13.
If I do a system ->system update -> check for updates -> download and install. It says it downloads update LE2115_11.F.17_2170_20021123112, installs it, and reboots.
After rebooting the phone shows a successfully installed update message, but when I look at under About the system is still on Android 11 (11.2.10.10). No change at all.
If I try sticking the OTA zip LE2115_11.F.17_2170_202211231112 in root, and using that for a local update the phone gives me a update failed message after a few seconds. No useful error messages at all.
Can someone point me in the right direction? I can't figure out how to get this off A11 and back to A13 (F18).
This is making me want to rip out my hair as everything I have tried has failed to get me onto a current firmware.
wizardknight said:
I have an LE2115. I tried to update install CRdroid, and during the process the guide required an upgrade to firmware F18.
I was already on the newest (F20 I think) firmware, so I figured a small roll back would be needed. I downloaded F18 from the CRdroid firmware link, and when it was run it ended up bricking the phone. Annoying, but I didn't think it the end of the world.
To unbrick it I downloaded the MSM global 11.2.10.10 and flashed the phone with A11 (11.2.10.10). I was able to get back into the phone, and everything seemed ok at first glance.
The problem is now I can't install any updates to get it back to android 13.
If I do a system ->system update -> check for updates -> download and install. It says it downloads update LE2115_11.F.17_2170_20021123112, installs it, and reboots.
After rebooting the phone shows a successfully installed update message, but when I look at under About the system is still on Android 11 (11.2.10.10). No change at all.
If I try sticking the OTA zip LE2115_11.F.17_2170_202211231112 in root, and using that for a local update the phone gives me a update failed message after a few seconds. No useful error messages at all.
Can someone point me in the right direction? I can't figure out how to get this off A11 and back to A13 (F18).
This is making me want to rip out my hair as everything I have tried has failed to get me onto a current firmware.
Click to expand...
Click to collapse
I have the same device. After the 11.2.10.10 comes C48 first a12 build but it's marked F17 update. Then comes C-66 it's also marked F-17. Take it. Next update you guessed is labeled F-17 and it is actually F-17. Android 13. Then you will get F-18 ota as well. Then have to go into oxygen updater from playstore and update to F20. Latest with Jan sec patch. Since they dropped Android 13 all their device updates for op9 are labeled wrong. After msm you started on 11.2.4.4. I flash lineage and mess with things but mostly stay on stock as it's great and cam is good on os. Good luck. Check out pixelify by Kingsman 44. Real nice for op9 also.
mattie_49 said:
I have the same device. After the 11.2.10.10 comes C48 first a12 build but it's marked F17 update. Then comes C-66 it's also marked F-17. Take it. Next update you guessed is labeled F-17 and it is actually F-17. Android 13. Then you will get F-18 ota as well. Then have to go into oxygen updater from playstore and update to F20. Latest with Jan sec patch. Since they dropped Android 13 all their device updates for op9 are labeled wrong. After msm you started on 11.2.4.4. I flash lineage and mess with things but mostly stay on stock as it's great and cam is good on os. Good luck. Check out pixelify by Kingsman 44. Real nice for op9 also.
Click to expand...
Click to collapse
Ok. Thanks. I will run the update multiple times, and see if I can get to F18.
I can't believe the naming is all buggered up. Ok, well maybe I can believe it. Seems like OnePlus is just not doing a good job anymore, but there are not many other flagship grade phones with unlocked boot loaders and custom roms anymore (and I have been using custom android roms since the touch pro 2 days). It's making me a sad panda.
I just upgraded from a OnePlus 7t to the 9 because I got a crazy good price for an open box phone on clearance. Now I am starting to wonder if I made the wrong decision.
If I have to download 5+ updates every time something doesn't flash right I am going to burn though my 1TB internet cap in no time.
Update:
After ~10gb of updates I got to F18.
Now to go and get a custom rom on this thing, and hope I don't have to unbrick it again.