Has anyone unroot via SuperSU and managed to update via OTA ? Thanks
User @Mnemoch shared with me that he managed to do that. He did full unroot in SuperSU, rebooted a couple times, then tried sideloading and the OTA worked fine.
But do note that he rooted with chainfire autoroot, if your method was different you may have different results.
Related
So I was having issue with my note 3 ( bluetooth issues ) I upgraded to 4.4.2
AT&T sent me a new / refurb phone and it has 4.3 on it.
So Im curious on what you guys would do?
Upgrade to 4.4.2 and stick with all this stupid bloatware
or
Root, and rom it?
If that latter, does anyone have any links to do that ( I used to do it with my S2, S3 and S4 )
thank s
Root it. It's not worth the grief to upgrade it to 4.4.2.
You can root it and use safestrap to install custom ROMs, or just enjoy the stock setup with root.
Sent from my locked down Note 3 via the tapatalk app
ROOT AND ROM it!
I was ROOTED and ROM'd, but I got bit by the OTA Upgrade bug... I went through all the hassle of downgrading, unrooting, resetting, then upgrading.
Now I've got the fresh new bloated OTA official 4.4.2 and NO ROOT.
Should I use Kingo? is that still safe for the Note 3 on 4.3?
well I rooted it with Kingo, However I'm having issues with SafeStrap.
Downloaded the APK and Busybox.
Installed SafeStrap and installed the recovery. When I manually reboot or reboot into the recovery via the app, it just boot as normal
Root it!
I rooted with Kingo, no problems, the first day I got the Note 3 and took the Nb4 update. I was so lucky to catch the KK update and froze it mid-download with ttb. I am so glad!! I wouldn't be able to use this thing without root. I have installed safestrap and roms without issue. (staying on 4.3 roms mind you)
scojosmac said:
well I rooted it with Kingo, However I'm having issues with SafeStrap.
Downloaded the APK and Busybox.
Installed SafeStrap and installed the recovery. When I manually reboot or reboot into the recovery via the app, it just boot as normal
Click to expand...
Click to collapse
try uninstalling ss then install it again, make sure it is 3.71 not 3.72. 3.71 doesnt need busybox if im not mistaken.
scojosmac said:
well I rooted it with Kingo, However I'm having issues with SafeStrap.
Downloaded the APK and Busybox.
Installed SafeStrap and installed the recovery. When I manually reboot or reboot into the recovery via the app, it just boot as normal
Click to expand...
Click to collapse
I am going to use Kingo tomorrow as well I think. How does get root? Will it have superuser on it after it roots or do you have to put it on the phone yourself?
Thanks.
Krunk83 said:
I am going to use Kingo tomorrow as well I think. How does get root? Will it have superuser on it after it roots or do you have to put it on the phone yourself?
Thanks.
Click to expand...
Click to collapse
kingo installs supersu. when supersu installs, click on it and choose disable knox, presto!
i upgraded to nc2 and want to downgrade to mj5 now.. any method ?
anuragsodhi1 said:
i upgraded to nc2 and want to downgrade to mj5 now.. any method ?
Click to expand...
Click to collapse
no downgrades from official ota nc2 sir, no root method and no unlocked bootloader.
scojosmac said:
well I rooted it with Kingo, However I'm having issues with SafeStrap.
Downloaded the APK and Busybox.
Installed SafeStrap and installed the recovery. When I manually reboot or reboot into the recovery via the app, it just boot as normal
Click to expand...
Click to collapse
Did you try rebooting into recovery via a power menu? That is what the tutorial says it should do. Hold power to bring up the menu and it should then have an option to reboot into recovery. I am going to try safestrap too I think.
Last night I went to open Titanium Backup and was notified that I didn't have root. I've been rooted with ioroot for over a year now without issues. Root Checker app confirmes root was lost. SuperSu gave binaries error.
HOWEVER, in About Phone > System Status it was still showing as 'Rooted'. I'm still on 4.2.2 / VS98011A. All I've done is update the same ol' apps I've had for months.
What gives? Anybody have any ideas why this would happen?
The only thing I can think of is when SuperSu updated recently it asked to use TWRP (instead of the 'normal' method) to run a script to update binaries which I obliged. It seemed to struggle with that.
Anyway, I did use TowelRoot this time since I was too lazy to refresh my memory on the ioroot process. It worked fine however I've had a few random locks and a random reboot. I never had those issues before.
Any insight would be appreciated.
newuzer1 said:
Last night I went to open Titanium Backup and was notified that I didn't have root. I've been rooted with ioroot for over a year now without issues. Root Checker app confirmes root was lost. SuperSu gave binaries error.
HOWEVER, in About Phone > System Status it was still showing as 'Rooted'. I'm still on 4.2.2 / VS98011A. All I've done is update the same ol' apps I've had for months.
What gives? Anybody have any ideas why this would happen?
The only thing I can think of is when SuperSu updated recently it asked to use TWRP (instead of the 'normal' method) to run a script to update binaries which I obliged. It seemed to struggle with that.
Anyway, I did use TowelRoot this time since I was too lazy to refresh my memory on the ioroot process. It worked fine however I've had a few random locks and a random reboot. I never had those issues before.
Any insight would be appreciated.
Click to expand...
Click to collapse
Do you have TWRP installed? If so try to get it to reflash the binaries again.
mjones73 said:
Do you have TWRP installed? If so try to get it to reflash the binaries again.
Click to expand...
Click to collapse
After rerooting with towelroot, i uninstalled SuperSu. Then reinstalled SuperSu and choose install binaries via 'normal' method. That appears to have worked fine.
My question relates to why did I lose su/root functionality in the first place? Is this known to happen sometimes with app updates, (not just system/os/ota updates)? That has me concerned.
newuzer1 said:
After rerooting with towelroot, i uninstalled SuperSu. Then reinstalled SuperSu and choose install binaries via 'normal' method. That appears to have worked fine.
My question relates to why did I lose su/root functionality in the first place? Is this known to happen sometimes with app updates, (not just system/os/ota updates)? That has me concerned.
Click to expand...
Click to collapse
I would assume not installing the SuperSU binary updates correctly broke SuperSU. You didn't lose root per say, you broke SuperSU which apps need to be able to run as root.
SM-T700 UK version stock 5.0.2
1. Root using Kingroot 4.5
2. ONLY now !!! install and run Super-Sume
3. Update SuperSu binaries
That's all : you have root, SuperSu and Knox still "O" and Kingroot it's gone...
Would people please post the full build version of the firmware they have success or failure with, so others are aware of which ones work.
has this method been verified by other users?
Share your experience please!
It's brand new...
Verified by myself
Have you maintained root after reboot?
ashyx said:
Already tried it, v4.5 is posted in my kingroot thread, didn't work on lollipop for t805.
Neither did supersu me, binary always fails to update, once it did manage after several tries, but root is lost after reboot.
Supersu me is just the same script as posted in the kingroot thread. Root always lost after reboot.
Have you maintained root after reboot?
Click to expand...
Click to collapse
Just following your thread, messing with Kingroot 4.5 (from your tread) I obtained root.
Also someone there suggesting SuperSume to remove Kingroot.
I use it and that's it
Yes the root it's permanent
stefan.pilsu said:
Just following your thread, messing with Kingroot 4.5 (from your tread) I obtained root.
Also someone there suggesting SuperSume to remove Kingroot.
I use it and that's it
Yes the root it's permanent
Click to expand...
Click to collapse
Can you then install SuperSu or do you need to keep the SuperSume?
Anyone else confirm this method ?
louiscar said:
Can you then install SuperSu or do you need to keep the SuperSume?
Anyone else confirm this method ?
Click to expand...
Click to collapse
Super-Sume install SuperSu
Update binaries and done
I waiting also others to confirm
stefan.pilsu said:
I waiting also others to confirm
Click to expand...
Click to collapse
Ok Thanks for putting this up, if it's reliable it will save a lot time for many.
..guys try install first busy box while with kingo root, then install supersu. update binary. if successful,
..uninstall kingoroot . reboot supersu rules!!!!!!
angelshie said:
..guys try install first busy box while with kingo root, then install supersu. update binary. if successful,
..uninstall kingoroot . reboot supersu rules!!!!!!
Click to expand...
Click to collapse
Super_Sume make all this "work" with one click !
Ok guys, thanks for confirming, Sweet
Thanks for the tip. This worked perfectly. I installed Kingroot 4.5. When Kingroot runs scroll down and press "Try it" and it rooted. I then immediately installed Busybox from the Google Play store and ran the smart installer. After a successful install of Busybox, I then installed Super-Sume from the Play store. I ran Super-Sume and it installed Super SU and removed Kingroot. After that, I opened Super SU and allowed it to update the binary. Rebooted. I checked root with Root Checker app and checked Knox with an app called Knox Status on the Play store. Root is still active and Knox is still at "0". I powered off, then restarted again. Root has stayed.
I did this on a brand new US region SM-T700 pulled straight from the box and updated to Lolilipop from OTA.
System Version:
SM-T700
LRX22G.T700XXU1BOE3
*ROOT WORKING !! SMT-700 OTA 'lollipop'
Confirmed working on Lollipop NEE-T805XXU1BOE3 firmware.
Reflashed back to complete stock then ran Kingroot v4.5, root succeeded first time.
Ran Supersu me to remove Kingroot and install Supersu then updated the su binary.
Rebooted then checked root status. Full root access still available.
No need to install busybox as Supersu me already installs busy box.
Looks like we have a winner, no need to downgrade to Kitkat any more. :good:
Hopefully now T807/707 users can now get root.
Credits go to the devs of Kingroot, Chainfire and Supersu me.
ashyx said:
Confirmed working on Lollipop T805XXU1BOE3 firmware.
Reflashed back to complete stock then ran Kingroot v4.5, root succeeded first time.
Ran Supersu me to remove Kingroot and install Supersu then updated the su binary.
Rebooted then checked root status. Full root access still available.
No need to install busybox as Supersu me already installs busy box.
Looks like we have a winner, no need to downgrade to Kitkat any more. :good:
Hopefully now T807/707 users can now get root.
Credits got to the devs of Kingroot, Chainfire and Supersu me.
Click to expand...
Click to collapse
I've told you ...
ashyx said:
Confirmed working on Lollipop T805XXU1BOE3 firmware.
Reflashed back to complete stock then ran Kingroot v4.5, root succeeded first time.
Ran Supersu me to remove Kingroot and install Supersu then updated the su binary.
Rebooted then checked root status. Full root access still available.
No need to install busybox as Supersu me already installs busy box.
Looks like we have a winner, no need to downgrade to Kitkat any more. :good:
Hopefully now T807/707 users can now get root.
Credits go to the devs of Kingroot, Chainfire and Supersu me.
Click to expand...
Click to collapse
It does not appear to work on T707a with 5.0.2.
Maybe ashyx could help.
What exactly didn't work for you ?
stefan.pilsu said:
I've told you ...
Click to expand...
Click to collapse
Do you think this is likely to work for KitKat ANL1? I already downgraded as part of Ashyx's tutorial to ANF7.
My only reservation to going to Lollipop is that I want to use the Xposed framework which I think is still in it's infancy for 5.x or still not compatible.
So before this my options are to keep the original Kitkat by Flashfire - ANL1 or go directly to Lollipop. For the latter I could just get the OTA and do this method now. But not sure if I go to ANL1 kingroot will work as easily
If not I'll continue in the normal way I guess.
Once you have root with Kingroot install Super Sume and run it.
Kingroot 4.5 from ashyxs tread works for me.
Super-Sume just install busybox, SuperSu and get rid of Kingroot.
Why not use Flashfire to install whatever you want: KK or L ?
I rooted my phone using KingRoot. but when I try SuperSu Me it takes KingRoot away however despite using the updated google play store SuperSU from chainfire it can't update the binaries at all. One time it said there wasn't any installed and couldn't install any. I haven't unlocked my boot loader or recovery because I don't have a computer. Any help?
Edit: I'm running stock 4.4.2 using the latest Google play store version.
I have tried to use both update methods, despite not having a custom recovery. When using the normal method I just get installation failed and an okay an a reboot option. Ive tried rebooting but it doesn't help. I can't seem to use supersu me to transfer root control to super su. I also DO have Xposed installed but Im not sure if that's the cause. I do regularly use it. I may try to uninstall and I'll post an update on that.
I just picked up a used T817T yesterday. I was able to root it with Kingroot. I then found out that I lose root after a reboot. Even worse, without enabling the developer options and enabling the OEM unlock, it would no longer boot. I had to reflash the stock ROM with ODIN to recover.
I purchased and installed SuperSu Me-Pro and that replaced the Kingroot SU with SuperSu. Now I can reboot without losing root.
I'm being prompted to install an update T817TUVS2APB1/T817TTMB2APB1/T817TUVS2APB1. If I install this update, will I lose root? If I install it, can I still root with other methods?
I still have the stock recovery.
I'm currently on T817TUVS2AOL1.
I decided to roll the dice and try the update. I got a message that the software on my device was altered in an unapproved way and that it would not update. At least the nagging icon on the top of the screen is now gone.
DonS said:
I decided to roll the dice and try the update. I got a message that the software on my device was altered in an unapproved way and that it would not update. At least the nagging icon on the top of the screen is now gone.
Click to expand...
Click to collapse
Install it with Flashfire.