yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S 4] lookimback:
I just did this and it works. First it just updated from MI1 to MJ7. Then I decided I'd give it MK2 shot. It worked flawlessly. I am now on MK2 with root. :)
[Verizon Samsung Galaxy S 4] Bad Bimr:
Best way to do it is trade me your MDK phone for my ME7 phone. Then all is good. :)
[Verizon Samsung Galaxy S 4] harpdoc:
After doing steps 6-12, when I click on "Software Update" in Settings, it kills Settings and I get error message "Unfortunately Settings has stopped." I had already done steps 1-5 when MI1 came out. I'll try it again from scratch and see what happens. :(
[Verizon Samsung Galaxy S 4] Jayrod76:
With the S4,Sammy has killed the ability to go back to previous updates. For those on MDK,You really should think very hard about moving to any other builds. Loki will go bye bye.. No AOSP/AOKP,Etc. Sure,ME7 has SS but you are stuck with TW,at least until a Kexec solution is found. If that is what you like,go for it.

Just my .02

Sent from my Platyraptor extreme ultra maxxxx 4gLTE/GSM/ABC/123 Nick Knack Pattywack Ermegherd GED, MD,RNA,DNA,YMCA Edition S4! Via the 4th dimension....NOW RUNNING CARBON
[Verizon Samsung Galaxy S 4] cindylee60:
I can't wait to get off work tonight and try this!! :)
[Verizon Samsung Galaxy S 4] tech_head:
Did you freeze the update app??

Check to see if anything is frozen.

That is what happens when the FWUpgrade app is frozen.
[Verizon Samsung Galaxy S 4] open1your1eyes0:
Anyone with a VRUEMJ7 device willing to test if the VRUDMI1 factory image is still flashable for them? We currently don't have the new one so would like to check if this works or not.

Please note that flashing older factory image on top of newer MAY render your device unusable as no way (yet) to restore back to the newer image. ONLY test in the case you are willing to go back to Verizon or Samsung for a replacement if something goes wrong. I will not be responsible if this test renders your device soft-bricked. Please test/continue at your own risk only!

VRUDMI1 factory image can be found here: http://xdaforums.com/showthread.php?t=2301259

Disregard, confirmed that it will soft-brick! Working on a solution.
[Verizon Samsung Galaxy S 4] carzaddict:
I know this is a silly thing to say, but I am assuming MJ7 is is JB 4.3?

Im on stock rooted MI1

Im going to wait until a few more people do this. I am traveling for work at the moment and cant afford to brick my phone :eek:
[Verizon Samsung Galaxy S 4] skiddingus:
Yes it is 4.3.
[Verizon Samsung Galaxy S 4] urcboss07:
I got a replacement s4 today and the build number is ME7, I think Verizon or Samsung flash every phone with newer update than mdk.
[Verizon Samsung Galaxy S 4] pjrmax403:
Custom

After rooting with de la vega, phone shows custom again....should I try the OTA MJ7, does anyone know what I should expect?

Followed instructions to the "T" twice.

Thank you for any advice.:good:

P.S. May have had Super SU Survival mode on......just awoke from nap......probably shouldn't be doing this now;)
[Verizon Samsung Galaxy S 4] cindylee60:
YAY!!!!! I'm updated and have root!!! Thank you thank you thank you!

I love it when I get exactly what I want :)

it was fun and easy....I snuck did it at work :)

(buying you a beer)
[Verizon Samsung Galaxy S 4] bairste:
Thanks for the work on this. I had been trying to take this update and it is here.
[Verizon Samsung Galaxy S 4] Poofster:
I'm on ME7 using SafeStrap running Hyper 10...froze some apps and installed Xposed...do I need to switch to stock or unfreeze or delete anything before I Odin to MI7 in the first step? Thanks

Nevermind...first page of odin explains it
[Verizon Samsung Galaxy S 4] Tomsgt:
Nice work buddy. Was trying to get a hold of beans to send me this fill yesterday to try this every same thing out myself LOL. Looks like you tested it first :)
[Verizon Samsung Galaxy S 4] skiddingus:
My phone showed custom and the OTA was sucessful. I flashed the "no wipe" MI1 yesterday and took the OTA. The OTA was failing with all of my attempts to keep root before flashing the "no-wipe" file. I wish it wouldn't have worked now. I have lost root at the moment.

