Using the Software update after rooting - Verizon Samsung Galaxy S 4

It's funny , on some threads some say never to use the software update due to a possible brick. the I've seen on other threads to root then update because there seems to be a build update after the MJ7 build. Mine has the MJ7
Today, I've read that Kit Kat may be out by the end of the month
Can anyone shed light to my question?
Before I read, not to try the update, I did. All it did was fail, plus after I checked that I still had root and a 0 x 0 in the warranty status, so I felt good about that )
Thanks

There's a thread on how to keep root and update in the development section
Sent from my SCH-I545 using Tapatalk

joshm.1219 said:
There's a thread on how to keep root and update in the development section
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
thanks!

pbman1953 said:
thanks!
Click to expand...
Click to collapse
I guess the question is there an update build after MJ7? or is the newest MK2?

MK2 is the newest build just came out.
Sent from my SCH-I545 using Tapatalk

joshm.1219 said:
MK2 is the newest build just came out.
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
Is it worth the hastle to update since kit kat is so close?
Thanks

pbman1953 said:
Is it worth the hastle to update since kit kat is so close?
Thanks
Click to expand...
Click to collapse
If my OTA fails how can I get the update file?

pbman1953 said:
Is it worth the hastle to update since kit kat is so close?
Thanks
Click to expand...
Click to collapse
KitKat won't be here for a couple months.
Sent from my SCH-I545 using Tapatalk

pbman1953 said:
Is it worth the hastle to update since kit kat is so close?
Thanks
Click to expand...
Click to collapse
someone correct me if im wrong, but the any ota will error out if you have any system altering files ie xposed, viper4android, things like that. Or if you have deleted any factory apps you will need to get those back before attempting an ota. In my experience, i've had to odin flash a factory no wipe image before any ota took (me7 ,mi1, mj7,and mk2) therefor you would need to update in sequence to get the latest. ie from mj7 to mk2 before you could access any later version. so you'll eventually have to update to mk2 before kit kat anyways.

jhud25 said:
someone correct me if im wrong, but the any ota will error out if you have any system altering files ie xposed, viper4android, things like that. Or if you have deleted any factory apps you will need to get those back before attempting an ota. In my experience, i've had to odin flash a factory no wipe image before any ota took (me7 ,mi1, mj7,and mk2) therefor you would need to update in sequence to get the latest. ie from mj7 to mk2 before you could access any later version. so you'll eventually have to update to mk2 before kit kat anyways.
Click to expand...
Click to collapse
Not "any" system files, just any system files that the OTA is updating. Of course, it's not easy to tell what those files are.
The MI1 to MJ7 OTA, which was the update to 4.3, updated a LOT of files, so anything that you changed is likely to cause the update to fail.
MK2 doesn't touch nearly as much, so it's less likely to fail due to update. I think I've seen the MK2 update work even though xposed was installed and enabled, which wouldn't work when going to MJ7.

Having said all that wouldn't you still need to be on mk2 to ota the next update whatever that may be?
Sent from my SCH-I545 using xda premium

jhud25 said:
Having said all that wouldn't you still need to be on mk2 to ota the next update whatever that may be?
Click to expand...
Click to collapse
Yes, that's been the way the updates have come. No way to skip updates using OTAs.

Related

SCH-i545 Verizon GSIV - Stock from Root MK2

