http://forum.xda-developers.com/galaxy-s5/general/sm-g900f-root-android-5-0-t2963451
Soon...
Are you saying we can't root?
I personally havent ever seen that post as i just stick mainly to the tmobile board, not the unified board.
But i have root on DOB1.
Just use odin (3.07) and flash the CF-Auto-Root for the G900T ( even though the link on the CF-auto-Root website says for 4.4.2)
I just got the phone, it was updated to Lollypop, I would rather put a rom on it anyways, do I need to revert back or something? some help would be nice, I am new to this Tmobile phone.
joachim123 said:
I personally havent ever seen that post as i just stick mainly to the tmobile board, not the unified board.
But i have root on DOB1.
Just use odin (3.07) and flash the CF-Auto-Root for the G900T ( even though the link on the CF-auto-Root website says for 4.4.2)
Click to expand...
Click to collapse
That's what I thought. I usually just flash a recovery and flash super su.
I rooted my device just fine after updating to 5.0 with the cf auto root for kitkat... worked like a charm on lollipop 5.0
So does any twrp recovery .
Sent from my Tmobile S5 on Lollipop 5.0
SuperSU installed but no SU
Hi,
Just installed the DOB1 build, installed Philz recovery which worked OK and also installed the SuperSU ZIP through recovery (UPDATE-SuperSU-v1.94.zip) .
Everything seemed fine. I launched several applications (BusyBox, Titanium Backup, terminal emulation) and all of them prompted SuperSU to grant root permission and I acknowledged the permission. SuperSU app itself says that root is enabled.
BUT - it seems that even though SuperSU believes it gives root permission - it does not. The apps keeps asking (and "granted" root per the toast message) but they do not get root and keep asking for that after 30 sec. or so.
I also tried terminal emulation. At the shell prompt I've entered "su", immediately I've got the prompt to allow root, I clicked OK and the in the terminal emulation the cursor just got stuck. never got the "#" prompt for root access.
If someone was able to actually grant root access to the apps, can you please share the steps you've done that? following the posts through Philz' recovery and root did not help, I did follow the same steps I've done before upgrading to lollipop...
Thanks,
Gil.
---------- Post added at 02:30 PM ---------- Previous post was at 02:19 PM ----------
gilbnx said:
Hi,
Just installed the DOB1 build, installed Philz recovery which worked OK and also installed the SuperSU ZIP through recovery (UPDATE-SuperSU-v1.94.zip) .
Everything seemed fine. I launched several applications (BusyBox, Titanium Backup, terminal emulation) and all of them prompted SuperSU to grant root permission and I acknowledged the permission. SuperSU app itself says that root is enabled.
BUT - it seems that even though SuperSU believes it gives root permission - it does not. The apps keeps asking (and "granted" root per the toast message) but they do not get root and keep asking for that after 30 sec. or so.
I also tried terminal emulation. At the shell prompt I've entered "su", immediately I've got the prompt to allow root, I clicked OK and the in the terminal emulation the cursor just got stuck. never got the "#" prompt for root access.
If someone was able to actually grant root access to the apps, can you please share the steps you've done that? following the posts through Philz' recovery and root did not help, I did follow the same steps I've done before upgrading to lollipop...
Thanks,
Gil.
Click to expand...
Click to collapse
Sorry guys! My mistake, I didn't use cf-autoroot. I just ODIN'ed the autoroot and now all is well!
Please anyone who's taken the update (via OTA or by flashing the full DOB1 tar) and then rooted and installed custom recovery: if you've since installed custom Roms, please head over to this thread and let us know how you did it, what steps you took, etc.
http://forum.xda-developers.com/tmobile-galaxy-s5/general/warning-flashing-bootloader-modem-t3037034
Thanks much!
Related
(I cant post to the original thread, but im hoping someone here can help me please?)
Ive rooted 6 or so different android phones mainly using cf-autoroot, including an i9300, and never had any issues. But I have had a few issues rooting my 9503 using the cf-autoroot method (method #1 in this post). It aooeared to work, but SuperSU subsequently fell over, and Knox complained but after reading other posts I rectified that, but obviously not quite correctly:
After using cf-autoroot, SuperSU DID NOT appear in the apps list, but Google Play said it was installed but only presented the option to open it (not update or remove).
So I then tried flashing twrp (as per method #2 in this post) which all appeared to go successfully according to Odin. I was expecting to install superSU updater, as per step 3, but recovery mode appeared unchanged/stock so of course I couldnt flash anything as there was no option to do so. Yet there were no errors reported by Odin?
So I then got hold of the app file for SuperSU 1.93 and installed it (via Airdroid). It ran. It found knox. It removed it, and root was installed successfully (as verified by root checkers, titanium backup, droid wall and the like). So I concluded I had successfully rooted my 9305.
But when I reboot SuperSU falls over again on boot up, and the version I added via Airdroid has disappeared, and of course there is no root mode.
But I can then restore root access after a reboot simply by following the same process, namley installing the supersu apk via Airdroid.
Can anyone suggest what is the easiest way to get round this, or even why it's happening? And why is the later version of SuperSU disappearing on reboot?
non persistent SU after rooting Android 4.3 - solved
OK, so Im still unsure how I ended up successfully rooted ,but then reverting back to a non-working or incompatible SU version on reboot (presumably the version installed via cf-root?). It's news to me that an app installed via standard means can be overridden for any reason on reboot. One day someone might explain that or tell me the appropriate phrase to use for my friend google so he can explain it to me.
So what I was then trying to do was install a custom recovery so I could flash the latest SU, as per OP. Try as I might I cant. Even removing the battery once TWRP has been transferred using Odin the standard recovery still prevails. So that one is still unresolved.
But in the meantime, as with most well written apps, the answer is within SU itself. Going into Options in the Su installed via the standard app installer, I selected the option to install that SU as a binary. And it worked, so now SU persists across reboots.
Just in case someone else has the same issue, although judging by all the replies I suspect not (or maybe everyone else is able to post to the original thread, although I dont see this exact problem or solutio there).
If it didnt help anyone, sorry for wasting your time!
Hi,
I have the same problem : my root is lost after each reboot.
I must uninstall SuperSU, then update SuperSU end reboot to have the root again.
Could you give me your solution with simple words because I don't understand what you posted befort. Sorry for my bad english ...
Thanks.
Hello guys, I am new to XDA. I've been reading a lot of forums before I decided to register. So, here is my dilemma... I have a Sprint Galaxy Nexus and tried to root it. I rooted it successfully but when I open SuperSU it says something about SU Binaries couldn't be found or old. I downloaded Superuser from the Play Store and that says my SU binary is out of date. When I click on Recovery Install nothing happens. Root Checker says i still have root access. Xposed Framework and GravityBox work like normal. When I clicked on SuperSU again, it said the same thing and this time, after that Root Checker said I have NO root access, but GravityBox and my other Xposed modules still work fine when changing stuff like status bar clock or something. Titanium Backup doesn't work at though, its stuck on "Asking for root rights" I don't know what to do! I don't wanna brick my phone but I want this fixed. Anybody got suggestions?
srv2D said:
Hello guys, I am new to XDA. I've been reading a lot of forums before I decided to register. So, here is my dilemma... I have a Sprint Galaxy Nexus and tried to root it. I rooted it successfully but when I open SuperSU it says something about SU Binaries couldn't be found or old. I downloaded Superuser from the Play Store and that says my SU binary is out of date. When I click on Recovery Install nothing happens. Root Checker says i still have root access. Xposed Framework and GravityBox work like normal. When I clicked on SuperSU again, it said the same thing and this time, after that Root Checker said I have NO root access, but GravityBox and my other Xposed modules still work fine when changing stuff like status bar clock or something. Titanium Backup doesn't work at though, its stuck on "Asking for root rights" I don't know what to do! I don't wanna brick my phone but I want this fixed. Anybody got suggestions?
Click to expand...
Click to collapse
Do you have a custom recovery installed? If not, you should. If you do, then you should be able to just install the latest zip from Chainfire to get your binaries up to date and working properly.
Install this via custom recovery (CWM or TWRP) http://download.chainfire.eu/396/SuperSU/UPDATE-SuperSU-v1.94.zip?retrieve_file=1
I have TWRP v.2.1.2 installed, and I also put on a different su binary I found on a website that said modified for Android 4.3 devices, before I did that I didn't have root access even when I tried too
srv2D said:
I have TWRP v.2.1.2 installed, and I also put on a different su binary I found on a website that said modified for Android 4.3 devices, before I did that I didn't have root access even when I tried too
Click to expand...
Click to collapse
UPDATE: Thank you so much! I installed this and now SuperSU works just fine, Titanium Backup works fine, and I can still use GravityBox!:laugh:
:highfive:
As the title states, I'm trying to root my phone using towelroot, yet everytime that it runs all it does is reboot my phone which according to the splash screen for towelroot, says that it's unsuccessful. How do I go about correcting this?
breakneat said:
As the title states, I'm trying to root my phone using towelroot, yet everytime that it runs all it does is reboot my phone which according to the splash screen for towelroot, says that it's unsuccessful. How do I go about correcting this?
Click to expand...
Click to collapse
Have you downloaded SuperSU yet? I had the same issue until I did. I think I remember that was the solution.
Here are the complete instructions for rooting with Towelroot, not much to it.
http://forum.xda-developers.com/showthread.php?t=2784138
breakneat said:
As the title states, I'm trying to root my phone using towelroot, yet everytime that it runs all it does is reboot my phone which according to the splash screen for towelroot, says that it's unsuccessful. How do I go about correcting this?
Click to expand...
Click to collapse
Install SuperSU and busybox onto your phone before you try towel root, these will install but not set up. make sure you have usb debugging turned on, then try it again. SuperSu will bond with towel root and then ask to turn off knox...knox is trying to block it. You need SuperSu and then busybox running. if you get it rooted you'll be able to update SuperSu and set up busy box...maybe rom tool box, lucky patcher blackmart alpha, and rom manager after you get rooted too.
I had an instance where towel root said it worked and apps were saying I still needed full root access, so I used kingo android root to finish over it.
you can also try kingo android root (your decision and you own risk) it worked for me most times without any crap installed. even the chinese version rooted my phone but it puts its own program and SU, but if you already have SuperSU and busybox installed, the SuoerSu will uninstall those other SU apps and still have root. (your decision and you own risk).
Idk what those programs are that the post above me refer to, but all I did is download selinux mode changer and set to permissive, then use towelroot. See if that helps any
Sent from my SAMSUNG-SGH-I337 using XDA Free mobile app
@ryant35: Thanks for the insight, I had it downloaded, and I was following that guide - it didn't mention installing SuperSU until the device is rooted ( and SafeStrap installed )
@Neontc: SELinux Mode changer depends upon the device already being rooted from what I read on the download page. I'll give it a shot though.
If anyone knows how to fool TowelRoot into thinking that it's online, I'd be very happy to hear that news. I'm going to be out to sea without internet for my phone for about a month, and I'm still actively trying to root my phone...
Thanks again for the quick responses, and I'll try to update when I can as far as what's happened and how I fixxed it!
Maybe I am wrong more than likely I am but I was under the impression that busybox was included somehow with the towel root install. I went with the towel root first then came back with the su after the root was installed after I checked to make sure the root took using root checker from the play store. Jesse
Sent from my SCH-I545 using XDA Free mobile app
So I have a Starmobile Quest which is a local smartphone and I rooted it using a chinese rooting program called iroot, formerly vroot, as suggested by people using the same phone. At first the superuser app(which is a Chinese one) is working fine and I could use apps requiring root access but suddenly, something happened and now it won't give root access to any of the apps. I think, maybe root was somehow removed, and downloaded the root checker app and when I ran it, it told me that I wasn't rooted.
So I unrooted my phone using iroot and it was successful and again rooted it which was again successful. I go and run root checker again and I was surprised to see that I wasn't rooted. From there I repeated the unrooting and rooting process several times and still nothing. What I did notice was that whenever iroot was checking whether my phone was rooted, a pop up would appear on my phone which is from the superuser app asking for permission to give "shell" root access and I would always say yes.
I believe that my phone is actually rooted but the superuser app isn't promting me for root access whenever I use apps that require root, plus there is no log saved except for the "shell" one. I tried changing root access manager app to supersu and when I run it it tells me that it needs to update su binary. I click yes and use the normal method(I don't have cwm) and it tells me it's installing but after awhile I receive an error saying "installation failed. try rebooting.". I reboot my phone and try updating again and it still fails.
I tried everything the internet threw at me, reroot, factory reset, clear data, clear cache, etc and nothing's working. Can someone help me here?
Note: I can't find a stock/custom rom for my device. So flashing roms isn't an option for me.
Bump.
have you tried to flash another version of superuser?
Crom4rtie said:
have you tried to flash another version of superuser?
Click to expand...
Click to collapse
How do I do that?
black_fire21 said:
How do I do that?
Click to expand...
Click to collapse
go to your recovery and go to install zip ..choose your zip ..or just download supersu from the playstore
Crom4rtie said:
go to your recovery and go to install zip ..choose your zip ..or just download supersu from the playstore
Click to expand...
Click to collapse
Do you need a custom recovery for that? Because the model of the phone doesn't have a custom recovery yet.
Also, I tried to install supersu from the play store and it didn't work.
black_fire21 said:
Do you need a custom recovery for that? Because the model of the phone doesn't have a custom recovery yet.
Also, I tried to install supersu from the play store and it didn't work.
Click to expand...
Click to collapse
yes you need a custom recovery...but if the su from the playstore didn´t work then will this also not work
Crom4rtie said:
yes you need a custom recovery...but if the su from the playstore didn´t work then will this also not work
Click to expand...
Click to collapse
Damn it. I guess I'll have to wait till they make a stock rom which I think isn't gonna happen since it's been half a year since the phone is released and there hasn't been any development.
Last question, Is it possible to flash your phone using a computer?
black_fire21 said:
Damn it. I guess I'll have to wait till they make a stock rom which I think isn't gonna happen since it's been half a year since the phone is released and there hasn't been any development.
Last question, Is it possible to flash your phone using a computer?
Click to expand...
Click to collapse
Yes absolutely. Just note that there are no rooting apps on the Play Store. Simply downloading SuperSU or Superuser will NOT root your phone. You need to be rooted first, and if the SuperSU or Superuser app isn't automatically installed, then once you root you can install SuperSU or Superuser to manage apps that require root.
Popular methods of rooting include z4root, framaroot, MTKTools and iroot (or vroot)
Z4root and framaroot are both android applications which you will need to get from their sites or XDA (just run a search). MTKtools and iroot/vroot are computer applications and use ADB. MTKTools can also create a custom recovery for your device, though I don't remember the process too well.
Once you're rooted you will either have your Superuser app installed or you'll have to install it yourself (I personally prefer SuperSU). I also recommend installing busybox as well.
Hope that helps.
Don't forget to hit the thanks button if I helped you~
SeraphSephiroth said:
Yes absolutely. Just note that there are no rooting apps on the Play Store. Simply downloading SuperSU or Superuser will NOT root your phone. You need to be rooted first, and if the SuperSU or Superuser app isn't automatically installed, then once you root you can install SuperSU or Superuser to manage apps that require root.
Popular methods of rooting include z4root, framaroot, MTKTools and iroot (or vroot)
Z4root and framaroot are both android applications which you will need to get from their sites or XDA (just run a search). MTKtools and iroot/vroot are computer applications and use ADB. MTKTools can also create a custom recovery for your device, though I don't remember the process too well.
Once you're rooted you will either have your Superuser app installed or you'll have to install it yourself (I personally prefer SuperSU). I also recommend installing busybox as well.
Hope that helps.
Don't forget to hit the thanks button if I helped you~
Click to expand...
Click to collapse
So how do I do that?
Hello my buddy so I 've read your thread, there are many apps to do root like root master, framaroot, towel root, towelpieroot. And the way to install super su is doing again the root. And after to install it again.
These apps to do root.
YAMALILLO JR said:
These apps to do root.
Click to expand...
Click to collapse
Okay so some of those do. But not all are supported anymore.
---------- Post added at 04:47 AM ---------- Previous post was at 04:11 AM ----------
black_fire21 said:
So how do I do that?
Click to expand...
Click to collapse
So MTKTools can be found scattered all over XDA, and Framaroot has a dedicated thread (which I cannot link right now as I am on my phone). If memory serves, Jellybean and below had Dev options enabled by default. If not, go to settings -> About Device and tap on the build number several times until your dev options are enabled. Then simply enable USB debugging. When you plug in your device you may need to authenticate your PC to use the Debug bridge. Just hit accept. (I'm sure that you were aware of how to enable ADB but I felt I had to explain anyway)
I assume you have the ADB drivers for your device, but if not, there is a naked USB driver installer floating around XDA (I really would only trust XDA with stuff like this)
With ADB enabled you can use the iroot and MTKTools PC applications. Both are generally straightforward but don't hesitate to ask me if you have a question.
With the APK apps you can get from XDA and abroad, you can root the device somewhat easily.
Framaroot (last time I used it) has four options for rooting (latest version is 1.9.3) you will see all info you need on that thread.
Z4 root I do not recommend. It is somewhat outdated now, though you might want to try it as a last resort
Towelroot is fairly simple as well. Simply download and run the app and you'll either get root or you won't.
My personal recommendations are MTKTools for a pc toolkit (seeing as it can compile a custom recovery too, which it did for my Lenovo S6000)
For apk rooting, I suggest Framaroot. I've never had any problems with it thus far.
I hope that explained it enough but if not, don't hesitate to ask questions. After all, you never learn if you don't ask ^-^
Nevermind guys. I downloaded a bunch of rooting programs and tried them. Root Genius worked and now I have root access. Thanks for replying to this thread.
ReInstall SuperSU and check with Android Terminal Emulator.
Ok dudes just i share this thread, cuz i like to help other dudes that they are juniors or they're beginning .
I know this model is new, but how do we start a section for this model? It's a great phone with plenty under the hood. It seems to have an unlock oem bootloader option in the developer options. How can I root this phone, but more importantly, are there any custom ROMs which will work with it? Can there be some ported over? Any assistance appreciated.
This is the ZTE Warp 7 N9519 for Boost Mobile
:highfive:
GrimeSyndicate said:
I know this model is new, but how do we start a section for this model? It's a great phone with plenty under the hood. It seems to have an unlock oem bootloader option in the developer options. How can I root this phone, but more importantly, are there any custom ROMs which will work with it? Can there be some ported over? Any assistance appreciated.
This is the ZTE Warp 7 N9519 for Boost Mobile
:highfive:
Click to expand...
Click to collapse
I have this phone it seems unrootable. Help?
I know i have tge same device....someone getthis phone and help us...im stuck in the same spot.
I'm on the same page. Spent a few hours on trying to find a working root method but no success. However, King root, specifically version 4.1.0.703, worked for a bit then after close to 30 minutes, the phone restarted itself and was unrooted. I decided not to try it again especially since I just got this phone yesterday.
I have this phone too... Been all over the forums, all over xda university, and im still lost... If someone could give me a little direction, custom recovery or root access... Do i have to build from source? That seems a little above my pay-grade
so has anyone found a solution for rooting?
i looked at XDA a while back when i first got the phone but nothing.
ive been doing reaserch and placing my findings in a different androidforums.(website)
since i didnt see any options to post on here.
anyone wanna help us with info?
KingRoot works after a couple of tries, root access verified, but phone will reboot anywhere from 30 seconds to 30 minutes and root access is denied upon phone start. Haven't tried anything fancy in the little time I've had root access, then again I am not sure this phone is even compatible with custom recovery nor does it have any development of custom roms.. Wondering why the phone reboots and removed root, set SELinux to permissive to no avail, maybe there's a security package or two that could be disabled/blocked to prevent the phone from removing root access?
Really good phone for the money and the specs lend well to a debloated/custom ROM.. Not giving up on these lesser loved phones, finally got my S550TL rooted thanks to the helpful members here don't want to stop now lol.
Caddykings1987 said:
KingRoot works after a couple of tries, root access verified, but phone will reboot anywhere from 30 seconds to 30 minutes and root access is denied upon phone start. Haven't tried anything fancy in the little time I've had root access, then again I am not sure this phone is even compatible with custom recovery nor does it have any development of custom roms.. Wondering why the phone reboots and removed root, set SELinux to permissive to no avail, maybe there's a security package or two that could be disabled/blocked to prevent the phone from removing root access?
Really good phone for the money and the specs lend well to a debloated/custom ROM.. Not giving up on these lesser loved phones, finally got my S550TL rooted thanks to the helpful members here don't want to stop now lol.
Click to expand...
Click to collapse
Have you tried installing the su file with SuperSu before the device rebooted. Because when I had root for less than 10 minutes I checked to see if there was a su file installed and there wasn't any. Is like if KingRoot was simulating root access and didn't install the su file.
---------- Post added at 04:07 PM ---------- Previous post was at 04:01 PM ----------
Heartseed said:
I'm on the same page. Spent a few hours on trying to find a working root method but no success. However, King root, specifically version 4.1.0.703, worked for a bit then after close to 30 minutes, the phone restarted itself and was unrooted. I decided not to try it again especially since I just got this phone yesterday.
Click to expand...
Click to collapse
You should try installing the su file with SuperSu because KingRoot doesn't really install the su file and when the device reboots it removes all root access that KingRoot was simulating. I recommend getting root access with KingRoot then installing the su file with SuperSu and see if it works.
Has any one tried adding SuperSu after temp KingRoot? Or tried adding SuperSU and replacing KingRoot with Super-Sume Pro app?
Just tried Rooting with KingRoot thru APK and didn't even temp root
shezzy83 said:
Has any one tried adding SuperSu after temp KingRoot? Or tried adding SuperSU and replacing KingRoot with Super-Sume Pro app?
Just tried Rooting with KingRoot thru APK and didn't even temp root
Click to expand...
Click to collapse
If KingRoot is not temp rooting your device just go to recovery and clear cache then it should work. Also I wanted to update the su file with SuperSU when I had temp root but I fear it might brick or something. I found out the su was located at sbin.
Are we getting anywhere on this? I really like this phone but i need to de-bloat
drgsrbad81 said:
Are we getting anywhere on this? I really like this phone but i need to de-bloat
Click to expand...
Click to collapse
Not really, I just need someone to update the su binary with SuperSU once temp rooted with KingRoot to see if after that the root doesn't remove after reboot. Or maybe moving the Su file to xbin or bin since it is at sbin.
Tried to install binary through Chainfire SuperSU app and got the "binary update failed" message.
Weird how KingRoot simulates root access without installing any SU binaries, I was able to disable a few packages and verify root access through other apps until the phone restarted.
Can you flash an SU binary through flashify or similar app without restarting to bootloader/recovery (where root access is once again revoked)?
hmmm....thinking of using this as my next phone can anyone give info on a working Fastboot Mode? if there is then we can maybe do the same method of flashing a custom TWRP recovery in order to flash SuperSU
Really like this phone, just got it yesterday. I tried the temp root with kingroot and then after 5 or 10 minutes it rebooted. I'm a bit hesitant to download Flashify and try flashing as I do not know what will happen. But its a good start we have an entry point to work with :silly:
Caddykings1987 said:
Tried to install binary through Chainfire SuperSU app and got the "binary update failed" message.
Weird how KingRoot simulates root access without installing any SU binaries, I was able to disable a few packages and verify root access through other apps until the phone restarted.
Can you flash an SU binary through flashify or similar app without restarting to bootloader/recovery (where root access is once again revoked)?
Click to expand...
Click to collapse
Actually it does install a su binary because when I go to sbin I see a su file there
I was able to confirm root after rooting with kingroot and i tried replacing it with SU but it fails and reboots. I'm very new to ZTE as this is my first phone. I wouldn't think obtaining permanent root would be super difficult since we are able to get some sort of root with king. I am no code expert either so I remain in the dark...
mycosmicmind said:
I was able to confirm root after rooting with kingroot and i tried replacing it with SU but it fails and reboots. I'm very new to ZTE as this is my first phone. I wouldn't think obtaining permanent root would be super difficult since we are able to get some sort of root with king. I am no code expert either so I remain in the dark...
Click to expand...
Click to collapse
So I noticed something very helpful that will totally or maybe allow us to have permanent root. When I rooted with KingRoot I went to Superuser and it said that su binary can't be updated because of its location /sbin/su, so that shows that the su file needs to be at /xbin or /bin. We can try moving the su file to /xbin or /bin once we have temp root to see if it becomes permanent.
---------- Post added at 09:14 PM ---------- Previous post was at 09:13 PM ----------
So I noticed something very helpful that will totally or maybe allow us to have permanent root. When I rooted with KingRoot I went to Superuser and it said that su binary can't be updated because of its location /sbin/su, so that shows that the su file needs to be at /xbin or /bin. We can try moving the su file to /xbin or /bin once we have temp root to see if it becomes permanent.
i can try tomorrow, i dont know if i'll be able to do it before a reboot though
mycosmicmind said:
i can try tomorrow, i dont know if i'll be able to do it before a reboot though
Click to expand...
Click to collapse
The average is about 5 minutes that it allows you to have root, sometimes it let's you even more but it reboots.