---------- Post added at 07:37 PM ---------- Previous post was at 07:35 PM ----------

Has anyone tried to go back from MJ7 to MI1 yet? I'm tempted to try it but I hate to risk it today. I'm assuming you would just odin flash the no-wipe factory image, correct?
[Verizon Samsung Galaxy S 4] spc_hicks09:
I've been told you cannot go back to MI1.
[Verizon Samsung Galaxy S 4] Tomsgt:
Video incoming as soon as I can edit it.
[Verizon Samsung Galaxy S 4] harpdoc:
tech head, thank you!! I totally forgot that I'd frozen Samsung Updates a while back. Update is downloading as we speak.
[Verizon Samsung Galaxy S 4] JaeKay:
Can anyone with root provide the new Internet. Apk? Thanks ;D
[Verizon Samsung Galaxy S 4] pjrmax403:
Kept Root

I took the OTA anyhow.................h3ll yes it worked. Rebooted twice and still have Root on MJ7:good::good:
[Verizon Samsung Galaxy S 4] KB Smoka:
Downloading the update now.....Will report back when it's done.

***Update***

YES, YES and YES....Updated with root. Thanks to everyone involved.

KB
[Verizon Samsung Galaxy S 4] tech_head:
Just remember that thanks thing on the sidebar. :cyclops:
[Verizon Samsung Galaxy S 4] harpdoc:
The update downloaded, but then I got a "Software update unsuccessful" error. Unfroze all apps and tried again, but same thing. I'm at a loss.
[Verizon Samsung Galaxy S 4] chrismyu:
I have just updated using the directions in the OP. Works GREAT!
[Verizon Samsung Galaxy S 4] portscan:
Mine will not root using the stock MI1 image. It will only root using the Root_De_La_Vega MI1 image.
[Verizon Samsung Galaxy S 4] haunting:
Worked great

Thanks!
[Verizon Samsung Galaxy S 4] Tomsgt:
Here is my video on these steps. http://youtu.be/vfxW4-8Wflg Can you please post this in your OP thanks

RootJunky / Tomsgt
[Verizon Samsung Galaxy S 4] portscan:
Using root de la vega image and tried doing it by flashing from recovery manually. It seems to be going through now. Currently on patching system files.. No turning back now lol. Guess we will see if root sticks. Funny it wouldn't take OTA with the param file change. Oh well, if this works all is good.
[Verizon Samsung Galaxy S 4] mpgwrx:
I can confirm this worked for me! I was rooted stock MI1 and now I'm updated with root. Only thing now on boot up the Samsung logo has an unlocked pictured below it. Is this OK?
[Verizon Samsung Galaxy S 4] ToastyZ71:
Yep, won't hurt a thing, and you may not always get it.
[Verizon Samsung Galaxy S 4] portscan:
I have the new internet apk backed up with ES. You still need it?

---------- Post added at 10:15 PM ---------- Previous post was at 10:14 PM ----------

I am happy, but VERY surprised they removed the ongoing wifi notification.. I HATED that thing! Thank God someone listened to our cries..
[Verizon Samsung Galaxy S 4] open1your1eyes0:
OP has been updated with much more detailed and clear instructions now that it is a confirmed working method :good:
[Verizon Samsung Galaxy S 4] portscan:
Here is the Internet apk in a zip file.
[Verizon Samsung Galaxy S 4] portscan:
I don't like this right here.. Anything via SQL we wanna do seems blocked by KNOX. What happens if you freeze KNOX with titanium?
[Verizon Samsung Galaxy S 4] Poofster:
When I Odin to mI1 do I have to remove my sd card? Or will it be ok
[Verizon Samsung Galaxy S 4] anthony92170:
Please forgive me but if you take this route can safe strap work or you are stuck on rooted 4.3. Also can exposed work with this
[Verizon Samsung Galaxy S 4] portscan:
In order to do the root you have to remove the sd card.

---------- Post added at 11:28 PM ---------- Previous post was at 11:25 PM ----------

