[Resolved] Magisk 11.1 getting ErrorCode : 1 - General Questions and Answers

So I've been trying to unroot my OP3 and it seems to unroot it self just fine, but once I want to install the Magisk zip it gives me "Updater Process Ended with error: 1" and I have no clue why because the root from SuperSU is gone I checked I couldn't access rooted apps anymore, so I tried to flash the Magisk 11.1.zip and I got the Updater Process Ended with error: 1 message.
I had rooted with SR1-SuperSU-v2.79
The thing is when I try to root with SuperSU again and then when I flash the Magisk zip it flashes just fine, but once I open the Magisk Manager part and go to Settings->Magisk Hide - I get the notification that I'm not using MagiskSU and it tells me that I'm not rooted with MagiskSU.
Anyone who can help me get it rooted the right way with Magisk?
EDIT:
The issue has been resolved, what I did was once I hit Unroot in SuperSU in the Settings you need to click Yes when it asks to flash stock recovery for OTAs.
After this I could flash Magisk and now I pass the Safetynet Check.

Zer0w said:
So I've been trying to unroot my OP3 and it seems to unroot it self just fine, but once I want to install the Magisk zip it gives me "Updater Process Ended with error: 1" and I have no clue why because the root from SuperSU is gone I checked I couldn't access rooted apps anymore, so I tried to flash the Magisk 11.1.zip and I got the Updater Process Ended with error: 1 message.
I had rooted with SR1-SuperSU-v2.79
The thing is when I try to root with SuperSU again and then when I flash the Magisk zip it flashes just fine, but once I open the Magisk Manager part and go to Settings->Magisk Hide - I get the notification that I'm not using MagiskSU and it tells me that I'm not rooted with MagiskSU.
Anyone who can help me get it rooted the right way with Magisk?
EDIT:
The issue has been resolved, what I did was once I hit Unroot in SuperSU in the Settings you need to click Yes when it asks to flash stock recovery for OTAs.
After this I could flash Magisk and now I pass the Safetynet Check.
Click to expand...
Click to collapse
can you elloborate i am facing same issue

Rush94 said:
can you elloborate i am facing same issue
Click to expand...
Click to collapse
I did say how I resolved it, it's just that when you Unroot you let the stock recovery flash itself back. After that to be sure that your device still works let the device boot itself to the homescreen and check if SuperSU is gone, after that go back to TWRP and flash Magisk.

Zer0w said:
I did say how I resolved it, it's just that when you Unroot you let the stock recovery flash itself back. After that to be sure that your device still works let the device boot itself to the homescreen and check if SuperSU is gone, after that go back to TWRP and flash Magisk.
Click to expand...
Click to collapse
Gotcha thanks

Related

On H83010i, bootloader unlocked not rooted. Want H83020f rooted

