I want to switch from SuperSU 2.79 to Magisk. I tried the unrooting option in SuperSU but the phone doesnt boot, it stays on the google image. Reflashed SuperSU 2.79 and phone boots without a problem.
Then i booted into botloader and flashed the original stock boot.img from n6f27c factory image, but same result, phone stays at the google image and doesnt boot. Reflasing supersu 2.79 fixes the problem.
What would be the best way to move from supersu to magisk without having to completely wipe phone and flash n6f27c factory file.
Would flashing boot.img and system.img be enough? And then install magisk from twrp to get root again or is there another option that works.
TMG1961 said:
I want to switch from SuperSU 2.79 to Magisk. I tried the unrooting option in SuperSU but the phone doesnt boot, it stays on the google image. Reflashed SuperSU 2.79 and phone boots without a problem.
Then i booted into botloader and flashed the original stock boot.img from n6f27c factory image, but same result, phone stays at the google image and doesnt boot. Reflasing supersu 2.79 fixes the problem.
What would be the best way to move from supersu to magisk without having to completely wipe phone and flash n6f27c factory file.
Would flashing boot.img and system.img be enough? And then install magisk from twrp to get root again or is there another option that works.
Click to expand...
Click to collapse
Try using unsu.zip. You can find it in osm0sis' odds and ends thread. Scroll down through the first post.
ktmom said:
Try using unsu.zip. You can find it in osm0sis' odds and ends thread. Scroll down through the first post.
Click to expand...
Click to collapse
Thanks, that did the trick. Rooted with Magisk now.
I have Magisk 12, supersu and twrp on OP5.
when trying to update to 13.3 it shows
error
boot image patched by other program
please restore to stock boot image
restore stock kernel and re-flash 13.3.
tommy1616 said:
restore stock kernel and re-flash 13.3.
Click to expand...
Click to collapse
how to restore stock kernel?
netsonic said:
how to restore stock kernel?
Click to expand...
Click to collapse
You should be able to choose the full unroot option in the SuperSU app and let it restore your boot image. Don't let it restore recovery...
Then you boot to recovery and flash the Magisk zip again.
If it didn't work you'll have to open up your ROM zip/firmware package and extract the boot.img file. You can flash it in TWRP.
Didgeridoohan said:
You should be able to choose the full unroot option in the SuperSU app and let it restore your boot image. Don't let it restore recovery...
Then you boot to recovery and flash the Magisk zip again.
If it didn't work you'll have to open up your ROM zip/firmware package and extract the boot.img file. You can flash it in TWRP.
Click to expand...
Click to collapse
the full unroot option in the SuperSU - Is it in setting->uncheck "enable supersu"?
netsonic said:
the full unroot option in the SuperSU - Is it in setting->uncheck "enable supersu"?
Click to expand...
Click to collapse
It's the option named "Full unroot"... :laugh:
There's more on this in the Magisk troubleshooting guide ("Boot image patched by other programs").
I had SuperSU installed (but I needed to hide the root from some apps), and I installed Magisk with the Direct Install method with succes.
I reboted and now is stuck in a boot loop...
What can I do to fix it?
I'm using a Galaxy Note 3 (Android 5) with stock firmware.
https://didgeridoohan.com/magisk/Magisk#hn_Moving_from_another_systemless_root_solution_to_MagiskSU
Edit:
https://didgeridoohan.com/magisk/Magisk#hn_Bootloop
And of course the rest of the guide:
https://didgeridoohan.com/magisk
I didn't know I have to backup my boot.img file
I'm searching for my original boot.img file from the firmware right now, but until the download is complete (15 hours :| ), I'm trying to flash the magisk uninstaller and use it with twrp terminal.
Didgeridoohan said:
Edit:
https://didgeridoohan.com/magisk/Magisk#hn_Bootloop
Click to expand...
Click to collapse
Thank you!
Solved it!
I flashed the Magisk uninstaller (Magisk-uninstaller-20180921.zip from https://github.com/topjohnwu/Magisk/releases) with TWRP, and it worked!
So I've used TWRP r16 and it throws an "Image not signed or corrupt" error as suggested by other users I ignored it, but everytime I reboot to system and try to get to recovery "no command" show's up meaning TWRP was replaced by stock recovery all help will be appreciated.
Thanks
Akash731 said:
So I've used TWRP r16 and it throws an "Image not signed or corrupt" error as suggested by other users I ignored it, but everytime I reboot to system and try to get to recovery "no command" show's up meaning TWRP was replaced by stock recovery all help will be appreciated.
Thanks
Click to expand...
Click to collapse
You need to flash Magisk after flashing TWRP
1. Flash Latest TWRP
2. Reboot to TWRP
3. Flash Magisk
If you boot in to system after flashing TWRP, TWRP will be removed
pradeeppk said:
You need to flash Magisk after flashing TWRP
1. Flash Latest TWRP
2. Reboot to TWRP
3. Flash Magisk
If you boot in to system after flashing TWRP, TWRP will be removed
Click to expand...
Click to collapse
Hey thanks that worked.
But everytime I boot to system and boot to twrp the data gets encrypted and I can't access the files do you happen to know any solution for this?
Akash731 said:
Hey thanks that worked.
But everytime I boot to system and boot to twrp the data gets encrypted and I can't access the files do you happen to know any solution for this?
Click to expand...
Click to collapse
If you are on stock Rom, according to my knoweldge it is not possible to remove encryption, if you format your date in twrp for removing encryption then reboot to system you can see that the phone is again encrypted.
But in custom roms this doesnt happen.
pradeeppk said:
You need to flash Magisk after flashing TWRP
1. Flash Latest TWRP
2. Reboot to TWRP
3. Flash Magisk
If you boot in to system after flashing TWRP, TWRP will be removed
Click to expand...
Click to collapse
pradeeppk said:
If you are on stock Rom, according to my knoweldge it is not possible to remove encryption, if you format your date in twrp for removing encryption then reboot to system you can see that the phone is again encrypted.
But in custom roms this doesnt happen.
Click to expand...
Click to collapse
I don't want to try custom rom's as this is my main device guess I'm stuck with the encryption then thanks for your help. :good:
Edit:-
Tried TWRP r20 it decrypts fine thanks
pradeeppk said:
You need to flash Magisk after flashing TWRP
1. Flash Latest TWRP
2. Reboot to TWRP
3. Flash Magisk
If you boot in to system after flashing TWRP, TWRP will be removed
Click to expand...
Click to collapse
You don't have to flash Magisk after flashing TWRP. The two are unrelated.
After flashing TWRP you have to boot into recovery, not system. Once TWRP was started, you can reboot into system. No need for Magisk (unless you want Magisk anyway).
gewe said:
You don't have to flash Magisk after flashing TWRP. The two are unrelated.
After flashing TWRP you have to boot into recovery, not system. Once TWRP was started, you can reboot into system. No need for Magisk (unless you want Magisk anyway).
Click to expand...
Click to collapse
It will not work in stock ROM, if you flash a custom rom there is no need to flash Magisk.
You should flash Magisk or custom kernel after flashing TWRP otherwise it will be erased.
Google about TWRP erasing after reboot you should get too many posts regarding this
This is one of them
https://forum.xda-developers.com/oneplus-3t/help/twrp-deleted-booting-t3769867
pradeeppk said:
It will not work in stock ROM, if you flash a custom rom there is no need to flash Magisk.
You should flash Magisk or custom kernel after flashing TWRP otherwise it will be erased.
Google about TWRP erasing after reboot you should get too many posts regarding this
This is one of them
https://forum.xda-developers.com/oneplus-3t/help/twrp-deleted-booting-t3769867
Click to expand...
Click to collapse
I am using stock ROM, and yes, also Magisk (installed later). IIRC Magisk is not needed for TWRP to work. When I receive the next OTA notification, I will test this.
The thread you are referring to is for a OnePlus 3T. For our device this is the thread: https://forum.xda-developers.com/moto-g5s-plus/development/recovery-twrp-3-1-1-r7-t3694910.
Since there is no official TWRP for the Moto G5S Plus, I took the following text from the TWRP page for the Moto G5S.
Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery. After typing fastboot reboot, hold the key combo and boot to TWRP. Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install.
Click to expand...
Click to collapse
Instead of that you can also use fastboot reboot-bootloader, and then from the bootloader start recovery.
pradeeppk said:
It will not work in stock ROM, if you flash a custom rom there is no need to flash Magisk.
You should flash Magisk or custom kernel after flashing TWRP otherwise it will be erased.
Google about TWRP erasing after reboot you should get too many posts regarding this
This is one of them
https://forum.xda-developers.com/oneplus-3t/help/twrp-deleted-booting-t3769867
Click to expand...
Click to collapse
Two days ago I received a notification for an OTA update, containing the August 2019 security patches.
After going back to stock ROM, installing all the updates up to the latest, I installed TWRP. After booting into recovery, and then into system, and recovery again, TWRP was gone. Strange, I don't remember this happening before. Maybe I always installed Magisk before booting into system.
Bottom line: you were right, I was wrong. Thanks for pointing it out.
gewe said:
Two days ago I received a notification for an OTA update, containing the August 2019 security patches.
After going back to stock ROM, installing all the updates up to the latest, I installed TWRP. After booting into recovery, and then into system, and recovery again, TWRP was gone. Strange, I don't remember this happening before. Maybe I always installed Magisk before booting into system.
Bottom line: you were right, I was wrong. Thanks for pointing it out.
Click to expand...
Click to collapse
As like you said this is the first time in my life i need to flash magisk to stick twrp.
I usualy doesn't use root or custom roms, install twrp, remove unnecessary apps from stock system, replace host files with adaway hosts, replace or edit gps config files. and continue using stock.
This is the main routine from Android 1.5
(Samsung spica (i think it was the first Android phone from Samsung)).
It may be due to security reason stock kernel or system delete twrp.
When installing magisk it patch stock boot image, that may be the reason of twrp remains after flashing magisk.
Hello, I want to root my phone, but I want to know if it's better to use twrp to flash magisk, or simply directly flash magisk.
what does it mean simple directly flash magisk?
you can flash modified boot with magisk
jjsan said:
what does it mean simple directly flash magisk?
you can flash modified boot with magisk
Click to expand...
Click to collapse
Flash magisk directly with fastboot flash command, or flash twrp then flash magisk with it