Develop Bugs

[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!

Help with twrp for sprint g2?

Ok, so here is my issue. For the sake of time, i want to make this question as simple as possible.
I've been putting it off, but now that kit kat is here, i need to get the ball rolling with twrp and my phone. Basically, i am on zv7, rooted stock. I have not been able to install twrp on my phone, and I need someone who would be merciful enough to help me out, to explain to me how to install it on stock zv7, and get kit kat, as i dont want to unroot. I have yet to find instructions online that would be able to help me with my particular situation... Any help would be appreciated.... Thank you for your time guys.

mcluvin1065 said:
Ok, so here is my issue. For the sake of time, i want to make this question as simple as possible.
I've been putting it off, but now that kit kat is here, i need to get the ball rolling with twrp and my phone. Basically, i am on zv7, rooted stock. I have not been able to install twrp on my phone, and I need someone who would be merciful enough to help me out, to explain to me how to install it on stock zv7, and get kit kat, as i dont want to unroot. I have yet to find instructions online that would be able to help me with my particular situation... Any help would be appreciated.... Thank you for your time guys.
Click to expand...
Click to collapse
You can update with stock rooted. Why are you not on at least ZVA? You don't need a custom recovery to be rooted. You can be rooted and have stock recovery, but any time you take an OTA update you lose the root and have to rerun ioroot.
Sent from my LG-LS980 using Tapatalk

Stl Dark Knight said:
You can update with stock rooted. Why are you not on at least ZVA? You don't need a custom recovery to be rooted. You can be rooted and have stock recovery, but any time you take an OTA update you lose the root and have to rerun ioroot.
Sent from my LG-LS980 using Tapatalk
Click to expand...
Click to collapse
Thanks for your response!
My point exactly. I don't want to lose root, and i don't want to reroot. Even if i took the OTA on stock rooted, i'm pretty sure it would break several things I have now as i use alot of apps that require root privilegedes, e.g titanium backup. I realize you don't need to have twrp to be rooted (as i am rooted), but i do need it to safely flash an updated 4.4 zip that would preserve my root privileges, and upgrade me to kitkat...
P. S, i am not on ZVA because when i soft bricked earlier this year, i had to go back to full unrooted stock, and in my rush to reroot, forgot to upgrade to zva before rooting, which is why im on zv7...
Sent from my LG-LS980 using XDA Premium 4 mobile app

mcluvin1065 said:
Thanks for your response!
My point exactly. I don't want to lose root, and i don't want to reroot. Even if i took the OTA on stock rooted, i'm pretty sure it would break several things I have now as i use alot of apps that require root privilegedes, e.g titanium backup. I realize you don't need to have twrp to be rooted (as i am rooted), but i do need it to safely flash an updated 4.4 zip that would preserve my root privileges, and upgrade me to kitkat...
P. S, i am not on ZVA because when i soft bricked earlier this year, i had to go back to full unrooted stock, and in my rush to reroot, forgot to upgrade to zva before rooting, which is why im on zv7...
Sent from my LG-LS980 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2702007
If you follow this method you will not lose root. But, 4.4.2 can be rooted with ioroot25 anyway, and it's easy.
The only way to enter custom recovery will be through a terminal emulator command (see post #2). If you take the OTA, you will lose custom recovery altogether.

scottdanpor said:
http://forum.xda-developers.com/showthread.php?t=2702007
If you follow this method you will not lose root. But, 4.4.2 can be rooted with ioroot25 anyway, and it's easy.
The only way to enter custom recovery will be through a terminal emulator command (see post #2). If you take the OTA, you will lose custom recovery altogether.
Click to expand...
Click to collapse
It sounds like it would be easier for me to just take the OTA and reroot then go through this process of getting a custom recovery... Can i take the OTA on stock rooted zv7 without any serious reprocussions?
Sent from my LG-LS980 using XDA Premium 4 mobile app

mcluvin1065 said:
It sounds like it would be easier for me to just take the OTA and reroot then go through this process of getting a custom recovery... Can i take the OTA on stock rooted zv7 without any serious reprocussions?
Sent from my LG-LS980 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
If I'm not mistaken when you check for updates, you will have to update to zv8, then zva, then it will offer zvc. Check in your updater what it says is available. I don't expect you'll have any issues as long as you haven't modified files/removed system files.

scottdanpor said:
If I'm not mistaken when you check for updates, you will have to update to zv8, then zva, then it will offer zvc. Check in your updater what it says is available. I don't expect you'll have any issues as long as you haven't modified files/removed system files.
Click to expand...
Click to collapse
The only thing i have done is frozen some system apps, and i have X posed installed, as well as g2 xposed....i use root apps, but i dont think ive done anything besides that.... Should i continue?
Sent from my LG-LS980 using XDA Premium 4 mobile app

mcluvin1065 said:
The only thing i have done is frozen some system apps, and i have X posed installed, as well as g2 xposed....i use root apps, but i dont think ive done anything besides that.... Should i continue?
Sent from my LG-LS980 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
No. You will have to unfreeze those apps and completely remove xposed. You might want to flash Youdug's odexed stock rom if you continue to run into snags.
Also: If you are taking the OTA on your phone, you should probably unroot.

Ok, so here is what i did. I updated all the way to zva, but now im not seeing the kitkat update. How do i go about getting kitkat since the update broke root completely?
Just a note for those who want to preserve root while doing an OTA, supersu and superuser have a "survival mode" for people who want to preserve root. I had to factory reset so i couldn't do it, but just something to keep in mind.
Sent from my LG-LS980 using XDA Premium 4 mobile app

mcluvin1065 said:
Ok, so here is what i did. I updated all the way to zva, but now im not seeing the kitkat update. How do i go about getting kitkat since the update broke root completely?
Just a note for those who want to preserve root while doing an OTA, supersu and superuser have a "survival mode" for people who want to preserve root. I had to factory reset so i couldn't do it, but just something to keep in mind.
Sent from my LG-LS980 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
If you're not seeing the update you have a few options. Some say clearing Google services framework data and hitting check for updates repeatedly works. You can install it using the method above, or you can flash autoprime's .tot file using LG flash tool.
You can always re-root with ioroot25 if you need to.

Just want to say thanks to everyone here who took the time to help me out. For those of you who want to know, i decided to root from zva. I used the freegee app to download and install recovery (super easy) and am about to flash cm11 for stock kitkat.

FreeGee

FreeGee updated recently and now gives me the option to install CWM-6.0.4.7 or TWRP-2.6.3.3. Has anyone tried this yet?

morganstein said:
FreeGee updated recently and now gives me the option to install CWM-6.0.4.7 or TWRP-2.6.3.3. Has anyone tried this yet?
Click to expand...
Click to collapse
I'll tell you right now, i'm not going to try. Without knowing for sure I can have download mode back. No way
Sent from my Nexus 7 using Tapatalk

secret.animal said:
I'll tell you right now, i'm not going to try. Without knowing for sure I can have download mode back. No way
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Ha. That's what I'm waiting for.

Why aren't you wanting to try auto-rec.
http://forum.xda-developers.com/showthread.php?t=2715496
One button operation
Sent from my Nexus 7 using Tapatalk

Already answered.
Deleted.
How rude stealing my post 3 minutes before me secret.animal. lol

I have used it quite a few times and it works fine. Only thing is for me it would hang on install. I would just close the app, clear all tasks by holding down home button, run it again and it would say completed. I know that sounds weird but that used to happen on my old optimus g.
Sent from my LG-LS980 using xda app-developers app

leroybrute said:
Already answered.
Deleted.
How rude stealing my post 3 minutes before me secret.animal. lol
Click to expand...
Click to collapse
Sorry cuz, I got lucky that time.
Sent from my LG-LS980 using Tapatalk

secret.animal said:
Why aren't you wanting to try auto-rec.
http://forum.xda-developers.com/showthread.php?t=2715496
One button operation
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
I've been following the AutoRec thread for a couple days and I'm a little concerned that there's no follow up yet on those white lines that some are getting. I did notice that FreeGee no longer gives me a warning about ZVC being incompatible. Any body know if this means FreeGee is now safe?

whouston.jr said:
I've been following the AutoRec thread for a couple days and I'm a little concerned that there's no follow up yet on those white lines that some are getting. I did notice that FreeGee no longer gives me a warning about ZVC being incompatible. Any body know if this means FreeGee is now safe?
Click to expand...
Click to collapse
I had no issues with autorec. But I tot, rooted then used autorec.
I'm only guessing but it could be because of that. Some that had the lines already had twrp but had broken download before they used autorec. Like I said though, it's a guess.

leroybrute said:
I had no issues with autorec. But I tot, rooted then used autorec.
I'm only guessing but it could be because of that. Some that had the lines already had twrp but had broken download before they used autorec. Like I said though, it's a guess.
Click to expand...
Click to collapse
i got white lines and I was stock rooted, ls980, 4.4.2. had to .tot back.

mtg981 said:
i got white lines and I was stock rooted, ls980, 4.4.2. had to .tot back.
Click to expand...
Click to collapse
Have you rooted again and tried autorec since?

leroybrute said:
Have you rooted again and tried autorec since?
Click to expand...
Click to collapse
I also was rooted on stock ZVC. I installed autorec and let it do its thing. First try, I could not do a backup in TWRP. It would fail everytime. Then I booted to system and thought everything was fine till the screen went off. White lines slowly appeared and stayed. Only fix was to reboot. That got boring so I tot back to ZVC and used ioroot25 to root and then installed autorec. White lines again when screen off then back on. I think waiting until the dev can figure out what is being altered on our ls980, we have to wait.

sclarktay4 said:
I also was rooted on stock ZVC. I installed autorec and let it do its thing. First try, I could not do a backup in TWRP. It would fail everytime. Then I booted to system and thought everything was fine till the screen went off. White lines slowly appeared and stayed. Only fix was to reboot. That got boring so I tot back to ZVC and used ioroot25 to root and then installed autorec. White lines again when screen off then back on. I think waiting until the dev can figure out what is being altered on our ls980, we have to wait.
Click to expand...
Click to collapse
Did you wipe cache and dalvik and try autorec again?
Seems strange that it's working fine for a lot of us and not for others.

leroybrute said:
Did you wipe cache and dalvik and try autorec again?
Seems strange that it's working fine for a lot of us and not for others.
Click to expand...
Click to collapse
I can only think there is some tweak in the modified kernel that breaks us. Ota, tot, no matter what. I can see no matter what in TWRP, but in system it fails. I gone every way.
Just have to wait a bit longer.
Sent from my Nexus 7 using Tapatalk

secret.animal said:
I can only think there is some tweak in the modified kernel that breaks us. Ota, tot, no matter what. I can see no matter what in TWRP, but in system it fails. I gone every way.
Just have to wait a bit longer.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Agreed on modified kernel.
I hope @Cloudyfa sticks around for us, to help the ones that need it. He has contributed so much to the G2 community.

My big concern is that freegee doesn't give any info as to what version of ZVC OTA it's compatible with, and neither does the autorec thread for that method. Like in the ZVA-> ZVC thread, there's a zip of the OTA... which is slightly different than getting the official OTA through system updates on the phone. So I'm afraid to try either method and end up with an unrecoverable brick because I'm on the official OTA.
Anyone on completely stock ZVC, rooted, that has successfully used either method?

agentfusion said:
My big concern is that freegee doesn't give any info as to what version of ZVC OTA it's compatible with, and neither does the autorec thread for that method. Like in the ZVA-> ZVC thread, there's a zip of the OTA... which is slightly different than getting the official OTA through system updates on the phone. So I'm afraid to try either method and end up with an unrecoverable brick because I'm on the official OTA.
Anyone on completely stock ZVC, rooted, that has successfully used either method?
Click to expand...
Click to collapse
Auto-rec works fine. The modified kernel that every app or by manual has used is the same at the time.
The worst it will do if it does not work is give you lines in your display after the screen shuts off. A reboot fixes that. But to fix completely, is to tot back to zvc and stay just rooted.
Sent from my Nexus 7 using Tapatalk

Stock rooted zvc. Auto-rec worked for me. No lines. Everything works.Just downloaded app. From download folder pressed on the app let the phone install it. Then ran it. I did not have download mode at first so reran the app and download mode worked.

secret.animal said:
Auto-rec works fine. The modified kernel that every app or by manual has used is the same at the time.
The worst it will do if it does not work is give you lines in your display after the screen shuts off. A reboot fixes that. But to fix completely, is to tot back to zvc and stay just rooted.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Yep. Worked perfectly. No lines at all. Haven't tested download mode yet but system and recovery both work. Wooohoooo.

Glad to hear it worked!

Guide to Update to KitKat on a Rooted Phone

Hi All,
With all the threads about bricked phones, I wanted to take the safer route and outright ask for the best method to upgrade to KitKat on a rooted phone running 4.2.2 stock? I've already 'bricked" my phone once last year doing an OTA update, so I'm trying to avoid doing that again. I know this is a noob question, but I haven't been able to locate a sprint specific guide consolidating all of the information out there. Any help is appreciated.
Sprint LS980ZV7
4.2.2 stock on a rooted phone
twrp installed
IOroot25
Kernel: 3.4.0

thadeus_d3 said:
Hi All,
With all the threads about bricked phones, I wanted to take the safer route and outright ask for the best method to upgrade to KitKat on a rooted phone running 4.2.2 stock? I've already 'bricked" my phone once last year doing an OTA update, so I'm trying to avoid doing that again. I know this is a noob question, but I haven't been able to locate a sprint specific guide consolidating all of the information out there. Any help is appreciated.
Sprint LS980ZV7
4.2.2 stock on a rooted phone
twrp installed
IOroot25
Kernel: 3.4.0
Click to expand...
Click to collapse
Use this thread for the files
http://forum.xda-developers.com/showthread.php?p=51557219
Or you can use this one to flash zvc tot file straight to phone.
http://forum.xda-developers.com/showthread.php?p=45293512
The second post as you read will give information I thought a bit more clear on Sprint.
@#***This will wipe your phone as in complete. Nothing will be left of yours. So copy anything off internal [email protected]#***
Follow the directions, use ioroot25. Root.
If you want custom recovery.
http://forum.xda-developers.com/showthread.php?p=51857807
Use auto-rec from above thread. Thank cloudyfa for putting that together.
If you reboot after and screen shuts off and you get white lines.
You might a well tot back to zvc and just root. @Cloudyfa on that same thread is working out the details to fix.
Sent from my Nexus 7 using Tapatalk

secret.animal said:
Use this thread for the files
http://forum.xda-developers.com/showthread.php?p=51557219
Or you can use this one to flash zvc tot file straight to phone.
http://forum.xda-developers.com/showthread.php?p=45293512
The second post as you read will give information I thought a bit more clear on Sprint.
@#***This will wipe your phone as in complete. Nothing will be left of yours. So copy anything off internal [email protected]#***
Follow the directions, use ioroot25. Root.
If you want custom recovery.
http://forum.xda-developers.com/showthread.php?p=51857807
Use auto-rec from above thread. Thank cloudyfa for putting that together.
If you reboot after and screen shuts off and you get white lines.
You might a well tot back to zvc and just root. @Cloudyfa on that same thread is working out the details to fix.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Thank you for the reply. I'll give this a shot tonight!

I have a question: I already screwed up and applied the KitKat update to my rooted G2 without thinking. It's now stuck booting to TWRP, where I was a moron and of course didn't create a backup at any point. Is there a way for me to sideload the ROM onto my phone at this point?
Any ideas?

Coop1979 said:
I have a question: I already screwed up and applied the KitKat update to my rooted G2 without thinking. It's now stuck booting to TWRP, where I was a moron and of course didn't create a backup at any point. Is there a way for me to sideload the ROM onto my phone at this point?
Any ideas?
Click to expand...
Click to collapse
Even sideload may not help you, if you can access down load mode. You might get to use tot, back to stock.
But there is no stock zvc yet for ls980.
Sent from my Nexus 7 using Tapatalk

secret.animal said:
Even sideload may not help you, if you can access down load mode. You might get to use tot, back to stock.
But there is no stock zvc yet for ls980.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Thank you for that suggestion. I was able to use Download Mode to fix my G2 and then OTA the KitKat update. Your post saved my phone.
Sent from my Nexus 7 using Tapatalk

I must have gotten lucky...wasn't thinking and took the OTA a while ago. Lost root but phone is fine.
Now...I'm off to find it again so I can get tether working

thadeus_d3 said:
Thank you for the reply. I'll give this a shot tonight!
Click to expand...
Click to collapse
To the OP, can I ask which method you chose and how it went? I need to do this as well and I'm in the same boat as you (rooted ZVA with custom recovery).
Thanks.
Ed

esoh said:
To the OP, can I ask which method you chose and how it went? I need to do this as well and I'm in the same boat as you (rooted ZVA with custom recovery).
Thanks.
Ed
Click to expand...
Click to collapse
I actually read a bit more and decided to hold off on the update. I'm happy with my phone's performance, so I really don't have the time to troubleshoot should the update go awry.

thadeus_d3 said:
I actually read a bit more and decided to hold off on the update. I'm happy with my phone's performance, so I really don't have the time to troubleshoot should the update go awry.
Click to expand...
Click to collapse
I'm the same way, but I figured that I should just go ahead.
So I'll throw that out, anyone pick one of these methods have a preference? I'm on TWRP, rooted, stock ZVA. Some mods including tether and camera. Thanks.

[Q] T-Mobile Note II is only partially rooted.

Hi All,
Recently I tried to root my T-Mobile Note II running stock 4.3 with a few of the one ctick root apps. I've tried framaroot (no go), towelroot (not supported) rootmaster (vRoot) I think that's where the partial root came into play. It installed an app called kinguser (that says I'm not rooted WTH!). It also installed it as a system app, so now I can't uninstall it. I installed supersu which has to update binaries, but it won't disable Knox. Rootchecker also says I'm rooted somewhat. The 1st paragraph under congratulations says I'm rooted. Everything else says no I'm not. User and group ID is not returning or something to that effect. When I learned about the one click apps I thought it was a Godsend because I don't have a computer. I've tried so many things to try to get around Knox, nothing is working. Installed it then deleted it like I read somewhere, tried the su pm com.sec.knox.seandroid on terminal emulator still no go. I even tried to play around with the commands for knox on terminal emulator atill no go. I don't know if its something security related with the phone or what. I used towelroot on my girlfriends Sgh t999L with stock 4.3 and it worked. So now I'm really pissed! I've searched the web for anything like this and couldn't find nothing. I know I'm not the only one this has happened to. I used some app cant remember the name, but it did ask me to use root access for something. But it wasn't through supersu. Plus it wasn't a root type of app so I refused access. I'm trying remember everything before I post this, dont wanna post it and remember something right after I do. I know its a lot of great minds on hear hopefully someone will be able to help me out with this situation. Thanks in advance XDA members..
PS. Does anyone know what modstring. I can use to maybe get towelroot to work? Or of any other terminal emulator commands for knox.

Just Odin flash the root66 tar from MrRobinson. You'll end up rooted and running fine...
Hastily spouted for your befuddlement

Coug76 said:
Just Odin flash the root66 tar from MrRobinson. You'll end up rooted and running fine...
Hastily spouted for your befuddlement
Click to expand...
Click to collapse
Thanks for the prompt response Coug76. I read several of the route66 posts. It appears that this method is for the sgh t999 variants. I was able to acquire root access with towelroot for this phone. I didn't find any mention of the note 2 sgh t889 in any of those posts. I know that you are supposed to use methods for the particular model. I don't know if this is a universal method or what. I ran a different rootchecker app and it says that I have root but not root access. I understand the gist of that, but it isn't helping my situation. Is it safe to use this method for my phone, or could you please recommend something else that I can use? It would be greatly appreciated. Thanks again for the quick response. Awaiting your reply. Thanks in advance.

J3D1mineTR1X said:
Thanks for the prompt response Coug76. I read several of the route66 posts. It appears that this method is for the sgh t999 variants. I was able to acquire root access with towelroot for this phone. I didn't find any mention of the note 2 sgh t889 in any of those posts. I know that you are supposed to use methods for the particular model. I don't know if this is a universal method or what. I ran a different rootchecker app and it says that I have root but not root access. I understand the gist of that, but it isn't helping my situation. Is it safe to use this method for my phone, or could you please recommend something else that I can use? It would be greatly appreciated. Thanks again for the quick response. Awaiting your reply. Thanks in advance.
Click to expand...
Click to collapse
There is a sticky in the Development Section.
http://forum.xda-developers.com/showthread.php?t=1975560
Hastily spouted for your befuddlement

Coug76 said:
There is a sticky in the Development Section.
http://forum.xda-developers.com/showthread.php?t=1975560
Hastily spouted for your befuddlement
Click to expand...
Click to collapse
:good: :good: Thanks for your assistance and pointing me in the right direction. Since I don't have a computer, I'll have to wait til Monday to try this at the library. Thanks again, very much appreciated...

J3D1mineTR1X said:
:good: :good: Thanks for your assistance and pointing me in the right direction. Since I don't have a computer, I'll have to wait til Monday to try this at the library. Thanks again, very much appreciated...
Click to expand...
Click to collapse
While I prefer pc Odin, mobile Odin from Chainfire should take care of you. The only thing it won't flash in a Samsung tar is the bootloader. You already have the mk7 bootloader so you should be fine.
Hastily spouted for your befuddlement

Thanks again Coug76, your help is both needed and appropriated. I just purchased and tried [Root] Mobile Odin Pro. First time it asked for superuser permission. The next few times it gave me an "couldn't detect phone model" error message. So, apparently I need superuser permission to run the app (I'm not sure) . I got a refund after a few tries..
Sent from my SGH-T889 using XDA Premium 4 mobile app

Appreciated (type-o), apologize for that.
Sent from my SGH-T889 using XDA Premium 4 mobile app

J3D1mineTR1X said:
Appreciated (type-o), apologize for that.
Sent from my SGH-T889 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
There is a free version if Mobile Odin available on XDA FWIW. You would need root to make it work though. Brainfart there from yours truly.
Hastily spouted for your befuddlement

LOL! Thanks again my friend. I see there's wisdom in your words. Quick question: If mobile Odin ever comes around again to its former glory. What would be the steps to take to install what's needed? Once again thanks. As you see I'm still not rooted but I still purchased the XDA Premium 4 app. Mainly because of my correspondence with you my friend. Thanks again, can't say that it enough. You've given me hope when I thought all hope was lost.
*What good is knowledge, if its not to be shared* Read that on the back of a cereal box, naw I didn't. LOL!
Sent from my SGH-T889 using XDA Premium 4 mobile app

Did you manage to get it rooted?
I can't get my Note 2 rooted either. I must have rooted over 50 devices over the last 5 years and never ran into so much difficultly. I have tried the root66 method, various other links around. None of them work. I was on stock 4.3 as well. And I think that's the problem. These are very old links from 2 years ago and I think since I already had 4.3, I can't just go straight to a rooted 4.3. For me, the root only works on the first boot. The next time I boot, root is gone. I have tried different versions of SuperUser - 1.91, 1.99r4, 2.01. Nothing's worked. Tried installing superuser zip from TWRP and CWM. Same problem.

os2baba said:
I can't get my Note 2 rooted either. I must have rooted over 50 devices over the last 5 years and never ran into so much difficultly. I have tried the root66 method, various other links around. None of them work. I was on stock 4.3 as well. And I think that's the problem. These are very old links from 2 years ago and I think since I already had 4.3, I can't just go straight to a rooted 4.3. For me, the root only works on the first boot. The next time I boot, root is gone. I have tried different versions of SuperUser - 1.91, 1.99r4, 2.01. Nothing's worked. Tried installing superuser zip from TWRP and CWM. Same problem.
Click to expand...
Click to collapse
did you remove knox? I have heard of it messing with root

mattlowry said:
did you remove knox? I have heard of it messing with root
Click to expand...
Click to collapse
No. But I had never enabled it. The icon was still on the phone. Plus the ROM I downloaded has Knox removed from it. So it should have worked. It does get root on the first boot. But it's lost after a reboot.

os2baba said:
No. But I had never enabled it. The icon was still on the phone. Plus the ROM I downloaded has Knox removed from it. So it should have worked. It does get root on the first boot. But it's lost after a reboot.
Click to expand...
Click to collapse
When you open supersu app does it give an error?

mattlowry said:
When you open supersu app does it give an error?
Click to expand...
Click to collapse
Yes. I get a message
There is no SU binary installed, and SuperSU 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!
This is after the next boot. The first boot works.
Edit: I tried a number of links to try rooting.
Starting with and repeatedly trying
http://forum.xda-developers.com/showthread.php?t=1975560
I just found this one you started.
http://forum.xda-developers.com/showthread.php?t=2564430
Should I try that one? I presume it's different from the one in the first link. I'll have to reset the phone and all my settings. But at this point, I'm ready to try anything. I don't want to mess with a different kernel from your link on my current installation. BTW, how would I know what the current bootloader on my phone is and whether it's the latest? I was on Stock unrooted 4.3 when I started. I'm now on 4.3 (supposedly) rooted stock ROM from the first link.

os2baba said:
Yes. I get a message
There is no SU binary installed, and SuperSU 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!
This is after the next boot. The first boot works.
Edit: I tried a number of links to try rooting.
Starting with and repeatedly trying
http://forum.xda-developers.com/showthread.php?t=1975560
I just found this one you started.
http://forum.xda-developers.com/showthread.php?t=2564430
Should I try that one? I presume it's different from the one in the first link. I'll have to reset the phone and all my settings. But at this point, I'm ready to try anything. I don't want to mess with a different kernel from your link on my current installation. BTW, how would I know what the current bootloader on my phone is and whether it's the latest? I was on Stock unrooted 4.3 when I started. I'm now on 4.3 (supposedly) rooted stock ROM from the first link.
Click to expand...
Click to collapse
I'm in the same boat. I'm partially rooted myself. Im the one posted the question. I tried to root my T-Mobile Note II running stock 4.3 today with heimdall (think that's spelled right) for mac. Files were uploaded phone rebooted, no root. I got my partial root from a one click apk called vRoot or rootmaster. I have root but not root access. I've never had the luxury of being rooted at all. I've tried different things to disable knox with no luck. I really think samsung and tmobile did something extra with that update. Don't understand how dam near every other phone with 4.3 can be rooted. But this one presents a slew of problems. My rootchecker pro reads exactly like yours. Except my group and user ID's don't return anything. Other than that it's word for word everywhere else. If you come up with a solution please let me know, or rather share. I don't have a computer so it's hard for me to try anything. Good luck and thanks in advance if you get it done. Thanks again.
Sent from my SGH-T889 using XDA Premium 4 mobile app

The bootloader info is located in the about device area. Mine is T889UVUCMK7. Yours should be the same. Only difference between my phone and yours is mine started out on 4.1.2. Another thing with my phone is: whenever I try to load something through recovery mode by way of upload by external sd card. I always get a red "E" signature error and it doesn't put it on my phone. Hopefully the bootloader info is right. Someone with a bit more understanding about this stuff passed it on to me. My next attempt was going to be with route66, guess I don't have to try it out now being as though our situations are so similar.
Sent from my SGH-T889 using XDA Premium 4 mobile app

os2baba said:
Yes. I get a message
There is no SU binary installed, and SuperSU 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!
This is after the next boot. The first boot works.
Edit: I tried a number of links to try rooting.
Starting with and repeatedly trying
http://forum.xda-developers.com/showthread.php?t=1975560
I just found this one you started.
http://forum.xda-developers.com/showthread.php?t=2564430
Should I try that one? I presume it's different from the one in the first link. I'll have to reset the phone and all my settings. But at this point, I'm ready to try anything. I don't want to mess with a different kernel from your link on my current installation. BTW, how would I know what the current bootloader on my phone is and whether it's the latest? I was on Stock unrooted 4.3 when I started. I'm now on 4.3 (supposedly) rooted stock ROM from the first link.
Click to expand...
Click to collapse
What version of TWRP are you using?

os2baba said:
Yes. I get a message
There is no SU binary installed, and SuperSU 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!
This is after the next boot. The first boot works.
Edit: I tried a number of links to try rooting.
Starting with and repeatedly trying
http://forum.xda-developers.com/showthread.php?t=1975560
I just found this one you started.
http://forum.xda-developers.com/showthread.php?t=2564430
Should I try that one? I presume it's different from the one in the first link. I'll have to reset the phone and all my settings. But at this point, I'm ready to try anything. I don't want to mess with a different kernel from your link on my current installation. BTW, how would I know what the current bootloader on my phone is and whether it's the latest? I was on Stock unrooted 4.3 when I started. I'm now on 4.3 (supposedly) rooted stock ROM from the first link.
Click to expand...
Click to collapse
Finally got it working. http://forum.xda-developers.com/showpost.php?p=54157011&postcount=663