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.
Related
I am creating this thread because I have not found another ZACT rooting/flashing thread yet and I am hopping that a dev will pop in and start working on this, or help walk me through what I can do to get the ball rolling. Check out my first thread, The future of phones is coming
I received 2 phones a few weeks ago now. I wasn't thinking and just jumped the gun and updated to 4.3 on one of them (the other is my fiances and have instructed her NOT to do the update). I am unable to cf-auto-root with the sprint s3 method, so no root. I read if I get the recovery.img from the phone I can post in on Chainfire's cf-auto-root page and he can make a cf-auto-root for the zact s3. I can not get a recovery.img to send in because it is my understanding that to adb pull the recovery I need root. cant get root because I dont have a recovery.img?
I spoke with zact team members a few times. I told them I was having issues with 4.3 and wanted to go back to 4.2.2. A few people were helpful at first. Unfortunately, they are so small, I seem to keep running into the same people, and then they stop trying to help. What I have learned is, they "have confirmed with there Team, that if you process the software downgrade, the Zact software will not work on your phone. This is based upon how our software interfaces with the firmware." SO, that being said we would need to find out what software they have installed and have it integrated into any roms made. Does that sound right?
They also WILL NOT share the MSL. Which is another reason I want root. I still plan on cloning the phone as a backup if I have issues with flashing. but without the msl, i cant change the qualcomm settings to connect to dfs/cdma to back clone it.
I am not a developer, I could use some direction. I feel ZACT will start growing once people realize how much you can save compared to a sprint plan. I have noticed that I get better service then a lot of the people I work with. I am on prl version 24017, which I have not seen before either.
devildogwillbur said:
I am creating this thread because I have not found another ZACT rooting/flashing thread yet and I am hopping that a dev will pop in and start working on this, or help walk me through what I can do to get the ball rolling. Check out my first thread, The future of phones is coming
I received 2 phones a few weeks ago now. I wasn't thinking and just jumped the gun and updated to 4.3 on one of them (the other is my fiances and have instructed her NOT to do the update). I am unable to cf-auto-root with the sprint s3 method, so no root. I read if I get the recovery.img from the phone I can post in on Chainfire's cf-auto-root page and he can make a cf-auto-root for the zact s3. I can not get a recovery.img to send in because it is my understanding that to adb pull the recovery I need root. cant get root because I dont have a recovery.img?
I spoke with zact team members a few times. I told them I was having issues with 4.3 and wanted to go back to 4.2.2. A few people were helpful at first. Unfortunately, they are so small, I seem to keep running into the same people, and then they stop trying to help. What I have learned is, they "have confirmed with there Team, that if you process the software downgrade, the Zact software will not work on your phone. This is based upon how our software interfaces with the firmware." SO, that being said we would need to find out what software they have installed and have it integrated into any roms made. Does that sound right?
They also WILL NOT share the MSL. Which is another reason I want root. I still plan on cloning the phone as a backup if I have issues with flashing. but without the msl, i cant change the qualcomm settings to connect to dfs/cdma to back clone it.
I am not a developer, I could use some direction. I feel ZACT will start growing once people realize how much you can save compared to a sprint plan. I have noticed that I get better service then a lot of the people I work with. I am on prl version 24017, which I have not seen before either.
Click to expand...
Click to collapse
WARNING!! If you process that downgrade, you will trip KNOX security, then your phone will be bricked. Also, ESN cloning is illegal to talk about on XDA.
sent from my GS3
I will trip knox security? What exactly does Knox do, and what do you mean by that? I though Knox just makes it read 0x1 on the odin screen if you flash now? If thats what you mean, I already did that by flashing cf-auto-root. Its my understanding that the boot loader is the issue when downgrading. but on this site, they say that only at&t users should not try it, and technically this is a sprint phone I believe. Just with added software.
If I am wrong please let me know.
Also, I think you mean that it is not acceptable, not illegal. Illegal would imply I could get arrested for commenting about phone cloning on this site. And although cloning your personal phone for your own uses is not illegal, I will not mention it again on these forums. Thanks for the warnings.
sent from my GS3
Also, I guess I am not necessarily trying to downgrade, just trying to find out what needs to be done so that I can flash or ANYTHING to get away for 4.3 issues. Since the upgrade, my fiance sent me an mms and it has popped up in my messages 5 times, so it looks like she keeps sending it, but I am unable to open it because it wont download.
The more important issue is root. I want to be able to use my root apps to backup, re install my old backups from my last s3, and attempt to get my msl to try and fix the mms issue.
sent from my GS3
Today has been a productive day so far... using Skunk Ape1's root method "[Tutorial] Rooting the Sprint GalaxyS3 the Easy Way" I was able to get twrp recovery installed. (I wasn't able to do this before because prior the only method i knew was to go to goo.manager and that didn't recognize my device) SO, with twrp installed, i flashed the zip file from Skunk Ape1's root method. Following the instructions to the T everything seemed to work fine. After reboot, I had a knox message popped up, saying "SECURITY NOTICE: Unauthorized access to a secured area has..." I relive that root has been installed but knox is keeping locked up still. I am going to look for this mysterious "Knox remover script" that you will see in the first post on that page, then I will attempt root again.
I have officially given up on root currently. I have tried every root method I can find, my flash counter is somewhere around 13. I was able to use the knox removal script from here If anyone has suggestions for root, I am open to ideas. Thanks.
Finally did it
So, today i was just realizing the lack of space i had on my phone from downloading stuff and photos so i wanted to clean it up. I moved all the important stuff off, and though it would be a good time to factory reset and just have a clean new phone to start over again. ( I missed flashing and this was the closest thing I had) So, during the process of factory resting i wanted to clean everything so i click data, cach, internal external.. system.. yeah well bad idea. my phone rebooted and go stuck on the boot. So i restarted in recovery and reset again and this time is warned me that there was no OS installed... F*ck... Zact customer service wont give me the "custom software" that they installed so im screwed.
After hours of thinking and trying to do stupid odd ball things that i knew wouldnt work. I downloaded a sprint stock 4.3 tar file and odined to my phone. started up fine. works great. so... what zact said about flashing roms bricking this phone was BS.. the only custom thing i have seen was in the zact mobile app that came installed had some extra features used to send usage info and reboot stuff for zact troubleshooting. so with stock sprint rom, and zact mobile app im back to my phone working. AND with that, im going to move on to the rooting, and flashing of this piece of crap. Ill be back with more details later.
I have installed CyanogenMod with full root!!!
well first off, i had the CMinstaller set up but it did not recognize my device so after a while i decided to attempt to cf_auto_root, which seemed to work but failed root checker. I wanted to try another method. I had CMinstaller still up* I was attempting THIS method to root. I was using philz_touch_6.15.4-d2spr.tar.md5 that I flashed using Odin 3.07 (that I have had for a long time on my pc. so google that one)https://www.google.com/search?q=odin+3.07&oq=odin+3.07&aqs=chrome..69i57.3464j0j1&sourceid=chrome&ie=UTF-8 After i installed Philz touch, i noticed CMinstaller noticed my phone and started downloading system files. I continued what i was doing with the root method and installed DE-SAMSUNGNIZER_KNOX_REMOVAL_SCRIPT_V1.0 and UPDATE-SuperSU-v1.93 just as CMinstaller finished its download, so i said what the hey, and clicked install. next thing i knew i was running cyanogenmod with full root!!! please someone else verify this and let me know if you get it going too.
Deleted
Stock 4.3 with root
so yeah, just for to check i flashed back to stock 4.3 (not sure who uploaded it but it works) It does have knox so be warned. I then followed the root method in my previous post and it worked fine. i have stock with root. If someone can try it without using that tar file, let me know. Cant really go back once you do it so i cant try the root method with the zact "custom software" myself. Let me know what you find out. Hope this helps someone.
Thanks
Thanks for posting your struggles and successes. With Zact shutting down I was curious about what I could do with my kids' S3s if I don't like the Sprint plan that they are rolling us into. I may be trying this in a couple weeks...
Zact to Ting
Barnsie said:
Thanks for posting your struggles and successes. With Zact shutting down I was curious about what I could do with my kids' S3s if I don't like the Sprint plan that they are rolling us into. I may be trying this in a couple weeks...
Click to expand...
Click to collapse
What I would do and have done for my fiance and myself, get on Zact.com live chat ask them to Deactivate your phones. and give them the DEC on the back of the phones. It takes about one min for it to complete per phone. Then go on over to Ting.com and start up a new account with them using your old zact phone. Ting also lists the MSL that i struggled so much trying to get. I would recommend flashing a stock rooted rom debloated, to get all that ZACT crap off your phones. and start out fresh.
I had rooted my SGS3 while on 4.0.4 using the stock Samsung rom and Odin without issue no custom ROMS were installed just root access. Early August of 2013 the OTA for 4.1.2 was rolled out and I had accepted the update which was installed without issue, which apparently should not have been the case (everything I can find says OTAs will fail if you have root access, but this was not the case). I now want to either return to a full stock to get the 4.3.3 update at which point I may remain unrooted, or gain root again and update to 4.3.3 with root. I'm cautious about how to proceed here since I've read about a lot of people bricking their phones while attempting to root after 4.3.3. My primary concern is that my flash counter is tripped at 1, but I don't have root access and am not sure how to proceed with out potentially damaging my phone. So I'm essentially getting the worst of both worlds (unable to receive stock updates from carrier, no root access to update otherwise.) and don't want to be stuck on 4.1.2 for the life of this phone. I still have SuperSU installed, but when I open it it says "There is no SuperSU Binary installed and Super SU cannot install it. This is a problem!"
I have searched these forums and a few related to it, and from what I can gather I should just reroot the phone following instructions for 4.1.2, but if I want to make the jump to 4.3.3 I wasn't clear if this would be needed or not, but none of the threads I could find directly addressed the issue for the ATT SGS3 i747. The closest I found was a thread posted last month where the OP was directed to the CF Root procedures, but there was no followup after that. I'm just a little leery about what might happen if I reroot with another method and end up with duplicate files/.apks etc related to the root process on my phone.
I also wanted to be sure that rerooting using a different method wouldn't somehow damage my phone.
Can someone with some experience please advise of the safest best practice for me to either recover root and update, or remove root and update so I can start fresh later? From what I can gather this should be an easy fix, but I would prefer to rely on the expertise of someone more knowledgable as opposed to winging it on a gut feeling I will be ok.
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
Hi,
This is a great site.
I am doing this cause I deleted some photos by accident and want to use one single program that needs the phone to be rooted. Because there is no mass storage connectivity you know how it goes.
I used Odin3 to install "CF-Auto-Root-t03g-t03gxx-gtn7100.tar.md5" to my Samsung Galaxy Note 2 with Android 4.3.
Odin says "PASS!". When I try to start the SuperSU (version 2.01, was installed by Odin and CANT BE UPDATED in the play store, not even removed only opened form play store. This was the most common fix that people are giving to this situation, but it does not work for me because there is no update possibility) Because KNOX says unauthorized attempt to access not accessible areas. SuperSU does not prompt the possibility to terminate KNOX like some people are advising to do, even tough the 2.01 version of SuperSU should be able to do this. Even the RootChecker says that my phone is not rooted.
So my assumption is that the Root has not worked on my phone even tough Odin says so. So I want to try some other approach to root this phone. I just would like to know should I do some check for what Odin HAS changed in my phone and to try to change them back so I can for example try Kingos root safely.
So the questions are:
Does some one have a possible fix to my problem without me having to re root?
How can and what should I check before trying another root?
If I have to go back with stuff that Odin did, without it doing the root properly how can I do that?
And one a bit different question:
If I factory reset my phone it will install the 4.1 I thin on it, has no KNOX, will it write that on the part that is empty and might include that data of my deleted pictures or does it write it on the area that has the previous data of the Android system?
Thanks for advance if there is any advises.
Partial answer:
I followed basicly this instruction,
http://forum.xda-developers.com/showthread.php?t=2538991
just needed to find the correct TWRP for my phone and used the older 1.65 SuperSU, there is something wrong with the 2.01 and it compatibility with my phone.
This video also helped cause the information was similar to the one in the link.
https://www.youtube.com/watch?v=ZQAkLgXjnCo
Installed the DiskDigger and got most of the photos, so now I need to find out how to convert it from root version to version so I can upgrade my phone.
Everything is really easy with Odin. If the packet that I installed with it first that does't istall the custom recovery system would have had some other KNOX combatible version of SuperSU I think it would have worked. No I just needed to use the KNOX remover to remove it from my phone.
Thanks for the form all the answers where her and it just took me some time.
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.