Hi All!
I rooted my Galaxy S4 on Verizon earlier today (well, attempted to) with VRoot. It worked, but everything was really sluggish so I attempted to flash back to the stock Samsung ROM. I discovered that since I was running 4.3 with the MK2 OTA, I can't flash a previous version. I can't find a copy of the MK2 ROM anywhere. Does anyone here have any suggestions or maybe a link to the MK2 ROM for the i545 on Verizon?
Thanks!
Ross
rossifer said:
Hi All!
I rooted my Galaxy S4 on Verizon earlier today (well, attempted to) with VRoot. It worked, but everything was really sluggish so I attempted to flash back to the stock Samsung ROM. I discovered that since I was running 4.3 with the MK2 OTA, I can't flash a previous version. I can't find a copy of the MK2 ROM anywhere. Does anyone here have any suggestions or maybe a link to the MK2 ROM for the i545 on Verizon?
Thanks!
Ross
Click to expand...
Click to collapse
Got it fixed. Used Kies to download MK2 and reflash. All is now well. Still have the file if anyone else needs it.
rossifer said:
Got it fixed. Used Kies to download MK2 and reflash. All is now well. Still have the file if anyone else needs it.
Click to expand...
Click to collapse
So your device isn't rooted anymore? I'm trying to find a sure way to root my S4 i545 MK2 because I'm a noob. . .
TonioAG said:
So your device isn't rooted anymore? I'm trying to find a sure way to root my S4 i545 MK2 because I'm a noob. . .
Click to expand...
Click to collapse
There are several ways to root the mk2 version but both vroot and kingo have been deemed unsafe by the xda mods, in the development thread there is however a root method for mj7 that does in fact work with mk2. also im gonna warn you before hand that there is no custom recovery available for the mk2 or mj7 versions of the gs4.
Link to saferoot method: http://forum.xda-developers.com/showthread.php?t=2565758
Mtsprite said:
There are several ways to root the mk2 version but both vroot and kingo have been deemed unsafe by the xda mods, in the development thread there is however a root method for mj7 that does in fact work with mk2. also im gonna warn you before hand that there is no custom recovery available for the mk2 or mj7 versions of the gs4.
Link to saferoot method: http://forum.xda-developers.com/showthread.php?t=2565758
Click to expand...
Click to collapse
I used the same method. Worked quite well. But is it yet safe to flash?
xclementinex said:
I used the same method. Worked quite well. But is it yet safe to flash?
Click to expand...
Click to collapse
If your talking About flashing custom ROMS/recovery's, then no, and if you attempt to do either it most likely will result in a brick. However a Dev by the name of Hashcode, is currently working on making safestrap compatible with MJ7 & MK2. I hope that helps clear up some things.
Sent from my SCH-I545 using XDA Premium 4 mobile app
Is there a way to go back to MD5 from MK2 once you have root?
N8007 said:
Is there a way to go back to MD5 from MK2 once you have root?
Click to expand...
Click to collapse
Do u mean mdk?....there is no way
powered by hashcode safestrap hyperdrive 10.2
Guess I will have to wait.
rossifer said:
Got it fixed. Used Kies to download MK2 and reflash. All is now well. Still have the file if anyone else needs it.
Click to expand...
Click to collapse
How did you use Kies to download MK2 when you while rooted?
I have the Verizon S4... I took the OTA and updated to MK2. I then rooted using Saferoot.
All is good ...
Now.. Is the recovery unlocked? or do I need Safestrap Recovry to get ROMs on this?
Please advise.
Thanks!
A little help rooting mk2 via safe root. I've been rooted since me7 to mi1 to mj7. I flashed no wipe mj7 via Odin to take the ota mk2. Problem is the install bat closes as soon as I try to execute it. Drivers are correct Kies and Odin recognize my phone. Any suggestions?
Sent from my SCH-I545 using xda premium
paulsg63 said:
I have the Verizon S4... I took the OTA and updated to MK2. I then rooted using Saferoot.
All is good ...
Now.. Is the recovery unlocked? or do I need Safestrap Recovry to get ROMs on this?
Please advise.
Thanks!
Click to expand...
Click to collapse
No custom recovery.
---------- Post added at 07:57 PM ---------- Previous post was at 07:56 PM ----------
jhud25 said:
A little help rooting mk2 via safe root. I've been rooted since me7 to mi1 to mj7. I flashed no wipe mj7 via Odin to take the ota mk2. Problem is the install bat closes as soon as I try to execute it. Drivers are correct Kies and Odin recognize my phone. Any suggestions?
Sent from my SCH-I545 using xda premium
Click to expand...
Click to collapse
That's caused by a defect in the install script that I introduced when trying to add more prompting to help people connect. Re-download and it should be OK.
Thanks re downloading now
Sent from my SCH-I545 using xda premium
Re downloaded script worked like a charm. it errored out on busy box install but titanium verifies I have busy box installed. Great work on the exploit as well as the bat file. Thanks again, I was about to lose my mind
Sent from my SCH-I545 using xda premium
rossifer said:
Got it fixed. Used Kies to download MK2 and reflash. All is now well. Still have the file if anyone else needs it.
Click to expand...
Click to collapse
What is link to mk2 stock file?
I can't confirm but it has been said that mk2 is backwards compatible. Flash mj7 stock via odin. Then ota back to mk2. I know it's a long way around but it's worth looking into.
Sent from my SCH-I545 using xda premium
jhud25 said:
I can't confirm but it has been said that mk2 is backwards compatible. Flash mj7 stock via odin. Then ota back to mk2. I know it's a long way around but it's worth looking into.
Sent from my SCH-I545 using xda premium
Click to expand...
Click to collapse
Thank,s not a big deal to go back. I didn't think you could go back.
If you can go backwards that would be sweet. I would like to start running some custom Roms. I will give it a try.
Sent from my SCH-I545 using xda app-developers app
N8007 said:
If you can go backwards that would be sweet. I would like to start running some custom Roms. I will give it a try.
Sent from my SCH-I545 using xda app-developers app
Click to expand...
Click to collapse
You ONLY can go backwards from MK2 to MJ7. You seem to be interpreting this as being able to go back from MK2 to anything, and that's not the case.
Both of those releases only allow custom ROMs using Safestrap, and both support the same ROMs. There's no point in downgrading to MJ7.

