Accidentally flashed SuperSU twice, can't uninstall, what do? - Desire 626 Q&A, Help & Troubleshooting

Title explains pretty much all of it. I tried to install SuperSU via TWRP, but I ended up installing it twice on accident and as a result I cannot fully uninstall (doing so from SuperSU fails) it so I can use Magisk instead. Problem is, in double flashing I deleted the boot image backup it made when it did it the first time. In order to maintain most of the stock functionality while being rooted with Magisk, and am I going to need to relock the bootloader and revert it back to stock and start over, or does someone have the backup files that I can use to revert it to the stock, unrooted 6.0.1 ROM so I can flash Magisk on?
It's a VM/Sprint 626S on Marshmallow, stock ROM.

Related

Lost TWRP and root after installing rom

Hey everyone
I've been using the XT1053 Retail US Stock Lollipop Flashable ZIP without issue for quite a while, but decided to update to the modded version 2. So I flashed it, xposed, and supersu again. Booted up, everything was okay. But then it said I needed to update my supersu binary and that I didn't have root, so I went to reboot into recovery and flash supersu once more.
However, now I can't access TWRP and it merely says "no command"
Should I just try installing TWRP again or is there a way to see if it's still installed? It's weird that this happened after flashing a rom
edit: reflashed twrp recovery img, back to normal. Can't explain what caused this though

twrp, Root, modify system slightly, unroot to pass safety net possible?

Hi,
Sprint Note 5 here. Basically I'm just trying to get my phone to be unrooted to pass SafetyNet (Android Pay, Pokemon Go, and others) but have some system modications (adaway and removed boot sounds mainly).
What I did do is flash stock odin firmware, then twrp, supersu, and make my changes. Then if I just unroot with supersu it still fails SafetyNet. If I unroot and tell SuperSU to restore boot.img then I get a bootloop. Probably due to TWRP still being there and not stock Recovery? So I thought maybe from there I can just flash boot and recovery via odin but that didn't seem to work either. Is it possible to take the stock firmware and flash whatever I need except system? Or not possible to alter system and go back to stock boot/recovery?
Edit: I took stock firmware, extracted it, removed system.img, and repacked it up (sboot.bin, modem.bin, recovery.img, cm.bin, boot.img, cache.img) and flashed it . It works but then brings me to some "system update" screen and then stock recovery with a verity failed error. Reboot to device just bootloops. Maybe I need to just remove more than just system?

how to switch from super su to magisk?

