Develop Bugs

[Q] Root counter stuck to 1 and update questions

Hi guys,
I know this may not be the best place to ask this, but I don't have an high enough postcount to reply on the developer section, so... here we go
I've rooted my Note 2 using the procedure 1 shown here : http://forum.xda-developers.com/showpost.php?p=31801060&postcount=2 . The problem is, even after I run Triangle away, my device si marked as "modified" ( aka, I guess the counter is not properly reset).
I've no idea why, and the thing doesn't really bother me that much, if it wasn't for the next question :
Can I update my firmware using keis with a rooted phone, or that means looking for trouble?I'l stuck with the LJ1 firmware and afaik a new version should be avaible ... and again, in case I have to somehow reset the phone to install the update, is it worth it?
Thanks

I guess the counter is not properly reset......
Click to expand...
Click to collapse
You should post in Q/A thread
Anyway
Not properly reset means?
counter is 'No' or non zero?
which method you have used? 1 or 2
if counter is zero, you have used method 1 then factory reset, status should turn to 'official'

dr.ketan said:
Not properly reset means?
counter is 'No' or non zero?
Click to expand...
Click to collapse
The counter is 1 even after Triangle Away
which method you have used? 1 or 2
Click to expand...
Click to collapse
I used method 1 ( I don't plan on using modded firmwares)
if counter is zero, you have used method 1 then factory reset, status should turn to 'official'
Click to expand...
Click to collapse
At the moment, the device status is "modified", and yet, as I said, I carefully followed method 1 and I've tried to reset the counter using Triangle Away ( without success)
PS : thanks for your fast reply

You should get your rom from samfirmware.com and flash it using odin. If you're gonna rely on OTA or Kies, then you'll be outdated all the time. Also, counter stuck at 1 usually means you have custom recovery or custom rom installed. Factory resetting will usually remove Modified status, although I don't see the point of it, since like I said you needn't rely on OTA or Kies when there is a much better alternative.

kaharas said:
The counter is 1 even after Triangle Away
I used method 1 ( I don't plan on using modded firmwares)
At the moment, the device status is "modified", and yet, as I said, I carefully followed method 1 and I've tried to reset the counter using Triangle Away ( without success)
PS : thanks for your fast reply
Click to expand...
Click to collapse
If you are on stock rom and just rooted with method 1, then just reset counter again. And let boot it normally once before checking counter.
Sent from my GT-N7100 using xda premium

dr.ketan said:
If you are on stock rom and just rooted with method 1, then just reset counter again. And let boot it normally once before checking counter.
Sent from my GT-N7100 using xda premium
Click to expand...
Click to collapse
Thanks again for your time I am on a stock pre-rooted rom, but I've rooted a month or so ago, and I've already tried to reset the counter multiple times ( and I've restarted a lot of times too). Still, no success in changing my phone status.
MohJee said:
cut
Click to expand...
Click to collapse
Thanks for your reply too. Yet, the same questions stand :
1) If I download a newer firmware from the website you linked, can i flash it without bricking the phone, or I need to somehow unroot the phone before flashing
2) I've looked for firmwares of my country ( Italy ), and it looks like not even October's update is here yet -.- Should I just search using a foreign country ( US, UK or whatever) ? and if so ... which one?
PS: I'm sorry for the probably trivial questions, I'm a total noob

kaharas said:
Thanks again for your time I am on a stock pre-rooted rom, but I've rooted a month or so ago, and I've already tried to reset the counter multiple times ( and I've restarted a lot of times too). Still, no success in changing my phone status.
Thanks for your reply too. Yet, the same questions stand :
1) If I download a newer firmware from the website you linked, can i flash it without bricking the phone, or I need to somehow unroot the phone before flashing
2) I've looked for firmwares of my country ( Italy ), and it looks like not even October's update is here yet -.- Should I just search using a foreign country ( US, UK or whatever) ? and if so ... which one?
PS: I'm sorry for the probably trivial questions, I'm a total noob
Click to expand...
Click to collapse
You can flash without unrooting. Only adverse thing that will happen is that you'll lose root and will have to root again.
Yes, your country seems to be late to the update cycle. You can wait for the update or if you really want it now you can flash to another countries' rom.. As long as it is an international version rom. So USA is a no-no.

MohJee said:
You can flash without unrooting. Only adverse thing that will happen is that you'll lose root and will have to root again.
Yes, your country seems to be late to the update cycle. You can wait for the update or if you really want it now you can flash to another countries' rom.. As long as it is an international version rom. So USA is a no-no.
Click to expand...
Click to collapse
Any advice about which one is international?
And, while we are at it ... how can I make triangle away work? this whole counter thing is setting a feud between me and my note 2

Read sticky thread by me in android original development section.
You can flash any stock rom.
Sent from my GT-N7100 using xda premium