Stock root safe update from ME7

Sorry if this is a dumb question but I find it harder and harder to find stuff around here anymore with people using the same keywords in their threads for ROMS and updates such as stock when it's actually a modified stock etc.
Anyway where is a stock root safe rom coming from ME7 to get to 4.3 or 4.4
I have SU set for root saver but anytime I try and go to the OTA I get a settings have stopped error.
Sent from my Galaxy Nexus using Tapatalk
N00dle said:
Sorry if this is a dumb question but I find it harder and harder to find stuff around here anymore with people using the same keywords in their threads for ROMS and updates such as stock when it's actually a modified stock etc.
Anyway where is a stock root safe rom coming from ME7 to get to 4.3 or 4.4
I have SU set for root saver but anytime I try and go to the OTA I get a settings have stopped error.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
Using an OTA, ME7 will update to MI1. That's rootable with Saferoot, so why worry about root saver?
MI1 will OTA to MJ7, which will OTA to MK2. Those are also rootable.
I'd recommend flashing a no-wipe MK2, which will get you to 4.3. That's available in this post.
You can't get to 4.4 yet since Verizon hasn't released it for our phones.
k1mu said:
Using an OTA, ME7 will update to MI1. That's rootable with Saferoot, so why worry about root saver?
MI1 will OTA to MJ7, which will OTA to MK2. Those are also rootable.
I'd recommend flashing a no-wipe MK2, which will get you to 4.3. That's available in this post.
You can't get to 4.4 yet since Verizon hasn't released it for our phones.
Click to expand...
Click to collapse
Thanks this is the info I was looking for and having trouble digging through the noise if you will.
I didn't realize I was 3 versions behind.
Sent from my Galaxy Nexus using Tapatalk

Verizon S4 NC5 build question

