No root on m9 Android m - One (M9) Q&A, Help & Troubleshooting

I've been getting S-Off, bootloader unlock, and root on the m9 for a while. I'd flash TWRP, and let it root for me.
However, after the Android m update rolled out my method is no longer working. Letting TWRP root soft bricks the device. I tried using it to flash the latest version of SuperSU too, but even after it shows as successful, there's no SuperSU app installed and installing it from the play store shows the device to be not rooted. TWRP does stop offering to root for me however. I even tried installing a custom ROM which should have root, but again it lacked SuperSU and installing it showed the phone to be not rooted. What gives? Fortunately the phones are family phones and not someone requesting an unlock.
Sent from my HTC6545LVW using XDA Free mobile app

Eragon615 said:
I've been getting S-Off, bootloader unlock, and root on the m9 for a while. I'd flash TWRP, and let it root for me.
However, after the Android m update rolled out my method is no longer working. Letting TWRP root soft bricks the device. I tried using it to flash the latest version of SuperSU too, but even after it shows as successful, there's no SuperSU app installed and installing it from the play store shows the device to be not rooted. TWRP does stop offering to root for me however. I even tried installing a custom ROM which should have root, but again it lacked SuperSU and installing it showed the phone to be not rooted. What gives? Fortunately the phones are family phones and not someone requesting an unlock.
Sent from my HTC6545LVW using XDA Free mobile app
Click to expand...
Click to collapse
thats wierd.. Is Twrp allowed to make modifications on the device?? this might be the issue

Yeah, I decided to double check just to be sure, but still no dice. This has happened on 2 phones, so surely someone else has encountered this problem?
Sent from my HTC6545LVW using XDA Free mobile app

Related

[Q] Broke my SuperSU app by installing busybox?

