Related
Ok, I have done a million searches for this and I keep getting conflicting info. I want to run my Nexus 10 stock and get the OTAs. I have been avoiding CWM because I have always been told/read that it interferes with the OTA and I would not be able to get it. I have been running root on my N10 since I have owned it, but now I just received 4.3 and the only way to get root back is by flashing it with CWM. If I run stock 4.3 with root and CWM, will I be able to still get the OTA? If not, root is more important to me as I can always flash the next update, but I was hoping to just be able to do the OTAs. Anyway, thanks for any info on this!!!!
Hello everyone-
New user for the Samsung Galaxy S4 here. I used to own both the iPhone 3GS and 4S prior. My general background was writing VB in version 3.0 for AOL back in the late 90s for all you old school people, progs/punters that may remember those days. Unfortunately, even now I'm still have issues following along with new technology. So far, I have really enjoyed the android system and have made modifications through various launchers. I did use SuperSU and rooted the phone by the automated process. I realize these may be 'noob' questions, however; everyone I suppose goes through it at some point. I do have some general questions and several of them that I have read about have conflicting information. This will be somewhat long, but I do appreciate any input:
The Galaxy S4 that I have is SPH-L720, MK2, and 4.3 version.
At this point, I backed-up and installed several Google Games, Books, and Sprint ID, Sprint Worldwide, etc.....general bloatware using Titanium Back-up. Again the root method I used was SuperSU by Chainfire. I have NOT use TWRP/Clockwork Mod or flashed any custom ROMs. I just have it rooted and diabled some bloatware, installed Xposed Installer and other root only apps. I checked my phone and its status says 'custom'.
1. Given this set-up, can I still get OTA for new Android versions ? I don't care if it removes root, but I was just wondering if I can get OTA updates to get new versions for my phone. Some threads I have read say yes, others say no. If I cannot, how can I then get new updates ? I don't want to not be able to permanently update to 4.4 in the future. I know there is a way to update via Kies to the computer.
2. The root access via Chainfire SuperSU involves 2 components from what I understand. SU.apk and busybox. I was using Terminal Emulator based on the advice from this thread: http://forum.xda-developers.com/showthread.php?t=2565758
I could not get it to work when typing in the prompts on the screen, it just would not go through. I tried downloading Total Commander which allows root access. Can I instead of using Terminal Emulator to get rid of busybox, use Total Commander to get into the /system/xbin folder and manually delete all busybox files prior to using the permanent unroot of SuperSU feature in settings ? Or does the Full unroot remove everything ?
3. Maybe I still don't understand the flashing process, but it seems, you download Odin, then use the ROM file you need under the PDA selection then start the process while the phone is in download mode (home button, down volume, etc...) Is this how all custom ROMs and re-stores are performed ? Is this form of the restore different that the phone Samsung settings (back-up/restore) ? I've read about TWRP, custom recovery, Clockwork Mod, etc....but I dont understand what all these are. It seems easy enough to download files then put them via Odin then hit start....
At this point, I've refrained from doing anything other than back-up/uninstalling some bloatware and using some cool apps that supposed xposed installer. I'm worried that I might brick my expensive phone or render it unable to get anymore updates :crying:
Thanks for the input !
mikeprius said:
Hello everyone-
New user for the Samsung Galaxy S4 here. I used to own both the iPhone 3GS and 4S prior. My general background was writing VB in version 3.0 for AOL back in the late 90s for all you old school people, progs/punters that may remember those days. Unfortunately, even now I'm still have issues following along with new technology. So far, I have really enjoyed the android system and have made modifications through various launchers. I did use SuperSU and rooted the phone by the automated process. I realize these may be 'noob' questions, however; everyone I suppose goes through it at some point. I do have some general questions and several of them that I have read about have conflicting information. This will be somewhat long, but I do appreciate any input:
The Galaxy S4 that I have is SPH-L720, MK2, and 4.3 version.
At this point, I backed-up and installed several Google Games, Books, and Sprint ID, Sprint Worldwide, etc.....general bloatware using Titanium Back-up. Again the root method I used was SuperSU by Chainfire. I have NOT use TWRP/Clockwork Mod or flashed any custom ROMs. I just have it rooted and diabled some bloatware, installed Xposed Installer and other root only apps. I checked my phone and its status says 'custom'.
1. Given this set-up, can I still get OTA for new Android versions ? I don't care if it removes root, but I was just wondering if I can get OTA updates to get new versions for my phone. Some threads I have read say yes, others say no. If I cannot, how can I then get new updates ? I don't want to not be able to permanently update to 4.4 in the future. I know there is a way to update via Kies to the computer.
2. The root access via Chainfire SuperSU involves 2 components from what I understand. SU.apk and busybox. I was using Terminal Emulator based on the advice from this thread: http://forum.xda-developers.com/showthread.php?t=2565758
I could not get it to work when typing in the prompts on the screen, it just would not go through. I tried downloading Total Commander which allows root access. Can I instead of using Terminal Emulator to get rid of busybox, use Total Commander to get into the /system/xbin folder and manually delete all busybox files prior to using the permanent unroot of SuperSU feature in settings ? Or does the Full unroot remove everything ?
3. Maybe I still don't understand the flashing process, but it seems, you download Odin, then use the ROM file you need under the PDA selection then start the process while the phone is in download mode (home button, down volume, etc...) Is this how all custom ROMs and re-stores are performed ? Is this form of the restore different that the phone Samsung settings (back-up/restore) ? I've read about TWRP, custom recovery, Clockwork Mod, etc....but I dont understand what all these are. It seems easy enough to download files then put them via Odin then hit start....
At this point, I've refrained from doing anything other than back-up/uninstalling some bloatware and using some cool apps that supposed xposed installer. I'm worried that I might brick my expensive phone or render it unable to get anymore updates :crying:
Thanks for the input !
Click to expand...
Click to collapse
I can answer 1 & 3 for you.
1. No, you won't be able to take an OTA because you removed or modified system files. This will cause the update file of the OTA to abort once it encounters the modded file or can't find the file your removed. The best process to take an OTA would be to return the phone to stock before taking the OTA. The easiest method is to use Odin and install the full stock tar file that you are currently on. In your case it would be the MK2 tar file. This will return your phone to stock with the stock recovery and allow your phone to update via OTA, then you can re root.
3. Odin is used to flash things like stock tar files, modems(basebands), recoveries & firmwares. If you are installing a custom rom, that is usually done using a custom recovery like Phillz's or TWRP. These recoveries can be installed via odin or TWRP via goomanager app in playstore. Once the custom recovery is installed you copy the rom file or other mod to your sdcard and install through recovery.
cruise350 said:
I can answer 1 & 3 for you.
1. No, you won't be able to take an OTA because you removed or modified system files. This will cause the update file of the OTA to abort once it encounters the modded file or can't find the file your removed. The best process to take an OTA would be to return the phone to stock before taking the OTA. The easiest method is to use Odin and install the full stock tar file that you are currently on. In your case it would be the MK2 tar file. This will return your phone to stock with the stock recovery and allow your phone to update via OTA, then you can re root.
3. Odin is used to flash things like stock tar files, modems(basebands), recoveries & firmwares. If you are installing a custom rom, that is usually done using a custom recovery like Phillz's or TWRP. These recoveries can be installed via odin or TWRP via goomanager app in playstore. Once the custom recovery is installed you copy the rom file or other mod to your sdcard and install through recovery.
Click to expand...
Click to collapse
Thanks for the response....Does it matter what version of Odin I use if I were to restore the phone back to stock ? Also do I need to manually remove all rooted program and features, or can it be flashed back to stock ROM as is ? I have a lot of apps that I also don't want to lose and I've tried manually back up files on my SD card, but I didn't know if there was a way to back it up, so that it literally can be dumped right back in when stock is restored.
mikeprius said:
Thanks for the response....Does it matter what version of Odin I use if I were to restore the phone back to stock ? Also do I need to manually remove all rooted program and features, or can it be flashed back to stock ROM as is ? I have a lot of apps that I also don't want to lose and I've tried manually back up files on my SD card, but I didn't know if there was a way to back it up, so that it literally can be dumped right back in when stock is restored.
Click to expand...
Click to collapse
I believe if you are on MK2 you will want to use the latest version of odin which is ver3 3.09. If you are using the MK2 complete stock tar file it will rewrite everything in system and restore all the apps that were removed or modded so you don't need to manually remove root. Currently, the stock files available to us do not wipe the data partition so anything you have in that partition will remain there unless you do a factory reset. One thing you will want to make sure you are doing is backing up to the external sdcard and not the internal. You can then use TB to replace any files if you did a factory reset.
cruise350 said:
I believe if you are on MK2 you will want to use the latest version of odin which is ver3 3.09. If you are using the MK2 complete stock tar file it will rewrite everything in system and restore all the apps that were removed or modded so you don't need to manually remove root. Currently, the stock files available to us do not wipe the data partition so anything you have in that partition will remain there unless you do a factory reset. One thing you will want to make sure you are doing is backing up to the external sdcard and not the internal. You can then use TB to replace any files if you did a factory reset.
Click to expand...
Click to collapse
I'm using Kies 3 and using the data back-up feature ? I assume this is backing up to the computer then I was planning on using the 'restore data' feature once they phone is back to stock. Will this revert it back to the way it was previously customized before root ? So if I understand correctly, once I download Odin 3.0, I load the MK2 .tar file into the phone, enbable download mode, then hit start and the phone will be like it was out of the box and ready to be OTA and restored with prior data ? I may be confusing flashing the stock firmware with factory reset ?
I also noticed there is an update firmware feature on Kies 3, if I try using this while SuperSU is present and the phone is rooted, will I also have a failed update/issues ? Again, thanks for your help. Do appreciate it.
mikeprius said:
I'm using Kies 3 and using the data back-up feature ? I assume this is backing up to the computer then I was planning on using the 'restore data' feature once they phone is back to stock. Will this revert it back to the way it was previously customized before root ? So if I understand correctly, once I download Odin 3.0, I load the MK2 .tar file into the phone, enbable download mode, then hit start and the phone will be like it was out of the box and ready to be OTA and restored with prior data ? I may be confusing flashing the stock firmware with factory reset ?
I also noticed there is an update firmware feature on Kies 3, if I try using this while SuperSU is present and the phone is rooted, will I also have a failed update/issues ? Again, thanks for your help. Do appreciate it.
Click to expand...
Click to collapse
I have never used Kies and heard that it doesn't work with the MJA or MK2 software yet. I don't believe Kies will work if your status is custom but I could be wrong on that. If you odin the MK2 full tar file your phone will be back to stock but your data should still be there. You will only lose your data if you do a factory reset in recovery. Remember, a factory reset is just wiping the data partition and does not restore any software or apps.
cruise350 said:
I have never used Kies and heard that it doesn't work with the MJA or MK2 software yet. I don't believe Kies will work if your status is custom but I could be wrong on that. If you odin the MK2 full tar file your phone will be back to stock but your data should still be there. You will only lose your data if you do a factory reset in recovery. Remember, a factory reset is just wiping the data partition and does not restore any software or apps.
Click to expand...
Click to collapse
Ok, I think I have the general idea. It sounds similar to putting back on the stock 'image' nothing else.........I currently have the Odin 3.0 software, but I have been having a hard time finding the stock firmware online and downloading it. I will keep looking. Once I get the .tar and flash in download mode, will I just see all the bloatware back on, but everything else the same ? I was wondering what will happen if I kept Titanium Back-up, SuperSU, and Xposed Installer on when I do this ? Does it just render them all un-useable, but the new OTA will still install anyway ? Thanks.
mikeprius said:
Ok, I think I have the general idea. It sounds similar to putting back on the stock 'image' nothing else.........I currently have the Odin 3.0 software, but I have been having a hard time finding the stock firmware online and downloading it. I will keep looking. Once I get the .tar and flash in download mode, will I just see all the bloatware back on, but everything else the same ? I was wondering what will happen if I kept Titanium Back-up, SuperSU, and Xposed Installer on when I do this ? Does it just render them all un-useable, but the new OTA will still install anyway ? Thanks.
Click to expand...
Click to collapse
Every thing in the data partition(titanium backup) will remain and everything in the system partition (SuperSU & stuff modified via xposed installer) will be gone and replaced with the bloatware.
Sent from my SPH-L720 using Tapatalk
Ok, so it appears to have worked. I flashed the 4.3 prior version however it was hooked up to wifi and automatically downloaded the new version and removed root (not a big deal). My status says custom still, but I am assuming that I can OTA after the flash b/c it updated to the most recent 4.3 in Dec 2013. I re-rooted so it is back to prior, but I know now how to do it.
Is there anything that I may delete or uninstall that cannot be replaced by flashing the stock firmware ? For example I was thinking about getting rid of the 'help' on the phone and Titanium Back up said it is odexed or something to that extent and can only be replaced by using Titanium Backup and the exact same copy ?
I figured that I might as well just try deleting the bloatware and not back up b/c worse case scenario if something happens I can just flash back the stock ROM and all is well ?
Being able to flash the stock .tar through ODIN gives me peace of mind from screw ups, even if it removes root and takes time.
mikeprius said:
I figured that I might as well just try deleting the bloatware and not back up b/c worse case scenario if something happens I can just flash back the stock ROM and all is well ?
Click to expand...
Click to collapse
If you haven't spent much time customizing, that'll work fine. Most of us use custom recoveries (like Philz or TWRP) to make "nandroid" backups of our setups. A nandroid is like a drive image on a computer, so restoring it will restore all of the customizations you've done (accounts, apps, app data, bloatware deletions, etc). Nandroids don't back up firmware (modem, bootloader,etc), but back up the ROM completely. A Titanium backup is almost as good, but requires a bit more work.
As for deciding what apps you can delete, most of the custom ROM creators post a list of the bloatware they remove. So, if it's on their list, it's almost certainly ok to delete it on your phone too.
nobody291 said:
If you haven't spent much time customizing, that'll work fine. Most of us use custom recoveries (like Philz or TWRP) to make "nandroid" backups of our setups. A nandroid is like a drive image on a computer, so restoring it will restore all of the customizations you've done (accounts, apps, app data, bloatware deletions, etc). Nandroids don't back up firmware (modem, bootloader,etc), but back up the ROM completely. A Titanium backup is almost as good, but requires a bit more work.
As for deciding what apps you can delete, most of the custom ROM creators post a list of the bloatware they remove. So, if it's on their list, it's almost certainly ok to delete it on your phone too.
Click to expand...
Click to collapse
Thanks being able to flash the stock .tar and use ODIN gives me peace of mind of any potential screw ups. So far I'm just using stock rom and toggling some of the features with xposed installer and titanium back up.
I'd like to explore more eventually with custom ROMs and I've heard of Clockwork mod and TWRP, Nandroid, Cyanogen, etc... but I don't know what any of that means or what it is.
Is TWRP/Philz like ODIN program then you download custom ROMS like Cyanogen the same way as the stock firmware. tar ?
As you can tell I am extremely new to this.....this is also my first time owning an Android phone as well, but I never messed with jailbreaking my past 2 iPhones in the past. I just have used VB 3.0 back in the day....
mikeprius said:
Thanks being able to flash the stock .tar and use ODIN gives me peace of mind of any potential screw ups. So far I'm just using stock rom and toggling some of the features with xposed installer and titanium back up.
I'd like to explore more eventually with custom ROMs and I've heard of Clockwork mod and TWRP, Nandroid, Cyanogen, etc... but I don't know what any of that means or what it is.
Is TWRP/Philz like ODIN program then you download custom ROMS like Cyanogen the same way as the stock firmware. tar ?
As you can tell I am extremely new to this.....this is also my first time owning an Android phone as well, but I never messed with jailbreaking my past 2 iPhones in the past. I just have used VB 3.0 back in the day....
Click to expand...
Click to collapse
To me, one of the hardest parts of this whole thing is getting to the point where the basic terms make sense. I've been at this for a couple of years with an HTC Evo and now the GS4 since October, and sometimes it still makes my head spin. Here is an attempt to explain my understanding of a few things:
1. Booting...you can boot into Download mode, recovery, or system. Download mode is what you use with ODIN, you need the correct drivers on your computer (which can be found lots of places), so that ODIN and your phone can communicate. In download mode, the phone just accepts whatever ODIN sends it, so it's the easiest way to totally brick your phone. Don't mess with partitions and follow the instructions for whatever you're doing very carefully, because I think this is the only way to "hard brick" your phone.
2. Recovery - something you use to create images of your phone's ROM (nandroids), flash ROMs and mods, and restore past nandroids. The stock recovery will only flash approved updates from the carrier, so to do any of the things I listed you need a custom recovery. Most people use Philz (which is based on the ClockworkMod recovery) or TWRP. To flash the custom recovery, use ODIN and follow the instructions in the thread exactly. There is a way to flash recoveries without ODIN, but I've never done it. I was using TWRP, and switched to Philz to flash the rooted stock 4.3 update because the thread suggested it. They both seem to do the same thing, and I have been happy with both. I'm sure there are technical differences, but I couldn't explain what they are. You can switch back and forth as much as you'd like between the recoveries with ODIN. Recoveries can flash a complete ROM or just partial changes (like the hotspot mod). In a custom recovery (or the stock) you can also do factory resets and cache cleaning (most ROMs suggest you do this before flashing). Factory reset doesn't return the ROM to the factory original, it just clears out all of the user data (including user apps). A nandroid is the fastest way to restore a phone if you screw it up...I always make one before making significant changes to the phone. It takes several minutes to do, but I think it's well worth it. The operating system can't be running when you make one, that's why you need to boot into recovery mode. You create a Nandroid in Philz by selecting "backup and restore" then "backup to" which will allow backup to the internal storage or external SD card.
3. ROM - the actual operating system used by the phone when you actually use it as a smartphone. There are 2 basic flavors for the GS4...touchwiz and AOSP (Android Open Source Project). Touchwiz is Samsung's "flavor" of Android, AOSP is the "pure Google" version of Android. A lot of the things the GS4 will do rely on touchwiz (multiwindow is one example...but there are several). Some people really like the AOSP ROMs (Cyanogen is AOSP), but make sure you understand their limitations. I've never used one on the GS4. There are several touchwiz custom ROMs which have various features. I've tried a few and just settled on the stock rooted touchwiz ROM, but there are lots of options from great developers. I think most custom ROMs require you to use a custom recovery to flash them, but there might be ways to do it using ODIN. I like having a custom recovery, so I've only used ODIN for flashing modems and recoveries.
4. Firmware - as far as I can tell, there are two important parts of the firmware...the modem (sometimes called "radios" or "baseband"...find your version by looking in "about device"->"Baseband version"...the different modems are described by the last 3 letters you see) and the bootloader. The modem and the version of the ROM you flash need to match or you'll have problems with the radios in the phone (wifi seems to be the biggest problem if you have a mismatch). MF9 was the last modem version based on 4.2.2, and 4.3 has had MJA and MK2 (MK2 is the latest). The bootloader is what the phone uses to initially decide how to boot up. If you have the 4.3 version of the bootloader it will include "Knox", which will prevent you from flashing older versions of the modem, so you'll have to use a 4.3 ROM. Knox also "trips" a counter if you flash a custom ROM and Samsung claims they won't honor the warranty on a phone with the "Knox flag" tripped. If you have the 4.3 bootloader you're stuck with it (for now at least). I still have the 4.2.2 bootloader, so I don't have much more to offer on this subject. There are ways to get the 4.3 modem and ROM without the 4.3 bootloader. There is a lot here (and lots on youtube) on how to navigate the Knox minefield if you care about it. If you still have the 4.2.2 bootloader you can flash older (and newer) modems as much as you'd like without getting the updated bootloader using ODIN.
Hopefully this helps...this is a great place with lots of great people. Sometimes the scale of the amount of information here is overwhelming. But, search is your friend along with lots of time! Feel free to keep asking questions.
thanks for explaining this nobody-
The information does help quite a bit and I am still learning, however; I do enjoy the process of messing with the phone. My GS4 now runs the RAM at 750-800mg instead of a bloated 1.2GB which was happening quite a bit. I had to originally not use a lot of apps I wanted to like Facebook bc the programs themselves bloated up to accomidate the existing bloatware which was also running. I did flash my phone back with the stock firmware today and it looks like it installed all the stock software. My status said 'custom' when I looked at it however I was already connected to wifi and it went from 4.3 (Oct 2013 version which I flashed) to Dec 2013 version automatically so it appears that the OTA feature works.
I assumed if I accidently delete something from the phone that I really need to affects the phone, I can always flash the stock ROM to fix it. Losing the root is not that big of an issue, but I did lose Superuser and had to re-root the phone. I suppose I do have a few more questions, one was when I was reading another carrier provider thread.
1. Is there anything I can delete from the phone that I could not eventually recover by flashing the stock firmware ? When I uninstall for example the 'help' app on the phone Titanium Backup says this only copy can be replaced by using Titanium 5.1 and it's existing copy ? Could this just be replaced by flashing the stock firmware as well ? I like being able to flash the stockfirm ware rom at any point as a fail safe.
2. The other issue is the bootloader that I heard about ? It was on a Verizon thread where the person was able to flash the stock firmware on his phone, but then after an upgrade, he was not longer able to flash the rom b/c the carrier in the most recent upgrade he did blocked ODIN ? Is this something that I should possibly be concerned about in the future not being able to flash stock firmware via ODIN ? As you can tell, I'm pretty OCD about being able to have a failsafe for my phone. LOL. Thanks again for your help, I do appreciate it.
mikeprius said:
1. Is there anything I can delete from the phone that I could not eventually recover by flashing the stock firmware ? When I uninstall for example the 'help' app on the phone Titanium Backup says this only copy can be replaced by using Titanium 5.1 and it's existing copy ? Could this just be replaced by flashing the stock firmware as well ? I like being able to flash the stockfirm ware rom at any point as a fail safe.
Click to expand...
Click to collapse
Yes, you can always flash the stock firmware to fix whatever you do to the ROM (just to the ROM, use ODIN very carefully). In the case of the Help file, you could also back it up using Titanium, then delete the app, and restore it later using Titanium if you want it back. This is probably obvious, but use Titanium to delete the app, but don't delete the backup.
2. The other issue is the bootloader that I heard about ? It was on a Verizon thread where the person was able to flash the stock firmware on his phone, but then after an upgrade, he was not longer able to flash the rom b/c the carrier in the most recent upgrade he did blocked ODIN ? Is this something that I should possibly be concerned about in the future not being able to flash stock firmware via ODIN ? As you can tell, I'm pretty OCD about being able to have a failsafe for my phone. LOL. Thanks again for your help, I do appreciate it.
Click to expand...
Click to collapse
Sprint is a lot more friendly toward its users modifying their phones than Verizon. But, they could change their minds any time. For now, there are no issues (other than the Knox warranty issue). But, don't presume that'll always be the case. The best precaution is to not take OTA (over the air) updates. OTAs are the ones that pop up as a notification on the phone saying "system update available, tap to install". Kit Kat should become available in the next month or two, who knows what'll come along with the OTA. Threads will start here almost immediately when the update rolls out; watch those threads and don't do the update until you're comfortable with what's inside. I will wait and flash something from the development section, even if it is just the stock ROM.
nobody291 said:
Yes, you can always flash the stock firmware to fix whatever you do to the ROM (just to the ROM, use ODIN very carefully). In the case of the Help file, you could also back it up using Titanium, then delete the app, and restore it later using Titanium if you want it back. This is probably obvious, but use Titanium to delete the app, but don't delete the backup.
Sprint is a lot more friendly toward its users modifying their phones than Verizon. But, they could change their minds any time. For now, there are no issues (other than the Knox warranty issue). But, don't presume that'll always be the case. The best precaution is to not take OTA (over the air) updates. OTAs are the ones that pop up as a notification on the phone saying "system update available, tap to install". Kit Kat should become available in the next month or two, who knows what'll come along with the OTA. Threads will start here almost immediately when the update rolls out; watch those threads and don't do the update until you're comfortable with what's inside. I will wait and flash something from the development section, even if it is just the stock ROM.
Click to expand...
Click to collapse
It was good that you mentioned the Knox bootloader issue with the 4.3 upgrade. When I purchased my cell phone back in Nov, I believe it had the 4.3 (1st) version loaded, but it already had Knox features as I do recall seeing them. If I were to try and flash 4.2.2 like the version you initially had, would the phone have a bootloop error or fail to flash because there were some free wifi tethering exploits that were not yet fixed in the 4.2.2 version ? This may have been the error I read about due to the new Knox feature.
I think since my phone is currently rooted and I altered some of the bloatware system files that the update if it were made available OTA should not update anyway due to the root. Will the stock ROM/firmware .tar files eventually be posted in the developers section that can just be flashed via ODIN later on ? With that, if I were to load 4.4 and not like it, could I flash back 4.3 ? I am guessing this is the part where you mentioned that the carrier may decide differently later on.....I suppose I will just keep an eye out in the meantime.
Good good............, I'm picking up this pretty well so far.............
mikeprius said:
If I were to try and flash 4.2.2 like the version you initially had, would the phone have a bootloop error or fail to flash because there were some free wifi tethering exploits that were not yet fixed in the 4.2.2 version ?
Click to expand...
Click to collapse
I'm not sure what symptoms you'd see if you installed 4.2.2 with the 4.3 bootloader. Most likely the phone would fail to boot. ODIN will flash whatever you tell it to, I don't believe it does any compatibility checking on its own. You can still get the wifi hotspot feature to work even with Knox and the 4.3 bootloader, I don't think that was what they were trying to do with the update. There are threads discussing 4.3 and what changed, but there wasn't much obvious to the user. For now you can't go back if you're on 4.3, but there might be an exploit discovered down the road that lets you get the old bootloader and go back.
Will the stock ROM/firmware .tar files eventually be posted in the developers section that can just be flashed via ODIN later on ?
Click to expand...
Click to collapse
Yes, they won't be available immediately though. It can take some time for the community to re-obtain root too, depending on how big the changes are.
With that, if I were to load 4.4 and not like it, could I flash back 4.3 ?
Click to expand...
Click to collapse
I think you alluded to the answer already, but it depends. It took a month or two before you could flash the stock 4.3 without the 4.3 bootloader. There were custom ROMs available that used custom kernels sooner, but there was a problem trying to use the stock kernel with the 4.2.2 bootloader. So, always read and read and read some more before flashing updates.
So far i think i got the hang of it. I have been modifying the phones original touchwhiz. I ended up freezing alot of files instead of deleting them so the ability to turn them back on is there. Some of the files while there are not meant to be frozen/disabled/turned off. I tried a few methods for keeping SuperSU over an ODIN with no luck. I do have a question though. If i turned off (but did not delete) alot of system files and were to run ODIN again will all of them including the bloatware be turned back on and restored? That would be bad if i flashed, lost root, then simultaneously had all the system files disabled with no way to turn them back on......
This also a dumb question but what exactly am i flashing with ODIN? Its a 1.5 GB file with Sprint and it is a tar that restores all bloatware and turns the phone status back to official so i can get OTA updates. Am i flashing the entire stock ROM or just the firmware? Its nice that i have not lost any existing apps or data. It just restores the bloatware and removes root
Reading the above posts im guessing firmware....along the lines of the previous question will this restore system files and apps as well that have been shut off because ive been on a roll disabling and freezing a lot of files and apps and not sure what to turn back on to restore function to some of them. If the ODIN firmware flash resets all settings then that will also be very useful as well. Thanks much
mikeprius said:
Reading the above posts im guessing firmware....along the lines of the previous question will this restore system files and apps as well that have been shut off because ive been on a roll disabling and freezing a lot of files and apps and not sure what to turn back on to restore function to some of them. If the ODIN firmware flash resets all settings then that will also be very useful as well. Thanks much
Click to expand...
Click to collapse
The .tar you are flashing from sprint is what we would call stock firmware image. This is the image that shipped on the phone from the factory. I'm an avid flasher and would highly recommend installing twrp or philz touch, creating a nandroid backup and giving some debloated touchwiz roms a shot. You'll see some significant improvement in battery life and performance and some really cool upstream features. I use odin as a last resort, when I need to go back to stock for whatever reason (ie domestic sim unlock) or have fubar'd my current setup past a point of no return.
I recently upgraded my phone from a SGS2 i777 to the SGS4 i337. Of course after years of custom ROMs and kernels on the S2 I wanted to do the same on the S4. I attempted to perform the hack associated with the Loki exploit while running stock Mk2. After trying several methods and receiving the failure to root message I gave up and decided stock wasn't that bad and I could make do. I noticed that even after these attempts failed either Super User or Super sure would be installed. Sadly the super su binary needed to be updated but it never actually updated. I also noticed that I was getting the custom boot screen but no real root. Anyway I looked around the Web and xda for a solution, either a way to gain full root or to reset back to full stock. I was interested in trying some of samsung's apps as well as At&t's Isis wallet so I decided to try to unroot and "play by the rules" for a little while before I started using custom roms. I read in several places that a firmware update removes root (as well as patches the exploit) but I decided it was the easiest way to "unroot" because I didn't have any root privileges which of course were needed to unroot if I used any guide online. After an ota update from 4.2.2 MK2 firmware to 4.4 NB1 is still have the custom boot screen and Is is still things my phone is rooted and therefore will not run. Some how I have enough root to trip the custom screen and stop Isis but not enough root to unroot. Does anyone have a solution to bring my phone back to full stock without root in such a way that I don't lose or can reinstall samsung's app and a few if At&t's ? All relatively safe suggestions welcome. Thanks for taking the time to read and any help.
Since youre on nb1 now, download a copy of the stock nb1 rom and download odin v3.09. right click on odin and run as administrator. Boot your phone into download mode by turning it on holding volume down, power, and the home buttkn. Plug your phone in and odin should say <added!>. Load the stock rom on the pda slot then hit start. Your phone should reset as a 100% stock phone with the custom splash gone.
Sent from my SGH-I337 using XDA Premium 4 mobile app
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!