Hey guys I have been out of this for a while. I just got a replacement phone from verizon and it has NC5 build and not an mdk build. I cant seem to find a root for it. Is there one? also what steps should I do before rooting?
FlipFlop425 said:
Hey guys I have been out of this for a while. I just got a replacement phone from verizon and it has NC5 build and not an mdk build. I cant seem to find a root for it. Is there one? also what steps should I do before rooting?
Click to expand...
Click to collapse
There currently is no native root method for NC5 but you can downgrade partially back to MK2 and gain root.
Read through this thread and really take your time and make sure you do all the steps http://forum.xda-developers.com/showthread.php?t=2726868
Downgrade method is a little further down in the OP
Sent from my SCH-I545 using Tapatalk
Mistertac said:
There currently is no native root method for NC5 but you can downgrade partially back to MK2 and gain root.
Read through this thread and really take your time and make sure you do all the steps http://forum.xda-developers.com/showthread.php?t=2726868
Downgrade method is a little further down in the OP
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
If this is a new phone that I see has the knox app on it can nothing be done? I also attached my about phone screen
FlipFlop425 said:
If this is a new phone that I see has the knox app on it can nothing be done? I also attached my about phone screen
Click to expand...
Click to collapse
No you can go to that link I sent you earlier and downgrade partially and obtain root.
Sent from my SCH-I545 using Tapatalk
FlipFlop425 said:
Hey guys I have been out of this for a while. I just got a replacement phone from verizon and it has NC5 build and not an mdk build. I cant seem to find a root for it. Is there one? also what steps should I do before rooting?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2606501
decaturbob said:
http://forum.xda-developers.com/showthread.php?t=2606501
Click to expand...
Click to collapse
What a pain huh?
Stupid kit Kat update really clogged things up on here lol
Sent from my SCH-I545 using Tapatalk
Mistertac said:
What a pain huh?
Stupid kit Kat update really clogged things up on here lol
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
Under best of circumstances...people will mess up their phones from being lazy not to research before hand....but with nc5 and what you have to do.....been a steady stream.
sent by bajarom v2.2 kitkat
Yea this is crazy. I finally got it to install hyperdrive but am having problems with that bot being able to get back I into safestrap on reboot to install wife and super super fix

build VRUFNG6