I have successfully unlocked the bootloader my H83010i version.
I started down the path to root my device using H83010d tot file but stopped because I didn't know if when I upgrade to android 7.0 versions if I would lose root?
Therefore what is the easiest way to get to H83020f rooted?
How do I go from H83010i to H83020f and be rooted?
I have rooted a lot of samsung galaxy phones but this is my first LG so I am struggling a bit to understand how to upgrade. I assume if I do an OTA update it will install the latest version? I checked for system updates and it just said there is an update and to start downloading it but I don't know which update version that is?
Please advise.
Thanks in advance.
buyslake said:
I have successfully unlocked the bootloader my H83010i version.
I started down the path to root my device using H83010d tot file but stopped because I didn't know if when I upgrade to android 7.0 versions if I would lose root?
Therefore what is the easiest way to get to H83020f rooted?
How do I go from H83010i to H83020f and be rooted?
I have rooted a lot of samsung galaxy phones but this is my first LG so I am struggling a bit to understand how to upgrade. I assume if I do an OTA update it will install the latest version? I checked for system updates and it just said there is an update and to start downloading it but I don't know which update version that is?
Please advise.
Thanks in advance.
Click to expand...
Click to collapse
First of all, no need to use 10D tot file anymore. Download and install 20A kdz front autoprime located here:
https://forum.xda-developers.com/tmobile-lg-g5/development/stock-h830-20a-rom-flashable-zips-imgs-t3511294
Once that's installed, set up your system and then follow the following guide to get TWRP an root:
https://forum.xda-developers.com/tmobile-lg-g5/development/root-h830-running-30a-nougat-t3524322
After you have TWRP and root download the flashable 20F zip and install from TWRP (make sure to delete recovery from boot.p file after installing and also flash root). Here's the link to 20F:
https://forum.xda-developers.com/tmobile-lg-g5/development/stock-h830-20f-rom-flashable-zips-imgs-t3592855
If you follow all of that, you will be on stock 20F, rooted and with TWRP. After that, I recommend checking out the following custom kernel and installing that and using magisk instead of SuperSU. Kernel located here:
https://forum.xda-developers.com/tmobile-lg-g5/development/jan-17-2017-20c-deodexed-kernels-t3539611
Hopefully that helps, if you need more help just ask.
Thanks so much for taking the time to write me this great information. I have a question about the (make sure to delete recovery from boot.p file after installing and also flash root). ???????? Is this explained clearly somewhere? I don't know what I should do.
buyslake said:
Thanks so much for taking the time to write me this great information. I have a question about the (make sure to delete recovery from boot.p file after installing and also flash root). ???????? Is this explained clearly somewhere? I don't know what I should do.
Click to expand...
Click to collapse
After flashing the 20F version from TWRP, it creates a recovery from boot.p file in the system directory. If you don't delete this file before rebooting, you will lose TWRP. So, after doing the recowvery method to get root and TWRP and then after you flash the 20F from TWRP, after it's done flashing go to main menu of TWRP, click on mount, check system, go back to main menu, click advanced, click file manager and go-to system directory and click on the recovery from boot.p file and then delete. Now you can reboot without losing TWRP. Then you can flash SuperSU or magisk for root
Your Device software cannot be checked for corruption. Lock the bootloader
Thanks for the fast responses. After many hours of studying the posts and I finally got my LG G5 running on H830_20F_DeOdexed rom withh Asgard version 4.5 kernal and rooted with SuperSU v2.74.
However I keep getting the "your device software cannot be checked for corruption. lock the bootloader message upon starting up. see attachment
Does everyone get that message? Or is there a way to remove it?
I thought the Asgard kernal said it got rid of that?
buyslake said:
Thanks for the fast responses. After many hours of studying the posts and I finally got my LG G5 running on H830_20F_DeOdexed rom withh Asgard version 4.5 kernal and rooted with SuperSU v2.74.
However I keep getting the "your device software cannot be checked for corruption. lock the bootloader message upon starting up. see attachment
Does everyone get that message? Or is there a way to remove it?
I thought the Asgard kernal said it got rid of that?
Click to expand...
Click to collapse
You'll always have that message, no current way around it. Asgard kennel will allow you to pass safety net if you use magisk instead of SuperSU for root as it hides that the bootloader is unlocked from the system.
Where is Magisk?
jeffsga88 said:
You'll always have that message, no current way around it. Asgard kennel will allow you to pass safety net if you use magisk instead of SuperSU for root as it hides that the bootloader is unlocked from the system.
Click to expand...
Click to collapse
Are you saying that boot up message will not be there if I switch to Magisk?
I tried to find magisk but I was unable to locate the install file and instructions on how to change from SuperSU to magisk. Do you know the link to it?
buyslake said:
Are you saying that boot up message will not be there if I switch to Magisk?
I tried to find magisk but I was unable to locate the install file and instructions on how to change from SuperSU to magisk. Do you know the link to it?
Click to expand...
Click to collapse
No. I said currently there is no way to get rid of that message unless you lock the bootloader and you can't do that after modifying the system (i.e. installing TWRP and root). I said magisk will allow you to pass safety net. All that does is allow you to use apps that won't work with root / unlocked bootloader. If you don't use apps like Android pay or other apps that don't work when rooted, it really isn't necessary to switch from SuperSU to magisk. Anyways, if you're interested in magisk use Google (or XDA search) and search magisk XDA.

Magisk

