Hey here
Im on android 7.0 and the device is galaxy s7 edge G935F and no matter what i do..... Unrooting with the managaer options or flash the magisk uninstaller in twrp it always causes a boot loop. It starts normal when i flash magisk again... it would be easy to flash a new rom but i want to keep some changes ive made while rooted so thats the problem and i read a lot of flashing the boot loader (thats the BL part in the extracted rom package right?) from the rom thats currently installed. But that would wipe everything right? Or can i somehow flash that one like i flash magisk in twrp
I wonder if here is anything i can do to unroot successfully? Cache wipe wont end the loop
As always thanks for your time and answer
With best regards
Chris
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.
Can i install magisk through temporary twrp (using fastboot boot recovery xxx.img) in my poco f 1 ?
The answer to that would be a definite maybe.
Joke aside, that should work fine as long as TWRP is otherwise working as it should. There's no difference in functionality between flashing or just booting TWRP.
Why not flash it directly? That is, if there is a twrp for your phone.
As to Magisk, ask XDA
Sent from my SM-A605FN using Tapatalk
pr1jker said:
Why not flash it directly? That is, if there is a twrp for your phone.
As to Magisk, ask XDA
Click to expand...
Click to collapse
But i want to flash OTA
And before flashing OTA i will uninstall magisk
Didgeridoohan said:
The answer to that would be a definite maybe.
Joke aside, that should work fine as long as TWRP is otherwise working as it should. There's no difference in functionality between flashing or just booting TWRP.
Click to expand...
Click to collapse
If i flash temporary twrp , i can flash my OTAs too
I seen some of the people following this,
Flashing temporary twrp and flashing magisk and whenever OTA receives they are simply uninstalling magisk and flashing OTA.
Here my question if i go with this magisk will work perfectly or not ?
@Nicky Cheer There should be no issues with that setup. If you haven't already, I'd advice you to also take a look at @topjohnwu's OTA instructions.
Didgeridoohan said:
@Nicky Cheer There should be no issues with that setup. If you haven't already, I'd advice you to also take a look at @topjohnwu's OTA instructions.
Click to expand...
Click to collapse
Tq @Didgeridoohan and @topjohnwu for clarifying
But one more doubt what is the difference between restore image and complete uninstall under magisk manager ?
Nicky Cheer said:
Tq @Didgeridoohan and @topjohnwu for clarifying
But one more doubt what is the difference between restore image and complete uninstall under magisk manager ?
Click to expand...
Click to collapse
Restore image - only restore the stock boot image and leave all Magisk internals intact.
Complete uninstall - remove everything Magisk related from your device.
First option is preferred, since you then won't have to set everything up again afterwards.
Hi,
I have the following problem.
I was able to install the custom ROM properly on my Mi9t pro. Unfortunately my Orangefox Recovery was deleted After the installation.
If I want to install Magisk now, I have to reflash the recovery first.
Do you have any idea why the recovery is deleted? Is there a way to prevent that?
Thanks in advance.
der_andi01 said:
Hi,
I have the following problem.
I was able to install the custom ROM properly on my Mi9t pro. Unfortunately my Orangefox Recovery was deleted After the installation.
If I want to install Magisk now, I have to reflash the recovery first.
Do you have any idea why the recovery is deleted? Is there a way to prevent that?
Thanks in advance.
Click to expand...
Click to collapse
Your (custom) Recovery was really deleted?
Or replaced by stock Recovery
Who says that installation of Magisk requires custom Recovery?
Magisk documentation (Installation Instructions) - please find it on Magisk Github - certainly not.
Patch the boot.img and flash (it can be flashed by Fastboot, hence custom Recovery is not a must to have)
Hi,
it really gets deleted. My cell phone is then only in fastboot mode.
I am not interested in flashing Magisk either, but rather that recovery after an installation is no longer available. This makes installing updates more cumbersome.
I only have the problem when I flash a custom ROM. when I flash a MIUI ROM from xiaomi.eu Beta, the recovery is retained.
Hello everyone!
I just rooted my Galaxy A30 using Magisk. From what I have understood in my experience rooting this. This phone doesn't have a ramdisk so Magisk basically only boots when I do the recovery key combo. So I was wondering, Is it possible to install TWRP on this device since Magisk is basically hijacking the recovery to run. If it is possible, could someone guide me on how to install it while preserving Magisk?
Thanks in advance
The only way is installing TWRP via Odin. And then flash Magisk.zip