I have a Sprint GS4 with MK2 (SPH-L720), waited a while to root and saw Towel discussed, tried and it worked 100%. My experience rooting is mostly with HTC products so this was my first rooting with the GS4 and it couldn't have been easier. Added SU, verified root, all seems good!
I have an update that was downloaded over the past month or so that I have denied installing and glad I did since it seemed very easy to root!
So what's next? I'm used to installing a recovery and ROMing away.. I have ROM Toolbox installed (pro) and noticed they have the option to flash a recovery for you and wonder if that will work? If so, what recovery is good for this phone? I'm very used to TWRP and hope that is still a good recovery choice. My main goals are to be able to take the updates and keep root. Im fine with the stock look and feel but want that option to add the bling and speed when I'm ready..
I'm not too worried about the Knox being tripped but confident it was disabled during Towel root.
I always search, just can't find specific information on my phone and there are many many differences it seems. I figured compiling some answers would benefit others that bought the GS4 a while ago and never rooted until now. Any help or direction is appreciated!
Thanks!
For anyone in the same situation, I was able to avoid using Oden by utilizing ROM Toolbox, it flashed the newest version of TWRP successfully.
To summarize:
Sprint GS4, MK2 and never took an update for almost a year since purchase. Full root with Towelroot, installed Super User, granted and installed Root Checker to validate. Downloaded ROM Toolkit and flashed TWRP newest version. No issues, no crashes, no tripping KNOX. All good.
Seems there are a lot of people asking for help and while 'search' is useful, there are so many variables, so many threads to sift through its almost impossible to find what you need. Hopefully this helped someone.
Still determining how to take updates and if I will lose root. Still running stock but I am about to try my first custom ROM on this cell.
to my knowledge u can root every varient easily but even if u flashed twrp without tripping knox have u actually loaded it yet to see if recovery flag trips? and once u flash a rom it would deff trip the counter.. but who cares about knox anyway.. i tripped every counter within the hour of getting this phone
I have and it didnt but like you said, I didn't care if I tripped kmox etc. Thanks for the reply! So you believe it is safe to take the updates? Im really just trying to have tether working. Thanks!
If you're wanting to update via OTA, you'll have to unroot first.
There is no native hot spot hack for the NG2 update as of yet and Towelroot doesn't work yet either
Related
Hi there. I've had many rooted phones before. DX, tablets, S3. I've yet to root my S4 since I got it in August. I was waiting until it got 4.3 to do so. After all this Knox crap I held off a bit longer. Got the MK2 update a few days after the MJA update. I'm aware that I can still root MK2 with CF-Auto but I'm just not sure if its worth it yet. I really don't care about roms or even a custom recovery. I just want to tether a little. I don't plan on messing around with any system files much so a backup isn't entirely necessary. I guess what I'm asking is, is there a way I can tether with the MK2 OTA stock rooted? It doesn't seem like the hotspot mod was updated for MK2 yet. Just MJA. Would WiFiTether-TrevEMod possibly work still? The only other thing I'd like to do is remove the Knox system files. I think I saw something before about removing Knox (system files, not bootloader) but I can't remember where. It's hard to find a whole lot on MK2 yet because devs are still focused on circumventing MJA which I sincerely thank you all for btw. I just need a straight forward root, knox app removal, and tether process for MK2. Custom recovery also isn't a bad idea. I'd just want one that works. Philz right? Also, if any of this process goes bad I can always just flash the MJA tar and start over correct? Sorry for the long winded ramble. :silly: BTW, i could care less about tripping Knox.
Thanks
Jay
Oshuaj said:
Hi there. I've had many rooted phones before. DX, tablets, S3. I've yet to root my S4 since I got it in August. I was waiting until it got 4.3 to do so. After all this Knox crap I held off a bit longer. Got the MK2 update a few days after the MJA update. I'm aware that I can still root MK2 with CF-Auto but I'm just not sure if its worth it yet. I really don't care about roms or even a custom recovery. I just want to tether a little. I don't plan on messing around with any system files much so a backup isn't entirely necessary. I guess what I'm asking is, is there a way I can tether with the MK2 OTA stock rooted? It doesn't seem like the hotspot mod was updated for MK2 yet. Just MJA. Would WiFiTether-TrevEMod possibly work still? The only other thing I'd like to do is remove the Knox system files. I think I saw something before about removing Knox (system files, not bootloader) but I can't remember where. It's hard to find a whole lot on MK2 yet because devs are still focused on circumventing MJA which I sincerely thank you all for btw. I just need a straight forward root, knox app removal, and tether process for MK2. Custom recovery also isn't a bad idea. I'd just want one that works. Philz right? Also, if any of this process goes bad I can always just flash the MJA tar and start over correct? Sorry for the long winded ramble. :silly: BTW, i could care less about tripping Knox.
Thanks
Jay
Click to expand...
Click to collapse
If those are the only things you want, probably not worth rooting. You can use PDANET+ to get free tether w/o rooting, but it's either Bluetooth or wired connected. Works well, though.
And for backup, you can use Helium. Titanium Backup is available for un-rooted phones now too, so check that out here:
http://www.titaniumtrack.com/latest...supports-backups-from-non-rooted-devices.html
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
Ok I did a very stupid thing this morning. I have had my S5 for a week and decided I was ready to root. I had already done lots of research and watched some YouTube videos on it.
Of course the process is a breeze for anyone that is familiar with rooting in general. I attained root and was getting ready to look at the various ROMS.
While poking around the phone I noticed there was an update that could be applied. Now I know you are not suppose to take updates after rooting but I really hate not being on the most current version. So I started searching furiously to see if this update would break root. After 20 minutes or so I found nothing so I took the update. Surprise surprise it BROKE ROOT and Towel root won't fix it. I am devastated. ...is there nothing I can do.?
If anyone can provide hope I would appreciate it.
Now that I have plenty of time to look I have seen a couple of entries that says it did break root on some but not all phones. The update didn't even change the 4.4.2 status. Basically I have royally screwed up so if anyone else see that update.....BEWARE.!
You should be able to downgrade to a prior software version of the rom you have installed like NE2. I downgraded from NG2 to NE2 without tripping KNOX or any other issues. Flash the prior version of your firmware with Odin, untick Auto Reboot before the flash, after the flash pull the battery, wait 20 seconds, go into recovery and do a data factory reset. The phone should boot normal now. After you setup the phone, root with Towelroot and install superSU and SU Pro and enable root survival mode. This should keep the device rooted after an OTA or flash the new updated rom with Mobile Odin Pro and enable Evverroot and the other 2 options which should also keep the phone rooted. Both ways will not trip KNOX.
Thanks for the reply....did you do that with a Verizon phone? If so any links to the file? I've used Odin in the past I must admit it scares the crap out of me but if that is my only option I will do it. Also was that with a non development phone? It's like a dang minefield....lol.
GigaRack said:
Thanks for the reply....did you do that with a Verizon phone? If so any links to the file? I've used Odin in the past I must admit it scares the crap out of me but if that is my only option I will do it. Also was that with a non development phone? It's like a dang minefield....lol.
Click to expand...
Click to collapse
No, did it with an unbranded Dutch phone, its a non development phone with a unlocked bootloader. I don`t have xperience with US phones so better read up in the Verizon section before you do anything. Good luck mate
Ok I found the link...... http://forum.xda-developers.com/verizon-galaxy-s5/general/how-to-root-g900vvru1ane9-t2836201
..
Thanks very much. I have it rooted and on the latest version. Odin is not so scarey now....lol.
GigaRack said:
Odin is not so scarey now....lol.
Click to expand...
Click to collapse
Odin is never scary if you know how to use it
PS.: thank god for carriers that don't care about knox being 0x1
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
I've had my SGS4 on Sprint since release date. Rooted immediately, and have had it that way ever since. Looks like many of the root methods no longer work for the later build phones.
So... Can someone please point me in the direction of the root method for a new NG2 firmwared phone? I'm about to go get my replacement phone, and I don't want to even imagine staying on the Stock Sprint ROM...
I'd still like to know, for others that have a new post-MDL firmware phone...
But I got lucky. My replacement phone from Geek Squad was MDL. So CF Auto-Root, Install TWRP, Install NG2 Modem Only TAR file, and then load my favorite ROM. Restore my TWRP backup. And I'm right back where I was before the switch. Yay!
Cf auto root has worked for all updates. From MF9 to NG2.
long_tall_texan said:
Looks like many of the root methods no longer work for the later build phones.
Click to expand...
Click to collapse
I think maybe you're confused with the Knox warranty flag? Knox was introduced post-MF9 and if it is tripped (by rooting with CF for example), Samsung claims that they won't honor the warranty (although I still don't think we know of a case where this has actually happened?).