Hello guys i successfully unlocked Bootloader now i want to root my Nokia 3 via magisk i don't want twrp i just want boot img for magisk but for that i need root i try many apps for rooting but unsuccessfull i want to root then get boot img then unroot then root from magisk please help me.
mudit johari said:
Hello guys i successfully unlocked Bootloader now i want to root my Nokia 3 via magisk i don't want twrp i just want boot img for magisk but for that i need root i try many apps for rooting but unsuccessfull i want to root then get boot img then unroot then root from magisk please help me.
Click to expand...
Click to collapse
You can boot twrp without flashing and then flash root
https://forum.xda-developers.com/no...w-to-unlock-bootloader-nokia-3-t3699344/page2
Check post #15 by @SkaboXD
But when i flash twrp recovery then i go to recovery and ask for password i cancel it then ask for system modifications I'm confused so i dont give permission to twrp for system modifications then i flash magisk zip then wipe cache of dalvik cache and reboot then its stuck in bootloop
mudit johari said:
But when i flash twrp recovery then i go to recovery and ask for password i cancel it then ask for system modifications I'm confused so i dont give permission to twrp for system modifications then i flash magisk zip then wipe cache of dalvik cache and reboot then its stuck in bootloop
Click to expand...
Click to collapse
You said you wanted root, you were supposed to use the process to get root not flash magisk. I thought you had a method of installing magisk after getting root. I thought you were going to boot twrp recovery, not flash it, since you said you didn't want twrp.
Unfortunately you're going to have to flash stock with OST.
Check this link for more information:
https://forum.xda-developers.com/nokia-3/development/nokia-3-official-firmware-india-uae-t3674320
yeah now i got twrp but only come when boot from fastboot commands and i want magisk how can i get it?
did i have to first flash supersu zip from twrp then install magsik? but i want only magisk not supersu
mudit johari said:
did i have to first flash supersu zip from twrp then install magsik? but i want only magisk not supersu
Click to expand...
Click to collapse
I have never actually used magisk. I thought you had a way of installing/flashing magisk once you had root
I try installing magisk by flashing magisk zip from twrp but got bootloop
mudit johari said:
I try installing magisk by flashing magisk zip from twrp but got bootloop
Click to expand...
Click to collapse
Might I ask: what do you need magisk for?
Also in that recovery I got errors like can't Mount and some kind of encryption error and it say's I have to format data
Need magisk for root and modules as also I want all updates properly installed means i want to in stock recovery
mudit johari said:
Also in that recovery I got errors like can't Mount and some kind of encryption error and it say's I have to format data
Click to expand...
Click to collapse
In my opinion, only use the recovery for flashing stuff, don't mount anything other than sdcard, don't unlock. Maybe when there is a more compatible version of twrp ...
---------- Post added at 02:00 PM ---------- Previous post was at 01:17 PM ----------
mudit johari said:
Need magisk for root and modules as also I want all updates properly installed means i want to in stock recovery
Click to expand...
Click to collapse
Well i don't know about the modules, but when I flashed stock firmware with OST (first time I flashed recovery my phone was stuck in twrp) then flashed root and xposed, I was still able to install updates. The stock firmware I installed was 7.0, but now i'm on the most recent update. So unless there are some specific modules that you need from magisk, I think you can stick with the regular root.
On the other hand you can continue to experiment with magisk, maybe you will find something that we don't know yet and get it working. But remember, if you want to flash anything, don't format with twrp at all, just leave everything readonly and flash
I'm not able to go to recovery by buttons. Only by fastboot command why is that?
What the hell is this i just try to go to recovery by buttons it works but I'm on stock recovery but i flashed twrp then i format data did formatting data did something to recovery? Or is it that i have to use fastboot command to go to twrp recovery? Where the hell is that recovery?
mudit johari said:
What the hell is this i just try to go to recovery by buttons it works but I'm on stock recovery but i flashed twrp then i format data did formatting data did something to recovery? Or is it that i have to use fastboot command to go to twrp recovery? Where the hell is that recovery?
Click to expand...
Click to collapse
I don't know; the process of flashing recovery on HMD's nokias isn't yet fully developed, people have complained about flashing recovery but still not booting into it. Personally I would recommend that you use stock recovery and use fastboot to boot into twrp instead of actually flashing twrp whenever you want to flash anything. That way you are still able to install system update
But for installing magisk every where written that flash magisk zip from twrp but i got bootloop
mudit johari said:
But for installing magisk every where written that flash magisk zip from twrp but i got bootloop
Click to expand...
Click to collapse
Have you flashed stock firmware with OST? Can you boot normally now? If not, do that, then update ti the current android version using OTA. After that boot into twrp (whether you chose to flash twrp or just boot twrp is up to you). Do a backup then try flashing magisk again, maybe it will work this time
Yeah i already flashed stock rom with ost and already update to latest version i think magisk is not supported in Nokia 3
mudit johari said:
Hello guys i successfully unlocked Bootloader now i want to root my Nokia 3 via magisk i don't want twrp i just want boot img for magisk but for that i need root i try many apps for rooting but unsuccessfull i want to root then get boot img then unroot then root from magisk please help me.
Click to expand...
Click to collapse
Hello mate, you can't root nokia 3 with Magisk. Why? Because noone never send boot img to dev! So only option to root it is Chainfire SuperUser 2.79v.
Ok brother but i have a question if i root and then remove some system apps then can I safely install updates?

