yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S 4] portscan:
Calm down a little bit, dude, damn.. People are trying to help you and you're coming off dickish. 1st off, why do you care if the custom is there??? It doesn't make a heel of beans that it is there unless you're returning the phone. 2nd, if you are in dire need to have it removed for whatever reason just downgrade the MK2 (if on it) back to MJ7. The tar file image is on here, just look for it. Flash that in ODIN, then take the MK2 OTA manually. Your screen will go back to normal with no pad lock. Once again though, if you're not returning the phone for a warranty issue, then just leave it alone.
[Verizon Samsung Galaxy S 4] lilg754367:
I am saying when i unroot the phone and do a factory reset the phone still says custom when it reboots i read through here and there is nothing that says how to get the normal samsung from when the phone was never rooted before

---------- Post added at 05:58 AM ---------- Previous post was at 05:56 AM ----------

sorry i havent done this in years got rid of the iphone so getting back into this where can i get the mj7 to downgrade i am on mk2 4.3 i didnt think you could downgrade
[Verizon Samsung Galaxy S 4] portscan:
I just told you how to do it. Flash MJ7 back to the phone in ODIN. MK2 is downloadable back to MJ7, then manually take the OTA again. You will not have a custom screen. HOWEVER, IF YOU'RE NOT RETURNING THE PHONE FOR A WARRANTY REASON IT DOES NOT MATTER!

---------- Post added at 11:02 PM ---------- Previous post was at 11:00 PM ----------

I am using Wanam and my Knox is not tripped.
[Verizon Samsung Galaxy S 4] portscan:
Oh hell, why not Surge hahaha

http://xdaforums.com/showthread.php?t=2507253 <--------- MJ7 TAR!!!!! MJ7 TAR!!!!! MJ7 TAR!!!!
[Verizon Samsung Galaxy S 4] lilg754367:
and i dont think you can downgrade from mk2 to mj9 on att
[Verizon Samsung Galaxy S 4] portscan:
Then you're going to need to wait for an AT&T MK2 tar, use Wanam Xposed or just leave it there if you're not returning it.

---------- Post added at 11:35 PM ---------- Previous post was at 11:29 PM ----------

Or flash the stock AT&T MK2 file from here.. http://xdaforums.com/showthread.php?t=2498897&page=107
[Verizon Samsung Galaxy S 4] oliohh:
im on mk2 and when i run the install.bat it says that adb server is out of date and it just loops? what am i doing wrong?
[Verizon Samsung Galaxy S 4] nolabowler:
THANKS!!! now for i have done after root and STILL have NO FLAGS....AT&T Galaxy S4 on stock 4.3 MK2 ROOTED

I opened SuperSu and disabled knox

Installed Wanam Xposed from playstore.

Installed Xposed Installer from Wanam.

In Wanam i have Notification Panel< Enabled circle battery, Security Hacks< Fake System status, Disable Knox Notifications. System< i have Numerous Multi-window apps added to Multi-Window list.

I had to reboot twice to remove custom boot lock. the first reboot was in Wanam i hit the circling arrows then reboot and the lock boot screen was still there, the after it restarted i did a regular restart from the power button menu, and the regular Samsung Boot screen was there.

Just to confirm the no flags i went in to download mode with the volume down trick and all notifications for knox and evrything say official and 0x0.

Still Look Factory!!! Thanks Again SO SO SO Much.....Hope my info answers someone elses ?'s before they ask them.
[Verizon Samsung Galaxy S 4] lesgainous:
Basic Questions...

Being new to rooting, I have rooted my GS4 (AT&T) running (v.4.2.2 MF3) for the sole reason of being able to tether (use hotspot) without being charged for it. I used exploit adapted for AT&T by Jortex, and then used "App Quarantine" to isolate the hotspot feature. By the way, I was grandfathered in with unlimited data--that's why I want to use my phone as a hotspot.

So, the above is my current state, and here are my questions:

1) Can I update to MK2 without performing any "prepping" or unrooting? Can I just accept the OTA update?

2) Do the steps shown in the first post of this thread allow me to tether/hotspot without AT&T charging me?

2a) If yes, what do I need to do (if anything) after I follow the steps in that post?

2b) If no (or if there is another, easier way), how can I use my phone as a hotspot and tether without AT&T charging me?
[Verizon Samsung Galaxy S 4] azuziel:
Thanks guys. Used wanam to restore official status. Noticed a few benefits already. :)

Knox untripped on mk6 rooted stock 4.3, rwc region.

