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.
Related
I was on Oos 4.5.1 and wanted to update to Oreo. I followed the thread on this forum and downloaded the new TWRP BluSpark img file, the OOS full package and the Magisk zip. Booted into recovery, installed the img file and flashed OOS and the Magisk zip file. When i rebooted into system, i noticed Root wasn't installed and my recovery had reverted to stock recovery but my device bootloader was still unlocked. So i booted into fastboot mode, flashed the Blusparks img file and booted into recovery and flashed the magisk file. Now the phone rebooted and its stuck on the "Powered By Android" screen. The boot image of OP hasn't shown up. What do i do? I really don't want to hard reset my phone :/
No need to hard reset the phone, just go to recovery clean flash excluding internal storage then flash oxygen os 5.0 zip file and magisk 14.5.
Magisk 14.0 has boot issues.
I had similar issues which I resolved easily.
You may trigger DM verity flag after booting which you can disable easily.
ersandeepkr said:
No need to hard reset the phone, just go to recovery clean flash excluding internal storage then flash oxygen os 5.0 zip file and magisk 14.5.
Magisk 14.0 has boot issues.
I had similar issues which I resolved easily.
You may trigger DM verity flag after booting which you can disable easily.
Click to expand...
Click to collapse
Oh yes, i figured Magisk 14.0 was the issue. I waited for 30 mins+ and the phone still didnt boot up, so i switched it off and booted into recovery and flashed just the OOS zip file and it worked. I don't want to wipe data as well.
Can i flash Blusparks twrp from adb, boot into recovery and just flash OOS and Magisk 14.5 and wipe dalvik/cache?
Manjumeth-95 said:
Oh yes, i figured Magisk 14.0 was the issue. I waited for 30 mins+ and the phone still didnt boot up, so i switched it off and booted into recovery and flashed just the OOS zip file and it worked. I don't want to wipe data as well.
Can i flash Blusparks twrp from adb, boot into recovery and just flash OOS and Magisk 14.5 and wipe dalvik/cache?
Click to expand...
Click to collapse
You can flash bluspark recovery from fastboot. But for the successful installation and avoid problems, forget the application data. You can fresh install apps which is always recommended while flashing any ROM even if it is updated version. I never dirty flash ROM. I care for internal storage and not for the small apps.
You can try dirty flash as you stated but stability may be an issue.
Dirty flashed with Magisk 14.5 and it worked
Hello,
I have been struggling to root my device. I have not wiped and rooted it in some time and now coming back to it again magisk keeps breaking my device.
I have clean flashed the latest android 9.0.0 build. I have flashed TWRP custom recovery 3.3.0 successfully. I have tried to flash magisk 3 times now and afterwards my phone wont boot. I originally used magisk manager to get the latest zip and patch my boot image. I then rebooted to to bootloader and ran fast boot flash boot patched_Magisk.img. This wiped out my twrp recovery and my phone wouldn't boot, i couldn't get back into twrp recovery. I reflashed latest 9.0 build and wiped everything. I flashed twrp again and tried to flash Magisk 20.0 from recovery. It was successful but again i couldn't boot into my phone and it eventually restarted back into recovery which i still had twrp this time. I then tried it again with 19.3 and the same thing happened. can anyone tell me what is going on here? What am I missing? I have been having reflash factory 9.0 build each time just to get it to remove the patched boot image and boot up again.
Was either the TWRP version or the two check boxes it has now to install twrp app as system. Installed 3.2.3-1 and didnt install the twrp app through the recovery check boxes and it worked.
when i flashed the rom and now i no longer have access to root, twrp and on top of that.... gapps failed so i lost my google account on my phone. can anyone help me recover twrp, root, and successfully flash gapps. i have a great working os 17.1. no complaints there.
badwax said:
when i flashed the rom and now i no longer have access to root, twrp and on top of that.... gapps failed so i lost my google account on my phone. can anyone help me recover twrp, root, and successfully flash gapps. i have a great working os 17.1. no complaints there.
Click to expand...
Click to collapse
LineageOS 17.1 comes with a own recovery. Use the installer.zip provided on twrp.me to install TWRP. After that start TWRP and format /data. That's necessary to install the GApps. Otherwise you end in a bootloop.
Now flash GApps and Magisk and boot into system.
You can also temporarily boot into TWRP with "fastboot boot twrp.img" in fastboot. Then do backups etc. and reinstall the system.
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
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.