update to 9.5.9 bootloop, only fix was twrp bootloop fix but removed root

As the title says I updated to 9.5.9 and I installed magisk to ota slot and then I got a bootloop.... I fixed it by using twrp option to fix bootloop but that removed root, everything I do now sends it into a bootloop, please tell me there is a way to reroot this without wiping my data
https://forum.xda-developers.com/on...-to-uninstall-magisk-module-t3940369#poststop
Just had the same issue an hour ago. Do this then re-root your phone again. Easy. Then re-install magisk modules.
spart0n said:
As the title says I updated to 9.5.9 and I installed magisk to ota slot and then I got a bootloop.... I fixed it by using twrp option to fix bootloop but that removed root, everything I do now sends it into a bootloop, please tell me there is a way to reroot this without wiping my data
Click to expand...
Click to collapse
Had the same issue.
Same here. I just reflashed TWRP (flash boot command), flashed the TWRP installer zip, rebooted recovery and then flashed Magisk. That solved it.
By the way, theres a new TWRP out for the 7 Pro.
I got the same problem but my internal storage is encrypted (it shows 0kb). TWRP is not asking for PIN to unencrypt the partition. What can I do now?
Do we have a custom boot image for 9.5.9? I'm looking to root and want to find the best method which will continue to allow future updates (even if I need to flash manually)
dude9946 said:
Do we have a custom boot image for 9.5.9? I'm looking to root and want to find the best method which will continue to allow future updates (even if I need to flash manually)
Click to expand...
Click to collapse
Your best bet is to use the oxygen updater app, download 9.5.9 and then copy it to a PC then use boot.img extract thingy and then use magisk to patch it and then use fastboot to to root it

can't root S7 (SM-G930F) in system mode.