Hello, I am currently rooted on stock oos 4.0.3, with latest TWRP and super su free v2.79, can anyone help me out and tell me how to switch to magisk please, thank you!
Can I just use super su full unroot option then flash magisk?
Either reflash the original boot.img or download the unsu script from https://forum.xda-developers.com/showpost.php?p=63615067, then flash magisk again.
palesaint said:
Either reflash the original boot.img or download the unsu script from https://forum.xda-developers.com/showpost.php?p=63615067, then flash magisk again.
Click to expand...
Click to collapse
so flash unsu, then flash magisk. simple?
Dr Grato said:
so flash unsu, then flash magisk. simple?
Click to expand...
Click to collapse
If you use the unSU script the process is:
unSU
stock boot image
Magisk
This method did not work for me.
I am on KETAN n10 and initially, viper did not work. I installed magisk but that didn't fix it. nor the meefik busy box. So i decided to uninstall magisk and go back to superSU and it magically worked...
I unrooted from SuperSU itself like shown on the app's forum I believe. It rebooted my phone, I went into recovery first and then just flashed the latest magisk and made the switch :laugh:
SourPower said:
I unrooted from SuperSU itself like shown on the app's forum I believe. It rebooted my phone, I went into recovery first and then just flashed the latest magisk and made the switch :laugh:
Click to expand...
Click to collapse
So you just went into the SuperSU app and used the built in Unroot option, and when the phone rebooted, you went back into recovery and flashed the latest Magisk and did NOT flash a boot.img and everything worked fine? you have root with Magisk now instead of SU and you didnt get a bootloop at all??? (i really want to swap out SU for magisk in my sons LG G2, so he can play PoGo again lol) (His G2 is running CRdroid custom rom, I wonder if that effects the steps I'll need to take)
Can anyone offer me some guidance or assistance please and thank you?
JG420 said:
So you just went into the SuperSU app and used the built in Unroot option, and when the phone rebooted, you went back into recovery and flashed the latest Magisk and did NOT flash a boot.img and everything worked fine? you have root with Magisk now instead of SU and you didnt get a bootloop at all??? (i really want to swap out SU for magisk in my sons LG G2, so he can play PoGo again lol) (His G2 is running CRdroid custom rom, I wonder if that effects the steps I'll need to take)
Can anyone offer me some guidance or assistance please and thank you?
Click to expand...
Click to collapse
If there's a proper backup of the boot image for the SuperSU app's full unroot option to restore, then that process should work perfectly (I've done it on a few devices myself). It's when it can't properly restore the boot image you might have issues and you'll have to do it yourself.
Take a look in the Magisk Troubleshooting guide, under "Moving from another systemless root solution to MagiskSU".
The nuclear method might be, to just flash the full stock OOS zip (can flash in TWRP) which will unroot and restore the boot.img (and everything else!). Then immediately flash Magisk before rebooting (so have the Magisk zip on the phone before updating). This should fully remove SuperSU, install Magisk, and keep TWRP on the phone.
Seeing as the original poster is still on OOS 4.0.3, you may want to update, anyway!
JG420 said:
So you just went into the SuperSU app and used the built in Unroot option, and when the phone rebooted, you went back into recovery and flashed the latest Magisk and did NOT flash a boot.img and everything worked fine? you have root with Magisk now instead of SU and you didnt get a bootloop at all??? (i really want to swap out SU for magisk in my sons LG G2, so he can play PoGo again lol) (His G2 is running CRdroid custom rom, I wonder if that effects the steps I'll need to take)
Can anyone offer me some guidance or assistance please and thank you?
Click to expand...
Click to collapse
I've done this on my 3t but I do have a G3 coincidentally lol, but yes I unrooted from su, it restarted my phone, before booting back into the system I went in twrp right away and then flashed magisk.
There are two options given in the SuperSU app, one is clean up to switch to a different SU app and the other is to permanently unroot. Which option is better?
hypothrax said:
There are two options given in the SuperSU app, one is clean up to switch to a different SU app and the other is to permanently unroot. Which option is better?
Click to expand...
Click to collapse
I chose the Full Unroot option. Then flashed magisk. Worked perfectly.
Use the full unroot option. Catch here is that you might get dm-verity warning. It won't affect the phone in anyway but Android Pay might not work and you will see the warning for 5 seconds, everytime you restart the phone.
Thanks so much for ths thread. I am on Resurrection Remix OS and inititally installed SuperSU over Magisk (which came with the ROM). I decided that I wanted to use Magisk instead and followed the instructions in this thread and it worked a treat.

TWRP and root are gone

Question for those you you way smarter than I'll ever hope to be. I randomly lost root and TWRP on my 3T and I have no idea how this happened.
Quick (or not so quick) background - I was stock rooted OOS 4.1.6. I disabled AdAway for a bit yesterday to gain access to something it was blocking (done it many times) and when I re-enabled it my phone was stuck in a boot loop afterwards. Weird, but not concerning. I booted into TWRP and restored a backup. OOS 4.1.3 was my latest backup, so after successfully loading that up, I flashed the full 4.1.6 OTA and SuperSu as I've done before to update. Worked fine. Was adding my preferred mods via Substratum and Magisk and I messed up. Couldn't get Substratum to work properly and couldn't get Magisk to update to 13.1. I verified I had root, which I did. Went back to TWRP and reflashed 4.1.6 and SuperSU. When my phone was up and running again I didn't have root. Weird, so I tried again, still couldn't get SuperSU to flash properly. Got frustrated and figured I haven't had a clean install since getting the device in January. Every update I've flashed via TWRP has been dirty. So, factory reset, blah, blah, blah. Done it plenty of times with many devices. Flashed the OTA and SuperSu again, but noticed SuperSu failed. Rebooted recovery to try again, but it went to the stock recovery. My phone is working fine now, but I'm without root and I no longer have TWRP.
What might have caused this to happen? And how can I avoid it in the future? I know how to get it back (I'll do it after work) but it's frustrating.
What version of TWRP are you using? A few of the past versions have been having problems.
If you're already using Magisk anyways, just flash the Magisk zip and use that as your rooting solution. IIRC, the more recent versions of Magisk are no longer compatible with SuperSU anyways.
Anova's Origin said:
What version of TWRP are you using? A few of the past versions have been having problems.
If you're already using Magisk anyways, just flash the Magisk zip and use that as your rooting solution. IIRC, the more recent versions of Magisk are no longer compatible with SuperSU anyways.
Click to expand...
Click to collapse
I was using 3.0.4-1. Never had an issue before. But after I factory reset my phone and clean flashed the 4.1.6 update I ended up with the stock recovery. Unless I'm mistaken, I can't flash Magisk until I have TWRP again. I know how to get it back, I was more curious as to how this may have happened in the first place. What would have caused my root and custom recovery to disappear?
Rodeojones said:
I was using 3.0.4-1. Never had an issue before. But after I factory reset my phone and clean flashed the 4.1.6 update I ended up with the stock recovery. Unless I'm mistaken, I can't flash Magisk until I have TWRP again. I know how to get it back, I was more curious as to how this may have happened in the first place. What would have caused my root and custom recovery to disappear?
Click to expand...
Click to collapse
My mistake, I meant to ask SuperSU version, not TWRP. If SuperSU failed to root your phone after dirty flashing OOS (even if there was not error message), OOS will replace your recovery with the stock one.
Anova's Origin said:
My mistake, I meant to ask SuperSU version, not TWRP. If SuperSU failed to root your phone after dirty flashing OOS (even if there was not error message), OOS will replace your recovery with the stock one.
Click to expand...
Click to collapse
I was using version 2.8.2. Regardless, you answered my question as to how it happened in the first place, so thanks.

Miui 12 QFKEUXM

Received an update today , if i use standart ota updater via settings, does it overwrite the twrp and root stuff i have or it wont? Coz i never done this before, always using custom roms and now latest stock miui 11 with root.
You could flash the zip rom through the recovery, but keep in mind this. Let the phone boot with the new update, then go back to recovery (if you get the stock recovery, reflash it with fastboot), then flash magisk
So it is overwriting twrp and magisk even if i install it directly from twrp?
meezy5 said:
Received an update today , if i use standart ota updater via settings, does it overwrite the twrp and root stuff i have or it wont? Coz i never done this before, always using custom roms and now latest stock miui 11 with root.
Click to expand...
Click to collapse
You will loose Magisk/root but not Magisk Manager app and all Magisk data like modules, apps granted root, etc - once you re-root, everything will be there again.
I only suggest that you first un-hide Magisk Manager (if hidden for you), at the end you can hide it again
If you update via OTA, you will loose TWRP. If you don't want to flash TWRP again, then download the same full MIUI 12 zip package you got OTA notification for, and flash it from TWRP (without wiping, formatting or so), and immediately thereafter reboot first back to TWRP, and only then to MIUI 12
If you would like to update truly by OTA, you would have to flash the stock recovery back before starting the OTA.
Hence the way as described above, you save first on flashing stock recovery, and later on flashing TWRP back
Ok thanks so after twrp flash i have to reboot back to twrp , do i have to install force encrypt then to prevent overwriting twrp by miui or not?
meezy5 said:
Ok thanks so after twrp flash i have to reboot back to twrp , do i have to install force encrypt then to prevent overwriting twrp by miui or not?
Click to expand...
Click to collapse
See posts #933, #935-#937 in the TWRP thread:
https://forum.xda-developers.com/showpost.php?p=82945031&postcount=936

Categories

Resources