Hi guys,
I'm trying to understand if this (thread title) is possible and which is the right way.
I would like use OTA for this, but if not possible also manual update is good for me (but how? MiFlash?).
Issue: I have to install a Tasker plugin as system app: Nougat+ Tasker Tethering Control and this should change my system partition and not allow me to update by OTA, is it right? ...or my misunderstanding?
I would like also use app like AdAway that need read/write access to system partition to change hosts file.
Question: So what is the best way for keep phone rooted, allow system modification ant at the same time preserving OTA or stock rom update?
Thanks a lot for all suggestions and answer!
someone? any suggestions?
Install that tasker app as Magisk module and allow systemless hosts modification in Magisk settings. This way you won't have to modify system partition directly.
Two ways to update,
1. OTA
2. Miflash - which you have to download the rom. normally you have wait few days or week after OTA release.
No matter how you update, it will restore stock system. Thats mean you have to reinstall above apps everytime you update.
ltf_195 said:
Two ways to update,
1. OTA
2. Miflash - which you have to download the rom. normally you have wait few days or week after OTA release.
No matter how you update, it will restore stock system. Thats mean you have to reinstall above apps everytime you update, unless you root with Magisk.
Click to expand...
Click to collapse
Reading this page: https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md
NOTE: In order to apply OTAs, you HAVE to make sure you haven't modified /system (and /vendor if available) in anyway, even remounting the partition to rw will tamper block verification!!
Click to expand...
Click to collapse
So if I write my system partition, I think OTA don't running anymore.
note: for install system app (write sytem partition) as I need, of course I'll root my phone...there isn't other way, isn't it?
kam1kazze said:
So if I write my system partition, I think OTA don't running anymore.
Click to expand...
Click to collapse
Correct
kam1kazze said:
note: for install system app (write sytem partition) as I need, of course I'll root my phone...there isn't other way, isn't it?
Click to expand...
Click to collapse
If you already modified your system partition, follow this step:
1. download and flash stock rom from here.You can keep your data if you want.
2. Follow this guide to root using magisk https://forum.xda-developers.com/mi-a1/how-to/root-mi-a1-oreo-8-0-disabling-ota-magisk-t3728654
Magisk will root your phone without modified /system partition.
Good luck
So if I well understood I have to follow the posted guide https://forum.xda-developers.com/mi-a1/how-to/root-mi-a1-oreo-8-0-disabling-ota-magisk-t3728654 each time I flash the rom...
kam1kazze said:
So if I well understood I have to follow the posted guide https://forum.xda-developers.com/mi-a1/how-to/root-mi-a1-oreo-8-0-disabling-ota-magisk-t3728654 each time I flash the rom...
Click to expand...
Click to collapse
Correct. But if you follow the guide, your OTA will work again, so you dont need to download and flash every update.
When you successfully follow the guide, make sure you disable automatic update in developer option. When update arrive, follow this step https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md
ltf_195 said:
Correct. But if you follow the guide, your OTA will work again, so you dont need to download and flash every update.
When you successfully follow the guide, make sure you disable automatic update in developer option. When update arrive, follow this step https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md
Click to expand...
Click to collapse
Don't work OTA beacause I have write the system partition...this was my question
kam1kazze said:
I have to install a Tasker plugin as system app: Nougat+ Tasker Tethering Control
Click to expand...
Click to collapse
In the description on the play store it says it only requires root, do you really need to install it as a system app?
If you really need to install it to the system partition, do it as a magisk module (as was said before). That way you don't need to touch your system partition and you can still do OTAs (if you follow the magisk ota guide)
hacker1 said:
In the description on the play store it only says it requires root, do you really need to install it as a system app?
If you really need to install it to the system partition, do it as a magisk module (as was said before). That way you don't need to touch your system partition and you can still do OTAs (if you follow the magisk ota guide)
Click to expand...
Click to collapse
It need the root permission to install the app in system partition...this allow tasker plugin to enable/disable wi-fi tethering. Since nougat, tasker cannot do this without this plugin
I don't know how to transform it to a magisk module.
Thanks for all information
ltf_195 said:
Two ways to update,
1. OTA
2. Miflash - which you have to download the rom. normally you have wait few days or week after OTA release.
No matter how you update, it will restore stock system. Thats mean you have to reinstall above apps everytime you update.
Click to expand...
Click to collapse
With two, do you lose data as long you don't check the clear data?
Related
Hello,
I just wanted to share how I have rooted my device today, and it was way easier than the methods I have been reading about so far.
My device: Xperia Z2 , C6543.
How I did it:
1- I updated my flashtool to the latest version, downloaded the 7.1.2.A.0.314 ftf for my region and flashed like instructed in the post. (Note that If you don't have flashtool installed, you have to go inside it's drivers folder and install the Z2 driver so it can communicate to the phone).
http://forum.xda-developers.com/showthread.php?t=2759934
2- After the downgrade to the 7.1.2.A.0.314 version mentioned above, I went to the flashtool menu (My 65XX -> Root -> Force towelroot)
When prompted to, I have choosen the SuperSU option.
Then the towelroot app showed in the phone's screen, I've tapped on "make it rain" and let it run.
After that the phone restarted and it was rooted.
3. Okay, now that the 7.1.2.A.0.314 is rooted, an OTA update notification showed up to update to the same version (lol). Well, I just let it update, and the root was there (I confirmed by restoring some data in titanium backup).
4. After that, another OTA update showed up to update to 23.0.1.A.0.167. Again, I let it download and install.
Well, that's what it took for me to root my z2 in it's latest version with only one downgrade and no manual adb commands, no manual rootkit downloads, pretty similar to the way I've always rooted my ZQ (R.I.P - it drowned lol).
The credits are due to the hard-working people who made all the mentioned tools, I am only doing my part by sharing an easier method than what i've seen around. Feel free to share your toughts.
Laters!
Sorry to be noob! Will it break anything like camera x reality or anything? And for warranty, can I claim it by just unrooting it(it's in the su) ?
Did not break anything for me. Now I can use foldermount and transfer heavy apps to the external sd. Wonderful. As for the warranty, since there is no recovery installed and no bootloader unlocked, it is as easy as doing the step 1 in the procedure described. It will flash the unrooted system back.
But ist same method, if u use this or this tool.
This post doesnt deserve an original development section!
thanks. I will follow this guide as i had root, upgraded and lost it. But i've have been itching to flash stuff lol.
But ist same method, if u use this or this tool.
Click to expand...
Click to collapse
I am not sure I understand what you mean, but if you are talking about the xperiarootkit compared to the "force towelroot" from flashtool, I checked the scripts in advance and they seem to be the same thing yes. The only shortcut to what I did was not having to flash recovery, and creating customized ftf, etc.
This post doesnt deserve an original development section!
Click to expand...
Click to collapse
I am sorry you feel that way man, that comment was a great way to add value to the conversation, thank you.
remydlc said:
thanks. I will follow this guide as i had root, upgraded and lost it. But i've have been itching to flash stuff lol.
Click to expand...
Click to collapse
Did you tried ota survival in Supersu?
rjshrjndrn said:
Did you tried ota survival in Supersu?
Click to expand...
Click to collapse
not before applying the OTA. Perhaps that would have helped. I have the app installed, but it says the binaries are not installed, to consult the forums for re-rooting
remydlc said:
not before applying the OTA. Perhaps that would have helped. I have the app installed, but it says the binaries are not installed, to consult the forums for re-rooting
Click to expand...
Click to collapse
I think you have to do all the stuff one again and root device. Then check the option for its root survival and do ota updates. I think you'll be fine with the updates.
Question, /System RW? (don't confuse it with a TA Restore, as it could only be restoring to the /Data partition).
Moscow Desire said:
Question, /System RW? (don't confuse it with a TA Restore, as it could only be restoring to the /Data partition).
Click to expand...
Click to collapse
I doubt you'll have system RW access as sony ric should still be running, but if root is working fine flashing nut's recovery should fix this easily.
root achieved and kept
Nice one thanks for the info worked well and updated to .167 ota and kept root.
Going to give this a try. Thanks
Thanks for the info, OP.
I used flashtool to downgrade my D6503 to .55, tried to use towelroot, no luck. used the CVE root exploit and got root, but after that update center failed the verification to .314.
Your method works, so cheers!
Will the Phone be wiped during this root method
ecolupo said:
Will the Phone be wiped during this root method
Click to expand...
Click to collapse
flashtool will wipe your phone unless you unselect data partition (not recommended). The rooting part is non-destructive so no that part won't your phone.
ptmaniac said:
I doubt you'll have system RW access as sony ric should still be running, but if root is working fine flashing nut's recovery should fix this easily.
Click to expand...
Click to collapse
Tried to install nut's recovery with supersu option but all the apks in the script could not be written into system folder. Also could not install xposed installer. May have to downgrade again and avoid this method
update: no need to downgrade again. sony_ric prevents r/w to system folder even with root, so I just used ric killer by forty two: http://forum.xda-developers.com/xperia-z2/general/4-4-4-sony-ric-killer-t2953141
afterward I was able to install xposed installer via normal method.
Thank you for the tutorial. It worked fine for me.
What will happen if I do a factory reset via settings-menu? Will root be gone? Do I have to downgrade again or can I install SuperSU to get root back?
Sent from my D6503 using XDA Free mobile app
How to get back to stock rom with root n able to get OTA updates from google
Flash the Factory Image after Systemless SuperSU. You can't use xposed and some kernel because they modifi the system partition.
This thread will help you
http://forum.xda-developers.com/nexus-6p/themes-apps/systemless-root-themed-apps-t3292105
nickhil90490 said:
How to get back to stock rom with root n able to get OTA updates from google
Click to expand...
Click to collapse
It isn't very clear what you're actually asking here. Are you saying you have root now and you want to go back to stock without root? If so just flash the factory images. Or are you saying you want to have the stock ROM with root but still be able to take OTA updates? If so, you can't do that, in order to take an OTA you must have no modifications.
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
If you don't want to remove root/su/Xposed permanently, it makes no sense to use OTA-updates. Just follow step 10 of the guide by Heisenberg and re-flash SuperSu (systemless) and Xposed afterwards. Preparing the device for OTA is possible, but doesn't save you time.
@Heisenberg: Maybe you could include re-flashing of SuperSu (systemless) and Xposed in your guide as optional steps. It is mentioned at the end in one sentence, but it's so common that it deserves a real inclusion in the guide in my opinion.
gnadenlos said:
If you don't want to remove root/su/Xposed permanently, it makes no sense to use OTA-updates. Just follow step 10 of the guide by Heisenberg and re-flash SuperSu (systemless) and Xposed afterwards. Preparing the device for OTA is possible, but doesn't save you time.
@Heisenberg: Maybe you could include re-flashing of SuperSu (systemless) and Xposed in your guide as optional steps. It is mentioned at the end in one sentence, but it's so common that it deserves a real inclusion in the guide in my opinion.
Click to expand...
Click to collapse
Yeah that's probably not a bad idea, I'll add that tomorrow.
Recently I rooted my G5 plus and it worked really well for me. I didn't use SuperSU, instead, have Magisk installed. Unfortunately, now my phone isn't updating. What should I do to unroot it without much problem and without losing any data on my phone? And will it update if I unroot it?
It's a little more complicated than that... to bad there isn't a guide to doing it here somewhere... Hmmm....
https://forum.xda-developers.com/g5-plus/how-to/guide-complex-ota-update-magisk-rooted-t3688175
acejavelin said:
It's a little more complicated than that... to bad there isn't a guide to doing it here somewhere... Hmmm....
https://forum.xda-developers.com/g5-plus/how-to/guide-complex-ota-update-magisk-rooted-t3688175
Click to expand...
Click to collapse
So like can't I simply unroot my phone and install the updates? Isn't there any easy way of uprooting?
dt.dragonborn said:
So like can't I simply unroot my phone and install the updates? Isn't there any easy way of uprooting?
Click to expand...
Click to collapse
Root is only part of the problem, TWRP is another big one.
OTA updates can only be installed on a purely stock device, the install script will check multiple things to verify the device is unmodified and in the correct state before applying, then it applies changes to specific files or partitions, they must be at a known starting condition before changes can be applied.
So, can you simply "unroot and install updates"? No, you must undo all changes to the device that are system related... Return the recovery, boot, and system partitions to their original state or any update will fail. Unrooting does not undo any changes, adds, or deletions you performed with root access, those actions are permanent.
Isn't there an easy way of unrooting? Sure, Magisk and SuperSU both have methods of removal, but that doesn't gain you what is needed to apply an OTA update.
I provided a link previously, that is what you need to do.
dt.dragonborn said:
Recently I rooted my G5 plus and it worked really well for me. I didn't use SuperSU, instead, have Magisk installed. Unfortunately, now my phone isn't updating. What should I do to unroot it without much problem and without losing any data on my phone? And will it update if I unroot it?
Click to expand...
Click to collapse
Which OTA(s) isn't installing?
Sent from my Moto G Plus (5th Gen) using XDA Labs
cdysthe said:
Which OTA(s) isn't installing?
Click to expand...
Click to collapse
I am not much of a tech guy but the update says
New Version-NPN25.1 37-67
Improved audio in Video Capture
Data traffic improvements
acejavelin said:
Root is only part of the problem, TWRP is another big one.
OTA updates can only be installed on a purely stock device, the install script will check multiple things to verify the device is unmodified and in the correct state before applying, then it applies changes to specific files or partitions, they must be at a known starting condition before changes can be applied.
So, can you simply "unroot and install updates"? No, you must undo all changes to the device that are system related... Return the recovery, boot, and system partitions to their original state or any update will fail. Unrooting does not undo any changes, adds, or deletions you performed with root access, those actions are permanent.
Isn't there an easy way of unrooting? Sure, Magisk and SuperSU both have methods of removal, but that doesn't gain you what is needed to apply an OTA update.
I provided a link previously, that is what you need to do.
Click to expand...
Click to collapse
Thank you for this. I unlocked the bootloader, and installed TWRP and Magisk to gain root. This worked fine. However, I decided I wanted to go back to complete stock yesterday. So I uninstalled Magisk and flashed stock firmware using ADB. My phone is now unrooted, has a locked bootloader, and is running stock firmware which is what I wanted. Once I get the phone to boot, almost everything functions normally. However, it seems as though I now do not have any recovery whatsoever (and I assume that's because I did not specifically replace TWRP with stock recovery). So when I boot my phone, it goes to the bootloader and stops. If I then hit "start" on the bootloader, the ROM loads up normally after that. f that were the only issue, I could live with it. But not being able to get to recovery is concerning. And I am not able to get OTAs at the moment.
So, I'll check the other thread you mentioned. I assume I will need to flash stock recovery in order to get where I need to be.
Thank you for the post!
Hi, just got around to rooting my Kindle. Currently using SuperSu, curious if anyone has used Magisk with this tablet? Any reason not to do so?.
Thanks in advance.
I've debated doing this as well, as I don't like having to default grant everything root access.
As far as I understand though, none of your root apps/su requests can modify the system partition, so I haven't tried it yet.
@diplomatic is this true for the bootless root method without dm-verity?
No, you can modify /system if there's no dm-verity, @Kctucka
diplomatic said:
No, you can modify /system if there's no dm-verity, @Kctucka
Click to expand...
Click to collapse
Oh wow that's pretty awesome.
Sounds like there's no downside to Magisk on the 2017 HD 8 then.
Kctucka said:
Oh wow that's pretty awesome.
Sounds like there's no downside to Magisk on the 2017 HD 8 then.
Click to expand...
Click to collapse
Thanks, guys!
SuperSU access workaround
Kctucka said:
I've debated doing this as well, as I don't like having to default grant everything root access.
.....
Click to expand...
Click to collapse
There is a SuperSU access workaround without having to default grant everything root access:
https://forum.xda-developers.com/hd8-hd10/general/supersu-access-workaround-fire-devices-t3738269
Maybe I am mistaken, but how does one install Magisk on 2017 HD8 without TWRP ?
Dan_firehd said:
There is a SuperSU access workaround without having to default grant everything root access:
https://forum.xda-developers.com/hd8-hd10/general/supersu-access-workaround-fire-devices-t3738269
Maybe I am mistaken, but how does one install Magisk on 2017 HD8 without TWRP ?
Click to expand...
Click to collapse
Yeah I've seen that method, but didn't wanna redo it for every root app I add.
And this is the Bootless Root Magisk method:
https://forum.xda-developers.com/showpost.php?p=79626434&postcount=135
I think I'm gonna try this method when I get some free time.
Kctucka said:
Yeah I've seen that method, but didn't wanna redo it for every root app I add.
And this is the Bootless Root Magisk method:
https://forum.xda-developers.com/showpost.php?p=79626434&postcount=135
I think I'm gonna try this method when I get some free time.
Click to expand...
Click to collapse
@Kctucka would you let me know if that method works for you? I tried grabbing the stock boot image and modifying it with the latest version of Magisk, Could not get that to work either via ADB or Flashify because of the locked bootloader - stupid of me not to realize that from the start. I let my excitement get the best of me.
I am out of time today, but it seems like a modified BIN file might be an option.
koop1955 said:
@Kctucka would you let me know if that method works for you? I tried grabbing the stock boot image and modifying it with the latest version of Magisk, Could not get that to work either via ADB or Flashify because of the locked bootloader - stupid of me not to realize that from the start. I let my excitement get the best of me.
I am out of time today, but it seems like a modified BIN file might be an option.
Click to expand...
Click to collapse
Yeah will do! I'll probably try it tomorrow or the day after.
koop1955 said:
@Kctucka would you let me know if that method works for you? I tried grabbing the stock boot image and modifying it with the latest version of Magisk, Could not get that to work either via ADB or Flashify because of the locked bootloader - stupid of me not to realize that from the start. I let my excitement get the best of me.
I am out of time today, but it seems like a modified BIN file might be an option.
Click to expand...
Click to collapse
Ok so I successfully have Magisk working, and have been playing around with it for a bit now. I am running the latest version of Magisk Manager. To get it up and running, I chose the option in SuperSu to clean up binaries for different su method.
So far, all of my root apps detect root, except for titanium backup. I've messed around with it for a bit but haven't been able to figure it out. I'm guessing it has something to do with the location of the su binaries.
Also of note, FlashFire did not work at first. I realized that this is because the timebomb method we used along with the older app version, was from before Magisk existed. I grabbed the latest version of FlashFire from apk mirror, and it started without issues. I haven't tested by flashing anything yet though.
Lastly, the one minor inconvenience is that my kernel tweaks I enable at boot, do not work, as there is no root at boot. So I have to manually add zram every reboot. Perhaps there's a better way to do this.
All in all, this is a pretty solid root method, but obviously non ideal due to the locked bootloader.
I've also not tested how easy it is to switch back to SuperSu if desired, but I assume it's as simple as disabling the start up script, and updating su binaries in SuperSu.
@diplomatic is this the case? Or would you also need to delete the created files in the data partition? Thanks again for the awesome method!
Kctucka said:
Ok so I successfully have Magisk working, and have been playing around with it for a bit now. I am running the latest version of Magisk Manager. To get it up and running, I chose the option in SuperSu to clean up binaries for different su method.
Click to expand...
Click to collapse
Was that all that you did? That option and then install? And how did you change the time in your Kindle to get Flashify to work or just the latest APK?
And thanks for everything! Getting back into this after so long I feel like a n00b again.
koop1955 said:
Was that all that you did? That option and then install? And how did you change the time in your Kindle to get Flashify to work or just the latest APK?
And thanks for everything! Getting back into thhis after so long I feel like a n00b again.
Click to expand...
Click to collapse
That option was all I did to remove SuperSu. Then I followed the instructions here:
https://forum.xda-developers.com/showpost.php?p=79626434&postcount=135
Didn't take long to get it working.
And the time change was to get the version of FlashFire working that was compatible with the version of SuperSu we could run. See this post for more info if you're curious:
https://forum.xda-developers.com/hd8-hd10/general/hd-10-2017-xposed-t3722252
But with this new method, the most recent version of FlashFire works, as it's compatible with Magisk. The older version of FlashFire I had is not.
Also, I'm a noob myself. That's why I tagged diplomatic again, to correct the dumb things I might have said
Well, I am busy adding to your "Thanks" quotient, something seems to have fallen by the wayside today. Glad t have you around.
I think ultimately we are going to end up with a custom BIN file with Magisk and Xposed integrated.
Cheers.
koop1955 said:
Well, I am busy adding to your "Thanks" quotient, something seems to have fallen by the wayside today. Glad t have you around.
I think ultimately we are going to end up with a custom BIN file with Magisk and Xposed integrated.
Cheers.
Click to expand...
Click to collapse
That's awesome! Would that pass signature verification? Or would it be through hacked fastboot?
Also, that'd make it much easier to set up the device after a softbrick. FlashFire would be good to flash backups right away.
Kctucka said:
.....
Lastly, the one minor inconvenience is that my kernel tweaks I enable at boot, do not work, as there is no root at boot. So I have to manually add zram every reboot. Perhaps there's a better way to do this.
.....
Click to expand...
Click to collapse
Would you please let us know how did you do your "kernel tweaks" to add zram for a rooted 2017 HD8?
Thanks.
Dan_firehd said:
Would you please let us know how did you do your "kernel tweaks" to add zram for a rooted 2017 HD8?
Thanks.
Click to expand...
Click to collapse
My kernel tweaks were done with KA Mod Reborn, using the "apply on boot" setting:
https://forum.xda-developers.com/android/apps-games/approot4-0-ka-mod-reborn-v18-t3714105
I added 260 MB ZRAM with a swapiness of 10. You can also tweak low memory killer, laptop mode, and a whole bunch of other dials that I don't mess with as I don't fully understand what they do.
Kernel changes could also be done with a number of different apps that do similar things.
Unfortunately, the bootless root method doesn't give root on boot, so it and also most Magisk modules won't work. Can't think of a workaround currently.
Kctucka said:
I've also not tested how easy it is to switch back to SuperSu if desired, but I assume it's as simple as disabling the start up script, and updating su binaries in SuperSu.
@diplomatic is this the case? Or would you also need to delete the created files in the data partition? Thanks again for the awesome method!
Click to expand...
Click to collapse
Yeah, pretty much. The activation of root depends only the init.d app running the script. The su binaries don't really exist in storage. You can delete all the stuff under /data/adb if you want to wipe everything Magisk. In theory, it should be possible to install Magisk on the system partition. It probably doesn't support that method officially anymore. But if the bootless method works, then a similar script can be added to /system....
diplomatic said:
Yeah, pretty much. The activation of root depends only the init.d app running the script. The su binaries don't really exist in storage. You can delete all the stuff under /data/adb if you want to wipe everything Magisk. In theory, it should be possible to install Magisk on the system partition. It probably doesn't support that method officially anymore. But if the bootless method works, then a similar script can be added to /system....
Click to expand...
Click to collapse
That's super beneficial then, you can swap back and forth easily depending on what you need.
diplomatic said:
Yeah, pretty much. The activation of root depends only the init.d app running the script. The su binaries don't really exist in storage. You can delete all the stuff under /data/adb if you want to wipe everything Magisk. In theory, it should be possible to install Magisk on the system partition. It probably doesn't support that method officially anymore. But if the bootless method works, then a similar script can be added to /system....
Click to expand...
Click to collapse
How about just swapping the install-recovery.sh script for suboot.sh on devices that don't have dm-verity?
I think that's pretty much what SuperSU does as well.
That would give root much earlier during boot and not depend on the extra App.
Probably doesn't even need to run mtk-su each boot then either.
Yeah, that's on the right track, @k4y0z. What you can probably use is a modified SU_MINISCRIPT section of suboot.sh, at least as a starting point. That is the code that needs to be run as root. What should be changed is the path to the magiskinit & magisk binaries. Those could be placed somewhere on /system. You would only need mtk-su if selinux needs to be permissive. But I suspect it does for the 'magiskpolicy --live' call. (But then how does SuperSU handle it with enforcing?)
Just received the stable Nothing OS 1.5 based on Android 13. Finally the wait is over. Check for updates.
What country are you in and what build where you on when you got the update?
bariz143 said:
What country are you in and what build where you on when you got the update?
Click to expand...
Click to collapse
I am using an Indian unit and was using 1.5 beta
Nice. Think its a slow rollout then. Im in Europe/Sweden and no update here yet. Im on Beta 2
bariz143 said:
Nice. Think its a slow rollout then. Im in Europe/Sweden and no update here yet. Im on Beta 2
Click to expand...
Click to collapse
You'll get it by the end of the week.
bariz143 said:
Nice. Think its a slow rollout then. Im in Europe/Sweden and no update here yet. Im on Beta 2
Click to expand...
Click to collapse
Nothing stable version 1.5.2 arrived via OTA right now in Czech Republic EU.
I was an official beta tester!
bariz143 said:
Nice. Think its a slow rollout then. Im in Europe/Sweden and no update here yet. Im on Beta 2
Click to expand...
Click to collapse
Got it overnight, Croatia
Is updating with root quite simple? Do I just need to restore the boot, apply the OTA, boot with the new magisk_boot, and if successful, install root permanently via magisk?
I haven't been able to find a guide, and the information is scattered, which makes me a bit unsure. Some questions come to mind: If something modifies the system, do I need to reflash it before the update? How can I find out if it's modified? Does installing Revanced YouTube as root modify the system? Do I need to uninstall any Magisk modules?
To be safe, should I only update when the ROM is available? Alternatively, I can sideload the update via recovery or put it in an OTA folder and run the updater?
What steps if anything goes wrong?
Maybe someone has the energy to write a short guide, which would be greatly appreciated by me and maybe others too.
dedors said:
Is updating with root quite simple? Do I just need to restore the boot, apply the OTA, boot with the new magisk_boot, and if successful, install root permanently via magisk?
I haven't been able to find a guide, and the information is scattered, which makes me a bit unsure. Some questions come to mind: If something modifies the system, do I need to reflash it before the update? How can I find out if it's modified? Does installing Revanced YouTube as root modify the system? Do I need to uninstall any Magisk modules?
To be safe, should I only update when the ROM is available? Alternatively, I can sideload the update via recovery or put it in an OTA folder and run the updater?
What steps if anything goes wrong?
Maybe someone has the energy to write a short guide, which would be greatly appreciated by me and maybe others too.
Click to expand...
Click to collapse
Open magisk, select uninstall and then restore stock images, DO NOT REBOOT, perform the OTA update, after it finishes DO NOT REBOOT, open magisk, select install, select install in the inactive slot.
After it finishes reboot when magisk ask you to.
You can only apply ota updates if system and vendor partitions are not modified.
You have to restore them if you have modified them or deselect the magisk modules that modify them.
Revanced yt is systemless, like busybox, universal safetynet fix and (obv) systemless host.
If a module modifies system it should be noted on the official repo or xda page.
After the update you can re activate all the modules that modify system and vendor.
Update when you feel it, sometimes it's good to wait, sometimes it's pointless.
If you don't have the ota update message you can update with the zip file.
You still have restore stock images, then either install the ota via dialer (which worked for me) or sideload recovery (which didn't).
After it finishes installing, reboot into fastboot and boot the modified boot.img
Open magisk and direct install it.
Depending on WHERE the operation goes wrong you could need just to boot the modified 1.1.8 boot img again to return in the previous context, maybe you could need to flash the full zip because of a soft brick or in the most extreme cases EDL mode with the guide here in xda.