Hello XDA !
This is my first post..sorry for my bad english.
I bought a S7 (SM-G930F) Android 8.0 and i rooted it then i noticed that was just systemless root.. and it's totally useless for me because i want to uninstall system apps and change build.prop..
so I flashed the stock rom and reflashed TWRP, then I executed a command to force SuperSU to install in system
(echo SYSTEMLESS=false>>/data/.SuperSU)
and I installed SuperSU.zip..but it stucks on bootloop.. I tried many different SuperSU.zip versions even a modified version for system mode root, but nothing works..
by the way I installed no-verity-opt-encrypt-6.1.zip before installing SuperSU.zip !
ysnelazzab said:
Hello XDA !
This is my first post..sorry for my bad english.
I bought a S7 (SM-G930F) Android 8.0 and i rooted it then i noticed that was just systemless root.. and it's totally useless for me because i want to uninstall system apps and change build.prop..
so I flashed the stock rom and reflashed TWRP, then I executed a command to force SuperSU to install in system
(echo SYSTEMLESS=false>>/data/.SuperSU)
and I installed SuperSU.zip..but it stucks on bootloop.. I tried many different SuperSU.zip versions even a modified version for system mode root, but nothing works..
by the way I installed no-verity-opt-encrypt-6.1.zip before installing SuperSU.zip !
Click to expand...
Click to collapse
i havent rooted an S7 in a while, but dont you just flash twrp in Odin with the reboot box unchecked and once the flash completes, reboot into twrp which will present you a slider that says something along the lines of "slide to allower SU access" or something like that. Once youve done that, then you flash magisk in TWRP, boot, install busybox, and you should then be asked if you want to grant SU access to busybox, if it does that, youre all set
youdoofus said:
i havent rooted an S7 in a while, but dont you just flash twrp in Odin with the reboot box unchecked and once the flash completes, reboot into twrp which will present you a slider that says something along the lines of "slide to allower SU access" or something like that. Once youve done that, then you flash magisk in TWRP, boot, install busybox, and you should then be asked if you want to grant SU access to busybox, if it does that, youre all set
Click to expand...
Click to collapse
Thank you so much for your response !
I did everything in the correct way, i flashed twrp with reboot option disabled.. and i formated data then reboot to recovery and I installed no verity and after that i installed SuperSU and it's done successfully but it ended up with a bootloop..
also I tried to install a system mode supersu.zip and it freezes TWRP and stuck on "installing"
I think literally I can't do the system root.. so i did systemless root.
ysnelazzab said:
Thank you so much for your response !
I did everything in the correct way, i flashed twrp with reboot option disabled.. and i formated data then reboot to recovery and I installed no verity and after that i installed SuperSU and it's done successfully but it ended up with a bootloop..
also I tried to install a system mode supersu.zip and it freezes TWRP and stuck on "installing"
I think literally I can't do the system root.. so i did systemless root.
Click to expand...
Click to collapse
the F models should allow for system root, not sure tho as i didnt spend much time with my S7 and S7 Edge. Still have em tho. If i remember, i could dink with them tonight
youdoofus said:
the F models should allow for system root, not sure tho as i didnt spend much time with my S7 and S7 Edge. Still have em tho. If i remember, i could dink with them tonight
Click to expand...
Click to collapse
mine is G930F oreo 8.0 i tried everything to do system root but failed.. one thing I didn't do is a custom rom. i prefer a rooted stock rom.
ysnelazzab said:
mine is G930F oreo 8.0 i tried everything to do system root but failed.. one thing I didn't do is a custom rom. i prefer a rooted stock rom.
Click to expand...
Click to collapse
well, you cant do a custom ROM without a custom recovery. bootloader is unlocked i assume
youdoofus said:
well, you cant do a custom ROM without a custom recovery. bootloader is unlocked i assume
Click to expand...
Click to collapse
as I said i have TWRP which is a custom recovery. and i don't want custom ROM i just want my stock ROM system rooted not systemless.
ysnelazzab said:
as I said i have TWRP which is a custom recovery. and i don't want custom ROM i just want my stock ROM system rooted not systemless.
Click to expand...
Click to collapse
im well aware that TWRP is a custom recovery, i remember when it first launched and people were converting from CWM to TWRP. Anyways, if youve successfully installed twrp, try factory resetting the device and then booting. You should only need to flash magisk in TWRP and busy box in the OS once booted

[SOLVED] OTA with ROOT...

