Hi all,
I've got a VZW S4 and I've yet to take any OTA's or updates. I rooted it within the first week it was released and have postponed the OTA's every day since. I really don't think I use my root for very much so I'm not completely against losing it, but the questions still stand: Should I bother to take the OTA and risk losing root? Is there -any- benefit to me still being on the pre-release kernel of the S4? Any developers need anything from my phone before I make this decision?
Thanks,
Opethfan89
If you're still on MDK there is no benefit of updating, you'll only lose your ability to flash ROMs. If you're on ME7 you'll lose safestrap. If you're on MI1... well then it's your call.
GreatDayChap said:
If you're still on MDK there is no benefit of updating, you'll only lose your ability to flash ROMs. If you're on ME7 you'll lose safestrap. If you're on MI1... well then it's your call.
Click to expand...
Click to collapse
I believe I'm on MDK still -- whatever the pre-release kernel was that everyone used right when the phone came out to root stuff (Loki seems to ring a bell).
I haven't used any custom ROMs, but if my current configuration allows me to then I would definitely like to retain that ability. I know I tried an AOSP ROM once and it was horrible, so I switched back to stock and I haven't gone back since.
Perhaps I should spend a weekend tinkering around...
I have a similar question. I'm on ME7 Rooted and some bloatware frozen. The only things I use root for these days is for my ad-blocker, Titanium backup, and a clocksync app that keeps my time synced to NIST.
Is it worth going to 4.3 without a root exploit for just these few apps? is there a non-root method of backup and restore like TiBu?
---------- Post added at 10:06 PM ---------- Previous post was at 09:51 PM ----------
I have a similar question. I'm on ME7 Rooted and some bloatware frozen. The only things I use root for these days is for an ad-blocker, Titanium backup, Bloatware freezer and a clock sync app that keeps my time synced to NIST.
Is it worth going to 4.3 without a root exploit for just these few apps? Is there a non-root method of backup and restore like TiBu?
What is the best way to unroot my phone before taking any updates. Should I use the superSU unroot method? Should I unfreeze the bloatware first?
thanks
Related
I followed this thread to root: http://forum.xda-developers.com/showthread.php?t=2024207
I think I used the Root66 stock VRALJB I don't remember. My phone model number says SCH-I605, the Android version is 4.1.1, Baseband is I605VRALL4, Build number is JRO03C.I605VRALJB. I don't know if the kernel number is necessary because it's really long to type out, but if you need it I will post it.
Then I unlocked the Bootloader using AdamOutler's thread and now I have a custom TW recovery thing.
When I try to do the update in the Settings, it reboots to the TW recovery and doesn't do anything. When I select to turn on the phone with the TW recovery, it says the update failed. Someone told me that I shouldn't do that update because it's something called OTA and it's bad for my rooted phone, but then how do I know when I need an update? Do I have to check this forum every day for announcements? Which thread will the updates be in?
Thank you
The update option in settings is for Verizon OTA updates. OTA stands for over-the-air. The updates are sent to your phone using the Verizon data network. After the update is loaded onto your phone, it reboots into stock recovery to install the update. Since you have a custom recovery, (TWRP, I believe), the update will always fail. I see that you have the latest baseband, which is really the only reason for taking the OTA update to begin with.
Now that you have a custom recovery, you can flash any of the wonderful 4.1 ROMs that we have at our disposal. I'm currently on Jedi X11 and I recommend that, but there are more to choose from. One word of caution: if you decide to flash a 4.2 ROM, then you can't go back to a 4.1 ROM unless you flash the sd card downgrade .zip file. This is because 4.2 will change your directories around. I will try to link to a thread with the downgrade zip in it on another post.
---------- Post added at 02:40 PM ---------- Previous post was at 02:35 PM ----------
Here is the link to that thread. The downgrade .zip is in the third post
http://forum.xda-developers.com/showthread.php?t=2129787
I haven't installed a ROM because I want to keep all the stock stuff, but if there is a ROM that keeps all the stock but somehow increases speed, then I'd install it but I don't know of any that don't not have some stock stuff removed.
The annoying thing is that the phone keeps telling me to update every 3 days and I don't like it. Is there a way I can stop this without doing anything bad to the phone?
While it's true that all ROMs are not 100% stock, you have to ask yourself what you really want to keep. The ROM I'm running is Touchwiz-based, which means it has all the S-Pen apps along with true multi-window functionality. The stuff that I left coming from pure stock was mostly bloatware.
Either way, if staying on pure stock is all that you want and you want to stop receiving the OTA update notices, then you need to use an app that can freeze other apps. Freezing means that the app is disabled, will no longer appear in your app drawer, and will not start up when you boot the phone. I use Titanium Backup to freeze apps. I recommend freezing apps over outright deleting them because you may inadvertently soft brick your phone that way.
Once you have Titanium Backup or another app with the same functionality, then you need to find and freeze SDM 1.0. It was mentioned in this post here:
http://forum.xda-developers.com/showthread.php?t=2177551
---------- Post added at 09:07 PM ---------- Previous post was at 08:48 PM ----------
I will add that I am not sure why you would unlock your bootloader if you didn't intend to flash any ROMs. The act of unlocking the bootloader is what took away your stock recovery and causes your OTA updates to fail when the installation process starts. You may want to research how to get your phone back to 100% stock if you want to be able to take updates in the future.
I had ME7 and rooted that, MODded some stuff, tweaked settings, disabled/froze bloatware... and everything was fine. Stable, fast enough.
Then I allowed (because I couldn't stand the constant Update Nag!!!) the MI1 update and DeLaVega Rooted that and things have been unstable since. Seemingly random apps are crashing and occasionally causing rebooting, sometimes it needs the battery pulled. The most critical app, and the one that leads to reboots the most, is Google Maps Nav - the one app I need most.
I am thinking I would like to revert to factory stock ME7, then re-root it, and maybe TWRP (and I have Titanium). There's nothing in MJ7 I need or want and I don't trust MI1 (it was out what... three weeks?)
I would do this myself but I can seem to find a ME7 Image that WIPES and unroots the phone.
It would probably help if someone would explain a bit more how the pieces work. I gather there's a bootloader, a kernal, the ROM and user data. Rooting deals with the boot cycle, the kernal is the main OS, the ROM contains OS layer above the kernal along with system apps and such. Obviously, those three have to get along. So my question is, if I used DeLaVega to root MI1, Can I just flash a non-wipe ME7 ROM? It seesm to me that the MI1 root tool would not get along with the ME7 ROM -- is that right?
BTW, I'm not a ROMmer. I get how ODIN works but I've never flashed anything (via Odin) to my phone(s) other than that MI1 root image (and WHY/WHAT is that 1.3gb?!? The ME7 exploit was a few KB)
Thank you VERY MUCH in advance for explanations, links and so on.
-- Bear
lordbear said:
I had ME7 and rooted that, MODded some stuff, tweaked settings, disabled/froze bloatware... and everything was fine. Stable, fast enough.
Then I allowed (because I couldn't stand the constant Update Nag!!!) the MI1 update and DeLaVega Rooted that and things have been unstable since. Seemingly random apps are crashing and occasionally causing rebooting, sometimes it needs the battery pulled. The most critical app, and the one that leads to reboots the most, is Google Maps Nav - the one app I need most.
I am thinking I would like to revert to factory stock ME7, then re-root it, and maybe TWRP (and I have Titanium). There's nothing in MJ7 I need or want and I don't trust MI1 (it was out what... three weeks?)
I would do this myself but I can seem to find a ME7 Image that WIPES and unroots the phone.
It would probably help if someone would explain a bit more how the pieces work. I gather there's a bootloader, a kernal, the ROM and user data. Rooting deals with the boot cycle, the kernal is the main OS, the ROM contains OS layer above the kernal along with system apps and such. Obviously, those three have to get along. So my question is, if I used DeLaVega to root MI1, Can I just flash a non-wipe ME7 ROM? It seesm to me that the MI1 root tool would not get along with the ME7 ROM -- is that right?
BTW, I'm not a ROMmer. I get how ODIN works but I've never flashed anything (via Odin) to my phone(s) other than that MI1 root image (and WHY/WHAT is that 1.3gb?!? The ME7 exploit was a few KB)
Thank you VERY MUCH in advance for explanations, links and so on.
-- Bear
Click to expand...
Click to collapse
as for as i know there is no method to downgrade once you have taken an update, not even with ODIN. once you take an OTA or update it you are stuck with it, you cannot go backwords
th3bl3d said:
as for as i know there is no method to downgrade once you have taken an update, not even with ODIN. once you take an OTA or update it you are stuck with it, you cannot go backwords
Click to expand...
Click to collapse
+1.
Now the only thing I can say is backup using TI and do a FDR (factory data reset).
This should clean up your issue. You will not lose root.
After that restore your apps one at a time and by all means make sure you *DO NOT* take the MJ7 update.
You think you are stuck now????
I have MI1 and it's rock solid with no crashes.
I have all the bloat frozen or disabled.
My phone never reboots or hangs.
tech_head said:
+1.
Now the only thing I can say is backup using TI and do a FDR (factory data reset).
This should clean up your issue. You will not lose root.
After that restore your apps one at a time and by all means make sure you *DO NOT* take the MJ7 update.
You think you are stuck now????
I have MI1 and it's rock solid with no crashes.
I have all the bloat frozen or disabled.
My phone never reboots or hangs.
Click to expand...
Click to collapse
I did FDR twice. Turned off restore of Google stuff during setup wizard, turned of AutoUpdate in Store so I could control what apps loaded, too.
After first FDR it appears I still had root. I think that MAYBE something went funky because I was rooted on ME7, let MI1 come via OTA, then DeLaVega'ed that. I just don't know.
Now, I have a different phone, I am going to need to UNroot and FDR the phone I will send back. Haven't found info on UNroot for Mi1/DeLaVega yet. I've seen ROMs for ME7-nowipe and MJ7-wipe.
Thanks
Bear
lordbear said:
I did FDR twice. Turned off restore of Google stuff during setup wizard, turned of AutoUpdate in Store so I could control what apps loaded, too.
After first FDR it appears I still had root. I think that MAYBE something went funky because I was rooted on ME7, let MI1 come via OTA, then DeLaVega'ed that. I just don't know.
Now, I have a different phone, I am going to need to UNroot and FDR the phone I will send back. Haven't found info on UNroot for Mi1/DeLaVega yet. I've seen ROMs for ME7-nowipe and MJ7-wipe.
Thanks
Bear
Click to expand...
Click to collapse
Look at this thread. -> http://forum.xda-developers.com/showthread.php?t=2301259
Hey guys, completely new here. I have had my S4 for awhile now and decided to finally root my device. I came across the vroot method and rooted my MJ7 s4. I now (stupidly) realize that not only is there little support for MJ7, but also that vroot has not been confirmed safe as it is a Chinese root method. My phone appears to work perfectly and I can confirm that it is rooted under MJ7 with no issues so far, but my question is: is there any way to err...uproot it and go back to stock until a safe method is confirmed? Or should I just wait until an Odin file is released? Like I said the phone works perfectly, I am just cautious and don't know what the next step is. Thanks!
No
ProtossPaul said:
Hey guys, completely new here. I have had my S4 for awhile now and decided to finally root my device. I came across the vroot method and rooted my MJ7 s4. I now (stupidly) realize that not only is there little support for MJ7, but also that vroot has not been confirmed safe as it is a Chinese root method. My phone appears to work perfectly and I can confirm that it is rooted under MJ7 with no issues so far, but my question is: is there any way to err...uproot it and go back to stock until a safe method is confirmed? Or should I just wait until an Odin file is released? Like I said the phone works perfectly, I am just cautious and don't know what the next step is. Thanks!
Click to expand...
Click to collapse
Well you're on mj7 like I am and that means we sit and wait for someone to find us a way to either run Safestrap or a bootloader unlock for custom recovery.
There already are Odin files in here and someone made a script to remove the Chinese superuser you're talking about and replace it with chainfires supersu.
Search around on here a little bit Youll find all that.
Verizon Galaxy S4
# MJ7 #
ALL Knoxed Up!
---------- Post added at 05:25 AM ---------- Previous post was at 05:16 AM ----------
Here's a video on the entire vroot method plus supersu
http://forum.xda-developers.com/showthread.php?t=
And here's a link to an Odin file, although I don't think you really need it. Plus it's a full Wipe
http://forum.xda-developers.com/showthread.php?t=2507253
Verizon Galaxy S4
# MJ7 #
ALL Knoxed Up!
Mistertac said:
No
Well you're on mj7 like I am and that means we sit and wait for someone to find us a way to either run Safestrap or a bootloader unlock for custom recovery.
There already are Odin files in here and someone made a script to remove the Chinese superuser you're talking about and replace it with chainfires supersu.
Search around on here a little bit Youll find all that.
Verizon Galaxy S4
# MJ7 #
ALL Knoxed Up!
---------- Post added at 05:25 AM ---------- Previous post was at 05:16 AM ----------
Here's a video on the entire vroot method plus supersu
http://forum.xda-developers.com/showthread.php?t=
And here's a link to an Odin file, although I don't think you really need it. Plus it's a full Wipe
http://forum.xda-developers.com/showthread.php?t=2507253
Verizon Galaxy S4
# MJ7 #
ALL Knoxed Up!
Click to expand...
Click to collapse
Okay great, I assume I used the same method as you did, I also have supersu so I suppose that means the Chinese garbage is gone. There really can't be any harm in leaving it in the current rooted MJ7 state right? I mean support will be released eventually. Waiting for safestrap seems like the best option just as far as safety is concerned. I have zero experience with rooting or flashing so I will wait for support to do a Titanium backup or something.
ProtossPaul said:
Okay great, I assume I used the same method as you did, I also have supersu so I suppose that means the Chinese garbage is gone. There really can't be any harm in leaving it in the current rooted MJ7 state right? I mean support will be released eventually. Waiting for safestrap seems like the best option just as far as safety is concerned. I have zero experience with rooting or flashing so I will wait for support to do a Titanium backup or something.
Click to expand...
Click to collapse
No that's our only option as of now. I'd go into titanium and freeze sdm and fwupgrade so that in the event there is another OTA you can wait to see if there is a method to retain root through it. Always look on here first before taking any OTA.!!!
I'm on mj7 rooted and I'm running xposed framework to customize my s4 quite a bit... And then I just remove /freeze everything I don't want using Titanium. And I'm happy with my phone.
The devs are working on both Safestrap and unlocking the bootloader. It's a lot of work but those guys are on here working diligently.
Verizon Galaxy S4
# MJ7 #
ALL Knoxed Up!
---------- Post added at 06:41 AM ---------- Previous post was at 05:54 AM ----------
Also here's a thread listing some of the things people have been freezing using Titanium.
Maybe itll help.
http://forum.xda-developers.com/showthread.php?t=2314265
Verizon Galaxy S4
# MJ7 #
ALL Knoxed Up!
Mistertac said:
No that's our only option as of now. I'd go into titanium and freeze sdm and fwupgrade so that in the event there is another OTA you can wait to see if there is a method to retain root through it. Always look on here first before taking any OTA.!!!
I'm on mj7 rooted and I'm running xposed framework to customize my s4 quite a bit... And then I just remove /freeze everything I don't want using Titanium. And I'm happy with my phone.
The devs are working on both Safestrap and unlocking the bootloader. It's a lot of work but those guys are on here working diligently.
Verizon Galaxy S4
# MJ7 #
ALL Knoxed Up!
---------- Post added at 06:41 AM ---------- Previous post was at 05:54 AM ----------
Also here's a thread listing some of the things people have been freezing using Titanium.
Maybe itll help.
http://forum.xda-developers.com/showthread.php?t=2314265
Verizon Galaxy S4
# MJ7 #
ALL Knoxed Up!
Click to expand...
Click to collapse
I really should have done more research before doing this, but can you explain to me the reason to use safestrap when you have flashed a recovery on Titanium backup? I thought that if you screwed anything up you could just revert to your last flash on Titanium. Also unlocking the bootloader is going to allow us to use custom ROMS right? Sorry, really trying to get up to speed, it's a difficult time to get into this with MJ7. I really just want to go about this in the safest way possible.
ProtossPaul said:
I really should have done more research before doing this, but can you explain to me the reason to use safestrap when you have flashed a recovery on Titanium backup? I thought that if you screwed anything up you could just revert to your last flash on Titanium. Also unlocking the bootloader is going to allow us to use custom ROMS right? Sorry, really trying to get up to speed, it's a difficult time to get into this with MJ7. I really just want to go about this in the safest way possible.
Click to expand...
Click to collapse
Well.. Couple things..
First off since we have an mj7 Verizon S4 there is no flashing anything at all. No roms at all. Titanium backup is a tool that can save all your system and user data/apps. As well as uninstall and freeze things.
Safestrap if it ever gets to us just allows the flashing of roms on a '' safe'' location on our phones. It doesn't touch our actual mj7 Samsung Touchwiz.
No custom recovery like Clockwork Mod for us because the bootloader is locked up!
There are many people on here working on both of these issues with the bootloader itself and going the Safestrap route as well.
For now grab titanium and freeze those two things I mentioned earlier so that your phone recieves no further updates. You don't want an update until you know there is a safe way to root, or keep root, if that's important to ya.
Other than that you can use xposed framework and modules to hook up you're phone.
Verizon Galaxy S4
# MJ7 #
ALL Knoxed Up!
Mistertac said:
Well.. Couple things..
First off since we have an mj7 Verizon S4 there is no flashing anything at all. No roms at all. Titanium backup is a tool that can save all your system and user data/apps. As well as uninstall and freeze things.
Safestrap if it ever gets to us just allows the flashing of roms on a '' safe'' location on our phones. It doesn't touch our actual mj7 Samsung Touchwiz.
No custom recovery like Clockwork Mod for us because the bootloader is locked up!
There are many people on here working on both of these issues with the bootloader itself and going the Safestrap route as well.
For now grab titanium and freeze those two things I mentioned earlier so that your phone recieves no further updates. You don't want an update until you know there is a safe way to root, or keep root, if that's important to ya.
Other than that you can use xposed framework and modules to hook up you're phone.
Verizon Galaxy S4
# MJ7 #
ALL Knoxed Up!
Click to expand...
Click to collapse
First of all, I want to say thanks so much for helping me. I know it wasn't addressed in the title of my thread but I really do appreciate it. I have noticed that people seem skeptical about doing anything on the rooted MJ7 framework so I just thought I should ask of its safe to do Titanium without bricking my phone? Not only have I never done it before but I am cautious if it is safe because I haven't backed anything up yet. Didn't want to use an old method now that we are on MJ7). Can I use the current version of titanium with MJ7 safely? Also what can I do with the Xposed framework? I thought that was used to load custom ROMS?
Thank you SO much.
Alright, so I have some questions that can probably be chalked up in the 'Rooted MJ7, what now?' category. I can't specifically find these answers, but I've read a ton of what basically boils down to, you can't do sh*t with mj7.
So I realize there's no flashing ROMs on mj7, which sucks a big one, but that's fine, I'll deal.
I've rooted the phone via vroot and all is good there. Triangle away doesn't seem to work, but whatever. It's highly unlikely that I'll need to take the phone into the store.
My biggest gripe is that I can't seem to get adb to work to push files to the phone. I keep getting 'permission denied' errors when I get to the 'adb push ..............' part. Near as I can tell from my reading, this is because the bootloader is locked. Is that right? I tried adding 'ro.secure=1' to 0 in default.prop, but that didn't work. I was trying to push a modded services.odex to /system/framework. Does anyone know how to get adb fully working on a rooted mj7? If you check my sig., you'll see that I'm not a total noob persay. I've been using adb for years. I have all the right files installed on my PC and what not.
ProtossPaul said:
First of all, I want to say thanks so much for helping me. I know it wasn't addressed in the title of my thread but I really do appreciate it. I have noticed that people seem skeptical about doing anything on the rooted MJ7 framework so I just thought I should ask of its safe to do Titanium without bricking my phone? Not only have I never done it before but I am cautious if it is safe because I haven't backed anything up yet. Didn't want to use an old method now that we are on MJ7). Can I use the current version of titanium with MJ7 safely? Also what can I do with the Xposed framework? I thought that was used to load custom ROMS?
Thank you SO much.
Click to expand...
Click to collapse
Titanium is not used to load roms. It's used for backing things up primarily and that's it. It can also uninstall /freeze things, but that's all.
There's not really much we can do now except use xposed framework/mods to customize our phones. It is very safe and everything is located right here on xda.
For now take a look at this
http://forum.xda-developers.com/showthread.php?t=2383484
Read from beginning and install the framework first, then Wanam.
It explains everything.
Verizon Galaxy S4
# MJ7 #
ALL Knoxed Up!
---------- Post added at 07:31 AM ---------- Previous post was at 07:22 AM ----------
sharkie405 said:
Alright, so I have some questions that can probably be chalked up in the 'Rooted MJ7, what now?' category. I can't specifically find these answers, but I've read a ton of what basically boils down to, you can't do sh*t with mj7.
So I realize there's no flashing ROMs on mj7, which sucks a big one, but that's fine, I'll deal.
I've rooted the phone via vroot and all is good there. Triangle away doesn't seem to work, but whatever. It's highly unlikely that I'll need to take the phone into the store.
My biggest gripe is that I can't seem to get adb to work to push files to the phone. I keep getting 'permission denied' errors when I get to the 'adb push ..............' part. Near as I can tell from my reading, this is because the bootloader is locked. Is that right? I tried adding 'ro.secure=1' to 0 in default.prop, but that didn't work. I was trying to push a modded services.odex to /system/framework. Does anyone know how to get adb fully working on a rooted mj7? If you check my sig., you'll see that I'm not a total noob persay. I've been using adb for years. I have all the right files installed on my PC and what not.
Click to expand...
Click to collapse
No there's no custom recovery or even Safestrap, which means no roms yet unfortunately.
There's no triangle away either but I've seen some folks working on something like Knox Away which is the same kind of thing since we're all stuck with Knox now!
As far as your ADB questions I'm not your guy for that. I'd say though that maybe it's got to do with the new security we have on these things now for sure.
I'm sure someone way more qualified than me can lead you in the right direction.
Verizon Galaxy S4
# MJ7 #
ALL Knoxed Up!
Mistertac said:
...but I've seen some folks working on something like Knox Away which is the same kind of thing since we're all stuck with Knox now!
Click to expand...
Click to collapse
I've deleted all the Knox files I could find (about 12 or so) using FX Explorer along with some other security stuff that I found. I guess that's not enough to fully get rid of Knox since I still have that 'custom' screen at boot...
Man, I really wish I would have done more reading before deciding to go with a Samsung. Oh well, despite all this, it's still a great phone.
Thanks for your reply.
sharkie405 said:
I've deleted all the Knox files I could find (about 12 or so) using FX Explorer along with some other security stuff that I found. I guess that's not enough to fully get rid of Knox since I still have that 'custom' screen at boot...
Man, I really wish I would have done more reading before deciding to go with a Samsung. Oh well, despite all this, it's still a great phone.
Thanks for your reply.
Click to expand...
Click to collapse
No there's no getting rid of Knox, it's part of the actual bootloader and kernel on some level. You can get rid of the Knox app which is on our phones but that's about it.
I was thinking the same thing about getting an S4 but from what I've read this sort of security is going to be more common on a lot of phones not just Samsung.
That custom screen went away on my phone, I wouldn't worry so much about that.
The s4 is an awesome phone, take a look at all the xposed modules you can add and really customize it.
Verizon Galaxy S4
# MJ7 #
ALL Knoxed Up!
Am having trouble un-rooting MK2 for warranty work and could use some pointers.
Here's the problem: I'm not getting 4G/LTE signal, even in dense urban areas.
I think I need a new SIM, which will entail a trip to the Verizon Store, which means un-rooting.
I recently upgraded to a Galaxy S4. I have Unlimited Data, so I did the upgrade on another line, then used my existing SIM from my Galaxy Nexus to activate. It seemed to work fine.
Then did the following:
• Rooted
• WiFi Tether hack
• Installed Xposed and Wanum to remove custom boot screen
So I read the various un-root threads. This seems the most useful:
http://forum.xda-developers.com/showthread.php?t=2578209
but I'm concerned about the warning about losing the Loki Exploit and not being able to re-root.
If I ODIN the factory image, will I still be able to root it without Loki?
Other threads recommended a full-reset, which I did from stock recovery. Afterwards, I am still rooted and the Custom boot screen still appears.
So, how can I get back to a factory state to get a new SIM and then still be able to re-root?
Being able to use SafeStrap would be nice, but my main requirements are Root and WiFi tether. I can live with Nova Launcher over stock TouchWiz. I backed up the customized image in TiBu so I'll be able to restore once re-rooted.
Thoughts?
jpinsl said:
Am having trouble un-rooting MK2 for warranty work and could use some pointers.
Here's the problem: I'm not getting 4G/LTE signal, even in dense urban areas.
I think I need a new SIM, which will entail a trip to the Verizon Store, which means un-rooting.
I recently upgraded to a Galaxy S4. I have Unlimited Data, so I did the upgrade on another line, then used my existing SIM from my Galaxy Nexus to activate. It seemed to work fine.
Then did the following:
• Rooted
• WiFi Tether hack
• Installed Xposed and Wanum to remove custom boot screen
So I read the various un-root threads. This seems the most useful:
http://forum.xda-developers.com/showthread.php?t=2578209
but I'm concerned about the warning about losing the Loki Exploit and not being able to re-root.
If I ODIN the factory image, will I still be able to root it without Loki?
Other threads recommended a full-reset, which I did from stock recovery. Afterwards, I am still rooted and the Custom boot screen still appears.
So, how can I get back to a factory state to get a new SIM and then still be able to re-root?
Being able to use SafeStrap would be nice, but my main requirements are Root and WiFi tether. I can live with Nova Launcher over stock TouchWiz. I backed up the customized image in TiBu so I'll be able to restore once re-rooted.
Thoughts?
Click to expand...
Click to collapse
Don't worry about any of this. I just did this few weeks ago. They don't care about your phone status as far as custom goes for a new Sim Card. Alls they do is put it in and power it back up. And your good.
As far as the other things you said.. If you're on MK2 build then nothing to do with Loki applies to you.
Anyways..... You're going to be just fine.
Sent from my SCH-I545 using Tapatalk
---------- Post added at 12:24 PM ---------- Previous post was at 12:16 PM ----------
By the way... I went into Verizon running a custom recovery and a AOSP ROM. Your on mk2 which is still Stock TW. All the menus and settings are the same. They are not in a AOSP ROM like mine was.
The Verizon people were actually jealous of my phone .
Its when you send your phone in for an insurance claim that you want to do what you originally asked about.
Sent from my SCH-I545 using Tapatalk
Hi all, thanks in advance for any help on this. I have a few general s5 rooting questions. I'm an experienced 'rooter' having rooted and installed custom ROMs on many previous devices.
- I've ready that the s5 has an 'e-fuse' that gets 'blown' when the device is rooted. this then voids the warranty and prevents things like Fort Knox from running. I get that, and understand the risks. But, I've also read that the lollipop update will remove root. These two things seem to contradict themselves.
- on other devices I've rooted, I've then installed a custom ROM. I don't plan to do this with my s5. I haven't been able to find much written on the experience of a rooted s5 running the samsung stock ROM/firmware. I'd like to use something like xposed to change parts of the ROM (like the white background that's so pervasive in the s5 flavor of lollipop). I'm curious if anyone is running lollipop on an s5 that is rooted but running stock samsung firmware and xposed.
thanks!
Rooting won't trip Knox. Installing a custom recovery will. If you have insurance on your device tripping Knox doesn't matter, your covered anyway.
thanks!
stncldtex said:
Rooting won't trip Knox. Installing a custom recovery will. If you have insurance on your device tripping Knox doesn't matter, your covered anyway.
Click to expand...
Click to collapse
very interesting, thanks! can I run xposed/titanium backup pro/other root things without a custom recovery? all I'm really interested in is modifying Samsung-dictated things (like apps that can't be frozen and colors/elements that can't be changed) + making complete backups to the SD card. If I recall from my previous experiences, a custom recovery was the way to create a nandroid backup...but I think perhaps titanium backup pro can do that from the android front-end (with root).
I assume that I should wait to root until the tmobile s5 gets lollipop? i.e. that update will kill root?
scwtech said:
very interesting, thanks! can I run xposed/titanium backup pro/other root things without a custom recovery? all I'm really interested in is modifying Samsung-dictated things (like apps that can't be frozen and colors/elements that can't be changed) + making complete backups to the SD card. If I recall from my previous experiences, a custom recovery was the way to create a nandroid backup...but I think perhaps titanium backup pro can do that from the android front-end (with root).
I assume that I should wait to root until the tmobile s5 gets lollipop? i.e. that update will kill root?
Click to expand...
Click to collapse
Right now there are threads that show you how to get rooted lollipop on your phone without tripping Knox which basically involves downgrading the kernel so you can root with towelroot, then using mobile Odin to flash lollipop and inject root in the process. It seems people are able to do this without issues. To this point, I do not think that anyone has found an exploit for lollipop.
The problem you will run into is that Xposed still does not run on lollipop so you cannot do much in the way of customization. Most of the G900F ROMs can run on the G900T so you might poke around in those threads to pick up more info.
Hope this helps a little.
If I or anybody on XDA helps you, please hit the "Thanks" button.
scwtech said:
very interesting, thanks! can I run xposed/titanium backup pro/other root things without a custom recovery? all I'm really interested in is modifying Samsung-dictated things (like apps that can't be frozen and colors/elements that can't be changed) + making complete backups to the SD card. If I recall from my previous experiences, a custom recovery was the way to create a nandroid backup...but I think perhaps titanium backup pro can do that from the android front-end (with root).
I assume that I should wait to root until the tmobile s5 gets lollipop? i.e. that update will kill root?
Click to expand...
Click to collapse
System runtime is different. Art for lollipop compared to dalvik.. So it's not compatible as of now
Sent from my SM-G900T using XDA Free mobile app
This does not work with lollipop
---------- Post added at 07:30 PM ---------- Previous post was at 07:25 PM ----------
gspears said:
Right now there are threads that show you how to get rooted lollipop on your phone without tripping Knox which basically involves downgrading the kernel so you can root with towelroot, then using mobile Odin to flash lollipop and inject root in the process. It seems people are able to do this without issues. To this point, I do not think that anyone has found an exploit for lollipop.
The problem you will run into is that Xposed still does not run on lollipop so you cannot do much in the way of customization. Most of the G900F ROMs can run on the G900T so you might poke around in those threads to pick up more info.
Hope this helps a little.
If I or anybody on XDA helps you, please hit the "Thanks" button.
Click to expand...
Click to collapse
are you sure ? I have been able to downgrade. towelroot and flash lollipop and it boots but supersu does not work properly. root apps ask permission and supersu grants permission but the apps dont actually work
stncldtex said:
Rooting won't trip Knox. Installing a custom recovery will. If you have insurance on your device tripping Knox doesn't matter, your covered anyway.
Click to expand...
Click to collapse
I don;t know where you heard that rooting won;'t trip Knox but I beleive you are wrong about that At least I know that Flashing cf auto root - flashing recovery or flashing custom roms all trip knox. If your phone can use Towel Root - that rooting process does not trip knox - but I am not sure if Towel Root works on Lollipop or on the S5 for that matter. (I may be wrong about Towel Root - I have never used that process so I can't say for sure)
Flashing a new rom via ODIN does not trip knox. It is just like getting an UPDATE from the carrier OTA.
BUT, If you are already rooted - you already have tripped knox - flashing Lollipop will remove root - but it will not do anything to change the fact that you tripped knox on your phone already.
As far as I know everything I have said is correct - based on what I have learned thru reading - flashing and using several different samsung phones -
finally, I see a lot of people paranoid as hell about tripping knox - and I can tell you without any hesitation that I have never had a problem getting service or replacements after rooting a phone - there have been a few times back when I first started flashing roms that I had issues with my phone and I took it in and got a replacement without any issue - once I broke my screen and got a replacement then too - both times I was rooted, running custom recovery - etc.
I hope this helps you
I used towel root on NE6. You can downgrade to that via Odin and not trip knox. As far as flashing 5.0 and losing root. I came from Alliance flash Twisted lollipop and kept root. Then used Odin to flash the bootloader and modem for OB1.
Do you still have Knox 0?
How did you flash lollipop?