I do hope this is relevant here, since I'm having much the same problems. I'm a bit of a noob, but I've done my research, as you may see from the post.
I plan to have stock ROM/Recovery with Mobile Odin and the RedPill kernel. I'm kind of stuck. Let me run you through what I did so far, to clarify:
Rooted with method 2 almost w/o update or modification.
Wanted back in on OTA, so flashed stock recovery from here.
Used TriangleAway, but it told me it couldn't get/set the counter. Told it to reboot and do it, but just powered off the phone and didn't turn into the mentioned "special boot mode".
Can't get into recovery after attempting TriangleAway, that just powers off the phone. Recovery bricked? Download mode works, though.
Here's what I want to do:
Stock recovery/ROM (latest) with OTA and root, and Kies updatability.
Working stock recovery.
RedPill Kernel (optional since don't know how it may react with OTA/Kies)
Mobile Odin
Titanium Backup for preserving my Apps
I'm ready to use Titanium Backup for preserving my Apps, but will it preserve my settings/alarms? Or are those backed up to Samsung/Google?
You can refer me to the rooting post, if needed. Just give me an overview of what needs to be done and I'll do the rest.
EDIT: Came up with a possible solution.
Titanium Backup
Ketan's Thread
Stock ROM
Root: Method 1.
Mobile Odin
Optional
Convert Redpill to *.tar.md5 using Toolkit
Flash using mobile Odin
Titanium Backup (Restore)
What are the chances of this succeeding? Can I do the "optional" ones and not lose OTA?
Thanks a lot to any effort anyone may make to answer.

Thanks again everybody for your replies
I was wondering if anybody else had any idea about how to solve my main problem, that seems to have gone unnoticed for a while now : my counter is still at 1.
I've tried using triangle and restart teh device once before checking the status, but nothing has changed.
As I've already said, I used method one, and flashed a prerooted stock rom, but it looks like the counter is increased from 0 to 1 everytime I reboot.

kaharas said:
Thanks again everybody for your replies
I was wondering if anybody else had any idea about how to solve my main problem, that seems to have gone unnoticed for a while now : my counter is still at 1.
I've tried using triangle and restart teh device once before checking the status, but nothing has changed.
As I've already said, I used method one, and flashed a prerooted stock rom, but it looks like the counter is increased from 0 to 1 everytime I reboot.
Click to expand...
Click to collapse
i have the same situation, always shows 1, dr. recommend me flash stock via pc odin and do a full wipe, but i havent try it yet,
currently i just use custom kernel and triangle away set it reset on boot

emprize said:
i have the same situation, always shows 1, dr. recommend me flash stock via pc odin and do a full wipe, but i havent try it yet,
currently i just use custom kernel and triangle away set it reset on boot
Click to expand...
Click to collapse
NOTE: I have the LTE version (n7105) but I assume the following also applies to the n7100
I had the very same issue as the OP: I rooted the device using PC Odin with dr.ketan's method #1 but couldn't reset the counter with Triangle Away.
I then downloaded the firmware for my model from samfirmware and flashed it using Mobile Odin Pro with all the EverRoot options and all the wipes selected.
Now the device is rooted and the counter is back to zero
Hope this helps.

From ATT 4.3 knox, to Slimbean and to Slimkat

I tried this method and I got a Knox warranty void http://forum.xda-dev...555&postcount=1 . Not OP's fault,i'm sure it was my error.
Being I got the void anyway,I wiped and installed KIES_HOME_I317UCALJ2_I317ATTALJ2_215287_REV04_user _low_ship.tar.md5. It downgraded my BL to 4.1, then I rooted and flashed Slimbean 4.3 (with TWRP) with success. It counted against my binary download,but didn't trip knox again (Dont know if KNOX trips more then once). The only thing I did was used root explorer and deleted all Knox. Then I froze what was left with Titaniam.
EDIT
OK now I successfuly flashed the latest Slimkat with no problems what so ever. Still no trouble with Knox or bootloader. I have all backups of what I had installed if devs want to look and confirm what I have said is true.
Is this supposed to be possible or was people scared of tripping knox ????

BR7fan said:
I tried this method and I got a Knox warranty void http://forum.xda-dev...555&postcount=1 . Not OP's fault,i'm sure it was my error.
Being I got the void anyway,I wiped and installed KIES_HOME_I317UCALJ2_I317ATTALJ2_215287_REV04_user _low_ship.tar.md5. It downgraded my BL to 4.1, then I rooted and flashed Slimbean 4.3 (with TWRP) with success. It counted against my binary download,but didn't trip knox again (Dont know if KNOX trips more then once). The only thing I did was used root explorer and deleted all Knox. Then I froze what was left with Titaniam.
EDIT
OK now I successfuly flashed the latest Slimkat with no problems what so ever. Still no trouble with Knox or bootloader. I have all backups of what I had installed if devs want to look and confirm what I have said is true.
Is this supposed to be possible or was people scared of tripping knox ????
Click to expand...
Click to collapse
Link didn't work, so I couldn't see what you did....
You can check to see if Knox is tripped by turning off phone.
Once it’s off, you need to press this button combination: volume down, power button and home button. Keep them pressed until the download mode shows up. Once you’re there, you will be required to press volume up to enter the download mode or volume down to cancel and reboot the device. Press Up.
Upper left will show flash counts and last line will show if Knox is tripped.
Also to check which bootloader you are on:
search in play store - android system info - look in buildinfo
also there is an app called info - look in os
I should be in bed now..... I think this is right, open Android Terminal; type getprop ro.bootloader. That should tell you what bootloader you are on also.
I'm curious....

dicksteele said:
link didn't work, so i couldn't see what you did....
You can check to see if knox is tripped by turning off phone.
Once it’s off, you need to press this button combination: Volume down, power button and home button. Keep them pressed until the download mode shows up. Once you’re there, you will be required to press volume up to enter the download mode or volume down to cancel and reboot the device. Press up.
Upper left will show flash counts and last line will show if knox is tripped.
Also to check which bootloader you are on:
Search in play store - android system info - look in buildinfo
also there is an app called info - look in os
i should be in bed now..... I think this is right, open android terminal; type getprop ro.bootloader. That should tell you what bootloader you are on also.
I'm curious....
Click to expand...
Click to collapse
13i7ucubmk6
Knox is tripped. It happened when I was trying to downgrade using one of members method. But I did it by just installing the old att firmware
forum.xda-developers.com/showthread.php?t=2502464

BR7fan said:
13i7ucubmk6
Knox is tripped. It happened when I was trying to downgrade using one of members method. But I did it by just installing the old att firmware
forum.xda-developers.com/showthread.php?t=2502464
Click to expand...
Click to collapse
Interesting. Which firmware was it?
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app

dicksteele said:
interesting. Which firmware was it?
Sent from my samsung-sgh-i317 using xda premium 4 mobile app
Click to expand...
Click to collapse
_i317attalj2_215287_rev04

this is the problem I've been having: Copy and pasted from a thread I created.
So I have a AT&T Samsung Galaxy Note 2 that as of 5 hours ago was completely stock and running android 4.3 (the official one from AT&T). I got bored last night and decided I wanted to root my phone (something I hadn't yet done in the entire year I had my phone). So I looked up how to root, read the instructions all the way (I thought my research was complete). I rooted using the CF auto method. After doing that I flashed TWRP using ODIN. I also downloaded Titanium Backup, Rom Manager & My Backup Root. I tried to use all three of these applications to make a backup of my device so that I could flash the custom Rom I wanted without losing all my information. That is when my troubles began.
Whenever I tried to access any of these apps I got a pop up saying Unfortunately, SuperSU has stopped and a notification stating An attempt to access a secure area on your phone without authorization has been blocked. None of the apps would run either and just kept freezing or loading forever.Thinking I'd done something wrong I repeated the root process all over again. I still kept getting the same notifications though. I typed in the unauthorized access notification message into google and discovered about Knox. Doing some tinkering of my own I went to settings (more tab)>>security>>device administrators>> unchecked knox>>deactivate. After deactivating Knox I once again tried to gain root access and had no success. I followed the advice from previous threads and tried to change all Knox.apk files to knox.apk.bak using Explorer, I downloaded Android terminal and tried to delete knox via the command line su pm... That also did nothing. I went to the market and tried to download the SuperSU app by CHAINFIRE, it wouldn't work as it already says the app is installed but offers me no updating options. I also downloaded the Update SuperSU zip file and tried to flash it. My phone wont boot into recovery though so that hasn't gotten me anywhere. Downloaded Rom Manager and GooManager to try to get into recovery mode and still no success. later flashed philz_touch via ODIN as people who had similar problems had posted about it working for them. Didn't work for me. Flashed TWRP again using ODIN and am now just scratching my head trying to figure out how to fix this issue.
I'm personally not worried much about the warranty stuff but am more concerned with the fact that I can't root my phone. All I want is to be able to load a custom rom (MIUI v5) onto my phone. Any and all help would be greatly appreciated.... If you've seen someone else with an issue like mine please just redirect me to the proper thread then.
p.s. I also tried running the root verify app and it got stuck on a loading page.
When I power my phone off and boot into recovery mode (or whatever its called) my stats read as:
ODIN MODE
Product name: SGH-I317
Custom Binary Download: Yes (7 counts) - this is from all my attempts to reroot and flash different recoveries
Current Binary: Custom
System Status: Custom
Knox Warranty Void: 1
AP SWAEV: A2

Ladyfinesse08 said:
this is the problem I've been having: Copy and pasted from a thread I created.
So I have a AT&T Samsung Galaxy Note 2 that as of 5 hours ago was completely stock and running android 4.3 (the official one from AT&T). I got bored last night and decided I wanted to root my phone (something I hadn't yet done in the entire year I had my phone). So I looked up how to root, read the instructions all the way (I thought my research was complete). I rooted using the CF auto method. After doing that I flashed TWRP using ODIN. I also downloaded Titanium Backup, Rom Manager & My Backup Root. I tried to use all three of these applications to make a backup of my device so that I could flash the custom Rom I wanted without losing all my information. That is when my troubles began.
Whenever I tried to access any of these apps I got a pop up saying Unfortunately, SuperSU has stopped and a notification stating An attempt to access a secure area on your phone without authorization has been blocked. None of the apps would run either and just kept freezing or loading forever.Thinking I'd done something wrong I repeated the root process all over again. I still kept getting the same notifications though. I typed in the unauthorized access notification message into google and discovered about Knox. Doing some tinkering of my own I went to settings (more tab)>>security>>device administrators>> unchecked knox>>deactivate. After deactivating Knox I once again tried to gain root access and had no success. I followed the advice from previous threads and tried to change all Knox.apk files to knox.apk.bak using Explorer, I downloaded Android terminal and tried to delete knox via the command line su pm... That also did nothing. I went to the market and tried to download the SuperSU app by CHAINFIRE, it wouldn't work as it already says the app is installed but offers me no updating options. I also downloaded the Update SuperSU zip file and tried to flash it. My phone wont boot into recovery though so that hasn't gotten me anywhere. Downloaded Rom Manager and GooManager to try to get into recovery mode and still no success. later flashed philz_touch via ODIN as people who had similar problems had posted about it working for them. Didn't work for me. Flashed TWRP again using ODIN and am now just scratching my head trying to figure out how to fix this issue.
I'm personally not worried much about the warranty stuff but am more concerned with the fact that I can't root my phone. All I want is to be able to load a custom rom (MIUI v5) onto my phone. Any and all help would be greatly appreciated.... If you've seen someone else with an issue like mine please just redirect me to the proper thread then.
p.s. I also tried running the root verify app and it got stuck on a loading page.
When I power my phone off and boot into recovery mode (or whatever its called) my stats read as:
ODIN MODE
Product name: SGH-I317
Custom Binary Download: Yes (7 counts) - this is from all my attempts to reroot and flash different recoveries
Current Binary: Custom
System Status: Custom
Knox Warranty Void: 1
AP SWAEV: A2
Click to expand...
Click to collapse
I think I'm tracking.....
First try going to settings, More, them go to application manager.
Remove super su. Go back to Google Play and download latest supersu.
Superuser executable does not get deleted when removing supersu app
See if that works
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app

or flash download.chainfire.eu/282/SuperSU/ SuperSu with TWRP

BR7fan said:
or flash download.chainfire.eu/282/SuperSU/ SuperSu with TWRP
Click to expand...
Click to collapse
That looks better.
I looked at updater script and it deletes old stuff first before installing.
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app

dicksteele said:
I think I'm tracking.....
First try going to settings, More, them go to application manager.
Remove super su. Go back to Google Play and download latest supersu.
Superuser executable does not get deleted when removing supersu app
See if that works
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks so much for your help. I tried doing what you said. When I go to SuperSU application under application manager it won't allow me to reomove it. All I can do is Turn it OFF. When If I go to the play market after turning it off the only option I get is to enable it again. Looking under App Info though it's showing that I'm on version 1.93 of SuperSu. I think from all the stuff I've been reading I'm supposed to be on version 1.95.
As for flashing it your TWRP I can't because I can't load into recovery mode with TWRP. The only thing thats working for me is ODIN. Not sure if there's a way to flash from ODIN or not but I personally don't know of one (I'm new to ODIN).

Ladyfinesse08 said:
Thanks so much for your help. I tried doing what you said. When I go to SuperSU application under application manager it won't allow me to reomove it. All I can do is Turn it OFF. When If I go to the play market after turning it off the only option I get is to enable it again. Looking under App Info though it's showing that I'm on version 1.93 of SuperSu. I think from all the stuff I've been reading I'm supposed to be on version 1.95.
As for flashing it your TWRP I can't because I can't load into recovery mode with TWRP. The only thing thats working for me is ODIN. Not sure if there's a way to flash from ODIN or not but I personally don't know of one (I'm new to ODIN).
Click to expand...
Click to collapse
http://goo.im/devs/OpenRecovery/t0lteatt/openrecovery-twrp-2.6.3.1-t0lteatt.img.tar
Here's a copy to flash in ODIN. If you can't boot into recovery after this, there are other things we can try from ODIN.
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app

BR7fan said:
_i317attalj2_215287_rev04
Click to expand...
Click to collapse
K. I understand now. I think.
You were on MK6, the 4.3 OTA bootloader.
You tried flashing seanz MJ4 4.3 Leak bootloader and Knox didn't appreciate that.
You could still ODIN back to the LJ2 because it doesn't include a bootloader.

dicksteele said:
K. I understand now. I think.
You were on MK6, the 4.3 OTA bootloader.
You tried flashing seanz MJ4 4.3 Leak bootloader and Knox didn't appreciate that.
You could still ODIN back to the LJ2 because it doesn't include a bootloader.
Click to expand...
Click to collapse
I dont want to falsh back. What had me puzzled is that I thought that with knox you couldnt flash any rom because of secure bootloader. I am able to flash what ever I want with out any extra steps. Its like it was before knox came around.

BR7fan said:
I dont want to falsh back. What had me puzzled is that I thought that with knox you couldnt flash any rom because of secure bootloader. I am able to flash what ever I want with out any extra steps. Its like it was before knox came around.
Click to expand...
Click to collapse
Knox wasn't/isn't as restrictive as we imagined. It's more of an annoyance.
Biggest annoyance is not being able to flash older bootloaders, and the easily viewable notice that Knox had been tripped.
We've had it long enough to know our limitations
Man's got to know his limitations.
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app

[Q] SGH-I317M with KNOX can not be rooted

Mine Note II is SGH-I317M with baseband version of I317MVLUCMK5 and KNOX.
I have tried CF-Auto-Root and Root SuperSU but weren't able to root my note II.
I have tried using different version of Odin, reinstalled the USB driver and tried using philz touch and cwm6 root to backup and root.
Nothing worked........Can't even start SuperSU.....
KNOX keep giving me security notice "An attempt to access a secure area on your device without authorisation has been blocked."
I also tried an updated Superuser. Still nothing worked....
Any idea anyone?
Thank you very much.

Stewegg said:
Mine Note II is SGH-I317M with baseband version of I317MVLUCMK5 and KNOX.
I have tried CF-Auto-Root and Root SuperSU but weren't able to root my note II.
I have tried using different version of Odin, reinstalled the USB driver and tried using philz touch and cwm6 root to backup and root.
Nothing worked........Can't even start SuperSU.....
KNOX keep giving me security notice "An attempt to access a secure area on your device without authorisation has been blocked."
I also tried an updated Superuser. Still nothing worked....
Any idea anyone?
Thank you very much.
Click to expand...
Click to collapse
You need to disable knox first
http://forum.xda-developers.com/showthread.php?p=49860203

Stewegg said:
Can't even start SuperSU
Click to expand...
Click to collapse
This is really weird, when I did this to my SGH-I747/M it was updated to stock 4.3 so it had KNOX and I got the same message as you but to disable it, all I did was open SuperSU and it prompts me to disable KNOX and then it's "fully" rooted and I could install a custom recovery after that.
I know it worked on the S3 because it's currently rooted running a custom ROM. Are you using the right version of Odin? I was trying to use 1.85 I think it was and it wasn't working at first, I tried 3.09 and it worked like a dream.
Did you remember to go into the Security Settings and turn off Reactivation Lock? I know this can play a factor when rooting with KNOX.
Also, KNOX never goes away, even though I'm running an AOSP ROM now on the S3, it still shows the KNOX counter with 0x1, even with it disabled. I can also not get any ROM's lower then 4.3 to work anymore so I can no longer run RootBox 4.2.2 on the S3.
I'm not sure if it's just me, or just my phone, but since that KNOX update was already on it when I got the phone used, it will not let me go to any ROM's lower then 4.3

VeeDaub said:
This is really weird, when I did this to my SGH-I747/M it was updated to stock 4.3 so it had KNOX and I got the same message as you but to disable it, all I did was open SuperSU and it prompts me to disable KNOX and then it's "fully" rooted and I could install a custom recovery after that.
I know it worked on the S3 because it's currently rooted running a custom ROM. Are you using the right version of Odin? I was trying to use 1.85 I think it was and it wasn't working at first, I tried 3.09 and it worked like a dream.
Did you remember to go into the Security Settings and turn off Reactivation Lock? I know this can play a factor when rooting with KNOX.
Also, KNOX never goes away, even though I'm running an AOSP ROM now on the S3, it still shows the KNOX counter with 0x1, even with it disabled. I can also not get any ROM's lower then 4.3 to work anymore so I can no longer run RootBox 4.2.2 on the S3.
I'm not sure if it's just me, or just my phone, but since that KNOX update was already on it when I got the phone used, it will not let me go to any ROM's lower then 4.3
Click to expand...
Click to collapse
Where is the Reactivation Lock located?
I can not find it in the Security Settings.

mrevankyle said:
You need to disable knox first
http://forum.xda-developers.com/showthread.php?p=49860203
Click to expand...
Click to collapse
I was following the steps in the post you have posted.
When I tried to flash the DrKetan_MultiTool_AdvanceV5, it gives me an error: E:signature verification failed. and stopped the flash.
Any idea?

Stewegg said:
I was following the steps in the post you have posted.
When I tried to flash the DrKetan_MultiTool_AdvanceV5, it gives me an error: E:signature verification failed. and stopped the flash.
Any idea?
Click to expand...
Click to collapse
hey man i have the same phone as you, just found an easy way to root it after struggling. Just updated to Stock 4.3 Bell Firmware using odin, completely fresh phone.
How to root it:
1. Flash philz recovery in odin "philz_touch_6.19.3-t0lteatt.tar.md5" (Download mode= Vol Down + Home + Power)
2. Reboot back into android once
3. Power off phone
4. Boot into recovery (Vol Up + Home + Power)
5. Goto philz settings->Reroot rom (or something to that effect)
6. Recovery will tell you done, and to reboot and install SuperSU from Play Store
7. Reboot download and install SuperSU from Play Store
8. Open SuperSU it will immediately ask if you would like to disable Knox.. say yes
9. Done
Link to philz recovery tar for our phone i317M
http://goo.im/devs/philz_touch/CWM_Advanced_Edition/t0lteatt/philz_touch_6.19.3-t0lteatt.tar.md5

Does this work?
My wife's Rogers note2 is bone stock running I317MVLUCMK5.
She is paranoid about Knox and possibly killing her phone.
She wants me to get it rooted, but I'm struggling to find a clear cut answer.
Also, it would be better if anyone knows how to (if possible) downgrade to 4.1.2 and start from there... As I know how to do that one like the back of my hand.
Sent from my SGH-I317 using Tapatalk

Stewegg said:
Mine Note II is SGH-I317M with baseband version of I317MVLUCMK5 and KNOX.
I have tried CF-Auto-Root and Root SuperSU but weren't able to root my note II.
I have tried using different version of Odin, reinstalled the USB driver and tried using philz touch and cwm6 root to backup and root.
Nothing worked........Can't even start SuperSU.....
KNOX keep giving me security notice "An attempt to access a secure area on your device without authorisation has been blocked."
I also tried an updated Superuser. Still nothing worked....
Any idea anyone?
Thank you very much.
Click to expand...
Click to collapse
Simple. First get the root. Like the su binary and stuff. once you are rooted get suersu. What I mean by first get root is literally get root through a program or something. After this you will have root but you wont have root access. So get supersu now and launch the app. It will ask to update your su binary. Say yes. then the thing will say something about knox then ask you if you want to try to disable knox. Tap yes and knox should be disabled and your su binary should be updated and working.

I'm exactly in the middle of nowhere .. Try to root with CF method. After the first try and reboot. I got the knox alert "unauthorized, bla, bla" the thing is that I can't get the full root or return to stock. Also when I tried to install knox in order to Uninstaller it, I can't. My phone is not allowed to use knox any more... I already tried to download Su and update it in order to disable knox with no success.... Stupid knox and stupid 4.3:crying:

My phone is I317M Rogers, it run stock 4.3. I followed this guide, http://forum.xda-developers.com/showthread.php?t=2618261 rooted success.

Eun-Hjzjined said:
Does this work?
My wife's Rogers note2 is bone stock running I317MVLUCMK5.
She is paranoid about Knox and possibly killing her phone.
She wants me to get it rooted, but I'm struggling to find a clear cut answer.
Also, it would be better if anyone knows how to (if possible) downgrade to 4.1.2 and start from there... As I know how to do that one like the back of my hand.
Sent from my SGH-I317 using Tapatalk
Click to expand...
Click to collapse
ifentanez said:
I'm exactly in the middle of nowhere .. Try to root with CF method. After the first try and reboot. I got the knox alert "unauthorized, bla, bla" the thing is that I can't get the full root or return to stock. Also when I tried to install knox in order to Uninstaller it, I can't. My phone is not allowed to use knox any more... I already tried to download Su and update it in order to disable knox with no success.... Stupid knox and stupid 4.3:crying:
Click to expand...
Click to collapse
koodiifin said:
hey man i have the same phone as you, just found an easy way to root it after struggling. Just updated to Stock 4.3 Bell Firmware using odin, completely fresh phone.
How to root it:
1. Flash philz recovery in odin "philz_touch_6.19.3-t0lteatt.tar.md5" (Download mode= Vol Down + Home + Power)
2. Reboot back into android once
3. Power off phone
4. Boot into recovery (Vol Up + Home + Power)
5. Goto philz settings->Reroot rom (or something to that effect)
6. Recovery will tell you done, and to reboot and install SuperSU from Play Store
7. Reboot download and install SuperSU from Play Store
8. Open SuperSU it will immediately ask if you would like to disable Knox.. say yes
9. Done
......
Click to expand...
Click to collapse
koodiifin's way worked perfectly!
Thank you koodiifin!

[GUIDE] how to root Sph-L710/L710T S3 4.4.2 (updated as of 8/19/2015)

I'm sorry i had the wrong links and because of this i had miss information. So i formally apologize by updating with the proper links.
this first method doesn't work with the Sph-L710T or the Sph-L710 on NJ2/NJ3
First method: You can root the stock 4.4.2 ND8/NDC:laugh:
1st. Make sure your on 4.4.2 ND8 or NDC
2nd. Download Towel Root
3rd. Place Towel Root in sdcard or internal storage
4th. With any file manager find and install Towel Root
5th. Open Towel Root and well root
6th. Go to play store and download https://play.google.com/store/apps/details?id=eu.chainfire.supersu&hl=en and also https://play.google.com/store/apps/details?id=stericson.busybox&hl=en let super user update the binary
7th. Flash any recovery you want {personally i went with PhilZ Touch (this was before PhilZ had a root Option)}
8th. Enjoy your rooted stock 4.4.2 ND8/NDC
Down below is one more way too root Stock ND8/NDC/NJ2/NJ3 or NF4/OA3 (L710T) and basically any other update
(link to the almighty ODIN)
Second Method: mostly recommended
1st. Odin flash TWRP
2nd. In Odin choose PDA, PA or AP then select the TWRP Tar you just downloaded
3rd. Make sure Auto reboot is unchecked (also at this time your s3 should be in download mode)
4th. Hit start and let Odin let it finish!!
5th. Hold power button to turn off your S3, after it turns off about 10 seconds later it will turn back on to the battery charging screen so before that quickly hold Volume+ and Home, to boot into recovery
6th. now your in TWRP
7th. so to root your stock rom with TWRP flash the following file SuperSU.zip by Chain fire (pro tip. Install any other custom recovery the same way I did for TWRP above if it is in .tar format)
and here is Philz recovery for the D2Lte 6.48.4 ( which you must flash in TWRP)
and here is TWRP that was made specifically for the D2Rephersher/triband/L710T TWRP (which you must flash in a recovery)
Third method Most recent.
Hidyman said:
This is in reference to Samsung Galaxy S3 for Boost Mobile SPH-L710.
Just want to let anyone out there that updated their Boost S3 to L710VPUC0J1 know that you can still root and/or ROM your phone.
Use the instructions to (use Odin to) update the recovery to TWRP first (in the second set of instructions). I had trouble trying to go right to PhilZ Recovery (which I believe is based off of ClockWorkMod). I Had to do the TWRP (twrp-2.8.7.0-d2spr.img.tar) first.
It was the only way to get it to actually accept the recovery, not sure why, maybe because the latest Samsung firmware fixed an exploit or two.
This is an older phone, but it is still a viable one.
I hope this helps someone out there.
It took me a while to figure this quandary out.
As always this WILL flag KNOX, but I'm sure this won't be an issue at this date and time (8/2016).
Click to expand...
Click to collapse

work on ND8 rom? sprint phone?

Tekone said:
work on ND8 rom? sprint phone?
Click to expand...
Click to collapse
i want to say yes but towel root does come with a warning that it might brick your device.....but i want to say yes since most things that can be done to the ND8 can be done to the NDC and also in reverse order.....so try it and report back it will be good to know if it works on both bootloaders

Sprint S3 Android 4.4.2 ND8-It works!
I just used this method to root my Sprint S3 running Android 4.4.2 and ND8, since my USB port is on the fritz, and it worked successfully. I have root, and was able to do a full apps backup with Titanium Backup, and gained root access in ES File Explorer. Next, download and install a custom backup. Thanks, great job, and could not have been made easier to do!

oops
Rooted the phone in one click. Unfortunately, I lost all data (no 3G or 4G connection). Did I goof? I'm looking in the stickies and can't seem to find an answer. I'd appreciate any help I can get.

henhun said:
Rooted the phone in one click. Unfortunately, I lost all data (no 3G or 4G connection). Did I goof? I'm looking in the stickies and can't seem to find an answer. I'd appreciate any help I can get.
Click to expand...
Click to collapse
ND8 or NDC? have you tried updating your profile/PRL?

6th_Hokage said:
ND8 or NDC? have you tried updating your profile/PRL?
Click to expand...
Click to collapse
Ya know. People keep talking about ND8 and ND___. I have no idea what that means. I know I should be embarrassed.
UPDATE: FIGURED IT OUT, BASEBAND VERSION. GOTCHA. IT IS NDC.
I was JUST coming back to update my post. I DID update the PRL and restarted my phone. That seems to have done the trick. Thank GOD I got my data connection back!! It worked. Even though I found the info somewhere else, thank you so much for the quick reply. PRL update fixes the problem. You're awesome.

I used it before i had a custom recovery. And on reboot i wouldnt have root. After i ran it root checker told me i was rooted then reboot killed. I installed philz and all was ok
Sent from my SPH-L710 using XDA Free mobile app

jbnorton0524 said:
I used it before i had a custom recovery. And on reboot i wouldnt have root. After i ran it root checker told me i was rooted then reboot killed. I installed philz and all was ok
Sent from my SPH-L710 using XDA Free mobile app
Click to expand...
Click to collapse
many users of basically the same phone report different things with every root method out there. If it worked for you that's great tell other users what you did for it to work and if it didn't work, then ask for help and you will get help; some people don't have success with any method while others do with all of the methods.....my phone falls under every method.....

Successful Towelroot on VM Galaxy S3 4.4.2.NDC
6th_Hokage said:
you can root the stock 4.4.2
first step make sure your on 4.4.2
second step download Towel Root
third step place Towel Root in sdcard or internal storage
fourth step with any file manager find and install Towel Root
fifth step root
sixth step go to play store and download Superuser (Chainfire) and also Busy Box (Stericson) let super user update the binary
seventh step flash any recovery you want personally i went with Philliz Touch
eighth step if you want flash a custom rom now if not enjoy your rooted stock 4.4.2
Click to expand...
Click to collapse
Straight forward, fast and easy. I did notice the following:
1) Updating binary reported it did not successfully install. I've seen this before on other devices, but everything worked well. Ext SD and Camera all OK. Everything works fine so far - Titanium, Nandroid, Root Browser, etc.
2) At one point, I was directed to install Busy Box. Having done this on other devices, I said "Yes" and installed it.
3) I see that my device now shows Device Status as Custom ( was Normal before, if I remember correctly). Is this due to Busy Box?
4) Is Device Status the only way to know the KNOX Status? I see no yellow triangle as I did on my Galaxy Reverb.
5) I got a Google warning to uninstall Towelroot since it is usafe and a security exploit. I understand that.
I would like to verify the KNOX status and if tripped in the Towelroot process, to let potential users know of that possibility.
Thank You! And thanks to everyone who has continued to work on keeping root free!
Dave

