Database Info

xoom 4.1.1 update root question

I applied the [UPDATE][JB]Stock Android 4.1.1 JRO03H, Root, via CWM Recovery (US Wi-Fi MZ604) to my mz604. I applied it on top of the previous stock rooted version. It appeared to update successfully. Most apps worked as required and no data loss.
However, I did notice that I do not have root access. Vodoo OTA reports that it is rooted but superuser permission not granted. Root Checker reports Status: not rooted. Superuser reports root access denied on all attempts since the update.
I have searched the forums for a similar situation but did not find any. I think it may only be a permissions issue. Does anyone have a suggestion on how this could be resolved? If it means wiping, I may just pass on the root for now since everything is working so well. I only rooted in the first place so that I could edit the wifi file for hotspot use from my phone (ad hoc mode). That edit is still intact. Otherwise the only thing I'm not able to use is the usb stick mount app.
Thanks in advance for any advice.

janegraves said:
I applied the [UPDATE][JB]Stock Android 4.1.1 JRO03H, Root, via CWM Recovery (US Wi-Fi MZ604) to my mz604. I applied it on top of the previous stock rooted version. It appeared to update successfully. Most apps worked as required and no data loss.
However, I did notice that I do not have root access. Vodoo OTA reports that it is rooted but superuser permission not granted. Root Checker reports Status: not rooted. Superuser reports root access denied on all attempts since the update.
I have searched the forums for a similar situation but did not find any. I think it may only be a permissions issue. Does anyone have a suggestion on how this could be resolved? If it means wiping, I may just pass on the root for now since everything is working so well. I only rooted in the first place so that I could edit the wifi file for hotspot use from my phone (ad hoc mode). That edit is still intact. Otherwise the only thing I'm not able to use is the usb stick mount app.
Thanks in advance for any advice.
Click to expand...
Click to collapse
Did you update superuser or change any settings in superuser yet? I tried this on Stachres build as well and had some issues.
For what its worth...the EOS nightlies are using SuperSU now and I haven't had any root issues with tibu or anttek FE.
Sent from my Xoom using xda premium

tincbtrar said:
Did you update superuser or change any settings in superuser yet? I tried this on Stachres build as well and had some issues.
For what its worth...the EOS nightlies are using SuperSU now and I haven't had any root issues with tibu or anttek FE.
Sent from my Xoom using xda premium
Click to expand...
Click to collapse
No. I didn't change anything, just ran the Stachres update file. It said completed successfully. I did get 26 app updates after reboot, and SuperUser may have been one of them, but I didn't pay attention. I'll try the SuperSU. Do I get it from the forum or the google app store?
UPDATE: I just installed SuperSU and when I open it it gets denied superuser access.

I have tried to use the Universal Root Method but No go.....Security Issue that gives Root has been patched in JB.....
Try this Method...... Its a lot of steps but It will work in the end...

Just flash the latest Super User Zip file after rooting using Universal Root and you'll gain root again. That worked for me. Download it from here http://androidsu.com/superuser/ I used the Superuser-3.1.3-arm-signed.zip
Sent from my SAMSUNG-SGH-I747 using xda premium

I tried that process. Still no root. I even did fix permissions, and shelled in to the root prompt and did the chown and chmod commands. They were successful, but when I reboot, still no root access. It is a mystery.
Is it possible to install the 4.0.4 update over the 4.1.1 without losing everything?

janegraves said:
I tried that process. Still no root. I even did fix permissions, and shelled in to the root prompt and did the chown and chmod commands. They were successful, but when I reboot, still no root access. It is a mystery.
Is it possible to install the 4.0.4 update over the 4.1.1 without losing everything?
Click to expand...
Click to collapse
this method has to flash rom, is there a way to root without flash rom. I flashed recovery, but can't choose zip from sd card, though i put su zip in a external sdcard.

Has anyone tried this method.
This would make things much easier. Universal Root/Flash superuser does this work....

Last chance to root

I have seen this discussed in several places, but I think a formal thread on the issue is in order.
Jelly Bean Has been updated with rock solid security and, so far, the only known way to root Jelly Bean at the moment is to unlock the bootloader and flash the su binary from a custom recovery. It is possible, however unlikely, that some dev will find a way to root jellybean that doesn't require unlocking.
If you wish to have root access with Jelly Bean without unlocking, it is highly reccomended that you root your tablet before updating.
Before updating, download the SuperSU app from the market, and let it update the su binary (Rootkeeper has failed to keep root with Superuser on the tf300). Make a backup withVoodoo OTA Rootkeeper. If there already exists a backup, delete it and backup again so that your backup is the SuperSU binary.

