Related
Hi guys,
I am new to the xda forums and I have been researching about rooting my note 10.1 2014 p600 (WIFI). I have three questions about rooting my device.
1. How would I update my tab with root? I heard you can't get OTA updates.
2. What is the best and safest way to root?
3. How do I get TWRP and is it good?
I haven't installed knox on it yet and I am a beginner to linux and have done research so I know what root is.
dudeian said:
Hi guys,
I am new to the xda forums and I have been researching about rooting my note 10.1 2014 p600 (WIFI). I have three questions about rooting my device.
1. How would I update my tab with root? I heard you can't get OTA updates.
2. What is the best and safest way to root?
3. How do I get TWRP and is it good?
I haven't installed knox on it yet and I am a beginner to linux and have done research so I know what root is.
Click to expand...
Click to collapse
Ok, First, for the p600 if you root, you will trip Knox which will void your warranty and there is no way around this and this is the only way to root your model (p600), If you don't care about warranty then continue...
1) Download this file https://dl.dropboxusercontent.com/u/11938873/CF-Auto-Root-lt03wifi-lt03wifixx-smp600.zip then unzip, you will see this file CF-Auto-Root-lt03wifi-lt03wifixx-smp600.tar.md5.
2) Turn Off Tablet, Hold Volume Down + Power. Follow the instructions on the screen to get to download mode (Odin mode).
Rooting Instructions
1.Flash the CF-Auto-Root-lt03wifi-lt03wifixx-smp600.tar.md5 file with Odin v3.09 (put in AP slot, don't change any other settings, click start)
2.Let it do its trick! boot up then go to play store download and install supersu in order to update supersu to the latest binary.
3. Boot back into Odin mode and flash TWRP version 2.6.3.3 found here https://goo.im/devs/OpenRecovery/lt03wifiue/
That's all!
buhohitr said:
Ok, First, for the p600 if you root, you will trip Knox which will void your warranty and there is no way around this and this is the only way to root your model (p600), If you don't care about warranty then continue...
1) Download this file then unzip, you will see this file CF-Auto-Root-lt03wifi-lt03wifixx-smp600.tar.md5.
2) Turn Off Tablet, Hold Volume Down + Power. Follow the instructions on the screen to get to download mode (Odin mode).
Rooting Instructions
1.Flash the CF-Auto-Root-lt03wifi-lt03wifixx-smp600.tar.md5 file with Odin v3.09 (put in AP slot, don't change any other settings, click start)
2.Let it do its trick! boot up then go to play store download and install supersu in order to update supersu to the latest binary.
3. Boot back into Odin mode and flash TWRP version 2.6.3.3 found here
That's all!
Click to expand...
Click to collapse
Thanks! This is great help.
buhohitr said:
Ok, First, for the p600 if you root, you will trip Knox which will void your warranty and there is no way around this and this is the only way to root your model (p600), If you don't care about warranty then continue...
Click to expand...
Click to collapse
Knox is just a shortcut to the install link, Does this mean it's not installed or is the shortcut just extras (I don't know how to post screenshots).
dudeian said:
Knox is just a shortcut to the install link, Does this mean it's not installed or is the shortcut just extras (I don't know how to post screenshots).
Click to expand...
Click to collapse
I don't understand what you are saying???
When I said tripped Knox void warranty is that your device detected that you installed unauthorized software which tripped the knox counter. You can see this by boot into download mode (Odin mode) and you should see a line like this:
Warranty bit: 1 (factory is 0x0)
I hope that what you're asking!
buhohitr said:
I don't understand what you are saying???
When I said tripped Knox void warranty is that your device detected that you installed unauthorized software which tripped the knox counter. You can see this by boot into download mode (Odin mode) and you should see a line like this:
Warranty bit: 1 (factory is 0x0)
I hope that what you're asking!
Click to expand...
Click to collapse
Yup.
ok, now i'm getting confused.
my p600 is still on 4.3 jellybean. but from what i read, as long as did not update to kitkat firmware, i can still unroot and reverse the warranty bit bcoz they don't have knox yet. but it'll be too late if i updated to kikat right? btw, i used cf-auto-root.
just weeks ago i rooted my p600 and flashed stock recovery, so now my p600 thinks its stock official firmware, even say so in about device.
i haven't tried unrooting it yet to confirm that i can get warrenty back by flashing back whole stock firmware bcoz i don't want to redo all settings again. but thats the impression i'm geting.
anyhow if i can't really reverse that warranty thing i don't really care anyways. i warranty my stuff better than they do it, and since i think i can still get updates, it bothers me even less if its unreversible. but in the case if i'm right, and i can reverse that warranty bit. maybe one day i'd like to update to kitkat. then what? i'll have to have knox in my system and i can't reverse warranty counter anymore?
is there a way i can update to a custom kikat firmware (one day) and not have knox so i'll still be able to get warranty back?
i kind of realized the dilemma i have here since if i own the device for more than a yr, my warranty wouldn't matter anymore. am i just thinking too much and worrying myself?
kazukiflame said:
ok, now i'm getting confused.
my p600 is still on 4.3 jellybean. but from what i read, as long as did not update to kitkat firmware, i can still unroot and reverse the warranty bit bcoz they don't have knox yet. but it'll be too late if i updated to kikat right? btw, i used cf-auto-root.
just weeks ago i rooted my p600 and flashed stock recovery, so now my p600 thinks its stock official firmware, even say so in about device.
i haven't tried unrooting it yet to confirm that i can get warrenty back by flashing back whole stock firmware bcoz i don't want to redo all settings again. but thats the impression i'm geting.
anyhow if i can't really reverse that warranty thing i don't really care anyways. i warranty my stuff better than they do it, and since i think i can still get updates, it bothers me even less if its unreversible. but in the case if i'm right, and i can reverse that warranty bit. maybe one day i'd like to update to kitkat. then what? i'll have to have knox in my system and i can't reverse warranty counter anymore?
is there a way i can update to a custom kikat firmware (one day) and not have knox so i'll still be able to get warranty back?
i kind of realized the dilemma i have here since if i own the device for more than a yr, my warranty wouldn't matter anymore. am i just thinking too much and worrying myself?
Click to expand...
Click to collapse
Yes you're confused!!. Knox has nothing to do with warranty bit, once this tripped, you can't undo doesn't matter you on 4.3 or 4.4.
I'm a little confused on a few other issues. I have read over 40 pages on another thread here about rooting etc and I couldn't find the answer to a few questions. I've just successfully rooted using the most recent instructions (P600 - CF Auto root) but in earlier instructions (about a year ago) you had to also install the stock recovery file using Odin. Is that a necessary step? Is it needed for OTA updates? Since I've read that OTA updates will unroot and possibly prevent you from rooting at all, is it best to just forget about OTAs and flash up to date files from this site? Is it also prudent to turn off auto updating in the settings.
If I'm not installing custom roms and backed up using Titanium Pro do I really need to install TWRP? Any other benefits other than nandroid? Thanks
jbarr3 said:
I'm a little confused on a few other issues. I have read over 40 pages on another thread here about rooting etc and I couldn't find the answer to a few questions. I've just successfully rooted using the most recent instructions (P600 - CF Auto root) but in earlier instructions (about a year ago) you had to also install the stock recovery file using Odin. Is that a necessary step? Is it needed for OTA updates? Since I've read that OTA updates will unroot and possibly prevent you from rooting at all, is it best to just forget about OTAs and flash up to date files from this site? Is it also prudent to turn off auto updating in the settings.
If I'm not installing custom roms and backed up using Titanium Pro do I really need to install TWRP? Any other benefits other than nandroid? Thanks
Click to expand...
Click to collapse
Once you rooted you can't use OTA update any more. So the easiest going forward is to flash TWRP and use it to flash pre-rooted rom from this site.
Thanks buhohitr
I guess I'm installing TWRP tonight. There are many versions up to 2.8 I think. Which one do you recommend for P600? I've tried searching for "installing TWRP" but there were no obvious hits like there were for rooting. Which is the key thread?
To my first question, I'm assuming that the later root methods automatically installs or leaves the stock recovery as earlier methods needed to load it. Am I right?
jbarr3 said:
I've tried searching for "installing TWRP" but there were no obvious hits like there were for rooting.
Click to expand...
Click to collapse
OK found the thread and I just read the last 55 pages (that took a while) and boy is it scary. So many problems. Touch not accurate, inverted screens, certain versions failing eg 2.7, can't access external SD card, continual looping, booting into the old recovery , OTG cables not working, time zones can't be set properly, some say turn off autoboot in odin and some say don't change default settings etc etc. the list goes on and on. I likened it to a bushfire or tornado. Some houses still stand and some don't and you want to know the silly thing here, I am an experienced computer teacher with a degree in computer science and I've upgraded firmware on over a hundred devices over the years and yet all this rooting and recovery stuff is another world. The rooting process, admittedly, was a piece of cake and the instructions for flashing TWRP seems easy too but after that there seems to be so many problems. So hit and miss.
All i want to do is load TWRP on a P600. I will only load custom ROMs when a new firmware version comes out. Can someone alleviate my fears who has successfully loaded TWRP recently on a P600 using ODIN without massive tweaking to get it going. What version TWRP did you use and did you turn off autoboot or not?
PS Have I posted this in the correct section?
Took the plunge and loaded the latest TWRP 2.8.1 and it worked perfectly except I could only back to the main SD storage and not my extSD. I ended up, as a work around, moving the backup files to the extSD drive and PC.
I think I was worried unnecessarily.
Q&A for [Root][Port] Cf-Autoroot T700 [Tab S 8.4]
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:
galaxy tab s stuck on battery screen after using the cf-Autoroot
I tried rooting my galaxy tab s 8.4 using the cf-Autoroot method however at the end it said failed. I attempted to restart tablet but it was stuck on download mode, finally after searching forums I found one that explained how to power it off, and it said if I did it I would be golden. Now I have 2 choices battery screen or off. Please help I have the stock firmware but no way to reinstall
Does this root method reset or wipe the device?
@lbert said:
Does this root method reset or wipe the device?
Click to expand...
Click to collapse
Nope just installs supersu and root. You will still have your apps.
cf autorootf
I was just going to say - towelroot won't trip KNOX - at least as it applies to the 705, AND, the tab pro version as well. So I curious why folks would still use CF, if they're concerned about the 0x1 flag.
hillg001 said:
I was just going to say - towelroot won't trip KNOX - at least as it applies to the 705, AND, the tab pro version as well. So I curious why folks would still use CF, if they're concerned about the 0x1 flag.
Click to expand...
Click to collapse
Well no one has tried downgrading to a kernel that towelroot could of worked with. Thought those builds were also old we do not know it if works. But people have claimed they got their tablet replaced(hardware deffect) even if they tripped knox so thats probaly why they use CF
CF Autoroot for Samsung Galaxy Tab S 8.4
Used this method;
http://forum.xda-developers.com/galaxy-tab-s/development/root-cf-autoroot-t700-t2805366
Worked amazing, so easy to do and pleased that I'm rooted now! Now able to use Sixaxis and PS3 controller with all my specific profiles for various games as needed.
Build KOT49H.T700XXU1ANL2 (SM-T700 WiFi only)
WAY TO GO Beantown!!! Many thanks!!!
can not use screen mirroring after root ....
can not use screen mirroring after root .... can you fix this ?
Tripped Knox...?
I used this method and Knox Warranty went from Knox Warranty Void: 0 to Knox Warranty Void: 1. I have never had to deal with this, but is the warranty voided now? Does it mean anything that it is in gray and not red or something?
Maybe I miss read all the posts saying this will not trip Knox, but..... Why did this happen? I guess it isn't that big of a deal, as I just bought this last night, I can easily just exchange it for a new one, but if it will keep happening, there isn't much of a point.
Thanks.
Alyusha said:
I used this method and Knox Warranty went from Knox Warranty Void: 0 to Knox Warranty Void: 1. I have never had to deal with this, but is the warranty voided now? Does it mean anything that it is in gray and not red or something?
Maybe I miss read all the posts saying this will not trip Knox, but..... Why did this happen? I guess it isn't that big of a deal, as I just bought this last night, I can easily just exchange it for a new one, but if it will keep happening, there isn't much of a point.
Thanks.
Click to expand...
Click to collapse
Seriously? Directly from the post that you downloaded the root package from --
"Warning: I cannot be held responsible for anything you do to your phone, rooting is optional! This Does Trip The Knox Warranty Bit Built into the Bootloader of the Tab S 10.5"
In Big BOLD letters.
hawkxcore said:
Seriously? Directly from the post that you downloaded the root package from --
"Warning: I cannot be held responsible for anything you do to your phone, rooting is optional! This Does Trip The Knox Warranty Bit Built into the Bootloader of the Tab S 10.5"
In Big BOLD letters.
Click to expand...
Click to collapse
Seriously? Directly from the post that I download the root package from --
TITLE
"[Root][Port] Cf-Autoroot T700 [Tab S 8.4]"
I rooted the 8.4, not 10.5. Not sure what difference this would have since the hardware for the two are identical. In retrospect maybe I should have triple checked, but that exact warning you quoted would lead one to believe it would would trip Knox on the 10.5 and not 8.4.
Thanks
CF-Autoroot T700 [Tab S 8.4] lost after OTA
Hello, I had previously rooted my Tab S 8.4 with CF-Autoroot from Beanstown with no problem. However I received some OTA update from Samsung and now I have lost root access. I tried to root again as I previously had...and even though Odin says it was a success, I still don't have root. Has anyone else ran into this?
dhughes20 said:
Hello, I had previously rooted my Tab S 8.4 with CF-Autoroot from Beanstown with no problem. However I received some OTA update from Samsung and now I have lost root access. I tried to root again as I previously had...and even though Odin says it was a success, I still don't have root. Has anyone else ran into this?
Click to expand...
Click to collapse
Cfautoroot needs to be updated. Just install twrp recovery and flash supersu.zip (google it) with twrp and you should get root
DUHAsianSKILLZ said:
Cfautoroot needs to be updated. Just install twrp recovery and flash supersu.zip (google it) with twrp and you should get root
Click to expand...
Click to collapse
That did it! Thanks so much for the help! Very appreciated!
linux
I want to flash twrp in sm-t700 using heimdall and linux does it work there?
PreachyPreachyMachine said:
Used this method;
http://forum.xda-developers.com/galaxy-tab-s/development/root-cf-autoroot-t700-t2805366
Worked amazing, so easy to do and pleased that I'm rooted now! Now able to use Sixaxis and PS3 controller with all my specific profiles for various games as needed.
Build KOT49H.T700XXU1ANL2 (SM-T700 WiFi only)
WAY TO GO Beantown!!! Many thanks!!!
Click to expand...
Click to collapse
I have same build (KOT49H.T700XXU1ANL2) but could not find chainfire autoroot to root my device (only chainfire build version available is KOT49H.T700XXU1ANF9). Did not want to first downgrade to that version for fear of bricking. Seems like this Beantown rooting worked for you....just wanted to reconfirm same build number before trying.
Thanks
Doesn't matter what build your running. Just flash the one for your model.
ashyx
Today, 07:43 PM |#18
Senior Member1,146 posts Thanks: 378
Doesn't matter what build your running. Just flash the one for your model.
According to the "autoroot.chainfire.eu" website, it is build specific:
"[*] Warning: The above tutorial is only for Android 4.4.2 with the built id KOT49H.T700XXU1ANF9.
[*] If your device isnt running on the same built id KOT49H.T700XXU1ANF9, then you need to download and flash the firmware based on the same build id then after try to root your device from the above method."
This is what is scaring me from trying.
tomkasan said:
ashyx
Today, 07:43 PM |#18
Senior Member1,146 posts Thanks: 378
Doesn't matter what build your running. Just flash the one for your model.
According to the "autoroot.chainfire.eu" website, it is build specific:
"
[*] Warning: The above tutorial is only for Android 4.4.2 with the built id KOT49H.T700XXU1ANF9.
[*] If your device isnt running on the same built id KOT49H.T700XXU1ANF9, then you need to download and flash the firmware based on the same build id then after try to root your device from the above method."
This is what is scaring me from trying.
Click to expand...
Click to collapse
Ok have it your way, cuz I don't know what I'm talking about. :banghead:
Better tell the rooted lollipop users they shouldn't have used it.
Maybe you should look at my Sig.
for a Samsung Galaxy Note Edge (AT&T SM-N915A) Has anyone used ODIN to flash 4.4.4 from Lollipop (which I read doesn't trip knox) and then used Kingroot to get temporary root and then install Safestrap? I didn't really find any custom roms, but when booting from Safestrap, wouldn't root still be available even if you installed the stock Lollipop rom as the SS rom? Or would it be too difficult to remove the recovery if that's present in the stock LP rom so it doesn't mess with SS if you boot from it?
Slimicus said:
for a Samsung Galaxy Note Edge (AT&T SM-N915A) Has anyone used ODIN to flash 4.4.4 from Lollipop (which I read doesn't trip knox) and then used Kingroot to get temporary root and then install Safestrap? I didn't really find any custom roms, but when booting from Safestrap, wouldn't root still be available even if you installed the stock Lollipop rom as the SS rom? Or would it be too difficult to remove the recovery if that's present in the stock LP rom so it doesn't mess with SS if you boot from it?
Click to expand...
Click to collapse
I did use ODIN to go back to KitKat and then used Kingoroot, but the safestrap part your talking about I have no clue. Was unaware of any safestrap for the Notre 4 or Edge.
Back on Lollipop unrooted though. Found the temp root annoying and with FF browser and AdBlock plugin I'm getting by
help
rquinn19 said:
I did use ODIN to go back to KitKat and then used Kingoroot, but the safestrap part your talking about I have no clue. Was unaware of any safestrap for the Notre 4 or Edge.
Back on Lollipop unrooted though. Found the temp root annoying and with FF browser and AdBlock plugin I'm getting by
Click to expand...
Click to collapse
Can you plz send me a link for the kitkat firmware?
shylude said:
Can you plz send me a link for the kitkat firmware?
Click to expand...
Click to collapse
http://forum.xda-developers.com/note-edge/general/att-note-4-edge-kitkat-odin-tar-files-t3108344
What's up guys? I need some help rooting my N-915A, can you guys show me the path. I'm running lolllipop 5.0.1
Is there ever going to be a root for this phone? Its almost a year and nothing is out yet? I have never had to wait this long for any android phone before. so frustrating
Anything yet
xxswagga1xx said:
What's up guys? I need some help rooting my N-915A, can you guys show me the path. I'm running lolllipop 5.0.1
Click to expand...
Click to collapse
Sorry, no permanent root yet... But the 5.1.1 upgrade is available, just remember to clear the cache before attempting to upgrade.
djwasel said:
Is there ever going to be a root for this phone? Its almost a year and nothing is out yet? I have never had to wait this long for any android phone before. so frustrating
Click to expand...
Click to collapse
Probably not, but that is my opinion and not based on fact.
sandog12 said:
Anything yet
Click to expand...
Click to collapse
Sorry, no permanent root yet...
So it is possible now to get temporary root access using kingroot on 5.1.1 but I am hoping someone get this information to chainfire so that chainfire can use it to come up with a permanent root using odin.
How could i upgrade to 5.1.1 im using 915a in pakistan? Can any on help me ?
hey guys,
I am from Vietnam and i just 've bought the SM-N910A (said that from ATT) in Vietnam. I used RootChecker and Phone INFO to get to check my phone.
The result is my phone was ROOTED!!!. I restarted some times but the ROOT is still accessed.
I tried to use Root Explorer to copy/paste from/into system folder, it's ok like other rooted devices.
I'm following xda-note edge and see everyone's saying that NO way to permanent root ATT note egde.
I also dont know what method the seller used to root my edge, but i think it's permanently rooted.
I've NOT try to unlock bootloader neither install recovery. There seem to be no official method for ATT edge. I am afraid bricking my device.
I upload some screen to show you my note. Thanks and need your advice, guys
datbi_201 said:
hey guys,
I am from Vietnam and i just 've bought the SM-N910A (said that from ATT) in Vietnam. I used RootChecker and Phone INFO to get to check my phone.
The result is my phone was ROOTED!!!. I restarted some times but the ROOT is still accessed.
I tried to use Root Explorer to copy/paste from/into system folder, it's ok like other rooted devices.
I'm following xda-note edge and see everyone's saying that NO way to permanent root ATT note egde.
I also don't know what method the seller used to root my edge, but i think it's permanently rooted.
I've NOT try to unlock bootloader neither install recovery. There seem to be no official method for ATT edge. I am afraid bricking my device.
I upload some screen to show you my note. Thanks and need your advice, guys
Click to expand...
Click to collapse
When you moved data into /system did you remove it before rebooting, or did you leave it in /system and were still able to boot?
If you could enable USB Debugging and open a shell with ADB and type "ps", then post the output, that may be a place to start.
Recently, kingroot has been able to get root on my note, but after 5-10 minutes I get ANRs and the phone crashes, then I have to re flash with Odin to go back to stock. I have logcat logs up to where it crashes as well.
I'm on 5.1.1
Edit
5 minutes after I posted this AT&T tried pushing a security update. Probably to fix this.
Sent from my SAMSUNG-SM-N915A using XDA-Developers mobile app
cabewse said:
Recently, kingroot has been able to get root on my note, but after 5-10 minutes I get ANRs and the phone crashes, then I have to re flash with Odin to go back to stock. I have logcat logs up to where it crashes as well.
I'm on 5.1.1
Edit
5 minutes after I posted this AT&T tried pushing a security update. Probably to fix this.
Sent from my SAMSUNG-SM-N915A using []
Click to expand...
Click to collapse
Hi, i have a n915a too but the baseband ends in BOC8 and the last firmware is 5.0.1, if i use the stock firmware 5.1.1 from other baseband? it will brick the phone?.
is there a way to install different firmware from another model?, like change n915a to n915f or something like that
sorry, my english is not good.
kashaki said:
Hi, i have a n915a too but the baseband ends in BOC8 and the last firmware is 5.0.1, if i use the stock firmware 5.1.1 from other baseband? it will brick the phone?.
is there a way to install different firmware from another model?, like change n915a to n915f or something like that
sorry, my english is not good.
Click to expand...
Click to collapse
Bringing this back to life, we are now September of 2016. Any way of permanent root on Note Edge?
Lethal Ludacy said:
So it is possible now to get temporary root access using kingroot on 5.1.1 but I am hoping someone get this information to chainfire so that chainfire can use it to come up with a permanent root using odin.
Click to expand...
Click to collapse
I root my phone using kingroot at&t SM-N915A 5.1.1
stunomatic0 said:
I root my phone using kingroot at&t SM-N915A 5.1.1
Click to expand...
Click to collapse
I did temp root with KingRoot too. I went and disable the bothering Carrier IQ which was taking all my zerolemon battery. And also I disable most most of the bloatware of at&t.
Let's hope Chainfire or someone co.e with the permanent one.
Sent from my SAMSUNG-SM-N910A using Tapatalk
Customs boot icon
I rooted my at&t note edge using king root. Then I installed SuperSU and used the option to install binaries in "normal" mode. Then the phone rebooted and in the booting screen i got an icon with an unlocked lock that said "Custom" then the phone booted normally no problem.
I dont know if this information is useful but i thought it was important to share.
juanfe1a said:
I rooted my at&t note edge using king root. Then I installed SuperSU and used the option to install binaries in "normal" mode. Then the phone rebooted and in the booting screen i got an icon with an unlocked lock that said "Custom" then the phone booted normally no problem.
I dont know if this information is useful but i thought it was important to share.
Click to expand...
Click to collapse
What android do you have?
SAMSUNG SM-N910A With Tapatalk
gremy1987 said:
What android do you have?
SAMSUNG SM-N910A With Tapatalk
Click to expand...
Click to collapse
I have 5.1.1. After rooting the phone repeatly bacause after 30 seconds of being rooted the phone rebooted. I went into download mode (home + dwVol) the status showed that was official and that it was locked. I don't know if this information is relevant but sharing is important.
Hello,
I have a Samsung Galaxy S4(SGH-M919) with TMobile.
The android version is 4.4.4. Since i am still in the contract with TMobile,
the phone is locked with that carrier. (Btw, does this mean i have. a locked bootloader automatically??..but.i.found some on the net saying... Tmobile doesnt put locked bootloader??)
I tried to root this phone with towelroot, but it says it is not supported.
So i found an article saying this phone can be rooted by cf-auto-root with odin.
before i try, i would like ti ask something.
1. it says if the phone has locked bootloader, this rooting procedure can make the phone
brick. how do i check whether i have locked bootloader or not?
i havent installed any custom ROM .. i havent tried to root the phone other than towelroot.
Btw, i just went to download menu, though i didnt go further from there.
i saw "Write Protectiom : Enabled" ...does this mean i have locked bootloader phone?
Thanks
You don't have locked bootloader. You can use cf-auto-root just remember that you will trip your Knox flag. Other than that, there is no side effects as far as performance in hardware or software
The only root method I could get to work was CF Autoroot flashing with Odin. Just make sure you have the correct version for the T-Mobile SGH-M919. I don't believe SuperSu was included with the root. You need SuperSu installed after you get rooted. When apps want to access root files SuperSu will not allow that access w/o your permission. It's free and available on Playstore.
Jim
In regard to what OTISDOG said about the rooting, I have a MetroPCS branded M919N. I use firmware for both T-Mobile and Metro on the phone with absolutely no issues. Rooting the phone with CF-AutoRoot was a quick and painless process. Reason I rooted? To get rid of all the bloat on the phone. My battery lasts longer and is more responsive in general. I asked the reps at a local store if I would have a problem if I needed my phone to be serviced under warranty. He told me that none of his rooted customers had problems getting their phones fixed under warranty unless the phone was running a custom rom or recovery like CyanogenMod or TWRP. Your mileage may vary by your location and/or store visited.
otisdog said:
The only root method I could get to work was CF Autoroot flashing with Odin. Just make sure you have the correct version for the T-Mobile SGH-M919. I don't believe SuperSu was included with the root. You need SuperSu installed after you get rooted. When apps want to access root files SuperSu will not allow that access w/o your permission. It's free and available on Playstore.
Jim
Click to expand...
Click to collapse
Hello, after a search on these forums I could not find any topic about my specific problem so here goes.
I purchased a secondhand P605.
When I checked the Knox trigger it said 0x1, which made me wonder if anyone tried to root it before. It is not rooted at the moment, and I am unable to root it because Knox prevents it. I did update it to Lollipop.
So, I took to the Web and tried to disable Knox. This seems impossible, due to the fact that I don't even have permission to enter the Knox container!
Does anyone have any idea how to disable Knox when one doesn't have access to Knox at all?
Thanks in advance.
Airethilien said:
Hello, after a search on these forums I could not find any topic about my specific problem so here goes.
I purchased a secondhand P605.
When I checked the Knox trigger it said 0x1, which made me wonder if anyone tried to root it before. It is not rooted at the moment, and I am unable to root it because Knox prevents it. I did update it to Lollipop.
So, I took to the Web and tried to disable Knox. This seems impossible, due to the fact that I don't even have permission to enter the Knox container!
Does anyone have any idea how to disable Knox when one doesn't have access to Knox at all?
Thanks in advance.
Click to expand...
Click to collapse
If you updated to 5.1.1 then you need a modded kernel to root. Install TWRP, then flash new kernel and then flash supersu.
Your P605has definitely been modified either with a kernel or recovery, that's why you have Knox trigger 0x1.
Will try that , thank you.