Hi all,
I have an Xperia 10 running lineage, everytime it does an A/B upgrade, magisk and twrp will be gone.
If I try to manually update via twrp it kind of screws up the encrypted data partition and causes a bootloop.
I'm currently contemplating on how I should use SmartPack-Kernel Manager to flash twrp before the phone reboots into the new active partition, and then restores magisk with twrp, any comments?
(Unable to try it first because I thought magisk would have been preserved but I guess it didn't so I'm waiting for the next update)
It works, just use the SmartPack-Kernel Manager to flash Magisk and TWRP. Installing Magisk with Magisk Manager won't work because apparently it only patches the current boot image.
Xanth0k1d said:
Hi all,
I have an Xperia 10 running lineage, everytime it does an A/B upgrade, magisk and twrp will be gone.
If I try to manually update via twrp it kind of screws up the encrypted data partition and causes a bootloop.
I'm currently contemplating on how I should use SmartPack-Kernel Manager to flash twrp before the phone reboots into the new active partition, and then restores magisk with twrp, any comments?
(Unable to try it first because I thought magisk would have been preserved but I guess it didn't so I'm waiting for the next update)
Click to expand...
Click to collapse
Same with me it seems that every time u upgrade lineage os twrp recovery gets replaced by lineage os recovery and magisk gets uninstalled too
It's better to don't upgrade lineage os so it doesn't happen again
Related
went through the tutorial and everything went fine until magisk installation. stuck on loading screen forever. only complete wipe\installing twrp img helps to restore the system.
but then no root of course.
any ideas?
+1, I have the same error in havoc pie, in oreo magisk work fine?
subwoffer13 said:
went through the tutorial and everything went fine until magisk installation. stuck on loading screen forever. only complete wipe\installing twrp img helps to restore the system.
but then no root of course.
any ideas?
Click to expand...
Click to collapse
Could you provide information about your current setup as well as steps you performed to flash Magisk?
@topjohnwu have previously mentioned that it might not be a good idea to have TWRP installed along with Magisk on A/B devices (since the recovery is in the boot image). Use fastboot to boot TWRP and then install Magisk leaving the stock recovery untouched.
I have solved it by reinstalling stock os, and then when installing twrp and magisk , I didn't check "install twrp as system app" , as it suggests at the end of flashing . Bam , now I have twrp recovery and rooted phone .
Read a similar problem from this thread https://forum.xda-developers.com/k20-pro/how-to/redmi-k20-pro-firmware-10-3-8-0-9-6-13-t3939647
I'm already unlocked and I was gonna stick with the China ROM for now, so I flashed Magisk. After an hour I noticed my root access WAS GONE. So tried restarting it and... bootloop! Magisk uninstaller fixed this BUT I want that Magisk. So I kept retrying... Fastboot, flash TWRP(another issue is TWRP wont stick no matter what it will be replaced by stock recovery), Install magisk, bootloop... Rinse and repeat.
I tried 2 methods installing Magisk. TWRP and the Boot Image Patching using boot.img from latest China ROM miui_RAPHAEL_V10.3.12.0.PFKCNXM_75ea367433_9.0.zip
Im running out of ideas, can anyone here help and share how they fixed it? Thanks!
you should change to Xiaomi EU rom, no issues with Magisk.
Try installing ver 18 or 18.1 magisk i had issues with ver 19 and up on pocof1. Also on pocof1 you had to install dfe (disable force encryption) and them twrp wouldnt be replaced with stock boot recovery. Also any update that comes when twrp is installed will rewrite it to stock recovery.
Wipe userdata/factory reset after installing magisk
I have the same issue and resolve it by install OrangeFox-R10.0_8-Stable & Magisk-v20.1.zip.
So, i updated magisk (version 21? EDIT: manager was set to upda te to beta, but 20.4 also bootloops :/ ). Before rebooting, also installed to inactive slot, cause.... If you can do it after a OTA update, why not doing it normally, right? Bootloop. Have to press both the power button and VOL up for it to turn off. Usually just the long press on power buttton would do the trick.
Oneplus 7T OOS 10.012 EU
SOLUTION for the bootloop:
- Installed TWRP 3.4.0.2
- Because it cannot access data partition nor transfer files via USB, i did adb push -p local-pc-file-here /tmp
- So, i installed OOS 10.0.13 from there and it booted fine, however without magisk even tough i installed it from /tmp as well right after the ROM install without reboot.
- Tried to reinstall magisk from TWRP (had to reinstall it too, as OOS deleted it), but it bootlooped again. So, i'll wait for a boot file with it.
Executing Magisk-uninstaller-20201003.zip on TWRP did NOT work, cause it couldn't mount the necessary partitions.
EDIT: I have no magisk modules, so i don't know why all of this mess :/
If magisk was already installed on the inactive slot before you patched it, the boot image gets corrupted (at least it always does on my 7T). Really shouldn't use the ota patch feature if you're not installing an ota
Allen77777 said:
If magisk was already installed on the inactive slot before you patched it, the boot image gets corrupted (at least it always does on my 7T). Really shouldn't use the ota patch feature if you're not installing an ota
Click to expand...
Click to collapse
Gotcha! All good now. BTW, if anyone needs, there's a patched boot file on 7T's forum for 10.0.13 EU.
I have the same issue with 10.0.13 HD65AA.
First I tried to do the full update like usual with installing Magis 21 into both slots before reboot but then I got stuck on the boot animation.
Tried a lot of things until I found this thread here. Once I got into TWRP I pushed the latest ROM over to the phone and installed it and I could get back into my phone again. But once I tried to install Magisk via TWRP or boot the patched image for 10.0.13 HD65AA from XDA I get stucked in the boot animation again. So I had to once again push the ROM to the phone and install it into the second slot and once again my phone boots again.
So for whatever reason there is an issue with Magisk and both 10.0.13 HD65AA and HD65BA. So at least for me for now no root.
Thank you very much for at least getting into my phone again without losing any data. :good:
Hi,
I am running the official Lineage 16.0 build from Microg with the latest Orangefox Recovery.
This week I installed an Lineage Update, the phone booted into Recovery, I entered my pattern, phone said unable to decrypt but did flash my update and rebooted. But now I lost magisk and have no root anymore. So tried to boot into recovery, enter my pattern, but decryption fails....
So I put the magisk .zip on a microsd card, but cant find it in my recovery to flash...
Formatting data will wipe all my apps, images, settings and so on am I right?
Is there a way to fix this?
How do you guys update your Roms with magisk root? That's the first time I used magisk, used the addon from lineage before to root my phones.
I've been using LineageOS on my Poco F3 for a while now, everything worked as supposed until I updated Magisk from v23 to 24 a while back. Safetynet wouldn't pass anymore and I ended up extracting the boot.img and 'injecting' Magisk and got everything to work again, including safetynet. The only thing: I couldn't update LineageOS anymore. It would end up in a bootloop and after a while would revert and works again.
I then try to install the OTA first, installed Magisk through the app on the inactive partition and then do a reboot. This ended up in a bootloop which I could only recover from by doing a factory reset from recovery.
I now again have a working phone, using partition a as the active partition and an update would result in a bootloop (in Lineage recovery, after the update during the bootloop, I see the new version on partition b), eventually falling back to the working a partition.
I already did a Factory reset and a complete reinstall of LineageOS.
The Magisk App is now installed (through the .apk), but it does not say installed in the app, the only option when I try Install is 'select and patch a file'.
I am not sure what to do next and not brick my device Any help would be much appriciated.