Do we have to uninstall Superuser and then install SuperSU or can both be installed?

BTrack said:
Do we have to uninstall Superuser and then install SuperSU or can both be installed?
Click to expand...
Click to collapse
Both can be installed. Just make sure SuperSU updates the binary so that it becomes the dominant app.

BTrack said:
Do we have to uninstall Superuser and then install SuperSU or can both be installed?
Click to expand...
Click to collapse
There's no upside to keeping Superuser if you have SuperSU installed. I deleted it to avoid any confusion personally.

My tf700 is due to arrive next Wednesday and I assume it will want to update when I start setting it up and rooting it, can I dismiss the update notice until I am ready?

maxal said:
My tf700 is due to arrive next Wednesday and I assume it will want to update when I start setting it up and rooting it, can I dismiss the update notice until I am ready?
Click to expand...
Click to collapse
Yes, you can postpone the update.
Sent from my ASUS Transformer Pad TF700T using XDA Premium HD app.

maxal said:
My tf700 is due to arrive next Wednesday and I assume it will want to update when I start setting it up and rooting it, can I dismiss the update notice until I am ready?
Click to expand...
Click to collapse
Also if it has pre .30 firmware you might consider unlocking it and creating the nvflash files for it if you ever plan on doing anything beyond rooting.

rightonred said:
I have seen this discussed in several places, but I think a formal thread on the issue is in order.
Jelly Bean Has been updated with rock solid security and, so far, the only known way to root Jelly Bean at the moment is to unlock the bootloader and flash the su binary from a custom recovery. It is possible, however unlikely, that some dev will find a way to root jellybean that doesn't require unlocking.
If you wish to have root access with Jelly Bean without unlocking, it is highly reccomended that you root your tablet before updating.
Before updating, download the SuperSU app from the market, and let it update the su binary (Rootkeeper has failed to keep root with Superuser on the tf300). Make a backup withVoodoo OTA Rootkeeper. If there already exists a backup, delete it and backup again so that your backup is the SuperSU binary.
Click to expand...
Click to collapse
I've lost root with .26 and .30. have always been able to re root with debugfs.
how can i maintain root this time? i use voodoo each time, and i have deleted su copy, then resaved it, that didn't work last time either.
i have superuser AND supersu installed. i can't uninstall superuser.
if i buy the pro key for supersu, will that save my root?

Man, I'd root if I could but I haven't had any luck. I run DebugFS and it seems to be only partially rooted. Sometimes the Superuser log shows the shell was given access. Root Explorer seems OK. But Superuser Update Fixer, Titanium, Root Checker, Terminal Emulator, and MyBackup all say they've been denied. I don't know what else to do. I've tried all the various fixes in the forums.

Also to note you need to be rooted to use the SuperSU app. I have always been rooted via debugfs method and decided I wanted to preserve come JB. I installed SuperSU and it asked for root permissions. After that I ran the binary updater, and then deleted superuser. THEN I went to OTARootkeeper and deleted old backup, and rebacked up. Now when programs ask for root access the SuperSU asks for root permissions so I know it's worked.

neo1738 said:
Also to note you need to be rooted to use the SuperSU app. I have always been rooted via debugfs method and decided I wanted to preserve come JB. I installed SuperSU and it asked for root permissions. After that I ran the binary updater, and then deleted superuser. THEN I went to OTARootkeeper and deleted old backup, and rebacked up. Now when programs ask for root access the SuperSU asks for root permissions so I know it's worked.
Click to expand...
Click to collapse
What is "the binary updater"? Last OTA, I had SuperSU and Voodoo OTA and lost root, so I'm a bit concerned there may be something I should have done that I missed. I currently have SuperSU (uninstalled old Superuser) and Voodoo OTA. All the boxes are checked on my Voodoo OTA dialog including "protected su backup".

