Third method worked for me. I deleted all of the files of the last module installed using TWRP and the bootloop was gone, the phone started normally. Thanks for the help!
@@kamalazzouzi4671for me yeah, it saved my phone, I just had to hold the volume down button until I reached the home screen then there was a big safe mode written in the corner and as promised by the video, it deactivated all of my tweaks at next boot (despite having magisk bootloop protector)
Thanks a lot for your method of extracting the boot.img from the rom zip file and installing it via fastboot. You saved me from factory resetting my phone after it got into a bootloop post installing magisk. Thanks
Wasn’t aware that my samsung phone had a safe mode feature, the only thing that still worked while bootlooping as I couldn’t access the recovery nor the fastboot mode
My phone went into bootloop. (Because I loaded a module.) When I loaded the original init_boot.img file, the phone turns on. However, when I patch it with magisk and flash init_boot.img again, it goes into bootloop again. When I run the "adb wait-for-device shell magisk --remove-modules" code while the phone is in bootloop to delete the magisk modules, it does not see the phone and the bootloop continues. (While bootloop is occurring, the phone restarts itself before the hyper os message appears and this prevents it from seeing the phone.) Booting into safe mode did not work. (I do this with the original patch file because bootloop occurs when magisk is installed and I cannot switch to safe mode while bootloop, and therefore magisk does not work in safe mode. The only solution is to install twrp, but my device does not support twrp (mi 14t pro (rothko)). Can anyone help? I want to root it again, but right now I have to use my phone without rooting. (I do not want to reset my phone.)
3rd method. you saved my data first time root, but due to decent iq and failing twrp, i came to know orange fox works same as twrp, or else after this video i would have failed.
Hello, I installed magisk on my rooted Samsung A51 phone and pressed the update button, then my phone did not turn on again and went into bootloop. But I'm trying the solution you showed in the video. adb folder does not open, what should I do? I don't want my data to be deleted.
@@SufyanAli-zh3pn I tried a few different methods but it still didn't work. The phone has been at home for a while now. I will take it to a phone repair shop soon.
In the second method will the device boot first time so we can clear magisk app data ? My twrp only works for first time after being flashed on the current rom and so its virtually useless for me unless i first flash Twrp again for method 3
in the 2nd method, the device will boot everytime until you decide to flash magisk patched boot.img (to get back root). so that time before flashing the boot u need to clear magisk data.
@@TekHckSir please help, I tried flashing magisk alpha from inside magisk delta. Now the phone is in bootloop. The Poco symbol shows then it goes black and again poco symbol shows. I have lineage os and Twrp installed. I cant boot into safe mode, when i try pressing pressing vokume up it goes into fastboot. Please help
![3 Methods to Boot any Android to Safe Mode [Includes Magisk Bootloop Fix]](http://i.ytimg.com/vi/jlkU-0qKbOA/mqdefault.jpg)
![3 Methods to Boot any Android to Safe Mode [Includes Magisk Bootloop Fix]](/img/tr.png)
![BLACK BAG - Official Trailer [HD] - Only in Theaters March 14](http://i.ytimg.com/vi/Du0Xp8WX_7I/mqdefault.jpg)
![Blox Fruits Dragon Rework Update [Full Stream]](http://i.ytimg.com/vi/EqDAp8udhm0/mqdefault.jpg)
Third method worked for me. I deleted all of the files of the last module installed using TWRP and the bootloop was gone, the phone started normally. Thanks for the help!
Safe mode worked for you??
@@kamalazzouzi4671for me yeah, it saved my phone, I just had to hold the volume down button until I reached the home screen then there was a big safe mode written in the corner and as promised by the video, it deactivated all of my tweaks at next boot (despite having magisk bootloop protector)
Thanks a lot for your method of extracting the boot.img from the rom zip file and installing it via fastboot. You saved me from factory resetting my phone after it got into a bootloop post installing magisk. Thanks
dude you just saved my huge time and saved me from danger. thanks a lot brother. you are really awsome
Thank you so much
You saved me
I got rid of bootloop of my Xiaomi device by removing magiskadule
First method is really very helpful!
Wasn’t aware that my samsung phone had a safe mode feature, the only thing that still worked while bootlooping as I couldn’t access the recovery nor the fastboot mode
Thank you!
Sir, could you please give a point how to clear magisk app data (before flash the stock ROM)?
Thanks! Third method helped very quickly!
My phone went into bootloop. (Because I loaded a module.) When I loaded the original init_boot.img file, the phone turns on. However, when I patch it with magisk and flash init_boot.img again, it goes into bootloop again. When I run the "adb wait-for-device shell magisk --remove-modules" code while the phone is in bootloop to delete the magisk modules, it does not see the phone and the bootloop continues. (While bootloop is occurring, the phone restarts itself before the hyper os message appears and this prevents it from seeing the phone.) Booting into safe mode did not work. (I do this with the original patch file because bootloop occurs when magisk is installed and I cannot switch to safe mode while bootloop, and therefore magisk does not work in safe mode. The only solution is to install twrp, but my device does not support twrp (mi 14t pro (rothko)). Can anyone help? I want to root it again, but right now I have to use my phone without rooting. (I do not want to reset my phone.)
I made the mistake of updating Magisk and the boot loop showed up. Not even the 3rd method works for me. Not sure what to do at this point.
i dont have twrp and my Tecno k17 got bootloop by a magisk module. When i go to recovey mode it says "No command"
YOU ARE LIFE SAVER
Holy shit thanks a lot brother
you saved my phone
1st method is effective - thanks
3rd method.
you saved my data
first time root, but due to decent iq and failing twrp, i came to know orange fox works same as twrp, or else after this video i would have failed.
Third method works thank you sir
Hello, I installed magisk on my rooted Samsung A51 phone and pressed the update button, then my phone did not turn on again and went into bootloop. But I'm trying the solution you showed in the video. adb folder does not open, what should I do? I don't want my data to be deleted.
Same
How did you resolve the problem
Same model asy he Kiya main b or ab ya bootloop mein hai
@@SufyanAli-zh3pn I tried a few different methods but it still didn't work. The phone has been at home for a while now. I will take it to a phone repair shop soon.
In the second method will the device boot first time so we can clear magisk app data ? My twrp only works for first time after being flashed on the current rom and so its virtually useless for me unless i first flash Twrp again for method 3
in the 2nd method, the device will boot everytime until you decide to flash magisk patched boot.img (to get back root).
so that time before flashing the boot u need to clear magisk data.
@@TekHckSir please help, I tried flashing magisk alpha from inside magisk delta. Now the phone is in bootloop. The Poco symbol shows then it goes black and again poco symbol shows. I have lineage os and Twrp installed. I cant boot into safe mode, when i try pressing pressing vokume up it goes into fastboot. Please help
Thanks. 1st method working in lineage os 21
thankk yooouuuu soo much bro you saved my phone
an idea
patch stock img, create a kernel su img, delete everything you need, patch magisk lol
I rarely comment but thanks 🙏 for the help
Thanks
In android 13 twrp data folder is empty
😅same problem.
fastboot flash boot C:\Users\KSK\Downloads\boot.img
target reported max download size of 534772736 bytes
sending 'boot' (16692 KB)...
FAILED (remote: unknown command)
finished. total time: 0.017s