Related
So I am running full stock on my Pixel that is updated to Oreo. I've read through the latest thread (HERE) on the new beta for Magisk that supports Pixel devices and wanted to know what steps folks may have followed to get this installed and working. The regular thread details some steps but it appears that those are driven towards other devices and doesn't account for the difference of Pixel devices.
Thx!
loaded up fine on my pixel!
eqbirvin said:
loaded up fine on my pixel!
Click to expand...
Click to collapse
Are you able to share the steps you took to get it loaded? It would seem that it isn't the same as other or previous version since those didn't apply to pixel devices.
Thx
Do modules work?
There's an offical Magisk Pixel (XL) Thread
I'm running it on Pure Nexus July build now. I ended up having to re-flash (dirty) the ROM to clear up the old goodwin_c Magisk install.
Seems okay for now. I have a couple of modules loaded but haven't had the opportunity to test whether they actually work. AirAudio at least doesn't fire a warning that the module isn't found.
There is a new update today. Mods were broken. Supposedly fixed now.
https://forum.xda-developers.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589/post73966889
Steps on 8.0 were as follows
make sure youre on stock boot
boot into system once with stock boot
then boot into android 0 twrp
flash magisk
reboot to system
finished
So after a while I decided to finally upgrade to Android 10, I refused it a long time because of Snapchat modification reasons which only works on Pie.
My 7 Pro is ofc rooted with Magisk, I have several modules active and also have edxposed and Swift Installer installed.
I want to go sure to not mess anything up, because last times I upgraded a firmware, I either messed up the encryption and had to format everything in the end or got stuck in a recovery bootloop.
How do I upgrade properly in my current status?
Thanks!
Or wait a couple of months for them to tweak it a bit?
I only run Magik and not Xposed, not that it matters!
I'm not rooted, but I've been running R since the first public ßeta.
It's been the smallest update so far in a long time for Android. Very little has changed, compared to previous major version upgrades.
If you can root (and from what I read i think you can with Magisk), make a full backup and try it.
Sent from my Pixel 4 XL using Tapatalk
I don't really know what you'd be waiting for. I don't think a non-rooted person would notice much in terms of drawbacks. Magisk modules level, there were some issues... but I think most things are getting worked out. Xposed technically works, but more than half of my modules broke in a way that probably won't be fixed for a while. I still feel like I'm at a net-negative in terms of phone features. A11 brought little and broke a lot of my QoL tweaks that used Xposed.
I make no claims about SafetyNet as I use no apps that even check it.
I think A11 has been released formally by google and most of issues have been fixed or addressed.
I used magisk and edxposed. That's not a problem for me(I used Edxposed for fingerface only). Regarding of safetynet issue, it also has solution to make it pass by magisk modules and kernel side.
Until now, I'm happy with A11.
I ended up doing a full wipe and upgrade to Android 11 Oct 2020.
I have Magisk running with the SQL Lite mods for Google Pay and obviously I have root so I'm basically back where I was on Android 10.
I hadn't use Xposed yet and I don't know if I will yet. I was using Viper Audio mod but I don't know if I noticed a major difference, mostly I just stream bluetooth in my SUV.
So far, so good.
I tried it and reverted back to 10 - as mentioned didn't gain much but broke a lot. Even in stock form I can't get videos to load a subtitle file because of storage permissions and what not. A tweaked out install of 10 is faaaar nicer imo so that's what I'm running, probably until a new phone comes out sadly.
Kris Chen said:
I think A11 has been released formally by google and most of issues have been fixed or addressed.
I used magisk and edxposed. That's not a problem for me(I used Edxposed for fingerface only). Regarding of safetynet issue, it also has solution to make it pass by magisk modules and kernel side.
Until now, I'm happy with A11.
Click to expand...
Click to collapse
can i ask how you upgraded to A11? Im on 10 rooted with magisk and keep hearing mixed messages on upgrading. And is it necessary to wipe? I really don't want to.
A11 is not too bad, but as others have said little things here and there that break. Like for me I listen to SiriusXM app on mobile and for some odd reason it will stop playing all of a sudden and close. It's like the aggressive memory management kills the app for no reason. I even have battery optimization turned off and still does it.
Thinking about moving back to A10 from August, not really much I have to have to stick with latest A11 updates.
qman66 said:
can i ask how you upgraded to A11? Im on 10 rooted with magisk and keep hearing mixed messages on upgrading. And is it necessary to wipe? I really don't want to.
Click to expand...
Click to collapse
Flash the factory image, but remove the -w in the flash-all file. Then in Magisk Manager switch tot he beta channel and patch the boot image with that. Flash it and you're done.
GjorgiDxc said:
Flash the factory image, but remove the -w in the flash-all file. Then in Magisk Manager switch tot he beta channel and patch the boot image with that. Flash it and you're done.
Click to expand...
Click to collapse
You do know the latest version of magisk has a11 support?
GjorgiDxc said:
Flash the factory image, but remove the -w in the flash-all file. Then in Magisk Manager switch tot he beta channel and patch the boot image with that. Flash it and you're done.
Click to expand...
Click to collapse
Ok so I shouldn't install it via the ota? I keep getting the pop up to update every day.
Does using Magisk to dl / install the OTA, then patch the non-live and newly flashed partition, then finally rebooting not work?
When I was rooted that was always the easiest way.
And based upon the post 2 above this one, Magisk now supports A11 without ẞeta, right?
From Coral, with Tapatalk.
kdoggy said:
I ended up doing a full wipe and upgrade to Android 11 Oct 2020.
I have Magisk running with the SQL Lite mods for Google Pay and obviously I have root so I'm basically back where I was on Android 10.
I hadn't use Xposed yet and I don't know if I will yet. I was using Viper Audio mod but I don't know if I noticed a major difference, mostly I just stream bluetooth in my SUV.
So far, so good.
Click to expand...
Click to collapse
How is 11 for you going so far, I am thinking in reverting back to 10, battery is awful on 11
Hello everyone. Long time since I had an android device and I'm cutting the chains of my iPhone wanting to be de-Googled and de-Appled. I was running Lineage 17.1 from Microg and thought I had everything working on it until I started updating some software on my phone over the air. I rebooted and it went to bootloop. Since then I re-installed 17.1 and got things working again. I just upgraded to 18.1 and want to make sure it's all set up properly and won't have any errors.
Magisk says SafetyNet has an "SafetyNet API Error." "Basicintegrity, ctsProfile, evalType N/A." all in red when I check if it's working. I've done some digging, but want to make sure I do this right. I need to get the boot.img file from the original firmware. Should I get this from the oneplus website, or should I be looking for something else since I have Lineage? Can anyone provide the raw boot.img file for the OnePlus 7 Pro that I should use? I'm a little overwhelmed with all of the steps to extract it from the original firmware. Please and thanks for any help getting this phone set up the way I need it to work!
That error show when safety net API download was incomplete/corrupt, you can try to erase data from magisk manager and check safetynet again but with a better internet connection or use another magisk version like canary
And if you end in a bootloop for any magisk module just turn off your device and in your computer in a CMD/powershell/terminal window enter this command
adb wait-for-device shell magisk --remove-modules
Then connect and turn on your phone and automatically your phone will reboot with all your magisk modules disabled
Use magisk canary bro,,,
I sideloaded Canary and still get the red SafetyNet API error screen after opening it. Can someone direct me to a full tutorial on how Magisk works and what the modules do? I'm thinking I might need to do a full uninstall of Magisk and start over. If I do this will I lose all the data on the phone and have to start from scratch? Thanks for your help so far!
Well I've spent several hours researching tutorials and typing in codes via Terminal on my Mac and have gotten the phone restocked twice and working normal on stock OS, but after putting TWRP on it and then installing Lineage 18.1 it goes into a Lineage logo boot loop. What am I missing here?
It seems to me that TWRP is not compatible with Lineage. Sometimes when I rebooted the phone and was playing with the Recovery.IMG I saw the Lineage Recovery, then other times the TWRP would flash on and off in a boot loop. I have been careful about using the command " ./fastboot boot TWRP.img " and not "flash" TWRP, as would be the case for non a/b storage devices. On a couple occasions I could reboot with the Lineage Recovery.IMG and it would boot to startup, but if I rebooted to Recovery from the home screen, it would get stuck on TWRP.
I'm probably just missing something simple, but what might I be doing wrong? Is it the timing of installing TWRP and then installing Lineage in the same TWRP session?
This all stemmed from me wanting to get TWRP with Lineage 18.1 and getting Magisk and Microg working correctly for a "de-googled" phone with working apps. I'm frustrated, but will keep trying if I can get some direction. Thanks for your input.
-L
Lear31pilot said:
Well I've spent several hours researching tutorials and typing in codes via Terminal on my Mac and have gotten the phone restocked twice and working normal on stock OS, but after putting TWRP on it and then installing Lineage 18.1 it goes into a Lineage logo boot loop. What am I missing here?
It seems to me that TWRP is not compatible with Lineage. Sometimes when I rebooted the phone and was playing with the Recovery.IMG I saw the Lineage Recovery, then other times the TWRP would flash on and off in a boot loop. I have been careful about using the command " ./fastboot boot TWRP.img " and not "flash" TWRP, as would be the case for non a/b storage devices. On a couple occasions I could reboot with the Lineage Recovery.IMG and it would boot to startup, but if I rebooted to Recovery from the home screen, it would get stuck on TWRP.
I'm probably just missing something simple, but what might I be doing wrong? Is it the timing of installing TWRP and then installing Lineage in the same TWRP session?
This all stemmed from me wanting to get TWRP with Lineage 18.1 and getting Magisk and Microg working correctly for a "de-googled" phone with working apps. I'm frustrated, but will keep trying if I can get some direction. Thanks for your input.
-L
Click to expand...
Click to collapse
TWRP is not working for OOS11 or A11 ROMs using Oos11 blobs.
Lossyx said:
TWRP is not working for OOS11 or A11 ROMs using Oos11 blobs.
Click to expand...
Click to collapse
Got it! I'll go back to 17.1 Thanks!
Bump
Still trying to find a solution. I get fairly far into flashing the ROM, getting TWRP working and then end up stuck at Microg not letting me open the location menu. If only there were a guide with start to finish Lineage 17.1 or 18.1 with Microg and Magisk for my OnePlus 7 Pro. I find some guides, but there isn't one that encompasses everything that actually works. I'm going to try Lineage 18.1 with Microg built in and then flash Magisk.
Lear31pilot said:
Bump
Still trying to find a solution. I get fairly far into flashing the ROM, getting TWRP working and then end up stuck at Microg not letting me open the location menu. If only there were a guide with start to finish Lineage 17.1 or 18.1 with Microg and Magisk for my OnePlus 7 Pro. I find some guides, but there isn't one that encompasses everything that actually works. I'm going to try Lineage 18.1 with Microg built in and then flash Magisk.
Click to expand...
Click to collapse
I never installed lineage but i guess you can flash the ROM, change slots, then format data(this will erase all your stuff) and flash magisk then reboot into system
And for the safety net error yesterday was released a "fix" for that so try again
RokCruz said:
I never installed lineage but i guess you can flash the ROM, change slots, then format data(this will erase all your stuff) and flash magisk then reboot into system
And for the safety net error yesterday was released a "fix" for that so try again
Click to expand...
Click to collapse
Thank you. I'll have to address this at some point. I got the phone restocked, and flashed 18.1 Lineage on it again. Got all my apps and accounts back up on it. I'm just debating running Magisk again knowing that I'll likely have to start from scratch again. I wasn't able to get TWRP working correctly, so I left Lineage Recovery on, so it will be some time before I try going through this again. I'm going to do some research on what exactly is happening when I put recoveries and ROMs on different slots. Same goes for the Magisk. It's all quite new to me with the "slots" and what information has to go on which slot. I also need to find out how to backup my apps so if I re-flash a ROM, it's not so painful to get my data back on the phone.
At least I have a working phone without a Google login and most of the apps I want work. I'm only missing Lyft and my bank app. Again, thanks for the reply, and I'll look into this when I have some time to play with the phone again.
Lear31pilot said:
Thank you. I'll have to address this at some point. I got the phone restocked, and flashed 18.1 Lineage on it again. Got all my apps and accounts back up on it. I'm just debating running Magisk again knowing that I'll likely have to start from scratch again. I wasn't able to get TWRP working correctly, so I left Lineage Recovery on, so it will be some time before I try going through this again. I'm going to do some research on what exactly is happening when I put recoveries and ROMs on different slots. Same goes for the Magisk. It's all quite new to me with the "slots" and what information has to go on which slot. I also need to find out how to backup my apps so if I re-flash a ROM, it's not so painful to get my data back on the phone.
At least I have a working phone without a Google login and most of the apps I want work. I'm only missing Lyft and my bank app. Again, thanks for the reply, and I'll look into this when I have some time to play with the phone again.
Click to expand...
Click to collapse
TWRP can't boot in devices with OOS 11 blobs and encrypted data, for Magisk the only way I can imagine is using a patched boot.img.
Make a backup of your current boot.img(lineage) with apps like Franco kernel, then Patch it with magisk, then flash it in fastboot (fastboot flash boot boot.img)
if something woes wrong you can restore the backup from Franco kernel
RokCruz said:
TWRP can't boot in devices with OOS 11 blobs and encrypted data, for Magisk the only way I can imagine is using a patched boot.img.
Make a backup of your current boot.img(lineage) with apps like Franco kernel, then Patch it with magisk, then flash it in fastboot (fastboot flash boot boot.img)
if something woes wrong you can restore the backup from Franco kernel
Click to expand...
Click to collapse
Thanks RokCruz,
I'm going to get 18.1 back on with the LOS Recovery again. I'll try the boot patch method with the LOS boot.img from 18.1 for Magisk. I haven't tried the Franco kernel as I just now found out about it. I don't really need to do anything else fancy with the phone in terms of overclocking or underclocking. Does that kernel facilitate easier backups? I'm still learning a LOT about how Android works. It's been a steep learning curve. Fortunately, I can get myself out of any binds with a restock and fastboot!
Lear31pilot said:
Thanks RokCruz,
I'm going to get 18.1 back on with the LOS Recovery again. I'll try the boot patch method with the LOS boot.img from 18.1 for Magisk. I haven't tried the Franco kernel as I just now found out about it. I don't really need to do anything else fancy with the phone in terms of overclocking or underclocking. Does that kernel facilitate easier backups? I'm still learning a LOT about how Android works. It's been a steep learning curve. Fortunately, I can get myself out of any binds with a restock and fastboot!
Click to expand...
Click to collapse
Yes only for boot backups, I always made a backup of my boot.img of every OB just in case something goes wrong but i have never experienced that.
I personally prefer OOS, just install custom kernel and some mods like Cyberpunk 2077 theme, Riru Lsposed and a adbloker and that's all I need
RokCruz said:
Yes only for boot backups, I always made a backup of my boot.img of every OB just in case something goes wrong but i have never experienced that.
I personally prefer OOS, just install custom kernel and some mods like Cyberpunk 2077 theme, Riru Lsposed and a adbloker and that's all I need
Click to expand...
Click to collapse
I'm trying to de-google. Can I de-google on OOS? Most stock ROMs require a google login.
Lear31pilot said:
I'm trying to de-google. Can I de-google on OOS? Most stock ROMs require a google login.
Click to expand...
Click to collapse
I guess you can, just use a debloater
But it's better to install HydrogenOS just disable Chinese apps, install micro g and it's complements and you can run any Google dependant app, safety net passes without problems too.
I installed hydrogen and it runs smoothly but Cyberpunk isn't available for it so I reinstalled OOS
RokCruz said:
I guess you can, just use a debloater
But it's better to install HydrogenOS just disable Chinese apps, install micro g and it's complements and you can run any Google dependant app, safety net passes without problems too.
I installed hydrogen and it runs smoothly but Cyberpunk isn't available for it so I reinstalled OOS
Click to expand...
Click to collapse
Thanks for the tip about Hydrogen. I'll do some research on that. And thanks for getting back so quickly. The Android community really has some great people. Happy to be apart of it!
So
Lear31pilot said:
Thanks for the tip about Hydrogen. I'll do some research on that. And thanks for getting back so quickly. The Android community really has some great people. Happy to be apart of it!
Click to expand...
Click to collapse
So at the end of the day, I ended up with HydrogenOS 11 and have F-Droid and Aurora Store installed and working fine. I didn't/don't need Magisk or MicroG since HOS apparently is OK'd by google and all of my apps work.
So this worked perfectly for me. I have a fully functional OS and no Google sign-in needed. I did as you said and just deleted the Chinese bloat apps. I can't manage to get rid of the "Market" app though.
Lyft works and all of my location requiring apps like Waze work as well. Thanks for pointing me in the right direction.
Question: Will OxygenOS work the same without a google login? If so, what would be the advantage of HOS vs OOS? HOS 11 has an entire section devoted to a Google login for different services. I left it blank, but just wondering what the difference would be on OOS.
Lear31pilot said:
So
So at the end of the day, I ended up with HydrogenOS 11 and have F-Droid and Aurora Store installed and working fine. I didn't/don't need Magisk or MicroG since HOS apparently is OK'd by google and all of my apps work.
So this worked perfectly for me. I have a fully functional OS and no Google sign-in needed. I did as you said and just deleted the Chinese bloat apps. I can't manage to get rid of the "Market" app though.
Lyft works and all of my location requiring apps like Waze work as well. Thanks for pointing me in the right direction.
Question: Will OxygenOS work the same without a google login? If so, what would be the advantage of HOS vs OOS? HOS 11 has an entire section devoted to a Google login for different services. I left it blank, but just wondering what the difference would be on OOS.
Click to expand...
Click to collapse
Market can be disabled if my mind serve me right, OOS could end in a bootloop if we remove all Google apps so it's better not to do that.
I never see that section, I only installed OB1 and OB2 and never see that.
And remember you need to install magisk in order to pass safetynet.
RokCruz said:
Market can be disabled if my mind serve me right, OOS could end in a bootloop if we remove all Google apps so it's better not to do that.
I never see that section, I only installed OB1 and OB2 and never see that.
Click to expand...
Click to collapse
Looks like I'm denied the ability to disable the Market App.
Photo's attached for the Google settings I have available on HOS 11.
Also unable to make the microphone work in the keyboard for voice to text, but I have a feeling I won't be able to make that work without logging in to Google. Currently looking for some workarounds.
What will passing Safetynet allow me to do that I'm not already able to do now? Use banking apps and "tap to pay" type apps? I haven't found my bank app on the Aurora Store just yet. "US Bank" if it makes a difference.
I'll continue to play with this OS, but so far, it seems the easiest to get working right from the get-go.
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)