redheadplantguy said:
I've lost root with .26 and .30. have always been able to re root with debugfs.
how can i maintain root this time? i use voodoo each time, and i have deleted su copy, then resaved it, that didn't work last time either.
i have superuser AND supersu installed. i can't uninstall superuser.
if i buy the pro key for supersu, will that save my root?
Click to expand...
Click to collapse
I can't see what the problem is. Make sure all of the checkboxes are checked in Voodoo and you should be good to go. superuser can be uninstalled using the root uninstaller app.
das0527 said:
Man, I'd root if I could but I haven't had any luck. I run DebugFS and it seems to be only partially rooted. Sometimes the Superuser log shows the shell was given access. Root Explorer seems OK. But Superuser Update Fixer, Titanium, Root Checker, Terminal Emulator, and MyBackup all say they've been denied. I don't know what else to do. I've tried all the various fixes in the forums.
Click to expand...
Click to collapse
Root with debugfs seems to be iffy. Try opening the superuser app, then switch out of it. If superuser is running in the background, the apps should be granted root access.

Also, to restore, you just:
1. Run SuperSU manually once
2. Run Voodoo OTA and restore
In that order, right?

Wonder if I'm good?
By default does OTA Rootkeeper keep the SuperSU or Superuser APK? I had SuperSU installed before installing and backing up root. Was curious if I am good to go, or if I will have to redo it?
rightonred said:
Before updating, download the SuperSU app from the market, and let it update the su binary (Rootkeeper has failed to keep root with Superuser on the tf300). Make a backup withVoodoo OTA Rootkeeper. If there already exists a backup, delete it and backup again so that your backup is the SuperSU binary.
Click to expand...
Click to collapse

droidhaxxor said:
By default does OTA Rootkeeper keep the SuperSU or Superuser APK? I had SuperSU installed before installing and backing up root. Was curious if I am good to go, or if I will have to redo it?
Click to expand...
Click to collapse
Whichever app manages root access at the time the backup is made, it backs up the binary for that app.If that binary is the supersu binary than you're good to go. The apk and the binary are separate files though. if you loose the app, you can simply reinstall it from the market. The binary requires root access to manage.

I just picked up my infinity today and want to root it but I usually keep it stock for a little does this mean if I'm on .30 I have to root before I take the job update?
Sent from my EVO using xda app-developers app

scataldo721 said:
I just picked up my infinity today and want to root it but I usually keep it stock for a little does this mean if I'm on .30 I have to root before I take the job update?
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
we just don't know if the root method will work after the jb update. we also don't know if a rootkeeper will even work but might as well root now as then you have 2 possible methods of obtaining root once you get the jb update.

fatpandas said:
we just don't know if the root method will work after the jb update. we also don't know if a rootkeeper will even work but might as well root now as then you have 2 possible methods of obtaining root once you get the jb update.
Click to expand...
Click to collapse
If I want to root and unlock should I do it now or after job?
Sent from my EVO using xda app-developers app

scataldo721 said:
If I want to root and unlock should I do it now or after job?
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
if you want to root, i would definitely do it now. mainly because the process if very easy and MOST people have had no problems with it. We're not sure what will happen once JB comes out though.
as for unlocking, i'm not too sure. only thing to be aware of would be that you won't get the OTA after unlocked so you would have to flash it manually. though at that point, you may just go flash some custom roms. just take those into consideration and see what is more important to you.

Bump since jb is out.

OTA Rootkeeper failed to protect my root after updating to JB from ICS

Twice I have updated from ICD to JB after getting root on ICS then saving my root with OTA.. however after I get into JB and launch OTA, there is no option to restore root.
Superuser is checked and so is /system supports root protection..
can i get some help? do i have to use SU Elite? :/

Beret67 said:
Twice I have updated from ICD to JB after getting root on ICS then saving my root with OTA.. however after I get into JB and launch OTA, there is no option to restore root.
Superuser is checked and so is /system supports root protection..
can i get some help? do i have to use SU Elite? :/
Click to expand...
Click to collapse
bump

Did you temp unroot before accepting the OTA? I don't think it works unless you do this step.

