I think the problems started ever since I rooted the device. That's the only thing I can think of. I will say that I only rooted it, I did not freeze or remove any apps, install anything or otherwise modify the system. I haven't even installed a recovery yet.
Is it possible the root made my system unstable? What do you guys suggest I do to try and fix this problem?
Thanks
Sent from my GT-N5110 using xda app-developers app
have you tried un-rooting? Anytime you mess with the system it has the potential to make it unstable.
Sent from my GT-N5110 using Tapatalk HD
I installed software on mine which changes color balance and runs as a service.
When it was running, the device crashed occasionally.
Once I uninstalled it, the behavior stopped.
Rooting probably doesn't create a problem, but try uninstalling any software you've added, then stepwise walk through adding in apps.
I've also seen some apps create lockups for the camera app.
theraker007 said:
I will say that I only rooted it, I did not freeze or remove any apps, install anything or otherwise modify the system. I haven't even installed a recovery yet.
Click to expand...
Click to collapse
Then why did you root? Just waiting for the development to come around?
I'm rooted and haven't seen this issue. Its rebooted once, maybe twice on its own in the 2 weeks or so since rooting.
Yeah I thought we'd have custom roms by now. How do I safely uproot and get back to factory. I would like to wipe everything and start from scratch
SuperSU
Using framaroot.apk with Aragorn exploit, I noticed that the SuperSU option is more stable that Superuser.
I ran into problems with my first Note 8 after I installed XMBC. It would lock up within 10 seconds or so of reboot. I would highly recommend that you take advantage of the root toolkit in this forum, install CWM recovery and make a full backup once you get it behaving again. It is good to have something to go back to if you have unexpected problems!
EDIT: You can flash back a stock image using the toolkit: http://forum.xda-developers.com/showthread.php?t=2251033
well i dont know what the heck is going wrong with the toolkit, but i did everything correctly, installed all the drivers, serial # shows up in the toolkit, checked off developer debugging mode. I tried to flash CWM from toolkit in PDA and everytime i try to go to recovery it just has the stock recovery there not CWM.
I have rooted many mobile devices and flashed numerous ROMS. However I recently purchased a Galaxy Note 10.1 2014 edition and have not been able to get very far in my attempts to root, etc. I have tried Odin and CF-Auto-Root and although it appears to be successful the device is not rooted. I want to install TWRP and then the knox free stock ROM. I am able to push the necessary files to the sdcard with ADB and I can see that the files are in /sdcard using ES File explorer. However when I boot into recovery mode /sdcard is red and at the top of the list and it will not let me navigate to it to install any zip files. I though at first it might be because of the MobileIron I use for company email but I did a factory reset and still have this problem. I just need to root the device so I can use Titanium BU to remove the Samsung apps I don't want. Any help with this would be most appreciated. What do I need to do?
~metafizik
Ultimately I think the first thing I need to resolve is that even though the Odin rooting process appears to be working according to Odin(PASS). The fact is that regardless which combination of Odin 3.07/3.09 and CF-Auto-Root (tried 2 versions) even though Odin says it was successful it turns out the device is not getting rooted. This should be a no brainer but for for whatever reason this device will not root so far.
Bumping this as I have not received any replies. I am hoping that someone has run across a similar situation and can offer some guidance.
Thank you,
~metafizik
metafizik said:
Ultimately I think the first thing I need to resolve is that even though the Odin rooting process appears to be working according to Odin(PASS). The fact is that regardless which combination of Odin 3.07/3.09 and CF-Auto-Root (tried 2 versions) even though Odin says it was successful it turns out the device is not getting rooted. This should be a no brainer but for for whatever reason this device will not root so far.
Click to expand...
Click to collapse
Did you install super su?Did you try to flash twrp.If your not rooted twrp will ask to root.Have you tried to install a root app and see if the permissions pop up?
When you say recovery do you mean the stock one?Im pretty sure i had same problem.It was rooted but i thought it wasnt.
mikep2323 said:
Did you install super su?Did you try to flash twrp.If your not rooted twrp will ask to root.Have you tried to install a root app and see if the permissions pop up?
When you say recovery do you mean the stock one?Im pretty sure i had same problem.It was rooted but i thought it wasnt.
Click to expand...
Click to collapse
This is a very strange deal. As previously stated I have tried various combinations of Odin and CF-Auto-Root and the Odin process completes with PASS. However when I boot the OS and run Titanium it is never able to gain root access and Root Checker says it is not rooted. Unfortunately even after doing a factory reset the MobileIron Admin console at work says it is rooted so I can't use it for company email. I have definitely tripped the Knox bit. Also I want to install TWRP and have pushed the file to /sdcard and can see it there using a file explorer app. However when I boot into stock recovery I cannot see any of the zip files I have copied there. I also tried to flash TWRP with Odin and again it completes with PASS but TWRP never gets installed. And yes I installed SuperSU but did so from the Play Store.
I purchased this device just last week. I am wondering if maybe Samsung has changed things in the past few weeks and locked these friggin things down even more? This is the first device of many I have owned that I couldn't root or install a custom recovery or ROM. In any case this will definitely be my last Samsung device. I would however like to do whatever I so desire with it since I paid good money for it.
I have resolved all of the problems I was having. They were all due to Knox and my inexperience with it. I was fortunate to have customized my Note 2 before it received the Knox updates. All is well and there is no new unknown vodoo lurking in the latest iteration of Samsung devices.
First off, I am completely new to rooting so my apologies if I don't catch on to some of the terms being used.
So the other night, I attempted in starting the process in rooting my n5110 using the Unified Android Toolkit. I got through installing necessary drivers, flashing rom, installing twrp and then when i installed supersu, it had mentioned something about no binaries found. after some searching, I came to the conclusion that it might be the fact that I was on 4.4.2 and it was an incompatibility issue. I then tried cf-auto-root but after the flashing step, I was expecting supersu to work then but it wouldn't even load, just giving me the "supersu has stopped" message every time. So I instead tried a factory reset to try cf-aut-boot again but supersu just wouldn't work. At that point I tried uninstalling supersu but there wasn't even a option available. From reading around, I concluded that my device had to be rooted in order to do that but since I wasn't even able to do that, I got desperate and wiped my whole entire system with twrp which resulted in my os being deleted also...
That being said, I would really like to learn the in's and out's of rooting an android device but before that, if someone could give me a step-by-step process in restoring my device so that I could try rooting it again, that would be greatly appreciated. Then if someone could point me to a guide or site in learning about rooting since I'm such a "newb", that would be wonderful also.
kombobreaker said:
First off, I am completely new to rooting so my apologies if I don't catch on to some of the terms being used.
So the other night, I attempted in starting the process in rooting my n5110 using the Unified Android Toolkit. I got through installing necessary drivers, flashing rom, installing twrp and then when i installed supersu, it had mentioned something about no binaries found. after some searching, I came to the conclusion that it might be the fact that I was on 4.4.2 and it was an incompatibility issue. I then tried cf-auto-root but after the flashing step, I was expecting supersu to work then but it wouldn't even load, just giving me the "supersu has stopped" message every time. So I instead tried a factory reset to try cf-aut-boot again but supersu just wouldn't work. At that point I tried uninstalling supersu but there wasn't even a option available. From reading around, I concluded that my device had to be rooted in order to do that but since I wasn't even able to do that, I got desperate and wiped my whole entire system with twrp which resulted in my os being deleted also...
That being said, I would really like to learn the in's and out's of rooting an android device but before that, if someone could give me a step-by-step process in restoring my device so that I could try rooting it again, that would be greatly appreciated. Then if someone could point me to a guide or site in learning about rooting since I'm such a "newb", that would be wonderful also.
Click to expand...
Click to collapse
Since you already have a custom recovery installed, I would suggest just flashing a rooted rom. The type of rom depends on whether you want 4.2.2 or 4.4.2.
Might start with one of these and can then flash whatever rom you want from that point on:
4.2.2
4.4.2
As for learning about root....each manufacturer has different methods that work. For the Note 8 specifically there are numerous root threads in General and Dev sections that have step-by-step instructions (like CF Autoroot).
thank you for that. I guess i have to do some research now in order to up my rooting game.
I am like you. I only know enough to be dangerous, as I type this, my Note 8 is bricked and am trying to recover it.
As far as your SU concern, you need to turn it into an app. Get the pro version, and towards the bottom, after you open it, you will have this option to make it an app. This should help.
Good luck
Sent from my SGH-I317 using XDA Premium 4 mobile app
If your getting the supersu has stopped error, try downloading the latest supersu apk from the Internet and open the app. You will be asked to update binary and disable Knox. I had to do this twice but it solved my problem. Hope this helps.
---------- Post added at 01:38 PM ---------- Previous post was at 01:36 PM ----------
Also to flash a custom recovery you will want to flash clockworkrecovery through Odin first, and then I would personally suggest flashing Philz recovery.
Ps it's very important you know what Odin is if you're rooting Samsung devices so I would get familiar with it.
First of all I want to thank all the developers on this and all forums, I hope that you prosper in your endeavers...
I have been at this since the sprint mogul came out. Playing around with PPC kitchen and technology keeps getting more 'interesting'...During the s3 root procedure I was fascinated with the Knox and how it was dealt with automatically with Supersu, and how cwm took control of keeping itself as the recovery as well as offering to keep root(such manners!)...
Check your Version # this how to is meant for 4.2.2 ONLY
I believe there was just an update(cause my phone downloaded it and wanted to install) I knew it was time to root again.
This summer I finally upgraded from my beloved Galaxy s1... After many a rom it was victim of a glass of water
spill...Bought a s3 sph-d710 for cheap and have been loving the phone but missing my wifi teather(and text to speech
prowess, why does the s3 stock suck worse than s1 cyanogen 10.2?) so I know I must root.
OOps my volume UP button is
broken! How to I get to downoad mode? to use ODIN! Gueess I gotta Root on the Phone...
ABD? Tried finding the tiny version of abd but after failed downloads and searching for links for the tiny version were
broken so...instead I Installed towel root and followed the guide here
http://gs3.wonderhowto.com/how-to/easiest-one-click-root-method-for-your-samsung-galaxy-s3-0155625/
It was so amazingly easy(you download towelR touch the red Icon or one of the donate links in TR), wait 20 second click make it rain, wait 20 seconds then check with saferoot...(after installing it @ goo.im)! After TR immediately without rebooting install #saferoot(do not attempt to get root with this just install), and install CWM recovery which I did thru rom manager(via google play, I attempted to install from their site but it was a zip and it did not jive with my unpackaging skillsEDIT Drr it was prolly for cwm?). Safe root does something for SuperSU so that it will not hang while removing knox( wait 5 min if it seems to hang then force quit and u prolly did not install saferoot yet so do that and try again)
(EDIT: be sure and install safe root (FROM GOO.IM)after you make it rain with TR and then you install supersu & rom manager.Also Install towelroot and Supersu from their perspective verified real web page not other sources/googleplay) I was freezing at chainfires supersu install after making it rain)but once saferoot is installed it will disable knox(noted above)
I then took out Knox with Supersu simply by opening the program(it will ask you if you want to kill Knox) also it will ask to
update everytime.
Then I Installed the 4g and hotspot fix via CWM recovery via Rom Manager reboot into recovery and I was fully functioning..done! ND8Oxed 4.4.2..
http://forum.xda-developers.com/showthread.php?t=2224083
I Used this post below as a general guide Hope this helps some, click thanks if I did..thanks all!
Happy Camper (rooted, tethered sprint galaxy s3)
Finally, I got my Sprint S3 tether working.
Many thanks to both bilgerryan and jdsingle76.
So just to help out other noob out there, what I did was:
1. root the S3. www idigitaltimes com/samsung-galaxy-s3-android-442-kitkat-update-how-root-sprint-sph-l710-variant-and-install-custom-roms
(Sorry I am not allowed to post links yet)
2. Install a custom recovery. I did not use Philz. I am sure it must be very good. However, I am not very good at using
Odin yet. I used CWM. Installed it directly from play store. There are lots of youtube videos on how to do it.
3. copy the Hotspot ROM zip file to the SD card in the phone. In my case, the ROM is the ND8 odexing version
4. Back up my stock rom (rooted) with the CWM recovery, in case something goes wrong. Lots of youtube videos too.
5. install rom from the zip file using CWM recovery. (again, lots of youtube videos available)
6. factory reset and wipe the cache
7. reboot and setup the phone from scratch.
There you go.
vizionforever said:
First of all I want to thank all the developers on this and all forums, I hope that you prosper in your endeavers...
I have been at this since the sprint mogul came out. Playing around with PPC kitchen and technology keeps getting more 'interesting'...During the s3 root procedure I was fascinated with the Knox and how it was dealt with automatically with Supersu, and how cwm took control of keeping itself as the recovery as well as offering to keep root(such manners!)...
This summer I finally upgraded from my beloved Galaxy s1... After many a rom it was victim of a glass of water
spill...Bought a s3 sph-d710 for cheap and have been loving the phone but missing my wifi teather(and text to speech
prowess, why does the s3 stock suck worse than s1 cyanogen 10.2?) so I know I must root.
OOps my volume UP button is
broken! How to I get to downoad mode?
ABD? Tried finding the tiny version of abd but after failed downloads and searching for links for the tiny version were
broken so...instead I Installed towel root and followed the guide here
http://gs3.wonderhowto.com/how-to/easiest-one-click-root-method-for-your-samsung-galaxy-s3-0155625/
It was so amazingly easy(you touch the red Icon or one of the donate links in TR), wait 20 second click make it rain, wait 20 seconds then check with saferoot as root checker will tell you that you are not rooted?! After TR immediately without rebooting install #root checker, and supersu and CWM which I did thru rom manager.
Strangely #Root checker(upon my request) kept reporting that I did not have root. Curious if root checker was wrong I
nstalled safe root (noted above)and Obviously there is some whole new route to root cause It said I was indeed still rooted, weird!
I then tookout Knox with Supersu simply by opening the program(it will ask you if you want to kill Knox) also it will ask to
update everytime.
Finally I Installed, then opened Rom manager and Installed (VIA ROM MANAGER)!)CWM. Treves wifi tether did not work for me in 4.4.2 so I knew I must install fix via zip in CWM.
Then I Installed the 4g and hotspot fix and I was fully functioning..done! ND8Oxed 4.4.2..
I Used this post below as a general guide Hope this helps some, click thanks if I did..thanks all!
Happy Camper (rooted, tethered sprint galaxy s3)
Finally, I got my Sprint S3 tether working.
Many thanks to both bilgerryan and jdsingle76.
So just to help out other noob out there, what I did was:
1. root the S3. www idigitaltimes com/samsung-galaxy-s3-android-442-kitkat-update-how-root-sprint-sph-l710-variant-and-install-custom-roms
(Sorry I am not allowed to post links yet)
2. Install a custom recovery. I did not use Philz. I am sure it must be very good. However, I am not very good at using
Odin yet. I used CWM. Installed it directly from play store. There are lots of youtube videos on how to do it.
3. copy the Hotspot ROM zip file to the SD card in the phone. In my case, the ROM is the ND8 odexing version
4. Back up my stock rom (rooted) with the CWM recovery, in case something goes wrong. Lots of youtube videos too.
5. install rom from the zip file using CWM recovery. (again, lots of youtube videos available)
6. factory reset and wipe the cache
7. reboot and setup the phone from scratch.
There you go.
Click to expand...
Click to collapse
TowelRoot seems to be broken when it comes to the latest S3 model called the Sph-L710T and i have a guide in this question thread with root info for the Sph-L710 http://forum.xda-developers.com/showthread.php?t=2787771 if you want to take a look at it but thanks for the info
Its finally happened. I picked up my note 8 today from my nightstand and said "why not try" and low and behold, Kingroot 4.1 successfully rooted my Note 8!
Thanks , just download the apk 4.1 version of kingroot and get root acces for 4.4.2
Gracias , solo descarguen el apk version 4.1 de kingroot y listo acceso root para la i467 at&t , que hace tiempo ando buscando
excelente !
Done!!
Just rooted with King root 4.1
Thanks for the heads up on this!
---------- Post added at 09:46 PM ---------- Previous post was at 09:24 PM ----------
EDIT: After rooting with kingroot, I used the app from the Google play store called "SuperSu Me" This app removes king root and installs supersu while keeping root... it took less than a minute to do.
Amazing app
I tried this on two tablets and it failed. Is there specific procedure?
KC
Not sure which version of kingroot you're using, but o.p. specified to use version 4.1.
I downloaded king root v4.1... and ran it... no tricks.
Here is a link that I found to the app for kingroot for you:
https://userscloud.com/33vyymss3kkq
Hope the picture uploaded....I get this screen using 4.1.
Do this first : flash with odin 3.09.3 the original firmware 4.1
: select "AP" choose the at&t firmware it comes with 4.1 android version
then update to kit kat , rename the file on internet called xxxx.cfg to xxxxxx.zip
put this file in your micro sd card, reboot on recovery stock and flash the update , and get 4.4.2 android kk, then , download the apk 4.1 , do not connect the tablet online to the website of king root , this method does not work, it is with the apk 4.1 version of kingroot and done!
Importante : tablet on mode developer option and usb debugging check
None of the king root versions I found work. Gets to 24% then reboots.
No luck yet. Will keep waiting.
That was my experience as well. Not sure if this is viable based on my experience.
It's definitely a feasible process, it worked fine for me. I'm really confused why it works for some people but not for others...
For those still trying to gain root access using Kingroot... here is a link to a few different versions of "kingroot", a version of "kinguser" (their version of supersu), and a version of "purify" (their version of a memory manager). If it didn't work easily, it may still work with a bit more trial and error, as it did for me (after losing root yesterday).
https://drive.google.com/file/d/0B3w...ew?usp=sharing
Yesterday morning, i woke up to find that I had somehow lost root on my tablet... I tried to re-root using the previous process, and it no longer seemed to work. Soooo, I spent a good chunk of time figuring out how to get root back yesterday. The good news is, I got root back... the process however, was somewhat convoluted.
So I tried to find a step by step reproduce-able way to get root every time - and I was not successful at coming up with an exact process that works every time... I was however able to get rooted every time, but the process seemed to vary a bit each time... so trial and error seems to be the key here. I experimented for hours doing this... gaining root, uninstalling root, and retrying - all in the name of trying to help others figure out how to do it on their device.
So here is the basics of how I achieved root... DISCLAIMER - I TAKE NO RESPONSIBILITY FOR YOU, YOUR ACTIONS, OR THE FUNCTIONALITY OF YOUR DEVICE - BEFORE/DURING/OR AFTER YOU TRYING ANY OF THESE PROCESSES THAT I TRIED. THINGS CAN GO WRONG - YOU CAN END UP WITH PROBLEMS - A BRICKED TABLET, A DIVORCE, A DEAD DOG, OR HIT BY A NUCLEAR BLAST. ANY OF WHICH, I TAKE NO RESPONSIBILITY FOR. IF YOU PUSH THE BUTTONS, ITS YOUR RESPONSIBILITY.
Since there is no factory image for 4.4.2 on our device, proceed with caution... if something goes really wrong, you will have a paperweight. There is no Kies or Odin to save you... Also, my knox warranty void count shows as 1 and custom device status, so if you are worried about that be aware...
1) download all the files in the folder at the link above, extract them from the folder and put all the apk's on your device, but dont install them yet (doesn't matter internal/external memory)
2) Boot into stock recovery and wipe cache. reboot.
3) Install kingroot v4.0.1.237
4) open kingroot and try the rooting process. the device will likely reboot at around 18 to 25% or so... once the device reboots, open kingroot again and let it finish the rooting process. If it works - you should go buy lottery tickets, because you just got really lucky! If it doesn't work, proceed to the next step.
5) Install Purify. Run Purify process. Take notice after running the process - at the top of the app does it say root is achieved?? If not, return to step 4 and try rooting again. If that does not work...
6) Install kinguser. open kinguser, does it say you have root access? If not, try the prompt to repair root access (if it shows up)... if not, return to step 4, and try to root again. If no root, try step 5 again. If not, try step 6 again...
7) If still no root access, uninstall kingroot, and install one of the other versions of kingroot... try all of the above again. If still no root... uninstall all 3 apps and start over at step 2 using a different version of kingroot to start with.
I wish I could say there was a logical rhyme or reason for what works and what doesn't... but there didn't appear to be an exact process that works every time. Fortunately, I was able to get root if I tried long enough and tried different combinations of processes. Periodically clearing the cache from the stock recovery really seemed to help increase my odds of success when things weren't going well.
Occassionally the process landed me in a bootloop at the at&t screen... after holding the power button for an eternity, the device would power off - then I would reboot and it would boot normally.
Additionally, I tried on many occasions to swap "kinguser" with "supersu" using an app call "Super-Sume". Sometimes the process worked, and successfully removed kingroot, kinguser, and purify - while keeping root and installing Supersu... Other times the process removed the kinguser, kingroot, and purify - but I also lost root. I tried both the paid and free versions of Super-Sume, but the free version is the one that seemed to work best.
It's up to you if you want to go through all of this - it was tiresome... but if you really want root, maybe trying something like this might help you - maybe not. I also noticed that kinguser seems to sometimes have root access, sometimes not... so sometimes it was just a matter of opening one of the 3 apps and re-running a process or two and root would be restored... not sure why that happens - which is why i opted to use super-sume to remove kingroot once root was achieved. but we will see if i keep root now... if not, at least I know the process above seemed to work for me.
Thanks Dandroid, I will try your suggestions. I got this tablet 2 months ago, rooted it right away with Kingroot, worked great. But was suspicious of the app, so used supersume to remove. Had root for a few more days then lost it. My first thought was the Samsung Security updates patched the root. So I download Kingroot and run it again and it doesnt work anymore. Why is root not working? Either the Samsung security updates closed the loophole or somehow Kingroot punishes you for removing their app. I believe Kingroot puts you on a blacklist because they have your IP address and IMEI. These are just my suspicions. So Dandroid do you still have root after all this time?
dandroid7 said:
For those still trying to gain root access using Kingroot... here is a link to a few different versions of "kingroot", a version of "kinguser" (their version of supersu), and a version of "purify" (their version of a memory manager). If it didn't work easily, it may still work with a bit more trial and error, as it did for me (after losing root yesterday).
https://drive.google.com/file/d/0B3w...ew?usp=sharing
Yesterday morning, i woke up to find that I had somehow lost root on my tablet... I tried to re-root using the previous process, and it no longer seemed to work. Soooo, I spent a good chunk of time figuring out how to get root back yesterday. The good news is, I got root back... the process however, was somewhat convoluted.
So I tried to find a step by step reproduce-able way to get root every time - and I was not successful at coming up with an exact process that works every time... I was however able to get rooted every time, but the process seemed to vary a bit each time... so trial and error seems to be the key here. I experimented for hours doing this... gaining root, uninstalling root, and retrying - all in the name of trying to help others figure out how to do it on their device.
So here is the basics of how I achieved root... DISCLAIMER - I TAKE NO RESPONSIBILITY FOR YOU, YOUR ACTIONS, OR THE FUNCTIONALITY OF YOUR DEVICE - BEFORE/DURING/OR AFTER YOU TRYING ANY OF THESE PROCESSES THAT I TRIED. THINGS CAN GO WRONG - YOU CAN END UP WITH PROBLEMS - A BRICKED TABLET, A DIVORCE, A DEAD DOG, OR HIT BY A NUCLEAR BLAST. ANY OF WHICH, I TAKE NO RESPONSIBILITY FOR. IF YOU PUSH THE BUTTONS, ITS YOUR RESPONSIBILITY.
Since there is no factory image for 4.4.2 on our device, proceed with caution... if something goes really wrong, you will have a paperweight. There is no Kies or Odin to save you... Also, my knox warranty void count shows as 1 and custom device status, so if you are worried about that be aware...
1) download all the files in the folder at the link above, extract them from the folder and put all the apk's on your device, but dont install them yet (doesn't matter internal/external memory)
2) Boot into stock recovery and wipe cache. reboot.
3) Install kingroot v4.0.1.237
4) open kingroot and try the rooting process. the device will likely reboot at around 18 to 25% or so... once the device reboots, open kingroot again and let it finish the rooting process. If it works - you should go buy lottery tickets, because you just got really lucky! If it doesn't work, proceed to the next step.
5) Install Purify. Run Purify process. Take notice after running the process - at the top of the app does it say root is achieved?? If not, return to step 4 and try rooting again. If that does not work...
6) Install kinguser. open kinguser, does it say you have root access? If not, try the prompt to repair root access (if it shows up)... if not, return to step 4, and try to root again. If no root, try step 5 again. If not, try step 6 again...
7) If still no root access, uninstall kingroot, and install one of the other versions of kingroot... try all of the above again. If still no root... uninstall all 3 apps and start over at step 2 using a different version of kingroot to start with.
I wish I could say there was a logical rhyme or reason for what works and what doesn't... but there didn't appear to be an exact process that works every time. Fortunately, I was able to get root if I tried long enough and tried different combinations of processes. Periodically clearing the cache from the stock recovery really seemed to help increase my odds of success when things weren't going well.
Occassionally the process landed me in a bootloop at the at&t screen... after holding the power button for an eternity, the device would power off - then I would reboot and it would boot normally.
Additionally, I tried on many occasions to swap "kinguser" with "supersu" using an app call "Super-Sume". Sometimes the process worked, and successfully removed kingroot, kinguser, and purify - while keeping root and installing Supersu... Other times the process removed the kinguser, kingroot, and purify - but I also lost root. I tried both the paid and free versions of Super-Sume, but the free version is the one that seemed to work best.
It's up to you if you want to go through all of this - it was tiresome... but if you really want root, maybe trying something like this might help you - maybe not. I also noticed that kinguser seems to sometimes have root access, sometimes not... so sometimes it was just a matter of opening one of the 3 apps and re-running a process or two and root would be restored... not sure why that happens - which is why i opted to use super-sume to remove kingroot once root was achieved. but we will see if i keep root now... if not, at least I know the process above seemed to work for me.
Click to expand...
Click to collapse
Yes, I still have root.
I recently read in a forum for a different device that king root is actually a temporary root??? I have not seen that said anywhere else, just in that forum, so not sure if that was device specific?? But that does seem to explain why we lost root...
Since I used super-sume to remove king root and retain root, that may be why I still have root. As soon as I installed supersu, I also checked the survival mode box on supersu to try and keep root.
typhoonk said:
None of the king root versions I found work. Gets to 24% then reboots.
No luck yet. Will keep waiting.
Click to expand...
Click to collapse
try this
http://forum.xda-developers.com/galaxy-note-8-0/help/root-sgh-i467-4-4-2-success-t3182211
It's supposed to reboot... after it reboots, reopen the KingRoot app and let it finish the process. The English version of the app clearly says that it will need to reboot and then finish the rooting process.
I used the computer version. Worked prefect. Then unistalled with superseme
Sent from my SAMSUNG-SGH-I467 using Tapatalk
I appreciate everybody's input on this. It seems that some of us have been successful. I however have not.
Is there any way to get a system image from one of you folks that are already rooted, so the rest of us can load in our tablets? I don't know if this is a stupid question I'm not that well versed in loading via Odin.
King root v4.1
It seemed to work fine with my note 8 I'm running sgh-i467 4.4.2 but yet to find any custom rom, when there is one made please let me know! Just rooted today and I love the freedom but would like to learn a lot more about the different stuff I could do with this, any suggestions??
till this newest ver, 46.2, Kingroot never worked on mine but somehow it rooted my device with this new version..
Not sure why, but I love this having root on Note8 now.