Related
Hi everyone, I have about 7 days left on my "14 day return policy" from the Sprint store. I love XDA and it's been a HUGE help to me in the last few years. I like the phone, it's pretty snappy, and the camera is great. But I can't use a phone without root (who can??) and eventually Samsung will stop pushing updates to this phone so I'm going to need to flash custom ROMs (cyanogenmod did wonders on my last phone, the Galaxy S1). I also know that I can't mount SMB or CFS shares without flashing a kernel that supports it and I'm not sure if the S4's official firmware supports the ability to do so (which I believe requires root anyway, so I guess I answered my own question.
I have a couple of questions about the S4 that I'm hoping someone who has experience can tell me about this.
1) Can I root using VRoot and NOT trip the Knox warranty bit?
2) After rooting, can I install a recovery (I've read that Philz CWM recovery works but can't find definitive answers on this).
3) Should I even care about the Knox software?
I don't need to use the phone in an enterprise environment, but I also don't want the phone's bootloader locked to Samsung firmwares if it means I won't be able to install custom FW's or kernels.
Should I return the phone? I'll pay the $35 restocking fee just to save myself from having to deal with Samsung's (and this my opinion) bonehead move of abandoning its developer userbase.
Any and all responses would be appreciated. Thanks for reading and helping!
epi4gtn said:
Hi everyone, I have about 7 days left on my "14 day return policy" from the Sprint store. I love XDA and it's been a HUGE help to me in the last few years. I like the phone, it's pretty snappy, and the camera is great. But I can't use a phone without root (who can??) and eventually Samsung will stop pushing updates to this phone so I'm going to need to flash custom ROMs (cyanogenmod did wonders on my last phone, the Galaxy S1). I also know that I can't mount SMB or CFS shares without flashing a kernel that supports it and I'm not sure if the S4's official firmware supports the ability to do so (which I believe requires root anyway, so I guess I answered my own question.
I have a couple of questions about the S4 that I'm hoping someone who has experience can tell me about this.
1) Can I root using VRoot and NOT trip the Knox warranty bit?
2) After rooting, can I install a recovery (I've read that Philz CWM recovery works but can't find definitive answers on this).
3) Should I even care about the Knox software?
I don't need to use the phone in an enterprise environment, but I also don't want the phone's bootloader locked to Samsung firmwares if it means I won't be able to install custom FW's or kernels.
Should I return the phone? I'll pay the $35 restocking fee just to save myself from having to deal with Samsung's (and this my opinion) bonehead move of abandoning its developer userbase.
Any and all responses would be appreciated. Thanks for reading and helping!
Click to expand...
Click to collapse
I am not worried about the Knox bit. Mine is tripped and it's not preventing anything, AFAIK. I can still install Sammy firmwares, ROM's that are at the correct version/level, mods, apps, etc. It seems it's really only a flag for enterprise users. I agree it kind of sucks, and I'm not a fan of it, but it doesn't seem to be causing any real harm at this point warranty or service wise. Some say it may prevent Samsung from honoring the warranty, but I'm not sure that's true, based on reading the forums.
As far as Samsung stopping pushing firmwares to this phone, that should be a long way off since this is their flagship smartphone at this point. It's a great phone and I've been very happy with mine, which I got the weekend they were released. Rooted, stock rom, hotspot mod. So much better phone than my old HTC Androids!
jejb said:
I am not worried about the Knox bit. Mine is tripped and it's not preventing anything, AFAIK. I can still install Sammy firmwares, ROM's that are at the correct version/level, mods, apps, etc. It seems it's really only a flag for enterprise users. I agree it kind of sucks, and I'm not a fan of it, but it doesn't seem to be causing any real harm at this point warranty or service wise. Some say it may prevent Samsung from honoring the warranty, but I'm not sure that's true, based on reading the forums.
As far as Samsung stopping pushing firmwares to this phone, that should be a long way off since this is their flagship smartphone at this point. It's a great phone and I've been very happy with mine, which I got the weekend they were released. Rooted, stock rom, hotspot mod. So much better phone than my old HTC Androids!
Click to expand...
Click to collapse
This is just a thought... but... check your phone, when I got mine not too long back it still came with 4.2 on it. If yours still has 4.2 you wouldn't have to worry about knox as long as you didn't take the OTA. You could root it and rom it all you wanted.
Yes you should return the phone. That way you **** all the people who return their phones for legitimate warranty/insurance reasons with higher costs.
Sent from my SPH-L720 using Tapatalk
frostedunit said:
Yes you should return the phone. That way you **** all the people who return their phones for legitimate warranty/insurance reasons with higher costs.
Sent from my SPH-L720 using Tapatalk
Click to expand...
Click to collapse
I haven't done any type of rooting or modification to the phone yet. That's the reason I'm asking, I haven't tripped the counter. I'm just aggravated by not having root and being able to remove this crapware. I wouldn't be ****ing anyone. Please don't be a ****.
jejb said:
I am not worried about the Knox bit. Mine is tripped and it's not preventing anything, AFAIK. I can still install Sammy firmwares, ROM's that are at the correct version/level, mods, apps, etc. It seems it's really only a flag for enterprise users. I agree it kind of sucks, and I'm not a fan of it, but it doesn't seem to be causing any real harm at this point warranty or service wise. Some say it may prevent Samsung from honoring the warranty, but I'm not sure that's true, based on reading the forums.
As far as Samsung stopping pushing firmwares to this phone, that should be a long way off since this is their flagship smartphone at this point. It's a great phone and I've been very happy with mine, which I got the weekend they were released. Rooted, stock rom, hotspot mod. So much better phone than my old HTC Androids!
Click to expand...
Click to collapse
This is great news, can you point me to the tool you used to root the phone? I've read the Chinese VRoot method doesn't trip the counter, but installs "Superuser" which can subsequently be removed and replaced with SuperSU. I think using SuperSU and something like DroidWall to monitor the device to make sure nothing fishy is going on will help us determine whether or not VRoot is really malware (I've read comments saying that it's some kind of spyware but I'm not sure of the technical prowess of those commenters).
What recovery are you using to flash custom ROMs?
And as asked in a previous post-- Did you root before taking the OTA? Or did you take the OTA and do you see the Knox Warranty Bit marked as 0x1 in the stock recovery?
Thanks for the replies, appreciate all the info guys!
epi4gtn said:
I haven't done any type of rooting or modification to the phone yet. That's the reason I'm asking, I haven't tripped the counter. I'm just aggravated by not having root and being able to remove this crapware. I wouldn't be ****ing anyone. Please don't be a ****.
This is great news, can you point me to the tool you used to root the phone? I've read the Chinese VRoot method doesn't trip the counter, but installs "Superuser" which can subsequently be removed and replaced with SuperSU. I think using SuperSU and something like DroidWall to monitor the device to make sure nothing fishy is going on will help us determine whether or not VRoot is really malware (I've read comments saying that it's some kind of spyware but I'm not sure of the technical prowess of those commenters).
What recovery are you using to flash custom ROMs?
And as asked in a previous post-- Did you root before taking the OTA? Or did you take the OTA and do you see the Knox Warranty Bit marked as 0x1 in the stock recovery?
Thanks for the replies, appreciate all the info guys![/QUOTE
I used an app from thePlayStore called Triangle Away to reset the counter. You have to be rooted, but it works perfectly. Just an FYI.
Click to expand...
Click to collapse
epi4gtn said:
I haven't done any type of rooting or modification to the phone yet. That's the reason I'm asking, I haven't tripped the counter. I'm just aggravated by not having root and being able to remove this crapware. I wouldn't be ****ing anyone. Please don't be a ****.
This is great news, can you point me to the tool you used to root the phone? I've read the Chinese VRoot method doesn't trip the counter, but installs "Superuser" which can subsequently be removed and replaced with SuperSU. I think using SuperSU and something like DroidWall to monitor the device to make sure nothing fishy is going on will help us determine whether or not VRoot is really malware (I've read comments saying that it's some kind of spyware but I'm not sure of the technical prowess of those commenters).
What recovery are you using to flash custom ROMs?
And as asked in a previous post-- Did you root before taking the OTA? Or did you take the OTA and do you see the Knox Warranty Bit marked as 0x1 in the stock recovery?
Thanks for the replies, appreciate all the info guys!
Click to expand...
Click to collapse
Dont use vroot. Until some dev can pin point what the chinese root method actually does. And if your on 4.2.2 your ok but once ota to 4.3 then you have knox bootloader meaning you cant downgrade firmwares. It wont stop you from changing kernels and roms. Knox flag just voids your warranty with samsung but if you have insurance with sprint they can care less about it tripped. I updated to 4.3 and tripped the knox amd I havent seen no problems really. Btw please make research this has been talked about lately too much.
SoFaKiNgStOkeD said:
epi4gtn said:
I haven't done any type of rooting or modification to the phone yet. That's the reason I'm asking, I haven't tripped the counter. I'm just aggravated by not having root and being able to remove this crapware. I wouldn't be ****ing anyone. Please don't be a ****.
This is great news, can you point me to the tool you used to root the phone? I've read the Chinese VRoot method doesn't trip the counter, but installs "Superuser" which can subsequently be removed and replaced with SuperSU. I think using SuperSU and something like DroidWall to monitor the device to make sure nothing fishy is going on will help us determine whether or not VRoot is really malware (I've read comments saying that it's some kind of spyware but I'm not sure of the technical prowess of those commenters).
What recovery are you using to flash custom ROMs?
And as asked in a previous post-- Did you root before taking the OTA? Or did you take the OTA and do you see the Knox Warranty Bit marked as 0x1 in the stock recovery?
Thanks for the replies, appreciate all the info guys![/QUOTE
I used an app from thePlayStore called Triangle Away to reset the counter. You have to be rooted, but it works perfectly. Just an FYI.
Click to expand...
Click to collapse
That only works if your on 4.2. It wont reset the knox bootloader counter.
Sent from my SPH-L720 using xda app-developers app
Click to expand...
Click to collapse
epi4gtn said:
This is great news, can you point me to the tool you used to root the phone? I've read the Chinese VRoot method doesn't trip the counter, but installs "Superuser" which can subsequently be removed and replaced with SuperSU. I think using SuperSU and something like DroidWall to monitor the device to make sure nothing fishy is going on will help us determine whether or not VRoot is really malware (I've read comments saying that it's some kind of spyware but I'm not sure of the technical prowess of those commenters).
What recovery are you using to flash custom ROMs?
And as asked in a previous post-- Did you root before taking the OTA? Or did you take the OTA and do you see the Knox Warranty Bit marked as 0x1 in the stock recovery?
Thanks for the replies, appreciate all the info guys!
Click to expand...
Click to collapse
Yes, my Knox bit it tripped/set. It is 0x1 on the download screen. Can't view it in recovery. I just used CF Auto Root after going to 4.3. Should be easy to search and find that thread. I'm on the stock rom with tweaks.
Using TWRP recovery, but I've tried several, including Philz and OUDHS. It seems Philz is the flavor of the month, so you might want to go with that just to be safe.
I did not root before taking the OTA. I don't think I'd try it that way. I was rooted, but went back to stock to take the update. If you get back to stock, reset the custom bits on your download screen (triangle away and RTN's seem to do that, but might have to do more than one), recover your apps/data and then take the OTA, it should be the most sure fire method. Then root, custom recovery, nandroid backup and play from there.
jejb said:
Yes, my Knox bit it tripped/set. It is 0x1 on the download screen. Can't view it in recovery. I just used CF Auto Root after going to 4.3. Should be easy to search and find that thread. I'm on the stock rom with tweaks.
Using TWRP recovery, but I've tried several, including Philz and OUDHS. It seems Philz is the flavor of the month, so you might want to go with that just to be safe.
I did not root before taking the OTA. I don't think I'd try it that way. I was rooted, but went back to stock to take the update. If you get back to stock, reset the custom bits on your download screen (triangle away and RTN's seem to do that, but might have to do more than one), recover your apps/data and then take the OTA, it should be the most sure fire method. Then root, custom recovery, nandroid backup and play from there.
Click to expand...
Click to collapse
Thank you, I plan to just use CF-Auto-Root to root the phone. I'm starting to care less about the Knox bit getting tripped.
I came across this post by rawintellect that seems to have everything I'd need out of the phone, rooted/deodexed MK2 with all the bloat removed, BUT it says in the description that the Knox Bootloader is removed *EDIT: After thinking about the statement some more, I think he means the Knox bootloader is NOT included in the rom, but this raises another question, can I install it on a phone WITH the knox bootloader?), so I'm afraid of attempting to flash it because as I understand it, it's impossible to replace the knox bootloader.
Here's the post: http://forum.xda-developers.com/showpost.php?p=48516106
This individual seems to have gotten everything working: http://forum.xda-developers.com/showpost.php?p=48516106&postcount=88
Do you know if anyone is able to flash Philz through Odin successfully on the MJA/knox bootloader?
I took mine back after I took the OTA. I was honest about why I was returning it, that the firmware introduces restrictions and annoying features (I cited the multiple WiFi security warnings in particular) I was not willing to accept, and the independent store I was dealing with gave me an exchange to a new phone with 4.2. I first asked if they could downgrade the phone to 4.2, including the bootloader, they researched that option, finding it impossible.
If they had not given me the exchange, I would have picked a different color and done it that way.
Try this Guide
http://forum.xda-developers.com/showthread.php?t=2572000
MrTasselhof
Hi everyone,
I am going to purchase a Note 3 the next week (probably Vodafone Australia) and would be interested to know if there is a way to prevent the upgrade from 4.3 JB to 4.4 KK?! More specifically on an unrooted phone...
One of the main reasons is the App permission manager in 4.3 that would allow to restrict apps on an unrooted phone -
and I would prefer to keep it unrooted (The only reason for me to root a phone would be to restrict app permissions, but with 4.3 that seems to be unnecessary, so why risk tripping Knox).
I know one could turn off the notifications for the Google Framework Services,to stop the nagging reminders, but this only would delay the upgrade, not prevent it afaik.
So maybe there is a way using the App permission manager in 4.3 or something else?
Any help is greatly appreciated -
Many thanks in advance :cyclops:
On an uprooted phone...not that I know of. On a rooted phone, it's a piece of cake...just rename one file.
Sent from my Note 3 via Tapatalk
grovin said:
Hi everyone,
I am going to purchase a Note 3 the next week (probably Vodafone Australia) and would be interested to know if there is a way to prevent the upgrade from 4.3 JB to 4.4 KK?! More specifically on an unrooted phone...
One of the main reasons is the App permission manager in 4.3 that would allow to restrict apps on an unrooted phone -
and I would prefer to keep it unrooted (The only reason for me to root a phone would be to restrict app permissions, but with 4.3 that seems to be unnecessary, so why risk tripping Knox).
I know one could turn off the notifications for the Google Framework Services,to stop the nagging reminders, but this only would delay the upgrade, not prevent it afaik.
So maybe there is a way using the App permission manager in 4.3 or something else?
Any help is greatly appreciated -
Many thanks in advance :cyclops:
Click to expand...
Click to collapse
First you must take into account that very latest models might at some point come directly with 4.4.2.
If the phone is on 4.3 as far as I know you need to reject the licence agreement on the updates - when you first start your phone after initial steps it will show a notification on software updates, will make you choose a country and ask to agree to the license - if you say NO you will get no OS upgrade.
If you are also on one of early firmware versions like MI7 (where you can root with URDLV) you also need to disable the security updates.
Hi there -
Thanks a lot for all your answers!
Declining the license terms doesn#t sound too bad - would it have any other disadvantages if one does so?
Cheers,
grovin
Ok, i just got my samsung galaxy s5 a week ago. And yesterday i checked for an update and there was one and i downloaded it and installed it. The update said it improved software stability on the s5. I have the t-mobile version and after i intstalled the update i found out that geohot released a root for the device :| . what im afraid of is that this update fixed the exploit the root is using or, this update will detect whether i root the device or now and knox will be tripped. does anyone else know anything about this update that was sent out by t-mobile yesterday?
KERNAL version
3.4.0-1616466
Fri May 23 20:25:39 KST 2014
Build Number
KOT49H.G900TUVU1ANE6
SE for Android Status
Enforcing
SEPF_SM-G900T_4.4.2_0016
Fri May 23 20:25:18 2014
Security software version
MDF v1.0 release 3
VPN v1.4 Release 1
nightlyshade said:
Ok, i just got my samsung galaxy s5 a week ago. And yesterday i checked for an update and there was one and i downloaded it and installed it. The update said it improved software stability on the s5. I have the t-mobile version and after i intstalled the update i found out that geohot released a root for the device :| . what im afraid of is that this update fixed the exploit the root is using or, this update will detect whether i root the device or now and knox will be tripped. does anyone else know anything about this update that was sent out by t-mobile yesterday?
KERNAL version
3.4.0-1616466
Fri May 23 20:25:39 KST 2014
Build Number
KOT49H.G900TUVU1ANE6
SE for Android Status
Enforcing
SEPF_SM-G900T_4.4.2_0016
Fri May 23 20:25:18 2014
Security software version
MDF v1.0 release 3
VPN v1.4 Release 1
Click to expand...
Click to collapse
Try Towelroot, it is confirmed working on the S5 and it doesn`t trip KNOX. Link http://towelroot.com/ and click the Lambda from the phones browser and follow instructions.
+1 on towelroot. Works fast and nothing negative can happen if you mess up. I'm talking about the rooting process that is. Hit one button and done. If it's not compatible it just won't root
Sent to you from my slimmed down S5
your KNOX will trigger only if you install CUSTOM RECOVERY or CUSTOM KERNEL. and the safest method that I KNOW to root without triggering KNOX is TOWEL ROOT as described by our 2 good member in your thread.
rooting makes private mode useless
Towel Root is your best bet, like Chaintanyapatel8880 said the only time Knox will trigger is flashing a custom recovery or rom. I think the only rom you can flash that won't trigger it is the alliance rom in the tmobile section since there is an option to flash it through Odin.
Sent from my SM-G900T using XDA Premium 4 mobile app
nightlyshade said:
Ok, i just got my samsung galaxy s5 a week ago. And yesterday i checked for an update and there was one and i downloaded it and installed it. The update said it improved software stability on the s5. I have the t-mobile version and after i intstalled the update i found out that geohot released a root for the device :| . what im afraid of is that this update fixed the exploit the root is using or, this update will detect whether i root the device or now and knox will be tripped. does anyone else know anything about this update that was sent out by t-mobile yesterday?
KERNAL version
3.4.0-1616466
Fri May 23 20:25:39 KST 2014
Build Number
KOT49H.G900TUVU1ANE6
SE for Android Status
Enforcing
SEPF_SM-G900T_4.4.2_0016
Fri May 23 20:25:18 2014
Security software version
MDF v1.0 release 3
VPN v1.4 Release 1
Click to expand...
Click to collapse
Reiterating from my personal experience. T-Mo G900t KOT49H.G900TUVU1ANE6
I recently sent back a knox tripped back for battery issues, the battery life was horrid. Freaking Android system. (No problemas)
After trying towelroot i'm rooted with stock rom, Make sure to do these things when you do root, Disable ServiceIQ (Find in search) and start looking into making modifications via system tuner but don't do the one click partition stuff that improves stuff for you, that will earn you a factory reset and a whole lot of force closes. =)
Since i've rooted i've had no issues with installing Xposed, BusyBox and all the other goodies that rooting comes with but remember, if you do install a new rom which usually requires a new recovery you WILL trip knox :cyclops: (Correct me if i'm wrong)
I can't tell you how many times i've factory reset and rentered in my credentials but i'm loving titanium backup now.
Stay stock and modify, but don't touch bootloader or recovery
I'd love to get back to Alliance rom or Omega, but I want the radio updates until stuff is ironed out or knox is beaten. I made the mistake of rooting the first day and was stuck with the ANCH baseband and couldn't do anything about it and when you trip your knox you say byebye to radio and modem updates until the higher ups figure things out.
I'm not new to flashing ROMs, but I am new to flashing them for the S5. What is it with this KNOX thing that everyone keeps talking about? Why is it so dangerous? Is that the reason modding for the S5 seems to be at a standstill?
Luuthian said:
I'm not new to flashing ROMs, but I am new to flashing them for the S5. What is it with this KNOX thing that everyone keeps talking about? Why is it so dangerous? Is that the reason modding for the S5 seems to be at a standstill?
Click to expand...
Click to collapse
KNOX is advanced security. Before if the binary counter goes custom we can use triangle away and reset the counter which will set the phone for the warranty but in case of KNOX, there is no way we can reset once it becomes 0x1. and the warranty is gone... there is no way as of yet to reset it... it can become 0x1 if you flash custom recovery and or custom kernel but if you use TOWEL ROOT by GEOHOT, knox will not change. I have tried personally...
Ah, okay. So you can actually easily flash the S5 (well, as much as any other locked phone) but people don't want to lose their warranty...
Doesn't seem like the worst trade-off to me though. If a Google Play edition of the device hits, I would gladly flash my device to a stock Android 5.0 ROM on the S5.
Luuthian said:
Ah, okay. So you can actually easily flash the S5 (well, as much as any other locked phone) but people don't want to lose their warranty...
Doesn't seem like the worst trade-off to me though. If a Google Play edition of the device hits, I would gladly flash my device to a stock Android 5.0 ROM on the S5.
Click to expand...
Click to collapse
Actually It is a golden deal even if we loose warranty. rooting and custom recovery unlocks tons of features. It's like heaven for smartphone...
Luuthian said:
Is that the reason modding for the S5 seems to be at a standstill?
Click to expand...
Click to collapse
Urghhh if I read another statement like that I'm gonna scream! Modding is NOT at a standstill!! Why do so many people use these sweeping statements just because they can't have a fully working non Samsung based Rom. Modding is very much on the move for Samsung based roms. If you are waiting for fully working non Samsung you may as well have bought a N5 as by not using Samsung software you lose a hell of a lot of what makes an s5 and s5! Buy a nexus... Save some money and be happy
Sent from my SM-G900F using Tapatalk
towerlroot worked here without messing up knox.
this is my first smartphone I was worried too -- ecspecially because I have insurance on the phone lol
I have not put in custom rom there yet because I need to get a SD card and would rather move my apps there before doing so, but no issues and the thing could not be easier to do with his program.
That's great...
Sent from my SM-G900F using XDA Premium 4 mobile app
The question is, can a rooted (but older) firmware be as secure as a non-rooted (up-to-date) firmware?
Sure you install apps or modify certain files/settings to improve security, but what if there's a serious security flaw in the kernel?
Installing a newer kernel would render towelroot useless (the reason i don't mention CF-Auto-Root is because of KNOX, but you can't always have the best of both worlds)
Goldie said:
Urghhh if I read another statement like that I'm gonna scream! Modding is NOT at a standstill!! Why do so many people use these sweeping statements just because they can't have a fully working non Samsung based Rom. Modding is very much on the move for Samsung based roms. If you are waiting for fully working non Samsung you may as well have bought a N5 as by not using Samsung software you lose a hell of a lot of what makes an s5 and s5! Buy a nexus... Save some money and be happy
Sent from my SM-G900F using Tapatalk
Click to expand...
Click to collapse
I didn't mean it like that. I assume people simply aren't working on it much because the bootloader hasn't been unlocked. POintless to build ROMs that can't be used yet. That's all. I'm actually quite happy with my S5, and would be even if we never saw a big ROM community for it. It's a good phone, and Touch Wiz is far less intrusive than it used to be. Even knowing an F device is in the works I'm still happy with my purchase.
A week ago, I got a prompt to update to the most recent Android version. I have a Galaxy S5 SM-G900F. Had rooted it with Towelroot in July and everything was smooth, haven't done any major changes other than SuperSU and titanium. After I ok'ed the software update, it got to like 30% or something until it crashed and rebooted. Everything seems fine, just the update didn't get installed, I'm still 4.4.2. When trying to update it, it says that my operating system has been modified in an unauthorized way (towelroot) and that I should try to download updates using Kies.
So I looked a bit for solutions, I checked the SuperSU survival mode AFTER failing the update, and now my question is, what is the best way to update whilst retaining root and all my settings, in the fastest way? Or just what is the best solution to update? Don't really want to download Kies just for this. Sorry for noobness. Thanks for any help, appreciate it.
tempest22 said:
just what is the best solution to update?
Click to expand...
Click to collapse
The best thing to do is always search first. Most questions have been asked and answered before, so a quick search gives you an immediate answer, not to mention a larger number of replies and accumulated wisdom. And if any aspect remains unanswered, you are in a much better position to pose informed questions.
Of course that is a pipe dream, because most people aren't sensible enough to take 30 seconds to search, expecting someone else to gift wrap the answer for them.
Anyway, the best approach is arguably to never be first to accept an update. Instead wait a few days and then see what early adopters are posting about any given new update. Every update is different and that will quickly tell you if there are any issues regarding root and inevitably how to deal with them. OTA updates will usually break root and often fail to install properly as well. It's better to wait and install an update via Odin IMO.
Some apps, notably mobile odin pro and super su pro have root survival modes that will attempt to regain root after an update. But there are no guarantees and you should not rely upon them. Instead treat it as an emergency plan B.
.
Did you change from dalvik to ART. I got the same message after changing to art and going back to dalvik sorted it for me.
Sent from my Galaxy S5 running NeatRom 0X1
fffft said:
The best thing to do is always search first. Most questions have been asked and answered before, so a quick search gives you an immediate answer, not to mention a larger number of replies and accumulated wisdom. And if any aspect remains unanswered, you are in a much better position to pose informed questions.
Of course that is a pipe dream, because most people aren't sensible enough to take 30 seconds to search, expecting someone else to gift wrap the answer for them.
Anyway, the best approach is arguably to never be first to accept an update. Instead wait a few days and then see what early adopters are posting about any given new update. Every update is different and that will quickly tell you if there are any issues regarding root and inevitably how to deal with them. OTA updates will usually break root and often fail to install properly as well. It's better to wait and install an update via Odin IMO.
Some apps, notably mobile odin pro and super su pro have root survival modes that will attempt to regain root after an update. But there are no guarantees and you should not rely upon them. Instead treat it as an emergency plan B.
.
Click to expand...
Click to collapse
Thanks for the answer. I'm not technically well versed, I just know that this forum is the best for people like me who need advice from the pros lol. I would rather just have the most recent update because I don't want any vulnerabilities or whatever. I haven't ever used Odin, just Towelroot and done. I don't use any roms, just factory plus root through towelroot and supersu, that's it for now. So again, how would a noob like me go about safely getting an update and having the reassurance that Towelroot will either still be there, or if an unroot is necessary, that towelroot will be able to root again? Kies? Also, is an actual OTA update still possible (I'm getting that error message) or is a computer update the only thing left?
Prof Peach said:
Did you change from dalvik to ART. I got the same message after changing to art and going back to dalvik sorted it for me.
Sent from my Galaxy S5 running NeatRom 0X1
Click to expand...
Click to collapse
nope, just towelrooted it 2 months ago and that's that. no roms. still have 4.2.2, wanted to update. I got a failed update a week ago when I got an OTA update prompt. That failed, root is stil there, S5 working fine but can't do OTA since it gives me that error message. What could I do to safely get the most recent software update but retain root, OR be able to update and reroot again with towelroot if I need to unroot to update...
can anybody help please?
Why not find a stock rooted rom for your model and flash it?
tempest22 said:
nope, just towelrooted it 2 months ago and that's that. no roms. still have 4.2.2, wanted to update. I got a failed update a week ago when I got an OTA update prompt. That failed, root is stil there, S5 working fine but can't do OTA since it gives me that error message. What could I do to safely get the most recent software update but retain root, OR be able to update and reroot again with towelroot if I need to unroot to update...
Click to expand...
Click to collapse
Just downgrade to an older rom like NE2 and root with Towelroot, after that flash the new rom with Mobile Odin Pro and keep root with Everroot and the other 2 options enabled. Or flash an older kernel on your updated rom now and reroot with TR, look here for how to http://forum.xda-developers.com/galaxy-s5/general/how-to-root-triggering-knox-2nd-method-t2843044. Or as posted above a pre-rooted stock rom like Alexander rom.
metalfan78 said:
Why not find a stock rooted rom for your model and flash it?
Click to expand...
Click to collapse
I'm sorry but I really don't know what that means in this context for an update. I used Towelroot 2 months ago to root and still haven't gotten myself anx root aps or mods (but was planning on it right when the update failed). Is there not a simple way to make this update work while either 1)unrooting, then updating then rerooting with Towelroot, or 2) updating whilst retaining Towelroot?
and ecniqu
gee2012 said:
Just downgrade to an older rom like NE2 and root with Towelroot, after that flash the new rom with Mobile Odin Pro and keep root with Everroot and the other 2 options enabled. Or flash an older kernel on your updated rom now and reroot with TR, look here for how to http://forum.xda-developers.com/galaxy-s5/general/how-to-root-triggering-knox-2nd-method-t2843044. Or as posted above a pre-rooted stock rom like Alexander rom.
Click to expand...
Click to collapse
I don't think you understand what I'm asking for, or I'm just way too much of a noob, probably that. but I'd just like to update to the most recent Android version. I'm 4.4.2, got an update prompt 1 week ago, have an SM-G900F, and have Towelrooted 2 months ago. All I want is to update. How can I do this, since I'm getting the failure message that it can't be updated due to my device being modified. If I unroot with supersu, then update, then (if the update works) try to Towelroot again, will Towelroot work? Or does the new update **** with it? Or an I update with Samsung Kies, while retaining Towelroot? Ahhhh I'm so sorry for this stupid question but I really don't know
no halp?
I'm really sorry for bumping this again, but I just honestly have no clue what to do to get it updated and either retain Towelroot or be able to install it again after updating. somebody help a noob out please.
my samsung galaxy s5 , it is rooted but I would like to upgrade, I can't do the OTA upgrade so I should proceed with Kies , I would like to know whether I have to unroot my phone (how do I do that? via kies? it does not matter if it'll lose the root, I just want to be sure I would still be able to use my samsung without creating any damage)or just directly proceed with the upgrade,furthermore, my phone was a sumsung galaxy s5 tmobile but I managed to unlock it in order to use it with other carriers, if I install the original firmware and then upgrade to the newest version, can I still use it with other carriers or will return locked? thank you in advance for your help
Checked old threads, and even made a thread a couple months ago about this question, but it goes a bit further.
I've finally rooted using this method: http://forum.xda-developers.com/galaxy-s4-tmobile/general/root-nb4-knox-0x0-t2802185
I didn't trip knox, that's great right?! Well, I went further, installed xposed, then gravity box and started playing around with my newly rooted device.
I then installed supersu (I haven't really needed it but I wanted to test something out from another thread, here: http://forums.androidcentral.com/samsung-safe-knox/366118-solution-how-permanently-remove-knox.html)
Well I've removed Knox!
Not quite: because knox is located in the bootloader, it's a little more complicated to remove. My question (finally) is that even though I've disabled knox as a pesky security feature, if I were to finally enable a custom recovery, or flash to a different rom (I wanna go aosp, and go to lolipop) would I have issues with knox again, and trip the counter? I still want to upgrade my phone using JUMP but I don't want to have problems with T-Mobile.
Thanks guys!
devilsmarch said:
Checked old threads, and even made a thread a couple months ago about this question, but it goes a bit further.
I've finally rooted using this method: http://forum.xda-developers.com/galaxy-s4-tmobile/general/root-nb4-knox-0x0-t2802185
I didn't trip knox, that's great right?! Well, I went further, installed xposed, then gravity box and started playing around with my newly rooted device.
I then installed supersu (I haven't really needed it but I wanted to test something out from another thread, here: http://forums.androidcentral.com/samsung-safe-knox/366118-solution-how-permanently-remove-knox.html)
Well I've removed Knox!
Not quite: because knox is located in the bootloader, it's a little more complicated to remove. My question (finally) is that even though I've disabled knox as a pesky security feature, if I were to finally enable a custom recovery, or flash to a different rom (I wanna go aosp, and go to lolipop) would I have issues with knox again, and trip the counter? I still want to upgrade my phone using JUMP but I don't want to have problems with T-Mobile.
Thanks guys!
Click to expand...
Click to collapse
As soon as you flash custom recovery knox will be tripped
1eyedmonster said:
As soon as you flash custom recovery knox will be tripped
Click to expand...
Click to collapse
Kinda what I thought would happen unless you changed the bootloader.
You can't change it unless it has the same certificate from Samsung right? Even if you copied it over to a different bootloader?
devilsmarch said:
Kinda what I thought would happen unless you changed the bootloader.
You can't change it unless it has the same certificate from Samsung right? Even if you copied it over to a different bootloader?
Click to expand...
Click to collapse
I know once you have the latest bootloader you can't go back and with the forthcoming android L you will need the latest bootloader so I would just update to the latest version and root and flash away aosp or whatever I know it invalidates your warranty but for me it's worth the risk however the cm12 alpha is full of bugs so I would wait for a beta at least to avoid disappointment