Hello everyone,
I have a question about the update process of OOS while having Magisk installed as described in this thread: https://forum.xda-developers.com/oneplus-8/how-to/guide-how-to-root-oneplus-8-twrp-t4084849
I've heard from a friend which has a OP8 Pro and a few users on the internet that after a software update the fingerprint no longer functions when you have Magisk (Canary) installed while doing the update and that people need a backup of their persist partition to restore this functionality.
Now I want to make sure I have a backup of this and any other essential partition just in case something does go wrong because currently I'm on OOS 10.5.4 and a update for OOS 10.5.6 is ready for me in the OOS System Updater.
So which partitions should I back up and what app, tool or something else should I be using to back these up?
Thanks in advance.
What I knew regrading fingerprint sensor doesn't work during using unbrick tool to restore your device to oxygen OS. There's nothing to do with root(Install Magisk). If I don't misunderstood.
Related
Hello everyone,
I just received my OP6 coming from the OPO and while I have been flashing LOS (sultans), magisk, twrp and co since my S1+, recent years obviously changed a lot.
So before bricking stuff or getting into bootloops, I briefly want to confirm if I miss something or got the order wrong:
update the stock OOS to the latest version
unlock bootloader
flash twrp
flash magisk
get root access to backup modemst1 & 2
decide if I wanna to with OOS, OOS open beta or LOS (didnt check yet if it is available with PIE)
flash ROM & magisk
flash gcam?! (worth it?)
figure out how to enable VoLTE & VoWIFI
check if I can get my banking ups running with the backups from Titanium (I guess the architecture will case me problems here)
Anything else e.g. in regards to tremble that I should know about? Is a backup of the stock image worth it? (guess I can download one from here anyway)
balleny said:
Hello everyone,
I just received my OP6 coming from the OPO and while I have been flashing LOS (sultans), magisk, twrp and co since my S1+, recent years obviously changed a lot.
So before bricking stuff or getting into bootloops, I briefly want to confirm if I miss something or got the order wrong:
update the stock OOS to the latest version
unlock bootloader
flash twrp
flash magisk
get root access to backup modemst1 & 2
decide if I wanna to with OOS, OOS open beta or LOS (didnt check yet if it is available with PIE)
flash ROM & magisk
flash gcam?! (worth it?)
figure out how to enable VoLTE & VoWIFI
check if I can get my banking ups running with the backups from Titanium (I guess the architecture will case me problems here)
Anything else e.g. in regards to tremble that I should know about? Is a backup of the stock image worth it? (guess I can download one from here anyway)
Click to expand...
Click to collapse
1. Settings, system, systemupdate
2. Read the big guide
3. Same as above
4. Same as 2
5. Same as above
6. Omni is good, havoc is good... All depends on your usage, you have to try the roms and decide for yourself.
7. After each rom flash you must flash twrp, then reboot to twrp then gapps then magisk if you want to use custom roms. (A/B partitions, read that info in guide section)
8. You don't flash, you install an apk. Many people like it. Up to you if you will like it. Try, just an apk.
9. For me, they worked from first boot.
10. Probably not, Google has made improvements in security and that's why titanium stopped working on bank aps etc.
Now that I have (almost accidentally) upgraded my phone to Android 11 (stock), I would like to root my POCO F2.
I am currently not interested in any custom-ROM, but I need root for proper backup and a couple of other functions.
But what is the best way? I don't want to loose Fingerprint, and Banking-applications?
I understand after unlocking the BL, I can install MAGISK by flashing a patched Boot-image.
People in this forum recommend to flash TWRP, and then install MAGISK as the better way.
So, if there is an OTA-upgrade available my TWRP and MAGISK will be gone - but what about data?
With a previous device (Xiaomi A1) instead of flashing TWRP I was just booting into TWRP to install MAGISK, is this possible with our POCO F2?
After rooting, what will NOT be working?
Who can answer?
Thanks!
Anybody?
Let me rephrase:
Installing MAGISK by flashing a patched Boot-image seems easier and a smaller change to the overall system, compared to flash TWRP and the patched Boot-image.
The method recommended by MAGISK is also flashing the patched Boot-image. Nevertheless a lot of people recommend to go via TWRP. Why? What is the advantage?
Why do you want to root your device?
just downgrade .
I like Titanium Backup, all apps working with Android Auto (eg Screen2Auto), Tasker ..
So are you saying rooting and still have Fingerprint and Banking apps working under Android 11 is not possible?
Tiemichael said:
I like Titanium Backup, all apps working with Android Auto (eg Screen2Auto), Tasker ..
So are you saying rooting and still have Fingerprint and Banking apps working under Android 11 is not possible?
Click to expand...
Click to collapse
Nothing said of all this, maybe here you will find the answers to your questions.
https://forum.xda-developers.com/t/...droid-11-and-magisk-on-xiaomi-eu-rom.4170031/
Hi guys. I know there has been a million topics about this and I've read most of them but does anyone know which route is currently the safest for an ota update? I have a 7pro rooted with Twrp and magisk. I'm on 10.0.5 and looking to update to 10.0.10.
Should I use trwp recovery and flash everything from there or can I flash locally and then use magisk along with the a/b retention script? I messed up rooting the phone originally and lost some data and now I have a mental block around which method is safest to do without losing my data or bootlooping. I want to make sure both slots update correctly and I'm unsure of the correct method.
Any help would be appreciated before I give it a go, thank you.
I'm also wondering if I've edited the build prop in any way with the build prop editor, will this cause a boot loop or will a full ota zip return it to normal anyway?
Thanks
Bxperiaz3 said:
Hi guys. I know there has been a million topics about this and I've read most of them but does anyone know which route is currently the safest for an ota update? I have a 7pro rooted with Twrp and magisk. I'm on 10.0.5 and looking to update to 10.0.10.
Should I use trwp recovery and flash everything from there or can I flash locally and then use magisk along with the a/b retention script? I messed up rooting the phone originally and lost some data and now I have a mental block around which method is safest to do without losing my data or bootlooping. I want to make sure both slots update correctly and I'm unsure of the correct method.
Any help would be appreciated before I give it a go, thank you.
Click to expand...
Click to collapse
the typical and safe route to take an OTA and keep your root is:
download OTA using oxygen downloader app
Use the sytem update app to install the file above using the local upgrade option. DO NOT REBOOT.
Use magisk to install the twrp a/b keeper script. DO NOT REBOOT.
Use magisk to install magisk to the inactive slot. Then reboot.
I have the gm1913 phone which is a different variant, but I'm sure that the concept is the same.
Good luck.
Thanks for the reply. Did something similar to this
What I ended up doing incase anyone else needs to know..
Disable all magisk modules and reboot
Flash full update from local storage
Don't reboot
Go to magisk and flash twrp zip
Don't reboot
Flash magisk zip to separate slot (ota option)
Now phone reboots its self
Re enable modules in Magisk
Reboot
Profit
Hello!
I am on an older version of Android 11 and I would like to install the latest Android 11 OTA without losing root and TWRP.
I know that I could just manually flash the lasted Android 11 firmware, then re-install TWRP and Magisk, but this would mean losing all data and having to reinstall apps, restore backups, etc...
So I was wondering if there were a quicker way to install OTA updates without losing data and root.
I know that there are many articles on the subject but they all refer to a previous version of TWRP and Magisk. Because TWRP 3.6.0 sports a completely revamped codebase I would like to know what is the latest recommended method if any.
This is my system info:
Android 11 sargo-rq1a.201105.002-factory-2433e0c0
Magisk v23
TWRP 3.6.0-11_0
Japan region
PS I do not intend to update to Android 12 yet
I ended up flashing the latest version of the stock firmware and reinstalling TWRP and root. However if you have a solution please post it for future reference.
I was looking for the same thing, didn't find any good solution, however, you can edit the flash-all script so that it doesn't wipe your data (remove the -w argument if I remember well).
reyqn said:
I was looking for the same thing, didn't find any good solution, however, you can edit the flash-all script so that it doesn't wipe your data (remove the -w argument if I remember well).
Click to expand...
Click to collapse
The flashall script will still remove TWRP and root though, right?
blksith0 said:
The flashall script will still remove TWRP and root though, right?
Click to expand...
Click to collapse
Yeah it does, you have to reflash them after
It's annoying that we can't choose the OTA android installs, it has to be the latest one. On some phones you can choose a local file, but I didn't find a way to do so with a pixel 3a.
If you were able to do this, in theory you could just flash the magisk module for twrp retention and preflash magisk on the unactive partition after installing the ota but before rebooting. Then just reboot and you keep everything.
I'm not ready to update to android 12 either (gravitybox, twrp), but I'll try then...
LastStarDust said:
I ended up flashing the latest version of the stock firmware and reinstalling TWRP and root. However if you have a solution please post it for future reference.
Click to expand...
Click to collapse
I don't understand. Just flash the Full Factory OTA zip in TWRP. That won't remove any data. And you can just check the box to "Automatically flash TWRP after zip" so that you'll keep whatever TWRP you're using. Then you just have to reboot recovery (so that you're on the updated slot) and flash the Magisk APK in TWRP. Reboot and profit.
P.S. This post belongs in Q&A.
Captain_Throwback said:
I don't understand. Just flash the Full Factory OTA zip in TWRP
Click to expand...
Click to collapse
I wondered if you could do this, apparently TWRP doesn't recommend it.
Also I had no idea how this works on a device with A/B partitions. Does TWRP automatically flash on the inactive partition?
reyqn said:
I wondered if you could do this, apparently TWRP doesn't recommend it.
Also I had no idea how this works on a device with A/B partitions. Does TWRP automatically flash on the inactive partition?
Click to expand...
Click to collapse
That 'recommendation' is specific to incremental OTAs. Also, it not generally being supported isn't the same as it not being recommended.
TWRP will install the zip to the inactive slot, and then when you reboot, the device will automatically boot into the updated slot.
Thanks for the precisions, I'll know for the next time. TWRP really is awesome
hi everyone, i flashed pixel 3a to android 12 and now my imei is 004400.... and no service ..... what should i do?
Hello all,
My phone came with ColorOS OOS 12 and I hate it. As soon as I rooted it it started crashing daily, I even reflashed a fresh oos12 image using the local update tool and only granted superuser to one app (solid explorer so I could access user files) and it still crashes. Not to mention all the apps i want to use don't work on android 12 (call recorder, busy box) and no custom recovery.
I've been reading through the forum and I found a downgrade package that looks like its hosted by oneplus: https://oxygenos.oneplus.net/OnePlu...all_2107082125_downgrade_059624cc7298428b.zip
I just wanted to make sure I am doing this correctly...
Do I use the OP Local Update app to flash?
Will I be able to flash TWRP for android 11 afterwards?
Will i need to relock the bootloader?
Should i re-root using the magisk slot b method or wait until its flashed and use TWRP?
Will it try to OTA back to android 12? If so, what's the best method to get on the latest version of android 11?
Thanks for the help.
I am running COS C.62 on my OP9 with root and having no issues. Did you make sure to do all the things in this guide?
Root OnePlus ColorOS 12 OxygenOS Android 12 via Magisk
In this tutorial, we will show you detailed steps to root your OnePlus device running ColorOS 12 Android 12 via Magisk Patched Boot.img file.
www.droidwin.com
Anyway, yes, use the local upgrade APK, put the downgrade file in the root of storage, run it. Reboot. Factory reset and wipe data to clear out any leftover crap (don't restore a backup - if you want to use Clone Phone you can do that but only restore app APKs and messages). When it reboots it should offer the latest OOS11 OTA first. If not, just download it and place it in the root and use the local upgrade function in the settings menu of the OOS11 system updater.
There is no need re-lock the bootloader and if you do, you risk a brick that has to be recovered with MSM Tool.
Root by following the guide I linked. I just went through this yesterday after flashing COS broke mobile data. I have Magisk 24.3 working with denylist, Widevine L1, and SafetyNet passes so I have Google Pay.
EtherealRemnant said:
I am running COS C.62 on my OP9 with root and having no issues. Did you make sure to do all the things in this guide?
Root OnePlus ColorOS 12 OxygenOS Android 12 via Magisk
In this tutorial, we will show you detailed steps to root your OnePlus device running ColorOS 12 Android 12 via Magisk Patched Boot.img file.
www.droidwin.com
Anyway, yes, use the local upgrade APK, put the downgrade file in the root of storage, run it. Reboot. Factory reset and wipe data to clear out any leftover crap (don't restore a backup - if you want to use Clone Phone you can do that but only restore app APKs and messages). When it reboots it should offer the latest OOS11 OTA first. If not, just download it and place it in the root and use the local upgrade function in the settings menu of the OOS11 system updater.
There is no need re-lock the bootloader and if you do, you risk a brick that has to be recovered with MSM Tool.
Root by following the guide I linked. I just went through this yesterday after flashing COS broke mobile data. I have Magisk 24.3 working with denylist, Widevine L1, and SafetyNet passes so I have Google Pay.
Click to expand...
Click to collapse
Thank you, ill give it a try.
First i used the payload.bin method and it was crashing, then i reflashed the latest OTA using the local update tool and used the magisk slot b method. still crashing.
It might have less to do with the root and more with me using root to disable certain apps (youtube, chrome, OP community, google news/podcast/tv) i dont want them on my phone but they might be too tightly integrated. If its still crashing on android 11 ill re-enable them and see if that helps.
aaronbaird1 said:
Thank you, ill give it a try.
First i used the payload.bin method and it was crashing, then i reflashed the latest OTA using the local update tool and used the magisk slot b method. still crashing.
It might have less to do with the root and more with me using root to disable certain apps (youtube, chrome, OP community, google news/podcast/tv) i dont want them on my phone but they might be too tightly integrated. If its still crashing on android 11 ill re-enable them and see if that helps.
Click to expand...
Click to collapse
Okay you're on OOS, not COS. COS doesn't have Google apps by default (but has plenty more bloatware, I just don't use it).
It's certainly possible that disabling Google apps is your problem. If you don't want Google apps, you're better off with a custom ROM that doesn't have them. CalyxOS has a beta for OnePlus 9 and it's totally de-Googled. There's also Lineage.
EtherealRemnant said:
Okay you're on OOS, not COS. COS doesn't have Google apps by default (but has plenty more bloatware, I just don't use it).
It's certainly possible that disabling Google apps is your problem. If you don't want Google apps, you're better off with a custom ROM that doesn't have them. CalyxOS has a beta for OnePlus 9 and it's totally de-Googled. There's also Lineage.
Click to expand...
Click to collapse
ahhhh. i didnt realize there was a difference. I thought OP was just calling their android 12 build ColorOS.
Either way, for custom roms i would have to go back to 11 to flash TWRP right? or can you flash custom roms using fastboot?
aaronbaird1 said:
ahhhh. i didnt realize there was a difference. I thought OP was just calling their android 12 build ColorOS.
Either way, for custom roms i would have to go back to 11 to flash TWRP right? or can you flash custom roms using fastboot?
Click to expand...
Click to collapse
You would need to back to 11 because OnePlus hasn't released working sources for 12. Just use the downgrade package, factory reset, then upgrade to 11.2.10.10 and you'll be good to go for custom ROMs. TWRP isn't used for flashing them, they all generally post their own recovery. StagOS was the best one I used (plus the dev is really responsive when there are issues) and people seem to really be enjoying Nameless but that came out after I went back to stock so I haven't tried it yet.
Before you mess with custom ROMs, make sure that you download the global MSM Tool and make sure you can connect it. Honestly since you have to go back anyway, might as well download and use the MSM Tool to get the device back to 11 anyway.
GLOBAL OnePlus 9 MSM TOOL UPDATED
Frist off Im not responsible for anything that happens to your phone!!! VERY SIMPLE IF YOU ARE BICKED,BOOTLOOPED OR JUST WANT TO GO BACK TO 100% STOCK THIS WILL WIPE ALL DATA!!! AN RELOCK BOOTLOADER OOS 11.2.4.4.LE25AA MUST HAVE QAULCOMM...
forum.xda-developers.com
Easiest way to get it into EDL is adb reboot edl but if you want to practice the key combination in case you can't get into the OS, I found if you open the MSM, check use lite firehose, and click Start before you connect the phone, it has less connection errors because it's waiting for the phone so as soon as you connect the cable, it pops up.
EtherealRemnant said:
TWRP isn't used for flashing them, they all generally post their own recovery.
Click to expand...
Click to collapse
Really??? you can tell I haven't messed with custom roms in a long time.
Thank you for all the help. I'll try it out.
aaronbaird1 said:
Really??? you can tell I haven't messed with custom roms in a long time.
Thank you for all the help. I'll try it out.
Click to expand...
Click to collapse
Yeah TWRP has issues. I soft bricked last time I tried to do anything with it and had to use MSM Tool to get back to working order.