Related
I received a message yesterday to update. I did so and then realized some of the rooted features were not working. It said i had granted superuser permission, but i would get the message saying your phone is not rooted. I tried rooting again and when it got to the bottom line it said something like "failed file already exist" and then "Your Phone is Rooted!"
I guess at this point I would like to unroot and maybe wait for the 2.3.6 root.
I originally used the 1 click exploit method not the superoneclick.
Any help would be greatly appreciated.
Thanks
Info currently on Android version:2.3.6
System version: 55.13.25.mb865.ATT.en.US
Same. Kinda worried, not sure if a lot of rooted stuff is working. Can't really tell. Kind of regret updating.
EDIT:
SetCPU app tells me that it is having trouble accessing 'permissions'. I can't change the CPU or do anything in that app.
Superuser app seems to say that it is 'allowed' though.
Yes. I regret the update now as well. I was'nt thinking when I did it. Superuser will show they are allowed, but they don"t really seem to be fully functional. If you delete a rooted app and reinstall it will not be shown in Superuser. I just want to unroot and wait fo a better option.
I'm not going to 'do anything' about this right now because I feel like a lot of these updates are helpful (like no more carrierIQ according to some post in the atrix 2 forum for this site, and less end call lag). Going to wait and see if someone finds a root exploit for this. Just kinda bummed about not being able to use SetCPU now.
I'm good with the update. At this point I would like to remove the root that isn't really a root anymore. I do miss titanium backup.
Ok, need some major advice re: this OTA update..
I've got the Atrix 2, obviously...and when i got it, i did the one click root, then immediately installed titanium backup and did a full backup to my microsd card. Then i started yanking out all the bloatware. Thats about all i did. No weird mods, etc...
Now im getting this notice that there is a OTA update, i download it, but it has an error when it installs and keeps nagging me about the update.
What does everybody suggest I do at this point? If I restore my phone using the titanium backup, will that allow me to get the update? I'm guessing the error is caused because the OTA is trying to update apps that I removed.
And if I do that and it works... will my phone still be rooted? Or will I have to re-root?
I'm new to this and ANY help or ANY advice would be GREAT.
Please, let me know something =)
~bobby
[email protected]
this is my first time on the XDA dev forums, so please speak slowly and be kind
I also had Titanium backup. I did the upgrade and it did not recognize the root after the upgrade. Therefore Titanium back up was not accessible. I also have not found a way to root the atrix 2 now that it is upgraded to 2.3.6. When I try the "1click exploit" method to root it goes through the process and says its already rooted, but I have no super user capabilities. Let me know if you find a solution. Otherwise if the root for titanium back up is important to you I would hold off on the upgrade for now.
When you did choose to do the update, did it give u errors until u restored your phone back to stock? What I mean is, did you have any errors installing the update when it first rolled out?
Because I have tried to do the update when it first came out, but it downloads, gets about 1/3 of the way installed and then give me an error and reboots. I'm thinking the only way to get past that is to use my titanium backup and put back all the stuff I took off right? Cause I made my backup IMMEDIATELY after I rooted my phone.
Root is important to me, and this stupid update isnt, but I also don't like being nagged about it every time I turn around.
I dunno what to do. :/ Im honestly kinda angry that they would do this and screw up root access for those of us who have it.
Sorta makes me wonder if that was part of the whole idea to begin with.
---------- Post added at 06:25 PM ---------- Previous post was at 06:08 PM ----------
Also, I just found this article. I haven't been a member here long enough for it to allow me to post links to the outside world, but just google these keywords: theandroidsoul, update atrix 2 to 2.3.6 OTA with root retained.
It gives these instructions:
Compatibility
This guide has been specifically written for the Motorola Atrix 2. Do not try to attempt it any other device as it may cause issues with your device. Check your device model number in: Settings » About Phone
How To Apply 2.3.6 OTA Update on the Atrix 4G, with Root retained
Download and Install OTA Rootkeeper on your Atrix 2
Launch OTA Rootkeeper, and Select ‘Create SU backup‘
Once SU backup is completed, Select Temp Unroot .
Now exit OTA Rootkeeper
Uninstall the Superuser app. In case you have Superuser Elite installed, uninstall that too.
Now uninstall OTA Rootkeeper. The backup you created through OTA rootkeeper in Step 2 above will still be retained, so don’t worry.
Now go ahead and download the 2.3.6 OTA update to the phone and apply it
Once the update is complete, reboot the phone. Once it has rebooted, power-cycle the phone ( Switch it off and power it back on after a minute)
Once the phone has booted back up, install OTA Rootkeeper and Superuser again
Launch OTA Rootkeeper, and Select Restore Root. This should bring up a superuser permission prompt, Accept it.
Now reboot the phone.
That’s it!! You have updated to the latest 2.3.6 OTA, and are also rooted.
______________
I am thinking about trying this. Using Titanium backup to get my phone back to how it was right after I rooted it, then following this guide, and then doing the OTA update.
Anybody see any holes in that plot before I go do something stupid?
~bobby
Bobby Anderson said:
When you did choose to do the update, did it give u errors until u restored your phone back to stock? What I mean is, did you have any errors installing the update when it first rolled out?
Because I have tried to do the update when it first came out, but it downloads, gets about 1/3 of the way installed and then give me an error and reboots. I'm thinking the only way to get past that is to use my titanium backup and put back all the stuff I took off right? Cause I made my backup IMMEDIATELY after I rooted my phone.
Root is important to me, and this stupid update isnt, but I also don't like being nagged about it every time I turn around.
I dunno what to do. :/ Im honestly kinda angry that they would do this and screw up root access for those of us who have it.
Sorta makes me wonder if that was part of the whole idea to begin with.
---------- Post added at 06:25 PM ---------- Previous post was at 06:08 PM ----------
Also, I just found this article. I haven't been a member here long enough for it to allow me to post links to the outside world, but just google these keywords: theandroidsoul, update atrix 2 to 2.3.6 OTA with root retained.
It gives these instructions:
Compatibility
This guide has been specifically written for the Motorola Atrix 2. Do not try to attempt it any other device as it may cause issues with your device. Check your device model number in: Settings » About Phone
How To Apply 2.3.6 OTA Update on the Atrix 4G, with Root retained
Download and Install OTA Rootkeeper on your Atrix 2
Launch OTA Rootkeeper, and Select ‘Create SU backup‘
Once SU backup is completed, Select Temp Unroot .
Now exit OTA Rootkeeper
Uninstall the Superuser app. In case you have Superuser Elite installed, uninstall that too.
Now uninstall OTA Rootkeeper. The backup you created through OTA rootkeeper in Step 2 above will still be retained, so don’t worry.
Now go ahead and download the 2.3.6 OTA update to the phone and apply it
Once the update is complete, reboot the phone. Once it has rebooted, power-cycle the phone ( Switch it off and power it back on after a minute)
Once the phone has booted back up, install OTA Rootkeeper and Superuser again
Launch OTA Rootkeeper, and Select Restore Root. This should bring up a superuser permission prompt, Accept it.
Now reboot the phone.
That’s it!! You have updated to the latest 2.3.6 OTA, and are also rooted.
______________
I am thinking about trying this. Using Titanium backup to get my phone back to how it was right after I rooted it, then following this guide, and then doing the OTA update.
Anybody see any holes in that plot before I go do something stupid?
~bobby
Click to expand...
Click to collapse
To answer the first part. I downloaded the update when I recived the message. I wasnt thinking about it giving problems with the root. I had no issues at all with the download. just the root not working afterwards.
The second part sounds like it might work for you, but it must be done before you update. It is too late for me to use this method. If i could unroot it, which I haven't found a way yet. I would try the method to save the root.
At least you thought about the upgrade and the root before thinking "oh boy an update lets do it", like I did. Now I'm stuck with a phone that thinks its rooted, but wonn't grant superuser permissions and won't take another root.
OTA failed
I ran into the same thing, downloaded the OTA today and run the update, really without thinking about the implications ('nother stupid n00b here : )). Interestingly it failed immediately and I still have root, I don't have any idea why it failed except maybe Superuser blocked the OTA packages SU access, is that even possible?
Anyway,,,Has anyone tried the OTA Rootkeeper procedure? I would like to have the update, because of stability issues, but I want to keep root more than I want the update.
Thanks
Did not work for me I back up to SD Card and used Titanium Back up and after the update cant get anything to work. Guess I have to wait until one of the experts comes up with anoter 1-Click_Exploit or Exploit (Manual). I'm new at all this and know just enough to be dangerous:-(
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
(FYI, this is my first android device so i'm a noob to this world, but I have some experience in the iphone jbreaking)
SITUATION: Ok, so I picked up a TF300 US model, with ICS 9.4.3.17 on it. Reading up all over the forums for help and did the following: used sparky's guide and used the Sparkyroot.apk tool, along with Superused.apk and VoodooOTArootkeeper, and it worked great! Thanks to the "Allaboutandroids dotcom" youtube user guide.
My plan is to stay on stock OS. I do NOT want to unlock. (keep warranty and such)
I'm into retro gaming mostly and I don't think I need custom ROMS to enjoy most apps. I would like to moderately overclock the CPU, if that's available without unlocking.
THREE QUESTIONS:
1. So i'm reading that to do the future updates and eventually JBean, that I need to let it do the OTA (that's the tablet requesting to update without me manually selecting it right?) and I will lose root, but SHOULD be able to restore it, without unlocking correct?
2. HOW/WHERE is my root backed up to and how can I extract it to my PC, in case I need to copy it back over after an update. (I have a microsd card in the tf300 as well)
3. Before I do an OTA update, should I do anything?
4. Can I somehow just jump to the latest JB update, or does the tablet need to do incremental updates starting with 9.4.3.18 (or whatever is after .17)
Thanks again for any advice forum people. Regarding question 3. I hear people saying I need to do stuff in Voodoo AND/OR install SuperSU. (Not just Superuser.apk
Great forum and helped my decision to get one of these. Just hoping now I can get my wife to stop nagging me for not getting a 2.5X as $$$ iPad! (under $250 for NEW TF300 16gb. Yay!)
So just as an update, I ran root checker and everything is good and in green. I have superuser installed but NOT SuperSU (I guess it's one or the other but not both, and i'm not sure what the difference is between them)
But when I go to update superuser binaries, it fails at the first step (downloading manifest) every time. I have shut down/restarted so that's not it.
I also ran superuser update fixer 1.2, and it says that everything is fine.
I read that binaries should be updated before allowing an OS update so any thoughts on next steps? The goal is to get jellybean up and running and NOT permanently lose my root. (while still keeping the bootloader unlocked, which it currently is)
I've hooked it up via usb to laptop and gone to the googleplay store and found superuser (in case I had a old version) but it always states "This application is not compatible with your TF300 device" and refuses to install it that way. Could try hunting on the net for a loose .apk version of it, if that's what I need.
Thanks!
Just get supersu (a lot more reliable than superuser) and run it right after installing, it will update the binaries. Then make sure your root is backed up with ota rootkeeper. Once you have done those things you can update through the notification on the pad. I'm not sure if the updates are incremental, but they might be, so just in case between each update restore root with ota rootkeeper run supersu and reboot before going to next update, also always make sure your root is backed up. Good luck, once you are on jb there's no way on getting rooted without unlocking as of yet, so I repeat myself make sure your root is backed up wit ota rootkeeper and you have supersu before updating.
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
jgaf said:
Just get supersu (a lot more reliable than superuser) and run it right after installing, it will update the binaries. Then make sure your root is backed up with ota rootkeeper. Once you have done those things you can update through the notification on the pad. I'm not sure if the updates are incremental, but they might be, so just in case between each update restore root with ota rootkeeper run supersu and reboot before going to next update, also always make sure your root is backed up.
Click to expand...
Click to collapse
Thanks jgaf for the help!
So when I do the "backup" with rootkeeper, it's actually 'saving' the root but temporarily turning it off right? And doing an update doesn't wipe my device, so rootkeeper SHOULD be there correct? So to do a system update (when I click on the bottom right and see the brightness adjust and enable wifi, etc, there is a message saying a system update is available. That is the OTA update correct? Before I do that, I need to run rootkeeper and click the "temp save root", and it basically turns off root access but saves it from being wiped off with the new update right?
I've read that some people say to activate some optional "prevent root loss due to update" feature on Superuser. Does supersu have/need that?
And last, if I switch from Superuser to SuperSU, how do I safely switch over? Do I delete Superuser, and then download/install superSU, or install both on the device and then do some kinda remove or update?
I read that by doing the update methods you decscibed, I can basically keep my root on jellybean without being unlocked. (but it's tricky and some users lose the root regardless) Guess there's not one 100% "rooted and locked" foolproof method yet.
So far this method is working but i've only had one OTA update offered and that bumped it from .17 - .30. So that's not JellyBean yet. Hopefully the rootkeeper and supersu reapplying method will continue to work like this. Thanks!
You don't really need to temp unroot for updates, just make sure that everything is checked in rootkeeper. Sorry I took so long to answer, but those switching from superuser to supersu you need to install supersu and run it before removing superuser.
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
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
Hi all,
I am having problems with my phone and its starting to drive me crazy. I have a ZTE N817 (Obama phone) which I rooted and flashed TWRP to about 8 months ago. The rom is stock because I've never been able to find any custom roms. I used the kingoroot PC application to root the device (the app I've found that was able to root it), and replaced kinguser with supersu. Everything worked great, or at least as good as one can expect from a device with such lown spec hardware.
About a week ago I opened my busybox installer (Busybox Pro (Stericson) and I noticed the app said either I didn't have root or I needed to update the supersu binary. I had the most recent supersu binary but I reinstalled it and updated the binary anyway. The binary updated fine. Busybox still said I didnt have root. I then down loaded a root checker app from the store, it said I had root and my busybox installation was fine. I opened a few more apps that require root (titanium backup, root explorer, etc) all said the device was not rooted. I installed a couple more root checkers, both said the device was not rooted but one said busybox was installed and the other said it wasnt. The first root checker app still said the phone was rooted and busybox installed.
Whenever I run an app that requires root, I get the popup from supersu asking me to grant root access. I grant it but then the apps just tell me that they are unable to get root access and my device is not rooted. I reinstalled kingoroot on my PC and ran it to root the phone again. It said it ran successfully, supersu installed fine and updated the binary. Still no change in anything. I tried to use kingoroot to unroot the device (just so I could root it again) but kingoroot was unsuccessful, but it says it has no problems rooting it.
At this point I have no idea what is going on or how I can get root access back. Any help or ideas anyone may have will be greatly appreciated.:highfive: Like I said, its seriously starting to drive me nuts. :crying::crying:
Happy Memorial Day to everyone!
jritt said:
Hi all,
I am having problems with my phone and its starting to drive me crazy. I have a ZTE N817 (Obama phone) which I rooted and flashed TWRP to about 8 months ago. The rom is stock because I've never been able to find any custom roms. I used the kingoroot PC application to root the device (the app I've found that was able to root it), and replaced kinguser with supersu. Everything worked great, or at least as good as one can expect from a device with such lown spec hardware.
About a week ago I opened my busybox installer (Busybox Pro (Stericson) and I noticed the app said either I didn't have root or I needed to update the supersu binary. I had the most recent supersu binary but I reinstalled it and updated the binary anyway. The binary updated fine. Busybox still said I didnt have root. I then down loaded a root checker app from the store, it said I had root and my busybox installation was fine. I opened a few more apps that require root (titanium backup, root explorer, etc) all said the device was not rooted. I installed a couple more root checkers, both said the device was not rooted but one said busybox was installed and the other said it wasnt. The first root checker app still said the phone was rooted and busybox installed.
Whenever I run an app that requires root, I get the popup from supersu asking me to grant root access. I grant it but then the apps just tell me that they are unable to get root access and my device is not rooted. I reinstalled kingoroot on my PC and ran it to root the phone again. It said it ran successfully, supersu installed fine and updated the binary. Still no change in anything. I tried to use kingoroot to unroot the device (just so I could root it again) but kingoroot was unsuccessful, but it says it has no problems rooting it.
At this point I have no idea what is going on or how I can get root access back. Any help or ideas anyone may have will be greatly appreciated.:highfive: Like I said, its seriously starting to drive me nuts. :crying::crying:
Happy Memorial Day to everyone!
Click to expand...
Click to collapse
you have twrp still?
install latest supersu.zip
Sent from my XT1096 using Tapatalk
sd_shadow said:
you have twrp still?
install latest supersu.zip
Sent from my XT1096 using Tapatalk
Click to expand...
Click to collapse
Yes, I still have TWRP. If I install supersu from the play store without the binary installed the app will tell me immediately after opening that my device is not rooted and it won't work. If I flash the binary through TWRP first, then supersu installs from the play store no different than if the device was still rooted, but I still don't have root. I get the toast notifications whenever an app requests access, but of course it is unable to grant it. I am still on the exact same version of Android as when I got the phone, nothing other than apps themselves have been updated. I have zero idea how I lost root, and even more confusing to me is why I cannot reacquire it. Again just last night, I tried Kingoroot (what I originally rooted the device with), Dr Fone, iRoot, eRoot and Framaroot. Every one failed.:crying: It's a real pain in the rear because the phone's hardware is so lacking that root access is needed just to make the device somewhat usable. I have not ever been able to find a custom rom despite searching all over many times. But last night I was thinking, since I stil have TWRP if I can find someone else with the same handset with root....could I flash a backup of their stock rom? Would that work?:fingers-crossed: I'm becoming extremely frustrated
jritt said:
Yes, I still have TWRP. If I install supersu from the play store without the binary installed the app will tell me immediately after opening that my device is not rooted and it won't work. If I flash the binary through TWRP first, then supersu installs from the play store no different than if the device was still rooted, but I still don't have root. I get the toast notifications whenever an app requests access, but of course it is unable to grant it. I am still on the exact same version of Android as when I got the phone, nothing other than apps themselves have been updated. I have zero idea how I lost root, and even more confusing to me is why I cannot reacquire it. Again just last night, I tried Kingoroot (what I originally rooted the device with), Dr Fone, iRoot, eRoot and Framaroot. Every one failed.:crying: It's a real pain in the rear because the phone's hardware is so lacking that root access is needed just to make the device somewhat usable. I have not ever been able to find a custom rom despite searching all over many times. But last night I was thinking, since I stil have TWRP if I can find someone else with the same handset with root....could I flash a backup of their stock rom? Would that work?:fingers-crossed: I'm becoming extremely frustrated
Click to expand...
Click to collapse
which Supersu.zip zip are you using?
Sent from my XT1254 using Tapatalk
sd_shadow said:
which Supersu.zip zip are you using?
Sent from my XT1254 using Tapatalk
Click to expand...
Click to collapse
The one I used last night was SR3-SuperSU-v2.79-SR3-20170114223742.zip.
jritt said:
The one I used last night was SR3-SuperSU-v2.79-SR3-20170114223742.zip.
Click to expand...
Click to collapse
Here are some things to check.
Maybe you need to make sure you have root access in developer options set to "apps and adb".
Make sure you have a root explorer and that it is enabled.
Check SELinux to see if it's set to "enforcing" or "permissive", set it to permissive if you can.
You might need to use SuperSU in "systemless mode"
Yes, in theory, a rooted backup from someone else should work.
Sent from my SM-S903VL using Tapatalk