Haven't seen anyone install SS yet, I don't think anyway. There is currently no tar image to odin back if it doesn't work. I wouldn't trust it right now. Hashcode may be the one to ask for pure clarification though. As far as I know we can't go from MJ7 back to MI1 and without that MJ7 tar file you would be hosed for sure if it bricked.
[Verizon Samsung Galaxy S 4] JaeKay:
Thanks. I'm gonna see if it works on ME7
[Verizon Samsung Galaxy S 4] mastridonicus:
Running MDK

I am running MDK and all that, but I've never flashed a custom ROM or used more than root access.

Is there a way to just flash the stock bootloader so I can take the OTA to get to 4.3?
[Verizon Samsung Galaxy S 4] FAUguy:
Mine is running MDK with CWM Recovery.

I don't mind losing CWM, if the phone can be updated to Android 4.3 with Root access.

Would this process work, or could it soft brick the phone since CWM is installed instead of the stock bootloader?
[Verizon Samsung Galaxy S 4] Crawshayi:
I'm currently on stock ME7 rooted and considering to do the steps to get to MJ7 but have a few quick questions... should I unfreeze all my bloat before Odining the MI1 or will it just overwrite what TiBu did? In fact should I delete all root apps before doing this like Xposed, Adaway, etc?
[Verizon Samsung Galaxy S 4] FAUguy:
It turns out this process worked fine more me. The only thing I did first was to flash the stock MDK TW ROM and PIT file, which removed the CWM.

Then I followed the steps in post #1. Now have 4.3 installed and root has been kept.
[Verizon Samsung Galaxy S 4] Tada10:
How can I disable this system blocking crap? :)

Sent from my Galaxy S4
[Verizon Samsung Galaxy S 4] Tada10:
Just a heads up. I used Triangle Away to get rid of the Custom Logo on boot...it got rid of it and made everything official but side effect is it also got rid of my root in 4.3.....oh well took one for the team.

Sent from my Galaxy S4
[Verizon Samsung Galaxy S 4] anthony92170:
Just to let you know that xposed framework 2.3 works and so does wanam. I tried safe strap keeps getting blocked.
[Verizon Samsung Galaxy S 4] kevin527:
sd card

I did all the steps and I'm rooted but my external SD card won't mount. Any suggestions
[Verizon Samsung Galaxy S 4] portscan:
So basically Samsung got smart and placed security in place after the boot. Hash had SS run the hijack before the boot. They put security in place after boot up, so anything that tries to exploit will be blocked. Clever! I can confirm that SQL editor gets blocked when you try to look at settings.db and you confirmed SS triggers the block notification as well. Looks like some trickery work for our amazing dev team here. I am sure someone will crack it in just a matter of time.
[Verizon Samsung Galaxy S 4] k1mu:
My phone is in a weird state.

Started from stock MI1, SuperSU Pro in recovery mode ready to go.

Now, after the OTA, I have this:

shell@jfltevzw:/ $ ls -l /system/xbin/su
-rwsr-sr-x root root 100452 2013-10-18 20:47 su
shell@jfltevzw:/ $

Cool! That means that SuperSU was able to keep the 'su' binary setuid root. (The 's' in 'rws').

But, when I try to actually use it:

shell@jfltevzw:/ $ su
/system/bin/sh: su: can't execute: Permission denied
126|shell@jfltevzw:/ $

Something's blocking access to the 'su' binary. SELinux getting in the way?

126|shell@jfltevzw:/ $ ls -Z /system/xbin/su
-rwsr-sr-x root root u:object_r:su_exec:s0 su
shell@jfltevzw:/ $

Reboot hasn't fixed this. And, the device is showing "Custom" status.

Any ideas? I'm pretty sure that I'm screwed at the moment.

-------------------

Further on this - apparently there's a working 'su' binary in /system/bin/.ext/.su which either Voodoo OTA Rootkeeper or SuperSU stashed away.

When I execute that, I get a "# " prompt. Woo hoo!

Oh, but not so fast. If I try "# mount -o remount,rw /system I get

"mount: Permission denied"

The file "/file_contexts" has the following line:

/system/xbin/su u:object_r:su_exec:s0

That context is why I'm not able to execute the /system/xbin/su file.

