Miui goes into bootloop after flashing Magisk - Xiaomi Redmi Note 7 Pro Questions & Answers

So I've been on the Global Indian MIUI for a while now. And what I usually did was I patched a boot image file using Magisk and then flashed it through fastboot. That way I didn't need a custom recovery and I could get straight updates from MIUI as usual.
After updating to MIUI 10.3.13 I tried to do the same thing once again, but this time I'm met with a Bootloop. The bootlogo shows and the boot animation starts and then suddenly phone reboots and it keeps going on like this until I flash back the stock boot image.
So I installed TWRP and tried flashing Magisk from there but same result. Goes into bootloop. Tried flashing the patched image file from TWRP but end result still same.
So any solution to this? Or any rooting alternative other than magisk?
Is anybody else facing this or are is it just me?

Related

Phone not booting up

So apparently after many days of using CM13.1
Yesterday i tried tried Carbon Rom( Yep the new build of 14.1)
Used it for 2 days then thought of rooting it.
Flashed the latest SR3 Supersu package and was working fine.
Flashed Arise V4A and changed SELinux to permissive and then the phone won't boot properly up.
Either it would get to the boot anim then get bootlooped again or completely shut down.
I tried restoring nandroid,but same result.
Tried flashing different roms,fastboot images of COS12.1,11,13.1 and even tried OPO toolkit
All results in the same bootloop/shutdown in boot anim.
Any help would be nice !
Update : Tried AOSPe and worked for a while until i clicked on Facebook and it shut down completely ;-;
TWRP works but when i flash roms it shuts down
If you have access to twrp, wipe data,cache,dalvik.
If it still doesn't boot flash stock cos13.1 ROM from fastboot.
ROM mirrors here: https://forums.oneplus.net/threads/mirrors-for-official-cyanogen-roms-ota-updates.141825/
seanwlk said:
If you have access to twrp, wipe data,cache,dalvik.
If it still doesn't boot flash stock cos13.1 ROM from fastboot.
ROM mirrors here: https://forums.oneplus.net/threads/mirrors-for-official-cyanogen-roms-ota-updates.141825/
Click to expand...
Click to collapse
Well i tried your method but after this TWRP shuts down or restarts when i try to flash roms or gapps.
Or bootloop when i flash Su.
try to flash stock firmware image, there ya go : https://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541

soft brick again and again

Hello,
I have many problems with my oneplus 6, twrp and the a/b partitioning.
I installed twrp successfully and had a working setup, but wanted to start from scratch so I installed a custom-oos using twrp again.
But then I only could boot to twrp and no chance of getting the rom to boot up.
In twrp I installed the rom again and now the only thing I see when trying to boot up is the white led, nothing else.
This happened a few times now, don't know what I am doing wrong.
Any help?
Thanks
Try flashing Magisk. It worked for me but I was on official OOS...
Joan Tur (OP6)
Thanks, but magisk says "unable to repack boot image"

Oneplus 5 stuck on fastboot, but still have access to recovery.

Hi XDA, after searching over countless threads and not being able to find the answer i'm after here goes my first post, so the problem originated when I accidentally signed out of Snapchat and wasn't able to sign back in due to safetynet so I went about trying to unroot and reroot using Magisk, however when installing the Magisk.zip, I ran into "Error 1" which I fixed by flashing a stock boot image with "fastboot flash boot boot.img", finally the zip file "successfully" installed via TWRP but upon trying to boot my phone to OS it constantly just goes back to fastboot mode and refuses to boot properly, I still have access to TWRP and have tried flashing back to stock recovery as well to no avail. What i'm wondering is if I somehow flashed the boot improperly and that's causing it to not boot to OS and if not what else can I do to restore my phone to working order, at this point i'm not that fussed over having root access but need to know how I can fix this, I have also tried flashing a stock ROM from stock recovery but just after starting the install it and the loading bar going up slightly it stops and goes back to the file selection page. Please help!
Edit: I have flashed the boot.img again using a newer stock image and now when I attempt to boot normally I get taken to a black screen with a white LED

Twrp opening screen shown then device goes into bootloop.

I had pixel experience rom installed and tried to flash the new update when it showed error 7. Anyways, trying to fix it, i decided to wipe and install fresh rom. But when i try to boot to recovery now, the twrp opening screen comes up and instead of going into recovery menu, goes into boot loop. Tried flashing dummy img and flashing new twrp img too but same result. Tried booting to recovery using fastboot boot twrp.img too still same result.
btw device is redmi note 5 pro
[email protected] said:
I had pixel experience rom installed and tried to flash the new update when it showed error 7. Anyways, trying to fix it, i decided to wipe and install fresh rom. But when i try to boot to recovery now, the twrp opening screen comes up and instead of going into recovery menu, goes into boot loop. Tried flashing dummy img and flashing new twrp img too but same result. Tried booting to recovery using fastboot boot twrp.img too still same result.
btw device is redmi note 5 pro
Click to expand...
Click to collapse
Try reinstalling the stock ROM, it'll delete any modification brought to the device...

Help! Stuck to the google loading screen after rooting andriod 11

My pixel 3a stuck to the loading screen after flashing the magisk patched boot.img.
Used magisk manage V23 stable
boot.img obtained from OAT image sargo 210805.001
I already tried flash to both slots but did seem to work either. Phone starts normally if flashing back to the unpatched boot.img
Does anyone else have the same problem?
Thanks!!!
The loading screen may take several minutes, be patient. If really stuck, there is something wrong with the magiskboot.img. You need to flash back boot.img and do the rooting again, try beta version channel in Magisk app.

Categories

Resources