Switching from SuperSU to Magisk problems - Galaxy S6 Q&A, Help & Troubleshooting

Greetings,
I'm trying to move from SuperSu to Magisk, but have hit a problem with "fully" unrooting SuperSU.
If I tell it to restore the stock boot image the full unroot fails.
If I tell it not to restore the stock boot image, the full unroot "succeeds", but the stock boot image is not restored (obviously) and Magisk fails with an error about non-stock boot image.
If I re-install SuperSU the log shows it attempting to restore the factory boot image, failing and then going ahead with the already patched image.
Is there any way to install just the boot image (Odin, TWRP or ???) without wiping the entire phone?
Phone is a G920T with DPK1, I have the full DPK1 stock image but don't know how to install just the boot image.
Any help is greatly appreciated!

Related

Need MHA-L29 recovery.img

Unlocked bootloader and tried to with SuperSU but no boot. Having a hard time to go back to stock but need to find stock recovery for newest FW C567B190. I could not boot into TWRP only flash it so I couldn't make a backup. I just was able to get into the wifi restore screen and it downloads the 2.4gb image and installs but then said I have serious errors and recommended a factory restore, did it but same error. I did make a backup of all the other partitions so I hope to be able to get something going. New here and all this was certainly easier on my 6P and OP3. Thanks for the help.
rzracer2 said:
Unlocked bootloader and tried to with SuperSU but no boot. Having a hard time to go back to stock but need to find stock recovery for newest FW C567B190. I could not boot into TWRP only flash it so I couldn't make a backup. I just was able to get into the wifi restore screen and it downloads the 2.4gb image and installs but then said I have serious errors and recommended a factory restore, did it but same error. I did make a backup of all the other partitions so I hope to be able to get something going. New here and all this was certainly easier on my 6P and OP3. Thanks for the help.
Click to expand...
Click to collapse
Which SuperSU did you try? The only official working one is SuperSU 2.82 SR1, the others fail to install.
And unless you decrypted (Wipe - 'Format Data' button in TWRP) SuperSU will remove the encryption flag in fstab in ramdisk... That means you'll boot but stay encrypted, which leads to a bootloop.
You could try flashing this stock boot image for C567B190 in TWRP (Install - Install Image - select 'boot' partition): https://mega.nz/#!cw01zCCS!AX3wKw0V7pbIYC79Ny6OJ5CTuyxq-xA1ibltLMIRRZQ
Then flash this SuperSU (It's to stay encrypted): https://mega.nz/#!18FW1QTQ!3DCA3KrIUSRqEu4L-expci4HcKtk6F25fE1u6ecJV9Q
If that fails, here's stock recovery for C567B190: https://mega.nz/#!hgsEhBiC!Jf2Utp768UIS0N1-3jhPeoN0qaW_TlFsFf5uN9vKLEs
Recovery needs to be flashed with fastboot in download mode.
Thanks for the information Stockholm! After the second wifi recovery download it booted fine but did relock the bootloader. I did use 2.82 Sr1 but didn't format data which as you stated caused a bootloop. Might give it another try but I might just return it. Not happy with the stock firmware so I need to spend some time and see if there is a ROM available proper smartlock, raise to wake would be nice as it even works on my S8 with Glipse Notifications but not on the Mate. Thanks again!
ante0 said:
Which SuperSU did you try? The only official working one is SuperSU 2.82 SR1, the others fail to install.
And unless you decrypted (Wipe - 'Format Data' button in TWRP) SuperSU will remove the encryption flag in fstab in ramdisk... That means you'll boot but stay encrypted, which leads to a bootloop.
You could try flashing this stock boot image for C567B190 in TWRP (Install - Install Image - select 'boot' partition): https://mega.nz/#!cw01zCCS!AX3wKw0V7pbIYC79Ny6OJ5CTuyxq-xA1ibltLMIRRZQ
Then flash this SuperSU (It's to stay encrypted): https://mega.nz/#!18FW1QTQ!3DCA3KrIUSRqEu4L-expci4HcKtk6F25fE1u6ecJV9Q
If that fails, here's stock recovery for C567B190: https://mega.nz/#!hgsEhBiC!Jf2Utp768UIS0N1-3jhPeoN0qaW_TlFsFf5uN9vKLEs
Recovery needs to be flashed with fastboot in download mode.
Click to expand...
Click to collapse

can't change to magisk instead of superSU on samsung j111f

I have a samsung j111f rooted with a twrp recovery via flashing superSU zip but when i wanted to change to magisk i couldn't uninstall superSU via full unroot , I managed to do that many times before and rooted it again via twrp, but the problem now is that when i try to do a full unroot it asks me to revert to stock boot image i hit yes then it asks to revert to stock recovery so i hit no because i need it to flash magisk so it fails to full unroot, but when i hit no at recovering boot image it bypass but magisk dont want to flash because i have a modified boot partition; So please would you help me ?
PS : I have an unlocked bootloader witch i got since my first rooting following this : https://forum.xda-developers.com/android/development/root-samsung-galaxy-j1-ace-sm-j111m-f-t3395520
Also i have installed twrp recovery via odin on that unlocked bootloader because it always boot to stock recovery when i try to flash it on stock firmware
Never mind i found the sollution just full unroot without fixing bootloader from supperSU ,booted into twrp recovery flashed stock boot.img then magisk.zip and rebooted that's it got evrything worked
Click to expand...
Click to collapse

Restore boot image after unroot

Hi, years ago I installed lineage os 14.1 and supersu 2.82 on my father's mi 4c and I now wanted to unroot it to switch to magisk.
The unroot worked, however I wasn't able to restore the boot image. When I tried to install magisk, it didn't install it responding "Boot image patched by other programs!". So, I tried to flash the boot image with two I had from years ago but they both caused bootloop. Luckily I made a backup with TWRP of the boot before flashing it so I was able to start lineage again. Is there anyone who can help me to restore the boot image? Maybe without wipe all the data if possible. Thanks

I can't seem to Flash Magisk after the most recent OTA

I have TWRP installed but any time I try to Flash magisk, the boot image seems to corrupt and leaves me on the 'Bootloader unlocked' screen. I have to boot back into bootloader and use the 'repair recovery boot loop' option just to get back into my phone which then doesn't have Magisk available and root has not taken. Does anyone have any advice? Is there a boot image I need to flash after Magisk maybe? I'm fairly new to all this.
Isadorian said:
I have TWRP installed but any time I try to Flash magisk, the boot image seems to corrupt and leaves me on the 'Bootloader unlocked' screen. I have to boot back into bootloader and use the 'repair recovery boot loop' option just to get back into my phone which then doesn't have Magisk available and root has not taken. Does anyone have any advice? Is there a boot image I need to flash after Magisk maybe? I'm fairly new to all this.
Click to expand...
Click to collapse
Hello, would love to know because I have same issue here …
In fact I could effectively have root and magisk installed once, then I installed viper which didn't work... I removed viper module from Magisk Manager, then reboot, then got into the issue you describe. The 'repair recovery boot loop' allows booting but magisk is removed. And if I flash magisk again from TWRP, then the phone won't boot.
I tried reinstall TWRP/Magisk without success, tried lock/unlock bootloader (don't do that ! I could get out of it but no more success with magisk), also tried to remove the viper module with TWRP file manager (I could but it did not solve the issue), not sure what to do now.
What versions TWRP and Magisk?

Lost root after rebuilding boot partition (still have twrp)

Hello,
So my phone was in a recovery boot loop and had to rebuild the boot partition in twrp. So I'm back in my phone now and everything is the same but have lost root. Still have access to twrp. It's been a while since I rooted it and don't have any of the files anymore. What do I need to flash to get root back? Do I need to back up all my data or will it be safe?
I am still running android 9 and oos 9.0.7 and I assume bootloader is still unlocked. Orignally rooted with magisk.
thanks
kaotik123 said:
Hello,
So my phone was in a recovery boot loop and had to rebuild the boot partition in twrp. So I'm back in my phone now and everything is the same but have lost root. Still have access to twrp. It's been a while since I rooted it and don't have any of the files anymore. What do I need to flash to get root back? Do I need to back up all my data or will it be safe?
I am still running android 9 and oos 9.0.7 and I assume bootloader is still unlocked. Orignally rooted with magisk.
thanks
Click to expand...
Click to collapse
Damn it, so I booted into twrp and then flashed latest magisk v23 zip but when it finished it said failed to mount partition in red and now the phone just boots to fastboot mode.. I can get back into twrp.. and all my files are still there in file manager.. but it won't boot into my phone.. only fastboot mode. Any advice?
First, boot into TWRP and delete all Magisk Module files and folders:
How to Uninstall Magisk Modules Using TWRP Recovery
Removing the Magisk module manually causes bootloop. You can easily uninstall Magisk modules using TWRP recovery without resetting your device.
www.droidviews.com
I had the same and it seems a module was causing fastboot mode. If that doesn't work try downloading and flashing the stock boot image for your OOS version in TWRP (remember to flash TWRP again before reboot). At least then you will have your phone back.

Categories

Resources