I bought a used XT925 today. While the previous owner did go to some trouble to clean it, it still has a bunch of apps and some settings that I really don't want. Also, as a privacy paranoiac, I'm worried that there may be something malicious (however slight the possibility).
The device is rooted and running JB 4.1.2. I would love to factory reset it but having read a few reports of people losing root or worse (here, here, here and here, to list just a few) that plan seems ill-advised.
I've been toying with trying to script some kind of fs compare against a fs from a rom, but I'm not sure if this is even feasible. So far the only other thing I can think of to do is uninstall all the apps and manually sift through and delete all the other junk in the filesystem.
Does anyone have any suggestions on returning my device to the most "virgin" state possible while retaining root?
triplexdoubledadevelopers said:
I bought a used XT925 today. While the previous owner did go to some trouble to clean it, it still has a bunch of apps and some settings that I really don't want. Also, as a privacy paranoiac, I'm worried that there may be something malicious (however slight the possibility).
The device is rooted and running JB 4.1.2. I would love to factory reset it but having read a few reports of people losing root or worse (here, here, here and here, to list just a few) that plan seems ill-advised.
I've been toying with trying to script some kind of fs compare against a fs from a rom, but I'm not sure if this is even feasible. So far the only other thing I can think of to do is uninstall all the apps and manually sift through and delete all the other junk in the filesystem.
Does anyone have any suggestions on returning my device to the most "virgin" state possible while retaining root?
Click to expand...
Click to collapse
Simplest way is to use RSD Lite to send your device back to stock 4.1.2 -- then you can use the recently posted root method to gain root back. It should take < 15 minutes to do, most of that spent flashing with RSDLite. It'll actually take longer to download all the ADB drivers, Moto drivers, etc -- if you don't have them already.
triplexdoubledadevelopers said:
I bought a used XT925 today. While the previous owner did go to some trouble to clean it, it still has a bunch of apps and some settings that I really don't want. Also, as a privacy paranoiac, I'm worried that there may be something malicious (however slight the possibility).
The device is rooted and running JB 4.1.2. I would love to factory reset it but having read a few reports of people losing root or worse (here, here, here and here, to list just a few) that plan seems ill-advised.
I've been toying with trying to script some kind of fs compare against a fs from a rom, but I'm not sure if this is even feasible. So far the only other thing I can think of to do is uninstall all the apps and manually sift through and delete all the other junk in the filesystem.
Does anyone have any suggestions on returning my device to the most "virgin" state possible while retaining root?
Click to expand...
Click to collapse
Whats up,
Cpudan80 is right, your best bet is to flash stock 4.1.2, and to reroot. And it does take about 15 minutes if you don't already have drivers and stuff, but I can help you out, by linking you to my utility, which essentially does the heavy lifting of finding all of the programs and stuff, and puts it together into one convenient package.
Find it here: http://forum.xda-developers.com/showthread.php?t=2241788
Cpudan80 said:
Simplest way is to use RSD Lite to send your device back to stock 4.1.2 -- then you can use the recently posted root method to gain root back.
Click to expand...
Click to collapse
Mr.Parkinson said:
Cpudan80 is right, your best bet is to flash stock 4.1.2, and to reroot.
Click to expand...
Click to collapse
Thanks for the replies! Would you link me to that root method, Cpudan80? All of the root methods I've been able to find say that you must flash 4.0 or CWM first in order to root, then protect root and upgrade to JB again. Is there a new better way which doesn't require downgrading?
triplexdoubledadevelopers said:
Thanks for the replies! Would you link me to that root method, Cpudan80? All of the root methods I've been able to find say that you must flash 4.0 or CWM first in order to root, then protect root and upgrade to JB again. Is there a new better way which doesn't require downgrading?
Click to expand...
Click to collapse
There's a thread on here somewhere -- but here's the thread I followed (after using RSDLite to go back to clean 4.1.2). No hard steps at all, just run a bat file - press enter and viola - you're rooted.
http://www.droidrzr.com/index.php/topic/15208-root-motochopper-yet-another-android-root-exploit/
Cpudan80 said:
There's a thread on here somewhere -- but here's the thread I followed (after using RSDLite to go back to clean 4.1.2). No hard steps at all, just run a bat file - press enter and viola - you're rooted.
Click to expand...
Click to collapse
Amazing, thanks! I had seen that exploit at one point when I was considering getting an earlier RAZR version and was looking into how easy it was to root it. I thought that exploit didn't work with the XT925 since there was no link to it in the forum (and searches only revealed many tales of failed root attempts and downgrades). Thanks again!
The goal: Get my sluggish phone (Razr Maxx HD, JB 4.1.2, currently 9.16.6.XT926.Verizon.en.US, rooted, bootloader locked) to be less sluggish.
The proposed method: Wipe phone and start over.
The "problem": Because I am rooted and want to stay that way, I am aware that I can't just do a factory reset. I believe that I need to unroot first, then wipe, then reroot. But there are many more possible methods to do this than there were before and I'm having trouble figuring out which might be the best method for me (or which will even work, at all).
Background: If I had just blindly done what I did the last time I wiped (I think I was starting from ICS 0.7.2 last time, not JB), I would have backed up everything, used DROID_RAZR_HD_Utility1.10 which I have from before (dates appear to be 1/28/2013) to go back to 0.6.25.X926., and, using the zip files I have from before, go from 0.6.25 to 0.7.2 to 9.1.41 to 9.16.6. (I was never able to successfully take OTA updates). Like this: http://forum.xda-developers.com/showthread.php?t=2024423 BUT, now that I'm on JB, it's not clear to me that I can even do this. One post is telling me that if I'm on 9.16.6, I should NOT use Droid Razr HD Utility 1.10. http://forum.xda-developers.com/showthread.php?p=33610625#post33610625 and when I found the thread for the 1.21 utility, it also says no 9.16.6.
I've been wandering around the relevant posts that are linked from here: http://forum.xda-developers.com/showthread.php?t=2247250
but for whatever reason, this is just making my head spin. I'm more confused about what I can and cannot do, than I was before I started. I think too many OTA versions have passed me by... I was happy with the way things were working so I just didn't care about updates, KitKat, etc. I don't have a good feel for how many versions there are between 9.16.6 and current.
My actual question: I think I could really use some help narrowing down my options. Do I have any options at all? If so, can anyone suggest what my realistic options actually are? I don't care if I end up in JB or KitKat at the end; I do want to be able to restore some of the data from some of my apps using Titanium Backup and/or MyBackup Pro; and I want to be rooted when I am done. Any suggestions would be greatly appreciated.
Thank you, dlc
dlc2001 said:
The goal: Get my sluggish phone (Razr Maxx HD, JB 4.1.2, currently 9.16.6.XT926.Verizon.en.US, rooted, bootloader locked) to be less sluggish.
The proposed method: Wipe phone and start over.
The "problem": Because I am rooted and want to stay that way, I am aware that I can't just do a factory reset. I believe that I need to unroot first, then wipe, then reroot. But there are many more possible methods to do this than there were before and I'm having trouble figuring out which might be the best method for me (or which will even work, at all).
Background: If I had just blindly done what I did the last time I wiped (I think I was starting from ICS 0.7.2 last time, not JB), I would have backed up everything, used DROID_RAZR_HD_Utility1.10 which I have from before (dates appear to be 1/28/2013) to go back to 0.6.25.X926., and, using the zip files I have from before, go from 0.6.25 to 0.7.2 to 9.1.41 to 9.16.6. (I was never able to successfully take OTA updates). Like this: http://forum.xda-developers.com/showthread.php?t=2024423 BUT, now that I'm on JB, it's not clear to me that I can even do this. One post is telling me that if I'm on 9.16.6, I should NOT use Droid Razr HD Utility 1.10. http://forum.xda-developers.com/showthread.php?p=33610625#post33610625 and when I found the thread for the 1.21 utility, it also says no 9.16.6.
I've been wandering around the relevant posts that are linked from here: http://forum.xda-developers.com/showthread.php?t=2247250
but for whatever reason, this is just making my head spin. I'm more confused about what I can and cannot do, than I was before I started. I think too many OTA versions have passed me by... I was happy with the way things were working so I just didn't care about updates, KitKat, etc. I don't have a good feel for how many versions there are between 9.16.6 and current.
My actual question: I think I could really use some help narrowing down my options. Do I have any options at all? If so, can anyone suggest what my realistic options actually are? I don't care if I end up in JB or KitKat at the end; I do want to be able to restore some of the data from some of my apps using Titanium Backup and/or MyBackup Pro; and I want to be rooted when I am done. Any suggestions would be greatly appreciated.
Thank you, dlc
Click to expand...
Click to collapse
to get rid of the slowness of the phone i recommend going to a lolipop rom , LP has to be the quickest my phone has ran... ever.
-step 1 use rsd lite to flash [4.4.2] 183.46.10 fxz (make sure it ends with a 10 not a 14 or 15 or you wont be able to unlock bootloader)
http://www.droidrzr.com/index.php/topic/45494-fxz-442-1834610/
-step 2 root and unlock use TR.apk (root)and motopocalypse.apk (bootloader unlock)
http://forum.xda-developers.com/showthread.php?t=2783912
-step 3 use ADB fastboot to Flash custom recovery, i personally use twrp there are others you can use if you decide to do the research
http://www.droidrzr.com/index.php/topic/51883-recoverytwrp-2810-11-01-14/
-step 4 flash LP custom rom, i use blisspop, it seems to have the most updates at the moment . it has really impressed me
http://www.droidrzr.com/index.php/topic/60153-rom502lollipopmsm8960-kkbl-blisspop-official/
that rom comes with supersu built in so you will have root. if your reason for having root is to have exposed, it doesnt work on lolipop so stop at sstep 3 and either flash a KK custom rom or just flash supersu which will give you root on stock kitkat
OK, I will spend a little more time absorbing/reading and then I'll give it a shot, thanks muchly. I want to do some backups just in case, so it'll take a while...
Couple of followup questions based on the reading I've done so far from the links you provided, just so I know what I'm doing before I do it:
1. I think I get Steps 1 and 2. After Step 2 I am rooted and on stock KK, correct? So if I stop there do I still need to "flash supersu" per your comment at the end? Does the root in step 2 put supersu in my apps, and if not can I not just install it from google play?
2. Seems like I can use the Step 1 method to flash back to JB (or any other FXZ I can find) if I want. If I do that, is there any way to root JB, or is this trip I'm about to take, a one-way trip? Just to clarify, JB hasn't always been slow for me... it's just slowed down recently. Not saying I want to go back to JB for sure, but I like to know what options I am closing off when I move forward, and reviews of KitKat are not universally splendid.... I hear you about the custom ROM but for various work-related reasons I may be better off staying stock (well, stock + root) for a while at least.
Again, thank you for your help.
dlc2001 said:
OK, I will spend a little more time absorbing/reading and then I'll give it a shot, thanks muchly. I want to do some backups just in case, so it'll take a while...
Couple of followup questions based on the reading I've done so far from the links you provided, just so I know what I'm doing before I do it:
1. I think I get Steps 1 and 2. After Step 2 I am rooted and on stock KK, correct? So if I stop there do I still need to "flash supersu" per your comment at the end? Does the root in step 2 put supersu in my apps, and if not can I not just install it from google play?
2. Seems like I can use the Step 1 method to flash back to JB (or any other FXZ I can find) if I want. If I do that, is there any way to root JB, or is this trip I'm about to take, a one-way trip? Just to clarify, JB hasn't always been slow for me... it's just slowed down recently. Not saying I want to go back to JB for sure, but I like to know what options I am closing off when I move forward, and reviews of KitKat are not universally splendid.... I hear you about the custom ROM but for various work-related reasons I may be better off staying stock (well, stock + root) for a while at least.
Again, thank you for your help.
Click to expand...
Click to collapse
yes you can install it from playstore, but once your bootloader is unlocked you can always root by flashing in custom recovery. you dont need exploits anymore
All done, worked great!
So I have a Sprint Galaxy S6. Until last week, I was running Android 5.1. I actively avoided upgrading to 6.0.1 because things are getting more difficult with the use of certain programs and with rooting and all that.
Something important required me to TRY upgrading to Android 6, hoping this might solve my problem. It didn't. The problem has since fixed itself (much to my confusion), but now I'm stuck with Android 6. And by upgrading I lost my custom recovery and root. I now find out that downgrading is quite a task and multiple sources say don't do it under any circumstances.
I'm (probably) fine with keeping Android 6.0 if I could just figure out how to root my phone (preferably easily). Tried PingPongRoot which is what I had previously, also tried King Root and Kingo Root and nothing worked. They all failed. PPR even put me in a catch-22 whereby I couldn't root until I got SuperSU working, but SuperSU wouldn't work because the binary wasn't installed and required root to do so. So I needed root to make SuperSU work and needed SuperSU to work in order to root. Fail.
So I got CF-Auto-Root. I figured easy, right? Then I get something I've never seen before: "Custom Binary Blocked by FRP Lock." This was not on my phone before I updated. Flashing with Odin failed instantly. Phone still works, but I'm back to square one. Looked up how to fix this problem and found that, this too, could mess me up. I'm locked out of Titanium Backup until I root and I don't want to go ruining my phone without a backup of all of my apps, for which I need TB.
1) How do I root my Galaxy S6 SM-G920P Android 6.0.1 easily? Relatively easily?
2) Is there a safe way to get rid of the FRP Lock so that I can root?
3) If rooting Android 6 is going to be dangerous, is downgrading back to Android 5 possible? Is this equally, if not more, dangerous?
I did NOT know what a pain this would be going to Android 6. I'm totally frazzled right now and out of ideas. Any help would be appreciated.
hamstrman said:
So I have a Sprint Galaxy S6. Until last week, I was running Android 5.1. I actively avoided upgrading to 6.0.1 because things are getting more difficult with the use of certain programs and with rooting and all that.
Something important required me to TRY upgrading to Android 6, hoping this might solve my problem. It didn't. The problem has since fixed itself (much to my confusion), but now I'm stuck with Android 6. And by upgrading I lost my custom recovery and root. I now find out that downgrading is quite a task and multiple sources say don't do it under any circumstances.
I'm (probably) fine with keeping Android 6.0 if I could just figure out how to root my phone (preferably easily). Tried PingPongRoot which is what I had previously, also tried King Root and Kingo Root and nothing worked. They all failed. PPR even put me in a catch-22 whereby I couldn't root until I got SuperSU working, but SuperSU wouldn't work because the binary wasn't installed and required root to do so. So I needed root to make SuperSU work and needed SuperSU to work in order to root. Fail.
So I got CF-Auto-Root. I figured easy, right? Then I get something I've never seen before: "Custom Binary Blocked by FRP Lock." This was not on my phone before I updated. Flashing with Odin failed instantly. Phone still works, but I'm back to square one. Looked up how to fix this problem and found that, this too, could mess me up. I'm locked out of Titanium Backup until I root and I don't want to go ruining my phone without a backup of all of my apps, for which I need TB.
1) How do I root my Galaxy S6 SM-G920P Android 6.0.1 easily? Relatively easily?
2) Is there a safe way to get rid of the FRP Lock so that I can root?
3) If rooting Android 6 is going to be dangerous, is downgrading back to Android 5 possible? Is this equally, if not more, dangerous?
I did NOT know what a pain this would be going to Android 6. I'm totally frazzled right now and out of ideas. Any help would be appreciated.
Click to expand...
Click to collapse
Rooting is fairly straightforward with cf-autoroot, you're main problem here is frp (factory reset protection) which is a Google security feature, you need to remove this or bypass this 1st before doing anything. I've seen a few articles and guides on Google, but as I don't have this issue I cannot say if they work or not but at a glance they do not seem very difficult. But once you get past the frp lock you can go ahead and root. If you are on a newer marshmallow bootloader then downgrading to lollipop is pretty much impossible
sofir786 said:
Rooting is fairly straightforward with cf-autoroot, you're main problem here is frp (factory reset protection) which is a Google security feature, you need to remove this or bypass this 1st before doing anything. I've seen a few articles and guides on Google, but as I don't have this issue I cannot say if they work or not but at a glance they do not seem very difficult. But once you get past the frp lock you can go ahead and root. If you are on a newer marshmallow bootloader then downgrading to lollipop is pretty much impossible
Click to expand...
Click to collapse
Thanks. I looked it up myself. Requires something called "Find my mobile," a setting under "Lock Screen and Security." I don't have that.
Samsung's website says if you don't see it, then your device is not supported. Kill me now!
I completely screwed myself by updating. If anyone else knows a way to do this with my... limitations, I would love to hear about it.
hamstrman said:
Thanks. I looked it up myself. Requires something called "Find my mobile," a setting under "Lock Screen and Security." I don't have that.
Samsung's website says if you don't see it, then your device is not supported. Kill me now!
I completely screwed myself by updating. If anyone else knows a way to do this with my... limitations, I would love to hear about it.
Click to expand...
Click to collapse
Have you had a look at method 1 on the below page?
https://www.google.ie/amp/s/www.pro...tory-reset-protection-on-samsung-devices/amp/
sofir786 said:
Have you had a look at method 1 on the below page?
https://www.google.ie/amp/s/www.pro...tory-reset-protection-on-samsung-devices/amp/
Click to expand...
Click to collapse
Method 1 being... factory reset? I'm hoping to keep my phone in tact.
I did find something stupidly simple that someone just happened to off hand comment on in an old thread. Apparently there's a switch in the settings to disable OEM protections. I didn't think it would work but it really was that easy.
Was able to root successfully using CF, but then doing a SuperSU full unroot caused a bootloop. I have to figure out the proper way to root for my needs now.
Thanks for the suggestion, though!
I've made this thread to teach T337A owners how to root their device with SuperSU. Please note that this is a system-less root, meaning it's temporary, but can be re-applied. Rooting only takes about 5-7 minutes and brings numerous tweaks and advantages to your device. Just remember that every time you reboot or shut the device down, you will need to repeat the rooting process. This tutorial was designed for Lollipop 5.1.1, but it should work on KitKat as well.
Before beginning, you will need to download the following file, unzip it on your pc, then transfer it to your device's internal storage/external sd card.
T337AUCU2BOH4 (Lollipop) firmware can be found here
Root Files can be found here
Lets start!
1) Install both the APK files in the file on your device, If prompted, allow installation from unknown sources.
2) Make sure your device is connected to WiFi, then open Kingroot.
3) Once Kingroot is "Done searching for the best root strategy", click the "Try Now" button and wait about 3 minutes for KingRoot to give you a "Root Successfully" message.
4) This is where it gets kinda tricky, immediately after receiving the root success message, go into SuperSU-me, and grant root permissions when prompted.
5) Click on the big blue button in the middle of the frame and wait about 1 minute for the process to complete. DO NOT UPDATE THE SUPERSU BINARY, IT WILL CAUSE YOUR DEVICE TO BOOTLOOP.
6) IMMEDIATELY after the process has completed, go into Settings and make sure KingRoot or Purify is not installed! This is an important step because Kingroot and Kingroot adware tends to install itself in the system partition which can cause problems and frustration.
7 - Recommended) Download a root file explorer (such as ES File Explorer) and search "King" under /data and /system to ensure that the KingRoot app and its bloatware has been wiped from the system. This is to ensure that Kingroot still works properly after a reboot.
8) Enjoy root access!
If this tutorial helped you please be sure to hit the :good: button. If you had any issues or troubles during this process please feel free to let me know down below.
Cheers!
@KingOfTheNet
will flashfire work? bc it wont with kingroot
also, could itit.d be enabled and run these off of a script for example on startup so we don't have to do this after each reboot/shutdown
but i believe you would have to capture kingroots data somehow in the process of rooting
toolhas4degrees said:
@KingOfTheNet
will flashfire work? bc it wont with kingroot
also, could itit.d be enabled and run these off of a script for example on startup so we don't have to do this after each reboot/shutdown
but i believe you would have to capture kingroots data somehow in the process of rooting
Click to expand...
Click to collapse
FlashFire does work on SuperSU, I've tested that for myself. It does not work with KingRoot.
For the second question, I'm not sure. I haven't looked through that file myself and I might look through it later but right now, I would just avoid rebooting the tablet if you wanna keep root without repeating the process over and over again. It's what I do, repeating the process over and over again can get very tedious and annoying.
Cheers!
I assume you're talking about 5.1.1? It won't work with kingroot versions higher than 4.8. Also, flashfire will load, but if you try to flash a zip you're screwed. You can actually use replace kingroot with supersu zip in terminal emulator on any version kingroot. Same deal with su binary, don't update it. Wish I could figure out how I had permanent for with kingroot. I had to go messing with things and lost it. Nothing really special about this method, unless there's a dev out there that can do something with it.
xjimmy said:
I assume you're talking about 5.1.1? It won't work with kingroot versions higher than 4.8. Also, flashfire will load, but if you try to flash a zip you're screwed. You can actually use replace kingroot with supersu zip in terminal emulator on any version kingroot. Same deal with su binary, don't update it. Wish I could figure out how I had permanent for with kingroot. I had to go messing with things and lost it. Nothing really special about this method, unless there's a dev out there that can do something with it.
Click to expand...
Click to collapse
Sorry for the late response. Yes, somethings I forgot to mention in the original post:
1)Updating the SU Binary will put your device in a bootloop
2)Flashing anything with flashfire (based on what I've seen) results in a soft brick
3) I know you can replace kingroot with SuperSU in terminal, but when you reboot, you're unrooted again.
4) I'm trying to figure out how I could altar the boot.img so we can get permanent SuperSU on this thing the same way Chainfire did it with the US and Qualcomm Samsung Galaxy S7's.
Cheers!
Hi, @KingOfTheNet, thanks for helping out with this device, i rooted my device on KK nk2 build and now updated to 5.1.1, thanks to you! now i would like to root 5.1.1 (am aware it is a temp. root)
i have superSu Pro, do i need Super Sume for this to work?
KingOfTheNet said:
Sorry for the late response. Yes, somethings I forgot to mention in the original post:
1)Updating the SU Binary will put your device in a bootloop
2)Flashing anything with flashfire (based on what I've seen) results in a soft brick
3) I know you can replace kingroot with SuperSU in terminal, but when you reboot, you're unrooted again.
4) I'm trying to figure out how I could altar the boot.img so we can get permanent SuperSU on this thing the same way Chainfire did it with the US and Qualcomm Samsung Galaxy S7's.
Cheers!
Click to expand...
Click to collapse
Somehow I had it permanently rooted with kingroot a while back. I had the 4.9.6 apk on my tab at the time, is all I know. I could've updated from an earlier version, and maybe that was the cause. I've tried so many different versions of kingroot with no luck, but one peculiar occurrence; if I open kingroot, get into the settings and uninstall kingroot without saving a backup of root, then delete all the files in the tablet's main directory, and reinstall kingroot version 4.8.0, it somehow retains a partial permanent root. At least on my T337A running 5.1.1 BOH4 it will, as long as I get a fresh install of 4.8.0, let it root, then hit the optimize button right after. Then wait until it finally tells me that kingroot has been deployed as a system app. After that, when I try to open any root apps, the screen will darken as it does when the root permission tab pops up, but it never pops up. The app just freezes. I can kill it in the task manager screen to just go back to using my tablet. After I restart the tab, sometimes it'll tell me an app has been granted superuser permissions. If I open up terminal emulator, type in the 'su' command and hit enter, the screen will turn dark again like it's going to ask me to allow or deny superuser permission, but it just freezes like that again. I've tried all kinds of stuff with 4.8.0, but I still can't get it to stick. If you don't hit the optimize button in kingroot right after rooting, and just wait for kingroot to install as a system app, the allow/deny prompt comes up without freezing, but the partial permanent root glitch doesn't remain. ugh, tired of messing with it though. lol
Edit: I may be wrong. It might need to be rooted with 4.8.0, optimized, then rebooted right away for the partial root. I'll try to do it again and let you know what I find.
bklyndiaz said:
Hi, @KingOfTheNet, thanks for helping out with this device, i rooted my device on KK nk2 build and now updated to 5.1.1, thanks to you! now i would like to root 5.1.1 (am aware it is a temp. root)
i have superSu Pro, do i need Super Sume for this to work?
Click to expand...
Click to collapse
I'm happy to help out! You'd need king root installed, root the tab with king root, then use SuperSU me to replace the kingroot binaries with the SuperSU ones. It is an automatic process and should only take about 30 seconds or less. Pro version of SUPERSUme is not required, free version should work just fine.
Cheers!
xjimmy said:
Somehow I had it permanently rooted with kingroot a while back. I had the 4.9.6 apk on my tab at the time, is all I know. I could've updated from an earlier version, and maybe that was the cause. I've tried so many different versions of kingroot with no luck, but one peculiar occurrence; if I open kingroot, get into the settings and uninstall kingroot without saving a backup of root, then delete all the files in the tablet's main directory, and reinstall kingroot version 4.8.0, it somehow retains a partial permanent root. At least on my T337A running 5.1.1 BOH4 it will, as long as I get a fresh install of 4.8.0, let it root, then hit the optimize button right after. Then wait until it finally tells me that kingroot has been deployed as a system app. After that, when I try to open any root apps, the screen will darken as it does when the root permission tab pops up, but it never pops up. The app just freezes. I can kill it in the task manager screen to just go back to using my tablet. After I restart the tab, sometimes it'll tell me an app has been granted superuser permissions. If I open up terminal emulator, type in the 'su' command and hit enter, the screen will turn dark again like it's going to ask me to allow or deny superuser permission, but it just freezes like that again. I've tried all kinds of stuff with 4.8.0, but I still can't get it to stick. If you don't hit the optimize button in kingroot right after rooting, and just wait for kingroot to install as a system app, the allow/deny prompt comes up without freezing, but the partial permanent root glitch doesn't remain. ugh, tired of messing with it though. lol
Edit: I may be wrong. It might need to be rooted with 4.8.0, optimized, then rebooted right away for the partial root. I'll try to do it again and let you know what I find.
Click to expand...
Click to collapse
Kingroot does allow your device to retain permanent root after a certain time. However, Kingroot is not as powerful as SuperSU, is very limited in terms of what It can do, and has it's own 'bloatware' titled Purify. I'd honestly stick with SuperSU because it's (probably) the most powerful and efficient way to root your phone. I'd also suggest avoiding having to reboot the tablet at all with temp root because you would have to take 5 minutes to install it again, which was a pain in the butt for me.
As for the kingroot app freezing, that's usually the result of a bad download or a bad root. Plus kingroot is very limited in terms of what you can do on your kingrooted device. SUPERSU is the equivalent of an IOS jailbreak. SUPERSU gives you full control of your device, with no bloatware and limits, unlike kingroot.
Kingroot does sometimes delete the su binaries upon rebooting, which is another reason I don't like it all that much.
Another theory I thought of is that it's not Kingroot that's deleting the binaries, it's actually something that's set to happen when the device boots up. Either the actual Android os or the bootloader searches for and deletes the su binaries to prevent root.
I don't know for sure, I've kinda slowed down work on this device mainly because of a project I've been working on with the Samsung Galaxy S7 AT&T (SM-G930A). I'll look into these things when I get the chance.
Cheers!
I understand the limitations of Kingroot, and certainly supersu by all means is better. In the case of flashfire with supersu in this scenario, it's merely the difference of being able to open and run it just enough to work improperly and brick your device vs. Kingroot not being able to open it at all. I posted in a thread long before this one, how to replace kingroot with supersu, only I use the zip file in terminal emulator. Pretty sure I went over flashfire as well. The terminal emulator method works with new versions of kingroot, unlike supersu me. Are you suggesting that the T337A running 5.1.1 BOH4 can achieve permanent root via kingroot after "a certain amount of time"? Because I'm the only one I've seen on xda who's ever posted that they had permanent root from kingroot, but I didn't know how I did it. After I messed with things, i softbricked and had to flash back to stock, which, no offense, the stock file was available way before you posted it. Anyway, it's not the kingroot app freezing per se, i was talking about after rebooting, and without re-rooting, when trying to use rooted apps, they actually start to engage in the kingroot request superuser permissions pop-up. So, no, it's not a bad download, etc. I believe an older version of kingroot somehow permanently rooted my tab, perhaps with the help of something I was messing with at the time, perhaps not. I've intentionally rebooted my tab an unimaginable amount of times, testing to see if I possibly regained permanent root to no avail, so I know how that works. And it's not about having a hard time deciding on kingroot or supersu for a temproot, it's the interest in permanent root, the possibility off something like safestrap, and/or flashing custom roms, etc. When people say temproot is better or safer, i say boo. How many custom roms include a root toggle in the settings? Anyway I wish I could've gotten hold of a developer while I had permanent root. Maybe I could've done a system dump, or even try replacing the permanent kingroot with supers and drying out that could've stuck. You say you slowed down on this device, do you mean you were pursuing permanent root for it? Are you a developer? I have the AT&T S7 Edge (G935A). What's your project on the 930? Is it something for rooted S7's? I still have my edge running the engboot with the echoRom. Anyway, thanks for your reply.
---------- Post added at 01:01 AM ---------- Previous post was at 12:51 AM ----------
https://forum.xda-developers.com/tab-4/help/t337a-temp-root-bootlp-fix-tar-official-t3473737
*https://forum.xda-developers.com/tab-4/general/permanent-root-t337a-5-1-1-kingroot-t3518334
A couple of threads I started a long time ago that may be of interest to you.
xjimmy said:
I understand the limitations of Kingroot, and certainly supersu by all means is better. In the case of flashfire with supersu in this scenario, it's merely the difference of being able to open and run it just enough to work improperly and brick your device vs. Kingroot not being able to open it at all. I posted in a thread long before this one, how to replace kingroot with supersu, only I use the zip file in terminal emulator. Pretty sure I went over flashfire as well. The terminal emulator method works with new versions of kingroot, unlike supersu me. Are you suggesting that the T337A running 5.1.1 BOH4 can achieve permanent root via kingroot after "a certain amount of time"? Because I'm the only one I've seen on xda who's ever posted that they had permanent root from kingroot, but I didn't know how I did it. After I messed with things, i softbricked and had to flash back to stock, which, no offense, the stock file was available way before you posted it. Anyway, it's not the kingroot app freezing per se, i was talking about after rebooting, and without re-rooting, when trying to use rooted apps, they actually start to engage in the kingroot request superuser permissions pop-up. So, no, it's not a bad download, etc. I believe an older version of kingroot somehow permanently rooted my tab, perhaps with the help of something I was messing with at the time, perhaps not. I've intentionally rebooted my tab an unimaginable amount of times, testing to see if I possibly regained permanent root to no avail, so I know how that works. And it's not about having a hard time deciding on kingroot or supersu for a temproot, it's the interest in permanent root, the possibility off something like safestrap, and/or flashing custom roms, etc. When people say temproot is better or safer, i say boo. How many custom roms include a root toggle in the settings? Anyway I wish I could've gotten hold of a developer while I had permanent root. Maybe I could've done a system dump, or even try replacing the permanent kingroot with supers and drying out that could've stuck. You say you slowed down on this device, do you mean you were pursuing permanent root for it? Are you a developer? I have the AT&T S7 Edge (G935A). What's your project on the 930? Is it something for rooted S7's? I still have my edge running the engboot with the echoRom. Anyway, thanks for your reply.
---------- Post added at 01:01 AM ---------- Previous post was at 12:51 AM ----------
https://forum.xda-developers.com/tab-4/help/t337a-temp-root-bootlp-fix-tar-official-t3473737
*https://forum.xda-developers.com/tab-4/general/permanent-root-t337a-5-1-1-kingroot-t3518334
A couple of threads I started a long time ago that may be of interest to you.
Click to expand...
Click to collapse
No offence taken on the firmware post, I was simply trying to spread the fact that the firmware for the device does exist but is very hard to find and is often posted on shady websites for money, unless you're looking in the right places. It only took me 5 minutes on Google to find one of those sites.
You asked if I was saying that the Tab 4 BOH4 firmware allows you to retain permanent root after some time, and yes, that's exactly what I was saying. I rooted my tablet with Kingroot 4.8.0 a while back and after about 4 - 5 reboots (I counted how many times I rebooted it, but the numbers could vary), It retained root. All I do today is avoid rebooting the tablet at all costs. I prefer SuperSU because, like we've said, there are almost no limitations of what you can do in terms of being rooted. I'm trying to find out how I can make root permanent on the tab with SuperSU by using the eng-boot method used to root all Qualcomm variants of the Galaxy S7, but that may take a while. Since my S7 has the eng-boot root method, I can reboot it all I want and it stays rooted with SuperSU. But at this point, It's just an Idea. I mainly need to find out whether or not the bootloader or the os is wiping the binaries on boot. Some older and newer versions of kingroot can retain root after reboot, but I have yet to find a version of the app that can do so.
Actually, some versions of Cyanogenmod and other custom roms had root pre-installed (not like SuperSU, but close enough), and like CM specifically, there was a section in the settings app for this pre-baked root. Even if I still used CM today, I still would've flashed SuperSU. But on a small number of devices, temp root really is better. However, most of those devices that would be on that list have very little to no development on them. Thus, they are not yet (and may never be) supported for permanent root.
I am partially on the road to becoming a developer, but I don't know how far that's gonna go (my prediction is not that far at all). I was doing research on how I could make an eng-boot for the Tab 4, but I became interested in my Galaxy S7 (AT&T). By that, I mean I wanted to make my own custom version of the stock Marshmallow rom ("Custom but stock OS"). To shorten it up, I wanted to create a .zip flashable "super package" which included SuperSU v2.79, Viper4Android, Overclock tools, and other stuff. I've kinda been on and off in terms of motivation to make this idea a reality, primarily because most of the things I wanted to include in this "package", can easily be installed by you in like 3 minutes, or maybe less. The original motive behind the idea was to lessen the work for power users who wanted to free their device "from the shackles". I've been on and off on work between both devices, but It's hard for me to continue the work without proper motivation. These projects are merely just an Idea at this point, but some drafts and copies do exist on my computer.
Creating a custom Android rom straight from my own head is basically an impossible task for me, considering most of the devices I work with have locked bootloaders. I am still learning Java and other Android programming languages in some of my free time but, again, the motivation to continue is something I struggle to find.
Cheers!
Upgrading OS and rooting
I am currently running my t337a on 4.4.2 with build NK2. I was able to root with towel root awhile ago. I want to upgrade my os to 5.1.1 and root after but would like to make sure I go about it the right way.
Any help would be greatly appreciated. Thanks in advance!
loc626 said:
I am currently running my t337a on 4.4.2 with build NK2. I was able to root with towel root awhile ago. I want to upgrade my os to 5.1.1 and root after but would like to make sure I go about it the right way.
Any help would be greatly appreciated. Thanks in advance!
Click to expand...
Click to collapse
You can root on the latest Lollipop firmware, but it's systemless supersu/temporary, meaning it will go away if you shutdown or reboot the device (you can re-root it, of course, but It can be annoying). The option to upgrade is up to you, and once you do upgrade, you can't downgrade (Locked bootloader & different bootloader versions. Lollipop has the new bootloader.) If you are going to upgrade, you can flash the Lollipop firmware via Odin or upgrade via OTA. If upgrading, I recommend taking it over the air, mainly because I'm still working up Odin packages for them. The Odin packages that I do have available are the BOH4 (the previous and the initial Lollipop update) ones, so if you upgrade OTA, it'll take away one step in the upgrade process, making your life a tad bit easier. Reply back if you need further help or have any more questions.
Cheers!
KingOfTheNet said:
You can root on the latest Lollipop firmware, but it's systemless supersu/temporary, meaning it will go away if you shutdown or reboot the device (you can re-root it, of course, but It can be annoying). The option to upgrade is up to you, and once you do upgrade, you can't downgrade (Locked bootloader & different bootloader versions. Lollipop has the new bootloader.) If you are going to upgrade, you can flash the Lollipop firmware via Odin or upgrade via OTA. If upgrading, I recommend taking it over the air, mainly because I'm still working up Odin packages for them. The Odin packages that I do have available are the BOH4 (the previous and the initial Lollipop update) ones, so if you upgrade OTA, it'll take away one step in the upgrade process, making your life a tad bit easier. Reply back if you need further help or have any more questions.
Cheers!
Click to expand...
Click to collapse
I'm highly considering an upgrade for the feel and hopefully a better performance. Also, a few apps I have need updates but only compatible on Android 5 and up. I have the OTA ready to go. Would I need to unroot before upgrading the OS?
loc626 said:
I'm highly considering an upgrade for the feel and hopefully a better performance. Also, a few apps I have need updates but only compatible on Android 5 and up. I have the OTA ready to go. Would I need to unroot before upgrading the OS?
Click to expand...
Click to collapse
It would be best to unroot before installing to avoid any issues during the installation. Other then that, you're in the clear! Just remember, you cannot downgrade after the install!
Cheers!
KingOfTheNet said:
4) I'm trying to figure out how I could altar the boot.img so we can get permanent SuperSU on this thing the same way Chainfire did it with the US and Qualcomm Samsung Galaxy S7's.
Click to expand...
Click to collapse
I have always been under the assumption that the boot.img for the locked BL on the s7 was literally an engineering kernel from Samsung, and not something Chainfire created. The reason Im saying this is because if Chainfire created a boot image that can get around a locked bootloader, then logic should state that he cracked Sprint/ATT's signature for the BL. So my way of thinking is the success of even one locked boot loader ... it should apply across the board for all, correct? Or am I waaaaay off? lol
leeboski44 said:
I have always been under the assumption that the boot.img for the locked BL on the s7 was literally an engineering kernel from Samsung, and not something Chainfire created. The reason Im saying this is because if Chainfire created a boot image that can get around a locked bootloader, then logic should state that he cracked Sprint/ATT's signature for the BL. So my way of thinking is the success of even one locked boot loader ... it should apply across the board for all, correct? Or am I waaaaay off? lol
Click to expand...
Click to collapse
(1st question) Actually yeah, lol. It was an engineering kernel, he didn't make it . I'm assuming that was used during the development of the phone so Samsung and AT&T could construct the OS without running into any issues with the phones locked bootloader. At the time, I thought that Chainfire thought of some "mad science" to altar the boot.img so that it wont check the signatures of any of the files on boot.
Now I'm thinking:
1) He found a way to obtain all the phones signatures so that way he knows what signature the desired files (like a build of TWRP, or instance) would have to have so it can flash and boot properly.
--OR--
2) He somehow obtained or reproduced the engineering kernel that, like I said, was most likely used during software development for the phone (constructing the OS and the rest of the software).
I've done a little research on what engineering kernels actually do and why they are so useful now (to most people, the name is enough, lol). Apparently, they completely skip some of the signature checks on boot, primarily for /SYSTEM (The OS), which is why we were able to achieve permanent root the Qualcomm Galaxy S7 & S7 edge models. I do not think they skip signature checks for /RECOVERY or /BOOT, but we know that if we either reproduce or obtain the engineering kernel for this tablet, we can achieve permanent root the exact same way. I could be wrong, as I do not know for certain the Ins and outs of engineering kernels and how to get them, but It is very possible.
(2nd question) Now, I do not have much knowledge of bootloaders and signature checks, but I would go to the best assumption that since Sprint & AT&T, for example, are 2 completely different companies and are not affiliated (as of writing this), their bootloaders and updates would not have the same signatures. If they did, then Sprint would have to go to AT&T to sign their updates and such, and AT&T would have to do the same thing for Sprint. It just wouldn't really make sense. Lets think of it this way, If Target wants to sell a product in their stores that's already sold at Walmart, then should Target have to go to Walmart to get that approved? Or if Walmart wanted to sell something that's already sold at Target, then should Walmart have to go to Target for approval? Absolutely not, that wouldn't make any sense. Once again, I could be wrong, but it would make the most sense.
Please, anyone, correct me if I'm wrong.
Cheers!
KingOfTheNet said:
(1st question) Actually yeah, lol. It was an engineering kernel, he didn't make it . I'm assuming that was used during the development of the phone so Samsung and AT&T could construct the OS without running into any issues with the phones locked bootloader. At the time, I thought that Chainfire thought of some "mad science" to altar the boot.img so that it wont check the signatures of any of the files on boot.
Now I'm thinking:
1) He found a way to obtain all the phones signatures so that way he knows what signature the desired files (like a build of TWRP, or instance) would have to have so it can flash and boot properly.
--OR--
2) He somehow obtained or reproduced the engineering kernel that, like I said, was most likely used during software development for the phone (constructing the OS and the rest of the software).
I've done a little research on what engineering kernels actually do and why they are so useful now (to most people, the name is enough, lol). Apparently, they completely skip some of the signature checks on boot, primarily for /SYSTEM (The OS), which is why we were able to achieve permanent root the Qualcomm Galaxy S7 & S7 edge models. I do not think they skip signature checks for /RECOVERY or /BOOT, but we know that if we either reproduce or obtain the engineering kernel for this tablet, we can achieve permanent root the exact same way. I could be wrong, as I do not know for certain the Ins and outs of engineering kernels and how to get them, but It is very possible.
(2nd question) Now, I do not have much knowledge of bootloaders and signature checks, but I would go to the best assumption that since Sprint & AT&T, for example, are 2 completely different companies and are not affiliated (as of writing this), their bootloaders and updates would not have the same signatures. If they did, then Sprint would have to go to AT&T to sign their updates and such, and AT&T would have to do the same thing for Sprint. It just wouldn't really make sense. Lets think of it this way, If Target wants to sell a product in their stores that's already sold at Walmart, then should Target have to go to Walmart to get that approved? Or if Walmart wanted to sell something that's already sold at Target, then should Walmart have to go to Target for approval? Absolutely not, that wouldn't make any sense. Once again, I could be wrong, but it would make the most sense.
Please, anyone, correct me if I'm wrong.
Cheers!
Click to expand...
Click to collapse
No that makes perfect sense and thanks for clearing it up.
The whole thing about the signature being the means by which the bootloader is locked is important. Atleast to me it is, so thank you for clearing that up. :good: And so, it makes sense that the System partitions Signature check being skipped IS what allows access to root. But where my opinion differs on this is the Boot and Recovery implementation of the Signatures. I believe that it IS the carriers implementation that does not allow the Recovery and Boot partitions to be modified. If it were Samsungs then how is Samsung going to incorporate a Universal bootloader that knows how to load all carriers data, policy, etc?
And possibly this is what you were saying above and I am misreading it...
***EDIT*** I see you said that the signatures would NOT be the same between carriers, so I am in line with your theory there as well.
leeboski44 said:
No that makes perfect sense and thanks for clearing it up.
The whole thing about the signature being the means by which the bootloader is locked is important. Atleast to me it is, so thank you for clearing that up. :good: And so, it makes sense that the System partitions Signature check being skipped IS what allows access to root. But where my opinion differs on this is the Boot and Recovery implementation of the Signatures. I believe that it IS the carriers implementation that does not allow the Recovery and Boot partitions to be modified. If it were Samsungs then how is Samsung going to incorporate a Universal bootloader that knows how to load all carriers data, policy, etc?
And possibly this is what you were saying above and I am misreading it...
***EDIT*** I see you said that the signatures would NOT be the same between carriers, so I am in line with your theory there as well.
Click to expand...
Click to collapse
I'm glad I could be of help, however I don't see where I stated that the signature implementations on the BOOT and RECOVERY partitions was Samsung's idea not the carriers, if you could point that out for me that would be great.:good:
The engineering kernels skip SOME signature checks, both when flashing and booting into partitions, but I do not know exactly which ones they skip. We know it skips some of the signatures for /SYSTEM, but it does not do the same for the 2 other main ones, those being /BOOT & /RECOVERY. We know because "one of our own" attempted to flash their own build of TWRP recovery to the device (SM-G930A to be specific) only to get a signature check fail when booting the phone, which of course means that the phone has a locked bootloader and that the signatures for the /RECOVERY partition are still checked, but I do not know for certain about /BOOT. If I had to assume I'd say that /BOOT isn't checked, given the fact that if your phone is rooted then you would have had to flash the engineering kernel, which, like I said, skips some signature checks.
I hope I've cleared most things up for you.
Cheers!
KingOfTheNet said:
I've made this thread to teach T337A owners how to root their device with SuperSU. Please note that this is a system-less root, meaning it's temporary, but can be re-applied. Rooting only takes about 5-7 minutes and brings numerous tweaks and advantages to your device. Just remember that every time you reboot or shut the device down, you will need to repeat the rooting process. This tutorial was designed for Lollipop 5.1.1, but it should work on KitKat as well.
Before beginning, you will need to download the following file, unzip it on your pc, then transfer it to your device's internal storage/external sd card.
Root File: https://mega.nz/#!74Jl0ZqY!knlHuexbYGFkk1f4wHxq16u3L38EtfR9scQ0H7hISTA
Lets start!
1) Install both the APK files in the file on your device, If prompted, allow installation from unknown sources.
2) Make sure your device is connected to WiFi, then open Kingroot.
3) Once Kingroot is "Done searching for the best root strategy", click the "Try Now" button and wait about 3 minutes for KingRoot to give you a "Root Successfully" message.
4) This is where it gets kinda tricky, immediately after receiving the root success message, go into SuperSU-me, and grant root permissions when prompted.
5) Click on the big blue button in the middle of the frame and wait about 1 minute for the process to complete. DO NOT UPDATE THE SUPERSU BINARY, IT WILL BOOTLOOP.
6) IMMEDIATELY after the process has completed, go into Settings and make sure KingRoot or Purify is not installed! This is an important step because Kingroot and Kingroot adware tends to install itself in the system partition which can cause problems and frustration.
7 - Recommended) Download a root file explorer and search "King" under /data and /system to ensure that the KingRoot app and its bloatware has been wiped from the system.
8) Enjoy root access!
If this tutorial helped you please be sure to hit the :good: button. If you had any issues or troubles during this process please feel free to let me know down below.
Need T337A firmware? Check out my thread here: https://forum.xda-developers.com/tab-4/general/download-sm-t337a-lollipop-firmware-t3536509
Cheers!
Click to expand...
Click to collapse
The firmware you provided saved my sm-t337A tablet from being soft bricked. Although I was able to gain temp root from this method, king root tried to disable the SELinux on my device and after trying to temp root again caused the app to implant itself as bloatware into the /systems folder and was non functional when using the app. Do you happen to know of a custom recovery (TWRP or CWM) which would work for this device?