dave260 said:
Straight forward, fast and easy. I did notice the following:
1) Updating binary reported it did not successfully install. I've seen this before on other devices, but everything worked well. Ext SD and Camera all OK. Everything works fine so far - Titanium, Nandroid, Root Browser, etc.
2) At one point, I was directed to install Busy Box. Having done this on other devices, I said "Yes" and installed it.
3) I see that my device now shows Device Status as Custom ( was Normal before, if I remember correctly). Is this due to Busy Box?
4) Is Device Status the only way to know the KNOX Status? I see no yellow triangle as I did on my Galaxy Reverb.
5) I got a Google warning to uninstall Towelroot since it is unsafe and a security exploit. I understand that.
I would like to verify the KNOX status and if tripped in the Towelroot process, to let potential users know of that possibility.
Thank You! And thanks to everyone who has continued to work on keeping root free!
Dave
Click to expand...
Click to collapse
Knox only notifies Samsung that your device isn't stock anymore not necessarily rooted like with a custom recovery and then flashed mods and what not but if you Odin the stock rom it resets the counters so Samsung will never know....and that i have noticed TowelRoot doesn't trip that counter.....only the recoveries and when you update the binary (<---completely forgot to fix that) you must hit the option normal not TWRP/CWM

churninern said:
I just used this method to root my Sprint S3 running Android 4.4.2 and ND8, since my USB port is on the fritz, and it worked successfully. I have root, and was able to do a full apps backup with Titanium Backup, and gained root access in ES File Explorer. Next, download and install a custom backup. Thanks, great job, and could not have been made easier to do!
Click to expand...
Click to collapse
That's great news because same boat here. It worked on 4.3 as well.
I had the phone hacked before and something must not be fully stock so the Ota fails.
I downloaded a package and mobile odin should flash it properly and then I can root it with this again and install a nice modified TouchWiz rom.

