An available update has appeared, will I lose root if I update and if so can I re-root without losing my data? Thanks.
Take the update, it should see that you are rooted and continue to download the FULL OTA (around 2Gb). Install, DO NOT REBOOT. Open Magisk Manager, click Install, Install, Install to Inactove Slot(After OTA) reboot. All done and still rooted.
Cool cheers Ill try that out.
Btw I havent been able to access the update, on the update section I am getting network timeouts when connecting and now its not showing an available update. Strange.
jackURbody said:
Btw I havent been able to access the update, on the update section I am getting network timeouts when connecting and now its not showing an available update. Strange.
Click to expand...
Click to collapse
try Oxygen Updater from Play Store
I wrote a guide with complete instructions to avoid boot looping
https://forum.xda-developers.com/oneplus-7-pro/how-to/guide-ota-updates-magisk-t3937412
Thanks for the help btw, I downloaded from that app and everything working as expected after reeinstall magisk.and twrp.
jackURbody said:
An available update has appeared, will I lose root if I update and if so can I re-root without losing my data? Thanks.
Click to expand...
Click to collapse
Take the update. (It will be the full download. Before rebooting, and while the phone is updating save the OTA. It will be in an area called OTA. Copy the zip to the top level of /sdcard.)
Use Magisk install option to root and OTA.
Once you reboot do the OTA for the other slot with local install.
Now run Magisk again and have it install to the inactive OTA.
Now both slots will have the same software and be rooted.
Related
So I unlocked by Bootloader and Rooted my OP6, the question I have is will the OTA updates be installed without any problems or will I have to install it manually?
Also when I install twrp (I have not installed yet) how will I need to update my phone through OTA?
Sorry if this is a noob question because the last time I rooted and flashed roms the software support was over so I never had any OTA updates.
Thanks
It will download the update but it most probably will download the Full 1.4GB ZIP
Meaning it will install the full rom and not the small update package.
It will install normally to the other slot and after reboot you should be updated.
This should work just fine with TWRP because it updates your other slot within Android, not in recovery.
After update, reboot phone, then reboot to TWRP and install Magisk!
I updated while being rooted and TWRP installed. Just download the update, then reflash twrp and root and everything works fine.
So if u want update your system but don't need TWRP you can just download OTA with system updater and install it.
If you want magisk don't reboot! Open magisk and press install and install to second slot. Then reboot. You will have an updated system with working magisk!
Kollachi said:
So if u want update your system but don't need TWRP you can just download OTA with system updater and install it.
If you want magisk don't reboot! Open magisk and press install and install to second slot. Then reboot. You will have an updated system with working magisk!
Click to expand...
Click to collapse
So the only hitch to get an official incremental OTA update, is the root? Unlocked bootloader and TWRP installed doesn't cause any trouble?
If you just remove the root and then check for the update, evrything gonna be fine, am I right?
But how does it work this "slot a" "slot b"? What does it mean? After an update will your OP6 get 2 roms in the same time? The new and the previous? What happen after an update and the reboot? Have you to delete the old rom?
Thx for the patience...
zappomax said:
So the only hitch to get an official incremental OTA update, is the root? Unlocked bootloader and TWRP installed doesn't cause any trouble?
If you just remove the root and then check for the update, evrything gonna be fine, am I right?
But how does it work this "slot a" "slot b"? What does it mean? After an update will your OP6 get 2 roms in the same time? The new and the previous? What happen after an update and the reboot? Have you to delete the old rom?
Thx for the patience...
Click to expand...
Click to collapse
I didn't even remove root. I can't explain you how this a and b is working. but what I know is, that every OTA is change the partition. And no u won't have 2 systems.
zappomax said:
So the only hitch to get an official incremental OTA update, is the root? Unlocked bootloader and TWRP installed doesn't cause any trouble?
If you just remove the root and then check for the update, evrything gonna be fine, am I right?
But how does it work this "slot a" "slot b"? What does it mean? After an update will your OP6 get 2 roms in the same time? The new and the previous? What happen after an update and the reboot? Have you to delete the old rom?
Thx for the patience...
Click to expand...
Click to collapse
If your current system runs for example on slot "a" the update will be installed on slot "b "...the slot that you currently not using
Nick502 said:
It will download the update but it most probably will download the Full 1.4GB ZIP
Meaning it will install the full rom and not the small update package.
It will install normally to the other slot and after reboot you should be updated.
This should work just fine with TWRP because it updates your other slot within Android, not in recovery.
After update, reboot phone, then reboot to TWRP and install Magisk!
Click to expand...
Click to collapse
So if I flash twrp now, then update OOS, only my root will be removed right which can be again flashed by twrp?
Harsh Keswani said:
So if I flash twrp now, then update OOS, only my root will be removed right which can be again flashed by twrp?
Click to expand...
Click to collapse
Yes, I'm not sure if you will keep TWRP.
But you can always reinstall TWRP and then reflash Magisk
Nick502 said:
Yes, I'm not sure if you will keep TWRP.
But you can always reinstall TWRP and then reflash Magisk
Click to expand...
Click to collapse
Thanks
Nick502 said:
Yes, I'm not sure if you will keep TWRP.
But you can always reinstall TWRP and then reflash Magisk
Click to expand...
Click to collapse
One more thing, everytime I update, it's going to download the full ROM?
Harsh Keswani said:
One more thing, everytime I update, it's going to download the full ROM?
Click to expand...
Click to collapse
If I'm not wrong, on a rooted device OTA installs a full rom. On a not-rooted phone OTA installs just the incremental update.
I only unlocked the bootloader to prepare for TRWP and root (So no TWRP and root yet) and it tells me it will download full update.
TaranQ said:
I only unlocked the bootloader to prepare for TRWP and root (So no TWRP and root yet) and it tells me it will download full update.
Click to expand...
Click to collapse
I guess it recognizes the unlocked bootloader and then it always downloads and installs full update.
Why would you unlock your bootloader and then don't root :laugh:
---------- Post added at 01:15 PM ---------- Previous post was at 01:13 PM ----------
[/COLOR]
pdppdp said:
I guess it recognizes the unlocked bootloader and then it always downloads and installs full update.
Why would you unlock your bootloader and then don't root :laugh:
Click to expand...
Click to collapse
Because I was not sure I wanted root again there are always apps that even with Magisk hide won't work.
But just to make sure I prepared by unlocking bootloader so if I decide to go for TWRP and root my data and storage won't get wiped which would mean starting all over again and losing app-data.
So, if I update from a ROM rooted with TWRP, will not the user data be deleted? Should we just root again and install the TWRP?
I had rooted 5.1.5 with TWRP and Magisk. I just downloaded the full package, copied it to phone storage. Then went to system update, update locally, picked the file and it ran the update.
However after reboot and update complete I lost TWRP and root. So I went to fastboot, booted the official TWRP (fastboot boot twrp.img). Then flashed the official TWRP and Magisk for root, rebooted and all was good again.
I'm pretty sure there's an easier way of doing this but this worked for me.
marvel79 said:
I had rooted 5.1.5 with TWRP and Magisk. I just downloaded the full package, copied it to phone storage. Then went to system update, update locally, picked the file and it ran the update.
However after reboot and update complete I lost TWRP and root. So I went to fastboot, booted the official TWRP (fastboot boot twrp.img). Then flashed the official TWRP and Magisk for root, rebooted and all was good again.
I'm pretty sure there's an easier way of doing this but this worked for me.
Click to expand...
Click to collapse
In theory, with the Oxygen Updater application you can install the OTA and Magisk in 1 step.
sakun-ice said:
In theory, with the Oxygen Updater application you can install the OTA and Magisk in 1 step.
Click to expand...
Click to collapse
Yeah probably but it has a lot of mixed reviews and this takes me 10 minutes more or so oh well. I'll rather do it like this It's not like we get a new update every week
maybe to help you all
me: 5.1.5, unlocked bootloader, unofficial TWRP from thread by wuxianlin, magisk 16.4
my procedure was to change to official twrp which can be done easily by
downloading the twrp installer from official site, put to internal storage
flash twrp official installer
still in recovery, select reboot: recovery
flash magisk
boot system
now download full 5.1.6 signed flashable zip
recovery: flash 5.1.6
reflash recovery
reboot recovery
flash magisk
boot system
now you have rooted 5.1.6 with official twrp and magisk, no wipe needed
I have a rooted One Plus 6 running on stock Oxygen OS 9.0 There is an OTA update available at the moment. I have used FlashFire on my previous phone (Nexus 6P) and it worked flawlessly in keeping the root and applying OTA updates without any steps required. All I had to do was launch the app, it detected the firmware, and I would let it install. I purchased the professional version of the app as the free version stopped working at some point.
When I launch the same app on my OP6 and select "Flash zip or OTA" option I get another screen that has three options to check:
1. Auto-mount: Mount common paths before running update. Rarely necessary. Enable for A/B device OTAs, disable for all other OTAs.
2. Mount / system read / write: Mount /system read / write by default, rather than read-only. Doing this only once may break the future OTAs, Enable when flashing custom firmwares.
3. Restore boot and recovery images: Attempt to restore boot and recovery images before flashing. May be required for some OTA. Disable for non-OTA updates.
What's confusing me is the third option as that is already checked. It sounds like this option would install a factory image back on the phone? Should I uncheck it and check #1 as the only option?
If your bl is unlocked then you can't use ota to update. You have to flash the full zip in twrp.
se7ensde said:
If your bl is unlocked then you can't use ota to update. You have to flash the full zip in twrp.
Click to expand...
Click to collapse
I just found the instructions for update in another thread. I will have to use the blu-spark twrp to update it. Since I have never done it before, my question is, is it going to leave all the data and the app data intact? Things like pictures, videos, messages from messaging apps? Because in my mind I always thought of flashing the full image the same way as reinstalling the OS on any desktop computer - it deletes everything.
I am guessing the answer is no?
Is your bl already unlocked?
se7ensde said:
Is your bl already unlocked?
Click to expand...
Click to collapse
BL is unlocked and the phone is rooted.
shagexpert said:
BL is unlocked and the phone is rooted.
Click to expand...
Click to collapse
okay so if you have it setup Google will backup your apps calls and network settings and you will be able to sign out to your Google account and choose to restore it. For photos.. If you have Google photos installed it will backup everything you have told it to. But you shouldn't have to worry about any of this if you are just dirty flashing the update. Everything will be the way it was is like an ota only difference is you manually flashing the full room zip in twrp. So if your just dirty flashing you shouldn't lose any data.
Thanks! I will give it a try sometime later this week.
2 months ago I decided to root my Pixel 3(to improve Camera Performance). While rooting I mistakenly download Factory Image of Pixel3 XL(crosshatch) and patch it with magisk after that phone went into boot loop . After some period of time I recognized my childish mistake and downloaded the latest factory image for pixel 3(blueline) first flash the stock image to get phone out of boot loop after then I rooted without any problem. But since that day I am not being able to receive any OTA updates for my device, is it because I removed the stock OS and flashed Factory Image of my own , and also If i want to sideload OTA updates with magisk what are the procedure for that.
P.S Thanks in Advance....much needed help
Rahul_Yf said:
2 months ago I decided to root my Pixel 3(to improve Camera Performance). While rooting I mistakenly download Factory Image of Pixel3 XL(crosshatch) and patch it with magisk after that phone went into boot loop . After some period of time I recognized my childish mistake and downloaded the latest factory image for pixel 3(blueline) first flash the stock image to get phone out of boot loop after then I rooted without any problem. But since that day I am not being able to receive any OTA updates for my device, is it because I removed the stock OS and flashed Factory Image of my own , and also If i want to sideload OTA updates with magisk what are the procedure for that.
P.S Thanks in Advance....much needed help
Click to expand...
Click to collapse
If you're rooted you can't take an ota directly. But follow this guide and you can get the ota, apply it, and root again. Pay attention to when you can reboot. https://topjohnwu.github.io/Magisk/tutorials.html
Rahul_Yf said:
2 months ago I decided to root my Pixel 3(to improve Camera Performance). While rooting I mistakenly download Factory Image of Pixel3 XL(crosshatch) and patch it with magisk after that phone went into boot loop . After some period of time I recognized my childish mistake and downloaded the latest factory image for pixel 3(blueline) first flash the stock image to get phone out of boot loop after then I rooted without any problem. But since that day I am not being able to receive any OTA updates for my device, is it because I removed the stock OS and flashed Factory Image of my own , and also If i want to sideload OTA updates with magisk what are the procedure for that.
P.S Thanks in Advance....much needed help
Click to expand...
Click to collapse
That was discussed in several posts here recently: https://forum.xda-developers.com/app...32382/page3857
Apparently it has been going on for 3 years now. Some people are impacted, others are not. Luckily, I have not been impacted so far.
You can sideload the OTA. Instructions are at https://developers.google.com/android/ota You must re-root after sideloading.
Hi,
Same problem here.
But the link https://topjohnwu.github.io/Magisk/tutorials.html doesn't work, neither this one : https://forum.xda-developers.com/app...32382/page3857
Can someone tell me how make the OTA update ?
Thanks
Nik0LaAs said:
Hi,
Same problem here.
But the link https://topjohnwu.github.io/Magisk/tutorials.html doesn't work, neither this one : https://forum.xda-developers.com/app...32382/page3857
Can someone tell me how make the OTA update ?
Thanks
Click to expand...
Click to collapse
The new link is https://topjohnwu.github.io/Magisk/
The Magisk forum on XDA has shutdown. Use Github instead.
dcarvil said:
The new link is https://topjohnwu.github.io/Magisk/
The Magisk forum on XDA has shutdown. Use Github instead.
Click to expand...
Click to collapse
Thanks for the link.
But if I follow the guide, it says:
After restoring stock images, apply OTAs as you normally would (Settings → System → System Update).
But the problem is my phone doesn't receive OTA updates
I'm stuck in November security update, and my phone doesn't see any update. So what can I do ?
Nik0LaAs said:
Thanks for the link.
But if I follow the guide, it says:
After restoring stock images, apply OTAs as you normally would (Settings → System → System Update).
But the problem is my phone doesn't receive OTA updates
I'm stuck in November security update, and my phone doesn't see any update. So what can I do ?
Click to expand...
Click to collapse
I don't get update notifications, but I see the update when I do Settings → System → System Update. If you don't even see them, you'll have to download the image from https://developers.google.com/android/ota, then sideload it and reroot. You may be able to patch the downloaded image before sideloading, but that opens the door for more potential problems. I wouldn't recommend it.
dcarvil said:
I don't get update notifications, but I see the update when I do Settings → System → System Update. If you don't even see them, you'll have to download the image from https://developers.google.com/android/ota, then sideload it and reroot. You may be able to patch the downloaded image before sideloading, but that opens the door for more potential problems. I wouldn't recommend it.
Click to expand...
Click to collapse
Unfortunately, when I do Settings → System → System Update, my phone doesn't see any update. It stucks in November
So I cannot keep my root ? There is no other way to update ?
Nik0LaAs said:
Unfortunately, when I do Settings → System → System Update, my phone doesn't see any update. It stucks in November
So I cannot keep my root ? There is no other way to update ?
Click to expand...
Click to collapse
No other way to my knowledge. You can re-root after the update.
Hi,
After installing Magisk i no longer receive OTA Updates. The safety net checks are ok. How can i fix this?
Thanks.
+1
Sent from my Pixel 3 using Tapatalk
adrianppa said:
Hi,
After installing Magisk i no longer receive OTA Updates. The safety net checks are ok. How can i fix this?
Thanks.
Click to expand...
Click to collapse
AFAIK, your only choices are to sideload the OTA from https://developers.google.com/android/ota and re-root. You can also flash the factory image and re-root. Be sure to remove the -w from flash-all.bat/sh so you don't wipe your data. I prefer the factory image method. You can patch boot.img before flashing the image, which makes re-rooting a bit easier. I believe there have been some reports of OTA working again after flashing the factory image.
well you have root duh lol, off course otas will fail, at least they dont install unlike old times when install would be error
there are many ways to install but this is the easiest for me every month
each month download full system image
copy boot to phone and patch it with magisk apk, copy back to pc
apply full system image flash all.bat but remove the -w from the .bat (Edit the bat)
this will install the lastest ota but you wont lose any data or settings, everything well be okay
root is lost, now you have to root again
boot magisk boot image
apply direct install in magisk apk
restart
this has to be done every month
you can also uninstall magisk every month and let the ota download and install but that is even slower and annoying, this is how is done
The last System Update notification received was the Update from Android 11 to Android 12. It installed fine. Can keep up via sideload or a full manual flash, but why no notification of updates?
Are you bootloader unlocked and/or rooted?
I have never received an OTA notice or been able to do OTAs but I rooted as soon as I got my pixel 4a.
There was one update that was offered but it was strange, and was the first and only time a separate AU firmware was made.
My children have pixel 4as and get OTAs just fine.
a1291762 said:
Are you bootloader unlocked and/or rooted?
I have never received an OTA notice or been able to do OTAs but I rooted as soon as I got my pixel 4a
Click to expand...
Click to collapse
Bootloader unlocked and rooted from Day 1. I was notified of the update from A11 to A12 and was able to use the system OTA. Otherwise I have sideloaded or flashed the Factory Image.
Even with auto update off in Dev Options, all I read says one shiuld still receive notification of the OTA. Guess I'll contune to sideload
a1291762 said:
Are you bootloader unlocked and/or rooted?
I have never received an OTA notice or been able to do OTAs but I rooted as soon as I got my pixel 4a.
There was one update that was offered but it was strange, and was the first and only time a separate AU firmware was made.
My children have pixel 4as and get OTAs just fine.
Click to expand...
Click to collapse
How long after update release (usually 5th of the month or so) do they see their 4a updates?
I have a 4a, rooted and unlocked. When new updates come out (I check the https://developers.google.com/android/ota page), I just uninstall magisk from the phone, run the system update, then re-install magisk and re-root. I believe it was Monday night April 3 when I did it last. If you don;t mind the hassle of all the reboots, I find it an easy enough way to keep updated and rooted.
amphi66 said:
How long after update release (usually 5th of the month or so) do they see their 4a updates?
Click to expand...
Click to collapse
It can vary a little (I think sometimes google stages the roll out?), but it's normally pretty soon after. The April update was already offered and installed.
augggg said:
I just uninstall magisk from the phone, run the system update, then re-install magisk and re-root.
Click to expand...
Click to collapse
How do you get the new boot image for rooting after doing the OTA?
a1291762 said:
How do you get the new boot image for rooting after doing the OTA?
Click to expand...
Click to collapse
I do it by extracting/Magisk patching the boot.img from the Factory Image. Of course I had to sideload the OTA as it didn't show up in System updates.
a1291762 said:
How do you get the new boot image for rooting after doing the OTA?
Click to expand...
Click to collapse
For 4a, go to the latest factory image here, which is at the bottom of each phone's list of images: https://developers.google.com/android/images#sunfish
Download the factory image, then unzip the file. Go into the folder you get, then unzip the next zip file you see (starts with image-sunfish*), and look for the boot.img file. Should be 64mb
Thanks @augggg and @amphi66.
I use the factory image to upgrade each month. But since I have to download it, I see no value in doing an on-device OTA (ie. Uninstall Magisk, reboot, OTA, etc.)
@augggg mentioned uninstalling Magisk to OTA so I wondered if they had an alternative way of getting the boot image besides downloading the factory image or full OTA (which is a bit harder to unpack, but also includes the whole boot.img).
I suppose one could boot TWRP to extract the new boot.img from the phone and then use Magisk to patch that... But I feel like it'd end up being a lot more work than the few changed lines it takes to flash the factory image, and my download speeds aren't bad enough to make that faster
Since I have to download the full factory image inorder to patch the boot.img, I use the factory image to update as well.
But I would like to know the status of the technique to "uninstall-restore Images" in Magisk, not reboot, update via OTA, not reboot, "install to inactive slot" in Magisk, then finally reboot.
For me, an OTA system update is never found.
lbush said:
Since I have to download the full factory image inorder to patch the boot.img, I use the factory image to update as well.
But I would like to know the status of the technique to "uninstall-restore Images" in Magisk, not reboot, update via OTA, not reboot, "install to inactive slot" in Magisk, then finally reboot.
For me, an OTA system update is never found.
Click to expand...
Click to collapse
Exactly. Worked for me once, but have not seen an OTA nofication since
Just a May followup. 10 days w/ innumerable System Update checks and still have not seen the auto-rollout of the May OTA Update. Yes, I can certainly sideload OTA or flash the (already downloaded) Factory Image, but is this a typical delay? I was thinking 2 or 3 days after release. Thanks.
amphi66 said:
Just a May followup. 10 days w/ innumerable System Update checks and still have not seen the auto-rollout of the May OTA Update. Yes, I can certainly sideload OTA or flash the (already downloaded) Factory Image, but is this a typical delay? I was thinking 2 or 3 days after release. Thanks.
Click to expand...
Click to collapse
Gave up & sideloaded May OTA, followed by flashing the Magisk-patched boot.img to retain root. Still do not know why there was no OTA notification