Sent from my SGH-I337M
[Verizon Samsung Galaxy S 4] portscan:
As for me, I couldn't OTA to Verizon's MK2 even after unfreezing. I went back to MJ7 and lost root, took the OTA, then rooted MK2. I had survival checked, but root was lost. Some on Verizon have been able to keep root using survival to MK2 (not sure for AT&T.) You can give it a shot to see if it fails, make sure you turn on survival for SuperSU. If it works, AWESOME, if it fails, just unroot and unfreeze anything frozed and return everything back to stock, take the OTA, then use this method to root. It will root no problem. I can confirm FoxFi works on this update just like before, so you can tether with that. As far as them charging you, that's on your carrier. If they suspect you of tethering from seeing a high data usage, then I don't know what they would do. I did use 87Gigs on VZW and nothing happened.
[Verizon Samsung Galaxy S 4] lilg754367:
funny i did this and still have custom lock
[Verizon Samsung Galaxy S 4] jball:
I've said it in other threads.

I love seeing the unlocked padlock.

...............LOVE IT!!!!!!!!

ROOTED ATT MK2 using Tapatalk
[Verizon Samsung Galaxy S 4] lilg754367:
works!!! Thank you os much
[Verizon Samsung Galaxy S 4] Trak-X:
Try to open a command prompt, go the adb folder and do:

adb kill-server

adb devices

adb shell

If you can not get into shell, then you might need to update your adb files.
[Verizon Samsung Galaxy S 4] jball:
This is why I asked earlier if I should unroot and reroot using your method.there is mention of kernel specific benefits. I'm just seeking a straight up answer if root is root no matter how or if your root is more beneficial than the survival mode I used with OTA.i'm not trying to unroot or bug you any more intense than some.

ROOTED ATT MK2 using Tapatalk
[Verizon Samsung Galaxy S 4] WordsworthESP:
No. I imagine this is where most of your confusion comes from. I don't know how much experience you have rooting and flashing ROMs, but they typically tell you to wipe/factory reset before flashing. So if you don't lose root when wiping and flashing a ROM, why would you lose it now?

I'm glad you've got it figured out. Though in the future, do some reading and searching first, for your own sake. It'll save you some headaches, and don't forget it's also part of the XDA rules.

Sent from my MF(3)ing S4
[Verizon Samsung Galaxy S 4] oliohh:
Lol as noobie as this sounds, of everything you said i only know how to open the command prompt lol. Im assuming that probably means that i dont even have the adb files your referring to, therefore i most definitely need to update them. Can you be of assistance in helping me get to that point?
[Verizon Samsung Galaxy S 4] WordsworthESP:
Just in case anyone's getting stuck at the "Unlock and grant permission" stage, I had to toggle my USB connection from camera to the media storage, then back to camera mode for the device to prompt me. Hope that helps.

I'd try deleting the files and download the zip again, just for a fresh start. Move the zip to C:, then extract there, preferably in a folder with the same title as the zip. Make sure you've got USB debugging enabled on your device, plug it in and give Windows a minute to show the drivers installation or the autorun prompt, then run install.bat. If your PC is set to hide file extensions, ensure that you're running the .bat file and not the .sh file. Run as administrator just to be safe.

If it hangs at "Unlock and grant permission", toggle your USB connection mode from and back to camera mode and make sure your device stays awake, then you should receive the prompt. After you grant permission, it pretty much does everything for you until it reboots, then you'll see the shield in your notification bar and superuser should prompt you upon unlock. Good luck.

Sent from my AT&T S4 (MK2)
[Verizon Samsung Galaxy S 4] jco897j:
Its just a boot splash. It's nothing serious. You've been told the answer has already been stated in this thread. Reread the thread.
[Verizon Samsung Galaxy S 4] k1mu:
No, the "benefits" mentioned are simply things that the rooting technique takes advantage of to root the device. So, yes, root is root.

Using that technique, which I think is brilliant (I did not write the code that actually gains root on the phone, I just figured out how to use it once root was gained and install SuperSU even though SEAndroid and KNOX were blocking it).

Using that to do other things - like kexec - is quite possible regardless of how you rooted the device.
[Verizon Samsung Galaxy S 4] k1mu:
There's two things you can do. Easiest is to start task manager (press control-alt-delete and pick task manager) and look for anythng with "Image name" of adb.exe. Click to select it, then press the "Stop Process" button. Do this until the adb processes are gone.

