Related
Hey guys,
So today I decided to root my phone. I want to be able to use WiFi tethering without paying their ridiculous monthly fee, so I came here and read all I could about rooting my phone.
I downloaded the "Charge Kit V2" and proceeded with the instructions to install the "EE4stock_DXC.tar.md5" file to my phone. Everything worked as advertised and was completed in less than three minutes. I boot the phone, select the reboot option, and everything appears exactly as I left it.
Thinking I was rooted I downloaded the Android WiFi Tether app, but the thing won't work! So I go back to the FAQ and read that I could check to see if I were rooted by downloading a terminal emulator and typing "SU" into it. I did, and got "Permission Denied". I'm thinking this means I'm not rooted...
Am I rooted? If not, what did I do wrong? If so, why won't my WiFi tether work?
Thanks everyone!
ON edit: Just downloaded a root checker...apparently I'm not rooted. What could have gone wrong? Is the file I installed not rooted?
TomB985 said:
Hey guys,
So today I decided to root my phone. I want to be able to use WiFi tethering without paying their ridiculous monthly fee, so I came here and read all I could about rooting my phone.
I downloaded the "Charge Kit V2" and proceeded with the instructions to install the "EE4stock_DXC.tar.md5" file to my phone. Everything worked as advertised and was completed in less than three minutes. I boot the phone, select the reboot option, and everything appears exactly as I left it.
Thinking I was rooted I downloaded the Android WiFi Tether app, but the thing won't work! So I go back to the FAQ and read that I could check to see if I were rooted by downloading a terminal emulator and typing "SU" into it. I did, and got "Permission Denied". I'm thinking this means I'm not rooted...
Am I rooted? If not, what did I do wrong? If so, why won't my WiFi tether work?
Thanks everyone!
ON edit: Just downloaded a root checker...apparently I'm not rooted. What could have gone wrong? Is the file I installed not rooted?
Click to expand...
Click to collapse
I don't think that package is rooted, or at least it didn't root you when flashed (which happens sometimes).. use odin to flash CWM, boot straight into it and flash the superuser apk, when you boot up update the superuser app in the market and update the binary, after that you'll be rooted no problems
http://db.tt/4b3IK0C <--- superuser
blazing through on my 4G Droid Charge
Thanks for the reply!
Is there a good page with instructions on how to do this? I'm paranoid about bricking my phone and very new at this! Does the CWM load the same way the other.tar.md5 loaded?
What is a CWM?
Tried searching and didn't come up with much.
Thanks!
TomB985 said:
Thanks for the reply!
Is there a good page with instructions on how to do this? I'm paranoid about bricking my phone and very new at this! Does the CWM load the same way the other.tar.md5 loaded?
What is a CWM?
Tried searching and didn't come up with much.
Thanks!
Click to expand...
Click to collapse
this: http://forum.xda-developers.com/showthread.php?t=1160580 is a pretty good info thread on how to flash and what everything is though it's a little dated and most of the roms/CWM files are older, everything else like drivers and Odin versions are fine... CWM is short for ClockWorkMod recovery and along with Odin is what we use to flash roms/kernels/etc. to our phones, and yes in Odin it goes in the same PDA spot as a rom and flashes like normal... however since you don't have a custom kernel to make CWM 'stick' in your system its one time use after you flash it in Odin and you will have to Odin flash it again every time you want to use it, making it perfect if all you want to do is simply root the phone
Please use the Q&A Forum for questions Thanks
Moving to Q&A
THANKS!!!
After tinkering with it a few times, as well as a scare with a failed flash and temporarily bricked phone, I got it to work! I'm now rooted and have successfully run the tethering app with no errors.
Thank you for your time, you made this easy! And I didn't destroy my shiny new phone!
TomB985 said:
After tinkering with it a few times, as well as a scare with a failed flash and temporarily bricked phone, I got it to work! I'm now rooted and have successfully run the tethering app with no errors.
Thank you for your time, you made this easy! And I didn't destroy my shiny new phone!
Click to expand...
Click to collapse
nice glad to hear it, its a piece of cake after you do it once and learn it
blazing through on my 4G Droid Charge
I have done a lot of reading her about rooting and updating my TF300. After getting a headspinning amount of information, I'd like someone to verify what I think I know.
I have a TF300, stock ROM, no root, running US .17. I have not received any updates after going to Settings/about tab/update and pressing the update button (I get "no updates found') I have cleared DM and CM client and rebooted several times, but no updates are found. I have tried on several WiFI networks I have access to.
1. I should be able to root using one of several one click methods I have found here, correct?
2. Once rooted and root keeper is installed, I should be able to update to .29 and keep root, correct?
3. A manual update to US .29, once rooted, will cause me to lose root, correct?
4. Will I receive Over The Air update once rooted? If not, how can I update to US .29 without losing root?
5. Is this the best path to take, or is there another path that would be easier for a newb like me (I know just enough about Android to be dangerous)? What I mean by another path is, should I manually update to US .29 and wait for a one click solution to come out later, all the while enjoying the new update.
6. All this is to fix some lag issues I have with all browsers....Tried Stock, Dolphin, Firefox, Opera...all the same. Some FC and others just hang for up to 30 seconds, even in Performance mode (With only one tab open!) So this will "FIX" those lag issues, correct?
Thank you for your time
If you're still on .17, root with sparkyroot, save it with ota rootkeeper, update to .29 (if it isn't there, they've been posted in many places on the forums), and restore root. As for fixing lag issues, it depends on what you do, rooting alone won't change anything, but you can try out the different tweaks available.
Sent from my Incredible 2 using Tapatalk 2 Beta-5
Missed a couple of your questions, yes, you will still receive ota updates if you're rooted, as long as you don't unlock the bootloader. This is the easiest way to root too, all you need to do is follow sparkyroot's instructions and back up your root.
Sent from my Incredible 2 using Tapatalk 2 Beta-5
One question always leads to another
Thank you! But of course, I now have just a few more questions.
I do understand rooting alone will not help me with my lag issues. I'm hoping the update to .29 will. I am not a power user, but I would like the option open to me later to install ROMs, hence why I want to root now.
1. I thought I had to unlock bootloader to root. With sparkyroot I do not?
2. Since I have not unlocked bootloader, will rooting alone void my warranty? I thinking not since I should be able to unroot with no trace, correct?
3. I thought, (or read somewhere here, I think) that if I do a MANUAL install, I would lose root and be unable to regain it. If I get an update PUSHED to me by ASUS, Ill be able to regain root with rootkeeper. Is that correct?
I'd like to thank everyone here, by the way, for all the information I have gotten in my 30 days of owning this tablet and lurking here.
Throb1231 said:
Thank you! But of course, I now have just a few more questions.
I do understand rooting alone will not help me with my lag issues. I'm hoping the update to .29 will. I am not a power user, but I would like the option open to me later to install ROMs, hence why I want to root now.
1. I thought I had to unlock bootloader to root. With sparkyroot I do not?
2. Since I have not unlocked bootloader, will rooting alone void my warranty? I thinking not since I should be able to unroot with no trace, correct?
3. I thought, (or read somewhere here, I think) that if I do a MANUAL install, I would lose root and be unable to regain it. If I get an update PUSHED to me by ASUS, Ill be able to regain root with rootkeeper. Is that correct?
I'd like to thank everyone here, by the way, for all the information I have gotten in my 30 days of owning this tablet and lurking here.
Click to expand...
Click to collapse
No need to unlock for root. They are completely unrelated. Just update manually and use THIS THREAD to root .29. There's even a one-click tool like you wanted. Don't forget to press Thanks for miloj.
Oh, and after you've updated to .29 and rooted; don't forget to use OTA rootkeeper to backup root.
If Asus releases a new update it may save your root.
EndlessDissent said:
No need to unlock for root. They are completely unrelated. Just update manually and use THIS THREAD to root .29. There's even a one-click tool like you wanted. Don't forget to press Thanks for miloj.
Click to expand...
Click to collapse
He's still on the .17 software, so no need to do that. Just use the sparkyroot method, backup with rootkeeper and then update.
Edit to add that no, rooting will not void the warranty, just unroot before you need to send it back.
Sent from my Incredible 2 using Tapatalk 2 Beta-5
Yeah, he's still on .17, but he's not getting the OTA prompt. He wants to manually upgrade, and you can't restore root after a manual upgrade, so my advice still stands.
Thank you both! Rooted with Sparky root and backed up with OTA rootsaver. Now I have downloaded the .29 update from ASUS webpage and installed. It says I have lost root.
I tried to restore root with OTA and it says SU restored, however it does not show that I have root access. Tring to use Titanium BU also shows I do not have root.
Tried then to go back to Sparkyroot and try again, but to no avail. Do I now have to downgrade back to .17 to gain root because I messed it up, or is there a solution? I was rooted for several hours before the upgrade to .29.
Throb1231 said:
Thank you both! Rooted with Sparky root and backed up with OTA rootsaver. Now I have downloaded the .29 update from ASUS webpage and installed. It says I have lost root.
I tried to restore root with OTA and it says SU restored, however it does not show that I have root access. Tring to use Titanium BU also shows I do not have root.
Tried then to go back to Sparkyroot and try again, but to no avail. Do I now have to downgrade back to .17 to gain root because I messed it up, or is there a solution? I was rooted for several hours before the upgrade to .29.
Click to expand...
Click to collapse
No, you need to go to:
h tt p://forum.xda-developers.c om/showthread.php?t=1704209 (sorry for the chopped up link. I can't post links yet)
and root again.
EndlessDissent said:
Yeah, he's still on .17, but he's not getting the OTA prompt. He wants to manually upgrade, and you can't restore root after a manual upgrade, so my advice still stands.
Click to expand...
Click to collapse
Ah, ok. Didn't realize you couldn't restore if you updated manually.
Yes, it is as I thought. Tried Sparkys and miloj's root program and I can not get root. I ran the program twice from my lap top. Driver's for TF300 show installed in Device manager (Windows 7). ASUS sync was installed in laptop and recognized TF300 but the program was not running during root attempt.
When I run Superuser and attempt to update SU binaries, I get "Failed" when it attempts pathway to write update.
Attempted to restore using OTA rootkeeper but all I get is "SU Restored". Check boxes indicate no root.
Any other ideas?
Confirmed I am on .29 from a MANUAL update.
Tried again from home computer. Ran Sparky and miloj program. I get error stating
"failed to copy 'Superuser.apk' to '/data/local/tmp/Superuser.apk' : not a directory"
Tablet reboots and says I should be rooted but obviously not. Superuser not written to tablet
Throb1231 said:
Tried again from home computer. Ran Sparky and miloj program. I get error stating
"failed to copy 'Superuser.apk' to '/data/local/tmp/Superuser.apk' : not a directory"
Tablet reboots and says I should be rooted but obviously not. Superuser not written to tablet
Click to expand...
Click to collapse
Can you just install Superuser from the market? The su binaries might be there and the app just isn't installing. I may be wrong, not sure how the automated program works, but it can't hurt.
Just tried that. Installs fine but when I try to update binaries, I get error writing to filepath, telling me there is no root. I'm hoping this makes 10 posts for me so I can actually go to Sparky's thread in Dev. forum and ask directly. Thanks for your help tho. Ill still be monitoring here if anyone has a solution
Throb1231 said:
Just tried that. Installs fine but when I try to update binaries, I get error writing to filepath, telling me there is no root. I'm hoping this makes 10 posts for me so I can actually go to Sparky's thread in Dev. forum and ask directly. Thanks for your help tho. Ill still be monitoring here if anyone has a solution
Click to expand...
Click to collapse
Try manually doing the code from miloj's thread?
While the instructions in his thread are clear, they are way past my level of expertise. I would not attempt it without someone standing next to me. I have not entered code since the 1980's Compute! magazine days.
Throb1231 said:
While the instructions in his thread are clear, they are way past my level of expertise. I would not attempt it without someone standing next to me. I have not entered code since the 1980's Compute! magazine days.
Click to expand...
Click to collapse
Well, I can't think of anything else, you could just use the downgrade method, that's easy enough. The code really is just copy/paste though.
Throb1231 said:
Just tried that. Installs fine but when I try to update binaries, I get error writing to filepath, telling me there is no root. I'm hoping this makes 10 posts for me so I can actually go to Sparky's thread in Dev. forum and ask directly. Thanks for your help tho. Ill still be monitoring here if anyone has a solution
Click to expand...
Click to collapse
Your problem is not with the superuser apk.
The actual root is when you write an "su" binary to system and makes it executable (there is some access control stuff in between, but it's what's happening in essence).
So - your trouble is not with the installation nor the messages from superuser.apk - it's with the actual rooting method.
Make absolutely sure your adb drivers are working and that you've got the files "debugfs", "su" and the other debugfs file on top of the .bat file, which is the installation script, in the same directory whilst running the .bat file.
Agreed. I posted this in development.
It was surprisingly more difficult to install the drivers correctly than anticipated.
For those noobs like me, here's a step-by-step for installing the drivers before running the root method.
http://transformerprimeroot.com/tra...all-transformer-prime-usb-drivers-on-windows/
Please note that before using the step-by-step guide above, I also had to put the tf300 in Camera Mount to even get the "“ASUS Android Composite ADB Interface" option to show up in Device Manager.
Once you get this far, you can manually update the driver (found in the sparkym3 "Drivers" folder from the download) via the step-by-step.
Sent from my ASUS Transformer Pad TF300T using XDA
So I originally rooted my s3 with the GS3_debugfs-root_r2.7z method, flashed CWM and unlocked my bootloader. Since then i have flashed several roms and all was well until a couple days ago when i decided to restore my first backup in order to retrieve some data. I was still on G7 and kept getting the notification of the HE update. Even though I excepted the OTA and let it fail in CWM i kept get getting the notice almost every time i turn on my phone. I was getting so annoyed with it that i decided to flash a rom with HE in hopes that that would stop the OTA. In this whole process of restoring my backup my bootloader must have locked and when i flashed the rom I got stock on that "unauthorized software, contact Verizon screen". It freaked me out when i couldn't boot into recovery.
I followed the whole Odin, root66 method and was able to save my phone...phew... but have a couple questions now.
1) my phone has the superuser app and it shows that it cannot be uninstalled, like a system app but yet root checker says i am not rooted? Why is this.
2) Would installing supersu and updating binaries get me rooted again?
3) This one is just for curiosity..The message when i soft bricked my phone said you have unauthorized software and to go see a Verizon store. Would they really have been able help me or just tell me i am SOL
ps. Thank you to the XDA community for sharing instructions like the one i used to save my phone.
microdot said:
1) my phone has the superuser app and it shows that it cannot be uninstalled, like a system app but yet root checker says i am not rooted? Why is this.
2) Would installing supersu and updating binaries get me rooted again?
3) This one is just for curiosity..The message when i soft bricked my phone said you have unauthorized software and to go see a Verizon store. Would they really have been able help me or just tell me i am SOL
Click to expand...
Click to collapse
2: That could work, but so should loading the default SU and updating binaries.
3: They would not have been likely to help you, and may have even voided your warranty.
Going to a store would have yielded a bunch of head scratching and them telling you to file an insurance claim.
In the future if you want to block ota's freeze sdm and fwupdate in titanium.
I was messing with a bunch of stuff like supersu me, trying to replace kingroot with supersu in terminal emulator, but I don't think that had anything to do with it. I re-ran kingroot today, and now, even if I power it off all the way, or reboot, it still holds root! Permanent root is a big step, but I always want more. lol. I'm hoping there will be a way to replace it with supersu soon, and get flashfire working. On 5.1.1 BOH4 Good luck everyone!
Edit: I have no idea how I was able to keep a permanent root, but alas, I had to go messing with $#!+, and end result was having to flash stock firmware and not be able to get permanent root again. I'm not sure if things I was messing with played a strange part, or if somehow kingroot magically went through that one time, but it sucks to have lost it. I can replace kingroot with supersu using a Replace_Kinguser_with_SuperSU-v2.4 zip file, flashing it in terminal emulator, then using a power menu for root app to soft reboot before kingroot fail errors start to pop up. Sadly, if hard reboot or power off and on are done, root with supersu are wiped. If you do this, don't update the su binary or you'll hang at at&t logo in a softbrick.
whats wrong with twrp?
thelous said:
whats wrong with twrp?
Click to expand...
Click to collapse
Not sure what you mean. TWRP doesn't work on most samsung devices 5.0 & up. Also, Kingroot is limited, so as of now, flashfire doesn't work. What I'm hoping is, the supersu me app will be updated to replace the current kingroot with supersu, which should fix the flashfire problem. If flashfire works, I'm pretty sure custom roms can be flashed after that. Busybox is installable.
thelous said:
whats wrong with twrp?
Click to expand...
Click to collapse
the bootloader is locked
xjimmy said:
Not sure what you mean. TWRP doesn't work on most samsung devices 5.0 & up. Also, Kingroot is limited, so as of now, flashfire doesn't work. What I'm hoping is, the supersu me app will be updated to replace the current kingroot with supersu, which should fix the flashfire problem. If flashfire works, I'm pretty sure custom roms can be flashed after that. Busybox is installable.
Click to expand...
Click to collapse
if i remember right theres some files thst you need to delete to prevent "unroot" in boot...... similar to stock recovery flashing back on some devices after installing twrp or cwm
My rooting experience with kingroot has been temp root, with reboots causing soft brick, an update to kingroot making reboots possible without bricking, but causing unroot, and the latest update where it retains root after reboot. So whatever they did, it's working now. It is limited, however, as I doubt cwm or twrp is flashable, and flashfire doesn't work with kingroot.
What I don't want is for people to doubt me. It's easy to download the latest kingroot and try it. The lp fix boot.tar is still available, but you'll see, you won't need it. And the stock firmware .tar is available so you really have nothing to lose. What I'm hoping is, more people do it so we can move forward. I'd like to see a new version of supersu me, and flash fire working. Get to a point where we see some custom roms.
Which version of KingRoot did you use? 5.0.0 or 5.0.1?
Tried KingRoot v5.0.1 app and root doesnt stick after reboot. It actually took much longer to root then it takes with 5.0.0 version.
There is also two versions of KingRoot from different KingRoot websites; a 13.7mb and 18.5mb version. Large version, has ads and nagging notifications.
KGB7 said:
Tried KingRoot v5.0.1 app and root doesnt stick after reboot. It actually took much longer to root then it takes with 5.0.0 version.
There is also two versions of KingRoot from different KingRoot websites; a 13.7mb and 18.5mb version. Large version, has ads and nagging notifications.
Click to expand...
Click to collapse
If you're talking about the actual apk app for android, there is no version 5.0 or 5.0.1, the latest version is 4.9.2
You need to make sure you're going to Kingroot's actual website, otherwise you're going to end up on weird websites claiming to have the newest version and all that, end up with "ads and nagging notifications." lol. I bet if you opened up the kingroot app you downloaded, hit the options button (3 dots) in the top right corner and selected "about app," you'd see a different version of kingroot than 5.0, 5.0.1, or 4.9.2
If you're referring to the pc method, then I'm not sure what version that is. It pops up in a foreign language, and you might want to look up how to follow the steps accordingly. I'd be willing to bet that the pc version works just as well, though. Hope you figure out where you went wrong. Good luck.
xjimmy said:
If you're talking about the actual apk app for android, there is no version 5.0 or 5.0.1, the latest version is 4.9.2
You need to make sure you're going to Kingroot's actual website, otherwise you're going to end up on weird websites claiming to have the newest version and all that, end up with "ads and nagging notifications." lol. I bet if you opened up the kingroot app you downloaded, hit the options button (3 dots) in the top right corner and selected "about app," you'd see a different version of kingroot than 5.0, 5.0.1, or 4.9.2
If you're referring to the pc method, then I'm not sure what version that is. It pops up in a foreign language, and you might want to look up how to follow the steps accordingly. I'd be willing to bet that the pc version works just as well, though. Hope you figure out where you went wrong. Good luck.
Click to expand...
Click to collapse
The app i downloaded is version 5.0.1.392 165 from Kingroot.net
Su Version 3.64.
KGB7 said:
The app i downloaded is version 5.0.1.392 165 from Kingroot.net
Su Version 3.64.
Click to expand...
Click to collapse
Well I'll be damned. I just downloaded it and you're right. I just hate eating crow. I apologize. I will say that the reason I was insistent on it being the latest update is because that's what I did, was have my version kingroot (4.9.2 143) check for updates and it says it's up to date. I downloaded it from the official site, tried it, and had success the same day I posted this thread. My kernel version says v4.8.0 67, and my Su version says v3.61
I would be interested, if you were willing, to hear your results after trying version 4.9.2. Also, did you try it on the pc to see the difference? If none of this works, is there a developer that I could somehow give a system dump to, maybe to see how I have root still, including after reboots? I'm not making this up, and would be willing to show you on skype if you pm me. I'm afraid to unroot it now and try it again. lol
xjimmy said:
Well I'll be damned. I just downloaded it and you're right. I just hate eating crow. I apologize. I will say that the reason I was insistent on it being the latest update is because that's what I did, was have my version kingroot (4.9.2 143) check for updates and it says it's up to date. I downloaded it from the official site, tried it, and had success the same day I posted this thread. My kernel version says v4.8.0 67, and my Su version says v3.61
I would be interested, if you were willing, to hear your results after trying version 4.9.2. Also, did you try it on the pc to see the difference? If none of this works, is there a developer that I could somehow give a system dump to, maybe to see how I have root still, including after reboots? I'm not making this up, and would be willing to show you on skype if you pm me. I'm afraid to unroot it now and try it again. lol
Click to expand...
Click to collapse
I tried the PC app twice but, it was annoying having to read the instructions on their site because they didnt translate it. The root did stick once with PC app. Not sure what made it unstick. I think its because i cleared cache in the recovery mode but, i didnt test that theory, i switched to apk.
The manual update option in the apk doesn't work properly, each time it tells me that current version is up to date. So the auto update is also useless.
I'll test the 4.92 version of KingRoot apk on the tablet and get back to you with the results. At the end of the day, i have no need for permanent root after I debloated the tablet.
KingRoot has its own thread here on the forums. You can ask them directly if you have any questions.
http://forum.xda-developers.com/android/apps-games/one-click-root-tool-android-2-x-5-0-t3107461
edit:
Here are all the builds of KingRoot you can download for you to play with.
http://forum.xda-developers.com/devdb/project/?id=9793#downloads
update;
Ran kingroot apk 4.9.2 and the root doesnt stick. Either you got lucky or you did something with supersu.
.
KGB7 said:
I tried the PC app twice but, it was annoying having to read the instructions on their site because they didnt translate it. The root did stick once with PC app. Not sure what made it unstick. I think its because i cleared cache in the recovery mode but, i didnt test that theory, i switched to apk.
The manual update option in the apk doesn't work properly, each time it tells me that current version is up to date. So the auto update is also useless.
I'll test the 4.92 version of KingRoot apk on the tablet and get back to you with the results. At the end of the day, i have no need for permanent root after I debloated the tablet.
KingRoot has its own thread here on the forums. You can ask them directly if you have any questions.
http://forum.xda-developers.com/android/apps-games/one-click-root-tool-android-2-x-5-0-t3107461
edit:
Here are all the builds of KingRoot you can download for you to play with.
http://forum.xda-developers.com/devdb/project/?id=9793#downloads
update;
Ran kingroot apk 4.9.2 and the root doesnt stick. Either you got lucky or you did something with supersu.
.
Click to expand...
Click to collapse
I replied to this comment a while ago, so I thought. lol. You ever reply to something, hit submit, and come back later to find it not posted? grrr. Thank you for at least trying again. It wouldn't seem likely that by simply clearing the cache, root would get wiped. I almost want to try it myself. What I wrote was that I would, if possible, love to do a system dump, or whatever they call it, so a developer could take a look at how and why I have permanent root. That would be to say that a developer would be interested at all. Supersu just froze in the process, and I read it's because kingroot now patched it so it wouldn't remove their root. Would be cool to get supersu on it and maybe get a custom rom or two.
Get bootloader unlocked
toolhas4degrees said:
the bootloader is locked
Click to expand...
Click to collapse
How would you go about getting the bootloader unlocked for the samsung galaxy tab 4 sm-t337a in order to flash a twrp file?
nd4400 said:
How would you go about getting the bootloader unlocked for the samsung galaxy tab 4 sm-t337a in order to flash a twrp file?
Click to expand...
Click to collapse
Ask at&t nicely.
According to what I've seen on a SM-G900A thread, the NewKingrootV4.81_C136_B245_xda_release_2016_02_29_105243.apk was the last revision that didn't block supersume from working properly.
bbc581 said:
According to what I've seen on a SM-G900A thread, the NewKingrootV4.81_C136_B245_xda_release_2016_02_29_105243.apk was the last revision that didn't block supersume from working properly.
Click to expand...
Click to collapse
I read that too, but you know what, it still doesn't work. I've found a zip file called Replace_Kinguser_with_SuperSU-v2.4 that works. What you do is install a power menu for root users first, then root with kingroot. Next, you install the replace kinguser zip using terminal emulator, which there are instructions online and on youtube on how to do it. Once you've replaced kingroot with supersu, quickly use the power menu app to do a soft reboot, as to avoid kingroot failure errors. DO NOT update the su binary. Only problem is, if you do regular reboot, or power off the tab, then power it back on, root is lost again. I have no idea how I got permanent root with kingroot, but I've lost it now while messing with things. I wish I would've tried to replace it with supersu this way when I had it just to see if it woul've still retained permanent root as well. Now what?!?! lol
I'll test the 4.92 version of KingRoot apk on the tablet and get back to you with the results. At the end of the day, i have no need for permanent root after I debloated the tablet.
KingRoot has its own thread here on the forums. You can ask them directly if you have any questions.
http://forum.xda-developers.com/android/apps-games/one-click-root-tool-android-2-x-5-0-t3107461
edit:
Here are all the builds of KingRoot you can download for you to play with.
http://forum.xda-developers.com/devdb/project/?id=9793#downloads
update;
Ran kingroot apk 4.9.2 and the root doesnt stick. Either you got lucky or you did something with supersu.
.[/QUOTE]
Hey man, old stuff, I know, but I thought this was interesting:
http://androidforums.com/threads/tutorial-how-to-root-the-sm-t337a-lollipop-with-kingroot.1100261/:
I'm not sure if he's saying to keep rebooting, and re-rooting until root sticks permanently, or to leave kingroot running without rebooting for a long time, and permanent root will sink in eventually. I think he means the second one, too leave it running without rebooting. On a sidenote, I have been able to use a replace kingroot with superuser 2.74 via terminal emulator with success, even after rooting with latest version kingroot. Updating supersu binary results in softbrick on reboot though. If you don't update user binary, and you reboot, you just lose root, is all. And sometimes the zip doesn't work, and it takes reboot, re-root with kingroot, then re-run terminal emulator. Flashfire doesn't like kingroot, but it opens up with supersu after this method. Not sure if it can actually flash zips though. Just thought I'd share my latest findings.
xjimmy said:
I'll test the 4.92 version of KingRoot apk on the tablet and get back to you with the results. At the end of the day, i have no need for permanent root after I debloated the tablet.
Thanks for the info. An interesting discovery! After going back and reading that guy's article again, I noticed that he posted a link to download kingroot. I was curious what version he used. It was 4.8.1 . When I tried downloading 4.8.1 from the xda link you gave me, it kept popping up with a network error. This time I downloaded 4.8.1 somewhere else and tried it. After root, I kept closing kingroot, swiping it clear in task manager, and re-opening it until it gave me the notice that it deployed itself as a system app. I then rebooted (not soft reboot) and it partially kept a permanent root this time. If I went into root checker, it would tell me no root, but other apps were popping up the grant permission tab. I'm sure I'll get root to stick permanently again, then I'll try to install supersu over it again, see if I can't get that as a permanent root. It's not the end of the world to me either, but it just drove me nuts not knowing how the hell I got it. Also, it's just fun to mess with stuff. lol. So in the chain of updates, 4.8.1 is right before 4.9.2, so I'm guessing that I probably got permanent root from 4.8.1 and then updated it, or possibly that I ran 4.8.1, updated, and maybe optimizing or running root again with 4.9.2 finished the job. Anyway, thanks for writing back!
Click to expand...
Click to collapse
So, I finally got my phone (SM-J320FN) rooted, thanks to info and downloads on this forum.
But now I have some questions, to which I haven't found the answers to anywhere else on the web.
1. To root, I followed instructions that told me to switch-on OEM unlock and USB debugging. However, there was no mention about turning them off again after root. Should they be on, or off?
2. Part of my rooting process involved installing/flashing TWRP. I did read that TWRP can be removed after root. What are the advantages/disadvantages of leaving or removing?
3. Now my phone is rooted, what is the best app/way to prevent it becoming unrooted by updates?
That's all for now, thanks.
SGJ3 said:
So, I finally got my phone (SM-J320FN) rooted, thanks to info and downloads on this forum.
But now I have some questions, to which I haven't found the answers to anywhere else on the web.
1. To root, I followed instructions that told me to switch-on OEM unlock and USB debugging. However, there was no mention about turning them off again after root. Should they be on, or off?
2. Part of my rooting process involved installing/flashing TWRP. I did read that TWRP can be removed after root. What are the advantages/disadvantages of leaving or removing?
3. Now my phone is rooted, what is the best app/way to prevent it becoming unrooted by updates?
That's all for now, thanks.
Click to expand...
Click to collapse
It's better to let them on.
You can remove the TWRP recovery by flashing stock recovery. But TWRP can backup your whole android partitions (nandroid backup) that can restore your android if anything goes wrong.
TWRP can flash custom roms, mods, mount partitions, and many more. So, it's better to you have TWRP(custom recovery) installed.
If you are using SuperSU superuser app then in option you found OTA survival that prevent root from OTA updates.
I think you can't get OTA updates because you are rooted. If you get OTA updates and applied on rooted android then it chances of brick your android.
Hi every one. First sorry for bad grammar I am not so good at english. Now to the problem at hand.
Jester day I bought a smj320fn and realise it is not what I paid for, so I tried to root witk KingoRoot and fail. Then I realised there is a "bootlock" witch prevents root (I think it does that).
So I tried ODIN and installed a custom FMW and it worked, allso I instaled a custom twrp and boot win.rar file. and there is the problem.
Every time I hold the power buton the samsung logo apears for 5 seconds and then goes black. It wont take any commands. I tride the recover meny to open, no it wont, but I can restars it to boot again and fails every time.
I tried to do it from a youtube tutorial and maby I know what I did wrong. I Instaled a Sm-j320h boot on my smj320fn so I think thats the problem. Any whay how do I fix this. All and any solution are good.