Hey guys, new member although I've lurked for a while. I have been searching up and down the last couple of days to find a way to get past KNOX and reroot my device. Me being kinda rustic and not thinking about it, accepted an OTA firmware update a few days ago. Of course I lost root access. What I didn't know about at the time was how big of a problem KNOX had become recently.Well, this firmware update introduced KNOX onto my device. I've heard stories of people being able to use Kingo and Saferoot on 4.2.2 and 4.3 after KNOX. This has not been the case with me, and I'm wondering if anyone has had success with this. Odin doesn't work either. I noticed that write protection is set as yes when in ODIN mode, and I suspect this is KNOX preventing changes to the ROM. As a result I haven't even been able to reflash the stock ROM image I have, whereas I have heard that you can reflash stock ROM's, but can't go backwards as far as version number. Thanks for your help in advance.
HansBlenkers said:
Hey guys, new member although I've lurked for a while. I have been searching up and down the last couple of days to find a way to get past KNOX and reroot my device. Me being kinda rustic and not thinking about it, accepted an OTA firmware update a few days ago. Of course I lost root access. What I didn't know about at the time was how big of a problem KNOX had become recently.Well, this firmware update introduced KNOX onto my device. I've heard stories of people being able to use Kingo and Saferoot on 4.2.2 and 4.3 after KNOX. This has not been the case with me, and I'm wondering if anyone has had success with this. Odin doesn't work either. I noticed that write protection is set as yes when in ODIN mode, and I suspect this is KNOX preventing changes to the ROM. As a result I haven't even been able to reflash the stock ROM image I have, whereas I have heard that you can reflash stock ROM's, but can't go backwards as far as version number. Thanks for your help in advance.
Click to expand...
Click to collapse
Flash anything with ODIN will trip the KNOX. Kingo is basing their root method on Saferoot, just with a GUI to make things simpler. And Saferoot should work with ROM that is before KK (4.4). If your OTA update is 4.4 than Saferoot won't work, since Saferoot is using a vulnerability prior 4.4 version. Does Kingo or Saferoot give any error message?
And just to double check, for both Saferoot or Kingo to work, you need to enable USB ADB and debugging mode.
TNCS said:
Flash anything with ODIN will trip the KNOX. Kingo is basing their root method on Saferoot, just with a GUI to make things simpler. And Saferoot should work with ROM that is before KK (4.4). If your OTA update is 4.4 than Saferoot won't work, since Saferoot is using a vulnerability prior 4.4 version. Does Kingo or Saferoot give any error message?
And just to double check, for both Saferoot or Kingo to work, you need to enable USB ADB and debugging mode.
Click to expand...
Click to collapse
Hey thanks for the reply. I do have USB ADB and debugging turned on. I've also tried reinstalling kies and the USB drivers them selves. I don't really care if an Odin flash trips Knox, as I don't think I have a warranty to worry about. The OTA update brought my firmware upto date , so I'm still on 4.2.2. This means that technically Saferoot or Kingo should work as advertised. This brings me back to the Write Protection set to Yes, and it's the only thing I could see preventing me from rooting my phone.
EDIT: Well I just found out that the Mini USB I use to charge my mouse started shorting other USB devices. Not like short then come back on, it was so bad every port on the computer shut down and I had to restart to get them working again. It was also the cable I was using to plug my phone in. Will update again when I try another cable.
EDIT 2: Just tried with the cable I usually use for charging my phone. No change on Kingo, still get a Root Failed, Need Root error.
HansBlenkers said:
Hey thanks for the reply. I do have USB ADB and debugging turned on. I've also tried reinstalling kies and the USB drivers them selves. I don't really care if an Odin flash trips Knox, as I don't think I have a warranty to worry about. The OTA update brought my firmware upto date , so I'm still on 4.2.2. This means that technically Saferoot or Kingo should work as advertised. This brings me back to the Write Protection set to Yes, and it's the only thing I could see preventing me from rooting my phone.
EDIT: Well I just found out that the Mini USB I use to charge my mouse started shorting other USB devices. Not like short then come back on, it was so bad every port on the computer shut down and I had to restart to get them working again. It was also the cable I was using to plug my phone in. Will update again when I try another cable.
EDIT 2: Just tried with the cable I usually use for charging my phone. No change on Kingo, still get a Root Failed, Need Root error.
Click to expand...
Click to collapse
At this stage I can only suggest to try on a different PC (use don't need Kies, just the Samsung driver will do) with a cable that your are 100% sure it working. If it still not working, my only guess is your network provider enable a looked boot loader in the OTA update you just did (hence the Write Protection flag). If that the case, nothing can be done at this point.
Same Boat
Im in the same boat did realize that KNOX would change so much. I need to reroot so hopefully someone can figure it out without tripping knox.
It fails because of the Security notice....Unauthorized access to a secured area has been blocked. Tap to learn more. If you notice when you check USB debugging, look below at Verify apps via USB. It is checked and grayed out. It isn't checked when USB debugging is off. I don't know how this was circumvented on the S4. But I'm peeved I let the update happen. They conveniently left out any info about security, and I'm tempted to return the phone and get one that hasn't been updated. Figure they weren't forthcoming about what the update contained so I can raise enough stink, get an old phone, download the update, pass it off to someone who can hopefully pull everything but the bootloader and create a tar to flash via odin. If that's possible and someone is willing to do it. If I had another spare line, I'd get another phone to donate for the cause.
I think if we're on Knox we need Odin to Root because anything that gets transferred via USB will be blocked. I even tried rootkeeper, and it was blocked.
The tough part is, unless it's a premium phone, it's not getting the level of dev support we're used to (well I'm used to...haha). Rooting through odin, custom recovery....used to taking it for granted. And with Sprint EOL'ing the phone, it's not really going to gain any momentum, though I did only pay 99 cents for it on a spare line. Kinda ticks me off Samsung has gone this direction when they used to be so dev friendly. Almost enough to make the S4 my last Samsung.
TNCS said:
At this stage I can only suggest to try on a different PC (use don't need Kies, just the Samsung driver will do) with a cable that your are 100% sure it working. If it still not working, my only guess is your network provider enable a looked boot loader in the OTA update you just did (hence the Write Protection flag). If that the case, nothing can be done at this point.
Click to expand...
Click to collapse
the concern is not tripping knox from the bootloader perspective. The problem is the knox security app that can't be removed without root. So for everyone that has OTA updated to NA7, going the odin route to root is the only option as far as I know. I know I don't care about tripping the counter. I just want control back of my phone. And the only way to do that at the moment is to return it for a pre knox version which I'm apt to do at the moment since there is a lack of development, and the ones that are developing don't even have the phone. Kudos to them, but there's not much help once you've updated to NA7. And unfortunately, the update doesn't tell you it's locking down your phone. Then you're stuck in a quandary, because the update also provides updates for Spark, so unless someone does a dump of the download and someone can pick it apart and provide a zip sans Knox, we'll have to deal with a stock phone.
dbpaddler said:
the concern is not tripping knox from the bootloader perspective. The problem is the knox security app that can't be removed without root. So for everyone that has OTA updated to NA7, going the odin route to root is the only option as far as I know. I know I don't care about tripping the counter. I just want control back of my phone. And the only way to do that at the moment is to return it for a pre knox version which I'm apt to do at the moment since there is a lack of development, and the ones that are developing don't even have the phone. Kudos to them, but there's not much help once you've updated to NA7. And unfortunately, the update doesn't tell you it's locking down your phone. Then you're stuck in a quandary, because the update also provides updates for Spark, so unless someone does a dump of the download and someone can pick it apart and provide a zip sans Knox, we'll have to deal with a stock phone.
Click to expand...
Click to collapse
I was (after a good bit of tinkering, and deleting my modem on accident) able to install CWM and flash a CW11 version s0be is currently developing, and it's working pretty well as far as I can tell. Unfortunately, due to the lack of support on this forsaken Sprint device, I haven't been able to find a modem I can flash onto the damned thing to get it working properly again. I don't advise the route I took, firstly because of the effort it took, but I also damned near bricked it about 5 different times, and needed to use a Linux VM. Also, because of the lack of developers on this thing, if you delete your modem and A: don't have a friend (brother in my case, has same phone) you can pull a modem.bin off of and B: don't know how to build that .bin into a working .zip or a flashable tar.md5 you might get stuck with an unusable device at the end of the day. Really, the only thing Knox has done for us is complicate things a hell of a lot more than they need to be. Although, tbh, that might (most likely) have been my stupidity that deleted the modem. In any case, check it (s0be's CM11 development) out, it's coming along nicely. Just be careful with it.
........
thank you very mach
Related
Hi All
Let me start with few good things here You guys are amazing helping and providing tweaks for us:good:
I am Nexus user. I have Installed Custom Recovery, Flashed ROMs and rooted my Nexus 4 and Nexus 5. This is my First Samsung Tablet. I have waited enough for Nexus 10 (2). I finally bought SM-P600.
I was trying to find an Guide with links for Unlocking bootloader and Updating firmware and then flash Custom recovery for this but coudnt figure it out
I have been reading lots of things about Knox and counters related to it.
Can anyone Please help me find answers straight.
1) Any Rooting and Custom Recovery tools or ADB commands without Hitting the KNOX counter {Just In case IF I wanted to return it} If not then which one you recommend ?
By the Way I found few posts related to Rooting Which has confused me more. I used to use Chainfire SUROOT:
Rooting using CF-AUTO Root
Universal Root de la Vega
2) If I Root and want to use Stock ROM of SM-P600 will all apps work normally or any known issues with it ?
3) Is Odin any tool which everyone is taking about ? I am not sure about it Can you provide any links to its dev for more info. Found it about in a Post to return to STOCK ?
4) Are these ROMS and apps Odexed or Deodexed ROM?
5) Any Dependencies for Firmware and with any of the above questions. I mean In Universal Root I saw they were talking about certain version of firmware. Also Should I update the latest firmware and do a Nandriod backup ?
6) Also read that once KNOX counter goes up, I wont get any OTA ? My Plan is I will use it till next Nexus and will give it to parents with stock ROM. If I am using I can always use an Custom Rom and get updates. But for parents I want to return it to stock so that they can easily update when OTA is available.
I would like to make one more suggestion to MOD's Please Pin the Guides like the Rooting and stuff like Return to Stock which are quite common and useful so that its easy for newbies( aka for Samsung) like me.
Thanks
Zaib.
1. This is not really a single question with a single answer I think vaguely what you are asking is if you can root without tripping knox?
Nope. Not at this time.
2. If you use CF-Auto-Root you'll likely find that the vast majority of applications keep working without issue. Of those that don't, a handful you can manage back to a working state with various tweaks, but there are a few that are probably gone for good. You can basically kiss all the Samsung hub apps goodbye, these will start claiming they are not supported in your country even if they were working perfectly prior to rooting, some may continue working for a short time after but eventually something leaks and your access is cut. Screen mirroring will no longer work though this can be fixed with a small zip file flash. OTA updates are also gone.
Forget all the talk about 'triangle away' fixing any of this, it hasn't for me.
3. Odin is a tool that is able to flash firmware files or parts thereof to your device. Heimdall is an alternative suite of applications, while there is a GUI for it, it seems fairly hit and miss on Linux these days, I've never had much luck with it, on the other hand the command line tools work perfectly fine.
Once you trip Knox, there's no turning back! You won't lose your warranty in any meaningful way, but you may end up having to argue about it and drag in government regulators to get your tablet repaired free of charge depending on the dealer response.
4. I don't think this is particularly relevant to the SM-P600. My subjective opinion would be to stick with the bog standard Samsung ROM. If you want cool themes there are a multitude of launchers, Xposed takes care most other things you might ever care to tweak.
5. You have one choice. CF-Auto-Root. Backups are healthy.
6. True, but you'll still be able to flash via Odin so it doesn't really mean much of anything. Once you trip Knox, you can also kiss OTA updates goodbye as well.
What to do
My tab crash while flashing twrp
A.ratyan said:
What to do
My tab crash while flashing twrp
Click to expand...
Click to collapse
How are you flashing TWRP, through recovery or Odin?
I have a 16gb S3 which has been flashed to 4.3 (several times). My sons S3 is a 32GB but he broke the screen and bought a different phone. I thought I would like to swap out my motherboard and put his in my phone (both for the memory, and because I've set my Warranty Bit and I'm not entirely happy with 4.3's performance and his still has 4.1.2 so I can get a free reset on that). Both phones are T999's on the same account. His was bought off ebay but he was able to activate it so my assumption is that the IMEI is clean. Before I do this my questions are:
Will my IMEI change (is the IMEI locked to the motherboard)? If it changes, that's fine, as long as I can just pop my SIM in and be up and running.
Can I just do that swap, put my SIM in and go, or is there anything else I need to do with the phone after the swap? I work in a micro repair shop so I'm fine with doing all the hardware related work, just want to verify if I need to do anything extra after the swap.
The imei, and pretty much everything will be on the motherboard. Just swap it out and insert your SIM. Should be all you need to do.
Sent from my SGH-T999 using Tapatalk
OK, got the swap done, and a hard factory reset on 4.1.2 without issue.
So now I was planning on leaving it at that, but after reading through the [ROOT] TowelRoot - 4.3 & 4.4.2 thread today I'm thinking I'd like to try that. My goal is:
1. Update to latest 4.3 via OTA
2. Use the Towelroot tool to root and de-knox it
3. NOT set the warranty bit in the process (hopefully)
4. Create a debrick.img for T999 with clean NC2 (if it's still needed)
1,2, and 4 I'm good. Just curios if I OTA update 4.1.2 and follow all the steps for using towelroot, is there anything more I should be cautious or aware of about the warranty bit. My hope is that I don't do something stupid that will set it on this motherboard. I'd love to have 4.3 rooted but not set the bit.
I'm not concerned so much about the "modified" system or other counter(s)... triangle away was still working to clear those on my root66 NC2 load.
I think flashing the firmware via Odin is a better option. Too many people often seem to have trouble with OTA's. Thst and I personally just feel clean flashing the build you want is better than patching them up from a previous version.
In the end its what you are more comfortable with though. Just offering an alternative.
I'm comfortable doing an Odin flash but I thought that would set the warranty bit. I would've used root66, so am I off by thinking that? At any rate, I OTA'ed last night, ran towelroot and that worked, but I had some issues with the Supersu portion. It updated binaries, and then when it ask about disabling knox, I got a message saying Supersu install failed (or something similar). When I root checked it, it said it was rooted, and supersu was working, but all the knox related files were still on my phone. So I rebooted and ran supersu a second time and it just came up as it would if it were fully installed and working.
I never did figure out why, I even completely cleaned up/removed supersu from it's settings menu, re-installed it and tried again. At that point, it updated binaries without a hitch but didn't give me any prompt to do anything with knox. So does supersu somehow just disable knox, but leave all the files intact? I manually went in and deleted all the knox files myself at any rate and it didn't appear to screw anything up so far.
I also wondered if supersu issues had anything to do with the fact that when I installed it, I had not yet set Selinux to permissive.
Anyway, all that probably belongs in the threads for towelroot, so I got a little off topic .
Root66 apparently trips the warranty bit for some, but not all people. It did not trip mine. Since you've already done the OTA it doesn't really matter, but what I would've suggested next would've been to flash stock firmware via Odin, then Towelroot.
As for SuperSU, everyone has to reboot (or kill the process) before it'll properly disable Knox. And yes, that's all it does is disable it. Didn't have anything to do with seLinux.
OK, cool. So I guess it worked exactly as intended. Thanks for all the good info.
Interesting about the warranty bit.
Hello, this is my first android device, so I'm not too experienced with the whole rooting thing. My device is currently rooted with the original firmware that came on it. (Galaxy Tab S 10.5) not quite sure which version is on here or even where to find out. I tried to do an over the air update and it wouldn't let me because the device is rooted, but apparently there is a new firmware version out, so I definitely want to get on that.
How do I go about getting the latest firmware installed and getting my device rooted again?
Thanks!
How you rooted it the first time, just repeat the steps again.
Well to get an OTA as far as I know you will need to un-root and try the update, BUT if you rooted with Chainfire method probably is gona fail, because that method trips knox, and the update is going to fail.
If for whatever reason you can update, you might loose root and maybe the exploit that worked with your current build this time is not going to work.
To find out what build you have, go to settings>>>general>>about device and there it's
That's why once you root you have to block or deny the updates until the people here with more knowledge report that it's safe.
CyberManiaK said:
Well to get an OTA as far as I know you will need to un-root and try the update, BUT if you rooted with Chainfire method probably is gona fail, because that method trips knox, and the update is going to fail.
If for whatever reason you can update, you might loose root and maybe the exploit that worked with your current build this time is not going to work.
To find out what build you have, go to settings>>>general>>about device and there it's
That's why once you root you have to block or deny the updates until the people here with more knowledge report that it's safe.
Click to expand...
Click to collapse
The build number says:
KOT49H.T800XXU1ANF8
I haven't tried it for marks but auto update via Kies should work. Even if rooted. Does not affect root. And does not factory reset. i. e. you get same effect as OTA.
381
pibach said:
I haven't tried it for marks but auto update via Kies should work. Even if rooted. Does not affect root. And does not factory reset. i. e. you get same effect as OTA.
Click to expand...
Click to collapse
can anyone confirm this?
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.
Im on 5.1.1 G925TUVU3DOJ7. Is it possible to root 5.1.1 without tripping knox right now? Or can i downgrade to 5.0.2 by flashing stock 5.0.2 with odin then root with ping pong without tripping knox?
Also what are the best roms, kernals & other cool tweaks you recommend? Just got this phone so i would really appreciate the help, thanks have a good one.
I don't think there's a way to root without tripping KNOX right now. There was an engineering bootloader that allowed flashing without tripping KNOX, but I don't know if it still works (it might). However, this bootloader breaks the fingerprint scanner. There is no way to have an un-tripped KNOX and working fingerprint scanner at the moment, I know that for sure.
king.23 said:
Im on 5.1.1 G925TUVU3DOJ7. Is it possible to root 5.1.1 without tripping knox right now? Or can i downgrade to 5.0.2 by flashing stock 5.0.2 with odin then root with ping pong without tripping knox?
Also what are the best roms, kernals & other cool tweaks you recommend? Just got this phone so i would really appreciate the help, thanks have a good one.
Click to expand...
Click to collapse
PingPong used to work, it doesn't anymore. I agree with what the other poster said about the engineering bootloader however this file was requested to be removed by samsung (sboot.bin) so good luck finding it. I think you might be onto something downgrading to a previous release, I'm not too sure but the OH6 I think is the one that I used PingPong on to gain root but I don't know if the new bootloader will let u. It should though, if it replaces the sboot.bin it should let u downgrade. I'm just not sure, this new update has caused a lot of stuff to not want to flash for me, I'm waiting on my new internet to arrive before I start messing with it anymore because my phone is my only link to the outside world. if you find out please let us know? I'm very interested in the answer.
I've heard Hacker Kernel is a really good one, people seem to love it.
MindGlitch said:
PingPong used to work, it doesn't anymore. I agree with what the other poster said about the engineering bootloader however this file was requested to be removed by samsung (sboot.bin) so good luck finding it. I think you might be onto something downgrading to a previous release, I'm not too sure but the OH6 I think is the one that I used PingPong on to gain root but I don't know if the new bootloader will let u. It should though, if it replaces the sboot.bin it should let u downgrade. I'm just not sure, this new update has caused a lot of stuff to not want to flash for me, I'm waiting on my new internet to arrive before I start messing with it anymore because my phone is my only link to the outside world. if you find out please let us know? I'm very interested in the answer.
I've heard Hacker Kernel is a really good one, people seem to love it.
Click to expand...
Click to collapse
If I remember correctly, PingPong only worked on 5.0.X, and once you update to 5.1.X, you are no longer able to downgrade back to 5.0.X. I think if OP is on 5.1.1 his options for root are VERY limited if he wants an in-tact KNOX, especially since you are indeed correct, and the engineering bootloader seems to have been removed.
S6 Edge frozen on G925TUVU3DOJ7
guys i need help , after flashing the rom G925TUVU3DOJ7 on my S6 Edge 925T its stuck on galaxy logo and not booting , i've trying to use unikernal but its not work i get like flashing is locked !!!
Rooting is a risky business since last update, make sure you have a good download or download again from Samsung website and try again.
Pp.
Really why is everyone so concerned about knox? All it does is make it so you can't use Samsung Pay. So use Android Pay. Set it up before you root then back it up after you root. Restore it whenever you flash a new rom and it will work. I rooted the day I got my S6 Edge which was before the Plus came out and I have never had any problems. Everyone worried about knox this and knox that has a messed up phone.
HI,,I updated firmware 5.1.1 to a rooted G925T using Smart Switch (no errors etc) now the phone is stuck on android Samsung logo so I tried to reflash the firmware many times using Odin3 the only frimware it took with no errors was (G925TUVS3DOJC) which is the last one but still the same thing stuck at Samsung logo so i searched it online and it says something wrong with EFS and has Bad Root Key it know as DRK (DEV Root Key) and don't know how to fix that. anyone can hepl plz.