yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S 4] redwings73:
Need some help here! I used this method to upgrade to rooted MJ7 last week and after a day or so, I completely lost the ability to connect to wifi.... Everything else worked fine. I finally came Verizon and they decided it was worth a warranty replacement.

I got the replacement phone yesterday and went through the MJ7 root prices again... And everything worked fine, including wifi, until I got home. Now, I've lost wifi again. I get a light green wifi toggle rather than the bright neon green color and the "on" button in the wifi settings says on but it's grayed out and won't go to off.

It might be when I go from one wifi to another when it goes out. The first phone connected to wifi at home then the next morning wouldn't connect at all at work or ever again. The opposite happened today, connected at work then never again once I got home.

I've uninstalled adaway and Xposed thinking one of the other was the problem.

Any clue to what could be causing this and how to fix it?

Can I perform the MJ7 root process again to see if that gets wifi back? How would I go about that?
[Verizon Samsung Galaxy S 4] jimbob_sf:
I got stuck in between De La Vega and the OTA. So, I repeated the whole process and it worked without issue, except.... I lost root. I had root before the update to MJ7 and purchases SuperSU pro and had survival enabled. The only thing I did differently was I used Kies to apply the update. I'm guessing I'm up a freaking creak, but does anyone know if using Kies would mess this process up? I used Kies because I install it to get the most current drivers (I'm also on Win 8.1 x64) and the OTA failed the first time.

Anyone?
[Verizon Samsung Galaxy S 4] heath2805:
Currently there is none . There are kernel issues with the new 4.3 kernel. Last I read Nitro is trying to get it to work. Apparently Verizon has made this difficult with knox.
[Verizon Samsung Galaxy S 4] dhemke17:
Thanks for the reply, I just pulled the rom and am going to get to work on getting it going. I see the kernel issue and am going to see what I can do to get around that.
[Verizon Samsung Galaxy S 4] heath2805:
Thanks for looking into it. Glad to hear other devs are trying to figure this out. Heres what Nitro has, its available here http://www.elementalxdesigns.com/ec...ion-4-3-MJ7-Alpha-MDK-users&p=10178#post10178
[Verizon Samsung Galaxy S 4] wowthatisrandom:
Me and [MENTION=994064]scuccia[/MENTION] got everything(4G data, mms in/out, sms in, phone calls) but outgoing texts working. we used a i9505 rom, with ktoonz 11/4 kernel and restored saved apns from stock MDK rom. after about an hr of messing w outgoing texts we gave up.

what we did: http://pastie.org/private/bv3bnpaghlarazlytfpxrq
[Verizon Samsung Galaxy S 4] travisjshepherd:
Thinking about using my wife's upgrade to get a different phone, and give her my s4 rooted mj7. If I factory reset will I loose root?
[Verizon Samsung Galaxy S 4] permafrost91:
Don't know what I did but now it worked.
[Verizon Samsung Galaxy S 4] kasim1:
I did a factory reset and my root stayed in Place :good:
[Verizon Samsung Galaxy S 4] Jsyme222:
WIFI Tehter

I don't know if you've noticed it yet but here is a link to get wifi tether on MJ7. I can vouch for this method as I am currently using it.

http://xdaforums.com/showthread.php?t=2512981

---------- Post added at 09:46 AM ---------- Previous post was at 09:41 AM ----------

Have you attempted a hard reset? You will be able to keep root through a hard reset and I would try that first.
[Verizon Samsung Galaxy S 4] redwings73:
I have not because I was worried I woukd lose root access....

So, I can go to accounts/backup and reset/factory data reset and keep root?... Or is a hard reset different?
[Verizon Samsung Galaxy S 4] Jsyme222:
If you turn off the phone and boot into recovery via the volume up, home, and power button all at once, you can run a factory reset and you will keep your root. I have done this several times successfully.
[Verizon Samsung Galaxy S 4] Powell730:
Ok, I'm a little confused... I've read through the post but didn't find anything. I'm on me7, rooted w/ twpr, running hyperdrive, I'm not using safestrap...

So should I follow the steps in the op or should I just wait for someone to make a rom of the new mj7 that includes root?
[Verizon Samsung Galaxy S 4] cr4ck3r4lif3:
You should wait or I believe you'll lose your custom recovery
[Verizon Samsung Galaxy S 4] heath2805:
Yep, you should wait. You lose MDK and theres no going back. TW 4.3 is definitely not worth losing a custom recovery. Besides 4.4 is coming to AOSP builds soon.
[Verizon Samsung Galaxy S 4] Jsyme222:
How did you get TWPR on ME7 without using safestrap?
[Verizon Samsung Galaxy S 4] Powell730:
Rooted before me7 came out, installed my custom recovery. I never took the ota me7, I just waited until someone released the rom rooted (like I'm gonna do to get mj7).
[Verizon Samsung Galaxy S 4] heath2805:
Another words you must have a MDK version phone rooted via loki. Thats the only software version with a work around custom recovery. I'm there too man. Looks like a someone released a MJ7 base build already but I'm going to wait to see if its safe to flash because the kernel for TW 4.3 has issues with knox lol

Sent from my SCH-I545
[Verizon Samsung Galaxy S 4] Powell730:
That sounds more accurate yeah lol... It's been so long since I did it I didn't remember all the steps, just remember rooting before me7 and not taking the ota
[Verizon Samsung Galaxy S 4] jcwilliams:
This guide worked perfectly for me! Thanks!
[Verizon Samsung Galaxy S 4] Droidatar:
same boat here, will wait patiently.
[Verizon Samsung Galaxy S 4] tech_head:
Just be careful with things like Xposed and other modes you can do on root alone.

If you bugger the phone, you will be in a state where you lose root if you need ODIN to recover.

I'm waiting to move from MI1 until root is achieved on MJ7.

I tinker and have had to reflash MI1 once.
[Verizon Samsung Galaxy S 4] budding_developer:
I ended up going a completely different route -- rooted, then flashed over the stock ROM with a multi-carrier ROM & kernel, then went to AT&T's GoPhone plan. Got tired of those humongous phone bills!

I wrote a guide on how I did it, complete with links to everything -- come take a look! It's at --> http://xdaforums.com/showthread.php?p=47330320#post47330320
[Verizon Samsung Galaxy S 4] Zelmo88:
worked great for me, just follow instructions closely! And YES, you really do need to flash the MI1 system file in Step 1 even if you've already done steps 1 and 2!
[Verizon Samsung Galaxy S 4] JeeperDon:
Another satisfied customer here. Only hiccup was getting an OTA fail on the first try, and popup said I had a 410 error. I powered off/on redid the OTA and it downloaded and installed fine. Root still works.
[Verizon Samsung Galaxy S 4] scheirere:
A couple quick questions for the gurus and/or people that have sucessfully done this trick....

First, I believe my build number is MDK, from what I can tell under system settings. Should I download the VRUDMI1 file this thread's instructions suggest, or the VRUDMDK file that the linked thread suggests? I'm kinda confused on this and don't want to mess things up!

Secondly, If I do this, can I still run all my old ROMs/Backups or will they not work on the new build type?? I'd like to try the factory 4.3 rom with support for my Galaxy Gear watch but don't want to loose the ability to run some of the other ROMs if I would like. Any help is greatly appreciated!!
[Verizon Samsung Galaxy S 4] k1mu:
If you have MDK and update past that, you will no longer be able to use a custom recovery and will only be able to use Safestrap-compatible ROMs. All of your backups will be unusable until someone breaks the later bootloader.
[Verizon Samsung Galaxy S 4] steveojp:
ugh! I'm a bit confused. I accidentally hit install update when my phone told me there was an update. I knew it was 4.3..but am I able to still use this method if I already updated to 4.3 by accident? I don't think so right?
[Verizon Samsung Galaxy S 4] k1mu:
No, you can't use this to root MJ7.
[Verizon Samsung Galaxy S 4] emediately:
Vroot

Can't MJ7 be rooted already?

I rooted mine using some "VRoot" Chinese software from this website.

I got superuser and checked if phone was rooted, and it was.

However, now I'm stuck. MJ7 apparently has a locked bootloader, and I'm trying to install a Custom ROM, however can't boot into CWM.

I'm trying to use the Loki tool, however get the following error in terminal app:

loki abooit version does not match device
[Verizon Samsung Galaxy S 4] harrytery:
For the love of God. An answer is literally 2 posts above and you still ask.
[Verizon Samsung Galaxy S 4] k1mu:
You're wasting your time - all of those tools work on specific releases. Loki for MDK, the pwn tool for ME7, de la Vega for MI1.

You will not be able to install a custom recovery on MJ7. Eventually (hopefully) Hashcode will get Safestrap running, which will allow you to flash a limited set of custom ROMs. But right now, root is the best you can do.
[Verizon Samsung Galaxy S 4] budding_developer:
Unfortunately, this is only partially true -- it is a "false root" due to the implementation of restrictive SELinux policies on the MJ7 release. SuperSU will run, but SELinux has blocked busybox from running, so even though you appear to have root you are not able to actually use any root utilities. This block is implemented in the SELinux Security Policy, which is a Samsung-signed file -- you will not be able to simply substitute a modified policy definition file; it is checked on each boot, and if it doesn't pass the phone will simply sit there with a black screen (yes, I know this from experience! LOL!).
[Verizon Samsung Galaxy S 4] afrome:
I am getting the same error but now Knox is blocking my wifi from turning on how do i get rid of it
[Verizon Samsung Galaxy S 4] emarietta:
I honestly can't remember what I did to fix. I'm pretty sure clean odin me7 them root de LA Vega and did the ota and once that worked used titanium and removed Knox.... But if you want my.opinion stay on me7 because the mj firmware hasn't impressed me at all
[Verizon Samsung Galaxy S 4] k1mu:
Fortunately, that's only partially true.

If your SuperSU installation is complete, then there's a script run early during the startup that runs daemonsu in the background.

This is necessary for a more complete root function on 4.3.

When my phone updated to 4.3, it was in the state you describe. While I could use "su" to get UID 0 (and a "#" prompt), I couldn't do anything due to selinux enforcement. That's what daemonsu is used for as it starts up early enough to be able to make root access more useful.

So, what you're describing is half-rooted, which is where I was. Halfway simply isn't good enough.
[Verizon Samsung Galaxy S 4] smithilberry:
Method for Note 3 work for Galaxy S4?

this may be a stupid question, but would this method that works for the note 3 work for the galaxy s4? i ask because the two phones seem identical to me =S

http://www.andromods.com/root-unlock/vzw-galaxy-note-3-keep-root-vrumbmj7-supersu-wanam-xposed.html
[Verizon Samsung Galaxy S 4] k1mu:
That's the same methodology as this thread.
[Verizon Samsung Galaxy S 4] smithilberry:
i guess they're similar but not really...

1- this thread doesnt mention using xposed framework at all

2- that thread doesnt mention having to flash the original factory image first

3- that thread doesnt mention the prepare_param.sh file

do these not seem like fairly major differences? i ask especially cuz i been having trouble with the no wipe factory image file for MI1 so i havent been able to move on in the steps so I still havent upgraded to MJ7 because i do not wanna lose root...
[Verizon Samsung Galaxy S 4] k1mu:
1. Xposed framework isn't required for the I545 to retain root. Just SuperSU pro. That's probably also true for the Note 3 but since I don't have one, I can't tell.

2. Read the original post: STEP 1: Preparation asks you to install the factory MI1 image. I can't understand how you can miss that.

3. That's a difference caused by different techniques used to root the phone. The MI1 root overwrites the prepare_param.sh file, which needs to be restored before the MJ7 update will work.

I was downloading the no-wipe MI1 image to try to help you with your problem with installing it. I've now cancelled the download.
[Verizon Samsung Galaxy S 4] smithilberry:
I didn't miss step one. Step 1 is what is holding me back, lol. Unless you are saying that the no-wipe MI1 factory image step is not needed? and I could just skip to step 2?
[Verizon Samsung Galaxy S 4] k1mu:
No.

To keep root while updating to MJ7, you need to start from a clean image with no "bloat" removed and none of the system images that will be patched by the MJ7 update modified from their original state. That's what the first step does, which is to start from a no-wipe initial install.

Once you get there and have root, you then restore the original prepare_param.sh that Root de la Vega uses to root the phone, ensure that SuperSU Pro is protecting root, then allow the OTA. That's it.

Bypassing the steps described in the original post will either cause the OTA to fail, or will cause you to lose root.

This technique is not the simplest or most elegant, but it allows someone that can follow simple directions to get to rooted MJ7.

I tried to shortcut this and ended up having to flash a no-wipe image to recover and lost root. (Mostly due to attempts to recover which didn't work. You only get one chance at this.)
[Verizon Samsung Galaxy S 4] smithilberry:
alright, then im back to square one... i cannot get the no-wipe file to work =/

do you happen to have a working copy?
[Verizon Samsung Galaxy S 4] k1mu:
If no-wipe isn't working, you may need to install a full-wipe MJ7.

To know for sure, you'll need to post what the phone said when the flash failed.

If you're still having MD5 verification failures, then that's not it. You'll need to get a working network connection.

Fire your ISP and get another one, or go to your local Starbucks or Panera to try to download.

Yes, I have a working copy - from the OP. MD5 verifies fine.
[Verizon Samsung Galaxy S 4] smithilberry:
i bet your right about ISP... i been trying at school each time.... i will try at home where i got much better internet and could even connect an ethernet cable... i appreciate the advise, ill let you know how it goes!
[Verizon Samsung Galaxy S 4] smithilberry:
^^^^^^^^what this guy said =]

...finally got it working

....it was the internet that was ****ing up the no-wipe file needed for step one!

special thanks to k1mu for helping me and of course an extra special thanks to open1your1eyes0 for making it possible
[Verizon Samsung Galaxy S 4] ch.ch1:
How can I update from ME7 to MJ7 while keeping root?
[Verizon Samsung Galaxy S 4] budding_developer:
Effectively, you cannot.

There has been a method devised by which you can "technically" retain root after upgrading from MI1 to MJ7, however, in the implementation of SELinux's "Enforcing" mode done in MJ7, the utilities that allow root-level utilities to run are blocked from running at all; they instead generate a "Security Notification" in the notification bar but otherwise do nothing.

So, even though SuperSu can run, it can do nothing at all at the root level.

Sorry -- but the highest version of the Verizon firmware that can be rooted -- and be used as root -- is MI1. And if you have upgraded a non-rooted MI1 to MJ7, you cannot root it at all.

So my suggestion is to flash to MI1 from ME7, then use the "Root de la Vega" method to root it -- and then disable OTA updates by using a utility like Titanium Backup*Root to "freeze" or uninstall the file "/system/app/fwupdate.apk". You can then stay on MI1 until such time as the developers DO find a way around the SELinux implementation on MJ7.
[Verizon Samsung Galaxy S 4] k1mu:
Edit: Sorry, now I actually read the post - originally I thought you were saying the process in this thread didn't work. You're absolutely correct.

Yes, if you didn't take action to retain root while taking the MJ7 OTA, there's no useful way to get root back other than vroot.
[Verizon Samsung Galaxy S 4] ch.ch1:
Didn't take the update yet, per reading here I see you can upgrade from MI7 and keep root, but I'm asking if I'm going from ME7 how is done. How can I install only MI7 update and not MJ7 in order to try the root de LA Vega?
[Verizon Samsung Galaxy S 4] budding_developer:
I'm not sure about that, either... I have been reading where VROOT has been deemed malware -- what's up with that?
[Verizon Samsung Galaxy S 4] k1mu:
OTA updates only go one release at a time.

If you're on a clean ME7 ROM and allow the OTA to work, you'll get an update to MI1.

That will then allow you to use Root de la Vega to root the MI1 install.
[Verizon Samsung Galaxy S 4] ch.ch1:
OK, that sounds fine.
[Verizon Samsung Galaxy S 4] k1mu:
It's not known to be malware, but it's not known to NOT be malware. Since the authors refuse to share what they're doing during the root process, there's no way to tell if it's safe or not. There's lots of people saying they don't see anything happen that was unexpected, but a small number who claim they discovered unexpected files and applications. There's no way to verify these, unfortunately. So, we're left in this "we won't tell you what we're doing when we root your phone" situation. XDA decided, based on the lack of details, to not allow this program to be linked from the site. After all, this is a very strong open source movement.

I'm unrooted since at the moment vroot is apparently the only show in town for MJ7 and I won't use vroot.

There is no valid excuse whatsoever for these people to keep their rooting methods "secret". If Sammy wants to know what vroot is doing, they'll plug in a phone and run it. Game over. So, why are they keeping what they do secret? Perhaps it's because they're not disclosing what they're doing in addition to rooting the phone, but who knows?

Lots of people haven't noticed anything after using vroot - just like the millions of people infected with malware.
[Verizon Samsung Galaxy S 4] budding_developer:
Well, I can see both sides of the coin here... if they explain what they are doing, the exploit is patched that much quicker... and your point of Sammy simply plugging in a phone and watching what it does is equally valid. So, I guess it boils down to personal choice...

Since I have said good-bye to Verizon, and have converted both of my S4's over to ROMs that allow me to use AT&T at a much lower cost, I don't really have a dog in this fight -- I won't be using MJ7 under any circumstances.
[Verizon Samsung Galaxy S 4] swc2001:
Ok dumb question time!!!

But 1st an explanation of where my phone is at software wise.

I am on ME7, I have rooted it, I put hashcodes latest safestrap on (Safestrap-JFLTEVZW-3.65.apk), and I disabled OTA's

to disable the OTA I renamed /system/app/FWUpgrade.apk to FWUpgrade.bak as well as SDM.apk to SDM.bak

OK now I think yall are up to speed with where I am at on the phone. So what I was wondering was, if I follow this method of going to MJ7 will I be able to keep my apps Data and basically all of my settings that I worked so hard on? AND this will allow me to keep root as well?

What will happen to the existing safestrap since it wont work with MJ7? Do I need to uninstall the current Safestrap before proceeding with this Guide? You see if this all works like I am hoping it will.... I will be able to get to the new MJ7 update with Root and be able to install the new Safestrap that Hascode is building for MJ7 and will have out hopefully in the next 2 weeks or so..... WITH keeping all of my Data apps and basically all of those settings ringtones etc that I took such a long time putting together.

SO yeah possibly a dumb question I guess, so sorry for that. I just really dont want to do all of those settings and junk again if I can avoid it.

Thanks in advance for putting up with me!
[Verizon Samsung Galaxy S 4] smithilberry:
Nope, everything will be the save hence the purpose of the no wipe factory restore. I did this method recently and no data that you mention gets changed.

HOWEVER I cannot comment on the safe strap. I assume I did not have that cuz I do not know what that is nor do I haven't any info for you about that. Good luck!

PS no such thing as stupid question cuz you should be well informed on this sorta stuff cuz you def don't wanna mess ya phone up!
[Verizon Samsung Galaxy S 4] swc2001:
Awesome! Thanks so much for the quick response! I guess I will uninstall the safestrap just in case unless someone tells me otherwise. Again THANKS!
[Verizon Samsung Galaxy S 4] budding_developer:
At the present time, you will NOT be able to achieve or keep TRUE root priveleges on MJ7 -- the method does not give you a true root since the SELinux implementation on MJ7 prevents root-level utilities from running. So, while SuperSu may run, you cannot actually do anything with it since MJ7 stops su & busybox from running at all.

At the present time, there is also no way to achieve root on MJ7 -- no one has found a way to defeat the "enforcing" SELinux implementation present on MJ7. And until this is done, it would seem that hashcode's Safestrap will also not be able to do it's job on MJ7.

As I said in a previous post, the best you can do is flash the no-wipe image of MI1, flash the Root de la Vega exploit & go through it's procedure to achieve root on MI1, then install Safestrap -- and then stay right there until someone manages to defeat SELinux's "Enforcing" status and achieve root on MJ7. Both of the flash images I have refered to are "NO-WIPE" images, and will not harm your data; you may need to re-install any apps you installed that installed in the /system partition, but that depends on the app -- the data will still be there, though. Personally, I maintain backups in both Titanium Backup*Root and nandroid -- so as long as I have Safestrap accessible, I can always restore in some way.
[Verizon Samsung Galaxy S 4] swc2001:
I thought the vroot method was supposed to work just fine with MJ7. see the below Youtube link.

http://m.youtube.com/watch?v=K5mCsDyW-TI
[Verizon Samsung Galaxy S 4] budding_developer:
I have heard that it does, but there seems to be a controversy about whether or not it is malware... I don't know either way, and I am happy with the setup I have. I won't be moving to the MJ7 release no matter what happens -- if you want to try it, you're welcome to, though. I don't want to lose the ability to achieve root and run the firmware I want to on phones that no one else has any say over. That is why I am so p-o'ed at the carriers and refuse to accept their "lock-down".

You try it if you want -- I'm not saying it is malware or that it is not malware. I just have no need to try it, and I am not going to endorse something I haven't personally tried.

Good luck!
[Verizon Samsung Galaxy S 4] swc2001:
I understand.... you make good points... honestly the only reason I want the update is for the open gl es 3.0.... if they had a flash that gave me that.... I could stay where I am at and be very happy.
[Verizon Samsung Galaxy S 4] k1mu:
It's not as bad as you're saying. Apps can get root, and can do useful things. SELinux is still there blocking some things, but you can do an awful lot, such as run Titanium backup, modify system files, etc. It's really pretty reasonable now that I see what's going on.

Oh, I didn't use vroot and don't recommend it. I used a trustworthy rooter that I just released. http://xdaforums.com/showthread.php?t=2565758

Hopefully that won't turn out to be the case.

That's the best advice. If you can stay on MI1 (or better, earlier), you should.
[Verizon Samsung Galaxy S 4] swc2001:
Well is there anyone who can make the good parts of MJ7 flashable to ME7? Such as the open gl es 3.0 and the watch compatabilty? That way we could just skip the MJ7 update. That sure would be Awesome!
[Verizon Samsung Galaxy S 4] themusicmonkey:
Does anyone know if this works from MJ7 to MK2 update as well?
[Verizon Samsung Galaxy S 4] k1mu:
If you have SuperSU Pro with Survival Mode enabled, you'll keep root when updating to MK2.

It's not a big problem either way, as you can easily re-root MK2.