I have an HTC One M8 with ROM 4.16.1540.8 (5.0.1)
I'm trying to remove my SuperSU app so that i can downgrade it to a lower version(2.20) due to incompatibility with some of my apps (puzzle and dragons).
Bootloader is unlocked and it is s-on.
I have tried removing SuperSU through the app itself by using the reinstall, switch superuser app, and full unroot functions, but everytime I restarted the phone superSU would be back and in version 2.46. I also tried manually deleting the apk and su files in the bin and xbin folders in system using es file explorer but a restart just brought those back too.
Any help would be greatly appreciated. Thanks!
Find the flashable zip for the "older" version and flash in recovery. I would think that should do it.
Hi thanks for the reply.
I flashed superSU 2.23 from recovery, but i got stuck in bootloop. What should i do to fix it? Thanks!
Edit: flashed the updated su back in and got out of it. How do i do the downgrade without a bootloop?
ah46657 said:
Hi thanks for the reply.
I flashed superSU 2.23 from recovery, but i got stuck in bootloop. What should i do to fix it? Thanks!
Edit: flashed the updated su back in and got out of it. How do i do the downgrade without a bootloop?
Click to expand...
Click to collapse
Hmm, wouldn't expect that to happen. Obviously, since I would never intentionally bootloop someone!
Flash the stock ROM or restore stock nandroid. Then flash the desire SuperSU zip. That's the best I can think of.
Make a nandroid backup of your current setup (if you haven't already) to revert to "just in case".
how to unflash supersu zip
redpoint73 said:
Hmm, wouldn't expect that to happen. Obviously, since I would never intentionally bootloop someone!
Flash the stock ROM or restore stock nandroid. Then flash the desire SuperSU zip. That's the best I can think of.
Make a nandroid backup of your current setup (if you haven't already) to revert to "just in case".
Click to expand...
Click to collapse
recently i installed lineage os 14.1 in my device (rooted) and flashed supersu2.79 , but after updating it it 2.82, its showing SU BINARY OCCUPIED , so can i try downgrade supersu by flshing lower version,, if so how should i unflash previous supersu zip help
rajkumar1221 said:
recently i installed lineage os 14.1 in my device (rooted) and flashed supersu2.79 , but after updating it it 2.82, its showing SU BINARY OCCUPIED , so can i try downgrade supersu by flshing lower version,, if so how should i unflash previous supersu zip help
Click to expand...
Click to collapse
So you tried to flash 2.82? I don't think that is the proper way to update. Since you already have SuperSU installed, you should just be able to go into the SuperSU app, and update the binary from there. Or is that what led to the "binary occupied" error?
But back to the basic question, you can't "unflash" SuperSU. You can "dirty flash" Lineage (just wipe cache and dalvik, can keep user data), and that will put you back on the "unrooted" Lineage ROM. Then you should be able to flash SuperSU 2.82 via zip.
redpoint73 said:
So you tried to flash 2.82? I don't think that is the proper way to update. Since you already have SuperSU installed, you should just be able to go into the SuperSU app, and update the binary from there. Or is that what led to the "binary occupied" error?
But back to the basic question, you can't "unflash" SuperSU. You can "dirty flash" Lineage (just wipe cache and dalvik, can keep user data), and that will put you back on the "unrooted" Lineage ROM. Then you should be able to flash SuperSU 2.82 via zip.
Click to expand...
Click to collapse
i unrooted my device now,, should i have to "first root" it with official lineage os extra file addonsu arm and then should i have to flash supersu zip ?
rajkumar1221 said:
i unrooted my device now,, should i have to "first root" it with official lineage os extra file addonsu arm and then should i have to flash supersu zip ?
Click to expand...
Click to collapse
I don't personally use Lineage. I believe you will need to flash both of those, yes.
@redpoint73 , found this script made by osm0sis to "unSU". not sure if is relevant to earlier posts but thought maybe if you havent seen it yet would be worth looking at. maybe could help someone.?
http://forum.xda-developers.com/showthread.php?p=63615067
Related
Did everything correctly from start to finish, flashed the SuperSU and Busybox package, but still no root access.
Couldn't install binary on SuperSU so I tried superuser... begins to download the update but fails at request for root access.
Please HELP! TWRP installed fine, i've installed the 4.2 camera keyboard and clock through twrp and they all work fine...
Titaniumbackup says it has root, but I guess that isn't right.. lol
fastboot says *TAMPERED* and *UNLOCKED*.
I also apologize if this isn't the right place for this, I can't post in the development thread due to the fact that i have <10 posts
You sound rooted, if not you wouldn't have been able to install the 4.2 camera. download superuser and try that. if all is good. then try superSU.
Also reboot your phone and try to install superSU again. but you are rooted.
cmay227 said:
You sound rooted, if not you wouldn't have been able to install the 4.2 camera. download superuser and try that. if all is good. then try superSU.
Also reboot your phone and try to install superSU again. but you are rooted.
Click to expand...
Click to collapse
Sorry I meant to include that superuser failed to gain root access in the process of updating. SuperSU won't even update, just goes to installation failed.
theguitarhero94 said:
Sorry I meant to include that superuser failed to gain root access in the process of updating. SuperSU won't even update, just goes to installation failed.
Click to expand...
Click to collapse
are you trying to flash the binaries from the SU app? if so you can't do that with S-on you need to Download the Zip from the SU website and flash in recovery... watch one of the videos on root/ custom recovery they explain it in detail
DNA help
i installed what seems to be the first custom rom for the DNA
i unlocked the bootloader w/ htc dev and gained root w/ CWM
im having trouble posting to this thread as im a new user
http://forum.xda-developers.com/show...2014200&page=5
my device is hanging during boot animations at droid eye
how do i push the zip back to to SD card via command prompt if neccesay(if i wipe data)
also, im reluctant to perform factory reset from HTC bootloader menu w/ unlocked bootloader
BTW i did make a backup before rooting and before installing rom, but restore from it using CWM gives MD5 mismatch error
any advice?
bbeatz88 said:
i installed what seems to be the first custom rom for the DNA
i unlocked the bootloader w/ htc dev and gained root w/ CWM
im having trouble posting to this thread as im a new user
http://forum.xda-developers.com/show...2014200&page=5
my device is hanging during boot animations at droid eye
how do i push the zip back to to SD card via command prompt if neccesay(if i wipe data)
also, im reluctant to perform factory reset from HTC bootloader menu w/ unlocked bootloader
BTW i did make a backup before rooting and before installing rom, but restore from it using CWM gives MD5 mismatch error
any advice?
Click to expand...
Click to collapse
From what I understand if you are flashing the available custom ROM you must wipe system AND format data for it to install successfully. If you are able to get back into recovery just wipe those two and reflash the zip I believe you will be good to go after that.
two_cents said:
are you trying to flash the binaries from the SU app? if so you can't do that with S-on you need to Download the Zip from the SU website and flash in recovery... watch one of the videos on root/ custom recovery they explain it in detail
Click to expand...
Click to collapse
Finally got it to work. Fix was around xda. Had to install superuser and I then disable superuser in SuperSU and now the superuser updates correctly. Super su still asks me to update and fails but I guess I'll just use superuser... Weird also it reboots when the update fails sometimes
My problem is that I rooted the phone OK but randomly apps will say that they cannot get root. Like titanium backup will randomly do that, a reboot will usually fix it. Thoughts?
ilogik said:
My problem is that I rooted the phone OK but randomly apps will say that they cannot get root. Like titanium backup will randomly do that, a reboot will usually fix it. Thoughts?
Click to expand...
Click to collapse
I found that manually launching Superuser, then launching TiBu worked when TiBu wouldn't get root.
bbeatz88 said:
i installed what seems to be the first custom rom for the DNA
i unlocked the bootloader w/ htc dev and gained root w/ CWM
im having trouble posting to this thread as im a new user
http://forum.xda-developers.com/show...2014200&page=5
my device is hanging during boot animations at droid eye
how do i push the zip back to to SD card via command prompt if neccesay(if i wipe data)
also, im reluctant to perform factory reset from HTC bootloader menu w/ unlocked bootloader
BTW i did make a backup before rooting and before installing rom, but restore from it using CWM gives MD5 mismatch error
any advice?
Click to expand...
Click to collapse
md5 mismatch is because the backup is unrooted...
theguitarhero94 said:
md5 mismatch is because the backup is unrooted...
Click to expand...
Click to collapse
no... md5 mismatch is because the backup probably failed and the device rebooted before it completed. this is a known issue with both twrp and cwm recoveries on HTC DNA
Deuces said:
no... md5 mismatch is because the backup probably failed and the device rebooted before it completed. this is a known issue with both twrp and cwm recoveries on HTC DNA
Click to expand...
Click to collapse
gotcha, he didn't say anything about it not finishing, and I had the same issue a while back on my incredible and the backups definitely were completed... so i'm not really sure
OP, go see my post in this sub-forum about not being able to update the su binary. It should solve your issues.
Sent from my rooted and debloated Droid DNA.
I'm having the same issue, but disabling root in SuperSU doesn't work, and when I update the SU binary in SuperSU or Superuser my phone reboots.
Hey guys
I installed CM 13.0 (2016/01/02) on my i9300
Then installed GApps and everything was working fine
TWRP Recovery and SU were installed too
When I tried to open SU though (to enable root options) it said that SU Binary was not installed and that I had to manually re-root it
I used the CF-Auto-Root method but I still got the same message
Then I remember that I had installed a Kernel on my S4 i9500 when I had updated it to CM 12.1
So I googled and downloaded SiyahKernel v1.9.1
Now my phone is stuck on the boot-up. I get the S3 logo, then a purple eye and then a blank screen
I tried booting into recovery and reinstalling CM 13 but it just closes after displaying "Installing update"
Download mode re-rooting doesn't remove the kernel
Another website suggested I use another kernel but I wanted to get help before I did any more stupid things
Any help is appreciated
Joserin said:
Hey guys
I installed CM 13.0 (2016/01/02) on my i9300
Then installed GApps and everything was working fine
TWRP Recovery and SU were installed too
When I tried to open SU though (to enable root options) it said that SU Binary was not installed and that I had to manually re-root it
I used the CF-Auto-Root method but I still got the same message
Then I remember that I had installed a Kernel on my S4 i9500 when I had updated it to CM 12.1
So I googled and downloaded SiyahKernel v1.9.1
Now my phone is stuck on the boot-up. I get the S3 logo, then a purple eye and then a blank screen
I tried booting into recovery and reinstalling CM 13 but it just closes after displaying "Installing update"
Download mode re-rooting doesn't remove the kernel
Another website suggested I use another kernel but I wanted to get help before I did any more stupid things
Any help is appreciated
Click to expand...
Click to collapse
Looks like you totally screwed it up. Siyah on CM13?! you gotta be kidding me. Never ever install siyah again unless you're on stock ROM. Now I recommend 2 methods to you:
1. Backup efs and put it on your PC if you didn't back it up before. Full wipe your phone using twrp. Then extract the CM13 zip file on your PC then grab the boot.img file to an SD and put it on your phone and flash it using twrp. It will recover the stock CM13 kernel and then try to flash your CM13 zip. Better to download the updated ones. Be sure to use the latest twrp. And always use CM13 official root in developer options, trust me it's better.
2. If you couldn't flash CM13 again the only way I recommend is to flash stock using odin and then flash from the ground and bring your phone up.
JohnSmit268 said:
Looks like you totally screwed it up. Siyah on CM13?! you gotta be kidding me. Never ever install siyah again unless you're on stock ROM. Now I recommend 2 methods to you:
1. Backup efs and put it on your PC if you didn't back it up before. Full wipe your phone using twrp. Then extract the CM13 zip file on your PC then grab the boot.img file to an SD and put it on your phone and flash it using twrp. It will recover the stock CM13 kernel and then try to flash your CM13 zip. Better to download the updated ones. Be sure to use the latest twrp. And always use CM13 official root in developer options, trust me it's better.
2. If you couldn't flash CM13 again the only way I recommend is to flash stock using odin and then flash from the ground and bring your phone up.
Click to expand...
Click to collapse
It's okay I fixed it. I installed QS i9300 and then re-flashed CM and GApps. But the SuperSU is still bugged
A cursory reading said that CM is auto-rooted on stable versions and there is no stable version of CM 13 for the i9300 yet so I guess that might be the issue. The phone's working fine now, just no root access :3
Joserin said:
It's okay I fixed it. I installed QS i9300 and then re-flashed CM and GApps. But the SuperSU is still bugged
A cursory reading said that CM is auto-rooted on stable versions and there is no stable version of CM 13 for the i9300 yet so I guess that might be the issue. The phone's working fine now, just no root access :3
Click to expand...
Click to collapse
You read it wrong. It already have internal root. Go to setting--> about device and then tap build number constantly to enable developer settings. There you can find root access options. Turn it on for apps only or adn and apps and done.
Thank me if I helped you.:good:
JohnSmit268 said:
You read it wrong. It already have internal root. Go to setting--> about device and then tap build number constantly to enable developer settings. There you can find root access options. Turn it on for apps only or adn and apps and done.
Thank me if I helped you.:good:
Click to expand...
Click to collapse
I already did that.. Root Checker Basic says I do not have proper root access and the TWRP Manager tool also says I do not have root
It is really weird. I'm on i9300 official nightlies and have working root!
I rooted my S3 with this (by m0xx) https://download.chainfire.eu/229/CF-Root/CF-Auto-Root/CF-Auto-Root-m0-m0xx-gti9300.zip
I downloaded the 20160102 Nightly from this website https://download.cyanogenmod.org/?device=i9300
GApps from this website (ARM, 6.0, Stock) http://opengapps.org/
and TWRP via ODiN with https://twrp.me/devices/samsunggalaxys3internationalexynos.html (twrp-2.8.6.1-i9300.tar)
Idk if I did anything wrong or downloaded an older version... I know there's TWRP 2.8.7 but I dunno how to install the img file, I knew tar would be compatible with ODiN
Joserin said:
I rooted my S3 with this (by m0xx) https://download.chainfire.eu/229/CF-Root/CF-Auto-Root/CF-Auto-Root-m0-m0xx-gti9300.zip
I downloaded the 20160102 Nightly from this website https://download.cyanogenmod.org/?device=i9300
GApps from this website (ARM, 6.0, Stock) http://opengapps.org/
and TWRP via ODiN with https://twrp.me/devices/samsunggalaxys3internationalexynos.html (twrp-2.8.6.1-i9300.tar)
Idk if I did anything wrong or downloaded an older version... I know there's TWRP 2.8.7 but I dunno how to install the img file, I knew tar would be compatible with ODiN
Click to expand...
Click to collapse
If twrp offers to root then don't do that method. Flash superSU 2.4.6.zip and on reboot you will see the app logo in your drawer or if not there it will be above developer options in settings. Open and allow it to update binary.
kush2.0 said:
If twrp offers to root then don't do that method. Flash superSU 2.4.6.zip and on reboot you will see the app logo in your drawer or if not there it will be above developer options in settings. Open and allow it to update binary.
Click to expand...
Click to collapse
Already tried that. SU binary just doesn't update. I even downloaded the Update zip and flashed from recovery, it still asks to update the binary after reboot. There is no TWRP option to update the binary either, it directly goes to the normal method and fails everytime. Tried like 20 times probably
I'd say flash back to stock and start over. Installing siyah probably borked something.
shivadow said:
I'd say flash back to stock and start over. Installing siyah probably borked something.
Click to expand...
Click to collapse
The only reason I installed Siyah was because the binary wasn't installed. Multiple attempts to root didn't fix the issue.
Also I did flash stock ROM because after installing Siyah the phone wouldn't go past the S3 logo screen
What recovery version are you using then?? ??
---------- Post added at 04:02 PM ---------- Previous post was at 03:58 PM ----------
Joserin said:
The only reason I installed Siyah was because the binary wasn't installed. Multiple attempts to root didn't fix the issue.
Also I did flash stock ROM because after installing Siyah the phone wouldn't go past the S3 logo screen
Click to expand...
Click to collapse
I really dont thing a custom kernel for cm13 aosp roms exists for sgs3 gti9300
kush2.0 said:
What recovery version are you using then?? ??
Click to expand...
Click to collapse
kush2.0 said:
What recovery version are you using then?? ??
---------- Post added at 04:02 PM ---------- Previous post was at 03:58 PM ----------
I really dont thing a custom kernel for cm13 aosp roms exists for sgs3 gti9300
Click to expand...
Click to collapse
Yea I didn't know that before I installed it (it was 3 AM I was frustrated at SU)
Current TWRP version is 2.8.6.1
Joserin said:
Yea I didn't know that before I installed it (it was 3 AM I was frustrated at SU)
Current TWRP version is 2.8.6.1
Click to expand...
Click to collapse
Personally I would download twrp manager from play store if you havnt already got it. Flash/install twrp 2.8.7.X and boot into the newer twrp and flash superSU 2.4.6.zip. Try that before going back to stock.
kush2.0 said:
Personally I would download twrp manager from play store if you havnt already got it. Flash/install twrp 2.8.7.X and boot into the newer twrp and flash superSU 2.4.6.zip. Try that before going back to stock.
Click to expand...
Click to collapse
Uhm TWRP Manager doesn't work without root. Already tried that
@Joserin, you did your very best to make it complicated. Go back to firmware to get a clean base, as said several times before. Firmware doesn't mean a Touchwiz-based custom-ROM! Download it from sammobile.com and follow the instructions on downloadsite.
Joserin said:
Uhm TWRP Manager doesn't work without root. Already tried that
Click to expand...
Click to collapse
Yeah sorry you do need root access. Your probably better of doing what rp158
Said. Your twrp recovery isn't up to date enough to install a new cm13 based ROM.
rp158 said:
@Joserin, you did your very best to make it complicated. Go back to firmware to get a clean base, as said several times before. Firmware doesn't mean a Touchwiz-based custom-ROM! Download it from sammobile.com and follow the instructions on downloadsite.
Click to expand...
Click to collapse
Meh Id rather just let it be for what it is. It's my dad's phone and I just wanted him to have AdAway, he's not much of a tech-head.
Thanks people
No root access to S3 when upgraded to CM 13; affecting full access Ext SDcard
Before upgrading to CM 13 for my I 9300 (Int) I was on CM 11 and I had full root access on my device.
In fact I still have that recovery file which I backed up before upgrading to CM 13.
I was able to get root whenever I typed "SU" within the terminal window.
Then CM 13 became available for my device so I upgraded to it by following a few simple steps.
Most Everything works perfectly ...... except for one important problem !
I no longer have root access on my device !!!
Of course the first obvious fix was to try to enable root access by selecting it within the Developer Options to grant root access to Apps and ADB; but that didn't work. And I have tried numerous other possible solutions: reflashing SuperSU2.67, wiping everything clean and reinstalling CM 13 and Gapps from scratch, and other such recommendations but nothing has worked for this problem.
Some of my apps that need to write to the external SD card are unable to work but the apps work if I change the path to the internal storage.
Whenever I need to delete a file from my external SD using ES File Explorer it forces me to go to the CM File manager to approve the deletion.
I am unable to select "Root Access mode" within the CM File manager.
And my little "$" does not change to "#" when I type "SU" in the terminal window.
So all this is definitely a problem with us simply not having root access to our S3 devices.
I really would like to revive this topic because I am pretty sure that Joserin and I are not alone in this one.
The CM 13 is much nicer than the CM 11 and there must be a way to cross this hurdle.
Joserin, please let us know if by chance you have found a solution.
Thanks to all; awaiting your suggestions ......
kevin.a69 said:
Before upgrading to CM 13 for my I 9300 (Int) I was on CM 11 and I had full root access on my device.
In fact I still have that recovery file which I backed up before upgrading to CM 13.
I was able to get root whenever I typed "SU" within the terminal window.
Then CM 13 became available for my device so I upgraded to it by following a few simple steps.
Most Everything works perfectly ...... except for one important problem !
I no longer have root access on my device !!!
Of course the first obvious fix was to try to enable root access by selecting it within the Developer Options to grant root access to Apps and ADB; but that didn't work. And I have tried numerous other possible solutions: reflashing SuperSU2.67, wiping everything clean and reinstalling CM 13 and Gapps from scratch, and other such recommendations but nothing has worked for this problem.
Some of my apps that need to write to the external SD card are unable to work but the apps work if I change the path to the internal storage.
Whenever I need to delete a file from my external SD using ES File Explorer it forces me to go to the CM File manager to approve the deletion.
I am unable to select "Root Access mode" within the CM File manager.
And my little "$" does not change to "#" when I type "SU" in the terminal window.
So all this is definitely a problem with us simply not having root access to our S3 devices.
I really would like to revive this topic because I am pretty sure that Joserin and I are not alone in this one.
The CM 13 is much nicer than the CM 11 and there must be a way to cross this hurdle.
Joserin, please let us know if by chance you have found a solution.
Thanks to all; awaiting your suggestions ......
Click to expand...
Click to collapse
I flashed QSi9300KK on my phone (with kernel. I forget the name but it was the third option - not Agni or stock) and after that TWRP and then CM13. Everything's working fine now, even root access.
Remember do not pick the first two kernels in the installer, they didn't work correctly. Third one works like a charm.
Hi
I am running a CM13 Rom at the moment but want to go back to stock, I need to root it to restore apps via Titanium Backup.
As I already have TWRP installed can I just flash the stock rom via twrp then install SuperSU? or do I need to go back to stock and then create a custom image in the kitchen
mattwilkinson11 said:
Hi
I am running a CM13 Rom at the moment but want to go back to stock, I need to root it to restore apps via Titanium Backup.
As I already have TWRP installed can I just flash the stock rom via twrp then install SuperSU? or do I need to go back to stock and then create a custom image in the kitchen
Click to expand...
Click to collapse
If you have twrp, then flash the rom with it. Then supersu and allow modification to system partition. To keep twrp for future, open file manager in twrp and browse to system. Delete the file "recovery-from-boot.bak", after this your twrp will not be replaced with stock.
The only reason you need to cook custom boot image is to make sure that your twrp is not replaced with stock and at the same time without losing ota due to system modification.
WHen I swipe to install supersu it just reboots immediately and does not install it....
mattwilkinson11 said:
WHen I swipe to install supersu it just reboots immediately and does not install it....
Click to expand...
Click to collapse
Unlock your bootloader, flash twrp again. In mount, mount system and remove the "mount system as read only" check. then flash supersu.
" allow modification to system partition " how can i do this ?
if i install super su after restart will made problem ?
Is there a way to install the d003 ota update from TWRP on a rooted 5x KIW-L24 running B331? The updater pops up every time I boot up, but that method fails. Could it be because I used that script to remove stuff preinstalled on my phone?
bigman1 said:
Is there a way to install the d003 ota update from TWRP on a rooted 5x KIW-L24 running B331? The updater pops up every time I boot up, but that method fails. Could it be because I used that script to remove stuff preinstalled on my phone?
Click to expand...
Click to collapse
It would not update on mine with stock rom and twrp recovery. I think you need to go stock recovery and then update. You can reflash custom recovery and root once it's done. The D003 update definitely took care of my horrible GPS accuracy and fix.
cheers
I flashed the stock b331 recovery. Restored a b331 nandroid. Tried to ota, failed. Dowloaded the full image and did the dload folder reboot to stock recovery method. Fails out at 5%. Tried flashing the update.zip through twrp, fails. tried the newest b331 recovery from the repo, tried to dload folder again. fails... HELP!!!!! please?
bircky311 said:
I flashed the stock b331 recovery. Restored a b331 nandroid. Tried to ota, failed. Dowloaded the full image and did the dload folder reboot to stock recovery method. Fails out at 5%. Tried flashing the update.zip through twrp, fails. tried the newest b331 recovery from the repo, tried to dload folder again. fails... HELP!!!!! please?
Click to expand...
Click to collapse
I used the stock b331 plus stock recovery zip (July 31?) provided in the how to return to stock thread and did a factory reset before boot. It sounds like you still had a custom recovery. That will not work.
You need to be complete stock to be able to install an OTA. It's because it's a file patcher, if files are missing, or modified, it will fail.
That worked !!! Thanks a bunch. Nandroiding a fresh reset for future flubs.
Good !
bircky311 said:
That worked mooms! Thanks a bunch. Nandroiding a fresh reset for future flubs.
Click to expand...
Click to collapse
You are welcome
My SM-G900T is running Lollipop 5.1.1 rooted by installed twrp-3.0.2-2-klte + SuperSU using odin.
I am planning to update it to Marshmallow 6.0.1 (G900TUVS1GPK3) using odin. After the update, I believe the phone will be unrooted. Should I install twrp-3.0.2-2-klte + SuperSU again in order to bring back the root?
Yes, is the short answer. It's a pretty simple process, just flash the update, boot back to Download, flash TWRP, boot to recovery, then flash SU. However, after some experimentation, I'd recommend an extra step, especially if you're planning to run Xposed. After flashing the update, boot into the stock recovery and let the phone boot normally after the stock recovery does its thing. Without this step, Xposed breaks Wifi Calling, and my guess is there are other things which also break, since I get force-closed messages for a couple of T-Mobile processes if I don't let the stock recovery run. Once the phone has booted, just boot back to Download & then flash TWRP & install SU, and Xposed if you want it.
I'm not sure if you'll also need to wipe or not, all the updates I've done have been MM->MM. You can flash those without any wiping or restoring because they don't touch /data. I've found that switching between stock & modified MM roms without wiping appears to work but later causes severe performance problems. Between stock updates, I've had no problems even without wiping.
invisiblewave said:
Yes, is the short answer.
Click to expand...
Click to collapse
Thank you Invisiblewave. I understand that I need to reflash twrp, but since I installed SuperSU already and I think the update would not delete/uninstall it, if I flash SuperSu again, will there be a problem?
The update will remove your previous SuperSU install, so yes, you have to flash it again if you want root.
invisiblewave said:
After flashing the update, boot into the stock recovery and let the phone boot normally after the stock recovery does its thing. Without this step, Xposed breaks Wifi Calling, and my guess is there are other things which also break, since I get force-closed messages for a couple of T-Mobile processes if I don't let the stock recovery run. Once the phone has booted, just boot back to Download & then flash TWRP & install SU, and Xposed if you want it.
Click to expand...
Click to collapse
Thanks for the tips! I just did the same upgrade and wanted to make sure everything worked afterwards.
use this guide
https://forum.xda-developers.com/tm...l/root-how-to-root-sm-g900t-firmware-t3358190
That guide is incomplete. It needs an additional step after flashing the update to let the phone boot once normally, otherwise WiFi calling doesn't work. Flash update, reboot (stock recovery runs and does stuff), reboot to Download, then flash TWRP, SU, Xposed, etc.