Related
|Guide|How-To| Root & Install Custom Recovery for 4.3 / 4.4 Update |16 July 2014 |
Warning: Following any of these instructions will void your warranty, and could possibly cause irreparable harm to your device (i.e. bricked). If you do not understand these risks, stop here and do not proceed. If you do not know how to use Odin, stop here and do not proceed. I am not responsible for anything that happens to your device. YOU chose to follow this guide.
If you have not updated to 4.3, go here.
If you have not updated to 4.4, go here.
Finally, there is no guarantee that either method will work for you.
Root Method #1:
The first thing you should try is CF-Autoroot since this has worked for many users.
If you successfully root with this method, you can simply install Goo Manager or ROM Manager and install recovery.
This method failed for me after many attempts.
Edit:
Here is some potentially useful info for root method #1 from ansonantonym.
Root Method #2:
1) Reboot in to download mode
2) Flash TWRP with Odin via PDA
3) Reboot to recovery then flash SuperSu and the Knox Remover
4) Reboot
5) Download SuperSu from the Play Store
6) Open SuperSu and update the binary when prompted
7) Reboot
8) Enjoy rooted 4.3/4/4
Downloads:
Odin
TWRP (Odin flashable tar)
SuperSu (v1.65)
SuperSu (v2.01)
DE-SAMSUNGNIZER_KNOX_REMOVAL_SCRIPT_V1.0
If you found another method that worked for you, please post here so that others may benefit.
If you are uncertain about any of the steps above, please ask your questions here before proceeding.
Please be sure to thank Chainfire, Dees_Troy, and Kaito95.
*****
Noob here, first off I unrooted a while ago, then took the ota 4.3, is the bootloader locked? Cause according to the cf auto root site if your bootloader is locked you'll probably brick your phone if you flash the auto root? Also do these steps have to be in order? I tried rooting by other means and installing supersu first, wouldn't work so I removed knox with the script, and then updated supersu in the play store and still nothing, can I try to flash cf auto root now and then update supersu in the play store? Thanks a million, need this thing rooted
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
jeremyds45 said:
Noob here, first off I unrooted a while ago, then took the ota 4.3, is the bootloader locked? Cause according to the cf auto root site if your bootloader is locked you'll probably brick your phone if you flash the auto root? Also do these steps have to be in order? I tried rooting by other means and installing supersu first, wouldn't work so I removed knox with the script, and then updated supersu in the play store and still nothing, can I try to flash cf auto root now and then update supersu in the play store? Thanks a million, need this thing rooted
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Well, I'm not bricked, so I think that answers your question about the bootloader.
Do you have a custom recovery installed? I assume so since you say you flashed the Knox remover script. If you do have a custom recovery installed, just flash the SuperSu zip, then update in the Play Store.
upndwn4par said:
Well, I'm not bricked, so I think that answers your question about the bootloader.
Do you have a custom recovery installed? I assume so since you say you flashed the Knox remover script. If you do have a custom recovery installed, just flash the SuperSu zip, then update in the Play Store.
Click to expand...
Click to collapse
Ah it is so nice to have root again... Thank you so much for putting up with a noob.
Crazy events of a noob that lead me to root
Installed ota 4.3
Tried to root and install superuser by odin and then custom recovery to flash
Root didn't happen because of knox
Could only get to CWM custom recovery if it was right after odin and battery pull?...
Flashed the script to remove knox, which did remove knox
Tried the same root method as above and no root access
Tried supersu and then updating in play with no success
Changed security update settings etc nothing
Reset delvik, cache, permissions, etc nothing
Different root method and files for odin, and custom recovery stuck
Used files from this thread, went into custom recovery and flashed supersu
Installed supersu from play store...
Updated the binary using custom recovery
Rebooted...
ROOT access, all root applications work fine and root sticks even after reboots
I never messed with cf auto root method
THANK you guys for your time effort and sharing, helps noobs out like me a lot!
Sweet! I've missed root since I upgraded using the OTA file you provided. Looking forward to much other great things coming from you
Thank You
upndwn4par said:
Warning: Following any of these instructions will void your warranty, and could possibly cause irreparable harm to your device (i.e. bricked). If you do not understand these risks, stop here and do not proceed. If you do not know how to use Odin, stop here and do not proceed. I am not responsible for anything that happens to your device. YOU chose to follow this guide.
If you have not updated to 4.3, go here. Make sure you understand the risks and uncertainties described in the OP.
Finally, there is no guarantee that either method will work for you.
Root Method #1:
The first thing you should try is CF-Autoroot since this has worked for many users.
If you successfully root with this method, you can simply install Goo Manager or ROM Manager and install recovery.
This method failed for me after many attempts.
Root Method #2:
1) Reboot in to download mode
2) Flash TWRP with Odin via PDA
3) Reboot to recovery and flash SuperSu.
4) Flash the Knox Remover
5) Reboot
6) Download SuperSu from the Play Store
7) Update the binary when prompted
8) Reboot
8) Enjoy 4.3
Downloads:
Odin
TWRP (Odin flashable tar)
UpdateSuperSu
If you found another method that worked for you, please post here so that others may benefit.
If you are uncertain about any of the steps above, please ask your questions here before proceeding.
*****
Click to expand...
Click to collapse
Method two absolutely worked. Thank you so much. I was scared to flash TWRP but knowing you did it gave me the courage. Have full root and happy
questions about this root
Hi, I'm a little nervous with this root but I need the root as the phone is useless without it.
I have the [email protected] galaxy s3 I747 will all these files work with it im just double checking.
Also do you flash the knox remover the same way as you flash other things with the pda button?
Will I still be able to do factory restores?
Also I saw that knox remover removes a lot of apps, Can you install these deleted apps from the market if you need too?
THanks please let me know asap.
THANKS!!!! your a lifesaver didn't know how much longer i could take without root
Dunno where you guys got your 4.3 update from and how you got it working but I did the OTA and Root just does not want to stick. I used knox remover and Cf auto root but it loses root after a restart. SuperSu never opens and crashes as soon as you open it. I have a feeling Cf auto root is just not compatible for the ota 4.3 i747??
bkong said:
Dunno where you guys got your 4.3 update from and how you got it working but I did the OTA and Root just does not want to stick. I used knox remover and Cf auto root but it loses root after a restart. SuperSu never opens and crashes as soon as you open it. I have a feeling Cf auto root is just not compatible for the ota 4.3 i747??
Click to expand...
Click to collapse
use the TWRP method worked perfected for me
Thanks
PimpMyPC said:
Hi, I'm a little nervous with this root but I need the root as the phone is useless without it.
I have the [email protected] galaxy s3 I747 will all these files work with it im just double checking.
Also do you flash the knox remover the same way as you flash other things with the pda button?
Will I still be able to do factory restores?
Also I saw that knox remover removes a lot of apps, Can you install these deleted apps from the market if you need too?
THanks please let me know asap.
Click to expand...
Click to collapse
The second method worked great. I believe (and the way that worked for me) that you use your custom recovery to flash the knox script, not using Odin and pda. I don't think it removed anything other than knox, there is a different script for removing knox and att bloatware. Should still be able to factory reset... But can't guarantee that.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Root & Knox
When you go to Settings/More tab/Security/Device Administrators, You have KNOX and Android Device Manage. Both are unchecked on mine. So does that mean Knox is not working if unchecked and safe to try to Root?????
tailgunner9 said:
When you go to Settings/More tab/Security/Device Administrators, You have KNOX and Android Device Manage. Both are unchecked on mine. So does that mean Knox is not working if unchecked and safe to try to Root?????
Click to expand...
Click to collapse
Those settings are just for granting device administrator privileges. If unchecked, Knox is still doing it's thing, just not at an administrative level.
Yes, it is safe to try and root.
I have Android Device Manager as admin. That way if I ever lose my device I can just log in to the Play Store and locate and / or wipe the device.
To do this just flash the recovery.img file using odin and clicking the pda button correct?
Is there a way to freeze Knox instead of deleting it in the event I would want to go back to full stock?
After you are rooted, use an app like Titanium Backup(pro) or My Backup pro. Both will freeze it.
Root
If some of you out there use Root Method #2 and it works well and No problems, Please post and let us all know. Thanks
tailgunner9 said:
If some of you out there use Root Method #2 and it works well and No problems, Please post and let us all know. Thanks
Click to expand...
Click to collapse
I tried method 1 and failed.
Then tried method 2, but using a CMW tar that was posted yesterday.
I seem to be rooted!
So far no issues.. Just need to get everything setup as I had it in the leak.
indymx said:
I tried method 1 and failed.
Then tried method 2, but using a CMW tar that was posted yesterday.
I seem to be rooted!
So far no issues.. Just need to get everything setup as I had it in the leak.
Click to expand...
Click to collapse
Thanks indymx, may get the nerve up to try it on my AT&T S3. Let me know if you run into any problems. Guess Rom Manager and other programs that require Root are working Ok and you have rebooted few times to be sure it keeps Root?? Have Happy Thanksgiving.
sooo i was stock i took the OTA update to 4.3 mk6
i decided i didn't care about the knox counter so i rooted and custom recovery (this is the rom location http://forum.xda-developers.com/showthread.php?t=2589891) and this is the recovery location http://forum.xda-developers.com/showthread.php?t=2159652
now every thing is working (SU, Titanium Back up, and so on)
however when i try certain apps (game killer, game chi) it says i don't have root
i have searched everywhere but i am not seeing any posts about this
any help would be greatly appreciated
You could flash superSU from recovery to system...
That often corrects the issue...
Did you download superSU from the market and update it ??
Try that first....and if no change....flash this....g
http://download.chainfire.eu/382/SuperSU/UPDATE-SuperSU-v1.93.zip
Sent from my NOTE 2.750...
Courtesy of our amazing developers...
gregsarg said:
You could flash superSU from recovery to system...
That often corrects the issue...
Did you download superSU from the market and update it ??
Try that first....and if no change....flash this....g
http://download.chainfire.eu/382/SuperSU/UPDATE-SuperSU-v1.93.zip
Sent from my NOTE 2.750...
Courtesy of our amazing developers...
Click to expand...
Click to collapse
thanks for the help i will try this now
gregsarg said:
You could flash superSU from recovery to system...
That often corrects the issue...
Did you download superSU from the market and update it ??
Try that first....and if no change....flash this....g
http://download.chainfire.eu/382/SuperSU/UPDATE-SuperSU-v1.93.zip
Sent from my NOTE 2.750...
Courtesy of our amazing developers...
Click to expand...
Click to collapse
i uninstalled superSU then went to the market and downloaded and updated that didn't work it was still the same
no i have downloaded and installed from customer recovery and when i open superSU it says i need to manually re-root my phone so i guess i need to re flash my rom from original post?
Try installing the current version of SuperSU via Odin.. you shouldn't have to reinstall the rom...
Once SuperSU is installed, boot phone, check Play Store for updates for SuperSU and install if any. Then run SuperSU, update the binary if prompted, then when asked to disable Knox, answer yes. You should be good to go.
Zen Arcade said:
Try installing the current version of SuperSU via Odin.. you shouldn't have to reinstall the rom...
Once SuperSU is installed, boot phone, check Play Store for updates for SuperSU and install if any. Then run SuperSU, update the binary if prompted, then when asked to disable Knox, answer yes. You should be good to go.
Click to expand...
Click to collapse
okay i found it and did it and now i am back where i started most things work but the 2 app's i use most still say root permission denied (granted permission in superSU)
mrnewspaper said:
okay i found it and did it and now i am back where i started most things work but the 2 app's i use most still say root permission denied (granted permission in superSU)
Click to expand...
Click to collapse
Remove them from SU list. Restart app and approve the SU request again.....
dicksteele said:
Remove them from SU list. Restart app and approve the SU request again.....
Click to expand...
Click to collapse
okay done and no change
mrnewspaper said:
okay i found it and did it and now i am back where i started most things work but the 2 app's i use most still say root permission denied (granted permission in superSU)
Click to expand...
Click to collapse
Which apps?
Zen Arcade said:
Which apps?
Click to expand...
Click to collapse
the apps that wont work are game chi and game killer
the apps that are working looks like all of my apps that require root other then those 2
even root checker says i do have root
mrnewspaper said:
the apps that wont work are game chi and game killer
the apps that are working looks like all of my apps that require root other then those 2
even root checker says i do have root
Click to expand...
Click to collapse
Game Killer - Comments on Play Store show that this is a known issue with 4.3 and SuperSU with this app.
GameCIH - (I assume this is what you meant) Comments on Play Store also show a known issue with 4.3. Some comments from dev about enabling USB debugging, but it appears to be a 4.3 issue.
Looks like you are out of luck for now unless you step back to 4.2 or below.
Zen Arcade said:
Game Killer - Comments on Play Store show that this is a known issue with 4.3 and SuperSU with this app.
GameCIH - (I assume this is what you meant) Comments on Play Store also show a known issue with 4.3. Some comments from dev about enabling USB debugging, but it appears to be a 4.3 issue.
Looks like you are out of luck for now unless you step back to 4.2 or below.
Click to expand...
Click to collapse
i didn't see those notes but thanks to everyone for all the help and i will look in to stepping back again (i bricked the first time)
If you have the MK6 bootloader, avoid the MA4 stock package. You'll need the LJ2 stock package (which does not have a bootloader in it). See this guide... you can follow it up to the point where you have MH3 on your phone and then stop:
http://forum.xda-developers.com/showthread.php?t=2618447
Zen Arcade said:
If you have the MK6 bootloader, avoid the MA4 stock package. You'll need the LJ2 stock package (which does not have a bootloader in it). See this guide... you can follow it up to the point where you have MH3 on your phone and then stop:
http://forum.xda-developers.com/showthread.php?t=2618447
Click to expand...
Click to collapse
awesome thank you
Hello people,
I have a Note 2 (SGH-i317m) running the MVLUCMK5 Official Android 4.3 rom. I flashed the cf-autoroot from chainfire's website using odin and download mode, updated super SU as soon as the device booted, disabled Knox and got the device rooted. Root was working fine. Titanium backup could restore the app backup and everything.
However, when I restarted the phone, the root was gone. Any idea what's going on? I will have to flash CF again and it will work. But the flash counter keeps counting every flash. Is there a permanent root method for 4.3?
PS: Sorry to hijack this thread. I figured there was a relevant discussion going on, why clutter the section with a new thread. Also, since my post count is low, I couldn't post in CF's thread.
pavanchirmade said:
Hello people,
I have a Note 2 (SGH-i317m) running the MVLUCMK5 Official Android 4.3 rom. I flashed the cf-autoroot from chainfire's website using odin and download mode, updated super SU as soon as the device booted, disabled Knox and got the device rooted. Root was working fine. Titanium backup could restore the app backup and everything.
However, when I restarted the phone, the root was gone. Any idea what's going on? I will have to flash CF again and it will work. But the flash counter keeps counting every flash. Is there a permanent root method for 4.3?
PS: Sorry to hijack this thread. I figured there was a relevant discussion going on, why clutter the section with a new thread. Also, since my post count is low, I couldn't post in CF's thread.
Click to expand...
Click to collapse
Sounds like you may be using an older version of cf-auto-root? Try this one via Odin:
main - http://autoroot.chainfire.eu/
i317m - http://download.chainfire.eu/279/CF-Root/CF-Auto-Root/CF-Auto-Root-t0ltecan-t0ltevl-sghi317m.zip
Zen Arcade said:
Sounds like you may be using an older version of cf-auto-root? Try this one via Odin:
main - http://autoroot.chainfire.eu/
i317m - http://download.chainfire.eu/279/CF-Root/CF-Auto-Root/CF-Auto-Root-t0ltecan-t0ltevl-sghi317m.zip
Click to expand...
Click to collapse
I flashed the same one.
Are you running the stock kernel?
After you flash cf-auto-root and boot phone, what do the contents of this file look like?
/system/etc/install-recovery.sh
Does it reference SuperSU and run daemonsu or does it reference recovery-from-boot.p ?
Zen Arcade said:
Are you running the stock kernel?
After you flash cf-auto-root and boot phone, what do the contents of this file look like?
/system/etc/install-recovery.sh
Does it reference SuperSU and run daemonsu or does it reference recovery-from-boot.p ?
Click to expand...
Click to collapse
Here's a screenshot.
That's the correct file...
A deeper dive would involve looking at the permissions and properties of su and daemonsu in /system/xbin as well as a few other SuperSU related files in /system and subdirectories.
If you are running a custom kernel it's possible that it is pushing an older version of SuperSU (or other superuser app).
Do you have only the SuperSU app installed (i.e. no SuperUser or other app in the app drawer)?
Reaching at this point as it's not typical for the current versions of SuperSU to lose root.
One thing you can try is root with current, boot phone, immediately run SuperSU, choose "Full Unroot", reboot boot phone, then shutdown and reflash cf-auto-root and see if it sticks.
As for flash counter, once you get root to stick, you can use Triangle Away to reset that to zero - works for everything but the knox warranty counter.
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
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
Some tips for those who already took the OG5 OTA update and want root (will be obvious to most of you, and most of this has already been covered in other posts, but some might benefit from this guide with download links included):
1. Copy the BeastMode kernel zip to your phone or SD card.
2. Start Odin3 v3.10.6
3. Place the TWRP tar in the AP slot
4. Uncheck Auto Reboot in the options tab
5. Flash TWRP -- when it's finished flashing, disconnect USB and pull the battery for 10 seconds (on my phone, if I put the battery in too soon, it boots without pressing the power key)
6. Put the battery back in and boot to TWRP
7. Install the modified kernel zip you copied in step 1, and reboot.
8. Since you're in TWRP, might as well clear the cache.
At this point, there are a number of ways to get SuperSU on your phone. My TWRP asked me if I wanted it to install SuperSU, I said yes, but I already had SuperSU installed on my phone, anyway.
You can also use TWRP to install the SuperSU zip.
My phone complained about "KNOX has unfortunately stopped", so I just used Titanium to freeze all the KNOX apps, which cured that.
Be very patient the first time you run apps that request root. It will pop up the "grant" dialog eventually, but sometimes it's slow to do that after a boot.
NOTES: Some users are reporting that TWRP won't load. It may have to do with tripping that reactivation lock with Odin. Once done, it's possible TWRP can't deal with it. So you may be able to get around that by using Odin to install CWM recovery instead of TWRP.
Also, try rebooting recovery again after the flash to make sure the root prompt is clear. If it is booting the system, go into security and disable the reactivation lock.
Still getting the business about slow to wake or launcher not responding? Try adding the line below to end of your build.prop but have one empty line at bottom with no added spaces to the end this line:
ro.HOME_APP_ADJ=1
(thanks to samep for the added info in NOTES)
Will this process work on the Galaxy s5 with og5 5.11
Will this process work on the Galaxy s5 with og5 5.11, I no this is the note section but it appears to be the same build number in the same manufacturer is it possible for someone to report this kernel to the galaxy s5 and root it that way? What exactly is happening here on the note for those of you that wouldn't work on the s5?
Dmary said:
Will this process work on the Galaxy s5 with og5 5.11, I no this is the note section but it appears to be the same build number in the same manufacturer is it possible for someone to report this kernel to the galaxy s5 and root it that way? What exactly is happening here on the note for those of you that wouldn't work on the s5?
Click to expand...
Click to collapse
PM sent.
Sent from my SM-N910P using Tapatalk
So, its been about a year since I rooted a phone, but I feel like I'm missing something at the beginning of the instructions. In the video
https://www.youtube.com/watch?t=32&v=k2oOvf5tOCY
it goes over the auto root process, but that hasn't been updated. Is that something I need to run first anyway? Wouldn't it not work due to the mismatch of android version?
Oh, never mind. It froze at the TWRP screen, but a restart fixed that.
I would like to know if it's possible on the S5 as well...G900V...Everywhere i've read says it's not.
samep said:
PM sent.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
When I try to flash twrp, odin says failed. Any suggestions?
Thanks so much for this guide! Just got a new Note 4 and I'm about to root as well. Is TWRP still giving issues installing? Should I just go with CMW recovery? any other tips would be greatly appreciated. Just want to make sure I cover all bases before I begin...
Newbie_from_NJ said:
Thanks so much for this guide! Just got a new Note 4 and I'm about to root as well. Is TWRP still giving issues installing? Should I just go with CMW recovery? any other tips would be greatly appreciated. Just want to make sure I cover all bases before I begin...
Click to expand...
Click to collapse
TWRP is fine for most. Steps 4, 5 and 6 are important to assure TWRP recovery sticks.
If you decide to flash a custom ROM and get a binary failure, reboot recovery and try again.
Sent from my SM-N910P using Tapatalk
samep said:
Steps 4, 5 and 6 are important to assure TWRP recovery sticks.
Click to expand...
Click to collapse
Step 6, in order to do this, i will need to press button combinations on the phone, correct?
Do you happen to know them? If not, I'm sure Google to the rescue.
Sent from my SM-N910P using Tapatalk
Newbie_from_NJ said:
Step 6, in order to do this, i will need to press button combinations on the phone, correct?
Do you happen to know them? If not, I'm sure Google to the rescue.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
From power off, Vol+, Home + Power.
Sent from my SM-N910P using Tapatalk
I am also curious about whether this would work on a G900V.
Anyone try this on their 920v????
samep said:
PM sent.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
Could you please reply about G900V? I would greatly appreciate it.
AcidBurn22 said:
Could you please reply about G900V? I would greatly appreciate it.
Click to expand...
Click to collapse
I sent the PM to not clutter this thread with off-topic discussion.
Sorry, I don't have this phone, nor have I rooted one.
If you need help or don't know where to start, I'd suggest reading thread below before asking in thread:
http://forum.xda-developers.com/showpost.php?p=61688768&postcount=1
Reading through the OP's threads, the same thing started at OE1 update that started here, you can no longer downgrade in Odin once taking this one and later updates; it progressively worsens. Regarding your carrier, it appears that root prior to OG5 update is a prerequisite as well as steps to keep root in the update process (those do not apply here). But I don't claim to know any more about it than you so read, search and ask in the appropriate thread. Best wishes for success; perhaps it's not as grim as I describe it. I only researched a few minutes, following closed threads to links to next thread, starting here:
http://forum.xda-developers.com/showpost.php?p=61682294&postcount=242
If you have a choice, don't take the OE1 update until you're rooted and clear on how to keep root through updates. But again, I'm not claiming to know any more than yourself, possibly less with the effort I gave.
Anyone else finding this through search, please keep this thread on topic. Refer to your specific thread regarding phone model and carrier. Thanks.
Sent from my SM-N910P using Tapatalk
DaggettBeaver said:
Some tips for those who already took the OG5 OTA update and want root (will be obvious to most of you, and most of this has already been covered in other posts, but some might benefit from this guide with download links included):
1. Copy the BeastMode kernel zip to your phone or SD card.
2. Start Odin3 v3.10.6
3. Place the TWRP tar in the AP slot
4. Uncheck Auto Reboot in the options tab
5. Flash TWRP -- when it's finished flashing, disconnect USB and pull the battery for 10 seconds (on my phone, if I put the battery in too soon, it boots without pressing the power key)
6. Put the battery back in and boot to TWRP
7. Install the modified kernel zip you copied in step 1, and reboot.
8. Since you're in TWRP, might as well clear the cache.
At this point, there are a number of ways to get SuperSU on your phone. My TWRP asked me if I wanted it to install SuperSU, I said yes, but I already had SuperSU installed on my phone, anyway.
You can also use TWRP to install the SuperSU zip.
My phone complained about "KNOX has unfortunately stopped", so I just used Titanium to freeze all the KNOX apps, which cured that.
Be very patient the first time you run apps that request root. It will pop up the "grant" dialog eventually, but sometimes it's slow to do that after a boot.
NOTES: Some users are reporting that TWRP won't load. It may have to do with tripping that reactivation lock with Odin. Once done, it's possible TWRP can't deal with it. So you may be able to get around that by using Odin to install CWM recovery instead of TWRP.
Also, try rebooting recovery again after the flash to make sure the root prompt is clear. If it is booting the system, go into security and disable the reactivation lock.
Still getting the business about slow to wake or launcher not responding? Try adding the line below to end of your build.prop but have one empty line at bottom with no added spaces to the end this line:
ro.HOME_APP_ADJ=1
(thanks to samep for the added info in NOTES)
Click to expand...
Click to collapse
Thanks for this. I have Sprint SM-N910P 5.1.1 and want to root to debloat it.
I have rooted my previous phones. Where do I get the OG5 so I can proceed in rooting my Note 4?
Thanks in advance.:good:
Reivaj1803 said:
Thanks for this. I have Sprint SM-N910P 5.1.1 and want to root to debloat it.
I have rooted my previous phones. Where do I get the OG5 so I can proceed in rooting my Note 4?
Thanks in advance.:good:
Click to expand...
Click to collapse
Chainfire auto root for Note 4 has been updated. You could root with that. OK1 is the latest update; no reason to go back to an old update. You can still run a custom OG5 ROM if you like. I just don't recommend going backwards in Odin. Some stock tars just aren't able to flash after more recent updates are taken.
Sent from my SM-N910P using Tapatalk
samep said:
Chainfire auto root for Note 4 has been updated. You could root with that. OK1 is the latest update; no reason to go back to an old update. You can still run a custom OG5 ROM if you like. I just don't recommend going backwards in Odin. Some stock tars just aren't able to flash after more recent updates are taken.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
I wasn't aware of the latest update, thanks for the heads up.
I have never tried Chainfire auto root. I found Chainfire post http://forum.xda-developers.com/note-4/orig-development/sm-n910-cf-auto-root-t2897428
I'll try this route.
Thank you sir, greatly appreciate it. ???
samep said:
Chainfire auto root for Note 4 has been updated. You could root with that. OK1 is the latest update; no reason to go back to an old update. You can still run a custom OG5 ROM if you like. I just don't recommend going backwards in Odin. Some stock tars just aren't able to flash after more recent updates are taken.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
I have an issue I'm hoping you could help me with.
I posted this in the Chainfire thread, but have not received any response.
I rooted my Sprint Note 4 SM-N910P via Chainfire Auto Root. With the exception of 1 issue of being stuck in the bootloader where I had to remove the battery and then boot into recovery manually, all went well.
Once it was done and rebooted I got a message during boot, 'Set Warranty Bit: Kernel'
I have SM-N910P 5.1.1 and SU with Titaniun Backup Pro. Reason was to get rid of the bloatware.
I have un-installed the bloatware via TB and the confirmations show they have been deleted with strikethrough but no sooner that I go to check top confirm, they are active with the strikethrough removed.
I also get, out of the blue, prompt to download massive amounts of bloatware I never had to begin with "Sprint Default Configuration: Select to Install New Sprint Default Apps". At first thought it was an update so i downloaded it and along came uber, nba, stock care racing, sprint fun app and sprint international app and a few others.
I tried the same with those, to un-install via TB, and while some have been un-installed, the remaining have not and I get the message prompt to install again.
Anyone idea how I got this and how I can get rid of it?
Reivaj1803 said:
I have an issue I'm hoping you could help me with.
I posted this in the Chainfire thread, but have not received any response.
I rooted my Sprint Note 4 SM-N910P via Chainfire Auto Root. With the exception of 1 issue of being stuck in the bootloader where I had to remove the battery and then boot into recovery manually, all went well.
Once it was done and rebooted I got a message during boot, 'Set Warranty Bit: Kernel'
I have SM-N910P 5.1.1 and SU with Titaniun Backup Pro. Reason was to get rid of the bloatware.
I have un-installed the bloatware via TB and the confirmations show they have been deleted with strikethrough but no sooner that I go to check top confirm, they are active with the strikethrough removed.
I also get, out of the blue, prompt to download massive amounts of bloatware I never had to begin with "Sprint Default Configuration: Select to Install New Sprint Default Apps". At first thought it was an update so i downloaded it and along came uber, nba, stock care racing, sprint fun app and sprint international app and a few others.
I tried the same with those, to un-install via TB, and while some have been un-installed, the remaining have not and I get the message prompt to install again.
Anyone idea how I got this and how I can get rid of it?
Click to expand...
Click to collapse
I believe it was determined that titanium wasn't working correctly due to lack of busybox. OsmOsis wrote a nice script to install busybox that works for systemless root as well as the traditional system root method.
Goto the link below and look for his link to busybox installer and install that in recovery.http://forum.xda-developers.com/showpost.php?p=40409356&postcount=1
If you don't want the custom recovery, use Stericson Busybox in Google Play, instead.
The Sprint apps are likely getting pushed by a root folder /preload You can't freeze this with titanium and how you deal with that may leave indicators to detect that you modified system. Mounting to delete may trigger that and make it not possible to full un-root to take OTA for update. But you could just freeze the preloaded applications after they update. If you use the application manager in Settings, you get the option to remove updates and disable some apps but not all apps. I'm not sure how this applies to preload.
If OTA capability is not of importance, you can consider taking further steps to get a better kernel, make root more stable and modify system and read only partitions for more customization like deleting the preload directory.
So the solution would depend on your preferences. Retain OTA capability with strict SELinux Enforcing mode or go for more customization, not caring for OTA updates but waiting for update stock tar and electing a more stable root with custom kernel? Which would you prefer?
Sent from my SM-N910P using Tapatalk
samep said:
I believe it was determined that titanium wasn't working correctly due to lack of busybox. OsmOsis wrote a nice script to install busybox that works for systemless root as well as the traditional system root method.
Goto the link below and look for his link to busybox installer and install that in recovery.http://forum.xda-developers.com/showpost.php?p=40409356&postcount=1
If you don't want the custom recovery, use Stericson Busybox in Google Play, instead.
The Sprint apps are likely getting pushed by a root folder /preload You can't freeze this with titanium and how you deal with that may leave indicators to detect that you modified system. Mounting to delete may trigger that and make it not possible to full un-root to take OTA for update. But you could just freeze the preloaded applications after they update. If you use the application manager in Settings, you get the option to remove updates and disable some apps but not all apps. I'm not sure how this applies to preload.
If OTA capability is not of importance, you can consider taking further steps to get a better kernel, make root more stable and modify system and read only partitions for more customization like deleting the preload directory.
So the solution would depend on your preferences. Retain OTA capability with strict SELinux Enforcing mode or go for more customization, not caring for OTA updates but waiting for update stock tar and electing a more stable root with custom kernel? Which would you prefer?
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
I actually did remove and disabled most the apps that I was able to. The rest there were not options, other than root.
My preference was to root, maintain OTA capabilities and remove the bloatware.
What option/s would best suit that preference?