I just updated my Resurrection Remix Rom through OTA and installed twrp retention and magisk to inactive slot.after rebooting it just keeps stuck into boot screen and gets into recovery?? Can anyone tell what's wrong.
Related
Today I updated my magisk installation from v17.3 to v18.0 using the Magisk Manager app, I rebooted my phone and I'm stuck on the phone logo.
I can get into TWRP, from there I tried to reinstall v17.3 and also uninstall v18.00 but for both cases I get "unable to open boot image" followed by a red "Error 1" in TWRP.
I have a OnePlus Two, running stock MM rom from OnePlus. Never had a problem with Magisk, any tips on how to fix it?
It's not a bootloop, I think boot image is broken.
Thanks for your help
I managed to fix this by downloading the stock rom and flashing the boot.img file inside using TWRP, reflashed Magisk 18.0 without problems.
Does anyone know how to apply Havoc OS OTA from system updater without any boot loop for MI A2 Jasmine sprout. Whenever I get the notification & try to update from there after the download it successfully gets installed then in reboot it stucks in havoc logo. Tried from magisk twrp ab retention script magisk install to inactive slot after ota too but still fails. Only way to avoid it is when I get an update I download the rom on pc gapps magisk & other necessary things then clean flash from twrp & again have to set up device from begining which is really really bothersome. Plz help anyone..... TIA :crying:
PiSTONCFBRO said:
Does anyone know how to apply Havoc OS OTA from system updater without any boot loop for MI A2 Jasmine sprout. Whenever I get the notification & try to update from there after the download it successfully gets installed then in reboot it stucks in havoc logo. Tried from magisk twrp ab retention script magisk install to inactive slot after ota too but still fails. Only way to avoid it is when I get an update I download the rom on pc gapps magisk & other necessary things then clean flash from twrp & again have to set up device from begining which is really really bothersome. Plz help anyone..... TIA :crying:
Click to expand...
Click to collapse
you don't need the GAPPS or Magisk when you're dirty flashing the update
just download the ROM file and move it to your internal memory
reboot into recovery
dirty flash the ROM
that's it
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.
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
Hello,
I had a lenovo p2 (kuntao) lying around which I recently decided to unlock.
After unlocking I decided to flash lineageOS 18.1 on it. I wiped the phone and flashed lineageOS on it.
My phone was on the latest ota update before (android 7) and I flashed lineageOS 18.1 (android 11) on it.
Then I decided to get magisk for it. I first installed latest magisk app and patched the boot.img which was provided with the lineageOS zip. Then I went into fastboot mode and flashed the patched boot image.
This resulted in the phone bootlooping. I could only see 'lenovo powered by android' screen and it never reached lineageOS loading animation.
After flashing the stock boot image the boot loop was fixed.
While patching I had option to 'preserve force encryption' I tried both the images (on and off) both resulted in bootloop.
I even tried the latest canary build. It had the same issue too.
I've attached the stock boot.img and a patched one.
I've also attached the patch log
I don't know what other info to provide.
Plz help