Hi Guys,
I'm new to android, this is my first realy android device and I thought I was doing pretty good on my own till the crap hit the fan and now I'm just stuck and have no idea what to do next, any help would be appreciated.
So, I bought an infinity and got it rooted (using Debugfs) just fine, updated to JB and all was well till the .25 update came out which failed to work OTA, I had to side load the update which worked but it killed my root, I was told on the transformer forums that there was no way to root JB and I would have to downgrade to the .30 IC firmware.
I downgraded to .30, did a factory reset just to be on the safe side and ran Debugfs again to root, it did its thing and said my root was successful, although it didnt ask me if gid and uid were 0 but then I dont think it did the first time I did it either. I then installed root checker to verify the root, ran it and hit the check root button it then says:
Please wait for root check to complete the system appears to be running very slow" (not sure what that's about)
After a while it says that I do not have proper root access.
I tried doing a reset again and running the root again to no avail.
Also the system does not appear to be seeing the OTA updates, it hasnt notified me of a new update yet so thats just a little icing on the cake.
If anyone could help me figure this out I would greatly appreciate it.
Can you verify you're on ICS in settings/about tablet?
Sounds like the downgrade may have not happened.
Thank you for the reply,
Yes android version is 4.0.3 and build is 9.4.5.30
u50r said:
Yes android version is 4.0.3 and build is 9.4.5.30
Click to expand...
Click to collapse
Super user installed ok with debugfs right?
Ok so this is really weird, I opened up the superuser app to see if it worked, it didnt list anything in the app when I opened, I then closed it and went to run root checker again so I could tell you everything it said and this time it asked me fo allow super user acccess (which it didn't do before) and it worked, says I have root...what do you make of that?
I installed GMD gesture control to see if it works and it does, also installed OTA root keepr to see if it would protect the root and it did.
But I still am not getting the OTA updates, even when I check for them manually in the settings it says there are no updates and without OTA I cant preserve my root, right?
u50r said:
Ok so this is really weird, I opened up the superuser app to see if it worked, it didnt list anything in the app when I opened, I then closed it and went to run root checker again so I could tell you everything it said and this time it asked me fo allow super user acccess (which it didn't do before) and it worked, says I have root...what do you make of that?
I installed GMD gesture control to see if it works and it does, also installed OTA root keepr to see if it would protect the root and it did.
But I still am not getting the OTA updates, even when I check for them manually in the settings it says there are no updates and without OTA I cant preserve my root, right?
Click to expand...
Click to collapse
Well, if OTA is not working, it's going to be a pain in the As***, you need to manually upgrade using dlpkgfile incremental upgrade method can be found here http://forum.xda-developers.com/showthread.php?t=1803090 Good luck! It recommended that you do .16, then 18, then .20, then .23, then .25 ...(once you hit .18, you can skip directly to .25, but some reported didn't work, but you could give it a try).
buhohitr said:
Well, if OTA is not working, it's going to be a pain in the As***, you need to manually upgrade using dlpkgfile incremental upgrade method can be found here http://forum.xda-developers.com/showthread.php?t=1803090 Good luck! It recommended that you do .16, then 18, then .20, then .23, then .25 ...(once you hit .18, you can skip directly to .25, but some reported didn't work, but you could give it a try).
Click to expand...
Click to collapse
Hmm Ok, no way to just get it to start seeing the updates again? Its probably just a file somewhere that has a bad build version or something, no?
Also a couple stupid questions, I looked through that tutorial and there are a couple things it didnt explain (unless I missed it) but where do I get dlpkgfile files? or do I have to do something with the firwmare zip?
Also I searched for other tutorials on this subject and one said I have to temp disable root before I run it? is that true?
u50r said:
Hmm Ok, no way to just get it to start seeing the updates again? Its probably just a file somewhere that has a bad build version or something, no?
Also a couple stupid questions, I looked through that tutorial and there are a couple things it didnt explain (unless I missed it) but where do I get dlpkgfile files? or do I have to do something with the firwmare zip?
Also I searched for other tutorials on this subject and one said I have to temp disable root before I run it? is that true?
Click to expand...
Click to collapse
OK, it's a mystery, some can take OTA , some just won't do it, no matter what you do to it. So back to the update, you need to download the dlpkgfile from here http://forum.xda-developers.com/showthread.php?t=1926147
Well that second tutorial was much more helpful but as is my luck it didnt work, I did everything as specified but when it went to update all I got was the green android dude on his back with a red triangle and a excalamtion mark, just my luck.
u50r said:
Well that second tutorial was much more helpful but as is my luck it didnt work, I did everything as specified but when it went to update all I got was the green android dude on his back with a red triangle and a excalamtion mark, just my luck.
Click to expand...
Click to collapse
So you have the dlpkgfile (no extention, version .16, IF IT NAMED DIFFERNTLY, MAKE SURE RENAME BACK TO dlpkgfile) copied to /cache/ (Make sure this directory is empty before copy)
and command file (command with no extention, IF IT'S ZIP YOU MUST UNZIP FIRST) copied to /cache/recovery/ (There should be only 2 files in this directory, "last_install" and "last_log"
Turn off your device, then boot into recovery and wait a bit it should starts updating.
Your final should look like this before you shutdown your device: (no extention, file names have to be exact as below)
/cache/dlpkgfile
/cache/recovery/command
Yep did all that, I tried downloading the dlpkgfile from a different mirror and that seems to have done the trick, I'll keep trucking here and see if I can burn through a few of these updates, gonna be a long night lol.
I really do appreciate your help though, so Thank You!
buhohitr said:
once you hit .18, you can skip directly to .25, but some reported didn't work, but you could give it a try
Click to expand...
Click to collapse
Every specific dlkpgfile is the update from exactly one version to exactly another version. IF you have a dlkpkgfile that updates from .18 to .25, you can do that, but you need the correct dlpkgfile for that. Such files do exist, but I haven't seen them available here on xda. Someone even mentioned he has a dlpkgfile that updates directly from 9.4.5.30 to 10.4.4.25 - if you use that, you can (and must) do everything in one step.
Well I'm happy to say that after heaps of fun installing all the incremental updates everything works and I'm still rooted so we can declar victory and distribute experience points accordingly.
Thanks again for all your help, would have still been messing with this thing if it wasnt for your insight.
Related
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
I need some help, I have been trying to root my Verizon Razr XT912 running Device Software Version: 98.72.165.XT912.Verizon.en.US with the only tool I can find to use on DROID_RAZR_Utility_Jellybean_XT912_WinMacLin
Can anyone guide me in the right direction? thanks
Did you extract tool to desktop and then open it? It will give you all the instructions you need. Make sure you have USB debugging on too.
http://www.youtube.com/watch?v=XDV_72mPt4k
http://droidrazrroot.com/droid-razr-root/how-to-upgrade-to-and-root-jelly-bean-on-droid-razr/
There are two links that might be helpful to you. Hope it helps.
I lost root upon this last Verizon upgrade to 98.72.165. I think it was 98.72.16 before this weekend's update. I am going to try and go back to the original JB (98.72.16), enable root and hopefully find some type of rootkeeper utility that will stop this craziness. I can keep you posted if this works as I don't know what else to do. I use the Tasker application and most of my tasks are not functioning.
Everything worked well. I was able to reinstall the 98.72.16 image and then I applied root. So, I am back at the point before the upgrade of the software. I have root back and just completed a full titatium backup. Now, I need to figure out what others are using to keep root enabled so when a software update is applied I do not lose root. Anyone who can suggest what they use would be helpful.
To the first person who posted, I may be able to walk you through what I did and we can then learn what others are doing to keep root together.
98.72.165.en.US version
I am rooted. Haven't changed from the Moto/Verizon JellyBean update (4.1.2) but have deleted a lot of the programs I don't like or use. When I've tried to let the 98.72.165.en install it starts, then the Droid animation goes "belly up" with a "!"
I know others with root have installed it and I wouldn't mind having the update since I do travel within Canada about once a year. But, if I can't get it to install, then how do I tell the updated I don't want this? It's getting a bit tiresome to tell the installer "Not Now" every twelve hours.
Anybody have an answer?
fredlpage said:
I am rooted. Haven't changed from the Moto/Verizon JellyBean update (4.1.2) but have deleted a lot of the programs I don't like or use. When I've tried to let the 98.72.165.en install it starts, then the Droid animation goes "belly up" with a "!"
I know others with root have installed it and I wouldn't mind having the update since I do travel within Canada about once a year. But, if I can't get it to install, then how do I tell the updated I don't want this? It's getting a bit tiresome to tell the installer "Not Now" every twelve hours.
Click to expand...
Click to collapse
mwyarm said:
Everything worked well. I was able to reinstall the 98.72.16 image and then I applied root. So, I am back at the point before the upgrade of the software. I have root back and just completed a full titatium backup. Now, I need to figure out what others are using to keep root enabled so when a software update is applied I do not lose root. Anyone who can suggest what they use would be helpful.
To the first person who posted, I may be able to walk you through what I did and we can then learn what others are doing to keep root together.
Click to expand...
Click to collapse
How did you go back to 98.72.16?
Can you show me the steps please?
I was able to successfully root my phone after the update without a re-flashing or a wipe with Matt's Utility.
I followed the instruction in the link below. However, once I put the phone into BP Only mode, nothing happened. I let it sit there for about 5 minutes, then rebooted it normally and finished the exploit. It rooted the phone just fine.
http://mobility.forumsee.com/a/m/s/p12-9245-0620611--root-after-ota-165.html
I'm currently on NI1, and I just had a update notice. It's about 392mb in size. Didn't see anything about any updates so figured I'd post.
Did you take the update? Did it install? If so what is the firmware listed as?
Since it is 392mb I would assume it is an update, rather than a full version increment? Probably still 4.4.2 Let is know
It's almost done downloading now at 81%. I'll post back with a version once installed.
Are you rooted right now? If so it may not install, or try and fail. If you are rooted immediately after it finishes downloading you can copy the update file to your sdcard/external sdcard and upload it to a file sharing site. If it is in fact a newer version of firmware you could make devs happy. If you need to know how/where the update is located I can help you out
BEFORE IT INSTALLS open up a file browser (if rooted possibly) and navigate to \cache\fota\2400258.cfg. Should be the name or something similar. Long press on it and choose copy. Then navigate to you sdcard and paste it where you can find it. Then upload it to a sharing site.
Not rooted on this S4. The update went through and it was updated to NJ1 4.4.4
dankhar said:
Not rooted on this S4. The update went through and it was updated to NJ1 4.4.4
Click to expand...
Click to collapse
Thanks, hopefully SOMEONE will pull it soon.
Yeah. Been having random issues with my phone since the previous. All seems to be good now. The update does add a few new programa. Nothing worth using except maybe keeper. But so far so good.
Phones definitely a lot snappier now.!
I would love to see a screenshot of the about to confirm.
There you go.
Update failed on my rooted device
I just tried it, It failed to update and I lost root.
Here is a screen of the few apps it put on once completed. It also added a kids mode app.
If ANYBODY is rooted it most likely WILL FAIL. It is only 300+ MB sobitbis not a complete ROM and most like just has mostly PATCH files inside. I would recommend users that are rooted WAIT until a dev can do something with it, and check it out. Each update has locked our phones down harder.
On that note if ANYONE is rooted and downloads it, do NOT install it. But go to the location I listed above to pull the file from the phone and upload it to a sharing site. Then a dev can look into it first and incorporate it for our rooted phones WITHOUT updating the bootloader
After looking around the forums it looks like Samsung has pushed a few updates to phones ( S4 getting 4.4.4, S3 4.4.2 patch files, and the Note has gotten an update as well). I think these updates are probably going to be the final updates before they phase out old devices and possibly start porting 5.0 on our device (S4). I really wish there wasn't new At&t bloat, but hopefully these are new services that phase out all the old outdated bloat At&t had in the past :good: also to each his own I just never use those apps.
Thanks for posting this, I would've enjoyed this if I hadn't already flashed Goldenfinger and nandroided all my apps over... to lazy to use Safestrap again.
DON'T INSTALL IF YOU'RE ROOTED!
Nice. Wasn't doubting the OP. I see att has updated their support page to reflect the NJ4 update.
RockRatt said:
Are you rooted right now? If so it may not install, or try and fail. If you are rooted immediately after it finishes downloading you can copy the update file to your sdcard/external sdcard and upload it to a file sharing site. If it is in fact a newer version of firmware you could make devs happy. If you need to know how/where the update is located I can help you out
BEFORE IT INSTALLS open up a file browser (if rooted possibly) and navigate to \cache\fota\2400258.cfg. Should be the name or something similar. Long press on it and choose copy. Then navigate to you sdcard and paste it where you can find it. Then upload it to a sharing site.
Click to expand...
Click to collapse
If no one else does, I will try when I get to work tomorrow. We have numerous S4's that people traded in for the S5. I can see if I am able to root one and do the update using your instructions. If not I can check to see if onw of our Kiosks can allow me to pull the update. Not sure if they have that one yet for self updating. Will let you know in the AM.
dankhar said:
If no one else does, I will try when I get to work tomorrow. We have numerous S4's that people traded in for the S5. I can see if I am able to root one and do the update using your instructions. If not I can check to see if onw of our Kiosks can allow me to pull the update. Not sure if they have that one yet for self updating. Will let you know in the AM.
Click to expand...
Click to collapse
Thanks. Hopefully a dev can create a ROM for us all
Rooted S4
RockRatt said:
Thanks. Hopefully a dev can create a ROM for us all
Click to expand...
Click to collapse
Wish I had read this before. I am rooted so it said install interrupted after download. So do I have to unroot and return to stock? I am on NI1 4.4.2. Maybe you or someone can get copy for us to install it by. Let us know what to do if rooted to get the OTA. Thanks
Downloading now. I'll post when done. Rolled back to NB1 before updating so this is a 489MB download.
guut13 said:
Downloading now. I'll post when done. Rolled back to NB1 before updating so this is a 489MB download.
Click to expand...
Click to collapse
Guess I will roll back to NB1 also Friday. Got NB1 downloading now. Do I need to wipe or Anything before I flash file in Odin 3.09????
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 was downloading the new update 5.0 but it stopped and now the tablet says me "your system is updated" but with the 6.0.1.I can't restart the download now,what i have to do???
Same thing happened to me. Don't know why yet.
Same here. Where are you from?
Nvidia might have pulled it to fix something wait patiently it will come.
I had a similar problem as well. I got the notification to download the update, and when I clicked on the "Download" button in the notification, it did nothing. When I went into my settings and opened the OTA updater, it kept telling me that "Your system is up to date," even after repeatedly pressing the "Check Now" button, selecting "Clear data," rebooting, and messing with the advanced settings. I hope they fix this soon, I was really excited about this update!
Exact same issue here.
If you haven't root/twrp etc:
Download from here:
https://forum.xda-developers.com/shield-tablet/general/5-0-update-nougat-incoming-t3553612/page2 (there are two version - k1 & standard).
Paste it to internal memory, boot into recovery and apply update from zip.
Just wait a little. That's what NVIDIA calls "staggered rollout".
Just wanted to update and say that I got my OTA this morning and will apply it later this afternoon. Guess, just as suggested earlier, they staggered them. It's strange though that they actually pulled it back, but then again it might have been an issue with it.
if you have "nougat launcher apk" just delete it.
Been a while since I rooted mine and I'd prefer not to lose root. Anyone know if there's going to be a pre-rooted version available that won't require going through the whole process again? Honestly I don't recall if it was difficult or not but I know for previous phones I've had there was a rooted version of the OTA that someone would post within a day or two of the release. Made the whole update process quicker and easier.
Also, for those who have updated, how is the performance compared to Marshmallow?
My 2 cents: if the root is confirmed to work, there is no "process" per se.
D/L the root zip to the tablet, boot into recovery, flash that zip and reboot into system.
Should be within 2-3 min the whole thing.
Wayno-san said:
Been a while since I rooted mine and I'd prefer not to lose root. Anyone know if there's going to be a pre-rooted version available that won't require going through the whole process again? Honestly I don't recall if it was difficult or not but I know for previous phones I've had there was a rooted version of the OTA that someone would post within a day or two of the release. Made the whole update process quicker and easier.
Also, for those who have updated, how is the performance compared to Marshmallow?
Click to expand...
Click to collapse
Performance feels good so far. Don't know if there will be a pre-rooted version, but it's fairly simple and fast to root since your bootloader is unlocked and you'll get to keep all your data. If you want custom recovery I had to use the TWRP app after root to flash the recovery. Couldn't get it to stick using fastboot. There's a good rooting guide here:
http://nvidiashieldzone.com/shield-...ndroid-7-nougat/root-shield-tablet-k1-nougat/
pucka said:
Performance feels good so far. Don't know if there will be a pre-rooted version, but it's fairly simple and fast to root since your bootloader is unlocked and you'll get to keep all your data. If you want custom recovery I had to use the TWRP app after root to flash the recovery. Couldn't get it to stick using fastboot. There's a good rooting guide here:
http://nvidiashieldzone.com/shield-...ndroid-7-nougat/root-shield-tablet-k1-nougat/
Click to expand...
Click to collapse
Thanks for the info and the guide link. If I'm rooted can I let the update to nougat proceed and then just follow the procedure in the link? Thought I read somewhere that I need to unroot it first.
Wayno-san said:
Thanks for the info and the guide link. If I'm rooted can I let the update to nougat proceed and then just follow the procedure in the link? Thought I read somewhere that I need to unroot it first.
Click to expand...
Click to collapse
Yes you can just apply the update and there's no need to flash stock first. If you want to flash TWRP I would recommend getting root first by sideloading (like in the guide) and then using the TWRP app to flash TWRP.
I'm now rooted again with TWRP as custom recovery.