I'm going to go post a few questions about this over in the Q&A forum.
[Verizon Samsung Galaxy S 4] loonie01:
Anyone get this to install?
[Verizon Samsung Galaxy S 4] lazer9:
Yikes! Thanks for this info. Seems I will be holding out a bit on upgrading via this method & root as I don't want to lose the capability of a recovery to flash roms now or in the future in case a new exploit allowing SS capability isn't found.
[Verizon Samsung Galaxy S 4] bparent:
Running stock ME7 with root

I am also running stock ME7 with root, no frozen apps, etc. Do I need to ODIN to M1 first?
[Verizon Samsung Galaxy S 4] jwhistler:
I would also be interested to know if KNOX can be safely frozen and/or uninstalled via Titanium Backup...
[Verizon Samsung Galaxy S 4] mpgwrx:
I froze all the Knox stuff I could find with Titanium but I still get the security alert from Knox! Weird...also, I'm not sure if it was ok to freeze all the Knox crap but I did anyway and no ill effects so far.
[Verizon Samsung Galaxy S 4] topaz330:
stupid question of the day... my baseband version shows i545vrumdk but my build number is jdq39.i545vruame7. So am I still ok to use this method to keep root? Also any reason I should update my radio?
[Verizon Samsung Galaxy S 4] matt1733:
IF you have use safestrap this method will retain root when you update but if you have mdk as your base you'll lose your loki'd bootloader forever, which mean no cyanogen mod and other roms with different kernels
[Verizon Samsung Galaxy S 4] mrcrusha829:
This method worked for me as well... Only thing is I had to hard reset before starting the process from the beginning with ODIN of MI1. Just wanted to let others know that your Titanium backups may not work on some. Had to reinstall apps from the market for them to work.... guess it is expected as we are moving to a different version of the OS.
[Verizon Samsung Galaxy S 4] topaz330:
so if i upgrade my modem to the latest MJ7 I should be ok then? I use twrp
[Verizon Samsung Galaxy S 4] lazer9:
From my understanding starting 2 pages back and at the top of the last page, safestrap no longer works after upgrading and via this root method with 4.3 and will need modified to even access recovery anymore.

Edit: My bad, I missed the part where you said "Just the modem" and was thinking about the OP of this thread and rooting to 4.3. Yes, you can upgrade the modem ONLY and retain your recovery, ect...
[Verizon Samsung Galaxy S 4] Jayrod76:
Yes.I'm running it on my MDK.

Sent from my Platyraptor extreme ultra maxxxx 4gLTE/GSM/ABC/123 Nick Knack Pattywack Ermegherd GED, MD,RNA,DNA,YMCA Edition S4! Via the 4th dimension....NOW RUNNING CARBON

---------- Post added at 11:23 AM ---------- Previous post was at 11:19 AM ----------

And with the changes inherited in 4.3 ( SELinux stepped up) and Sammy's Knox ,yeah...the future is very bleak . Definitely am never going carrier again. Lucked out with having Loki...don't plan on tempting fate the next go round.

Sent from my Platyraptor extreme ultra maxxxx 4gLTE/GSM/ABC/123 Nick Knack Pattywack Ermegherd GED, MD,RNA,DNA,YMCA Edition S4! Via the 4th dimension....NOW RUNNING CARBON
[Verizon Samsung Galaxy S 4] anthony92170:
I used file explorer and removed Knox Verizon security and other bloat no ill effects yet and I don't get security warning. I tried titanium didn't work. Also was able to boost sound change start up and shut down sound. I think I know why SAFE STRAP isn't working I'll bet it's because this is one not deodexed.

---------- Post added at 11:42 AM ---------- Previous post was at 11:39 AM ----------

Not too bad for 1st run ant was at 60% when started
[Verizon Samsung Galaxy S 4] bucklyv:
Can someone who has taken the MJ7 update do a system dump and post the files...??? I am on MDK and have a working copy of the ECHOE 5.0 rom port that is 4.3, based on the i9505 ported to AT&T, but I can't get SMS/MMS outgoing messages to work. I think if I had the system, modules, libraries, and framework files from the VZW 4.3 update, then I could patch it and get everything working, providing a working 4.3 ROM for VZW.

