Related
Q&A for [Nexus 5] CF-Auto-Root
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [Nexus 5] CF-Auto-Root. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
nexus 5 autoroot: downloading root.img failed
Hi Chainfire, thanks a lot for the program!
I actually just paypal'd you a symbolic euro for all the effort.
But after all, de root did not work completely yet,
after the selection menu 'unlock bootloader YES/NO' (I choose NO btw, will stay with the stockrom for a while),
i get the error message
' downloading boot.img FAILED (command write failed (No such file or Directory) ) '
I don't see anyone else reporting this problem on the thread, so my question: what could cause it? What can I do?
Extra inf:
I am on a windows system (7) and had the trouble with usb-driver that was not installed first, dont know if that influenced it?
flekkie said:
Hi Chainfire, thanks a lot for the program!
I actually just paypal'd you a symbolic euro for all the effort.
But after all, de root did not work completely yet,
after the selection menu 'unlock bootloader YES/NO' (I choose NO btw, will stay with the stockrom for a while),
i get the error message
' downloading boot.img FAILED (command write failed (No such file or Directory) ) '
I don't see anyone else reporting this problem on the thread, so my question: what could cause it? What can I do?
Extra inf:
I am on a windows system (7) and had the trouble with usb-driver that was not installed first, dont know if that influenced it?
Click to expand...
Click to collapse
dont use root toolkits, as you will learn nothing, then think your phone is bricked when it needs some simple upkeep. its a nexus, its easy to root, no toolkits needed, unless you just dont want to learn anything/the basics.
Hi Simms22,
You're absolutely right, thanks for your remark.
Just for the sake of explaining why I tried the toolkit:
I literally just bought the phone (<24h), and I only wanted a quick access to the SU-privileges. I didn't want the unlock the bootloader and go for custom ROMs (yet).
I did this with my previous phone (sony xperia), and all the trouble I had with the process took me 1,5 full days to get the thing running again.
Just to say, I dont want to go all deep into it right now. If I could root my nexus with the tool, that'd be great, but if it isn't possible, I will first explore my new phone as a ordinary user I guess. Going trought all the flashing-nexus-infothreads if for later on.
Thanks for the advice!
flekkie said:
Hi Simms22,
You're absolutely right, thanks for your remark.
Just for the sake of explaining why I tried the toolkit:
I literally just bought the phone (<24h), and I only wanted a quick access to the SU-privileges. I didn't want the unlock the bootloader and go for custom ROMs (yet).
I did this with my previous phone (sony xperia), and all the trouble I had with the process took me 1,5 full days to get the thing running again.
Just to say, I dont want to go all deep into it right now. If I could root my nexus with the tool, that'd be great, but if it isn't possible, I will first explore my new phone as a ordinary user I guess. Going trought all the flashing-nexus-infothreads if for later on.
Thanks for the advice!
Click to expand...
Click to collapse
Unlocking bootloader and using custom ROMs etc on a Nexus is no where near as complicated as it is on a Sony device (or any other) - in regards to if anything goes wrong, it usually takes 5mins or so to start from scratch on a Nexus again compared to Sony/Samsung etc.
Also remember, there is no warranty issues on a Nexus device either. So you can unlock/lock your BL as and when you see fit.
radicalisto said:
Unlocking bootloader and using custom ROMs etc on a Nexus is no where near as complicated as it is on a Sony device (or any other) - in regards to if anything goes wrong, it usually takes 5mins or so to start from scratch on a Nexus again compared to Sony/Samsung etc.
Also remember, there is no warranty issues on a Nexus device either. So you can unlock/lock your BL as and when you see fit.
Click to expand...
Click to collapse
Ok, thanks a lot for your reply. It gave me confidence to try the 'unlock bootloder'-option, which worked like a charm
I am enjoying now the perks of a good titanium-datatranfer; I like!
See you around in a few months when I try custom ROMs!
Device already unlocked?
Hello,
I am also new to gaining root access on android devices, and I could use some help.
I have a Google Nexus 5, and followed the steps using CF Auto Root, but it only says <waiting for device> when started and wont proceed with anything. I have the device in bootloader and it tells me the Lock State is already unlocked. I haven't left CF Auto Root on <waiting for device> for more than 5 minutes, assuming it shouldn't take that long.
So I went ahead and installed SuperSU via Google Play to see what I could do, but SuperSU tells me that there is no SU binary installed, and that if I just upgraded to android 4.3, I will need to manually re-root. However, I have android 4.4.2.
I have used two different root checking applications, but they both told me that my device does not have proper root access.
Superuser also doesn't seem to work. It wont inform me when I try to use an app to perform root access actions.
Any help on what I could do next would be appreciated.
Thanks ~
Valdtun
Valdtun said:
Hello,
I am also new to gaining root access on android devices, and I could use some help.
I have a Google Nexus 5, and followed the steps using CF Auto Root, but it only says <waiting for device> when started and wont proceed with anything. I have the device in bootloader and it tells me the Lock State is already unlocked. I haven't left CF Auto Root on <waiting for device> for more than 5 minutes, assuming it shouldn't take that long.
So I went ahead and installed SuperSU via Google Play to see what I could do, but SuperSU tells me that there is no SU binary installed, and that if I just upgraded to android 4.3, I will need to manually re-root. However, I have android 4.4.2.
I have used two different root checking applications, but they both told me that my device does not have proper root access.
Superuser also doesn't seem to work. It wont inform me when I try to use an app to perform root access actions.
Any help on what I could do next would be appreciated.
Thanks ~
Valdtun
Click to expand...
Click to collapse
Your best bet is to learn to do it manually.
Your next steps are
1) install recovery
2) flash superSU zip from recovery
Recovery is installed by fastboot.
In my signature, is a link to guides and info threads. Click it and then read the thread "adb and fastboot. What is it?"
This will tell you what you need.
Then you can download TWRP recovery image to flash.
Solved
It seems that my driver wasn't very compatible, and now my phone has been successfully unlocked. Thank you for the help.
rootSU said:
Your best bet is to learn to do it manually.
Your next steps are
1) install recovery
2) flash superSU zip from recovery
Recovery is installed by fastboot.
In my signature, is a link to guides and info threads. Click it and then read the thread "adb and fastboot. What is it?"
This will tell you what you need.
Then you can download TWRP recovery image to flash.
Click to expand...
Click to collapse
I rooted my n5 running lollipop but some apps doesnt get the root access... I tried xmodgames ,es file explorer(root explorer option)
Any solution?
Sent from my Nexus 5 using XDA Free mobile app
myliferockkss said:
I rooted my n5 running lollipop but some apps doesnt get the root access... I tried xmodgames ,es file explorer(root explorer option)
Any solution?
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Same here, none of the root explorers I tried seem to work.
Will the latest CF Auto Root wipe the storage on encrypted Nexus 5?
myliferockkss said:
I rooted my n5 running lollipop but some apps doesnt get the root access... I tried xmodgames ,es file explorer(root explorer option)
Any solution?
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Try flashing pie patch. http://forum.xda-developers.com/goo...x-bypassing-pie-security-check-t2797731/page2 (post #13).
If problem still exists, try to install SELinuxModeChanger from the play store and change SELinux mode to permissive.
root
This is not a full root... at least in my nexus 5..
There are thing that I am not aloowed to do like disable startup apps and give some apps# permission
myliferockkss said:
I rooted my n5 running lollipop but some apps doesnt get the root access... I tried xmodgames ,es file explorer(root explorer option)
Any solution?
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Some root apps aren't working on lollipop right now. Root explorer on es file manager is one of these
ravi84m said:
Same here, none of the root explorers I tried seem to work.
Click to expand...
Click to collapse
Search "amaze file manager" on the play store, it works flawlessly
Thanks, pie patch did the trick for me.
I had to use SELinux Mode Changer for viper though.
CF-Auto Root
Relocking the bootloader will not reset your warranty, for that you would have to run CWMbootunlocker script in twrp or cwm or philz. Oh and here is the link to a good thread to explain all that..
http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
---------- Post added at 08:04 AM ---------- Previous post was at 07:56 AM ----------
myliferockkss said:
I rooted my n5 running lollipop but some apps doesnt get the root access... I tried xmodgames ,es file explorer(root explorer option)
Any solution?
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
That is because of new SELinux polices which developers will need to workaround it ..
WARNING WARNING WARNING
You could use SELinux mode changer or run setenforce via term emulator and set it to permissive However!! this allows more malware to have access to your phone basiclly
Want to ROOT my N5, just root it, already unlocked bootloader.
Hi,
I just want to root my nexus 5. I am on Android 5.0, updated during the official rollout, and not using any custom flash/ROM.
Boot-loader is already unlocked, I had rooted it when on 4.4.4 Kitkat, but after I updated to Lollipop, all root priviledges were lost.
I do not want to flash any custom ROM or anything, just want to root it.
I found may threads and guides showing how to root is, but all of them included unlocking bootloader or flashing a custom ROM.
I dont even know what a custom ROM is and what is its use?!?! (noob)
Please just help me root my phone.
Thanks
vvk619 said:
Hi,
I just want to root my nexus 5. I am on Android 5.0, updated during the official rollout, and not using any custom flash/ROM.
Boot-loader is already unlocked, I had rooted it when on 4.4.4 Kitkat, but after I updated to Lollipop, all root priviledges were lost.
I do not want to flash any custom ROM or anything, just want to root it.
I found may threads and guides showing how to root is, but all of them included unlocking bootloader or flashing a custom ROM.
I dont even know what a custom ROM is and what is its use?!?! (noob)
Please just help me root my phone.
Thanks
Click to expand...
Click to collapse
A couple of options:
1. Flash CF-Auto-Root
2. Boot to TWRP recovery and flash SuperSU.zip
Everything is well explained in the main CFAR thread or in the General sticky threads.
Apply update to version 2.37?
Hi all,
I rooted my Nexus 5 running Lollipop some time before with CF-Auto-Root. I think Chainfire still used a patched kernel in this approach and installed SuperSU v2.20.
Afaik Chainfire managed to get root without the need for a patched kernel now. Therefore I would like to update to v2.37. Can I? How? Would the kernel stay patched after using the latest CF-Auto-Root? Do I need to go back to the stock kernel before applying the latest CF-Auto-Root? And how to go back to the stock kernel?
Thanks for your help!
Maik
So what is the easiest way to root stock VZW LP 5.0?? I HAVE read around in the the forums for quite a bit but with all the updates going on to the software and with Sunshine 3.0 recently getting released, I haven't been able to find a solid answer.
I have held off updating, so I am completely stock on 4.4.4, with temp root via Weaksauce. I really only want root to run "Wifi tether router" for when I need it, and maybe uninstall some bloatware, otherwise I actually like stock just the way it is.
I know the update "breaks" root, and there isn't a way as of now to root 5.0, but then I see lots of people that have updated that are rooted.. So if anyone could be so kind as to explain how they are doing that, I would love to know. Is there maybe a Weaksauce 3.0 temproot on the horizon. I would be fine just running the update and waiting on that too as it's really not that big of a deal to go without it for a whlie. Thanks
baune7 said:
So what is the easiest way to root stock VZW LP 5.0?? I HAVE read around in the the forums for quite a bit but with all the updates going on to the software and with Sunshine 3.0 recently getting released, I haven't been able to find a solid answer.
I have held off updating, so I am completely stock on 4.4.4, with temp root via Weaksauce. I really only want root to run "Wifi tether router" for when I need it, and maybe uninstall some bloatware, otherwise I actually like stock just the way it is.
I know the update "breaks" root, and there isn't a way as of now to root 5.0, but then I see lots of people that have updated that are rooted.. So if anyone could be so kind as to explain how they are doing that, I would love to know. Is there maybe a Weaksauce 3.0 temproot on the horizon. I would be fine just running the update and waiting on that too as it's really not that big of a deal to go without it for a whlie. Thanks
Click to expand...
Click to collapse
There's currently no way to unlock the bootloader of an m8 with the lollipop update and s-on. To really root (permanent, not temp weaksauce) you need a custom recovery. What you need to do in your situation is turn s-off while you still have 4.4.4. This is done with sunshine which will turn s-off and unlocks your bootloader. Then you can take the ota. Once on lollipop, since you are still unlocked, you can flash a custom recovery and then flash the binaries from within recovery to give you root access. That well be a "real root" which will persist through a reboot.
now that Jcase has released Sunshine 3.0, and most are having good luck with it, couldn't I take the update, run Sunshine 3.0 sometime later, install a custom recovery, then flash SuperSU from that? Or does it only provide S-off and not unlock the bootloader?
baune7 said:
now that Jcase has released Sunshine 3.0, and most are having good luck with it, couldn't I take the update, run Sunshine 3.0 sometime later, install a custom recovery, then flash SuperSU from that? Or does it only provide S-off and not unlock the bootloader?
Click to expand...
Click to collapse
If you take the update sunshine3.0 will NOT work.
Hi,
Bassically I'm just trying to get my phone to be unrooted to pass SafetyNet (Android Pay, Pokemon Go, and others) but have some system modications (adaway and removed boot sounds mainly).
What I did do is flash stock odin firmware (PG1), then twrp, supersu, and make my changes. Then if I just unroot with supersu it still fails SafetyNet. If I unroot and tell SuperSU to restore boot.img then I get a bootloop. Probably due to TWRP still being there and not stock Recovery? So I thought maybe from there I can just flash boot and recovery via odin but that didn't seem to work either. Is it possible to take the stock firmware and flash whatever I need except system? Or not possible to alter system and go back to stock boot/recovery?
Thanks!
I don't play but here's a link for info
http://www.androidpolice.com/2016/09/11/guide-play-pokemon-go-0-37-rooted-android-magisk/
greco2003 said:
I don't play but here's a link for info
http://www.androidpolice.com/2016/09/11/guide-play-pokemon-go-0-37-rooted-android-magisk/
Click to expand...
Click to collapse
That no longer works to pass SafetyNet. Last couple weeks there have been a couple of root/xposed solutions only for Google to changes SafetyNet and detect it. So I was thinking of just getting rid of root but hopefully keeping the couple system mods I like...
Not much help in here. Anyone know of a way to have a modified system but no root (or recovery if I don't need twrp)? Mainly I'd just like to update my hosts file and remove the stupid reboot "ding".
My hope was to modify system via twrp/supersu and then flash recovery/boot to get it back to stock but there must be some sort of check because that just causes dm-verity failed notification in stock recovery. I can unroot via the SuperSU app but unrooting and telling it to restore stock boot.img causes loop. Unroot and tell it to leave boot.img lets my phone work but still doesn't pass safetynet checks.
All this work makes me miss my HTC phones. They seemed so much easier to manipulate.
This guy's solution lets me have a stock system with some system modifications. So now I have what I wanted, passing Safety Net, removed boot sound and applied adaway hosts file!
http://forum.xda-developers.com/android/apps-games/play-pokemon-root-switch-method-patched-t3483179
@henderjr i found this. Would this work under you're criteria needed??
https://theunlockr.com/2015/09/26/how-to-unroot-the-samsung-galaxy-note-5-t-mobile-sprint-versions/
Im thinking of doing this also.
I know yur post is pretty old bug i just got my note recently but i had no idea there was such a lack in development for sprint version. If u did end up accomplishing unroot with eneabled security, let me know. Thanks
Abu Nazir said:
@henderjr i found this. Would this work under you're criteria needed??
https://theunlockr.com/2015/09/26/how-to-unroot-the-samsung-galaxy-note-5-t-mobile-sprint-versions/
Im thinking of doing this also.
I know yur post is pretty old bug i just got my note recently but i had no idea there was such a lack in development for sprint version. If u did end up accomplishing unroot with eneabled security, let me know. Thanks
Click to expand...
Click to collapse
That will unroot it but you'll also lose all system modifications so it'll be stock again. I wanted adaway hosts file and a couple other system mods. What I posted above did work for me but about six weeks ago I exchanged my Note 5 for a new one (camera died on the old one) and haven't rooted. I enjoy using Samsung Pay so I haven't tripped Knox yet.
henderjr said:
That will unroot it but you'll also lose all system modifications so it'll be stock again. I wanted adaway hosts file and a couple other system mods. What I posted above did work for me but about six weeks ago I exchanged my Note 5 for a new one (camera died on the old one) and haven't rooted. I enjoy using Samsung Pay so I haven't tripped Knox yet.
Click to expand...
Click to collapse
Oh ok. Yep gotcha. Sorry i forgot u said that. Ive been reading so much on these forums in the past couple days im getting myself confused on what ive read and havent. Ok tho thanks alot. Really appreciate the reply tho on these dead forums. Lol. Thanks again
Hey all, sorry if this has been asked before but I searched and was unable to find posts related to my queestion so..
It's been a long while since I have updated my phone, I'm still on KK because I wanted to keep root at the time and so didn't want to go through hassle of updating and trying to get root back etc! But now I am ready to lose root and wondered if I did update using PC Companion from 23.0.a.2.98 to 23.5.A.1.291 (Latest available for me in UK), is this okay and please remind me if I will lose anything? Also, is there a need to delete root first? I seem to remember that if you update it will automatically lose root anyway - but just wanted to double check as I haven't been up to date with firmwares/phone related stuff for almost 2 years now! So am very rusty!
Thanks, hope it makes sense!
P.S - I now also seem to get that super bug with my notification bar not dragging now anymore, and sometimes it will keep coming down sparadically! Another reason why I hope updating may fix it.. Though I doubt it..
Updating still makes loosing root. but if you wanna a rooted Marshmallow, there are many topics that are sharing pre-rooted flashable zips. Just install recovery on your KK then flash latest pre-rooted zip. note that if you update using PC companion you will loose root and you won't be able to root phone. so instead of PC companion, use pre-rooted zip files.
P.S. you will loose guarantee after rooting.
agent.47 said:
Updating still makes loosing root. but if you wanna a rooted Marshmallow, there are many topics that are sharing pre-rooted flashable zips. Just install recovery on your KK then flash latest pre-rooted zip. note that if you update using PC companion you will loose root and you won't be able to root phone. so instead of PC companion, use pre-rooted zip files.
P.S. you will loose guarantee after rooting.
Click to expand...
Click to collapse
Thanks but I think you may have misunderstood my question? I don't want root anymore and just wondered if I needed to delete root before I update from KK to MM using PC Companion? But if I definitely will lose it then that's fine. Also, as I missed a lot of the updates in between, it's a big jump in updates - will this be ok?
SalamiQueen said:
Thanks but I think you may have misunderstood my question? I don't want root anymore and just wondered if I needed to delete root before I update from KK to MM using PC Companion? But if I definitely will lose it then that's fine. Also, as I missed a lot of the updates in between, it's a big jump in updates - will this be ok?
Click to expand...
Click to collapse
oh, sorry.
yes you are right about root and, there is no problem about updates between KK and MM. just for better performance reset your phone or wipe your data and internal storage after update.
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