Darkangels6sic6 said:
That's great news because same boat here. It worked on 4.3 as well.
I had the phone hacked before and something must not be fully stock so the Ota fails.
I downloaded a package and mobile odin should flash it properly and then I can root it with this again and install a nice modified TouchWiz rom.
Click to expand...
Click to collapse
just a quick add on Mobile Odin and stock ND8/NDC don't mix at all

Knox Counter and "Device Status"
6th_Hokage said:
Knox only notifies Samsung that your device isn't stock anymore not necessarily rooted like with a custom recovery and then flashed mods and what not but if you Odin the stock rom it resets the counters so Samsung will never know....and that i have noticed TowelRoot doesn't trip that counter.....only the recoveries and when you update the recovery you must hit the option normal not TWRP/CWM
Click to expand...
Click to collapse
Thanks for your response. I may be over thinking these indicators. All I did was Towelroot, successfully. On the phone, the "About Device, Status" now says CUSTOM (was "Official"). The Knox counter according to app "Phone Info" shows Knox Counter at 0x0. As you said, since the counter is not tripped, should be no problem on warranty. So then Device Status CUSTOM is not a problem? I'm not really worried about warranty at this point, but I think I'll hold off further mods for another 6 moths.
Thanks again for your help!

6th_Hokage said:
just a quick add on Mobile Odin and stock ND8/NDC don't mix at all
Click to expand...
Click to collapse
Thanks. I tried the md8 and mk3 "mk3 is what it's on". Both just restart and get stuck on splash screen :/.
I have to go to download mode and and restart it that way to boot system back up.
Do you have any other suggestion. I'm not sure what part of the system is altered. It seems like a stock recovery and it's stock firmware "now rooted". Maybe the kernel.
I can't use USB at all.
I'm guessing maybe I should install twrp. Then install a stock zip or try out a 4.3 rom that way. I would like to get to md8 one way or another. Most md8 Roms want you to odin or flash an md8 base.

