Related
help! please. I am look to root my samsung galaxy S4 Running android 4.3 with the build MK6.
PLEASE HELP?
Thank you
Use this method : http://forum.xda-developers.com/showthread.php?t=2293800
DaveRazr said:
Use this method : http://forum.xda-developers.com/showthread.php?t=2293800
Click to expand...
Click to collapse
Anything that will actually allow the install of a custom recovery?
arrush said:
Anything that will actually allow the install of a custom recovery?
Click to expand...
Click to collapse
There's no "true" custom recovery for phones running MF3 or above. MF3 phones can run Safestrap. MDB/MDL phones still have the ability to boot into a true custom recovery using loki.
Questions and Help issues go in Q&A and Help section
Thread moved
Thanks
FNSM
Mk6 can run cwm and twrp. Rogers unit isnt the same as att bud, happy flashing
Sent from my SGH-I337M
---------- Post added at 12:13 PM ---------- Previous post was at 12:09 PM ----------
jeboo said:
There's no "true" custom recovery for phones running MF3 or above. MF3 phones can run Safestrap. MDB/MDL phones still have the ability to boot into a true custom recovery using loki.
Click to expand...
Click to collapse
This is not the case at all. Mk6 is rogers / canaduan variant, and the bootloader is not locked. Root with cf auto root, and flash cwm or twrp via normal methods. You will trip knox counter, but you can run any recovery u like. MF3 is locked bootloader , mk6 is not.
Sent from my SGH-I337M
azuziel said:
Mk6 can run cwm and twrp. Rogers unit isnt the same as att bud, happy flashing
Sent from my SGH-I337M
---------- Post added at 12:13 PM ---------- Previous post was at 12:09 PM ----------
This is not the case at all. Mk6 is rogers / canaduan variant, and the bootloader is not locked. Root with cf auto root, and flash cwm or twrp via normal methods. You will trip knox counter, but you can run any recovery u like. MF3 is locked bootloader , mk6 is not.
Sent from my SGH-I337M
Click to expand...
Click to collapse
Oops, didn't even realize it was i337m...:silly:
I used kingo app. One touch root. Knox safe. I verified the vroot iemi crap is all removed in new version. After your reboot, update supersu binary via normal method, cancel any knox popups, and choose not to allow supersu to disable knox. Use titanium backup and guides found here to freeze all knox stuff. Then busybox, xposed as normal. Dont install custom recovery if you want to keep knox 0x0. If you dont care, then install cwm/twrp as per normal
Sent from my SGH-I337M
I deleted Knox completely from my phone as well as all the AT&T Bloatware. My phone is better without it.
azuziel said:
I used kingo app. One touch root. Knox safe. I verified the vroot iemi crap is all removed in new version. After your reboot, update supersu binary via normal method, cancel any knox popups, and choose not to allow supersu to disable knox. Use titanium backup and guides found here to freeze all knox stuff. Then busybox, xposed as normal. Dont install custom recovery if you want to keep knox 0x0. If you dont care, then install cwm/twrp as per normal
Sent from my SGH-I337M
Click to expand...
Click to collapse
Thanks a lot for that Kingo App, worked perfectly! I did get that Knox pop-up on 4.3 and I clicked view apps just to check it out.
2 Questions:
Anyways, how do you update supersu binary? There's no option or menu to do so and I didn't get a pop-up.
How do you choose not to allow supersu to disable Knox?
Thanks for the tip about not installing a custom recovery
azuziel said:
I used kingo app. One touch root. Knox safe. I verified the vroot iemi crap is all removed in new version. After your reboot, update supersu binary via normal method, cancel any knox popups, and choose not to allow supersu to disable knox. Use titanium backup and guides found here to freeze all knox stuff. Then busybox, xposed as normal. Dont install custom recovery if you want to keep knox 0x0. If you dont care, then install cwm/twrp as per normal
Sent from my SGH-I337M
Click to expand...
Click to collapse
Do you know if this was resolved then? http://forum.xda-developers.com/showthread.php?t=2460745&page=8 there was more going on behind the scenes than I would like to have.....
http://forum.xda-developers.com/showthread.php?t=2460745&page=8
Ramsey said:
Thanks a lot for that Kingo App, worked perfectly! I did get that Knox pop-up on 4.3 and I clicked view apps just to check it out.
2 Questions:
Anyways, how do you update supersu binary? There's no option or menu to do so and I didn't get a pop-up.
How do you choose not to allow supersu to disable Knox?
Thanks for the tip about not installing a custom recovery
Click to expand...
Click to collapse
regarding knox. It is safe to allow supersu to disable knox, i avoided it thinking it may trip bc wasn't sure how it went about freezing it. I tested, had supersu disable knox, rebooted, good to go.
Did an identical handset today, and failed to root. Did some poking and found out that kies3 appears to interfere with kingo, so uninstall temporarily when running kingo if you have issues.
Once supersu disabkes knox, you can then update the binaries via normal method. Also if kingo gets to the part where it asks about using odin method, say no, or it'll trip knox.unplug, reattach and try again. Had to do it thrice for an i377m i did today.
Heres what i did:
1 - connect usb to phone, and enable developer mode, then be sure to allow the dev prompt to always accept usb from this machine, phone will prompt to allow
2 - click root. Shouldn't get to odin question, id it does, dont allow odin method, restart the process.
3 - on successful root, you will see supersu install, grant it root, and allow it to disable knox.
4 update supersu binariez via normal method (don't need to use cwm/twrp on i377m only), it will prompt, until knox disabled, u wont be able to update binaries
5 - install busybox installer
I havent installed supersu as system app yet, i imagine its also safe to do so.
6 - check knox in download mode and ensure 0x0 for *both* knox codes
7- installed xposed and some modulez, greenify in particular, and enabled, recheck knox, still 0x0
Both phones i did with this method, once kies was removed, rooted BEFORE i had to install any camera exploits, or any other crap from play. If you habe trouble, reload samsung drivers, try another cable (i had a failure using a blackberry usb cable, switched to packaged smasung usb, worked fine), anothet usb, and even another computer. Old pc's with usb 1.1 wont work (well), usb 2/3 does work just fine.
Avoid clockworkmod, twrp, safesteap etc (or any other custom recovery) if you want to keep your warranty. If you dont care, then twrp/cwm work just fine, they will blow the knox efuse tho and set you 0x1. I work in IT and happen to know knox will work with exchange 2015 upon release. It will also screw up new versions of active sync, as your system isn't able meet the security requirements (having knox intact and not blown) of the organizations' corporate knox policies. Look for a bes like sys admin tool that expands on the remote wipe /lockz/ camera images etc, in the coming months. Exchange 2015 is still a ways away, but since you cant undo a blown efuse with any software, understand implications of blowing knox fully, not just warranty. And if you use exchange email, or plan to, keep knox untripped is best advice.
Gage_Hero said:
Do you know if this was resolved then? http://forum.xda-developers.com/showthread.php?t=2460745&page=8 there was more going on behind the scenes than I would like to have.....
http://forum.xda-developers.com/showthread.php?t=2460745&page=8
Click to expand...
Click to collapse
Yes. Ok, kingo is just an interface for all known exploits. The emei sniffing was actually being performed by vroot. Kingo was simply running existing vroot code. I talked to kingo support last week, who assured me that emei check was pulled during latest release, the vroot method is still present, however iz modified to remove those bad lines. When you run kingo, it opens a connection to kingo server to pull each exploit/patch as one method fails, pulls another, then another, as needed. This keeps package small, and allows for on the fly repo updatez on their end without having to re-release a package.
Kingo does not record emei at all any longer, it was vroot doing it, and kingo bc they simply ran vroot method without editing.
So you will see kingo go online to grab each exploit as required, in the new version, but no emei tracking any longer.
Besides the trojan that was used before in vroot, is picked up by avg free, so youd know if it were still doing it. I ran tcpview and tcpdump while flashing root to my device and didnt see any connections to china, any longer.
This can be verified on both odficial Facebook and Twitter account of kingo. Their intention is to at one point to charge a couple bucks for this app, having it exhibit malicious behaviour is bad for business. Youll notice vroot has no support or contact methods. Kingo does.
Sent from my SGH-I337M
Thanks, btw I can't seem to software update after I rooted my phone. It says my software was modified. Does anyone know how I can get it to check for updates? I'm already on 4.3 but I know our S4 will get 4.4 in a few months.
I am still good with Knox, I am at 0x0 for both lines.
Btw, I did freeze Knox in titanium, but not uninstall, just freeze. I did freeze many other apps but nothing dangerous, just normal ones like Travel, google movies, magazines, etc..
Ki Hi
Ramsey said:
Thanks, btw I can't seem to software update after I rooted my phone. It says my software was modified. Does anyone know how I can get it to check for updates? I'm already on 4.3 but I know our S4 will get 4.4 in a few months.
I am still good with Knox, I am at 0x0 for both lines.
Btw, I did freeze Knox in titanium, but not uninstall, just freeze. I did freeze many other apps but nothing dangerous, just normal ones like Travel, google movies, magazines, etc..
Click to expand...
Click to collapse
You cannot update ota when system is modified, there is an xposed module that changes modified to official tho. Not sure if it trips knox, likely. When updates come, unroot, apply, reroot. There are other guides that can be found here to update keepinng root with odin, you'll have to use the search provided.
Feezing with Titanium backup is fine. Supersu doesnt delete knox, it disables knox notifications. The whole point here is not tripping knox. That's why supersu asks if you want to disable knox, and not delete it, bc only disables, knox services still present. Feezing with tb is same result. Just supsrsu is free, tb is paid (for freezing anyway), though if youre on these forums, should be using tb anyway , titanium backup, greenify donation, and tasker are 3 must have root apps. Tasker is great. I use it to auto enable bluetooth and wifi based on gps location, or driving in the car. Lots of youtube vids on tasker if you areny familiat with it.
Sent from my SGH-I337M
There is an alternative to vroot and kingo methods. I was able to root mj6. I saw mk2 rooted as well successfully.
http://forum.xda-developers.com/showthread.php?t=2565758
If it helps any 4.3 MK6 users, I rooted using the download from this site and can confirm that it works:
http://forum.xda-developers.com/showthread.php?t=2565758
ravi_mytouch said:
There is an alternative to vroot and kingo methods. I was able to root mj6. I saw mk2 rooted as well successfully.
http://forum.xda-developers.com/showthread.php?t=2565758
Click to expand...
Click to collapse
Yep it does. Ive used it on a few i377m already. Wasn't available when i did mine. Kingo is relatively safe, latest release is, cant speak for previous or future versions. Kingo is just an interface that uses all known root methods (including vroot, and this method). Just keeps trying dif method til one works. Had this been available, would have used for mine. But it wasn't so setup a segregated lab at work, to test kingo and reports of malware. I didnt see any at that time via tcp dump and tcpview, however that could change since they just rip off other root methods/code to reuse, kingo does i mean. That said if you rooted with kingo, no need to repeat. Root is root (well, full root is full root), and no daemons u dont recognize running.
Sent from my SGH-I337M
Hey folks,
One of the forum moderators pointed me at this thread ( http://forum.xda-developers.com/showthread.php?t=2586586 ) as a suggestion to getting a ROM for my S4 that would alleviate the com.android.phone process crashes I had with other ROMS.
After flashing jfltespr_mk2_deodexed from micro-sd card through the Team Win recovery, my phone is now stuck at the Samsung Galaxy S4 logo screen with (Set Warranty Bit: Kernel) in the upper left.
Having looked through numerous threads on this issue, it seems there's a number of different remedies, from reflashing to simply powercycling.
There wasn't anything that was of much use in http://forum.xda-developers.com/showthread.php?t=2527706 either.
I have odin, and can boot into Team Win Recovery, or download mode. Suggestions/tips/ideas would be appreciated. Thanks.
Seems like you already have Knox tripped. And those warnings are because Knox detected modified files on your phone at boot up. I would suggest to odinto stock MK2
Sent from my SPH-L720 using Tapatalk
Go to this post and download the full stock mk2 tar file. Once downloaded extract the tar file from the zip file and install it using Odin 3.09 for best results. This will bring your phone to full stock unrooted. This should fix your phone problems. It is best to start with a clean slate. If you are still getting the force closes, then something on your data partition is causing your problem and you will need to do a factory reset after installing the tar file.
After you are up and running with no errors then you can re root your phone. I like safe root. It is quick and easy. Just Google Safe Root for Sprint Galaxy S4 and you will find it.
If this doesn't fix your phone than it might be hardware related. Also, just to be sure, make sure you don't have the L720T version of our phone. Because if you do, that is your problem.
http://forum.xda-developers.com/showpost.php?p=49213024
Sent from my icrap 2 using Tapatalk HD
That thread has a huge KNOX warning. I was hoping to ditch the Sprint bloatware.
Am I interpreting things right that I'm basically screwed for non-stock ROM's now?
Also, I have an SPH-L720
On the download rom screen, it reports KNOX KERNEL LOCK as 0x0, KNOX WARRANTY VOID as 0d?
cruise350 said:
Go to this post and download the full stock mk2 tar file. Once downloaded extract the tar file from the zip file and install it using Odin 3.09 for best results. This will bring your phone to full stock unrooted. This should fix your phone problems. It is best to start with a clean slate. If you are still getting the force closes, then something on your data partition is causing your problem and you will need to do a factory reset after installing the tar file.
After you are up and running with no errors then you can re root your phone. I like safe root. It is quick and easy. Just Google Safe Root for Sprint Galaxy S4 and you will find it.
If this doesn't fix your phone than it might be hardware related. Also, just to be sure, make sure you don't have the L720T version of our phone. Because if you do, that is your problem.
http://forum.xda-developers.com/showpost.php?p=49213024
Sent from my icrap 2 using Tapatalk HD
Click to expand...
Click to collapse
dearastronomer said:
That thread has a huge KNOX warning. I was hoping to ditch the Sprint bloatware.
Am I interpreting things right that I'm basically screwed for non-stock ROM's now?
Also, I have an SPH-L720
On the download rom screen, it reports KNOX KERNEL LOCK as 0x0, KNOX WARRANTY VOID as 0d?
Click to expand...
Click to collapse
You're not screwed for non stock ROMs, IF you don't mind tripping the knox 'counter'. If you follow @cruise350 advice you'll be back to Stock. then root (with SafeRoot maybe; search it's here or CF-Auto Root) you could then install a custom recovery (using GooManager or by Odining one), then flash away.
BUT you are going to trip the Knox counter by using a custom recovery.
Please spend a little (actually a lot) of time reading and understanding how things work on this phone and you'll really enjoy it and get the most out of it with as little frustration as possible.
Good luck
From the advice in this thread I was able to get back to stock ROM w/ root (CF-Auto-Root). Thanks for the tips, and for being patient.
I'm going to do some reading on Knox, because I'm getting conflicting reports on the ability to remove it.
leaderbuilder said:
You're not screwed for non stock ROMs, IF you don't mind tripping the knox 'counter'. If you follow @cruise350 advice you'll be back to Stock. then root (with SafeRoot maybe; search it's here or CF-Auto Root) you could then install a custom recovery (using GooManager or by Odining one), then flash away.
BUT you are going to trip the Knox counter by using a custom recovery.
Please spend a little (actually a lot) of time reading and understanding how things work on this phone and you'll really enjoy it and get the most out of it with as little frustration as possible.
Good luck
Click to expand...
Click to collapse
I still can't figure out what the big deal is people have about knox. It does not effect you at all if it is tripped unless you plan on sending your phone to Samsung for warranty service. It does not prevent you from running custom roms, installing mods, or using your phone to its full functionality. It is a secure container program for corporations and government agencies that require more security for access to their networks and information. If your company is not requiring you to have a secure phone, than it means nothing. It is easily disabled or removed. The main difference in our phones after MJA firmware is Samsung made it so we can't downgrade the bootloader any more. This was so they could fully implement the knox container to prevent downgrading to older non knox bootloaders thus skirting the knox security. The warranty flag that it trips is the knox warranty flag, which purpose is to let your IT department know that you have tampered with your phone and can no longer be guaranteed to provide the secure container. It also lets Samsung know you have tampered with your phone which may violate your warranty.
cruise350 said:
I still can't figure out what the big deal is people have about knox. It does not effect you at all if it is tripped unless you plan on sending your phone to Samsung for warranty service. It does not prevent you from running custom roms, installing mods, or using your phone to its full functionality. It is a secure container program for corporations and government agencies that require more security for access to their networks and information. If your company is not requiring you to have a secure phone, than it means nothing. It is easily disabled or removed. The main difference in our phones after MJA firmware is Samsung made it so we can't downgrade the bootloader any more. This was so they could fully implement the knox container to prevent downgrading to older non knox bootloaders thus skirting the knox security. The warranty flag that it trips is the knox warranty flag, which purpose is to let your IT department know that you have tampered with your phone and can no longer be guaranteed to provide the secure container. It also lets Samsung know you have tampered with your phone which may violate your warranty.
Click to expand...
Click to collapse
True but it lock the bootloader from what I’m hearing
Hence stopping the installation of custom roms
Hello everyone. Just hoping to find some advice on how I should go about upgrading to Kitkat.
I'm currently running rooted (via de la vega, knox at 0x0 currently) stock 4.3 firmware on a T-mob Note 3, stock bootloader. For now, I'd like to keep the rom stock but get it up to 4.4.2. I've been digging around trying to find out what I should do and am coming up a bit short. Hopefully I can get pointed in the right direction.
One thing I noticed is that one needs a different bootloader for 4.4.2 than 4.3. I'm no longer concerned about keeping knox at 0x0, and would like to throw CWM Touch on. Should I be installing CWM for 4.3 before updating to 4.4.2, then updating CWM? Or should I be installing CWM for 4.4.2 right from the start?
Is there another root method I should use, perhaps something that will handle getting the custom bootloader on as part of the process?
Is it possible to update like this without a wipe?
Ultimately, I'd prefer to get a bootloader on first so I can make a backup, and then retain some way of being able to revert to the backup if needed. I understand that once knox is tripped, there's no getting that back. That is fine.
If I need to provide more information before assistance can be provided, please ask. Thanks in advance for your help/suggestions.
SM-N900T
Android v4.3
Baseband N900TUVUBMI7
dethzord said:
...
Is it possible to update like this without a wipe?
Ultimately, I'd prefer to get a bootloader on first so I can make a backup, and then retain some way of being able to revert to the backup if needed. I understand that once knox is tripped, there's no getting that back. That is fine.
...
Click to expand...
Click to collapse
It is possible to do the update without the wipe on N9005, but probably on N900T you should better ask for details in the specific forum.
You should also keep in mind that (AFAIK) at this point it is impossible to return on N9005 from 4.4.2 back to 4.3 (with or without wipe, no matter what kind of backup you have). Some things might be different on N900T - so again you should ask in the right forum for more details!
Historically the first method available was with Mobile Odin Pro - look around for the specific thread on that.
Another option is to manually select a specific stock ROM that uses a kernel BEFORE July 2014, write it with normal Odin and then use Towelroot to re-root.
If you somehow managed to get on a version AFTER July 2014 Towelroot will no longer work and in that case you will need to read and understand the method described in this thread:
http://forum.xda-developers.com/galaxy-note-3/general/root-root-xxufnf4-stock-firmware-knox-t2840150
dethzord said:
Hello everyone. Just hoping to find some advice on how I should go about upgrading to Kitkat.
I'm currently running rooted (via de la vega, knox at 0x0 currently) stock 4.3 firmware on a T-mob Note 3, stock bootloader. For now, I'd like to keep the rom stock but get it up to 4.4.2. I've been digging around trying to find out what I should do and am coming up a bit short. Hopefully I can get pointed in the right direction.
One thing I noticed is that one needs a different bootloader for 4.4.2 than 4.3. I'm no longer concerned about keeping knox at 0x0, and would like to throw CWM Touch on. Should I be installing CWM for 4.3 before updating to 4.4.2, then updating CWM? Or should I be installing CWM for 4.4.2 right from the start?
Is there another root method I should use, perhaps something that will handle getting the custom bootloader on as part of the process?
Is it possible to update like this without a wipe?
Ultimately, I'd prefer to get a bootloader on first so I can make a backup, and then retain some way of being able to revert to the backup if needed. I understand that once knox is tripped, there's no getting that back. That is fine.
If I need to provide more information before assistance can be provided, please ask. Thanks in advance for your help/suggestions.
SM-N900T
Android v4.3
Baseband N900TUVUBMI7
Click to expand...
Click to collapse
The following instruction is for N900V. Not sure if it is also useful for N900T.
Code:
1. Open SuperSU settings
2. Scroll down to the bottom, Enable Pro. Reboot. (you have to purchase SuperSU Pro)
3. Check Survival mode
4. Uncheck Enable Superuser
5. Install OTA update
6. After reboot, Enable Superuser
7. Disable Survival mode
vndnguyen said:
The following instruction is for N900V. Not sure if it is also useful for N900T.
Code:
1. Open SuperSU settings
2. Scroll down to the bottom, Enable Pro. Reboot. (you have to purchase SuperSU Pro)
3. Check Survival mode
4. Uncheck Enable Superuser
5. Install OTA update
6. After reboot, Enable Superuser
7. Disable Survival mode
Click to expand...
Click to collapse
I'll try that tonight. Would try it immediately if not for low battery. I had done the survival and the OTA failed to install, but I didn't think to disable SU. Thanks, will let you know if it works.
Looks like it's a no go. Still fails to update. I dunno if there's anything else I might need to ditch first like Xposed or the like. But essentially, I might as well wipe if I have to redo all my tweaks.
But if I can't get the OTA working, I have to figure out what the best way to go about it will be as far as getting the right bootloader and installing in the right order, and retaining root. If I have to go with a custom rom, I will.
Situation:
I'm on Verizon with a Note 3 running 4.4.2. The methods shown for rooting almost always make the assumption that people want to run a custom ROM. I do not. The Safestrap developer bailed on the project, and nobody knows if it can be used in the future anyway.
Goals:
1. This is a business phone, not something that I want to continuously frog around with. I just want to be able to record telephone conversations when using my Bluetooth headset exactly the same as when I'm not, maybe a decent backup, and basically get my Verizon Note 3 and Android's functionality up to the level of where Windows Mobile has been since 2009. From what I understand, to do that may require the Xposed Framework.
2. Be able to give root back and have everything back like it was if necessary.
3. Be able to take OTA updates. I don't care if I need to uninstall some apps, give root back, accept the OTA update, take root back, and reinstall the apps. OTA updates don't happen often anyway.
4. Not lose the phone warranty in the process if possible. It seems one of the required apps for the root process is SuperSU. One of the options is to disable KNOX. Other than everyone doing it, and being recommended for vague reasons, why would I want to do that? Can you re-enable it later?
Thanks!
Towel root should do what you want. I currently don't know of anyone that used towel root or kingo that tripped Knox. Since you're on NC4 probably kingo isn't an option so it's towel root.
thegamerdarkseid said:
Towel root should do what you want. I currently don't know of anyone that used towel root or kingo that tripped Knox. Since you're on NC4 probably kingo isn't an option so it's towel root.
Click to expand...
Click to collapse
So Towel root and what? I'm guessing SuperSU without having it disable KNOX...or?
IT_Architect said:
So Towel root and what? I'm guessing SuperSU without having it disable KNOX...or?
Click to expand...
Click to collapse
You have to use SuperSu for root privileges.
IT_Architect said:
So Towel root and what? I'm guessing SuperSU without having it disable KNOX...or?
Click to expand...
Click to collapse
Towel Root is What you use to gain ROOT. Towel Root is basically a Program/Software that you will use to ROOT your Note 3. I used Kingo so I don't know much about Kingo but its probably not much different than Kingo, but based on what the other person said you need to use Towel Root. One thing you will want to do AFTER you go through the ROOT process is, Look in your app drawer & see if SuperSU is installed, if it is, you are Rooted, if it is Not, you are Not. I would also Download Root Checker from the Play Store to Verify you have ROOT.
SuperSU or Superuser is an app that gets installed in your phone when you Root it, that Manages what other apps you Grant/Deny Root permission. It does Not ROOT your phone. You do not need to download it from the Play Store. It is only in the Play Store to give you Updates, Its not meant to be as an initial download. Hope this Helps Bud. Happy Rooting! :laugh:
jasonsc1 said:
Towel Root is What you use to gain ROOTSuperSU or Superuser is an app gets installed in your phone when you Root it, that Manages what other apps you Grant/Deny Root permission...You do not need to download it from the Play Store. It is only in the Play Store to give you Updates
Click to expand...
Click to collapse
That makes sense.
So what I'm thinking is:
1. Root
2. Make sure SuperSU is there to know I'm rooted.
Later when there is an update:
- Refuse it until there is a way to get root without triggering KNOX.
- Uninstall root apps.
- From SuperSU give root back, which should bring it back to stock.
- Then allow the OTA and hopefully it will not trigger KNOX
I'm guessing it would be best not to install xposed framework because it makes system changes, which could cause things to go wrong during an update.
All that I need in the near term is to get my Bluetooth voice recording back.
Thanks!
IT_Architect said:
That makes sense.
So what I'm thinking is:
1. Root
2. Make sure SuperSU is there to know I'm rooted.
Later when there is an update:
- Refuse it until there is a way to get root without triggering KNOX.
- Uninstall root apps.
- From SuperSU give root back, which should bring it back to stock.
- Then allow the OTA and hopefully it will not trigger KNOX
I'm guessing it would be best not to install xposed framework because it makes system changes, which could cause things to go wrong during an update.
All that I need in the near term is to get my Bluetooth voice recording back.
Thanks!
Click to expand...
Click to collapse
That sounds like a Pretty good plan. I Rooted my Note 3 a while back. I was on JB & I'm still currently JB. ACTUALLY Its been a while since I've been on XDA. When I did Root my Note 3 there was NO WAY to ROOT Kit Kat 4.4.2. I did NOT know there was a way to ROOT it now. If there is Can you post a Link. Everything I've read says theirs No Way to Root Kit Kat but its been a while since I researched it. In my case After I Rooted my Note 3 I Froze SDM the app that receives Versions OTA updates. I kept getting one wanting me to Update to Kit Kat. I did not want to Lose my Root & then be on Kit Kat & not be able to Re-Root my Note 3. XDA has a version of Kit Kat made my a couple of the Developers, Beanstown106's & Hashcode's (the guy who made safestrap) that Already has Root. I'm going to Flash their Kit Kat version once I grow the Kahunas. I also Froze Knox so it could Not trip, although it did not Trip when I Rooted my Note 3 via Kingo but I'm on a different version than you.
Also You will Not need to Uninstall the Root apps. They will have No Effect on your phone. They will just not have Root permissions. I also don't see a need to Un Root- Re Root. I would just not accept the OTA Updates. I also have Xposed Framework with several modules & it & them have No negative effects on my Note 3. Anyways Hope this Helps somewhat, Post that Kit Kat Root Link if you can. Thanks
Here is a Link to what Im going to do.
http://forum.xda-developers.com/showthread.php?t=2740466
jasonsc1 said:
If there is Can you post a Link. Everything I've read says theirs No Way to Root Kit Kat
Click to expand...
Click to collapse
There are at least two:
1. Towelroot - Free
2. One Click Root - 2 packages to choose from: $29.95 package which includes root only and $39.95 which includes rooting + removal of bloatware + 30 days free tech support.
jasonsc1 said:
After I Rooted my Note 3 I Froze SDM the app that receives Versions OTA updates... I also Froze Knox so it could Not trip, although it did not Trip when I Rooted my Note 3
Click to expand...
Click to collapse
What did you use to freeze them with, Titanium?
jasonsc1 said:
Also You will Not need to Uninstall the Root apps. They will have No Effect on your phone. They will just not have Root permissions.
Click to expand...
Click to collapse
However they make changes in the system area, which I was concerned might foul up the OTA or trip KNOX.
jasonsc1 said:
I also don't see a need to Un Root- Re Root. I would just not accept the OTA Updates.
Click to expand...
Click to collapse
I am a little gun shy that if the OTA finds it rooted, it will trip KNOX and not do any more OTAs.
jasonsc1 said:
I also have Xposed Framework with several modules & it & them have No negative effects on my Note 3.
Click to expand...
Click to collapse
That is the only other product I looked at. It looks interesting, but I don't see that it brings anything to the table that I want. I'm not a customization guy, I just need to get basic functionality out of the phone such as call recording under Bluetooth and be able to backup my entire phone and settings.
Thanks!
IT_Architect said:
There are at least two:
1. Towelroot - Free
2. One Click Root - 2 packages to choose from: $29.95 package which includes root only and $39.95 which includes rooting + removal of bloatware + 30 days free tech support.
What did you use to freeze them with, Titanium?
However they make changes in the system area, which I was concerned might foul up the OTA or trip KNOX.
I am a little gun shy that if the OTA finds it rooted, it will trip KNOX and not do any more OTAs.
That is the only other product I looked at. It looks interesting, but I don't see that it brings anything to the table that I want. I'm not a customization guy, I just need to get basic functionality out of the phone such as call recording under Bluetooth and be able to backup my entire phone and settings.
Thanks!
Click to expand...
Click to collapse
Ok, I Rooted my Note 3 back in March, at that time there was No Way to Root Kit Kat. I did a lil Looking around & did find that you can Now Root Kit Kat.
No, I did not use Titanium, I do have it. I usually use Titanium just to backup my apps/data. I Froze the SDM app which is the app that Looks for/Receives OTA. So I do Not get any Updates. I don't see reason too. The only OTA that has came out since I bought my Note 3 is the Kit Kat OTA. If you Freeze that app you will have No Problems.
To my Knowledge the Only ROOT apps that can make changes to the System area is the Xposed apps/Modules. No other Root App that I know of makes any changes to the System area, unless you let it, & that can be reversed & the Apps STILL dont have to be Uninstalled. I can not think of ANY Reason to Uninstall the ROOT apps because there is Nothing about them that could cause Knox to Trip. I got NOTHING.
Yes Xposed opens a WHOLE NEW WORLD of Customization's. After having it, I could not live without it. I LOVE be able to Truly own my device. XPrivacy Guard gives me the Warm & Fuzzy that the 2 GPS tracking alarms I have on my Gixxer give me. I control what Permissions apps have, what information they can receive. I could not Live without XPosed or XPrivacy Guard,
jasonsc1 said:
Ok, I Rooted my Note 3 back in March, at that time there was No Way to Root Kit Kat. I did a lil Looking around & did find that you can Now Root Kit Kat.
Click to expand...
Click to collapse
I might add that 4.4.2 there is, but NOT 4.4.4 without tripping KNOX. I know the 4.4.2 settings interface is quite a bit different than JB, but whether that translates into anything useful, I don't know. I do know most docs are for JB. Thus, if there is anything in 4.4.2 worth having that you don't already have via root, now might be the time IF they are still rolling 4.4.2. You don't want to snag 4.4.4 by accident. I know that I haven't received an update request yet, and I am on 4.4.2, but the S5 gets 4.4.4. From the little reading I've done, there is little difference between 4.4.2 and 4.4.4 except KNOX has been updated, and a massive bug roll-up . (What those bugs might be, I have not researched.) Moving to KitKat, you also incur the problem of apps writing anywhere to the SD card. IMO, the biggest difference between JB and KitKat 4.4.2 and KitKat 4.4.4 is security. 4.4.4 on the Note 3 does NOT give you the new Touchwiz that the S5 gets with 4.4.4.
"At the beginning of June, Google released two new Android 4.4 KitKat updates. First was Android 4.4.3 KitKat, a massive bug fixer. A few days later, the company pushed out its Android 4.4.4 KitKat update. Both were, and still are, bug fixers aimed at squashing major Android 4.4.2 KitKat problems and they continue to land for key devices as we push toward the fall. I am miffed by the omission of the new TouchWiz on the 4.4.4 update on the Note 3"
There aren't any bugs that I noticed, and until they give you something other than putting you into tighter and tighter box, you might want to wait until they come out with something that benefits you.
jasonsc1 said:
No, I did not use Titanium, I do have it. I usually use Titanium just to backup my apps/data. I Froze the SDM app which is the app that Looks for/Receives OTA. So I do Not get any Updates. I don't see reason too. The only OTA that has came out since I bought my Note 3 is the Kit Kat OTA. If you Freeze that app you will have No Problems.
Click to expand...
Click to collapse
Back to my original question, what did you freeze it with, and BTW, is SDM the name of the program, or is that an abbreviation for something?
jasonsc1 said:
To my Knowledge the Only ROOT apps that can make changes to the System area is the Xposed apps/Modules. No other Root App that I know of makes any changes to the System area, unless you let it, & that can be reversed & the Apps STILL dont have to be Uninstalled. I can not think of ANY Reason to Uninstall the ROOT apps because there is Nothing about them that could cause Knox to Trip. I got NOTHING.
Click to expand...
Click to collapse
That is very helpful, and clarifies things for me.
jasonsc1 said:
Yes Xposed opens a WHOLE NEW WORLD of Customization's. After having it, I could not live without it. I LOVE be able to Truly own my device. XPrivacy Guard gives me the Warm & Fuzzy that the 2 GPS tracking alarms I have on my Gixxer give me. I control what Permissions apps have, what information they can receive. I could not Live without XPosed or XPrivacy Guard,
Click to expand...
Click to collapse
What is Gixxer? There is Privacy Guard, and XPrivacy. I assume you mean XPrivacy.
Thanks!
Lol, I meant to put what I used in my Last reply. I used Rom Toolbox Pro. It's also a Great App. I actually prefer it more than Titanium Backup. I believe because of the UI.
Glad to Help, what lil I can
Oh Gixxer is another name that Suzuki MC riders call their GSXR. I have a 08 GSXR 1000. A lot of riders call the GSXR, a Gixxer. Lol, or something like Gixxer 8k (08 GSXR 1000) would be mine. Lol. I sometimes assume everyone is a Rider. Lol. Sorry about that.
Yes I meant X PRIVACY Not LBE Privacy Guard. I've heard Horror stories about it. I have Never had a Problem with X PRIVACY yet.
Oh, One more thing, As far as Safe strap goes. You can definitely use it on your Note 3 right now. Yes the developer stop sending updates but trust me he's around. He's on here all the time, with New stuff. He helped develop the XDA Kit Kat Rom. His name is Hashcode. Again Safe strap is the ONLY way to go if you are going to flash Roms. That or TWERP, which is Harder (more complicated) to get on Note 3 & Not as Good. Safestrap is so Good bc you always can Boot into your Stock slot, while you still have a Custom slot too, if anything goes wrong, you could still Boot to the other.
Safestrap=The Best Custom Recovery, IMO
Later Bud. I work nightshift this weekend, so it's time for me to get some sleep to be back at it, at 6pm this evening.
This are my thoughts for everyone to critique. Let me know if there are any flies in the ointment before I proceed.
Prerequisites:
1. Go into Settings/Security, and make sure Unknown sources is checked, and Verify apps is unchecked.
Root for 4.4.2:
1. Install Towelroot
2. Install Check Root from Play Store and check for root
3. Download SuperSU zip file from the link on the developer's thread, http://forum.xda-developers.com/showthread.php?t=1538053. This will NOT come from the Play Store or Amazon. Then unzip it on your phone. Then go to the "common" directory, and run the APK. After that you may get a prompt to update the binaries.
4. When you Run SuperSU and it asks you if you want to disable KNOX, SAY NO!!!
5. Then install Titanium backup and Freeze KNOX, so you can Thaw it later.
____com.sec.enterprise.knox.attestation
____com.sec.knox.eventsmanager
____KLMS Agent
____KNOX
____Knox Notification Manager
____KNOX Store
Unroot back to factory for 4.4.2:
1. Go into Titanium Backup and Thaw KNOX.
2. Open ES File Explorer
____a. Go to Favorites and hit the / button
____b. Click on menu / Settings / and check Enable Root Explorer
____c. Also check Mount File System
____d. Click the back button
3. Then remove SU. (The developer is working on a way to do this automatically with his full unroot function, which will make this step unnecessary)
____a. Open ES File Manager
____b. To to system / bin and find the SU folder. Do a long press and delete
____c. Click the back button and go to system / xbin directory and find the SU file and delete if any present.
____d. Click the back button and go to system / app directory and find Superuser.apk and delete it if it on your phone.
4. Reboot. Root should be gone.
5. Do a factory reset, go to Settings / Personal / Backup and reset
Summary: This should put the phone back to stock for factory warranty, or to sell, or to simply start over.
I would suggest you drop the requirement to be able to take an OTA with a customized phone. It is almost always a better idea to (i) make your backups, investigate whether you can root the new release - and if so, then (ii) restore to full stock, (iii) take the OTA, (iv) re-root and (v) have your way with things.
The reasons are several, but at least one of them is that the OTA installers tend to do a top-level, recursive chmod()/chown() in /system/{x}bin, followed up with chmod()/chown() operations on individual files in those file subtrees as needed. This has the side effect of emasculating the "su" binary privilege escalation via setuid. I wouldn't be surprised if - as a result of SElinux enforcing mode - similar sorts of troubles start occurring due to similar resets/modding of SElinux extended attributes in the same file trees (e.g. if the OTA installer starts doing recursive chcon()s).
(The above is the raison de etre for apps like "OTA rootkeeper" and so forth - they attempt to work around this OTA installer side effect)
The second reason is that OTAs sometimes bundle a bootloader update. Samsung's strict rollback enforcement policies means that you probably will not be able to undo an OTA that you regret (for any reason) without triggering Knox.
I'm still on MJE. It made me happy when I bought the phone & is still making me happy, so the fact that there are new releases available doesn't bother me one whit. It is still a fantastic phablet (& I can exploit the WiFi tether bug without Wanam and all the related framework mods).
FWIW, I reviewed the .apk/.odex files that I "froze" (using "chmod 000", not TiBu); things have changed a little bit since MJE, but:
Knox Disable: ContainerAgent, ContainerEventsRelayManager, KLMSAgent, KNOXAgent, KNOXStore, KnoxAttestationAgent
OTA Nagware Disable: LocalFOTA, SDM
Asurian Spyware Disable: VMS.apk
Probably I should also disable SHealth too. These Samsung phones are bristling with surveillance crap, and there seems to be no end to it. Probably it's even worse now with KitKat. Who knew that the Orwellian future would be developed and financed by marketing companies ... and thereafter trivially co-opted by governments?
have fun with your phone.
I was pretty much settled on not rooting, and you come along and start making sense with solid business reasons. I also view Google, Samsung, Microsoft, and the government access for what it is, criminal activity. I simply want a phone that has the capabilities of my old Windows Mobile phone, and the same levels of privacy.
If they can spy on us, than a requirement for Google and all government personnel is to have 24 x 7 video and audio surveillance on them while they are at work, and every room in their house at home, and have it stream live on YouTube..
Just safestrap it already. Even on NC4 OTA, you can safestrap and install NC2 kernel and pick from many fantastic 4.4.2 ROMs. In the future, take the hypothetical 5.0 update and then you'll never have root, lol.
Anyway, you can return to stock NC4 if needed.
OR don't. Your loss.
xdadevnube said:
Just safestrap it already. Even on NC4 OTA, you can safestrap and install NC2 kernel and pick from many fantastic 4.4.2 ROMs.
Click to expand...
Click to collapse
- I don't see the necessity of a custom ROM. I simply want to be able to record calls with my Bluetooth active. This limitation serves as a reminder that a lot less effort goes into Android than we tend to believe. This is a legal requirement for many businesses. Fortunately for Android, most development and innovation is done out of necessity by phone makers such as Samsung, etc.
- I also want to be able to prevent the update to 4.4.4.
- To do the rooting and SafeStrap, I would want to be able to un-SafeStrap, un-SuperSU, re-enable KNOX, and un-root back to factory. I haven't seen that discussed anywhere. The only thing I see to be able to get back to factory is this, if it works: http://www.galaxynote3update.com/un...tock-official-firmware-4-4-2-or-4-4-3-kitkat/ and it does not address SafeStrap. There is more to this than warranty, it is getting the phone back to stock to fix problems. There are thousands of posts of people having problems after rooting and installing custom ROMs.
xdadevnube said:
In the future, take the hypothetical 5.0 update and then you'll never have root
Click to expand...
Click to collapse
That's what concerns me. I understand why Samsung is doing what they are doing. IOS has been pushing Android out of the enterprise and government by support efficiencies and legislated security requirements. Samsung is the only Android they are allowed to buy. Thus, I've noticed:
- The newer it is, the more secure it is. Security in the ?NIX world is simplistic and limited. The easiest fix is to block functionality, and add KNOX as the enforcer and recorder.
- The features you gain with each new release, are less valuable than the features you lose from increased operating system security. Android is rapidly becoming as confining as the iPhone.
- Control over privacy becomes less and less with each new release.
While the progression makes sense from an operating system security standpoint, but runs counter to privacy control and functionality, the reasons why people buy Android.
To completely unroot and restore to stock. Uninstall safestrap recovery. Uninstall towelroot. Uninstall busybox. Uninstall superuser. Factory reset phone. Then flash NC4 with odin for good measure. You really dont need to install safestrap at all unless you want to do backups.
IT_Architect said:
- I don't see the necessity of a custom ROM. I simply want to be able to record calls with my Bluetooth active. This limitation serves as a reminder that a lot less effort goes into Android than we tend to believe. This is a legal requirement for many businesses. Fortunately for Android, most development and innovation is done out of necessity by phone makers such as Samsung, etc.
- I also want to be able to prevent the update to 4.4.4.
- To do the rooting and SafeStrap, I would want to be able to un-SafeStrap, un-SuperSU, re-enable KNOX, and un-root back to factory. I haven't seen that discussed anywhere. The only thing I see to be able to get back to factory is this, if it works: http://www.galaxynote3update.com/un...tock-official-firmware-4-4-2-or-4-4-3-kitkat/ and it does not address SafeStrap. There is more to this than warranty, it is getting the phone back to stock to fix problems. There are thousands of posts of people having problems after rooting and installing custom ROMs.
That's what concerns me. I understand why Samsung is doing what they are doing. IOS has been pushing Android out of the enterprise and government by support efficiencies and legislated security requirements. Samsung is the only Android they are allowed to buy. Thus, I've noticed:
- The newer it is, the more secure it is. Security in the ?NIX world is simplistic and limited. The easiest fix is to block functionality, and add KNOX as the enforcer and recorder.
- The features you gain with each new release, are less valuable than the features you lose from increased operating system security. Android is rapidly becoming as confining as the iPhone.
- Control over privacy becomes less and less with each new release.
While the progression makes sense from an operating system security standpoint, but runs counter to privacy control and functionality, the reasons why people buy Android.
Click to expand...
Click to collapse
It takes 10 minutes to root. And 10 minutes to unroot. Including safe strap. Nothing will trip knox. Beans has the stock nc4 ota rooted deodexed and busy boxed. All is needed to do what you want to do. You will find Zero anything for your stock odex ota. So root safestrap flash the stock rom and add call recording via xposed.... There is no other info you need that isnt already posted in a sticky.
drewcam888 said:
To completely unroot and restore to stock. Uninstall safestrap recovery. Uninstall towelroot. Uninstall busybox. Uninstall superuser. Factory reset phone. Then flash NC4 with odin for good measure. You really don't need to install SafeStrap at all unless you want to do backups.
Click to expand...
Click to collapse
- When SuperSU is installed, it disables KNOX. If I uninstall SuperSU, will it re-enable KNOX, or if I flash back to Verizion KitKat 4.4.2 NC4 N900VVRUCNC4_N900VVZWCNC4_N900VVRUCNC4_HOME.tar.md5.7z, from here, http://forum.xda-developers.com/showthread.php?t=2524572 will it restore the KNOX functionality?
- What happens to the ROMs in the ROM Slots when you uninstall SafeStrap recovery? Is the space released or...?
RomsWell said:
It takes 10 minutes to root. And 10 minutes to unroot. Including safe strap. Nothing will trip knox. Beans has the stock nc4 ota rooted deodexed and busy boxed. All is needed to do what you want to do. You will find Zero anything for your stock odex ota. So root safestrap flash the stock rom and add call recording via xposed.... There is no other info you need that isnt already posted in a sticky.
Click to expand...
Click to collapse
And it takes days of research to get to the 10 minutes to make sure what you read is accurate, and will work with your phone. I've read so many stickys, forum posts, blogs, and YouTube videos, that I've lost count. What I've learned is the custom ROM process is far from straightforward.
a. The SuperSU at the PlayStore is from an archeological dig. What I've read so far, I need at least 2.13 for things to work right, 2.16 is current, and 2.19 beta.
b. For the Note 3, just within KitKat 4.4.2 there is NC2, NC3, and NC4. From what I've gathered from a lot of reading and videos is that Safestrap-HLTEVZW-NC2-3.75-B04.apk is the ONLY one that works right with Verizon's NC4.
c. The whole idea of SafeStrap is to preserve the factory slot, and work from another slot. BeansTown106's rooted deodexed ROM, replaces the factory ROM.
d. BeansTown106's rooted deodexed ROM is not an NC4 kernel ROM. "The nc4 stock rom beans has posted isnt patched for the nc4 kernel. "
Thanks!
Apparently this does not prevent OTA's. Like most, I didn't like Magazine UX or Knox so I flashed. Tripped the Knox Warranty Void =1. So I went to Sammobile and downloaded the July 2014 release and flashed it. Lo and behold, when I hit software updates it started downloading. Will let you know of my progress.
pworcester said:
Apparently this does not prevent OTA's. Like most, I didn't like Magazine UX or Knox so I flashed. Tripped the Knox Warranty Void =1. So I went to Sammobile and downloaded the July 2014 release and flashed it. Lo and behold, when I hit software updates it started downloading. Will let you know of my progress.
Click to expand...
Click to collapse
OK. It took me from ANF4 to ANI1!
pworcester said:
OK. It took me from ANF$ to ANI1!
Click to expand...
Click to collapse
and from ANI1 to ANK1! Sweet!!
KNOX is mainly meant to ensure an untampered device for corporate security purposes; not to prevent OTAs.
yes it just causes to end your guarantee in case you take it to samsung service
benveq said:
yes it just causes to end your guarantee in case you take it to samsung service
Click to expand...
Click to collapse
Its not clear that is the case either. Reports may vary, but at least some have said KNOX fuse tripped does not void warranty.
The main purpose for KNOX counter is for corporate IT staff to see that phone is untampered, and safe for enterprise use and various KNOX security apps.
redpoint73 said:
Its not clear that is the case either. Reports may vary, but at least some have said KNOX fuse tripped does not void warranty.
The main purpose for KNOX counter is for corporate IT staff to see that phone is untampered, and safe for enterprise use and various KNOX security apps.
Click to expand...
Click to collapse
I came from a tab2 10.1 that I could reset completely. Wasn't sure if knox would keep me from getting updates.
pworcester said:
I came from a tab2 10.1 that I could reset completely. Wasn't sure if knox would keep me from getting updates.
Click to expand...
Click to collapse
Its good to get more confirmation, in any case. There seems to be a good amount of mixed info about KNOX. So thanks for posting it.
redpoint73 said:
KNOX is mainly meant to ensure an untampered device for corporate security purposes; not to prevent OTAs.
Click to expand...
Click to collapse
Regardless of what it's meant for, if you trip Knox and then try to do an OTA you will get a message telling you you can't do that. Now, apparently manually flashing something removes that restriction, which is great, but the fact remains.
redpoint73 said:
Its not clear that is the case either. Reports may vary, but at least some have said KNOX fuse tripped does not void warranty.
The main purpose for KNOX counter is for corporate IT staff to see that phone is untampered, and safe for enterprise use and various KNOX security apps.
Click to expand...
Click to collapse
I used Odin to flash the July 2014 relase. Prior to that I had the current relase falshed through Odin When I would check for updates it would tell me my device was modified. Going back to July and letting it OTA to current, now when I check for updates it says the latest software is installed.
thebobmannh said:
Regardless of what it's meant for, if you trip Knox and then try to do an OTA you will get a message telling you you can't do that. Now, apparently manually flashing something removes that restriction, which is great, but the fact remains.
Click to expand...
Click to collapse
You're right, I wasn't completely clear on the details of the situation (once modded, I don't believe in OTAs) so thanks for clarifying.
---------- Post added at 09:51 AM ---------- Previous post was at 09:50 AM ----------
pworcester said:
I used Odin to flash the July 2014 relase. Prior to that I had the current relase falshed through Odin When I would check for updates it would tell me my device was modified. Going back to July and letting it OTA to current, now when I check for updates it says the latest software is installed.
Click to expand...
Click to collapse
Again, thanks for the clarification.
It's not the Knox status that matters for OTAs. It is the flag that identifies your setup as Custom that prevents OTAs. That is a result of having a custom recovery. For example, if I root my device, tripping Knox, and later decide to Odin back to stock without custom recovery, I can (and have) receive OTAs because my status is returned to Official. I can then re-root, flash custom recovery (thus resetting status to Custom), and no longer receive OTAs.
Sent telepathically
RiverCity.45 said:
It's not the Knox status that matters for OTAs. It is the flag that identifies your setup as Custom that prevents OTAs. That is a result of having a custom recovery. For example, if I root my device, tripping Knox, and later decide to Odin back to stock without custom recovery, I can (and have) receive OTAs because my status is returned to Official. I can then re-root, flash custom recovery (thus resetting status to Custom), and no longer receive OTAs.
Click to expand...
Click to collapse
Weird, all I did was root my T900 (via Odin), without installing a custom recovery, and was subsequently unable to take an OTA. I didn't really mess with it after that -- I switched to CM shortly after -- but that was my very limited experience. Could have been a fluke.
If you used CF Auto Root, part of the automated process mucks with recovery to achieve root (thereby rendering your status as Custom). One can Odin flash back to complete stock (which unroots and resets recovery to Official), but Knox remains tripped.
RiverCity.45 said:
If you used CF Auto Root, part of the automated process mucks with recovery to achieve root (thereby rendering your status as Custom). One can Odin flash back to complete stock (which unroots and resets recovery to Official), but Knox remains tripped.
Click to expand...
Click to collapse
Great info, thanks! THis is my first Samsung / Knox device so still learning the basics.
Would it be safe to dirty flash (flash without wiping /data, only /cache and dalvik) latest stock ROM over older stock ROMs (modified with custom recovery)?
Sorry to necro-ish-post. Just got one of these on sale and I'm getting used to the "Samsung Way" after a Nexus tablet.
Suppose I've rooted my ROM without tripping Knox. I'd imagine if another OTA comes along it might fail due to modifications to the ROM. Can I use Odin to reflash the system part of the ROM back to stock without tripping Knox, so that the OTA will subsequently work?
cmstlist said:
Sorry to necro-ish-post. Just got one of these on sale and I'm getting used to the "Samsung Way" after a Nexus tablet.
Suppose I've rooted my ROM without tripping Knox. I'd imagine if another OTA comes along it might fail due to modifications to the ROM. Can I use Odin to reflash the system part of the ROM back to stock without tripping Knox, so that the OTA will subsequently work?
Click to expand...
Click to collapse
Yep. You can get a stock ROM and flash it with ODIN. Knox won't be tripped and you will loose root. Other thing you can do is stay rooted, and flash with ODIN the new ROMs as soon as they are available. Instead of re-flashing the same ROM you are on right now, so you can get an OTA, why not wait until a new ROM is released and flash that new ROM then? You can reroot then, if you want (towelroot). Of course you have to keep an eye on the forum so you know when a new ROM is available. Or check samfirmware from time to time :good:
Good to know. I don't know if Lollipop is ever on the agenda for Tab Pro, but if so I'd imagine there won't be a way to get it Towelrooted.
HELP!!! U.S. version of sm-T520
I have the Sm-T520nzwaxar. I needed to flash a firmware to revert it to stock. I was aware of the region based firmwares, but I still flashed one. The process failed near the end. Odin said "Failed" and my tablet remained in download mode, didn't boot. Now, I have a tablet that is pretty damn bricked. It will only go to a screen saying "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again" and Download Mode.
I have determined that there is no such firmware for T520nzwaxar, despite being the U.S. model. The only thing I can hope for now is that such a file does exist or another firmware from another country would work.
PLEASE any help that can be given to a frimware that would work with this would be HUGELY appreciated.