Related
Hey, guys, I wanted to ask if someone tried OTA updates working with the new method of rooting released with magisk 14- a rooting method in which we do not need root or custom recovery beforehand, we just need to provide stock boot image dump to the magisk manager. This method will do us good because if OTA's still work after root we can be rooted on the stock roms without having to download full OTA's when a new update arrives. If someone can confirm working OTA's on the OOS open beta with this root method, it would be really helpful. Thank you!
As long as you take a backup of system and keep TWRP installed so you have a backup to revert to it should be fine. The risk of issues is just too high unless you don't give a **** about your personal data.
Puddi_Puddin said:
As long as you take a backup of system and keep TWRP installed so you have a backup to revert to it should be fine. The risk of issues is just too high unless you don't give a **** about your personal data.
Click to expand...
Click to collapse
Bro, I know how to work with TWRP. Your comment does not answer the question.
blaze95rs said:
Bro, I know how to work with TWRP. Your comment does not answer the question.
Click to expand...
Click to collapse
Well think of it about this. Magisk is just one big hack on the system partition. An OTA changes files on the system partition aswell. What if the OTA changes files that Magisk needs?
1. Your phone will go into a bootloop.
2. You might end up bricking it.
3. You just have to reflash Magisk.
4. Your phone becomes buggy as hell.
Thats why we also recommend to install the full zips when flashing roms and kernels that modify system because of possible conflicts.
Puddi_Puddin said:
Well think of it about this. Magisk is just one big hack on the system partition. An OTA changes files on the system partition aswell. What if the OTA changes files that Magisk needs?
1. Your phone will go into a bootloop.
2. You might end up bricking it.
3. You just have to reflash Magisk.
4. Your phone becomes buggy as hell.
Thats why we also recommend to install the full zips when flashing roms and kernels that modify system because of possible conflicts.
Click to expand...
Click to collapse
Obviously I would uninstall magisk and then install ota and reinstall magisk. Magisk is systemless so I think there shouldn't be any problem.
blaze95rs said:
Obviously I would uninstall magisk and then install ota and reinstall magisk. Magisk is systemless so I think there shouldn't be any problem.
Click to expand...
Click to collapse
See it for yourself! Its something most people do not recommend.
Puddi_Puddin said:
See it for yourself! Its something most people do not recommend.
Click to expand...
Click to collapse
You have missed the whole point of the post. This is a NEW method. Many people have not tried this method of root. So please, if you have any valuable information then only share. Do not litter. There should be logic to your answer and not general acceptance. Saying that many people do this or do that is not a very solid answer.
blaze95rs said:
You have missed the whole point of the post. This is a NEW method. Many people have not tried this method of root. So please, if you have any valuable information then only share. Do not litter. There should be logic to your answer and not general acceptance. Saying that many people do this or do that is not a very solid answer.
Click to expand...
Click to collapse
That doesn't matter. I get that it can be installed without a custom recovery. But that doesn't mean it won't conflict with possible ota's. Again, see it for yourself. Most people including me do rather play it the safe way.
I have recently updated to the lateset Oxygen OS Beta i had Magisk installed, i use Sparks Latest twrp version, with this you can install OTA updates. I dit not unlinstalled Magisk first, you do need the full rom file, but for me when i wanted to install the OTA, it found i had rooted and autmatacly downloaded the full rom. After you installed the update you can install the latest version of Magisk.
Okay, I'm running 8.1 on December 5th security patch, with Magisk and stock kernel.
I want to update my phone (mostly because it's nagging me), and I also want to run Elemental X.
Can someone help a noobie out? What should I do in order/steps to update my phone without loosing my data/app arrangements?
Magisk is obviously preventing me from being able to do OTA, and when I tried to "Uninstall" Magisk, my phone wouldn't boot anymore and I had to restore from NANDroid.
TIA!
XDA451 said:
Okay, I'm running 8.1 on December 5th security patch, with Magisk and stock kernel.
I want to update my phone (mostly because it's nagging me), and I also want to run Elemental X.
Can someone help a noobie out? What should I do in order/steps to update my phone without loosing my data/app arrangements?
TIA!
Click to expand...
Click to collapse
This should help :good:
https://forum.xda-developers.com/pixel-2-xl/how-to/guide-unlock-flash-root-pixel-2-xl-t3702418
Badger50 said:
This should help :good:
https://forum.xda-developers.com/pixel-2-xl/how-to/guide-unlock-flash-root-pixel-2-xl-t3702418
Click to expand...
Click to collapse
Thanks! I've used Nathan's guide before, I forgot it even existed!
XDA451 said:
Thanks! I've used Nathan's guide before, I forgot it even existed!
Click to expand...
Click to collapse
It's definitely worth bookmarking! He's a wizard at this stuff! :good:
Hi All,
I am currently rooted via Magisk with TWRP installed. I am unable to install the Feb OTA update because of this mostly. I am planning to get stock recovery while keeping the root - question is if I do this via the AIO tool <https://forum.xda-developers.com/pixel-2-xl/development/tool-tool-one-driversunlocktwrpfactory-t3730226> - will i lose all my data?
Thanks,
J2
arpanj2 said:
Hi All,
I am currently rooted via Magisk with TWRP installed. I am unable to install the Feb OTA update because of this mostly. I am planning to get stock recovery while keeping the root - question is if I do this via the AIO tool <https://forum.xda-developers.com/pi...l-tool-one-driversunlocktwrpfactory-t3730226> - will i lose all my data?
Thanks,
J2
Click to expand...
Click to collapse
If you want to take the ota, you need to be unrooted, and on stock recovery. You won't lose your data if your careful with the toolkit.
Badger50 said:
If you want to take the ota, you need to be unrooted, and on stock recovery. You won't lose your data if your careful with the toolkit.
Click to expand...
Click to collapse
Thanks Badger! For some reason I thought systemless root works with OTA.
arpanj2 said:
Thanks Badger! For some reason I thought systemless root works with OTA.
Click to expand...
Click to collapse
It used to, but not so much on this phone. Friendly advice for ya, learn how to flash factory images, and ditch the OTA's. Much quicker, and less room for error that side loading or waiting on OTA's. Just my opinion my friend ?
Badger50 said:
It used to, but not so much on this phone. Friendly advice for ya, learn how to flash factory images, and ditch the OTA's. Much quicker, and less room for error that side loading or waiting on OTA's. Just my opinion my friend
Click to expand...
Click to collapse
Hi badger,
If you are referring to steps laid out here - https://developers.google.com/android/images, then I can do it. Won't it still require me to be unrooted?
I am not that Tech agnostic - so if I am wrong, can you refer me to a thread where this is outlined. My only thing is that I get latest patches and still get to keep root without losing data
Thanks,
J2
arpanj2 said:
Hi badger,
If you are referring to steps laid out here - https://developers.google.com/android/images, then I can do it. Won't it still require me to be unrooted?
I am not that Tech agnostic - so if I am wrong, can you refer me to a thread where this is outlined. My only thing is that I get latest patches and still get to keep root without losing data
Thanks,
J2
Click to expand...
Click to collapse
Yep, that's the one. No, you don't have to be unrooted for it to work. You won't even lose any data once you learn the -w trick(you'll see) Here's a guide written by Flash, the kernel Dev Jedi Master. Look over that thread, and you'll figure it out pretty quick I bet ?
https://forum.xda-developers.com/pixel-2-xl/how-to/guide-unlock-flash-root-pixel-2-xl-t3702418
Badger50 said:
Yep, that's the one. No, you don't have to be unrooted for it to work. You won't even lose any data once you learn the -w trick(you'll see) Here's a guide written by Flash, the kernel Dev Jedi Master. Look over that thread, and you'll figure it out pretty quick I bet
https://forum.xda-developers.com/pixel-2-xl/how-to/guide-unlock-flash-root-pixel-2-xl-t3702418
Click to expand...
Click to collapse
Sounds perfect - I will get this done tonight
Thanks so much Badger! :angel:
arpanj2 said:
Sounds perfect - I will get this done tonight
Thanks so much Badger! :angel:
Click to expand...
Click to collapse
Welcome bro! Give em hell :good:
I can second this method. I flash factory images with root/unlocked bootloader. It is easy to do.
Just downloaded full zip update for the OP9P Global vLE2125_11.C.44_1440_2022201182114
I have a question... I have 2123 not 2125. Previous i have c38 eu but now I just update to c40 global and next c44 thought the updater. I need to re root I need to install install the boot.img from global? In the info my device is still 2123
Nope. You are good
Poloasis said:
Just downloaded full zip update for the OP9P Global vLE2125_11.C.44_1440_2022201182114
Click to expand...
Click to collapse
I got that update as well. Is it Android 12 or still 11?
Thank you
netgar said:
I got that update as well. Is it Android 12 or still 11?
Thank you
Click to expand...
Click to collapse
12
Just installed it. Looks like gcam access to all cameras is restored.
Poloasis said:
12
Click to expand...
Click to collapse
Thank you. So I guess I can't just root as always.
Have you been able to root it?
I downloaded the update from oxygen updater.
OnePlus9ProOxygen_22.E.44_OTA_1440_all_2201182111_30de568cd.zip
I got the EU ver. When i update i wont stick. Still the same. What am i doing wrong?
alpadie said:
I downloaded the update from oxygen updater.
OnePlus9ProOxygen_22.E.44_OTA_1440_all_2201182111_30de568cd.zip
I got the EU ver. When i update i wont stick. Still the same. What am i doing wrong?
Click to expand...
Click to collapse
Have u download the full zip? Your devices is rooted? If yes u need to restore stock boot.img and next install the update
davyleggend said:
Have u download the full zip? Your devices is rooted? If yes u need to restore stock boot.img and next install the update
Click to expand...
Click to collapse
Yes the full zip. I have root. How do i restore boot.img? And I guess that means no more root. Do We have root for the new one?
alpadie said:
Yes the full zip. I have root. How do i restore boot.img? And I guess that means no more root. Do We have root for the new one?
Click to expand...
Click to collapse
Open magisk and uninstall next local upgrade. For re root i'm waiting because I don't know what boot.img i need to flash. Probably i make it by my self.
davyleggend said:
Open magisk and uninstall next local upgrade. For re root i'm waiting because I don't know what boot.img i need to flash. Probably i make it by my self.
Click to expand...
Click to collapse
Okej thanks for the info. I'l will wait for when we have root
Installed C.44 EU over C.38 EU using local update app, latest Magisk Alpha, and keep root using the Magisk OTA option before rebooting after the update.
No need to unroot to upgrade
i went from c.39 to c.40 the day before yesterday. i used mlgmxyysd's tool to flash c39's stock images to the device then updated through the updater.
found the flashed boot image, flashed it (just like the old way, fastboot flash boot.img).
i then installed c.44 ota, went to magisk, installed it to the inactive slot, rebooted, and it ran fine.
with magisk alpha, you don't need the toolbox anymore (i believe)
Anyone have problem with haptics on c44? Haptics feedback is just missing on some menu actions.
Looks like an issue with work profile. Work apps such as MS Teams forces closed and an 'IT doesn't allow multiple users' toast notification pops up. Dang!
Damn... I better stay with A11
I have notification of update to le2123 have not updated yet
Any users any issues with certain apps android auto, Spotify etc
Use phone for work and don't want to feck it up
funkyirishman said:
I have notification of update to le2123 have not updated yet
Any users any issues with certain apps android auto, Spotify etc
Use phone for work and don't want to feck it up
Click to expand...
Click to collapse
If you're using a work profile you're more than likely going to run into bother. I do and intune won't install company policy certificate in the work profile rendering it useless
hallo dare said:
If you're using a work profile you're more than likely going to run into bother. I do and intune won't install company policy certificate in the work profile rendering it useless
Click to expand...
Click to collapse
I don't have a work profile but use certain apps like ms authentication and rsa secure I'd to log in
Hi,
I am currently on Android 12, rooted with Magisk, and I update each month using the latest Factory Image.
If (when) I upgrade to Android 13...
- I know it's usually recommended to do a clean install when you go to a brand new build, which means wiping data. I'm okay with this ASIDE from the fact that I have GBs worth of music on my phone which takes forever to both back up and restore.
- Do I really need to install 13 to both slots?
- Is root / Magisk working fine on 13?
- Any other suggestions on how to make this upgrade easier?
Thanks in advance!
Tony
tonyfiore75 said:
Hi,
I am currently on Android 12, rooted with Magisk, and I update each month using the latest Factory Image.
If (when) I upgrade to Android 13...
- I know it's usually recommended to do a clean install when you go to a brand new build, which means wiping data. I'm okay with this ASIDE from the fact that I have GBs worth of music on my phone which takes forever to both back up and restore.
- Do I really need to install 13 to both slots?
- Is root / Magisk working fine on 13?
- Any other suggestions on how to make this upgrade easier?
Thanks in advance!
Tony
Click to expand...
Click to collapse
it would be recommended to flash at least the bootloader to both slots, root works perfectly fine
tonyfiore75 said:
Hi,
I am currently on Android 12, rooted with Magisk, and I update each month using the latest Factory Image.
If (when) I upgrade to Android 13...
- I know it's usually recommended to do a clean install when you go to a brand new build, which means wiping data. I'm okay with this ASIDE from the fact that I have GBs worth of music on my phone which takes forever to both back up and restore.
Click to expand...
Click to collapse
I haven't wiped before flashing a new version of Android on my Pixel phones in the last 5-6 years. Android 13 Stable that I manually updated using the full factory image, coming from the first Android 12 July update has worked fine for me.
Good thing, too, because I hate starting from scratch any more.
(I too have hundreds of GBs of music on my phone)
tonyfiore75 said:
- Do I really need to install 13 to both slots?
Click to expand...
Click to collapse
"Have to"? No. It would be good advice to install it to both slots, though.
tonyfiore75 said:
- Is root / Magisk working fine on 13?
Click to expand...
Click to collapse
Yes.
tonyfiore75 said:
- Any other suggestions on how to make this upgrade easier?
Thanks in advance!
Tony
Click to expand...
Click to collapse
No. Everything was just like every month's normal update process for me with flashing the full firmware zip to update, and then I flashed it again to the other slot the next day.
Thanks, everyone! I really appreciate it. I'll just flash the update as I normally would (editing the .bat file) to Slot A and then do the same to Slot B. Or can you flash it to -all slots at the same time? I know I used to do that with my Pixel 4 but that may have just been when flashing the magisk file.
tonyfiore75 said:
Or can you flash it to -all slots at the same time?
Click to expand...
Click to collapse
Yes, you can.
Cool, thanks.
Sorry it's my first time with root and a custom kernel in the pixel, I have never updated it because I installed it on June, could you post a guide with the commands please?
Thanks a lot!
jumpet said:
Sorry it's my first time with root and a custom kernel in the pixel, I have never updated it because I installed it on June, could you post a guide with the commands please?
Thanks a lot!
Click to expand...
Click to collapse
Hiya! Just click the yellow How To Guide quick filter at the top of list of threads in this section, and there are at least two or three threads for how to update. The OP of the thread in my signature below also has the commands.
roirraW edor ehT said:
Yes, you can.
Click to expand...
Click to collapse
If I have to flash to both slots with the factory image, do I also have to flash to both slots with the updated Magisk file as well?
Didn't come to the forum to read messages in the past few days! I updated my P6P from A13 beta 4.1 to official using the factory image -w method as I have done it in the past 10 months. It is now running smoothly and I didn't encounter any problem so far. I start reading messages saying that A13 has to be flashed in slot A and slot B. Since I already upgrade my machine with normal method, I still able to keep my data, root and API integrity, and most import booting up normally, so do I have do it again to reflash to this Slot A/B thing? I am not so sure I understand this new requirement, so sorry if this question sounds stupid.
tonyfiore75 said:
If I have to flash to both slots with the factory image, do I also have to flash to both slots with the updated Magisk file as well?
Click to expand...
Click to collapse
Not really. Just do it on the slot you end up running. The slot you won't be running won't have root, but that's okay. You'll likely never actually use the other slot, and if by some rare chance you do, it's an easy thing to flash the Magisk'd stock boot.img to it at that time.
acwcanada said:
Didn't come to the forum to read messages in the past few days! I updated my P6P from A13 beta 4.1 to official using the factory image -w method as I have done it in the past 10 months. It is now running smoothly and I didn't encounter any problem so far. I start reading messages saying that A13 has to be flashed in slot A and slot B. Since I already upgrade my machine with normal method, I still able to keep my data, root and API integrity, and most import booting up normally, so do I have do it again to reflash to this Slot A/B thing? I am not so sure I understand this new requirement, so sorry if this question sounds stupid.
Click to expand...
Click to collapse
I'm trying to answer on mobile, so it's tough for me because most detailed support I give I do from the computer but I can't right now.
Check out the OP and last few pages of the thread on my signature below (use desktop mode in a mobile browser if necessary) for more information about flashing to both slots.
Look at it this way. Normally you only flash the full factory image once (so only to one slot). This time you did it once already, so now you'll have to switch slots and flash it to the other slot.
You could then switch slots again and use the slot you already re-rooted. Both slots have the same exact apps and app data - the second flashed slot just won't have the rooted boot.img that you already have on the slot you're running now.
I think it's most simple to use the Google flash tool. You don't have to wipe anything, just unroot, run the tool, reroot. Not script editing and praying that you didn't screw anything up.
rhetorician said:
I think it's most simple to use the Google flash tool. You don't have to wipe anything, just unroot, run the tool, reroot. Not script editing and praying that you didn't screw anything up.
Click to expand...
Click to collapse
That's how I do it every month
roirraW edor ehT said:
I'm trying to answer on mobile, so it's tough for me because most detailed support I give I do from the computer but I can't right now.
Check out the OP and last few pages of the thread on my signature below (use desktop mode in a mobile browser if necessary) for more information about flashing to both slots.
Look at it this way. Normally you only flash the full factory image once (so only to one slot). This time you did it once already, so now you'll have to switch slots and flash it to the other slot.
You could then switch slots again and use the slot you already re-rooted. Both slots have the same exact apps and app data - the second flashed slot just won't have the rooted boot.img that you already have on the slot you're running now.
Click to expand...
Click to collapse
OK, thanks so much, achieved done that. One more question, how about the future updates? Do we have to do it every month in the future when Google provide the monthly updates?
acwcanada said:
OK, thanks so much, achieved done that. One more question, how about the future updates? Do we have to do it every month in the future when Google provide the monthly updates?
Click to expand...
Click to collapse
No, you only needed to flash to both slots this one time just to make sure both slots were on A13.
Lughnasadh said:
No, you only needed to flash to both slots this one time just to make sure both slots were on A13.
Click to expand...
Click to collapse
Thank you for the feedback.
rhetorician said:
I think it's most simple to use the Google flash tool. You don't have to wipe anything, just unroot, run the tool, reroot. Not script editing and praying that you didn't screw anything up.
Click to expand...
Click to collapse
No need to unroot - just run the tool (making sure wipe or force flash all partitions isn't selected), and then reroot.
I like the satisfaction of getting my hands a little dirty, plus the knowledge that if something goes wrong, it's most probably my fault!
I also like to Magisk my own boot.img from the factory image, and if I'm going to download it anyway, I figure might as well flash it.