Darkangels6sic6 said:
Thanks. I tried the ND8 and MK3 "MK3 is what it's on". Both just restart and get stuck on splash screen :/.
I have to go to download mode and and restart it that way to boot system back up.
Do you have any other suggestion. I'm not sure what part of the system is altered. It seems like a stock recovery and it's stock firmware "now rooted". Maybe the kernel.
I can't use USB at all
I'm guessing maybe I should install TWRP. Then install a stock zip or try out a 4.3 rom that way. I would like to get to md8 one way or another. Most ND8 Roms want you to Odin or flash an md8 base.
Click to expand...
Click to collapse
cause they need the ND8 base to work as intended...my suggestion would be to get the usb port on your phone fixed but i don't know how expensive that will be

6th_Hokage said:
just a quick add on Mobile Odin and stock ND8/NDC don't mix at all
Click to expand...
Click to collapse
6th_Hokage said:
cause they need the ND8 base to work as intended...my suggestion would be to get the usb port on your phone fixed but i don't know how expensive that will be
Click to expand...
Click to collapse
I was afraid you would say that.

Holy crap. May I say, I am quite impressed. I never planned on rooting my S3 (I like it that much!) but this just looked so damn easy to do and it was!
For the curious! I have a Virgin Mobile S3, and I'm on Kitkat 4.4.2, baseband NDC. Verified root with Root Checker Basic. No problems with mobile data.
Many thank yous, 6th_Hokage!