sbdags said:
Did you temp unroot before accepting the OTA? I don't think it works unless you do this step.
Click to expand...
Click to collapse
I have reverted and upgraded 3 times and never "temp unrooted"
If you have a file explorer look for: /system/usr/we-need-root/su-backup
If that exists and if the perms are correct you can regain root. There are guides (I don't know where) but they walk you through regaining root.

Try the instruction here
http://forum.xda-developers.com/showthread.php?t=1926147

I had OTA RK and it didn't work for me either, for some strange reason I never found out. I installed SuperSU from the Play Store and that worked. It's been a loooooooooooong time since I had stock ROM though, so YMMV.

MartyHulskemper said:
I had OTA RK and it didn't work for me either, for some strange reason I never found out. I installed SuperSU from the Play Store and that worked. It's been a loooooooooooong time since I had stock ROM though, so YMMV.
Click to expand...
Click to collapse
Yeah, several guides suggest that you might have "partial root" and that rmoving/reinstalling supersu restores full root access.

Okay so this is getting a little frustrating now..
I never did untemp before with OTA and so i tried that. I rooted at ICS, saved the root with OTA and then untemp rooted and then upgraded to JB.. however I think i got a partial root because when I look at the OTA app again in JB there was no option to restore root..
so i tried SU E and it saus SU binary not found, i had only checked OTA survival though but there was two apps under the allow list: Root Checker Basic and Superuser. After unckecking ota survival i couldnt recheck them though. So here i am stuck on JB without root again. I have not tried bluewr post yet which i am about to. Also i hope flash still works in jb

Beret67 said:
Okay so this is getting a little frustrating now..
I never did untemp before with OTA and so i tried that. I rooted at ICS, saved the root with OTA and then untemp rooted and then upgraded to JB.. however I think i got a partial root because when I look at the OTA app again in JB there was no option to restore root..
so i tried SU E and it saus SU binary not found, i had only checked OTA survival though but there was two apps under the allow list: Root Checker Basic and Superuser. After unckecking ota survival i couldnt recheck them though. So here i am stuck on JB without root again. I have not tried bluewr post yet which i am about to. Also i hope flash still works in jb
Click to expand...
Click to collapse
Flash will work, you just need to install it either in ICS, or after as a third party app, as Google play doesn't allow download, only update now.
And try either SuperSU or Super User only, not both, and before temp unroot, be sure to update the binary on which ever one you use.

bluewr said:
Flash will work, you just need to install it either in ICS, or after as a third party app, as Google play doesn't allow download, only update now.
And try either SuperSU or Super User only, not both, and before temp unroot, be sure to update the binary on which ever one you use.
Click to expand...
Click to collapse
Update binary? How exactly do i do that? thanks for advice

Beret67 said:
Update binary? How exactly do i do that? thanks for advice
Click to expand...
Click to collapse
The trick is once you rooted, you need to launch superuser, and it will auto update your binary, then install OTA root keeper., then save root, then temp unroot, then upgrade, then use ota to restore root.

http://forum.xda-developers.com/showthread.php?t=1241517&nocache=1
Original devs op instructs to temp unroot.

Oops... double post.
Where'd the delete option go?

rooting 4.3 verizon gs3

I tried to root my sch-i535 4.3 I had MTP click and usb debugging click...and it failed in odin...I have an image and link of what I was using to root the phone below and this is what the phone gave me in download mode...how can I fix this problem?
product name: sch-i535
custom binary download: no
current binary Samsung: official
QUALCOMM secureboot: enable
warranty bit:0
bootloader rp swrev: 1
secure check fail: recovery

eddieleed said:
I tried to root my sch-i535 4.3 I had MTP click and usb debugging click...and it failed in odin...I have an image and link of what I was using to root the phone below and this is what the phone gave me in download mode...how can I fix this problem?
product name: sch-i535
custom binary download: no
current binary Samsung: official
QUALCOMM secureboot: enable
warranty bit:0
bootloader rp swrev: 1
secure check fail: recovery
Click to expand...
Click to collapse
If you spend the time looking through the countless 4.3 ota threads, you would see that you can't root from 4.3 that way... safestrap is it and trying to Odin root will probably brick your device...
Check twice, flash once...
Sent from my SCH-I535 using xda premium

Do you have info on it???
Do you have info on how to do it with Safestrap?
Macrodroid said:
If you spend the time looking through the countless 4.3 ota threads, you would see that you can't root from 4.3 that way... safestrap is it and trying to Odin root will probably brick your device...
Check twice, flash once...
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse

Dadiekane said:
Do you have info on how to do it with Safestrap?
Click to expand...
Click to collapse
It's actually saferoot not safestrap and you can find info about it and a link for it in the OP of this thread:
http://forum.xda-developers.com/showthread.php?t=2575661

landshark68 said:
It's actually saferoot not safestrap and you can find info about it and a link for it in the OP of this thread:
http://forum.xda-developers.com/showthread.php?t=2575661
Click to expand...
Click to collapse
I'll look into this as well...I'll keep faith that thier is a root out there or will b out there.

works
landshark68 said:
It's actually saferoot not safestrap and you can find info about it and a link for it in the OP of this thread:
http://forum.xda-developers.com/showthread.php?t=2575661
Click to expand...
Click to collapse
thanks for the link..it worked...I am rooted on my Verizon 4.3 galaxy s3...can I install recovery (cwm or twrp)?

eddieleed said:
thanks for the link..it worked...I am rooted on my Verizon 4.3 galaxy s3...can I install recovery (cwm or twrp)?
Click to expand...
Click to collapse
No, you can only root.

landshark68 said:
No, you can only root.
Click to expand...
Click to collapse
That's what I have been reading. Ill be waiting for a custom recovery...thank you for your and comments. :good:

can any one help I safe rooted my sch-i535 verizon jellybean 4.3 ..added titanium back and pressed something wrong in titanium back up that soft brick my phone so now all it says is "unauthorized software take to you local verizon dealer" i've tried everything Ive read on this site and then some,still boots to yellow screen of death.this is not the first phone i've rooted been playing with modifying phones since the V3M came out.yes it was updated by OTA 4.3..everything in Odin fails, the knot counter is tripped but i don't buy my phones from Verizon anyway, tried hard reset still nothing.I can get into down load mode (power,vol down/home)and reset mode(power, vol up/home)Kies says unauthorized software .anything would be helpful.......deadcat

Saferoot working in s3 verizon
Sent from my SCH-I535 using xda app-developers app

deadcatsrule said:
can any one help I safe rooted my sch-i535 verizon jellybean 4.3 ..added titanium back and pressed something wrong in titanium back up that soft brick my phone so now all it says is "unauthorized software take to you local verizon dealer" i've tried everything Ive read on this site and then some,still boots to yellow screen of death.this is not the first phone i've rooted been playing with modifying phones since the V3M came out.yes it was updated by OTA 4.3..everything in Odin fails, the knot counter is tripped but i don't buy my phones from Verizon anyway, tried hard reset still nothing.I can get into down load mode (power,vol down/home)and reset mode(power, vol up/home)Kies says unauthorized software .anything would be helpful.......deadcat
Click to expand...
Click to collapse
As long as you can get to download mode, you can flash the stock 4.3 image back. When you start TB, pay attention. Do not restore ANY system apps and do not allow it to change the phone ID.
Sent from my SCH-I535 using xda app-developers app

5ft24 said:
As long as you can get to download mode, you can flash the stock 4.3 image back. When you start TB, pay attention. Do not restore ANY system apps and do not allow it to change the phone ID.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
I backd up my phone with TB and have it saved on my laptop but dont know what file to try to flash and I can not find a good stock 4.3 image that i can get to flash back to the phone.from what im reading the boot loader is locked keeping me from flashing anything .I've picked up another S3 to use for now so I can try to undo what ever i did wrong

deadcatsrule said:
I backd up my phone with TB and have it saved on my laptop but dont know what file to try to flash and I can not find a good stock 4.3 image that i can get to flash back to the phone.from what im reading the boot loader is locked keeping me from flashing anything .I've picked up another S3 to use for now so I can try to undo what ever i did wrong
Click to expand...
Click to collapse
Try this http://forum.xda-developers.com/showthread.php?t=2589314
post one is to download the official firmware 4.3
post 2 is how to fix and if you follow the link after you redirected there're more info how to recover your phone depended on how bad it is, but if you still get into download mode you should be ok.

buhohitr said:
Try this http://forum.xda-developers.com/showthread.php?t=2589314
post one is to download the official firmware 4.3
post 2 is how to fix and if you follow the link after you redirected there're more info how to recover your phone depended on how bad it is, but if you still get into download mode you should be ok.
Click to expand...
Click to collapse
UPDATE!! the link and info you posted for me fixed my phone first try..THANKS

Help, using Saferoot to root OTA 4.3, but Supersu binary update failed
Followed all the steps of Saferoot, everything else seems ok except SuperSU failed to update su binary.
The weird thing is that steps after SuperSU update (disabling KNOX and installing busybox) seem ok, and while SuperSU's popup window asking for SU binary needs to be updated, I can see in the grayed out back showing ADB Shell as the only apps gained root access.
More detail on SuperSU binary update, I chose update su normal way (instead CWM/TWRP) and next popup will report "Installation failed. Please reboot and try again." I tried many reboots and results were all the same.
From Terminal emulator, su -v command shows su is at version 3.1.1 (that's the latest already). If I cancel binary update, SuperSU app will exit too. I tried to install superuser app and use it to update su binary as someone suggested, it will fail in gaining root access.
Any way to overcome this issue and gain root on this OTA 4.3? Please help.
Phone Info:
Device Name: SCH-I535
Baseband Version: I535VRUCML1
Build Number: JSS15J.I535VRUCML1
Hardware Version: I535.10

nook2hd said:
Followed all the steps of Saferoot, everything else seems ok except SuperSU failed to update su binary.
The weird thing is that steps after SuperSU update (disabling KNOX and installing busybox) seem ok, and while SuperSU's popup window asking for SU binary needs to be updated, I can see in the grayed out back showing ADB Shell as the only apps gained root access.
More detail on SuperSU binary update, I chose update su normal way (instead CWM/TWRP) and next popup will report "Installation failed. Please reboot and try again." I tried many reboots and results were all the same.
From Terminal emulator, su -v command shows su is at version 3.1.1 (that's the latest already). If I cancel binary update, SuperSU app will exit too. I tried to install superuser app and use it to update su binary as someone suggested, it will fail in gaining root access.
Any way to overcome this issue and gain root on this OTA 4.3? Please help.
Phone Info:
Device Name: SCH-I535
Baseband Version: I535VRUCML1
Build Number: JSS15J.I535VRUCML1
Hardware Version: I535.10
Click to expand...
Click to collapse
In super su options do the clean up for market reinstall. Then download supersu from the market. It may not be worded like that but you will see what I mean. And make sure you uninstall superuser if you haven't already.

Still the same
ThePagel said:
In super su options do the clean up for market reinstall. Then download supersu from the market. It may not be worded like that but you will see what I mean. And make sure you uninstall superuser if you haven't already.
Click to expand...
Click to collapse
I cannot get into SuperSU options (or settings as in the snapshots). Neither Cancel nor Continue to the binary update popup will not stop me into SuperSU app.
Unistalled superuser, force stopped SuperSU and cleared data, then reinstalled SuperSU from play store. However, when open SuperSU, still asks for su binary update and fail.
Any other ways to get this to work?

nook2hd said:
Unistalled superuser, force stopped SuperSU and cleared data, then reinstalled SuperSU from play store. However, when open SuperSU, still asks for su binary update and fail.
Any other ways to get this to work?
Click to expand...
Click to collapse
Did you do the cleanup option in supersu?
---------- Post added at 11:16 AM ---------- Previous post was at 11:12 AM ----------
Labeled reinstall under supersu settings.

ThePagel said:
Did you do the cleanup option in supersu?
---------- Post added at 11:16 AM ---------- Previous post was at 11:12 AM ----------
Labeled reinstall under supersu settings.
Click to expand...
Click to collapse
I cannot get into SuperSu settings when there are popup windows, and when popup is gone, SuperSU app exits with it somehow. Is there a way to bypass those popups and allow me to click on the settings?

nook2hd said:
I cannot get into SuperSu settings when there are popup windows, and when popup is gone, SuperSU app exits with it somehow. Is there a way to bypass those popups and allow me to click on the settings?
Click to expand...
Click to collapse
I have no clue. If you can't find a solution you could always factory reset and start over.

Accidently updated SuperSU

So I accidentally updated SuperSu. My brain was operating on auto and I tried to update the binary as well, it failed. Now I've lost root and can't seem to get it back. I tried uninstalling SuperSu then re flashing it via ADB like I did when I first rooted, but it just won't work. Any thoughts?
Running a tmobile s7 on the MMB29M.G930TUVU3APG1 build.
Thanks!

Still no luck
Does anyone have any ideas? I used the removal tool in the super su app, then uninstalled it, then reinstalled via adb, butI still can't fix what I've done.
Teeklee said:
So I accidentally updated SuperSu. My brain was operating on auto and I tried to update the binary as well, it failed. Now I've lost root and can't seem to get it back. I tried uninstalling SuperSu then re flashing it via ADB like I did when I first rooted, but it just won't work. Any thoughts?
Running a tmobile s7 on the MMB29M.G930TUVU3APG1 build.
Thanks!
Click to expand...
Click to collapse

Teeklee said:
Does anyone have any ideas? I used the removal tool in the super su app, then uninstalled it, then reinstalled via adb, butI still can't fix what I've done.
Click to expand...
Click to collapse
Yes. Save anything. Factory reset and reroot your phone with this superuser. Do not update the binary. It's included with the fastboot. Just run the root.bat file after you flashed your AP file in download mode.