1. I noticed exploits are being patched left and right.
2. Knox is easy to trip now.
3. There are no custom firmwares anymore for Samsung phones.
4. Samsung requests the removal of links on this board constantly.
5. Can't use Samsung pay with a knox tripped phone.
6. Downgrading is blocked in case you have an upgraded phone.
Is this what Samsung forums have come to now? Are there phones out there that you don't have to deal with Knox?
It seems people don't really care anymore about Samsung phones?
nafeasonto said:
1. I noticed exploits are being patched left and right.
2. Knox is easy to trip now.
3. There are no custom firmwares anymore for Samsung phones.
4. Samsung requests the removal of links on this board constantly.
5. Can't use Samsung pay with a knox tripped phone.
6. Downgrading is blocked in case you have an upgraded phone.
Is this what Samsung forums have come to now? Are there phones out there that you don't have to deal with Knox?
It seems people don't really care anymore about Samsung phones?
Click to expand...
Click to collapse
Your question has been asked by many people on multiple forums. Samsung's flagship is great as is, however the software has a few bugs that bother everyone which is why we root. Samsung built knox so there products would appeal to corporate customers. That is why it exists. To say there are no custom firm wares is false. Just read the development forums. Root is not an absolute must, but it is getting harder as time goes on
Snowby123 said:
Root is not an absolute must, but it is getting harder as time goes on
Click to expand...
Click to collapse
That doesn't make me hopeful.
nafeasonto said:
That doesn't make me hopeful.
Click to expand...
Click to collapse
I obtained root just to prove to myself it can be done. It is not the most important thing In the world. That said, I do understand your perspective. I appreciate the root apps and custom ROMs, and each year root access I harder and harder. Even without root you can appreciate any android device
I stopped rooting just because my Barclay's bank app doesn't work on rooted phones and it's very convenient for me. Also stock android got a lot better and I like it as it is. Also you have theme engines build it now so you can customize your phone without rooting. All that said of course there is some exceptional cases that root is needed, like recently with the new S6 there is no option to choose 2G only network mode on stock rom and I don't know if there is a no root solution for it
So perhaps I am in a shrinking group of people that still needs, or rather appreciates, rooting.
I'm not sure what I can discuss here...
I am switching from my S5 to my new S6 (got it today!) and I need to use Titanium Backup Pro. I am restoring every app from the former to the latter and some of my games aren't... stored on the Google Play store. And I like root-requiring game alterers, unlocking my phone to be a hotspot, and simpler things like using Coolify, Root Booster and Root Explorer, among others.
Now I've tested my ability to transfer everything over from one device to another (my tablet), so I know it will work. I just keep reading more and more about KNOX (which I successfully avoided on my S5) and how it's unavoidable on the S6. How you can't rollback to an earlier version of Android (since I got my phone today, I'm assuming I have 5.1.1). I don't care about Samsung Pay. At all.
Is it advisable for me to root? If I have 5.1.1, CAN I? I read that PingPongRoot won't even WORK on 5.1.1! What am I to do? Or does no one care about rooting anymore? Is anyone devoted to resolving these issues or did everyone shrug and go, "Eh."?
hamstrman said:
So perhaps I am in a shrinking group of people that still needs, or rather appreciates, rooting.
I'm not sure what I can discuss here...
I am switching from my S5 to my new S6 (got it today!) and I need to use Titanium Backup Pro. I am restoring every app from the former to the latter and some of my games aren't... stored on the Google Play store. And I like root-requiring game alterers, unlocking my phone to be a hotspot, and simpler things like using Coolify, Root Booster and Root Explorer, among others.
Now I've tested my ability to transfer everything over from one device to another (my tablet), so I know it will work. I just keep reading more and more about KNOX (which I successfully avoided on my S5) and how it's unavoidable on the S6. How you can't rollback to an earlier version of Android (since I got my phone today, I'm assuming I have 5.1.1). I don't care about Samsung Pay. At all.
Is it advisable for me to root? If I have 5.1.1, CAN I? I read that PingPongRoot won't even WORK on 5.1.1! What am I to do? Or does no one care about rooting anymore? Is anyone devoted to resolving these issues or did everyone shrug and go, "Eh."?
Click to expand...
Click to collapse
-_- 5.1.1 is perfectly/easily rootable just by flashing a custom kernel. And if you looked in the development forums you'd see there's plenty of devs that care as there is plenty of rom and kernel development going on.
hamstrman said:
So perhaps I am in a shrinking group of people that still needs, or rather appreciates, rooting.
I'm not sure what I can discuss here...
I am switching from my S5 to my new S6 (got it today!) and I need to use Titanium Backup Pro. I am restoring every app from the former to the latter and some of my games aren't... stored on the Google Play store. And I like root-requiring game alterers, unlocking my phone to be a hotspot, and simpler things like using Coolify, Root Booster and Root Explorer, among others.
Now I've tested my ability to transfer everything over from one device to another (my tablet), so I know it will work. I just keep reading more and more about KNOX (which I successfully avoided on my S5) and how it's unavoidable on the S6. How you can't rollback to an earlier version of Android (since I got my phone today, I'm assuming I have 5.1.1). I don't care about Samsung Pay. At all.
Is it advisable for me to root? If I have 5.1.1, CAN I? I read that PingPongRoot won't even WORK on 5.1.1! What am I to do? Or does no one care about rooting anymore? Is anyone devoted to resolving these issues or did everyone shrug and go, "Eh."?
Click to expand...
Click to collapse
First thing I want to say is I appreciate root just as much as you.
Secondly, PingPongRoot is incompatible with 5.1.1, but depending on which variant you have,
you might still be able to root or roll back to 5.0.2
Which variant do you have?
Two years ago I would not have dreamed of using an unrooted Android phone, but Android has come a long way now. I have been using my old Note 3 and my current S6 unrooted and I'm not missing root at all. Most of the reasons why I would root are available now without root.
I also enjoy unprecendented stability on my phones. No more flashing untested amateur stuff that fixes one thing and breaks 10 other things. So the answer to your question for me is, no, it's not worth rooting anymore.
drock212 said:
-_- 5.1.1 is perfectly/easily rootable just by flashing a custom kernel. And if you looked in the development forums you'd see there's plenty of devs that care as there is plenty of rom and kernel development going on.
Click to expand...
Click to collapse
I appreciate your response. I have been looking at the development forums. I've been reading all kinds of threads and I guess I just find it daunting. I'm kind of in my own head about how I'm going to do all this and it SEEMS there are so many restrictions on what will work with what (moreso than used to be), incompatibilities and laser-focused restrictions.
I typically feel confident about these things, but when I start reading the various threads, I feel like a n00b. I have to ask because, as you've seen here, I convinced myself out of the possibility of rooting.
---------- Post added at 05:30 AM ---------- Previous post was at 05:26 AM ----------
Snowby123 said:
First thing I want to say is I appreciate root just as much as you.
Secondly, PingPongRoot is incompatible with 5.1.1, but depending on which variant you have,
you might still be able to root or roll back to 5.0.2
Which variant do you have?
Click to expand...
Click to collapse
Good to know. Possibly. Thing is, I haven't activated my phone yet (and I just got it 5 hours ago) because I know it will deactivate my old one and I'm still doing Titanium Backup to Dropbox. And I'm just incredibly terrified that I will lose the ability to do something that requires my old phone to be active. I don't actually know what that would be, but that's just me.
So, I don't know what variant I have yet. I will report back on that. I should be ready to activate by tomorrow morning.
And thanks for the response. Whether you think I'm an idiot or not (goes for you too drock212), I'm glad I'm not alone in figuring this out.
hamstrman said:
And thanks for the response. Whether you think I'm an idiot or not (goes for you too drock212), I'm glad I'm not alone in figuring this out.
Click to expand...
Click to collapse
I do not like to ever use the word 'idiot' on XDA.
Newbie is the more appropriate word to use on these forums since 'idiot' is disrespectful.
Also, you sound more like the kinda guy who is not new to Android, just new to the Galaxy S6.
hamstrman said:
...
Now I've tested my ability to transfer everything over from one device to another (my tablet), so I know it will work. I just keep reading more and more about KNOX (which I successfully avoided on my S5) and how it's unavoidable on the S6. How you can't rollback to an earlier version of Android (since I got my phone today, I'm assuming I have 5.1.1). I don't care about Samsung Pay. At all.
...
Click to expand...
Click to collapse
KNOX & many other apps can be made non-functioning with the Google Playstore app:
"Package Disabler Pro".
It is very easy to follow or change any of their suggested recommendations.
Settings can be saved or restorded to or from .xml files. Password protection is possible.
Worthwhile.
Snowby123 said:
First thing I want to say is I appreciate root just as much as you.
Secondly, PingPongRoot is incompatible with 5.1.1, but depending on which variant you have,
you might still be able to root or roll back to 5.0.2
Which variant do you have?
Click to expand...
Click to collapse
Hey! I have version 5.0.2 on my phone! Fantastic. Now I just have to turn off auto updating.
Update: My phone is not supported by PingPongRoot... G920PVPU1AOC9.
M%#$&^@#r F*($&!er!
hamstrman said:
Hey! I have version 5.0.2 on my phone! Fantastic. Now I just have to turn off auto updating.
Update: My phone is not supported by PingPongRoot... G920PVPU1AOC9.
M%#$&^@#r F*($&!er!
Click to expand...
Click to collapse
Did you try using odin to revert back to an earlier build?
Snowby123 said:
First thing I want to say is I appreciate root just as much as you.
Secondly, PingPongRoot is incompatible with 5.1.1, but depending on which variant you have,
you might still be able to root or roll back to 5.0.2
Which variant do you have?
Click to expand...
Click to collapse
Snowby123 said:
Did you try using odin to revert back to an earlier build?
Click to expand...
Click to collapse
No... I... feel really dumb right now. Rooting has always been so easy. My build just WAS fine.
I will go find ODIN and a tutorial on that.
Update: Not finding anything remotely like that on the Internet, but will search these forums.
Edit 2: Not finding anything. I assume I'm searching incorrect terms. And the PingPongRoot thread is closed because people couldn't stay on topic!
Also wondering if downgrading my build will trip KNOX, for which PPR is specifically made to avoid.
Found this on rooting the sprint s6
http://techbeasts.com/2015/04/27/install-twrp-recovery-root-sprint-galaxy-s6-g920p/
hamstrman said:
No... I... feel really dumb right now. Rooting has always been so easy. My build just WAS fine.
I will go find ODIN and a tutorial on that.
Update: Not finding anything remotely like that on the Internet, but will search these forums.
Edit 2: Not finding anything. I assume I'm searching incorrect terms. And the PingPongRoot thread is closed because people couldn't stay on topic!
Also wondering if downgrading my build will trip KNOX, for which PPR is specifically made to avoid.
Click to expand...
Click to collapse
http://forum.xda-developers.com/galaxy-s6-edge/general/sm-g925f-s6-firmware-thread-t3078841
This is the thread to follow if you want to downgrade.
Restoring the stock firmware WILL NOT trip KNOX.
It is true that the PingPongRoot thread is closed, but you still can sideload the apk.
Snowby123 said:
http://forum.xda-developers.com/galaxy-s6-edge/general/sm-g925f-s6-firmware-thread-t3078841
This is the thread to follow if you want to downgrade.
Restoring the stock firmware WILL NOT trip KNOX.
It is true that the PingPongRoot thread is closed, but you still can sideload the apk.
Click to expand...
Click to collapse
This is great. I had found this thread, but didn't know if it applied.
And I already installed PPR, it just told me when I clicked "Get Root" that my build wasn't supported. Is there some close cousin of my build that would be "correct" to change to? Like the closest build name?
I have: G920PVPU1AOC9
On the list of approved builds, I see, for example, G920PVPU1AOCF.
hamstrman said:
This is great. I had found this thread, but didn't know if it applied.
And I already installed PPR, it just told me when I clicked "Get Root" that my build wasn't supported. Is there some close cousin of my build that would be "correct" to change to? Like the closest build name?
I have: G920PVPU1AOC9
On the list of approved builds, I see, for example, G920PVPU1AOCF.
Click to expand...
Click to collapse
Since your build number is for the Sprint variant, downgrade to the earliest build there is for the sprint variant.
If it is listed on the PingPongRoot thread, install it. The one you just mentioned looks like the one to use. Try it.
An update: Worked beautifully. Laterally changed my build from G920PVPU1AOC9 to G920PVPU1AOCF - success!
Installed PingPongRoot - success!
And everything followed... Titanium Backup, Lucky Patcher, etc.
Last part is kind of important, though. Tried to install Modded Google Play Store. Failed. Did research and found out I need Xposed to install it.
So I install Xposed (I already had a backup). It tells me my framework is outdated. So I do some more digging and find out I need a special version of Xposed for Lollipop, which I get and install. There's a .zip that I have to flash via recovery in order to make Xposed work which would make Lucky Patcher work which would make the Store work.
Flashing the zip requires TWRP or CWM recovery. Can I install either of those without tripping KNOX? This is getting way too complicated. I mean, logically, I would think that since I have PingPongRoot already, that I'm good.
Hey all!
I recently bought the LG Phoenix 2 (LG k371) from ATT, and I really want to root it. But alas, I was unable to find any root method that works for my phone. Does anyone know of a method that will currently work for my device? It is running MarshMallow 6.0. I can update with any other info needed.
Thanks!
Lg Phoenix 2 root
KingRoot app will temp root this phone and you can uninstall all the at&t crap just fine but I needs to be re rooted every time you restart the phone I had to uninstall KingRoot my phone keeps randomly rebooting if its rooted with it
siferx said:
KingRoot app will temp root this phone and you can uninstall all the at&t crap just fine but I needs to be re rooted every time you restart the phone I had to uninstall KingRoot my phone keeps randomly rebooting if its rooted with it
Click to expand...
Click to collapse
Tried KingRoot, no dice
BUMP: I really need a method for this...
I have the same phone. Kingroot did work for me. You have to run it several times but it does eventually work. Also had the random reboot issue on occasion but I did get the bloatware off. What I would like to know is once its temp rooted, is there a method to get permanent root? Any custom recoveries that work for this?
Well I totally boned my phone I think. Kingroot works but it caused a lot of instability. It reboots the phone within minutes of getting temp rooted. So I tried supersume to remove kingroot (which seems to also have a pretty bad reputation as far as privacy goes) to replace kingroot with supersu. Everything seemed to go fine, the binary updated and looked good. Once the phone reboots though, it freezes on the AT&T logo. When I try to factory reset the android pops on screen for about 5 seconds and nothing changes. I can't do anything with adb. Whenever I try to list devices the phone is detected but it says it isn't "Authorized". If anyone has any ideas I would really appreciate it.
KippaStep said:
Hey all!
I recently bought the LG Phoenix 2 (LG k371) from ATT, and I really want to root it. But alas, I was unable to find any root method that works for my phone. Does anyone know of a method that will currently work for my device? It is running MarshMallow 6.0. I can update with any other info needed.
Thanks!
Click to expand...
Click to collapse
I'm having the same issue looking for root method for this phone. If I have to convert to lollipop again somehow I will. Please help.
Hydran said:
Well I totally boned my phone I think. Kingroot works but it caused a lot of instability. It reboots the phone within minutes of getting temp rooted. So I tried supersume to remove kingroot (which seems to also have a pretty bad reputation as far as privacy goes) to replace kingroot with supersu. Everything seemed to go fine, the binary updated and looked good. Once the phone reboots though, it freezes on the AT&T logo. When I try to factory reset the android pops on screen for about 5 seconds and nothing changes. I can't do anything with adb. Whenever I try to list devices the phone is detected but it says it isn't "Authorized". If anyone has any ideas I would really appreciate it.
Click to expand...
Click to collapse
Anybody else try Kingroot then Supersume and have the same trouble or had any success?
mnorris0678 said:
Anybody else try Kingroot then Supersume and have the same trouble or had any success?
Click to expand...
Click to collapse
Installing super su when rooted with king will brick Everytime you can temp root to uninstall the at&t bloat but that's about as far as I got phone keeps rebooting every few minutes when rooted I think I'll just get a new phone
I'm really not a fan of the fact that this device de-roots itself on every reboot, I know the developers have more popular models to address, so I'm not complaining. I was just wondering if anyone knows a way to keep that from happening and safely get rid of KingRoot and put SuperSU on instead...
Supersume
Sent from my SM-N910T using XDA-Developers mobile app
root
did you try this guide?
http://forum.xda-developers.com/showthread.php?t=2684210
Stay away from Kingroot and supersume, you are going to brick your phone!!! You'll have to send it in to LG, and your phone will never be the same again!!!
It only takes one attempt of kingroot, and no more security updates from at&t, Error: !!your device is suspected of rooting!!
(even if you uninstall kingroot & unroot)
Phoenix 2 root
Anyone have any advice on hacking into the system somehow to bypass the boot loader in order to fix the bridging problem at&t left us with? Or possibly something like flashily to flash directly to device or so we can disable bootloader security, or bypass at&t security or something like the old school ways hacking the system if possible. I don't understand HW,SW,KERNEL,LINUX,CODE,APPS so its hard for me to hack it myself. Although, I have successfully rooted, flashed supersu and twrp'd my htc one m9. I have been into buildprops and enabled hotspot tethering and disabled data throttle through proxy servers and HSM. I just don't know where or how to start the root procession this device Cuz I'm still a newb. Please no one click root suggestions, I prefer the knowledge not the instant gratification! Thanks in advance!
try this guide
http://forum.xda-developers.com/android/development/guide-root-method-lg-devices-t3049772
update
Any idea how to update the software?
I tried to update on the phone without any result
brito9112 said:
try this guide
http://forum.xda-developers.com/android/development/guide-root-method-lg-devices-t3049772
Click to expand...
Click to collapse
I tried this method but it froze on the last step, I sat there for an hour while my phone was trying to run the script but nothing would happen.
Tried it as well
brito9112 said:
try this guide
http://forum.xda-developers.com/android/development/guide-root-method-lg-devices-t3049772
Click to expand...
Click to collapse
killerfurzeYT said:
I tried this method but it froze on the last step, I sat there for an hour while my phone was trying to run the script but nothing would happen.
Click to expand...
Click to collapse
Yeah I tried that before I attempted to Kingroot and then Supersume. Did the same thing. If anyone knows of a way to de-brick the phone when supersume fails I'd appreciate any help. Not sure it's even possible.
LG k371 is one of the k8 series.
All K8 were compressed at lz4 not the gzip. SuperSU v2.66 (and other previous system-less version of supersu installer) can't decompress LZ4-compressed kernel. So that procedure won't finish the last step.
There might be two ways to solve this issue, either repacking into gzip, or waiting for supersu's support to lz4.
I guess the supersu's support to lz4 could be easier. But I don't think ppl are working on it.
At that thread, someone succeed rooting another K8 model (LG K8 k350n), with a different chipset, Mediatek MT6735 . I guess you could check it out.
http://forum.xda-developers.com/apps/supersu/install-systemless-supersu-patch-lz4-t3475765
http://www.chinaphonearena.com/forum/printthread.php?tid=16681
http://forum.xda-developers.com/apps/supersu/supersu-v2-66-installed-lz4-compressed-t3296508
Hydran said:
Yeah I tried that before I attempted to Kingroot and then Supersume. Did the same thing. If anyone knows of a way to de-brick the phone when supersume fails I'd appreciate any help. Not sure it's even possible.
Click to expand...
Click to collapse
Did you try booting the phone into fast boot settings?
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?