http://www.droid-life.com/2014/10/1...date-with-knox-2-0-connectivity-improvements/
...Sigh. When will vzw pull their heads out of their..
Surge1223 said:
...Sigh. When will vzw pull their heads out of their..
Click to expand...
Click to collapse
Until they realize they are not doing their customers any favors, never.
I knew better. Got an MDK device, rooted it immediately and have been running CM ever since. [emoji41]
If you guys are talking about Knox 2.0...get used to it. Knox is being incorporated by Google in Android "L".
Remember, with all the hackers out there, the average Joe and Joan want their privacy secured...all the banking that is done from the phones now?
And also Verizon is the largest carrier for military and commercial contracts...to keep them and get more the phones have to be as secure as possible.
Anyone try to see if Towelroot works with this build?
I think they need to find another root method. Towelroot only works on kernels june 3 and below. I have no idea if it will work if you used it
I'm not upgrading. All flashaholics like me will DEFINITELY just wait for a possible exploit for NC5 than hope for the almost nonexistent chance there will be an unlock in the new firmware. Just my $0.02
Sent from an S4 Lost in the Echoe
SolidSnakeUS said:
Anyone try to see if Towelroot works with this build?
Click to expand...
Click to collapse
We have been able to use towelroot on the latest updates for the att S4, S5, and Vz S5 by flashing back the previous kernel, rooting, then reflashing the new unexploitable kernel. Vz S4 users will likely be able to do the same on NG6.
Sent from my SAMSUNG-SGH-I337 using XDA Free mobile app
Least they could have done was give us 4.4.4 at the same time.
Sent from my SCH-I545 using XDA Free mobile app
Anyone get this yet. What android version is it still 4.4.2
Does towelroot work on this update? I want to know before I take the plunge...
Sent from my SCH-I545 using Tapatalk
Downloading now. I don't care if I lose root. I'll test towelroot after the update.
MedleHed said:
Downloading now. I don't care if I lose root. I'll test towelroot after the update.
Click to expand...
Click to collapse
Towelroot is guaranteed not to work. A better option is to grab the update from your cache/fota folder and post so that we can make a workaround to keep root.
Yep id give it to muniz.
Theres no way im going through the drama we had last time.
Surge1223 said:
Yep id give it to muniz.
Theres no way im going through the drama we had last time.
Click to expand...
Click to collapse
Lol, I remember and don't blame you at all.
It's confirmed that towelroot doesn't work. The version is still 4.4.2. The first thing I noticed was the GPS toggle in the notification area is now a Location toggle.
Any method of rooting?
Now that Towelroot is out, is there any way of rooting on the latest version? Downgrading, flashing an image in Odin, etc? Or are we pretty much screwed until a work around is found?
asalkowskineo said:
Now that Towelroot is out, is there any way of rooting on the latest version? Downgrading, flashing an image in Odin, etc? Or are we pretty much screwed until a work around is found?
Click to expand...
Click to collapse
There is a very good chance that the kernel swap method will work on this latest build.
Someone just needs to grab the ota from their device. We'll take the kernel from the new update and package it into an Odin flashable .tar. You'll then flash the old NC5 kernel after taking the update, re-boot and root using towelroot, then reflash the new kernel. No guarantees but this method has been working on all of the latest Sammy updates.
muniz_ri said:
There is a very good chance that the kernel swap method will work on this latest build.
Someone just needs to grab the ota from their device. We'll take the kernel from the new update and package it into an Odin flashable .tar. You'll then flash the old NC5 kernel after taking the update, re-boot and root using towelroot, then reflash the new kernel. No guarantees but this method has been working on all of the latest Sammy updates.
Click to expand...
Click to collapse
I could give you guys the OTA if you tell me how to do it. I'm by no means an expert at rooting, but I've had a few years experience. So basically you'll modify the new kernel to allow downgrading to NC5, root, then update again? I had Towelroot before I updated, had OTA survival mode enabled in SuperSU, and had it installed as a system app, but I still lost root on this latest update. :crying:
muniz_ri said:
There is a very good chance that the kernel swap method will work on this latest build.
Someone just needs to grab the ota from their device. We'll take the kernel from the new update and package it into an Odin flashable .tar. You'll then flash the old NC5 kernel after taking the update, re-boot and root using towelroot, then reflash the new kernel. No guarantees but this method has been working on all of the latest Sammy updates.
Click to expand...
Click to collapse
When they finally block us from doing this, it will be a dark day lol.

[new update] i545vrugof1