I ask before in "guide to root motorla g stylus":
really is no way to work OTA while Magisk installed? i mean some Magisk Hide Props Config, or not install TWRP or anything? i actualy have Nokia 7 Plus (unlocked via unoficial method) and last year while not installed TWRP is possible check system update, install over air (while Magisk is installed), before reboot run MagiskManager, install Magisk to other slot, reboot, started from updated slot with Magisk installed, without need flash stock boot img before ota and flash manualy patched boot img after OTA... sure have Moto G Pro additional check or limitation and this not work? thanks...
Click to expand...
Click to collapse
without reaction, then try make separated thread, i actualy have one week "Motorola Moto G Pro" (XT2043-7), rooted, and wait for OTA, UpdateCheck in Settings not show me, try LMSA Rescue/Download and show me same version as have installed QPRS30.80-109-2-7...
Questions:
- Have any user of same phone, without root, already showed Octorber OTA?
- Is on rooted posible UpdateCheck with show if OTA avaiable?
- Have any working solution for OTA update on rooted phone without need connected with PC? Similar or same as i write about Nokia7Plus?
(i mean without flash back stock img, make ota, patch new boot.img file in MagiskManager, flash it via TWRP booted...
i think without PC be sure posible flash back stock boot.img to boot partition, before OTA, maybe download zip of full "rom" and extract boot.img, patch via MagiskManager, but not flash patched
EDIT: Sollution here
The answers to your first two questions are yes. When on stock I successfully updated. And while rooted there was a notification for ota update, it would download, but fall to install. I came across a way to do it without having to connect to pc. Some said it was successful but I was not able to try. It has something to do with placing your original boot.img into a a folder on one of the root directories but I had no idea how in the hell they came up with the system path to the file (encrypted??) Because I didn't have any of the folders on my phone and was to lazy at the time to ask for help. It was also an older thread so I didn't feel like bringing up a thread that old.
without root you updated system to higher (with Ocrober security patches) version than QPRS30.80-109-2-7 (this version have September security patches) ?
second part of you answer i think not understand, with rooted phone, put boot.img in "a" directory in one (which?where?) root folder and OTA services flash it before upgrade/reboot???
please, anyone with "Motorola Moto G Pro" (XT2043-7), channel "reteu", have already displayed update notification for "QPRS30.80-109-2-8" ?
Yesterday i finally get OTA notify with QPRS30.80-109-2-8, with Magisk installed, ofcourse failed install, then i find this solution, to update OTA over Air with Magisk installed without need any steps with PC
Code:
1. Settings System/DeveloperOptions/AutomaticSystemUpdate=Disable
2. Settings System/SystemUpdate/.../SmartUpdate=Disable
3. MagiskManager UninstallMagisk/RestoreImages
4. Settings System/SystemUpdate "doing normal update and wait for finish"
5. After OTA Instralled [B]NOT[/B] Restart
6. MagiskManager MagiskInstall/InstallToInactiveSlotAfterOTA/LetsGo "wait for finish"
7. After Magisk installed tap to Reboot button in Magisk Instalation wIndow...
Very nice writeup. With respect to step 3, I never installed Magisk Manager (I simply did the patch of boot.img) so what should I do to restore image? With respect to step 5, how do I get to that point? Is it a prompt after rebooting?
flroots said:
[...] step 3, I never installed Magisk Manager (I simply did the patch of boot.img) so what should I do to restore image?
Click to expand...
Click to collapse
you must have installed Magisk via TWRP (only temporary booted is enough), this make backup image which is latter in MagiskManager used for restore
flroots said:
[...] step 5, how do I get to that point? Is it a prompt after rebooting?
Click to expand...
Click to collapse
this is normal OTA screen, is show if you check update and if available, then show progress about installing, only is need after ota finished, not using reboot button in this OTA screen, but make steps 6 and 7
k3dar7 said:
you must have installed Magisk via TWRP (only temporary booted is enough), this make backup image which is latter in MagiskManager used for restore
Click to expand...
Click to collapse
I installed Magisk Manager via download of apk file (not TWRP). I then clicked on Magisk and chose "Select and patch a file". The end result was getting root. I never actually did a separate install of Magisk or Magisk Manager. I wonder if your step 3 will work in this case.
k3dar7 said:
this is normal OTA screen, is show if you check update and if available, then show progress about installing, only is need after ota finished, not using reboot button in this OTA screen, but make steps 6 and 7
Click to expand...
Click to collapse
Thanks
flroots said:
I installed Magisk Manager via download of apk file (not TWRP). I then clicked on Magisk and chose "Select and patch a file". The end result was getting root. I never actually did a separate install of Magisk or Magisk Manager. I wonder if your step 3 will work in this case.
Click to expand...
Click to collapse
Understand, but as i write, you must have installed Magisk via TWRP, with this method, Magisk make backup of boot image to "/data/magisk_backup_SomeRandomStrings/boot.img.gz", this file is used when you doing step 3, but if you only patch stock boot file, then ofcourse this backup is not created... i sugest you:
- revert boot to stock via same way as you flash patched before, but using stock boot.img
- boot TWRP (NOT flash, use command is section "Boot") and install Magisk.zip oficial release
- if on your phone/touchscreen variant not work touchscreen in TWRP, then (while still is booted TWRP) install it using adb
Thanks.
I have a couple questions:
1. Is it true that one shouldn't do an OTA unless the corresponding firmware can be downloaded due to the fact that you will lose root and not be able replace it until the corresponding boot.img can be obtained?
2. When downloading firmware from LMSA, does it download the latest or does it download your current version?
flroots said:
I have a couple questions:
1. Is it true that one shouldn't do an OTA unless the corresponding firmware can be downloaded due to the fact that you will lose root and not be able replace it until the corresponding boot.img can be obtained?
2. When downloading firmware from LMSA, does it download the latest or does it download your current version?
Click to expand...
Click to collapse
1. NO - i with Magisk installed, receive OTA October (delayed) and November, and hope with december be same
not need wait for avaiable boot.img, because with "Boot TWRP & Flash MagiskZip" is patched onthefly "any" version of boot partition on device.
2. not sure, i not use LMSA
k3dar7 said:
1. NO - i with Magisk installed, receive OTA October (delayed) and November, and hope with december be same
not need wait for avaiable boot.img, because with "Boot TWRP & Flash MagiskZip" is patched onthefly "any" version of boot partition on device.
Click to expand...
Click to collapse
Thanks, that sounds great. Would you mind elaborating the steps involved? I have TWRP and Magisk installed now.
k3dar7 said:
Yesterday i finally get OTA notify with QPRS30.80-109-2-8, with Magisk installed, ofcourse failed install, then i find this solution, to update OTA over Air with Magisk installed without need any steps with PC
Code:
1. Settings System/DeveloperOptions/AutomaticSystemUpdate=Disable
2. Settings System/SystemUpdate/.../SmartUpdate=Disable
3. MagiskManager UninstallMagisk/RestoreImages
4. Settings System/SystemUpdate "doing normal update and wait for finish"
5. After OTA Instralled [B]NOT[/B] Restart
6. MagiskManager MagiskInstall/InstallToInactiveSlotAfterOTA/LetsGo "wait for finish"
7. After Magisk installed tap to Reboot button in Magisk Instalation wIndow...
Click to expand...
Click to collapse
Do these steps cause loss of data? Thanks
flroots said:
Do these steps cause loss of data? Thanks
Click to expand...
Click to collapse
i ofcourse not garant ;-) but for me nothing lost, also installed magisk modules is preserved...
k3dar7 said:
Yesterday i finally get OTA notify with QPRS30.80-109-2-8, with Magisk installed, ofcourse failed install, then i find this solution, to update OTA over Air with Magisk installed without need any steps with PC
Code:
1. Settings System/DeveloperOptions/AutomaticSystemUpdate=Disable
2. Settings System/SystemUpdate/.../SmartUpdate=Disable
3. MagiskManager UninstallMagisk/RestoreImages
4. Settings System/SystemUpdate "doing normal update and wait for finish"
5. After OTA Instralled [B]NOT[/B] Restart
6. MagiskManager MagiskInstall/InstallToInactiveSlotAfterOTA/LetsGo "wait for finish"
7. After Magisk installed tap to Reboot button in Magisk Instalation wIndow...
Click to expand...
Click to collapse
Tried the above steps, but OTA update unsuccessful. Discovered that phone still rooted so obviously step 3 did not work for me. What should I try next? How about fastboot of original boot.img?
flroots said:
Tried the above steps, but OTA update unsuccessful. Discovered that phone still rooted so obviously step 3 did not work for me. What should I try next? How about fastboot of original boot.img?
Click to expand...
Click to collapse
step 3 restore boot image(what show you MagiskManager as output while you restore images??), but without reboot you have ofcourse still root, and you can't reboot if you want patch boot in other slot after ota via MagiskManager....
but i don't know reason why OTA failed anyway restoring original boot.img via fastboot be i think possible (not try in MotoGPro but manytime with Nokia7Plus)
k3dar7 said:
step 3 restore boot image(what show you MagiskManager as output while you restore images??), but without reboot you have ofcourse still root, and you can't reboot if you want patch boot in other slot after ota via MagiskManager....
but i don't know reason why OTA failed anyway restoring original boot.img via fastboot be i think possible (not try in MotoGPro but manytime with Nokia7Plus)
Click to expand...
Click to collapse
Thanks. Magisk simply says, "restoration done". Once I fastboot boot.img will I need to re-install magisk from scratch or should I continue with steps 6 and 7?
flroots said:
Thanks. Magisk simply says, "restoration done". Once I fastboot boot.img will I need to re-install magisk from scratch or should I continue with steps 6 and 7?
Click to expand...
Click to collapse
maybe magisk backup boot.img have already twrp inside if you install twrp before magisk?
anyway, if you flash stock boot.img, then step 6&7 is not applicable, because this need booted rooted system
btw: method above work for me also while i upgrade from Android10 to Android11 ;-)

Categories

Resources