Related
So as the official bootloader unlock broadened the audience of this from tinkerers/developers to basically everyone I thought this guide might me helpful for some...
PREREQUISITES:
- Unlocked bootloader (official or unofficial)
- latest magisk manager installed on phone (https://github.com/topjohnwu/Magisk/releases)
- latest fastboot and adb binaries from google(https://developer.android.com/studio/releases/platform-tools)
- latest twrp.img to boot (NOT FLASH), zip not needed (https://eu.dl.twrp.me/NB1/)
- Fully stock partitions (if you do not have this reflash latest stock via ostla), as OTA updates will do a integrity check.
- PC with WIN/OSX/LINUX with USB port^^ (on windows you might have to add .exe to the commands)
- disable automatic system updates in developer options, as you will still have to manually root the updated partition, so this makes sure you don't miss it. You still get notifications on available updates and can apply them easily(as you will see)
SETUP_STEPS:
1. Go into Magisk manager and "just download" the latest zip
2.1 Run
Code:
adb reboot bootloader
or reboot into download/fastboot mode via other means
2.2 Run
Code:
fastboot boot twrp-3.2.3-1-NB1.img
(change this when your version of twrp differs)
2.3 Flash the .zip magisk downloaded in 1.)
2.4 Reboot.
Congratulations you now have root!
STEPS_TO_UPDATE:
1. Go into Magisk Manager -> Uninstall -> Restore Images
2. Apply Update, DO NOT REBOOT YET
3. When step to finished and it promts you to reboot go into Magisk Manager -> Install -> Install to inactive Slot
Congratulations you can now reboot and will have an updated Android while keeping full root.
ALTERNATIVE GUIDE (without twrp, using prerooted boot.img)
(works for newest patch level, where twrp isn't working yet)
this guide works on newest patches as long as someone provides a prerooted boot.img.
So basically you either need a boot.img available or twrp...
Hopefully this helps until TWRP is compatible with September Security Patch
LINKS:
stock boot.img: (may to october patches)
https://cloud.vault81.de/s/fnoizKwi8kNF3Rg
prerooted boot.img: (may to october patches)
https://cloud.vault81.de/s/AeHiE5HR2qonb3N
PREREQUISITES:
- same as above minus twrp
- patched/prerooted boot image (either create it yourself or use link provided here)
STEPS_TO_ROOT:
0.
Code:
adb reboot bootloader
or get into download mode otherwise
1.
Code:
fastboot boot NB1_prerooted_boot.img
1.1. The phone will boot into an temporarily rooted state,
2. Use magisk manager-> Install -> "Direct Install" to persist the root.
3. Reboot
Congrats you now have root even on versions where twrp isn't working yet....
Edit1:
Added link to all stock boot images from may to october security
Edit2:
Did the same for magisk prerooted
Edit3:
Added November images thanks to @czupyt
TWRP isnt working right now so whoever updated to September patch cant do anything except unlock bootloader. Unless someone can pull a boot.img from the newest patch so we can all patch it through Magisk and get root.
ironman38102 said:
TWRP isnt working right now so whoever updated to September patch cant do anything except unlock bootloader. Unless someone can pull a boot.img from the newest patch so we can all patch it through Magisk and get root.
Click to expand...
Click to collapse
I can try to do that once I get back home tomorrow...
I have working magisk on september patch so I should have both prerooted and Stock (cause Magisk backups those)
Trissi said:
I can try to do that once I get back home tomorrow...
I have working magisk on september patch so I should have both prerooted and Stock (cause Magisk backups those)
Click to expand...
Click to collapse
That would be much appreciated. Alot of people who just unlocked bootloader cant root and the maintainer of our TWRP will take a couple of days
indeed
ironman38102 said:
TWRP isnt working right now so whoever updated to September patch cant do anything except unlock bootloader. Unless someone can pull a boot.img from the newest patch so we can all patch it through Magisk and get root.
Click to expand...
Click to collapse
Simple Solution: A/B Partition System.
One Slot is the September Update, the other is August Update.
Update to September, Unlock, witch to other Slot with August Update, Boot Offical TWRP 3.2.3-0 (-1 not booting tho).
Now you can Install the Install Zip for the August BL and Magisk.
Bootup and use Magisk for Inactive Slot.
So did I, but I'm still on August Slot, I'll try to root the September Boot Partiton, and Install TWRP later when Fix arrived.
But rooted September doens't seem very... Stable
LoaderFabi said:
Simple Solution: A/B Partition System.
One Slot is the September Update, the other is August Update.
Update to September, Unlock, witch to other Slot with August Update, Boot Offical TWRP 3.2.3-0 (-1 not booting tho).
Now you can Install the Install Zip for the August BL and Magisk.
Bootup and use Magisk for Inactive Slot.
So did I, but I'm still on August Slot, I'll try to root the September Boot Partiton, and Install TWRP later when Fix arrived.
But rooted September doens't seem very... Stable
Click to expand...
Click to collapse
I'm already about to install the September patch again. I downgraded to May so I could root my phone and provide the clean boot.img from the stock September so people can root without twrp. And honestly A/B partition is still new to me that I still don't understand it
ironman38102 said:
I'm already about to install the September patch again. I downgraded to May so I could root my phone and provide the clean boot.img from the stock September so people can root without twrp. And honestly A/B partition is still new to me that I still don't understand it
Click to expand...
Click to collapse
A/B system is not Complex at all. It's just having 2x a Partiton Group (Boot, System, OEM and Recovery I think) and having the ability with Fatboot to simply switch between group A and group B.
You Inital Set up Partiton A (Nokia did for us with Nougat 7.1.1). If you Update, the Update will be extracted to Partition B, aftzer finishing you reboot to Partiton Group B, leaving group A untouched in Case of Error on Partition B.
That's it pretty much.
LoaderFabi said:
A/B system is not Complex at all. It's just having 2x a Partiton Group (Boot, System, OEM and Recovery I think) and having the ability with Fatboot to simply switch between group A and group B.
You Inital Set up Partiton A (Nokia did for us with Nougat 7.1.1). If you Update, the Update will be extracted to Partition B, aftzer finishing you reboot to Partiton Group B, leaving group A untouched in Case of Error on Partition B.
That's it pretty much.
Click to expand...
Click to collapse
No I get that but its just that I forget cuz this is my first phone with a/b partition. Anyway I got the phone to latest patch rooted so I'll see if I can get the untouched img
i'm on september security update and followed the seconde guide, but still show the android logo not booting the phone
eric194 said:
i'm on september security update and followed the seconde guide, but still show the android logo not booting the phone
Click to expand...
Click to collapse
On what step? Was it after you completed the guide? Or did the patched image not boot already?
If the patched image worked but it din't afterwards, you should reflash the stock_boot.img and redo the guide again because you probably flashed twrp and broke your bootloader...
As you can see in the prerequisites this guide requires a stock bootloader to start.
Trissi said:
On what step? Was it after you completed the guide? Or did the patched image not boot already?
If the patched image worked but it din't afterwards, you should reflash the stock_boot.img and redo the guide again because you probably flashed twrp and broke your bootloader...
As you can see in the prerequisites this guide requires a stock bootloader to start.
Click to expand...
Click to collapse
Nop I didn't flash twrp & Im on stock bootloader fresh september no modifications
eric194 said:
Nop I didn't flash twrp & Im on stock bootloader fresh september no modifications
Click to expand...
Click to collapse
So did the prerooted Image Boot?
If so it basically has to be your boot/system partition(I had mine compromised too and couldn't fix it with just flashing boot.img had to reflash everything via ostla)
If even the prerooted Image didnt boot im sorry i don't really know how to help, as I have working root with Magisk on September patch and the Image boots just fine for me....
eric194 said:
Nop I didn't flash twrp & Im on stock bootloader fresh september no modifications
Click to expand...
Click to collapse
Also you could Switch slots to revert back to august Patch and use the normal twrp guide then... And run the September Update via the magisk method
Trissi said:
Also you could Switch slots to revert back to august Patch and use the normal twrp guide then... And run the September Update via the magisk method
Click to expand...
Click to collapse
Ok I will try that hope it'll work
Edit : thanks dude it worked
Hey everyone;
My Nokia TA-1004 is on the July SP (4.88B_SP02) with unlocked bootloader (unofficial method), TWRP and Magisk installed.
Where can I find a stock boot.img to flash? I tried flashing the boot.img on this thread and although I can boot fine my wifi will be broken (I tried and had to restore nandroid backup). I also tried following the guide here but my OSTLA won't get past "Flashing Service Bootloader".
Any help?
Xayar said:
Hey everyone;
My Nokia TA-1004 is on the July SP (4.88B_SP02) with unlocked bootloader (unofficial method), TWRP and Magisk installed.
Where can I find a stock boot.img to flash? I tried flashing the boot.img on this thread and although I can boot fine my wifi will be broken (I tried and had to restore nandroid backup). I also tried following the guide here but my OSTLA won't get past "Flashing Service Bootloader".
Any help?
Click to expand...
Click to collapse
Flash the full Stock build (i think its even may patch), via ostla (https://forum.xda-developers.com/no...ia-8-official-firmware-links-updated-t3678487), then follow this guide then reapply all updates by following the update steps...
So which file do I have to download from https://drive.google.com/drive/folders/1t64iHuQQjmMnzcujZtjYplh6ipbiF6Cw ? I tried with the 488B one and got stuck on "flashing service bootloader"...
Xayar said:
So which file do I have to download from https://drive.google.com/drive/folders/1t64iHuQQjmMnzcujZtjYplh6ipbiF6Cw ? I tried with the 488B one and got stuck on "flashing service bootloader"...
Click to expand...
Click to collapse
Are you trying to use OST LA 6.1.2? Cuz that doesnt work
For the life of me I cannot root this latest patch. I have tried 6 times either with having the Magisk app repack the boot image or by booting TWRP to install the Magisk zip. Using either method forces my phone into the same state/condition. When the phone reboots, it goes into recovery which says the data on my phone may be corrupt and prompts me to either try again or factory restore (erase data).
i was able to. i booted into twrp, sideloaded the twrp installer, then the magisk zip and sultan kernel and everything is running smoothly for me
Ok, so I was able to recover and root from an answer given in a pixel 3 thread using:
Pixel 3/Pixel 3 XL
- fastboot flash boot --slot all boot.img (from December factory image)
- fastboot boot twrp-3.2.3-1...img
- install Magisk' uninstaller
- magisk-18.0.zip
- reboot system
What happens though is when I use adaway to update the hosts file, it breaks everything and I can't boot into system until I do the above steps again. Strange...
Do you have adaway install by chance?
Hi! I have no problem with last update, magisk nor adaway. I just flashed last update with flash-all.bat script, than fastboot twrp, install magisk ver. 18... and everything is working on 100%.
To successfully root on the Dec update you must use Magisk v18.0
[2018.12.8] Magisk v18.0 - Root & Universal Systemless Interface [Android 5.0+]
If you've used an older version, you'll get a boot loop into Recovery.
Side load / install the uninstaller from @topjohnwu's page linked above.
Then side load / install again with v18.0
Use the uninstaller first.
Diesel_Jeremiah said:
To successfully root on the Dec update you must use Magisk v18.0
[2018.12.8] Magisk v18.0 - Root & Universal Systemless Interface [Android 5.0+]
If you've used an older version, you'll get a boot loop into Recovery.
Side load / install the uninstaller from @topjohnwu's page linked above.
Then side load / install again with v18.0
Use the uninstaller first.
Click to expand...
Click to collapse
I'm on the December patch and am rooted with Magisk 17.1.
I actually just noticed the new update and am fixing to update Magisk. But you don't have to use v18. 0 to root December update. I've been on December update since it came out and rooted like always right away and haven't had any bootloops.
I rooted okay today with Magisk 18.0. It sounds like some people have had problems if they did not first uninstall Magisk with the latest uninstaller. That's what I did as a precaution (rather than just restoring the stock boot.img with the Magisk app, before upgrading the factory image).
FilthyFord said:
I'm on the December patch and am rooted with Magisk 17.1.
I actually just noticed the new update and am fixing to update Magisk. But you don't have to use v18. 0 to root December update. I've been on December update since it came out and rooted like always right away and haven't had any bootloops.
Click to expand...
Click to collapse
I had issues on both of my Pixel 2 phones trying to use any Magisk less than v18.0
I also had issues with v18.0 until I used the uninstaller first.
I read that other people were having the same issue.
I guess you got lucky?
Diesel_Jeremiah said:
I had issues on both of my Pixel 2 phones trying to use any Magisk less than v18.0
I also had issues with v18.0 until I used the uninstaller first.
I read that other people were having the same issue.
I guess you got lucky?
Click to expand...
Click to collapse
I guess so. I always open the .bat file and remove the -w so that it don't we my phone tough. Not sure if that makes a difference.
somin.n said:
Hi! I have no problem with last update, magisk nor adaway. I just flashed last update with flash-all.bat script, than fastboot twrp, install magisk ver. 18... and everything is working on 100%.
Click to expand...
Click to collapse
I enabled automatically granted root access and after a few mins after boot it granted access to adaway and after a reboot it seems to have worked again.
https://androidfilehost.com/?w=files&flid=249276&sort_by=date&sort_dir=DESC
I have installed incremental upgrades for 9.0.2 and 9.0.3 and been able to do a TWRP less root using Magisk. For the upgrade to 9.0.4 I downloaded and installed the full upgrade. Following installation of oos_9.0.4_patched_boot.img, my phone reboots to recovery so I am unable to load Magisk. So I have to reinstall oos_9.0.4_stock_boot.img and stay unrooted. I can't find a similar problem - am I unique? Any solutions?
Solanoantuna said:
I have installed incremental upgrades for 9.0.2 and 9.0.3 and been able to do a TWRP less root using Magisk. For the upgrade to 9.0.4 I downloaded and installed the full upgrade. Following installation of oos_9.0.4_patched_boot.img, my phone reboots to recovery so I am unable to load Magisk. So I have to reinstall oos_9.0.4_stock_boot.img and stay unrooted. I can't find a similar problem - am I unique? Any solutions?
Click to expand...
Click to collapse
Flash Full OOS via fastboot (Guide: https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665 )
Then use fastboot to enter twrp blu_spark (TWRP: https://forum.xda-developers.com/devdb/project/?id=27466#downloads )
Then flash magisk (Magisk: https://forum.xda-developers.com/ap...k-v7-universal-systemless-t3473445?styleid=21 )
After magisk installed, reboot phone and install magisk app
Done.
PeterSmusi said:
Flash Full OOS via fastboot (Guide: https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665 )
Then use fastboot to enter twrp blu_spark (TWRP: https://forum.xda-developers.com/devdb/project/?id=27466#downloads )
Then flash magisk (Magisk: https://forum.xda-developers.com/ap...k-v7-universal-systemless-t3473445?styleid=21 )
After magisk installed, reboot phone and install magisk app
Done.
Click to expand...
Click to collapse
My apologies for the late reply. I'm not heavily into these things so I was reluctant to go into TWRP. So I ended up resetting my phone and now it all roots quite happily. But thanks for the ideas.
hii i have one plus 6 oxygen 9.0.6 but am not able to find out patched file
image
Deleted
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 ;-)
Just updated from 24.3 to 25.1, everything seems fine.
First update of the manager, no problem. In manager tried to update magisk from 24.3 to 25.1. No errors in the log, but my phone (Mi9T Pro) didn't get past the Miui logo. Flashed 24.3 in Recovery again.
Any thoughts on how to update?
Edit: Solved. Dowloaded zip and flashed in recovery. All's well.
I have problem - I followed guide (https://www.xda-developers.com/how-to-install-magisk/)
On my Xiaomi A2 (jasmine_sprout) I've extracted boot.img, patched with app and flashed boot from PC and after reboot I have Magisk app version 1.0. After running it it want's to upgrade but after downloading and confirming upgrade it upgrades, icon is changed to magisk app and then it is fall backed to basic version 1.0. Tried to adb install v25.1 from pc and it says:
adb: failed to install Magisk-25.1(25100).apk: Failure [INSTALL_FAILED_UPDATE_INCOMPATIBLE: Package com.topjohnwu.magisk signatures do not match previously installed version; ignoring!]
After manual unistalling remaining v1.0 new can be installed but when executed it is auto degraded to version 1.0
Could somebody give me a clue what happened?
d3im said:
extracted boot.img, patched with app
Click to expand...
Click to collapse
Did you use magisk 25.1 to patch boot.img? And are you on Android 12?
I'm on android 11 And I've used magisk version 25.1 to patch boot.img
If you have twrp, try flash magisk in twrp.
donkeyman1234 said:
Just updated from 24.3 to 25.1, everything seems fine.
Click to expand...
Click to collapse
Same here
OK, just flashed new custom ROM (Android 12.1), then Magisk 25.1 zip via twrp and finally Magisk apk app and it just works fine
Glad it works.