There is now a method to update while keeping root. See here
source: http://www.androidpolice.com/2015/0...xy-s4-with-stagefright-patch-and-other-fixes/
this is still 5.0.1 (hence the LRX22C build number) but it fixes the Stagefright vuln as well as other stuff
or it's supposed to fix stagefright... lol. good ol sammy.
anyway, if you want root, don't take this update. be patient.
let the discussion begin!
Hope nobody update this before someone capture it, patience..
Sent from my SCH-I545 using XDA Free mobile app
EdrickMG said:
Hope nobody update this before someone capture it, patience..
Sent from my SCH-I545 using XDA Free mobile app
Click to expand...
Click to collapse
Weird...I never accepted an update but just checked my build number and sure enough....LRX22C. No wonder I was able to root with Kingroot 2 weeks ago and cannot now....
kauaigs said:
Weird...I never accepted an update but just checked my build number and sure enough....LRX22C. No wonder I was able to root with Kingroot 2 weeks ago and cannot now....
Click to expand...
Click to collapse
eh. that didnt really matter.
i have a feeling the conflict with kingroot on oc1 was samsung's auto-updating SELinux stuff. no user intervention, it just runs in the background. although those updates make the samsung keyboard not exploitable. lol.
you have options: root, or have a secure phone. you can't have both.
skepticmisfit said:
eh. that didnt really matter.
i have a feeling the conflict with kingroot on oc1 was samsung's auto-updating SELinux stuff. no user intervention, it just runs in the background. although those updates make the samsung keyboard not exploitable. lol.
you have options: root, or have a secure phone. you can't have both.
Click to expand...
Click to collapse
Ah, ok - thanks. I've been trying to re-root since I had to do an odin restore, but Kingroot is unsuccessful...
kauaigs said:
Weird...I never accepted an update but just checked my build number and sure enough....LRX22C. No wonder I was able to root with Kingroot 2 weeks ago and cannot now....
Click to expand...
Click to collapse
LRX22C means nothing here (it just signifies 5.0.1, which is what most people are already running). It's what's at the tail end of the build number that counts - OF1. Reread the thread title, the OP and the linked article.
mike.s said:
LRX22C means nothing here (it just signifies 5.0.1, which is what most people are already running). It's what's at the tail end of the build number that counts - OF1. Reread the thread title, the OP and the linked article.
Click to expand...
Click to collapse
DOH....missed that. Thanks!
What's StageFright?
So being the n00b that I am, just to clarify, there is no functioning root for the Verizon Galaxy S4 with the specs i have (shown in my updated signature) short of using Odin and reloading 4.0?
Sir_Eagle said:
What's StageFright?
Click to expand...
Click to collapse
i'll try and sum it up
it was a security vulnerability discovered by jduck (Josh Drake) and, basically, someone can send you a malformed video through the MMS protocol and basically, malware would leak into your phone through that video message if it automatically downloaded.
the exploit specifically targets a system lib called "libstagefright.so" (clever name, eh?) and that library handles everything related to video playback. i think.
if you're not going to install of1, the best way to patch it right now would be to disable automatic downloading of mms messages through your messaging client. chompSMS has its own dealio with stagefright tho, and i've been using chomp for forever, so, yea.
storo1975 said:
So being the n00b that I am, just to clarify, there is no functioning root for the Verizon Galaxy S4 with the specs i have (shown in my updated signature) short of using Odin and reloading 4.0?
Click to expand...
Click to collapse
uhm
well
if you took oc1 via ota, you could try to root using kingroot desktop, that seems to have mixed results.
if you have the nk4 bootloader, you can downgrade to nc5 and root that using towelroot (easiest method ever)
you can't downgrade to kitkat if you took oc1 via ota
Bren caught the update, but is still uploading it. Hopefully kingroot or something else will get root for others.
Sorry guys phone died while re uploading bout to upload
Bren123 said:
Sorry guys phone died while re uploading bout to upload
Click to expand...
Click to collapse
you're uploading that giant file from your phone???
we have a new legend here
Sent from my SCH-I545 using Tapatalk
Bren123 said:
Sorry guys phone died while re uploading bout to upload
Click to expand...
Click to collapse
Any luck?
i just uploaded of a copy update.zip in the fota folder to google drive here. Is that what is needed?
bangdosa said:
i just uploaded of a copy update.zip in the fota folder to google drive here. Is that what is needed?
Click to expand...
Click to collapse
yup.
good job.
you will be credited for this. not sure if bren uploaded his zip yet but yea this is apparently what the update looks like.
all we need now is some pre-rooted ROMs
Sent from my SCH-I545 using Tapatalk
Hey, can someone cut out JUST the stage fright fix and make it flashable for ROMs?
XxD34THxX said:
Hey, can someone cut out JUST the stage fright fix and make it flashable for ROMs?
Click to expand...
Click to collapse
honestly, you could "fix" stagefright yourself by disabling automatic downloading of mms in your app
or if you use chomp, they already have their own fix in place
Sent from my SCH-I545 using Tapatalk
I just happend to wake up and see a software update getting dl'd...it was already at 60%. I went I went into DEFCON 5 freezing, and disabling and force closing stuff....wheew! Close one!

Categories

Resources