There's a copy of adb bundled with the zip file. Use "cd c:\Users\whatever" to change your directory to wherever you extracted the ZIP file.

Then "cd tools". The adb commands will now work.
[Verizon Samsung Galaxy S 4] lilg754367:
k1mu just wanted to say i fixed it with the wanam and xposed installer sorry for such a hassle its been years since rooting because i went with a stupid iphone for awhile but just wanted to ask im suppoed to go into xposed installer and click framework and hit install and thats what brings the galaxy s4 logo back?
[Verizon Samsung Galaxy S 4] portscan:
You have to select the option in Wanam under security hacks. It's called Fake system status. It wasn't that you were a hassle, it was the way you came off. Just learn from it and move on. We're all here for one mission.

EDIT: Also, you may need to reboot twice to make the padlock go away...
[Verizon Samsung Galaxy S 4] SoCalNewb:
Thanks DRELUXOID!

For anyone else on Mac that is a newb with terminal (like me), here are some additional notes that may help with a few of the steps above:

"3. I chmodded the install script +x just in case."

- The chmod operation is to make the .sh file executable.

- To perform the chmod operation (assuming you have adb installed, and it recognizes your connected device):

A) type "cd", then a space, then drag the folder containing the install.sh file to the terminal window. Hit enter key. (This changes your directory to the folder containing the install.sh file.)

B) In the terminal window, type "chmod +x install.sh". Hit enter key. The install.sh is now ready to be executed in terminal.

C) In the terminal window, type "sh install.sh". The install.sh script will now run, rooting your device. Follow what is on screen. Success!​

I got the basic terminal tips above from an external website: link HERE
[Verizon Samsung Galaxy S 4] oliohh:
Thank you a ton! Idk what aspect of what you told me was what helped, but whatever it was it worked and i am now rooted. Much appreciated! Im thinking i wasnt in camera mode lol
[Verizon Samsung Galaxy S 4] upther:
This worked great, thanks so much. Only problem I have now is the notification for Verizon Support & Protection that pops up every 15 minutes or so and says that programs on the phone have been modified. Is there any way to get that to stop?
[Verizon Samsung Galaxy S 4] k1mu:
Open a shell using either "adb shell" or terminal emulator. Use "su" to gain root, then try

pm disable com.asurion.android.verizon.vms

Or, freeze Verizon Support & Protection using Titanium Backup.
[Verizon Samsung Galaxy S 4] upther:
Doh! Why didn't I think of Titanium? Thanks.
[Verizon Samsung Galaxy S 4] WordsworthESP:
Typically with fairly simple processes (step-wise) people tend to omit certain details, whether it's because they're assumed to be implied or because it worked for them exactly as stated. Personally, I'm bad with implied directions, even if I know the environment extensively.

It's like if someone says "It's over there!" my first thought is, "Over where? There are 360° of possible 'there's.'"

Ridiculous thought processes aside, I'm glad you've got it working. Sometimes it takes time and for someone to run into issues before we realize we've missed something. Enjoy. :)

Sent from my AT&T Samsung S4 (MK2)
[Verizon Samsung Galaxy S 4] k1mu:
I was tempted to rickroll you for that, since it's it's right here in this forum. But I didn't.
[Verizon Samsung Galaxy S 4] phyrant:
This method worked for me on my AT&T S4 with 4.3 MK2
[Verizon Samsung Galaxy S 4] upther:
Same problem I had. Easiest way is to go into Titanium and freeze Verizon Security & Protection.
[Verizon Samsung Galaxy S 4] Naddict:
Thread cleaned.

Users need to remember that use of masking techniques for bypassing the filters is still considered to be profanity.

That, and using derogatory terms are not allowed or appreciated, ever.
[Verizon Samsung Galaxy S 4] skiddingus:
Worked like a charm on MK2. Thanks!!!
[Verizon Samsung Galaxy S 4] CheriePie:
File download was removed from first post? Please re-upload...

Trying to get my system prepared for doing this but having adb communication problems right now. Will post more details in a bit if I still can't get it working right as I'm trying a few different things to try to get it working.
[Verizon Samsung Galaxy S 4] HipHopIsLyfe37:
I'm not sure if I'm supposed to click the source .zip or if there is another .zip to download. I had Visual Studio on my PC because I was taking a programming class and it never just opened the file and ran the root commands. Also, the .zip under the Source section doesn't have all the files that were mentioned in the 1st post. Can anyone help me? I've rooted my previous devices plenty of times, so I am definitely not a rookie at this lol. Just having a hard time finding the correct files
[Verizon Samsung Galaxy S 4] WordsworthESP:
So tonight after getting home from work, I wanted to listen to some music. I'd installed Viper4Android now that I had root (something I was ecstatic about) and it had no effect, though it worked fine last night. So I tried checking a few things, and upon entering ES File Explorer I noticed I could not edit anything within /system (I installed V4A as a system app.) So I checked the ESFE's Root Explorer settings and I received an error stating, "Sorry, test failed. This feature cannot run on your device."

