I have found and tested a root method for the new 4.4.2 update that came out yesterday to the public.
Download Odin https://mega.co.nz/#!fJRkzTQL!uUN3LLhSCXIHtEFUlUDyPdf48rgEXj1wh5mgV5q8TkU
Download this file https://mega.co.nz/#!DdhkzBIZ!2wjBE5cGRnu1hIRuID3o05yjJb_Xe3C6gfEq1LwQn1g
Flash in ODIN and allow to reboot
THIS WILL TRIP YOUR KNOX COUNTER!
**This method is NOT mine. I found this through google searching, and give all credit to that developer, who I now have come to know is @Chainfire.**
Edit: added developers name after searching, so I could give proper credit.
I just used cf auto root that I used to root my phone when i got it with mf9 and it still works for me on 4.4.2 lol.
Sent from my SPH-L720 using XDA Premium 4 mobile app
@churchey360 I think that's what it is. I got all the stuff off of android police. It was meant for the i9505 when the software leaked. I thought I would upload it for everyone who was scared to update because there was no root
Sent from my SPH-L720 using xda app-developers app
Yeah I was scared to try it lol but I saw that one person had success so I did it anyway and it worked first try with no problems at all.
Sent from my SPH-L720 using XDA Premium 4 mobile app
help
This did not work for me it says su binary is missing any ideas?
It's a no-go.... But don't worry.
Downloaded and tried to use auto root file you have linked. Didn't work. In ODIN, gives MD5 sum doesn't match error.
I did try using an old CF-Autoroot that I had, that didn't work either.
I then downloaded it from the CF-Auto-Root Repository site, and viola. Worked like a charm.
I was on MK2, rooted. I had to flash back to MK2 stock, using the file supplied within a tread, (it ain't hard to find), cleared Google Framework and plugged in to charge, checked for Samsung Update. Update to 4.4.2 installed. Had a brief problem when after rebooting and upgrading apps, my screen remained black. I knew it was doing something though because I have pushbullet installed, and was getting the notifications on my PC screen. But a reboot fixed the black screen. I then tried the first two root attempts mentioned above. Then the one from the Repository. Now I'm good to go.
I tried CF autoroot several times and it did not work for me. I Flashed philz recovery and there is an option to reroot your phone and then just download supersu from the playstore. Now works like a charm....
kirschdog1 said:
This did not work for me it says su binary is missing any ideas?
Click to expand...
Click to collapse
When it reboots does it show a red android and text?
Sent from my SPH-L720 using xda app-developers app
lol knox already tripped..... I'll have to give this a try!
If a mod sees this, please close the thread. I suspect that @Chainfire will update his thread soon. And as this is his project I do not want to take his credit. I believe in giving credit where it is due. Great job Devs. Keep up the great work!
Sent from my SPH-L720 using xda app-developers app
needmymorningcoffee said:
Downloaded and tried to use auto root file you have linked. Didn't work. In ODIN, gives MD5 sum doesn't match error.
I did try using an old CF-Autoroot that I had, that didn't work either.
I then downloaded it from the CF-Auto-Root Repository site, and viola. Worked like a charm.
I was on MK2, rooted. I had to flash back to MK2 stock, using the file supplied within a tread, (it ain't hard to find), cleared Google Framework and plugged in to charge, checked for Samsung Update. Update to 4.4.2 installed. Had a brief problem when after rebooting and upgrading apps, my screen remained black. I knew it was doing something though because I have pushbullet installed, and was getting the notifications on my PC screen. But a reboot fixed the black screen. I then tried the first two root attempts mentioned above. Then the one from the Repository. Now I'm good to go.
Click to expand...
Click to collapse
This worked for me too. Downloaded CF Autoroot from Repository and it worked.
Thread closed at OP request.
Related
Hey guys. I got my grouper yesterday, I'm hoping for a warm welcome
The first thing I did when I took it out of the box was fire it up, unlocked and rooted. When I rooted, I flashed SuperSU flashable. I also flashed CWM touch. After that I flashed SmoothROM 4.4, and I was solid. I installed all of my usual apps, then went to do what I call debloating, (Looking for apps I don't use such as voicedialer.apk, and deleting them) using root browser (/system/app). I noticed it wouldn't delete, then tried another app that requires root permissions. Nothing. I got suspicious, then re-downloaded root checker. "Sorry! You're device does not have proper root access!" What happened? Is this just me, or is this a widespread problem with this ROM? I'd like to keep this ROM if possible. Is there a way to re-root my device (more or less)? Thanks, a response or any help would be very much appreciated.
Sent from my Nexus 7 using xda premium
Rom specific questions need to be posted in that rom's thread. Do not start new threads about custom rom issues.
LiquidPlatinum said:
Hey guys. I got my grouper yesterday, I'm hoping for a warm welcome
The first thing I did when I took it out of the box was fire it up, unlocked and rooted. When I rooted, I flashed SuperSU flashable. I also flashed CWM touch. After that I flashed SmoothROM 4.4, and I was solid. I installed all of my usual apps, then went to do what I call debloating, (Looking for apps I don't use such as voicedialer.apk, and deleting them) using root browser (/system/app). I noticed it wouldn't delete, then tried another app that requires root permissions. Nothing. I got suspicious, then re-downloaded root checker. "Sorry! You're device does not have proper root access!" What happened? Is this just me, or is this a widespread problem with this ROM? I'd like to keep this ROM if possible. Is there a way to re-root my device (more or less)? Thanks, a response or any help would be very much appreciated.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
I am having same issue
This issue has been addressed; do a Verizon Nexus Forum search.
Uninstall supersu, reboot, then install the market version, not the flash able zip
Sent from my Nexus 7 using xda premium
That fixed my issue
Sent from my HTC Raider X710e using xda app-developers app
So yesterday I decided to root my HTC one, after the 4.3 update.
After I unlocked the bootloader, I couldn't root using TWRP because the touchscreen wouldn't work when I booted to recovery. I figured out that I was using an old version TWRP, and once I updated TWRP it seemed like everything was going to work. Now I have SuperSU (updated to the newest version via app store) on my phone but when I try to open the app I get the following error
"There is no SU binary installed, and Super SU cannot install it. This is a problem!
If you just upgraded to Android 4.3, you need to manually re-root - consult the relevant forums for your device"
Uhhhh any ideas on how to fix this? This is the first time I have tried to root so I don't have alot of experience with this. I can't post in the Dev page because I previously had been a lurker and never really posted.
same problem
Same problem here.
I have T-Mobile HTC one that I convert to Google play edition.
After the update to 4.3 I lost the root.
Please help.
zcat84 said:
So yesterday I decided to root my HTC one, after the 4.3 update.
After I unlocked the bootloader, I couldn't root using TWRP because the touchscreen wouldn't work when I booted to recovery. I figured out that I was using an old version TWRP, and once I updated TWRP it seemed like everything was going to work. Now I have SuperSU (updated to the newest version via app store) on my phone but when I try to open the app I get the following error
"There is no SU binary installed, and Super SU cannot install it. This is a problem!
If you just upgraded to Android 4.3, you need to manually re-root - consult the relevant forums for your device"
Uhhhh any ideas on how to fix this? This is the first time I have tried to root so I don't have alot of experience with this. I can't post in the Dev page because I previously had been a lurker and never really posted.
Click to expand...
Click to collapse
Can you do it via recovery?
Sent from my HTC One using xda app-developers app
akuma24 said:
Can you do it via recovery?
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
I'm not sure what you mean. I can boot into recovery and get into twrp, and now that I have the new version of TWRP it the screen will work. I'm not sure if that answers your questions or not.
If one was to have SuperSu Pro with OTA survival mode, and update to KK would it work? Has anyone tried this?
Just a thought. :silly:
Don't quote me on this, but I'm pretty sure the update will still fail around 27%. There was something floating around here that said rooting the phone removes a file or something that the update looks for before allowing it to completely install. Obviously you have to be rooted to use SuperSU, so it most likely won't work.
We have people who managed to get it to update while rooted in survival mode it took root but left supersu in the system now unable to delete or use
Sent from my XT907 using xda app-developers app
yep, i did this and now have supersu in /system/app and su in /system/xbin, but root doesn't work and i can't get rid of them. the only real downside i've found so far is Isis Mobile wallet thinks the phone is rooted and doesn't work.. but i don't use Isis anyway.
Oh OK, I was just wondering. Thanks.
Sent from my SM-N900A using Tapatalk
Dankchild said:
Oh OK, I was just wondering. Thanks.
Sent from my SM-N900A using Tapatalk
Click to expand...
Click to collapse
yeah, it was worth a try for sure
So after getting my replacement N910T, I rooted it using the method here, and it seemed to go well, but during the process of reinstalling apps, I noticed some erratic behavior like the device not allowing root access when root checker says it is rooted. Or SuperSu not asking for SU access on apps that normally do, thereby denying root access, like Root Explorer. When I go back and check root checker again, sometimes it shows that it has access and other times it says that it doesn't. For a device with a supposedly unlocked bootloader, I've never encountered so many issues. My AT&T S4 which has a locked BL never gave me any issues once it was rooted. With all the devices I've rooted over the years, I've never had this much trouble. So I'm wondering if it's corrupted somehow? Or is there something about this systemless root that is the issue?
Here are the basics:
Android 5.1.1
Baseband OK2
Kernel Version 3.10.40-6209177
Build Number LMY47X.N910TUVU2DOK2
I've read threads until I'm crosseyed and googled but couldn't really come up with anything, so I could use some help here.
I had the same problem with a Note 4 Tmo I am working with. What SuperSU version are you using?
I had root issue problems (root chk says rooted, issues in ES File Expl, etc) when I used anything higher than 2.65.
Try flashing SuperSU 2.65 stable through recovery (I use TWRP 2.8.?.?) and when exiting out of recovery DO NOT allow SuperSU to be installed as SuperSU installation says...
Thanks much for the response. I'm using SuperSu 2.71; I didn't choose this version, it came with the root I got from here. So where do I find this version you're referring to?
Sent from my iPad using Tapatalk
Hi have you figured out your issue yet. If not, Try using supersu 2.52. It's the last full system root I believe. I have had much better luck with full system than systemless.
noob4598 said:
Hi have you figured out your issue yet. If not, Try using supersu 2.52. It's the last full system root I believe. I have had much better luck with full system than systemless.
Click to expand...
Click to collapse
I haven't tried anything else yet, I giving my head some time to clear. I've been at this for hours now, so I need a rest. Can I find that version of SuperSu as a flash able zip?
I used the links from Chainfire's thread on XDA
http://forum.xda-developers.com/showthread.php?t=1538053
Download to stable 2.65 is in that thread points to this link:
https://download.chainfire.eu/921/SuperSU/UPDATE-SuperSU-v2.65-20151226141550.zip
https://download.chainfire.eu/743/supersu this is link to 2.52 zip if u need it
Thanks for all the help, I'm glad this happened to someone other than me. One thing though: I'm on OK2, I thought you couldn't have system root with that.
Sent from my iPad using Tapatalk
Okay, the installation of supersu 2.52 via TWRP has definitely made a difference! The device is noticeably stabler now. One last thing, though: root checker shows it's rooted, but says that a superuser app isn't installed, which is what I thought supersu was. So now what?
Did you flash over 2.71. And do you have a su app icon on your scrren.
noob4598 said:
Did you flash over 2.71. And do you have a su app icon on your scrren.
Click to expand...
Click to collapse
Yes, I just flashed it from TWRP without doing anything else. And no, there isn't a Su app icon on the screen. I have a nandroid backup that'll put it back to the way it was before I did that, just in case it crashed and burned.
Download the app from playstore and then go to settings and do a full unroot. Then reboot to recovery and flash 2.52 then wipe cache and dalviche and reboot
MUCH BETTER!!! I'm in the process of reinstalling all of my apps; I don't want to take a chance of restoring my backup from Titanium, just in case there's something that won't play right.
I'll report back in a day or so.
Thanks to everyone who provided answers, it is most appreciated!
Welcome bud.
Thank you for the information guys. I was having the same issue as OP. Reverted SU as described and everything is much smoother
Yes, it's been a few days and my device is working the way it is supposed to. Interestingly enough, my SuperSU has automatically updated to version 2.65 but it's still working fine.
I've since turned off automatic updates in Google Play for fear of getting a version that begins the cycle all over again.
I still have the issue with the device telling me that the recovery is not seandroid enforcing even though I've updated to TWRP 3.0, and the set warranty bit: kernel issue. In spite of these, my device seems to work just fine with no issues.
Thanks again to everyone who offered help. It's nice when people offer help instead of posting just to tell you to find the answer yourself.
Sent from my SM-N910T using Tapatalk
Your welcome. And I get kernel is not seandroid enforcing on every reboot. Thought it was normal ha
My research on this has taken me all over the place, but none of the suggestions or explanations seem to apply. The device isn't ostensibly crippled, so I don't know.
Sent from my SM-N910T using Tapatalk
I think it's normal...maybe...ha Im pretty sure it's the warranty bit
are there root for N910A 5.1.1
I have an n910t running 5.1.1., dok2. I tried rooting several times with chainfire for 5.1.1. through Odin. It goes through the process okay (or at least it seems to), and appears to work at first, but then I lose it. Root Checker verifies root, as does SuperSU, but after a few minutes it's gone. Ive installed Titanium Backup, AdAway, and AdBlock. For the most part, they don't recognize root. If they do (it takes a long time to recognize) they lose it shortly thereafter. Rebooting doesn't help. I have no idea what I'm doing wrong. Anyone have any ideas??
Just looked now. For one example, SuperSU acknowledges AdAway, but when I try to fire up AdAway, it won't work, saying it doesn't have access.
Did you install twrp and did it ask after you booted to twrp if you wanted to root the device.. if so this was a no no.. your already rooted twrp just get a little confused with the new kernels... you must remove root and reinstall supersu and when it ask when you load twrp do not root but reboot do not swipe... unless there is an easier way this worked for me...
I had the same or a similar problem. I didn't lose root completely but at times various apps were unable to gain root (after previously getting it successfully). The phone would freeze while Titanium or Root Explorer for example were waiting fruitlessly for root to be granted. It was haphazard. One time the app would work and next time it wouldn't, or another wouldn't.
Finally it got so frustrating that I installed my favorite rom on it (Tekhd). Now all is stable. I was hoping to keep it stock rooted until mm came out but I couldn't figure out what was going on so I blew it away. I had twrp on it too and would always be prompted "root not detected" but if I allowed it to install SuperSu it would loop.
Sent from my SM-N910T3 using XDA-Developers mobile app
Thanks for the replies. I tried to install twrp once, but it kept freezing. Then I tried without it. Similar behavior outcomes either way.
I'm leaning toward just swapping out ROMS as this is very annoying. Isn't that a dangerous thing to attempt if root is so unstable though?
Eric618 said:
Thanks for the replies. I tried to install twrp once, but it kept freezing. Then I tried without it. Similar behavior outcomes either way.
I'm leaning toward just swapping out ROMS as this is very annoying. Isn't that a dangerous thing to attempt if root is so unstable though?
Click to expand...
Click to collapse
you need to odin the firmware for your phone and then restart fresh
without root twrp won't install rom you will get error..
Thanks. I did start fresh with stock firmware. Tried three times. Same result each time. I just reflashed to stock this morning. I'm actually using my old GS3 until I can figure this out. I'm on AT&T's network. I bought the T-Mobile variant just so I could root and possibly test drive a few custom ROMs. I'm ticked that even root has been elusive so far!
Any other suggestions?
Eric618 said:
Thanks. I did start fresh with stock firmware. Tried three times. Same result each time. I just reflashed to stock this morning. I'm actually using my old GS3 until I can figure this out. I'm on AT&T's network. I bought the T-Mobile variant just so I could root and possibly test drive a few custom ROMs. I'm ticked that even root has been elusive so far!
Any other suggestions?
Click to expand...
Click to collapse
Make sure your using a none corrupt download and when flashing root and twrp never let the phone restart to android screen... after you root and cf autoroot reboots hold down the buttons to boot into download mode and flash twrp.. make sure to get the .tar for 3.0 twrp.. if you need it i can post and once in DL mode flash twrp and then again do not boot the phone fully boot to twrp before and make backup if needed and when it ask after your done in twrp if you wanna root do not root in twrp... if this does not work i'm not sure what else it could be ... i have rooted my note 4 five times in the last month tring different things and it has happan one time to me and i had to odin firmware...
Thanks! I'll give that a try when I get home today.
S5Sickness said:
Make sure your using a none corrupt download and when flashing root and twrp never let the phone restart to android screen... after you root and cf autoroot reboots hold down the buttons to boot into download mode and flash twrp.. make sure to get the .tar for 3.0 twrp.. if you need it i can post and once in DL mode flash twrp and then again do not boot the phone fully boot to twrp before and make backup if needed and when it ask after your done in twrp if you wanna root do not root in twrp... if this does not work i'm not sure what else it could be ... i have rooted my note 4 five times in the last month tring different things and it has happan one time to me and i had to odin firmware...
Click to expand...
Click to collapse
You rock!! It seems that took care of it. I went through the process last night, but wanted to wait a bit to see if any issues surfaced. So far, it's been perfect. Thank you!!
Eric618 said:
You rock!! It seems that took care of it. I went through the process last night, but wanted to wait a bit to see if any issues surfaced. So far, it's been perfect. Thank you!!
Click to expand...
Click to collapse
Your Welcome...
Eric618 said:
I have an n910t running 5.1.1., dok2. I tried rooting several times with chainfire for 5.1.1. through Odin. It goes through the process okay (or at least it seems to), and appears to work at first, but then I lose it. Root Checker verifies root, as does SuperSU, but after a few minutes it's gone. Ive installed Titanium Backup, AdAway, and AdBlock. For the most part, they don't recognize root. If they do (it takes a long time to recognize) they lose it shortly thereafter. Rebooting doesn't help. I have no idea what I'm doing wrong. Anyone have any ideas??
Click to expand...
Click to collapse
Or as is the case with some roms, if an app takes to long to get supersu permission, especially after a reboot, all u have to do is open the supersu app then open the app u want root for.
Sent from my SM-G935F using XDA-Developers mobile app
marseillesw said:
Or as is the case with some roms, if an app takes to long to get supersu permission, especially after a reboot, all u have to do is open the supersu app then open the app u want root for.
Sent from my SM-G935F using XDA-Developers mobile app
Click to expand...
Click to collapse
I had tried that. It was very sluggish, and would frequently drop root access altogether. Since following S5Sickness's advice it's been solid, however.
https://tapatalk.com/shareLink?url=...share_tid=2997946&share_fid=3793&share_type=t
[TOOLKIT] SKIPSOFT ANDROID TOOLKIT - GALAXY NOTE 4 - Drivers, Root, Recovery + MORE
Sent from my SM-N910T3 using XDA-Developers mobile app