strangelady said:
Holy crap. May I say, I am quite impressed. I never planned on rooting my S3 (I like it that much!) but this just looked so damn easy to do and it was!
For the curious! I have a Virgin Mobile S3, and I'm on Kitkat 4.4.2, baseband NDC. Verified root with Root Checker Basic. No problems with mobile data.
Many thank yous, 6th_Hokage!
Click to expand...
Click to collapse
your welcome strangelady and if you want check out the links in my signature area for other cool stuff

added two more t=root methods

[Q] did I root or didnt I?

hey guys so im a noob at all of this so noob it down for me please
the other day i tried rooting my phone and i thought i succeeded at doing so since the SuperSU (blue hashtag) app appeared in my apps. knox's also is disabling supersu from running. when i open up knox it reads "your device is not authorized to enter samsung knox mode" im guessing thats because of it being rooted? so when i downloaded root checker to see if my phone is rooted and it comes out that my phone is not rooted.
so is my phone rooted and knox is keeping su from running or did i not root properly?
any suggestions

The Knox counter was probably tripped previously, that's why it gave you that message. What method did you use for root, what android version, and what device do you have?

serio22 said:
The Knox counter was probably tripped previously, that's why it gave you that message. What method did you use for root, what android version, and what device do you have?
Click to expand...
Click to collapse
its 4.3 jellybean
i think the root was called clockwork? and i have the tmobile t-999

dean03TJ said:
its 4.3 jellybean
i think the root was called clockwork? and i have the tmobile t-999
Click to expand...
Click to collapse
That's a recovery, which tripped Knox when you flashed it. And I assume you flashed SuperSU after? Make sure it is the latest

serio22 said:
That's a recovery, which tripped Knox when you flashed it. And I assume you flashed SuperSU after? Make sure it is the latest
Click to expand...
Click to collapse
ummm no i didnt. i thought it was just a root and then add cyanogen. haha
have a good site?

towelroot and root66 have good reps for rooting. might want to check those.
err on the side of kindness

dean03TJ said:
ummm no i didnt. i thought it was just a root and then add cyanogen. haha
have a good site?
Click to expand...
Click to collapse
XDA has all the info you need.. Cyanogen is prerooted so it shouldn't have any problems, but I did notice you said you had SuperSU, which is not the root app it uses. It also sounds like SuperSU and the cm you flashed is outdated, that blue hash was dropped long ago.. Did you try to update it like I suggested? If you are on cm10 flash cm11 instead