Magisk 21.4 semi-bricked my phone. How to recover. - Moto E4 Plus Questions & Answers

If you haven't backed up your phone with TWRP in a while, do it before upgrading Magisk. 20.4 works fine, but 21.4 messes up the boot image. I was able to get to recovery through the bootloader menu. If I attempted to boot the system, I'd get a blackscreen.
To get it back (without a TWRP backup), I had to extract the boot.img from the stock rom and flash it in TWRP. Then I had to reinstall my preferred rom and gapps.
If you have a TWRP backup, you can just restore the boot image to recover if this happens to you.

Related

OOS 5.0 With Root stuck on booting

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

[SOLVED]TWRP on STOCK?

TWRP on STOCK?
For some reason, I cannot seem to boot into stock ROM after flashing TWRP. I have tried both 3.2.3.1 and 3.2.1.1, and it always boots back into recovery. I have only been able to boot without TWRP directly installed, and booting TWRP from computer.
No problem with installed TWRP with other ROMs.
jhedfors said:
TWRP on STOCK?
For some reason, I cannot seem to boot into stock ROM after flashing TWRP. I have tried both 3.2.3.1 and 3.2.1.1, and it always boots back into recovery. I have only been able to boot without TWRP directly installed, and booting TWRP from computer.
No problem with installed TWRP with other ROMs.
Click to expand...
Click to collapse
I just went back to stock ProjectFI today using fastboot. After initial setup, I went back to fastboot to boot the 3.2.3-1-payton.img, then adb pushed both the twrp-installer-payton-3.2.3-1 and Magisk, installed them both at the same time and rebooted without incident.
EDIT: I used PAYTON_FI_OPWS28.46-21-12_subsidy-DEFAULT_regulatory-DEFAULT_CFC
Thanks @johnjingle.
Not sure if it was because I had Magisk already installed first that was my issue, but flashing TWRP on a fresh boot image THEN flashing Magisk did the trick.

bootloop after flashing magisk 18 - PIXEL 3

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 .

Help with Magisk root Pixel 2 factory Android 9.0.0 installed

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.

Question Root lost after official update - help?

I was unlocked and rooted at Indian 12.5.2 ROM for the longest time. Got a notification for 12.5.5 and installed it. That took away root, but that was expected.
Now I've installed official TWRP, but as soon as I install Magisk (either via zip from recovery or patched twrp recovery image via the Magisk app), when I try rebooting to system, phone instead boots back to TWRP with a 'Android Rescue Party Trigger' error.
Happened every single time I've tried above - phone tries booting and then boots to recovery, and only way to boot system again is to install unpatched TWRP recovery, but then there's no root.
What should I do?

Categories

Resources