Apparently I've lost root, oddly enough. Knox may've prevented the installation of Busybox, though I'm uncertain if that can cause root loss. This is very odd.

Edit

: I've re-rooted. Twice, actually.

First attempt

: I received two errors:

Error opening /system/xbin/ for write: Text file busy

Error opening /system/xbin/daemonsu for write: Text file busy

Second attempt

: only received this error:

Error opening /system/xbin/daemonsu for write: Text file busy

Back when I'd first rooted my HTC Inspire, I remember AAHK having a few errors and being told not to worry about them, so I wouldn't be surprised if this was a similar scenario, however I thought it'd be important to note... especially considering I lost root in the first place. It's not a huge deal, and if I have to repeat this process once a week, I'd do it in a heartbeat... it'd be a small price to pay. Though I am curious if anyone has had a similar experience, and if not, I wonder what could've been the cause.

Sent from my AT&T Samsung S4 (MK2)
[Verizon Samsung Galaxy S 4] CheriePie:
The correct file was there in the OP earlier today. But k1mu made some edits to it (as I can see from the changelog in post 1) and apparently forgot to reupload the new file. :(

I'm all set to go now, adb communication working properly and just waiting on this... unfortunately, I didn't download the older version beforehand so now I'm in limbo while I wait for the new file to be linked in the OP again. I believe this was probably just an oversight of k1mu in getting the new file back up there.

K1MU, hope you're still around and see this tonight so I can finish this up. Just got my Galaxy S4 yesterday and I'm attempting to root first before getting the rest of my software installed. Thanks!

---------- Post added at 11:54 PM ---------- Previous post was at 11:33 PM ----------

Alternately, does anyone have the version posted yesterday? (as it looks like 12/15 was the update prior to today's).

Supposedly the only update was a change of name so that one should work the same way. I now wish I'd taken the time to just download it even though I wasn't yet ready for it. Because I've already spent all day today getting things set up and now that I'm ready to root, I'm stuck waiting for the file. LOL
[Verizon Samsung Galaxy S 4] WordsworthESP:
Well this has taken a turn for the strangest. It seems I have "selective" root, Root Checker was able to confirm root, Busybox (Stericson) was granted root permission, though ES File Explorer and V4A are granted permission... but cannot utilize it. I've tried removing their access and permitting them again, with no luck. Very odd indeed.

Sent from my AT&T Samsung S4 (MK2)
[Verizon Samsung Galaxy S 4] jball:
Have you disabled "knox"

ROOTED ATT MK2 using Tapatalk
[Verizon Samsung Galaxy S 4] WordsworthESP:
Yeah. That's pretty much the first thing I did after rooting, as it's literally the first thing SuperSU asks. Everything was working fine until today, so I highly doubt it's Knox related.

Edit

: Finally, I've regained full root. Had to completely unroot, though the Custom startup screen persisted and made me doubt my process. Re-rooted and this time Busybox installed without a hitch, and no prompt to disable Knox, which confirms that it was disabled, just possibly too late. I suppose it blocked the install the first time around, but I'd restarted my device multiple times without incident, so I'm curious why it'd suddenly do it tonight. Oh well, I've got it back, and if this helps anyone else, in glad I was able to rectify it.

Sent from my AT&T Samsung S4 (MK2)
[Verizon Samsung Galaxy S 4] nnbengboy2:
Just updated to MK2 and I'm ready to root my S4. Too bad the download isn't attached yet. :( I'm happy to have an option for rooting though...I'm ready to get my Google Wallet back and running... :D
[Verizon Samsung Galaxy S 4] k1mu:
I just re-uploaded the zip to the OP. I'm not sure why it disappeared.
[Verizon Samsung Galaxy S 4] k1mu:
That means that you already had daemonsu installed and running, which implies that you were already rooted. If you're going to run this, you probablyneed to unroot first.

Fixing that error, however, just needs an adjustment to the process to move them out of the way before installing the new ones.
[Verizon Samsung Galaxy S 4] nnbengboy2:
Rooting my S4 is a lot different than my previous 2 phones...so I have a question.

Is there any way to install a custom recovery (CWM preferably) on this S4 with the MK2 build? I have successfully rooted using this guide, but have not found any successful methods for installing a recovery.
[Verizon Samsung Galaxy S 4] riker147:
This has been addressed many times. You can't install a custom recovery on any build after MDK. ME7 and MI1 builds are compatible with Safestrap. As of right now MJ7 and MK2 only have root, but Safestrap is close.
[Verizon Samsung Galaxy S 4] AndroidLonghorn:
I am having this same problem with Daemonsu, and when the script finishes and I try to open SuperSu, I get the error about the binaries not being up to date, so I cannot achieve root. It hasn't helped to delete or update SuperSu or try another superuser app or even a factory reset. Is there anyway you can write out the steps or modify the script to help with the Daemonsu already running error for those of us with only a basic understanding? Thanks for your help!
[Verizon Samsung Galaxy S 4] k1mu:
I've already fixed the rooting utility to move the unexpected daemonsu and su binaries to daemonsu.old and su.old prior to installing the new ones. Re-download and give it another try.

Edit: what kind of device and what baseband are you trying to root? Did you use vroot/kingo before trying this?
[Verizon Samsung Galaxy S 4] nnbengboy2:
I apologize for repeating a question, but it is difficult to scour through 30 pages to find a concise answer. Thank you for the clear answer and pointing me to safestrap (to keep an eye on it anyway).

I'm surprisingly happy with TouchWiz for now, so I guess I can hold on for a little longer. This is a huge change coming from the Galaxy Nexus. :)
[Verizon Samsung Galaxy S 4] decaturbob:
Before you venture down the safestrap route I urge you to do plenty of reading in the appropriate safestrap and ROM threads here. It takes some time but saves reloading and odining back.

powered by hashcode safestrap hyperdrive 10.2
[Verizon Samsung Galaxy S 4] tshelby73:
I came from gn myself also. I swore I wouldn't do another locked phone like my DROID x2 after having gn. I should have listened to myself but wanted something new and no n5 on Verizon. Love the hardware hate the software I would be happy with even aosp.
[Verizon Samsung Galaxy S 4] decaturbob:
Unless you have a mdk base...little chance of seeing asop or any custom kernel based ROM on the S4. Hashcode has given us an opening with safestrap for those u have me7 and mi1 Base. He is working on ss for mj7 and mdk2 users....but thus only allows us to use Roms based on the stock kernels. So far no boot loader exploit has been found since me7 was released. Without this exploit...no custom recovery will happen or a kerac module Dev for safestrap to run custom kernels.

powered by hashcode safestrap hyperdrive 10.2
[Verizon Samsung Galaxy S 4] MrKleen1:
Give it a little time. I also came from the Gnex and always was a big ROM flasher. Actually I still am because I didn't wait to buy the phone and was able to Loki bypass the bootloader. Sometimes I install the aosp ROMs or Google Play edition but always come back to the Touchwiz ROMs. I have to admit I don't mind touchwiz and I like some of the features.

I'd say sit back and enjoy how flawlessly this phone runs compared to past phones... :)

I think you will like it in time. Of course debloating is a good idea.
[Verizon Samsung Galaxy S 4] CheriePie:
Thanks for uploading the file again. I ran it and successfully gained root.

There's a problem I'm having though, similar to another person here, in that I can't mount /system as r/w. I've tried it with Solid Explorer (Unable to mount the system as read/write), ES File Explorer's Root Explorer won't enable either (Sorry test failed. This feature cannot run on your device.), and even ROM Toolbox's Scripter.

Other root-related features run such as browsing the /data directory, running TiBU, etc. It appears to be just a problem mounting the system partition as writable. Possibly this happened with the 4.3 update(s) to the Android OS?

SuperSU disabled Knox so I don't think that should be blocking it. Anything else I can check/do to get the system remount r/w working properly? (I could try a test with adb to see if that reports anything useful though I don't recall the correct command to do so.)

Thanks in advance for any help you can provide, or direct me to. :)
[Verizon Samsung Galaxy S 4] Domvillan:
I use root explorer and have no prob mounting r/w may want to try that
[Verizon Samsung Galaxy S 4] defcon888:
soooo simple

This was surprisingly simple and easy to do. Been waiting for this for 2 months (since MJ7). Now I have root....WOOOo HOOOOO