Bootloop after uninstalling Magisk any solution? - Samsung Galaxy M30 Questions & Answers

Hi guys i rooted my m30 using magisk for few months ago and i realized i cant use any bank application in my phone and that is really uncovenient. so i decided i want to unroot my phone, i tried to uninstalled the magisk from the application, after the system reboot my phone stuck in bootloop. the only way to escape the bootloop is to install magisk again. can someone help me to unroot my phone without any problem from bootloop? Any replies is appreciated

Bootloop after uninstalling​Experiencing a bootloop after uninstalling Magisk, either through the app or with the apk renamed to uninstall.zip and flashed through recovery, might mean that the boot image hasn't been restored correctly or that dm-verity otherwise triggers.
Try one of the following:
Restore your stock boot image (there's a copy of it stored in /data, named stock_boot_<sha1>.img.gz).
Flash a no-verity zip directly after uninstalling Magisk/restoring your stock boot image.
Dirty flash your ROM/factory image/firmware package.
Clean flash your ROM/factory image/firmware package.

contackcontact said:
Hi guys i rooted my m30 using magisk for few months ago and i realized i cant use any bank application in my phone and that is really uncovenient. so i decided i want to unroot my phone, i tried to uninstalled the magisk from the application, after the system reboot my phone stuck in bootloop. the only way to escape the bootloop is to install magisk again. can someone help me to unroot my phone without any problem from bootloop? Any replies is appreciated
Click to expand...
Click to collapse
Have u rooted ur device running on latest April 2021 patch? I also want to root but stuck....
Btw you can install latest firmware using odin it will solve all prblms

Related

Unroot/Hide root without causing a bootloop?

Hello,
I spent all day trying to find an answer to my problem, hope that you guys will help me
So, first of all, I'm on Mi Max 4/128, MIUI 8.2.3.0, unlocked BL.
What I need to do is root this device, add some apps as system apps and, since I use some apps which are quite keen on checking the SafetyNet, get rid of the root or hide it while keeping the changes I made while rooted.
I installed TWRP, flashed SuperSU, modified what I wanted, unrooted using the SuperSU GUI... And on the restart it started bootlooping, showing only the MI logo.... The only way out of this bootloop is to install the SuperSU again or clear the Data in TWRP, both of which defeat the purpose.
Tried with Magisk, hoping to simply hide the root... But it seems that MIUI won't fully pass the SafetyNet verification. Also after uninstalling it's all the same story with bootloops.
Next, after unrooting I tried flashing just the stock recovery.img and boot.img via fastboot, no luck there...
From what I've managed to find out, it's all caused by the forced dm-verity encryption. So one of the options for me would be to flash a modified kernel/boot.img that would not force the encryption, I guess? (I'm still a little hazy on the subject, correct me if I'm wrong ) Tried to do it, but I can't for the life of me find the modified boot.img or kernel for the latest Helium MIUI
Do you have any sugestions?
Okay, I figured it out! All it takes to avoid a bootloop after the unrooting is to flash this script:
https://forum.xda-developers.com/redmi-note-3/how-to/modified-twrp-deleting-emmcappsboot-t3371667
Unless anyone's got an idea how to hide the root with Magisk on MIUI, thread can be closed
Hi,
Even I'm facing the same issue. I'm on stock ROM and unrooting from SU caused bootloop. Now, I restored the nandroid backup and the Redmi 3s prime is booting. However, I would like to unroot it. Can we simply disable Dm-verity from TWRP before unrooting from SU? Or disabling Dm-verity will cause any issue?
The boot.img patcher I mentioned in the second post does just that, it deletes the dm-verity. Try it out

Magisk Modules causing bootloop.

I flashed the magisk module for using the auxiliary cameras in the Google-camera, and it resulted in the phone only booting to the flashboot mode and nothing else. I tried that twice and I'm certain that flashing it was the only problem.
I reflashed the stock boot image to solve it.
Is there a way now to safely flash it ?
Can anyone help combine a list for some other Magisk modules that may cause bootloop for the device?
PS: The device was rooted without using any custom recovery.
ha ha.. same thing happened with me.. flash stock boot.img and you'll be able to boot back to your system.. but if you need magisk back, custom recovery needs to be there.. which will help you to uninstall the module you have installed..
fathomer said:
I flashed the magisk module for using the auxiliary cameras in the Google-camera, and it resulted in the phone only booting to the flashboot mode and nothing else. I tried that twice and I'm certain that flashing it was the only problem.
I reflashed the stock boot image to solve it.
Is there a way now to safely flash it ?
Can anyone help combine a list for some other Magisk modules that may cause bootloop for the device?
PS: The device was rooted without using any custom recovery.
Click to expand...
Click to collapse
Factory reset will remove the rogue module

Problems rooting Xt-1952-1

Hey guys,
Hope someone can help me or point me in the right direction, I am having serious issues trying to root my 1952-1.
I followed the guide in this post to install TWRP
https://forum.xda-developers.com/g7-play/how-to/how-to-successfully-install-twrp-g7-play-t3979701
I followed all the guidelines but when i tried rebooting to recovery I ended up in having TWRP splash screen bootlooping, but was still able to fastboot boot twrp.
I then flashed Magisk, it completed and then i booted the phone back up, no magisk was in the app drawer. So i installed the Magisk Manager apk and this told me I was not rooted. Repeated the whole thing and still the same result.
I have also tried patching the boot.img file using magisk but same as before the phone is not rooted, on top of this I have also clean flashed the stock rom but again still not rooted.
Anyone got any ideas ?
Yeah the rooting process can be a little bit frustrating. You will have to copy the original boot.img file to your phone. In the magisk app make sure you enable recovery mode. Then you can patch the boot.img file. Copy it back to your computer and flash it via fastboot. But there is a catch. The phone will be rooted only if you boot the phone through recovery.

J6 SM-J600FN - Is it possible to install TWRP without boot-loop?

I have been trying to root my J6 SM-J600FN for a while, and I thought I was getting close to rooting it when I installed TWRP. But then, my phone was stuck in a boot-loop. I was able to fix it by installing current firmware, and I decided to attempt it a second time. I got the same result. Is there anything I can use to install TWRP that doesn't result in a boot-loop? I just want my phone rooted and be done with it.
As far as i know, trying to root stock rom isn't easy. I could be wrong but idk. You can try by:
1. Flashing stock
2. Flashing TWRP
3. Format data
4. Flash DM-Verity and Disable Force-Encrypt then flash magisk.
And i think you can't flash kernels on stock. I could be wrong but idk.
Hey, how did you even install TWRP?
Before I tried installing it my model number was "SM-J600 FN/DS" and now after the install, when I plug it into my pc it says that it's "FN-600G." Whenever I try to boot it in system mode it's stuck in a loop.
I haven't tried flashing the newest firmware yet because I can't even download it for my country.
Sorry, I am a total newbie and can't seem to fix it.
Al-Ameen Adewunmi said:
I have been trying to root my J6 SM-J600FN for a while, and I thought I was getting close to rooting it when I installed TWRP. But then, my phone was stuck in a boot-loop. I was able to fix it by installing current firmware, and I decided to attempt it a second time. I got the same result. Is there anything I can use to install TWRP that doesn't result in a boot-loop? I just want my phone rooted and be done with it.
Click to expand...
Click to collapse
Hi Guys,
Did you manage to do this? I was experiencing the same bootloop issue and I think it is the version of Twrp (I was using 3.3.1-0).
I used Odin to flash a lower version 3.2.3 found here after which I flashed this DM Verity + Magisk.
Root Success!

After trying to root with Magisk...

After I tried rooting with magisk, Pixel 2XL, 11.0.0 (RP1A.200720.009) And I flashed the patched .img file from magisk, My phone then right there got into a bootloop, I was able to get into the bootloader but nothing else, Now I cant get out of the bootloader and im wondering if there is someway to fix this, I saw a thread on this, Which says I have to change Magisk Manager to Canary but I cant because im stuck in a bootloop AND im in the bootloader, I already unrooted my drive by Flashing the original img but no help...
Any help?
If you flashed a patched img, then flashing back an unpatched boot.img would fix it. You can always download the the full factory image and flash it back.
killer23d said:
If you flashed a patched img, then flashing back an unpatched boot.img would fix it. You can always download the the full factory image and flash it back.
Click to expand...
Click to collapse
already done, if i flash it again will it work? because im still stuck in the bootloop
Nicster205 said:
already done, if i flash it again will it work? because im still stuck in the bootloop
Click to expand...
Click to collapse
if you reflash the factory boot.img then you'll get out of bootloop.
Nicster205 said:
After I tried rooting with magisk, Pixel 2XL, 11.0.0 (RP1A.200720.009) And I flashed the patched .img file from magisk, My phone then right there got into a bootloop, I was able to get into the bootloader but nothing else, Now I cant get out of the bootloader and im wondering if there is someway to fix this, I saw a thread on this, Which says I have to change Magisk Manager to Canary but I cant because im stuck in a bootloop AND im in the bootloader, I already unrooted my drive by Flashing the original img but no help...
Any help?
Click to expand...
Click to collapse
reflashing the factory boot.img seems useless. you can long-press the power button to force power down. then power up to the fastboot mode,and reflash the full factory image(11 or 10). the nomal methon working on 10 seems dizzy in 11 now.
fwiw, heres the path i used...i hate making it more steps than needed (tranferring boot image to device and back again for magisk patching for example)...
1) flash-all.bat (with wipe enabled - because clean install)
2) Immediately on reboot from 1 and before it gets anywhere near to beginning of setup: fastboot boot twrp-3.4.0-1-taimen.img
3) adb push Magisk-e66b0bf3(20425).zip /tmp
4) adb shell twrp install /tmp/Magisk-e66b0bf3(20425).zip
5) adb reboot
6) after reboot, install canary magisk manager (for whatever reason doesnt install from TWRP flash)
7) open canary magisk manager and enable magiskhide
This is caused by twrp
Use android toolbox, just boot twrp, flash magisk
boot into twrp go to advanced fix bootloop option reboot
Nicster205 said:
After I tried rooting with magisk, Pixel 2XL, 11.0.0 (RP1A.200720.009) And I flashed the patched .img file from magisk, My phone then right there got into a bootloop, I was able to get into the bootloader but nothing else, Now I cant get out of the bootloader and im wondering if there is someway to fix this, I saw a thread on this, Which says I have to change Magisk Manager to Canary but I cant because im stuck in a bootloop AND im in the bootloader, I already unrooted my drive by Flashing the original img but no help...
Any help?
Click to expand...
Click to collapse

Categories

Resources