Related
I read some stuff about doing an OTA update with Magisk (v18) on my Pixel 3 (Feb 2019), but I still have a few questions about doing it. I'd rather avoid re-installing TWRP and Magisk from recovery again, and I'd like to be able to do this all without my computer if possible (see planned process below).
1. From what I've read, I should be able to restore a stock boot image to the inactive boot partition (from within Magisk Manager) , then install the Update (both steps 1 and 2), then reinstall Magisk Manager to the inactive boot partition.. And then reboot, and I should have the update, and keep TWRP and Magisk, right? (just looking for confirmation of the process)
2. I never provided a stock image to Magisk when I installed it originally, and I don't have one right now. How do I extract the boot image from the stock image on the Android website?
3. And do I need to indicate to Magisk that I have a boot image, or will it ask me when I go in to restore non-root?
4. Are OTA updates cumulative, or do I need to update the stock boot image each update?
Thanks!
madhattr999 said:
I read some stuff about doing an OTA update with Magisk (v18) on my Pixel 3 (Feb 2019), but I still have a few questions about doing it. I'd rather avoid re-installing TWRP and Magisk from recovery again, and I'd like to be able to do this all without my computer if possible (see planned process below).
1. From what I've read, I should be able to restore a stock boot image to the inactive boot partition (from within Magisk Manager) , then install the Update (both steps 1 and 2), then reinstall Magisk Manager to the inactive boot partition.. And then reboot, and I should have the update, and keep TWRP and Magisk, right? (just looking for confirmation of the process)
2. I never provided a stock image to Magisk when I installed it originally, and I don't have one right now. How do I extract the boot image from the stock image on the Android website?
3. And do I need to indicate to Magisk that I have a boot image, or will it ask me when I go in to restore non-root?
4. Are OTA updates cumulative, or do I need to update the stock boot image each update?
Thanks!
Click to expand...
Click to collapse
Although what you described works for some devices it won't on the pixel. To update and have twrp and root you'll need a pc. If the ota would flash when you have twrp and root, it won't, it would overwrite twrp and the patched boot image. So you're back to needing a pc to get twrp and install magisk.
For your other questions, if you extract the factory image you'll find another zip file in there. That's were the image files are and you need to extract that zip. And, ota's are cumulative so you don't need install previous ones. But specifically to the boot image, a previous months boot image may or may not be the same as the current one, etc.
jd1639 said:
Although what you described works for some devices it won't on the pixel. To update and have twrp and root you'll need a pc. If the ota would flash when you have twrp and root, it won't, it would overwrite twrp and the patched boot image. So you're back to needing a pc to get twrp and install magisk.
Click to expand...
Click to collapse
I'm confused then. Isn't the method I described specifically for a phone with two boot partitions?
The instructions I am trying to reference:
Devices with A/B Partitions
Due to the fact that these devices have two separate partitions, it is possible to have the OTA installed to the inactive slot and have Magisk Manager to install Magisk onto the updated partition. The out-of-the-box OTA installation works seamlessly and Magisk can be preserved after the installation.
After restoring stock boot image, apply OTAs as you normally would (Settings → System → System Update).
Wait for the installation to be fully done (both step 1 and step 2 of the OTA), do not press the restart button!! Instead, go to (Magisk Manager → Install → Install to Inactive Slot) and install Magisk to the slot that the OTA engine just updated.
After installation is done, press the reboot button in Magisk Manager. Under-the-hood Magisk Manager forces your device to switch to the updated slot, bypassing any possible post-OTA verifications.
After the reboot, your device should be fully updated, and most importantly, Magisk is still installed to the updated system!
Click to expand...
Click to collapse
madhattr999 said:
I'm confused then. Isn't the method I described specifically for a phone with two boot partitions?
The instructions I am trying to reference:
Click to expand...
Click to collapse
It is, but it doesn't work on the pixel. Google's security, probably the M chip, but I may be wrong, prevents it from working. In theory, magisk should be able to patch a boot image on your device and you shouldn't need the magisk zip but that doesn't work either. You can certainly try what you're describing but backup at least your data partition with twrp and have it off your device before you try. Get the contents of your internal sdcard to if you have stuff there you don't want to lose.
Most likely restoring the stock boot image and trying to install the ota will just not work, but you never know.
jd1639 said:
It is, but it doesn't work on the pixel. Google's security, probably the M chip, but I may be wrong, prevents it from working. In theory, magisk should be able to patch a boot image on your device and you shouldn't need the magisk zip but that doesn't work either. You can certainly try what you're describing but backup at least your data partition with twrp and have it off your device before you try. Get the contents of your internal sdcard to if you have stuff there you don't want to lose.
Most likely restoring the stock boot image and trying to install the ota will just not work, but you never know.
Click to expand...
Click to collapse
Thanks, I'll back up my files and try that.
Well, as far as I know twrp backups only work for data (with verity and all that). Always bootloop on a vendor or system restore. Back up your data a million times and go for it. Worse thing that happens is back to zero. Wait, you said no computer? Well, put it on a free cloud saving service, have your data backed up out there. Not advertizing for any service in particular, but backing up data is something everyone should be thinking about.
I am about to go for broke on this device for the 4th time. Non boot several times, flashing, flashing, building, flashing. I have the added benefit of figuring out if cell service works as the vendor.img always breaks it. Good times mate.
I might be missing something here, so please clarify if there is a way to "Get March OTA without having to re-install Magisk/TWRP", and how. Wondering about exactly that. Thank you.
madhattr999 said:
I'm confused then. Isn't the method I described specifically for a phone with two boot partitions?
The instructions I am trying to reference:
Click to expand...
Click to collapse
What you have quoted works fine for me. I did both February and March update with this method on my P3 and no problems.
The only thing i noticed is that it takes more than 20 minutes to do step 2 of the instalation (optimizing apps)
But to be on the safe side, please backup.
Another thing: i don't have TWRP recovery, just Magisk root
fronten said:
I might be missing something here, so please clarify if there is a way to "Get March OTA without having to re-install Magisk/TWRP", and how. Wondering about exactly that. Thank you.
Click to expand...
Click to collapse
There is no way to do so. Either side loading the OTA, or fastbooting the factory image, will still require you to install root and twrp. Which, really isn't a big deal at all :good:
Badger50 said:
There is no way to do so. Either side loading the OTA, or fastbooting the factory image, will still require you to install root and twrp. Which, really isn't a big deal at all :good:
Click to expand...
Click to collapse
But the person above you said he was able to do it on both recent updates...
madhattr999 said:
But the person above you said he was able to do it on both recent updates...
Click to expand...
Click to collapse
He doesn't have twrp and if you do have twrp the ota won't work for sure. So you're welcome to try if you're only rooted, no twrp. But patching the boot image and installing it from magisk hasn't worked, but maybe it does now. Let us know.
dracushor87 said:
What you have quoted works fine for me. I did both February and March update with this method on my P3 and no problems.
The only thing i noticed is that it takes more than 20 minutes to do step 2 of the instalation (optimizing apps)
But to be on the safe side, please backup.
Another thing: i don't have TWRP recovery, just Magisk root
Click to expand...
Click to collapse
@dracushor87, can you confirm that the process described by @madhattr999 worked correctly? I have a Pixel 3, rooted with Magisk, without TWRP. I would like to apply the monthly updates as easily as possible: without wiping data, uninstall/reinstall Magisk, etc.
Specifically:
madhattr999 said:
1. From what I've read, I should be able to restore a stock boot image to the inactive boot partition (from within Magisk Manager) , then install the Update (both steps 1 and 2), then reinstall Magisk Manager to the inactive boot partition.. And then reboot, and I should have the update, and keep TWRP and Magisk, right? (just looking for confirmation of the process)
Click to expand...
Click to collapse
I looked through Magisk Manager, and don't see a way to "restore a stock boot image to the inactive boot partition".
In the installed state, I don't see any functions for patching or installing boot images within Magisk Manager.
timg11 said:
@dracushor87, can you confirm that the process described by @madhattr999 worked correctly? I have a Pixel 3, rooted with Magisk, without TWRP. I would like to apply the monthly updates as easily as possible: without wiping data, uninstall/reinstall Magisk, etc.
Specifically:
I looked through Magisk Manager, and don't see a way to "restore a stock boot image to the inactive boot partition".
In the installed state, I don't see any functions for patching or installing boot images within Magisk Manager.
Click to expand...
Click to collapse
Yes, i confirm. Before you start, please check if there is an update available. If there is, restore image, update, reinstall magisk and then reboot. If you reboot without reinstalling magisk, you will lose root. To install on the inactive slot, just click install in magisk manager and then you will be asked what method to use. If what i said is unclear, just requote me
dracushor87 said:
Yes, i confirm. Before you start, please check if there is an update available. If there is, restore image, update, reinstall magisk and then reboot. If you reboot without reinstalling magisk, you will lose root. To install on the inactive slot, just click install in magisk manager and then you will be asked what method to use. If what i said is unclear, just requote me
Click to expand...
Click to collapse
Used this method after the May update finally arrived for me yesterday. Backed up everything just in case, but it worked flawlessly.
Hey guys, i used to have a Pixel 2 XL and Deuces always worked for me to install monthly updates, but this time i tried the same method and ended up with a corrupted Pixel 3, had to flash stock images to fix it.
What is the best method to install monthly updates on a rooted Pixel 3? Just edit the flass-all to remove the -w? Or is there an easier way such as uninstalling Magisk or something?
Cheers
Either flash-all minus the -w or sideload the OTA with stuck recovery. No other methods to keep data. If you are installing TWRP (and not just using the fastboot boot instance leaving stock recovery), then using the flash-all (minus -w) saves you from having to flash boot.img first to get stock recovery back. Either method will require you to re-root and reinstall TWRP.
sliding_billy said:
Either flash-all minus the -w or sideload the OTA with stuck recovery. No other methods to keep data. If you are installing TWRP (and not just using the fastboot boot instance leaving stock recovery), then using the flash-all (minus -w) saves you from having to flash boot.img first to get stock recovery back. Either method will require you to re-root and reinstall TWRP.
Click to expand...
Click to collapse
Thanks, so there is currently no way to just click "Uninstall" from within Magisk Manager and let the OTA install automatically, right? I read a comment in another thread in which the OP was trying to do that
luizffgarcia said:
Thanks, so there is currently no way to just click "Uninstall" from within Magisk Manager and let the OTA install automatically, right? I read a comment in another thread in which the OP was trying to do that
Click to expand...
Click to collapse
Could it be done? Maybe, but it would take just as much work. You would have to uninstall Magisk, TWRP, a kernel and possibly other things to get the OTA to auto-run and install properly. Then, you would have to deal with timing of the OTA showing up once you have "unmodified" the phone. OTA showing up is hit and miss. I have been doing it on both a Pixel and Pixel XL (and now P3/P3XL) since the OG was released 3 years ago. I have used OTA sideloads a couple of times when I want to force a slot change. The flash-all (without -w) is the fastest, most reliable method and requires no prework except for the -w text deletion. All of the work is on the backside. Fastboot flash TWRP, install TWRP, install kernel, root. PLus, all of your magisk hide settings are retained. You are just flashing Magisk package to bring back root. You have to do all of that with a true OTA or sideload OTA as well.
luizffgarcia said:
Thanks, so there is currently no way to just click "Uninstall" from within Magisk Manager and let the OTA install automatically, right? I read a comment in another thread in which the OP was trying to do that
Click to expand...
Click to collapse
Without TWRP it is possible, I have seen people do it but I have not.
Open Magisk and uninstall root, do not reboot.
Take the OTA, do not reboot.
Open Magisk and install but install to the inactive slot since that is what you will boot to after reboot.
Reboot and cross your fingers. Don't try this unless you are near a computer and ready to flash all minus the -w.
I still prefer the flash all method. Clean, easy, fast and never fails.
*Note* Some people have had success with this, while some others have not. You do this at your own risk.
Prerequisites:
Magisk Manager might need to be unhidden based on reports from some users.
Magisk needs to have a backup of stock boot.img.
Preserve AVB 2.0/dm-verity must be enabled. (Have gotten mixed reports on this it might or might not be needed)
Check the following post if you don't meet the prerequisites
https://forum.xda-developers.com/showpost.php?p=81186247&postcount=73
Update Process
When phone detects update
1. Disable any desired Magisk modules, ex. Edxposed (I usually disable all modules just to be safe)
2. Reboot
3. In Magisk, select Uninstall, press Restore Images
4. Do NOT Reboot
5. Install OTA Update via Settings -> System -> System Updates
6. When prompted to reboot, Do NOT Reboot
7. In Magisk Manager press Install
8. Select Install to Inactive Slot
9. Reboot
10. Enable the Magisk modules one by one
In case of bootloop after enabling a module there are 2 ways that I know of on how to retain root and fix bootloop.
One requires ADB
While phone is stuck in bootloop, connect phone to PC and run this commands via ADB.
adb wait-for-device shell magisk --remove-modules
adb reboot
This will remove all modules and you should be able to boot.
The second way is via fastboot. More information in this thread.
https://forum.xda-developers.com/pixel-4-xl/themes/magisk-modules-disabler-booting-magisk-t3990557
Some information that might help some people.
eg1122 said:
I know some users flash patched boot.img that someone else patched, thus bypassing the creation of a backup. I think choosing or not choosing to preserve avb 2.0/dm-verity also affects if phone will take OTA. I always preserve mine and always patch my own boot.img so I haven't ran into any issues. I'll just have to wait and see what happens on my end once I get the update. This reminds me of some issues some people where getting early on when rooting. Some people had to flash the patched boot.img to both a/b slots and some people didn't. Having both slots with a patched boot will also break the restoring of stock boot.img as Magisk only restores the active slot.
Click to expand...
Click to collapse
If you do it this way you'll be using the patched boot image from the previous update and not the current one.
airmaxx23 said:
If you do it this way you'll be using the patched boot image from the previous update and not the current one.
Click to expand...
Click to collapse
No it doesn't. When you select install to inactive slot it patches the newly installed boot.img that has been installed to the inactive slot. Only reason phone promts you to reboot after an update is to switch slots.
For whatever reason, whenever I would try to do Uninstall - Restore images (in step 3 of the OP), I would get a toast error saying "Stock backup does not exist"
I'm not sure why the expected backup files hadn't been created. I suspect it has to do with the process of manually patching the boot image whilst initially rooting, as suggested in this Git issue.
Anyway, I was ultimately able to work around this, and was eventually able to get Uninstall - Restore images to work.
I wrote about my workaround method here.
pdfruth said:
For whatever reason, whenever I would try to do Uninstall - Restore images (in step 3 of the OP), I would get a toast error saying "Stock backup does not exist"
I'm not sure why the expected backup files hadn't been created. I suspect it has to do with the process of manually patching the boot image whilst initially rooting, as suggested in this Git issue.
Anyway, I was ultimately able to work around this, and was eventually able to get Uninstall - Restore images to work.
I wrote about my workaround method here.
Click to expand...
Click to collapse
Yeah, there needs to be a backed up stock boot img for this to work. Being able to restore images the way stated in the issue would solve this as you could just restore a stock boot.img then continue doing the steps.
So does this work for every update? Just do the steps and it works? Im a complete noob when it comes to this stuff i just follow the write ups and pray!
DemonicMurderer said:
So does this work for every update? Just do the steps and it works? Im a complete noob when it comes to this stuff i just follow the write ups and pray!
Click to expand...
Click to collapse
Yes, it has worked for me all the time. These are the exact steps recommended by topjohnwu, I just made them more readibly available to users. Here is a link to his tutorial.
https://topjohnwu.github.io/Magisk/tutorials.html#ota-installation
This work for the Verizon Pixel 4 XL???
SAMCR02018 said:
This work for the Verizon Pixel 4 XL???
Click to expand...
Click to collapse
Why would you need to since your not rooted with a locked bootloader? Just take the OTA.
Badger50 said:
Why would you need to since your not rooted with a locked bootloader? Just take the OTA.
Click to expand...
Click to collapse
Ok the can the Verizon version get the BL unlocked?
SAMCR02018 said:
Ok the can the Verizon version get the BL unlocked?
Click to expand...
Click to collapse
Nope. Unless you got lucky and they sold you a google version by mistake.
SAMCR02018 said:
Ok the can the Verizon version get the BL unlocked?
Click to expand...
Click to collapse
There is a write up for that.
Does anybody know if this also work with a custom kernel? I thought removing root and let magisk install old (boot) image should reinstall stock boot.img (if magisk first was installed through fastboot with stock kernel). Then i can take ota, patch inactive slot with magisk and then reboot. After reboot i can install custom kernel again througj ex kernel manager app. Does anybody know if this works?
Donric13 said:
Does anybody know if this also work with a custom kernel? I thought removing root and let magisk install old (boot) image should reinstall stock boot.img (if magisk first was installed through fastboot with stock kernel). Then i can take ota, patch inactive slot with magisk and then reboot. After reboot i can install custom kernel again througj ex kernel manager app. Does anybody know if this works?
Click to expand...
Click to collapse
Yes this method works with custom kernel. Magisk removed custom kernel when it restores stock boot.img
When does the dec patch come out, on the 5th?
I just started the process then realized it wasn't out yet so I haven't rebooted. When I go to the step of installing to the inactive slot I get a warning that you should only do this after the ota update - does anyone know if I'll be OK to go ahead with it even though I haven't done the ota yet?
in_dmand said:
When does the dec patch come out, on the 5th?
I just started the process then realized it wasn't out yet so I haven't rebooted. When I go to the step of installing to the inactive slot I get a warning that you should only do this after the ota update - does anyone know if I'll be OK to go ahead with it even though I haven't done the ota yet?
Click to expand...
Click to collapse
I wouldn't do it until the Dec ota comes out and that may be later today or sometime this week. Which is weird since all the other Pixels got it but hey it's Google
in_dmand said:
When does the dec patch come out, on the 5th?
I just started the process then realized it wasn't out yet so I haven't rebooted. When I go to the step of installing to the inactive slot I get a warning that you should only do this after the ota update - does anyone know if I'll be OK to go ahead with it even though I haven't done the ota yet?
Click to expand...
Click to collapse
Since it's not out yet, just do a direct install in Magisk to re-install it
Thanks for this guide !
Does anyone know how to update and maintain root for manually updating using OTA files ? Usually the update takes a long time to reach my phone, so I update using OTA files.
mkpansare said:
Thanks for this guide !
Does anyone know how to update and maintain root for manually updating using OTA files ? Usually the update takes a long time to reach my phone, so I update using OTA files.
Click to expand...
Click to collapse
The other way I update is using full factory images. Once you download the zip, extract it and find and open (via Notepad++ or similar advanced text editor) the flash-all.bat or flash-all.sh (depends on your system), find this line
fastboot -w update
replace with
fastboot update
Basically remove the -w, this will prevent a factory reset (wipe) on your device. Once it is done you will need to patch new boot.img via magisk and flash the newly patched boot.img via fastboot.
Hope this helps!
ps. I recommend to always disable Magisk Modules before updating as they could cause FC
eg1122 said:
Since it's not out yet, just do a direct install in Magisk to re-install it
Click to expand...
Click to collapse
Thanks that worked perfect... Was gonna be a long week without adblocker and lmt pie lol
I'm trying to update from 11.0.11.11 to 11.0.12.12 incremental update from oxygen updater and having this error:
"Fail on install system update" on 1% progress bar.
Try from system OTA and same error occur.
Somebody try and it work?
Thanks
just installed the same firmware without issue
jushhh said:
I'm trying to update from 11.0.11.11 to 11.0.12.12 incremental update from oxygen updater and having this error:
"Fail on install system update" on 1% progress bar.
Try from system OTA and same error occur.
Somebody try and it work?
Thanks
Click to expand...
Click to collapse
If you are rooted and/or have TWRP installed, then you need to restore the stock boot and/or recovery images before starting the update.
Then I will lose root access?
Not if you do it properly.
If you're using TWRP, then you'll have to restore the stock recovery.
If you're rooted then you can restore the stock boot using Magisk>Uninstall Magisk>Restore images but don't reboot or you'll lose root.
Then download and install the incremental update manually. Then install Magisk to the inactive slot and reboot.
See https://forum.xda-developers.com/t/...1-kb2003-kb2005.4178675/page-30#post-85801253
jushhh said:
Then I will lose root access?
Click to expand...
Click to collapse
1) Update software but DO NOT REBOOT
2) Open Magisk > tap install > tap Install to inactive slot > NOW reboot.
Make sure you disable any and all modules first. No need to uninstall, just disable them. Mainly just a precaution. Possibly remove security from the lockscreen too for good measure.
I lost root the other day actually forgetting to properly install Magisk before rebooting and now I have to buy a laptop just to root again.
BillGoss said:
Not if you do it properly.
If you're using TWRP, then you'll have to restore the stock recovery.
If you're rooted then you can restore the stock boot using Magisk>Uninstall Magisk>Restore images but don't reboot or you'll lose root.
Then download and install the incremental update manually. Then install Magisk to the inactive slot and reboot.
See https://forum.xda-developers.com/t/...1-kb2003-kb2005.4178675/page-30#post-85801253
Click to expand...
Click to collapse
Thanks @BillGoss, your instructions are perfect. Work like a charm.
Anyone have the stock firmware or stock image for 11.0.12.12.KB05AA? Trying to root it.
ClassickWORLD said:
Anyone have the stock firmware or stock image for 11.0.12.12.KB05AA? Trying to root it.
Click to expand...
Click to collapse
Use TWRP: https://forum.xda-developers.com/t/guide-rooting-oos-with-twrp.4327417/
since i did it manually and ended up with no boot.img backup from magisk, i had to manually extract boot.img from my last ota 11.0.11.11.KB05AA and reflash it through fastboot. then it let me update and i rerooted.
I get the notification but can't even try it because when i tap on it, it does nothing.
dazoe said:
I get the notification but can't even try it because when i tap on it, it does nothing.
Click to expand...
Click to collapse
I managed to install the update, I used oxygen updater to download the update, used restore images option in magisk, installed update (DID NOT REBOOT), used install to inactive slot in magisk, then rebooted.
Seems like it all went well.
BillGoss said:
If you are rooted and/or have TWRP installed, then you need to restore the stock boot and/or recovery images before starting the update.
Click to expand...
Click to collapse
Do I have root and twrp, what should I restore? Only recovery? If so, you have maybe some stock for 11.0.11.11 kb05ba? I don't know why, but I only have a copy of the boot.
e1thx said:
Do I have root and twrp, what should I restore? Only recovery? If so, you have maybe some stock for 11.0.11.11 kb05ba? I don't know why, but I only have a copy of the boot.
Click to expand...
Click to collapse
Use payload dumper to get a copy of the .11 recovery.
BillGoss said:
Use payload dumper to get a copy of the .11 recovery.
Click to expand...
Click to collapse
I have root and twrp, what should I restore? Only recovery? And then magic restore?
e1thx said:
I have root and twrp, what should I restore? Only recovery? And then magic restore?
Click to expand...
Click to collapse
Read Post #5.
BillGoss said:
Read Post #5.
Click to expand...
Click to collapse
I have read it, that's why I am asking.I need to recover two partitions? Or one
e1thx said:
I have read it, that's why I am asking.I need to recover two partitions? Or one
Click to expand...
Click to collapse
What don't you understand in post #5? You said you're rooted. So post #5 tells you what to do.
BillGoss said:
What don't you understand in post #5? You said you're rooted. So post #5 tells you what to do.
Click to expand...
Click to collapse
Sorry Bill, I get it all now. I just have to do as You wrote:
1) restore the stock boot using Magisk>Uninstall Magisk>Restore images but don't reboot or you'll lose root
2) install update manually, System update>Gear icon (local upgrade)
3) install Magisk to the inactive slot and reboot
Last question, where or how to download update manually?
e1thx said:
Sorry Bill, I get it all now. I just have to do as You wrote:
1) restore the stock boot using Magisk>Uninstall Magisk>Restore images but don't reboot or you'll lose root
2) install update manually, System update>Gear icon (local upgrade)
3) install Magisk to the inactive slot and reboot
Last question, where or how to download update manually?
Click to expand...
Click to collapse
Ah, well that's tricky if it's not available from OnePlus or the XDA rom thread. I believe Oxygen updater app will give you the rom also, but I've never used it.
Edit: just read your post again and I'm confused: what rom exactly are you looking for?
This thread is about ending up on 11.0.12.12.KB05AA
And if you're looking for that one you'll find it in https://forum.xda-developers.com/t/updates-thread.4188149/post-86165983
Halp! 🫠
I have all the correct partitions, but my fingerprint reader hasn't worked since I successfully got to Android 13 with root. Literally everything else works with the phone. I've tried a lot, but haven't been successful so hoping someone could point me in the right direction.
OnePlus 9
LE2115
Global (US)
I guess none of my sensors work? Audio and camera are fine... 🫠
Try flashing the rom again. A lot of people including me having weird bugs like missing stock apps and status bar missing. In your case is finger print. I would try flashing the rom and try rooting again. You should be able to obtain boot.img and gain root from there. Or just install to inactive slot.
Nhatlienhoan said:
Try flashing the rom again. A lot of people including me having weird bugs like missing stock apps and status bar missing. In your case is finger print. I would try flashing the rom and try rooting again. You should be able to obtain boot.img and gain root from there. Or just install to inactive slot.
Click to expand...
Click to collapse
My phone just got this OTA, but it's not showing up on oxygen updater?
LE2115_11.F.17_ 2170_202211231112
See attachments. In order to complete your suggestion, what are my steps but to upgrade to the newest version (listed above)?
-Remove password unlock on phone
-Back up everything 15 times
Remove/uninstall magisk modules
-Download latest Ota (listed above) either via oxygen updater or somehow through normal Ota process but *not* rebooting after completing
-Uninstall magisk
-Install Ota (listed above) and *don't* reboot
-Open magisk and install to inactive slot and reboot
-Check Magisk and root status
-Re-add magisk modules and password unlock, etc.
-Reboot, back everything up again as fresh upgrade- bobs your uncle, no chance, that's never how it actually goes down
Do I have that process more or less correct? At any point in that process should I backup partitions or extract fastboot anything? I'd like to complete your suggestion but now since there's an Ota I'd like to kill 2 birds 1 stone (if possible ).
fhedeitx said:
My phone just got this OTA, but it's not showing up on oxygen updater?
LE2115_11.F.17_ 2170_202211231112
See attachments. In order to complete your suggestion, what are my steps but to upgrade to the newest version (listed above)?
-Remove password unlock on phone
-Back up everything 15 times
Remove/uninstall magisk modules
-Download latest Ota (listed above) either via oxygen updater or somehow through normal Ota process but *not* rebooting after completing
-Uninstall magisk
-Install Ota (listed above) and *don't* reboot
-Open magisk and install to inactive slot and reboot
-Check Magisk and root status
-Re-add magisk modules and password unlock, etc.
-Reboot, back everything up again as fresh upgrade- bobs your uncle, no chance, that's never how it actually goes down
Do I have that process more or less correct? At any point in that process should I backup partitions or extract fastboot anything? I'd like to complete your suggestion but now since there's an Ota I'd like to kill 2 birds 1 stone (if possible ).
Click to expand...
Click to collapse
Usually, with previous ota updates do you have problem updating and regaining root like uninstall magisk/restore image: error in this step or error in the download of the ota? Because for some reason, this usually the case for me, and even with my completely uninstall magisk still error to download ota. But after msm (because I did some stupid thing) then I don't even need to restore image ib magisk to download ota.
As long as you be able to download ota, then install to inactive slot then reboot and you're good.
But incremental update usually has problem to retain magisk. I still suggest reflash the F16 to see if the finger print issue resolved. You always can flash the new incremental later any way.
Nhatlienhoan said:
Usually, with previous ota updates do you have problem updating and regaining root like uninstall magisk/restore image: error in this step or error in the download of the ota? Because for some reason, this usually the case for me, and even with my completely uninstall magisk still error to download ota. But after msm (because I did some stupid thing) then I don't even need to restore image ib magisk to download ota.
As long as you be able to download ota, then install to inactive slot then reboot and you're good.
But incremental update usually has problem to retain magisk. I still suggest reflash the F16 to see if the finger print issue resolved. You always can flash the new incremental later any way.
Click to expand...
Click to collapse
No matter what I do or how many times I read the directions, something still always goes wrong lol. How might one download a fresh LE2115_11_F.16 image? I used Oxygen Updater to get the file but I want to "re-download" the image- I can't with Oxygen Updater since I'm on LE2115_11_F.16 currently.
edit- this file?
Can you please spell it out for me using my sudo steps above? Download F.16 from above and put it in platform tools > adb fastboot reboot > fastboot set_active=? > fastboot boot F.16bootpatched.img > fastboot flash boot F.16boot.img > reboot > install magisk, etc.
fhedeitx said:
No matter what I do or how many times I read the directions, something still always goes wrong lol. How might one download a fresh LE2115_11_F.16 image? I used Oxygen Updater to get the file but I want to "re-download" the image- I can't with Oxygen Updater since I'm on LE2115_11_F.16 currently.
edit- this file?
Can you please spell it out for me using my sudo steps above? Download F.16 from above and put it in platform tools > adb fastboot reboot > fastboot set_active=? > fastboot boot F.16bootpatched.img > fastboot flash boot F.16boot.img > reboot > install magisk, etc.
Click to expand...
Click to collapse
I'm uploading the full ota f16. But the steps are:
Download full ota file (>4GB)
Install via local updater for android 12 apk
Don't reboot
Magisk/install to inactive slot
Reboot
I found that flashing only boot.img didn't change anything, so the whole package of ota was needed in my case. Will edit and update the full OTA file here after the uploading done.
Nhatlienhoan said:
I'm uploading the full ota f16. But the steps are:
Download full ota file (>4GB)
Install via local updater for android 12 apk
Don't reboot
Magisk/install to inactive slot
Reboot
I found that flashing only boot.img didn't change anything, so the whole package of ota was needed in my case. Will edit and update the full OTA file here after the uploading done.
Click to expand...
Click to collapse
Thanks! Followed your steps. Got back to... Right where I was haha. None of my sensors work nor does fingerprint
fhedeitx said:
Thanks! Followed your steps. Got back to... Right where I was haha. None of my sensors work nor does fingerprint
Click to expand...
Click to collapse
Lol. It was fine on android 12? Weird, really. Maybe try doing the same steps again. If not, I don't have anything else to add. Hopefully someone else knows more could help.