Though I would first need to get a few devs to say it was okay, as none of the work would be my own.

Cheers!
[Verizon Samsung Galaxy S 4] kzoak82:
Worked, Thanks! Just one question, do we leave survival mode enabled or disabled after the update? Sorry, if this is a stupid question.
[Verizon Samsung Galaxy S 4] jds3118:
Here you go lol I'm trying the same lol I'm having trouble viewing the build.prop though :)

http://xdaforums.com/showthread.php?t=2502591
[Verizon Samsung Galaxy S 4] s44:
No one on MDK should *ever* take or flash an official update to *anything*.

It's amazing that this still has to be said.

Yeah, just flash the one *without* NON-HLOS. That's not worth the trouble, the modem.bin is enough.
[Verizon Samsung Galaxy S 4] bucklyv:
jds,

I've been through that thread already... and have downloaded the update file. But that update file has .p files (patch files) that the updater script uses a key to unzip and install.

What I need is a dd image dump of a VZW GS4 that took the update as an OTA. In that case all of the .p files would have already been applied and I can pull the required system files (build prop, framework, etc...) and use only those needed to get the MMS outgoing services working... without loosing root, custom recovery, or any other MDK advantages, but still getting a working 4.3 ROM.
[Verizon Samsung Galaxy S 4] jds3118:
How about this 2nd and 3rd posts

http://xdaforums.com/showthread.php?p=46945003
[Verizon Samsung Galaxy S 4] Surge1223:
I made a stock root deodexed version but since I cant test it I wasnt going to post it, but I guess I can upload it for devs to use
[Verizon Samsung Galaxy S 4] bucklyv:
Surge,

That would be awesome! Thanks.
[Verizon Samsung Galaxy S 4] aznjosh:
How long did it take you guys to install the 4.3 update? My phone has been sitting on the software update screen for over 30 minutes now.
[Verizon Samsung Galaxy S 4] d1v:
Broken recovery???

I'm hoping for some help from the tech wizards out there.

I'm on MI1 and I believe I have a corrupt recovery. I'm not even sure if that is possible but here is what I am seeing and how I think I created the situation.

A few weeks ago, after upgrading to MI1, I stupidly attempted to apply TWRP recovery. It obviously didn't work and I was stuck in ODIN. I manually forced it to bypass and boot normally. All has been well and I haven't thought anything about it.

I attempted to upgrade to MJ7 using procedure documented above and it failed because it was stuck in ODIN. I backed out like I did before and I'm running again...just not in an upgraded state.

If I did jack my recovery, what if any, is the best way to fix it?

Any ideas? Thanks in advance for your help!
[Verizon Samsung Galaxy S 4] kyls2010:
Agreed, I am also unclear. I don't think it's a stupid question at all.
[Verizon Samsung Galaxy S 4] harpdoc:
Started over from step 1 and this time we have a winner!
[Verizon Samsung Galaxy S 4] k1mu:
It's OK to leave it enabled.
[Verizon Samsung Galaxy S 4] gunnermike:
Anybody have just the radio?
[Verizon Samsung Galaxy S 4] gunnermike:
Thanks! I always forget about the general section. I even said to myself I should look there and just didn't.
[Verizon Samsung Galaxy S 4] heath2805:
No prob. Just flash mj7 in recovery and your good :)
[Verizon Samsung Galaxy S 4] rdtapt:
So, if someone can clarify for me... If I tried this after updating to MJ5 and now get "firmware upgrade encountered an error" and am unable to boot into recovery, I am pretty much out of luck until there is an ODIN flashable .tar file, correct? I hate myself right now.

SOLUTION- I flashed the modem file in the second post of this thread and I boot up fine now.

http://xdaforums.com/showthread.php?t=2502591
[Verizon Samsung Galaxy S 4] DarkMenace:
Doesn't work! Upgraded then received a bunch of gmaps errors and system process not responding. Let the device sit for a little bit then noticed a Knox Security error and then lost SuperSU abilities. Application doesn't even work. Upgraded from VRUAME7. Now I'm stuck on a nonrooted device. I might as well do a warranty swap and complain of errors since there isn't a rooted Odin flash.
[Verizon Samsung Galaxy S 4] spc_hicks09:
Yeah, might as well commit warranty fraud....... /s
[Verizon Samsung Galaxy S 4] Surge1223:
Might as well try this now then right? http://ubuntuone.com/2SwsmPTW1jBYapwksa5AkR

