Dear all
Device: Pixel C
I am on 8.1.(July) and I want to apply the August security update.
I am rooted with Magisk.
TWRP 3.2.2. installed
Q: how do I flash the August security update without losing data, root/Magisk?
- I assume I just have to download the factory image of August, extract it and flash boot.img, system.img and vendor.img
- Do I lose root and Magisk then?
- Will i keep TWRP in doing so?
- If TWRP is kept, would it be enough to apply the magisk.zip with TWRP again?
tnx for confirmation or any hints!
Hello guys,
I got a OnePlus 7 pro
I am with the version 11.0.0.2 rooted with a modified boot.img
There is a way to update my phone to 11.0.2.1 without losing my data and the root ?
Thanks
Uninstall magisk reflash stock boot.img with backup or from 11.0.0.2 rom zip.
Then update to 11.0.2.1
Then reinstall magisk and reflash modified boot.img of 11.0.2.1
prad1po said:
Hello guys,
I got a OnePlus 7 pro
I am with the version 11.0.0.2 rooted with a modified boot.img
There is a way to update my phone to 11.0.2.1 without losing my data and the root ?
Thanks
Click to expand...
Click to collapse
Download oxygen updater
Download full stable build on your 7 pro version latest version
Once downloaded go to your setting and system update
Select local upgrade, wait til the update finishes but DO NOT RESTART
Once the update reaches to 100% go to Magisk
Select Magisk install
Select install to inactive slot (after ota)
Watch magisk load and NOW YOU CAN REBOOT
Hello thank you very much
This method is working
Hello everyone. I have unlocked and rooted T5 AGS2-W09 with 8.0.0.360 (OCEC431) stock firmware. Since few days ago I received a notification that there is a firmware update : 8.0.0.371 (OCEC431). Can somebody advise what is the best way to update without loosing root ?
Thanks in advance.
I just reroot it by patching ramdisk.img (extracted from update.zip) with magisk and flashing it back using fastboot
Hello, I have a OnePlus 9 running android 12 c.40 and I'm trying to update to c.47. When I try and update it says installation problem half way through. I've tried clearing the storage to most system and Google apps along with hiding them from magisk with no luck. I'm unsure if there's a way to update manually with Android 12 because I could not find a way. I was only able to update through TWRP before in which it is incompatible with Android 12. Would appreciate any help with this!
SeeTurtle said:
Hello, I have a OnePlus 9 running android 12 c.40 and I'm trying to update to c.47. When I try and update it says installation problem half way through. I've tried clearing the storage to most system and Google apps along with hiding them from magisk with no luck. I'm unsure if there's a way to update manually with Android 12 because I could not find a way. I was only able to update through TWRP before in which it is incompatible with Android 12. Would appreciate any help with this!
Click to expand...
Click to collapse
Google-ota detects altered partitions and ota fails... Your boot img is altered to root. Restore stock boot img for build your on currently. Google your method.
Google-ota detects altered partitions and ota fails... Your boot img is altered to root. Restore stock boot img for build your on currently. Google your method.
Click to expand...
Click to collapse
So I just completely uninstalled magisk and used the flash toolbox to retire stock images. I also flashed the stock boot.img myself but still with no luck
SeeTurtle said:
So I just completely uninstalled magisk and used the flash toolbox to retire stock images. I also flashed the stock boot.img myself but still with no luck
Click to expand...
Click to collapse
Did you also flash a custom kernel?
mattie_49 said:
Did you also flash a custom kernel?
Click to expand...
Click to collapse
Yes but I reflashed the stock kernel
SeeTurtle said:
Yes but I reflashed the stock kernel
Click to expand...
Click to collapse
Here is your other issue. Dtbo,vendor_boot stock untouched need flashed back.
SeeTurtle said:
Yes but I reflashed the stock kernel
Click to expand...
Click to collapse
This doesn't matter
mattie_49 said:
Here is your other issue. Dtbo,vendor_boot stock untouched need flashed back.
Click to expand...
Click to collapse
Unfortunately still getting the same error
I am in the same situation. I only had my OP 9 for a couple of weeks and I came from a OP 5 where rooting and flashing was much easier. It would be good to know what you did to get OOS updated.
So when you download the package, you can use Oxygen Updater to install it. Choose the root package and it will install with Magisk, you will lose Twrp recovery. But you can just flash that back afterwards. Worked like a charm for me
I don't have TWRP cause it's not compatible with Android 12. I've had to factory reset the last 3 updates because of this same issue. When I had TWRP I could update with oxygen update and keep root. Being android 12 I also don't have the option to manually update via the phones update system. I don't mind factory resetting again because I have swift backup. I'd just like to know how to avoid it. Like if I could just flash it with fastboot or something
I downloaded the Oxygen Updater app and downloaded the full OTA however not able to use the auto update method simply because TWRP does not work on A12. There is a manual process where you need to download the OP Local Update APK and use this to flash the update. I have not tried this myself but I would assume you would lose root doing this method and need to root your phone again.
Z-Blade said:
I downloaded the Oxygen Updater app and downloaded the full OTA however not able to use the auto update method simply because TWRP does not work on A12. There is a manual process where you need to download the OP Local Update APK and use this to flash the update. I have not tried this myself but I would assume you would lose root doing this method and need to root your phone again.
Click to expand...
Click to collapse
This worked! I uninstalled root in the first place so losing it didn't matter. This is the Apk. You have to remove the .zip in order to turn it into an APK. Thanks for the tip!
SeeTurtle said:
This worked! I uninstalled root in the first place so losing it didn't matter. This is the Apk. You have to remove the .zip in order to turn it into an APK. Thanks for the tip!
Click to expand...
Click to collapse
Sweet! I have downloaded the full OTA and extracted the boot.img so I can use Magisk to patch it to get root again. I still haven't gone through the process yet but thanks for letting us know this method works. Also thanks to @illusiveairforce for leading us to the Oxygen Updater app.
mattie_49 said:
Here is your other issue. Dtbo,vendor_boot stock untouched need flashed back.
Click to expand...
Click to collapse
Hi,
What else should I reflash to make sure all root traces are removed ?
abl.img
aop.img
bluetooth.img
boot.img
boot.on mobile.img
cpucp.img
devcfg.img
dsp.img
dtbo.img
engineering_cdt.img
featenabler.img
hyp.img
imagefv.img
keymaster.img
modem.img
multiimgoem.img
my_bigball.img
my_carrier.img
my_company.img
my_engineering.img
my_heytap.img
my_manifest.img
my_preload.img
my_product.img
my_region.img
my_stock.img
odm.img
oplusstanvbk.img
oplus_sec.img
product.img
qupfw.img
qweslicstore.img
shrm.img
splash.img
system.img
system_ext.img
tz.img
uefisecapp.img
vbmeta.img
vbmeta_system.img
vbmeta_vendor.img
vendor.img
vendor_boot.img
vm-bootsys.img
xbl.img
xbl_config.img
Hi folks, I am running a Pixel 6A that I rooted with magisk back in December. I stupidly did not disable OTA updates. Last night the QPR2 update came down and wiped root from my phone.
Bootloader is still unlocked and magisk app is installed.
I am confused about the best way to restore root. I see that the QPR2 beta required the use of the pixel 7 boot image. Does that still hold for the stable QPR2?
Also, the magisk app offers a way to choose and patch an image within the app. Can I get the pixel 7 boot image and patch it in magisk, or do I have to use the ADB/ fastboot method?
Sorry for the trouble. I promise I will disable OTA updates in the future. Thanks for any help.
Hello! I am also root user and if it is true that there was an update with the boot 6a not root and I had to use the pixel 7 or 7 pro (I do not remember which was) but if in doubt I would try only with the 6a just in case, the procedure is to download the full rom of the same version you have now, extract the boot.img, patch it with magisk and flash it by adb from the pc, is the method I use in each update and no problems until today, good luck and greetings!
If you are using Magisk Stable 26.1 or Canary 26101, you can use the Pixel 6a boot image to root as the problems mentioned above have been fixed with these versions of Magisk.
Problem solved. Y'all rock.
I'm having a similar problem. I'm am unable to find the boot.img anywhere in the zip file I'm on Bluejay TQ2A 230305.008E1.
RimWulf said:
I'm having a similar problem. I'm am unable to find the boot.img anywhere in the zip file I'm on Bluejay TQ2A 230305.008E1.
Click to expand...
Click to collapse
Download and open the zip => open "image-bluejay-tq2a.230305.008.e1.zip" => find your boot.img