(My first post on the forums! You guys have helped me out so much in the past, and I'm excited to finally communicate with you. Wish me luck!)
I recently installed the 4.3 OTA update on my Samsung Galaxy S3, using the zips and instructions from these threads:
http://forum.xda-developers.com/showthread.php?t=2387423
http://forum.xda-developers.com/showthread.php?t=2538991
It went perfectly, without a hitch. Everything was running great, and I was loving everything about stock, de-samsungized 4.3, root and custom bootloader.
I was very interested in the dSploit app, and installed it, found out I needed Busybox. I installed it using the busybox installer. This is where the trouble begins. SuperSU needed a binary update after I installed busybox for some reason, even though I was fairly certain I already had the latest binaries. I tried running it through the automatic update with my teamwin bootloader, but it only booted into recovery and nothing installed. After googling it for a bit, decided to re-flash SuperSU. Suddenly, I began recieving the message "Unfortunately, SuperSU has stopped working" every time I tried to access anything requiring root priviledges. Anything that had already been granted root access (including Titanium Backup, thank goodness) seemed to work fine as long as it didn't need to request additional privileges. Unfortunately, I'm now locked out of ES File Explorer and the xposed framework (all prior installed modules continue to function though)
My initial thought was to wipe and reload using the process I used to get here in the first place, but I'm running 4.3 now, and I understand that downgrading is impossible now, and no flashable 4.3 stock roms seem to exist.
So I'm lost, guys. I need my root back somehow... If I forgot any information you think would be relevant and/or helpful, let me know and I'll provide anything you need. I've been googling and searching the forums for days, but I haven't found anyone with this exact problem.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
RidleyofZebes said:
(My first post on the forums! You guys have helped me out so much in the past, and I'm excited to finally communicate with you. Wish me luck!)
I recently installed the 4.3 OTA update on my Samsung Galaxy S3, using the zips and instructions from these threads:
http://forum.xda-developers.com/showthread.php?t=2387423
http://forum.xda-developers.com/showthread.php?t=2538991
It went perfectly, without a hitch. Everything was running great, and I was loving everything about stock, de-samsungized 4.3, root and custom bootloader.
I was very interested in the dSploit app, and installed it, found out I needed Busybox. I installed it using the busybox installer. This is where the trouble begins. SuperSU needed a binary update after I installed busybox for some reason, even though I was fairly certain I already had the latest binaries. I tried running it through the automatic update with my teamwin bootloader, but it only booted into recovery and nothing installed. After googling it for a bit, decided to re-flash SuperSU. Suddenly, I began recieving the message "Unfortunately, SuperSU has stopped working" every time I tried to access anything requiring root priviledges. Anything that had already been granted root access (including Titanium Backup, thank goodness) seemed to work fine as long as it didn't need to request additional privileges. Unfortunately, I'm now locked out of ES File Explorer and the xposed framework (all prior installed modules continue to function though)
My initial thought was to wipe and reload using the process I used to get here in the first place, but I'm running 4.3 now, and I understand that downgrading is impossible now, and no flashable 4.3 stock roms seem to exist.
So I'm lost, guys. I need my root back somehow... If I forgot any information you think would be relevant and/or helpful, let me know and I'll provide anything you need. I've been googling and searching the forums for days, but I haven't found anyone with this exact problem.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Have you tried uninstalling and reinstalling SuperSu?
Since SuperSU was flashed to the device via Odin, it is registered as a system app. The app store only has the open option, and I can't access the app in the system folder without root privileges, which it won't give me, so...
Yeah. Unless there's a script I can run through recovery, that's a dead end.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
there is a zip of SuperSU you can flash from recovery
Sent from my SGH-I747M using Tapatalk
I've tried this. In fact, that was when SuperSU began force-closing. I just need to completely uninstall it and start fresh, I think.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Have you tried the cleanup/unroot options inside supersu settings? Then starting over?
I might not have stated this directly before, but the SuperSU app won't launch. I tap on it and immediately get the "Unfortunately" error. I have no way of accessing anything within the app.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
RidleyofZebes said:
I might not have stated this directly before, but the SuperSU app won't launch. I tap on it and immediately get the "Unfortunately" error. I have no way of accessing anything within the app.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Ok well then find one of the 4.3 roms in development that you can use. I'm on s3rx 3.0 and other than some hiccups (still a wip atm) that are liveable, its pretty stable. You can flash this safely in recovery without the bootloader/modem package since you already took the OTA without risk of bricking. Its prerooted so no worries there. Good luck
pre4speed said:
Ok well then find one of the 4.3 roms in development that you can use. I'm on s3rx 3.0 and other than some hiccups (still a wip atm) that are liveable, its pretty stable. You can flash this safely in recovery without the bootloader/modem package since you already took the OTA without risk of bricking. Its prerooted so no worries there. Good luck
Click to expand...
Click to collapse
Thank you for that. It's always good to have a fallback option.
I'm still wondering though, is there a script I could flash that would completely remove SuperSU / BusyBox / superUSER (CWM) to scratch and allow me to re-flash CF-Autoroot? Barring that, how difficult would it be to code one myself?
FIXED IT.
Apparently, flashing the latest version of SuperSU from the developer's website (1.86) will not work on Android 4.3. I flashed version 1.65 as provided in the original 4.3 Rooting Guide, then updated it in the Play Store followed by a binary update and re-installed BusyBox, and everything is back to running order. Thank you all for your help and advice!

(FIXED) Just took 10p update and now I can't root...

Anybody taken the same update? Universal root isn't working for me, it's saying it's a read only system. Any help??
((PROBLEM FIXED!!!)) HAVE PHONE ROOTED BEFORE, THEN USE TITANIUM BACKUP TO FREEZE AT&T APPS. Then update...enjoy still having root!
Try to flash again the older version with lg flash tool and root then.
Sent from my LG-E986 using xda app-developers app
rooting technique doesn't work
Won't take the update if you are rooted. Already tried.
Waiting for root safe confirmation before accepting an update that includes nothing more than Roms here have had for a while?
Sent from my LG-E980 using XDA Premium 4 mobile app
you should never take an update unless you're SURE it can be rooted. I bought an s4 in the store and before I left the worker updated my phone for me to, and it turns out that update is what locked down the bootloader and to this day if you have that firmware you still can't unlock the bootloader.. so before anyone accepts updates research first or you might end up with a stock phone, forever.
You can root S4 though. Big difference between unlocking boot loader and rooting lol
Sent from my LG-E980 using XDA Premium 4 mobile app
I wasn't talking about root. I was talking about the boot loader
sent from my lg g pro via tapatalk
deadenz said:
I wasn't talking about root. I was talking about the boot loader
sent from my lg g pro via tapatalk
Click to expand...
Click to collapse
That's what he's saying, basically the OP's problem differs slightly from yours in that although your phone was updated there was was still a means to root your phone even after losing the ability to unlock you boot loader. Meanwhile after updating the OP can't even get root. Someone correct me if I'm wrong though...
likemiketoo said:
That's what he's saying, basically the OP's problem differs slightly from yours in that although your phone was updated there was was still a means to root your phone even after losing the ability to unlock you boot loader. Meanwhile after updating the OP can't even get root. Someone correct me if I'm wrong though...
Click to expand...
Click to collapse
that was my whole point. don't take updates unless you research first and make sure there is a root method.
deadenz said:
that was my whole point. don't take updates unless you research first and make sure there is a root method.
Click to expand...
Click to collapse
I can CONFIRM 100% that you CAN UPDATE to 10p once you are rooted and use TITANIUM BACKUP to FREEZE the AT&T APPS. Tried twice...worked flawlessly both times. Hope I helped someone.:good:
I just rooted and updated to the P version. Kept root. I don't even have TBU installed, either, so freezing ATT apps is not a variable necessarily.
Sent from my LG-E980 using xda app-developers app
How can I force my phone to download this update if I'm rooted and on T-Mobile?
It doesn't matter if you freeze the apps. It matters if the apps are uninstalled.
Sent from my Optimus G Pro using XDA Premium 4 mobile app
Neroga said:
It doesn't matter if you freeze the apps. It matters if the apps are uninstalled.
Sent from my Optimus G Pro using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I never uninstalled them, only tried without being frozen, then with. Only updated with freezing. Not sure about uninstalling them.
Root sticks after the update. Your recovery must be stock, not CWM or TWRP. I didn't need to freeze anything, though I never deleted/disabled anything prior to the update.
What about the OP's question: Can anyone root AFTER taking the update? I assume his phone was not rooted prior to the update.
I just tried this myself on my "clean" phone and can confirm the univ root method does not work any more after the 10p update.
.
I'm having the same problem, hopefully somebody figures out a way way around this, I hate not being rooted.
Sent from my LG-E980 using XDA Premium 4 mobile app
jreed3786 said:
Won't take the update if you are rooted. Already tried.
Click to expand...
Click to collapse
looks like if your rooted but do not freeze, uninstall, or modify apps in any way that it will in fact update. Then after update go in and freeze the apps.
bailey37821 said:
looks like if your rooted but do not freeze, uninstall, or modify apps in any way that it will in fact update. Then after update go in and freeze the apps.
Click to expand...
Click to collapse
You might be on to something here! Definitely going to try tomorrow...even though I'm updated at the moment, and rooted!
well I had the similar issue as the OP. I was rooted, running CWM recovery and had removed most of the AT&T stock apps. I saw the update available and like a fool I accepted the update and then was stuck in CWM recovery boot loop. Nothing worked to get out of the loop so I decided to reflash with stock TOT file. Then I took the 10p update and found the Universal Root file not working (I updated before rooting).
I need to have root... so next try I reflash stock TOT file, root with Universal Root, accept update to 10p and all is good. I can once again remove AT&T stock apps, disable carrier-iq, use Freegees to go back to custom recovery, etc, etc, etc... all good now! :good:

4.3 Custom ROMs Keep Losing Root

I am having a strange issue on my T-Mobile Note 2... I keep losing my root access, even on different custom ROMs.
I don't post often because I can generally find what I need with a search but this one has me stumped. Could this be due to the 4.3/knox bootloader? Hopefully someone here can help. Here are all the details I can think of:
I have TWRP and generally flash my ROMs in recovery instead of Odin. The ROMs flash successfully and all other components work when I flash a ROM. Also, this has happened across at least 2 different custom rooted ROMs (Jedi x20 & Jedi Master x2).
I started out with the official 4.3 from T-Mobile before rooting and applying a custom ROM, so I have the 4.3 bootloader and can't get rid of it. I see Dr Ketan has come up with a way to remove the 4.3 bootloader on one of the other Note 2 variants (GT-N7100 & N7105)... but I don't see any way to do this on the T-Mobile version, please correct me if I am wrong.
When I lose root, I first notice with messages from my root apps saying that they can't get root access. I then check super su and it notifies me the su binary is missing and needs to be installed but it can't do it. Sometimes root comes back on its own after a while and other times I have to reflash my ROM once or a several times. I have also noticed the super su app is sometimes completely missing when this happens. I have also tried to reflash just SU through recovery but it doesn't always fix it; and if it does, it sometimes reverts to no root shortly after.
The most recent time this happened was this week... The phone lost root for a few days and stayed that way even after a few reboots. Then I woke up in this morning and saw that a scheduled titanium backup had completed. I tested my root apps and found my root access had been restored over night without any changes made by myself. The last time it happened before that, I lost root and it came back after a single reboot... but the reboot solution is inconsistent and only works every once in a while to restore root. Sometimes, multiple reboots do nothing to change the root status.
I have installed several anti virus apps and ran scans with each but the phone appears to be clean. I searched & read the threads for my ROM & searched the help forum too but haven't seen this same issue. I am open to suggestion on what could be causing this issue. If there is an existing thread, please politely point me in the correct direction & close this one.
Thanks!
EDIT 7/23/2014: Solution/Workaround found. See post 22: http://forum.xda-developers.com/showpost.php?p=54338165&postcount=22
Ok, it just happened again. This time, my battery was almost dead, so I powered the phone off and waited for it to finish shutting down. Then I pulled the dead battery and replaced it with a charged one. When it powered back on, I no longer had root. I took a screenshot of the su app error.
A couple reboots later and I have root again.
Sent from my SGH-T889 using XDA Free mobile app
Have you tried a new SuperSU
Here's Chainfire's 1.99
https://mega.co.nz/#!xt1lRJbI!CyaqzlWsZWd19gpedSD10K037k17_G0zThUe2QKD5ec
I'm also having the same problem. Can't access my recovery either. Can't update SU, says I have no root access. Am on SlimKat rom
Sent from my SGH-T889 using XDA Free mobile app
Double0EK said:
Have you tried a new SuperSU
Here's Chainfire's 1.99
https://mega.co.nz/#!xt1lRJbI!CyaqzlWsZWd19gpedSD10K037k17_G0zThUe2QKD5ec
Click to expand...
Click to collapse
I have tried a few different versions of Chainfire's Root including 1.80 & 1.93.
I haven't tried 1.99 yet but I will give it a shot next time I lose root.
Thanks for the suggestion! I'll let you know how it goes...
Need some help. Last time I flashed a new rom was a year ago. Been that long since I tinkered with my phone.. Now trying to upgrade but it's not working. Can't access my recovery because apparently I am not rooted. Can't update my SU because I can't access recovery. Downloaded teamwin app but that needs root to run..
Sent from my SGH-T889 using XDA Free mobile app
You_got_owned123 said:
Need some help. Last time I flashed a new rom was a year ago. Been that long since I tinkered with my phone.. Now trying to upgrade but it's not working. Can't access my recovery because apparently I am not rooted. Can't update my SU because I can't access recovery. Downloaded teamwin app but that needs root to run..
Sent from my SGH-T889 using XDA Free mobile app
Click to expand...
Click to collapse
Pretty sure powering off (be sure its unplugged from the charger)
And manually booting into recovery will still work. (Hold Menu + Vol up + Power)
You_got_owned123 said:
Need some help. Last time I flashed a new rom was a year ago. Been that long since I tinkered with my phone.. Now trying to upgrade but it's not working. Can't access my recovery because apparently I am not rooted. Can't update my SU because I can't access recovery. Downloaded teamwin app but that needs root to run..
Sent from my SGH-T889 using XDA Free mobile app
Click to expand...
Click to collapse
Here is the TWRP thread:
http://forum.xda-developers.com/showthread.php?t=1966105
In the thread, there is a download link that points to the Team Win site. You can find the recovery for the T-Mobile Note 2 here:
http://teamw.in/project/twrp2/123
There are several different methods of flashing recovery, you could try the Odin method, I don't think that requires root or an existing recovery.
Double0EK said:
Pretty sure powering off (be sure its unplugged from the charger)
And manually booting into recovery will still work. (Hold Menu + Vol up + Power)
Click to expand...
Click to collapse
Yes, Double0EK is right. This method will load whatever recovery is installed.
When this happened to me, the custom recovery kept getting overwritten with stock recovery.
Double0EK said:
Pretty sure powering off (be sure its unplugged from the charger)
And manually booting into recovery will still work. (Hold Menu + Vol up + Power)
Click to expand...
Click to collapse
I'm such an idiot! I forgot to hold the menu button! Was able to get into recovery and flash the new SU. Works perfectly now. Thanks all of you!
Ok, I lost root again... this time, I powered off, booted to recovery and flashed chainfire 1.99. When I booted back up, I still didnt have root. Also noticed su app is missing. Powered off & booted back into recovery... flashed root a few more times but still no root when I boot into my ROM.
Any other ideas?
Sent from my SGH-T889 using XDA Free mobile app
nickf123654 said:
Ok, I lost root again... this time, I powered off, booted to recovery and flashed chainfire 1.99. When I booted back up, I still didnt have root. Also noticed su app is missing. Powered off & booted back into recovery... flashed root a few more times but still no root when I boot into my ROM.
Any other ideas?
Sent from my SGH-T889 using XDA Free mobile app
Click to expand...
Click to collapse
Flash it 3 times then reboot.
I flashed it twice & rebooted... I'll try again and see if the 3rd time helps
Thanks!
Sent from my SGH-T889 using XDA Free mobile app
Flashed root 3x and rebooted... still no root :banghead:
Sent from my SGH-T889 using XDA Free mobile app
I may have missed this but did you try root66 v2 for 4.3 ?
Sent from my SGH-T889 using XDA Free mobile app
If you are referring to the root injected stock ROMs by mrRobinson, no I have not. I started out with official T-Mobile 4.3, rooted, installed recovery & flashed a custom ROM.
Root sticks for a while and then just disappears like it did yesterday. Then, a little while later I had root again. Really stange issue.
I was thinking of just backing up everything, then wiping everything and starting over from scratch.
After I wipe, I think I will try mrRobinson's 4.3 from Dec, that's the v2 you were referring to, right? I'll flash in Odin and then try to reinstall my current ROM and see what happens. Hopefully it will be more stable.
Sent from my SGH-T889 using XDA Free mobile app
nickf123654 said:
If you are referring to the root injected stock ROMs by mrRobinson, no I have not. I started out with official T-Mobile 4.3, rooted, installed recovery & flashed a custom ROM.
Root sticks for a while and then just disappears like it did yesterday. Then, a little while later I had root again. Really stange issue.
I was thinking of just backing up everything, then wiping everything and starting over from scratch.
After I wipe, I think I will try mrRobinson's 4.3 from Dec, that's the v2 you were referring to, right? I'll flash in Odin and then try to reinstall my current ROM and see what happens. Hopefully it will be more stable.
Sent from my SGH-T889 using XDA Free mobile app
Click to expand...
Click to collapse
Yes, I was referring to MrRobinsons 4.3 v2 ROM. What custom ROM do you plan to flash ?
I am currently using Jedi Master X2 and it has been stable, so I'll probably stick with that unless there is something new that looks interesting. I don't mind trying out some other ROMs if you have any suggestions.
Sent from my SGH-T889 using XDA Free mobile app
nickf123654 said:
Ok, I lost root again... this time, I powered off, booted to recovery and flashed chainfire 1.99. When I booted back up, I still didnt have root. Also noticed su app is missing. Powered off & booted back into recovery... flashed root a few more times but still no root when I boot into my ROM.
Any other ideas?
Sent from my SGH-T889 using XDA Free mobile app
Click to expand...
Click to collapse
You have to flash the supersu apk then install it when the phone boots then open the app and it may ask to update the binary
Sent from my GT-N7105 using XDA Premium 4 mobile app
I have tried flashing root in recovery and then installing super su after the phone boots but it is unable to install the su binary and I get the error from the screenshot in the 2nd post of this thread

How to root Note running 4.4.2

So I haven't been on xda for a while. I've rooted my note a good 12x. I got a replacement and decided to keep it stock as long as possible. Now my phone just pisses me off with touchwiz. I wanna flash a twrp or cwm so i can flash cm11 and so on. I know Samsung just puahed this new update out so idk if anyone has rooted it yet. Does any one know how to root and instal cwm on 4.4.2? Really want to flash a rom. Thank you very much for time and feedback
Sent from my SAMSUNG-SGH-I317 using XDA Free mobile app
Jonahng1994 said:
So I haven't been on xda for a while. I've rooted my note a good 12x. I got a replacement and decided to keep it stock as long as possible. Now my phone just pisses me off with touchwiz. I wanna flash a twrp or cwm so i can flash cm11 and so on. I know Samsung just puahed this new update out so idk if anyone has rooted it yet. Does any one know how to root and instal cwm on 4.4.2? Really want to flash a rom. Thank you very much for time and feedback
Sent from my SAMSUNG-SGH-I317 using XDA Free mobile app
Click to expand...
Click to collapse
I used cf auto root heres the link
http://forum.xda-developers.com/showthread.php?t=1980644
Can you please confirm that cf worked on 4.4.2? Their site only shows compatibility up to 4.3. I've been searching everywhere, but found no confirmed reports of cf or anything else working on 4.4.2. I want to root my i317 while retaining the stock rom so that I can enable tethering.
Sent from my SAMSUNG-SGH-I317 using XDA Free mobile app
MikeKidder said:
Can you please confirm that cf worked on 4.4.2? Their site only shows compatibility up to 4.3. I've been searching everywhere, but found no confirmed reports of cf or anything else working on 4.4.2. I want to root my i317 while retaining the stock rom so that I can enable tethering.
Sent from my SAMSUNG-SGH-I317 using XDA Free mobile app
Click to expand...
Click to collapse
Ive used it myself it works just fine
CF method worked on my i317 with Stock 4.4.2. I seen that the compatibility was up to 4.3 but I tried it anyways.
Sent from my SAMSUNG-SGH-I317 using Tapatalk
What recovery are you using, and how did you install it, TWRP bricked mine.
C auto root is flashed with odin in download mode. While rooting, it installs a custom recovery.
maybe it's kitkat, but it didn't install one for me. When I went into recovery, it was the normal factory recovery, which allowed nothing. I tried with Rom Manager, but nothing.
CF worked
I had to manually install the latest Supersu apk then update the binaries to get it working afterword, but I'm finally rooted
Now to get tether working
Sent from my SAMSUNG-SGH-I317 using XDA Free mobile app
did you get a recovery to work, and if you did, how!
jappel2 said:
did you get a recovery to work, and if you did, how!
Click to expand...
Click to collapse
Download a recovery like philz and flash it in odin while the phone is in download mode
Let me ask you this:
1. root with odin.
2. install CWM with odin?
3. Not I have 4.4.2 stock rom with root.
4. Can I install a custom rom with 4.4.2. stock rom still on the phone?
jappel2 said:
Let me ask you this:
4. Can I install a custom rom with 4.4.2. stock rom still on the phone?
Click to expand...
Click to collapse
Yes, if 1 - 3 is accomplished, you are ready for experiments in custom roms. You use the recovery to flash.
But make sure you have the latest recovery, and that you check the rom instructions a few times before you do anything.
Ok....cwm from Rom manager, or twrp through odin? I don't mean to break chops, I've rooted a captivate and played with it for a year, when my wtty was over with this phone, I rooted it, and had JediX 19 on it. I went back to stock, and then 4.4.2 When samsung stock 4.4.2 was installed, for some reason, it keeps bricking on me.
Ok, I rooted, and installed twrp from odin,.... passed. When I go into recovery, it's not there.
Ok. Hopefully someone has an answer. I rooted with CF auto root, Odin....fine. Installed CWM, fine. Downloaded SuperSU.....unfortunately superuser stopped working everytime I press on it. I cannot uninstall it, because it DOES NOT show up in application manager. I installed root checker, and says phone is not rooted. I can get into clockwork MOD, but no zip files show up. Can I use Odin to re flash CF auto root?, or just quit, I would hate to brick this again.
Sounds like Knox is blocking you. After rooting, install the latest Supersu apk (2.02) and install manually. Then when you open it, it should ask to update binaries. Let it, then it should ask about dialing Knox. Click yes. Viola, you're fully rooted. After the above is done, you can play with ROMs n such.
Up till that point, there is no need to flash anything, as auto root is designed to do the work for you from a pure stock rom.
Sent from my SAMSUNG-SGH-I317 using XDA Free mobile app
MikeKidder said:
Sounds like Knox is blocking you. After rooting, install the latest Supersu apk (2.02) and install manually. Then when you open it, it should ask to update binaries. Let it, then it should ask about dialing Knox. Click yes. Viola, you're fully rooted. After the above is done, you can play with ROMs n such.
Up till that point, there is no need to flash anything, as auto root is designed to do the work for you from a pure stock rom.
Sent from my SAMSUNG-SGH-I317 using XDA Free mobile app
Click to expand...
Click to collapse
Thank you sir! I went into ES file explorer, and manually installed SuperSU. Although it never asked about dialing KNOX. I installed Root Checker, and it says I'm rooted. Appreciate yours and everyone else's help. Have a great day.

[Q] Lost root after upgrade to 5.1.1 - how do I re-root?

Hi all,
I'm running a Sprint Note 2 (SPH-L900). I finally bit the bullet this week and upgraded from CM 11 to CM 12.1. However in the upgrade from KitKat to Lollipop, I seem to have lost root. I tried reinstalling SuperSU via both apk and by flashing in Philz recovery, but whenever I reopen SuperSU, I get a message that says "The SU binary is missing and SuperSU cannot install it. If you recently upgraded to Android 5.0, you need to manually re-root. Please consult the forums."
I've looked in the forums, but it seems like the answer that worked for most people is to flash SuperSU from recovery, which I have already done. Do I have to flash a file again through ODIN download mode like I did when I first rooted? If that's the case, can I flash a file which includes CWM on top of Philz that I already have, and will that be compatible with Lollipop?
I'd like some guidance so I don't accidentally brick my phone. Thanks for any guidance in advance!
Well all 5.1.1 roms come rooted. You just have to enable developer options (google it) and allow root for apps. If you want supersu then you need the newest version which only the new twrp has (although I think there is still issues with twrp for our device). I suggest using CyanideL if you like cm. CyanideL can be found under the development section.
FYI there is almost no brick on this device that cannot be recovered from. Flashing roms/recoveries/kernels are no real worries.
Sent from my GT-N7105 using XDA Premium 4 mobile app
jlmancuso said:
Well all 5.1.1 roms come rooted. You just have to enable developer options (google it) and allow root for apps. If you want supersu then you need the newest version which only the new twrp has (although I think there is still issues with twrp for our device). I suggest using CyanideL if you like cm. CyanideL can be found under the development section.
FYI there is almost no brick on this device that cannot be recovered from. Flashing roms/recoveries/kernels are no real worries.
Sent from my GT-N7105 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks. I forgot about developer options; did that and set option to all Root Access for Apps only, but my apps still don't have root. Any other ideas?
pillzbury said:
Thanks. I forgot about developer options; did that and set option to all Root Access for Apps only, but my apps still don't have root. Any other ideas?
Click to expand...
Click to collapse
My other suggestion is not to use stock cm.
Sent from my SPH-L900 using XDA Premium 4 mobile app

Categories

Resources