---------- Post added at 03:27 AM ---------- Previous post was at 03:08 AM ----------

You should have seen how long it took me to decide where id post them lol
[Verizon Samsung Galaxy S 4] hexom:
So I'm on version MI1 and I am rooted with no roms and I followed the instructions the OP posted and it fails each time. I even tried to manually install the 4.3 update how Tomsgt123 was instructing on his Youtube video and it still failed.

I copied the prepare_param.sh file over to the bin folder, overwrited it, made sure the permissions were checked accordingly and ran the update I received. That didn't work, so I tried to manually install the update and that didn't work either.

Any idea what I may be doing wrong or why it's not working?
[Verizon Samsung Galaxy S 4] guharajdeep:
Same for me... So i just ODIN ed the stock mi1 and took the update... Lost root however but i am sure its coming "soon"
[Verizon Samsung Galaxy S 4] k1mu:
Without knowing why it's not working, we're going to have a hard time guessing. You'll need to watch the update to see what error message is displayed; that will tell you what you haven't restored properly. Or use the "otachecker.txt" shell script that I posted to see what's missing or not intact.

For example, after restoring your prepare_param.sh file, open a terminal emulator window, and type "sha1sum /system/bin/prepare_param.sh". It should display cea94a424d264227c4e770391e8c41fab9b036cd - if not, then that file wasn't properly restored.

To run the attached checker, push it to your external SD card, then use "sh /mnt/extSdCard/otachecker.txt" - if all is as expected, you'll see no output. It'll tell you if any other files have been tampered with or are missing.
[Verizon Samsung Galaxy S 4] mrcrusha829:
Hard reset and start from the beginning... I was getting errors too until I did this.
[Verizon Samsung Galaxy S 4] kasim1:
Hi guys, just did a VRUEMJ7 upgrade "with root", now i can't send any MMs,

tried to clear cache but that didn't work.

Any1 else having same issue?
[Verizon Samsung Galaxy S 4] carzaddict:
i am stock and rooted as well....i was trying to avoid doing a hard reset, theres no easy way of backing up and restoring 100% (titanium does a good job, but not the best)
[Verizon Samsung Galaxy S 4] ffd173:
4.3 upgrade success!!

OK. I was on MI1, stock rooted. I received the update notice for MJ7. I used the method in the OP by replacing the prepare_sh file as instructed and using supers to keep root. I then let the update run and when all done I am now on MJ7 4.3 and ROOTED!!

Thanks a bunch for this great find!! It couldn't have been easier!

:D
[Verizon Samsung Galaxy S 4] dbreno:
I'm having problems, I keep getting update failed during the install after the boot...based on progress bar it was maybe 15-20% before the Android had his heart attack. . I have verified the SHA signature of the prepare_param.sh file and it is correct. Permissions are correct (755). I am on MI1 firmware with root using the "Root de la Vega" method. I even tried to remove safestrap to see if that mattered but it didn't (I had not used any ROM's with it yet).

Any thoughts on what to try? Is there any logging of the update to see where it is failing?

thanks!
[Verizon Samsung Galaxy S 4] carzaddict:
I bit the bullet and did the update......stock and rooted....it went successful! im so happy to no longer have that wi-fi notification anymore!
[Verizon Samsung Galaxy S 4] themusicmonkey:
I can't change the permissions of the file with Root Explorer. Can anyone help me out on what I need to do?

---------- Post added at 09:28 AM ---------- Previous post was at 09:22 AM ----------

Never mind. If you have this issue, just recopy the file to system/bin/ and change the permissions then. It has to do with the default, read only status of Root Explorer
[Verizon Samsung Galaxy S 4] bast525:
Has anyone upgraded directly from ME7 and kept root, without taking the MI1 update first?
[Verizon Samsung Galaxy S 4] k1mu:
You can't update to MJ7 without first being at MI1.

You could, I guess, use the MJ7 "no wipe" ODIN flash, but then you'll probably lose root.