yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 Active General] Devo7v:
I guess I only partially answered your question, so I'll go through your post line by line to make sure I convey what I was unable to last time.

I don't think it's a matter of preference for people whether they choose 4.3 or 4.4, on some phones 4.4 just flat out doesn't work so they are forced to use 4.3 if they want a working phone.

As I tried to say in my previous post, the 4.4 OTA was released on April 16 and subsequently pulled by AT&T on April 19 due to bugs. This OTA was captured and anybody who wants update to 4.4 manually is able to do so. Additionally root has been achieved on 4.4 and there are many people who are running rooted 4.4.2 right now. You can find more information on downloading and rooting the 4.4.2 update in the i537 Firmware Thread. So it's not so much that 4.3 provides more flexibility (both 4.3 and 4.4 have been rooted), but the fact that on some phones 4.4 doesn't work properly.

It sucks that you bricked your phone, but for future reference you can always flash the 4.3 ML2 Odin package and it should save your phone. Again you can find links to more information about ML2 and the Odin packages in the i537 Firmware Thread. If you're worried about bricking your phone after rooting, I would suggest looking into SafeStrap. To summarize what it does, it basically creates a second ROM on your phone that is independent of your original (stock) ROM. This way you can mess with your second ROM and do pretty much anything you want to it, even completely corrupt it, and you'll still be able to fall back to your working stock ROM and still have a working phone. It's a really great alternative to having a locked phone and not being able to flash custom ROMs. I would do a bit of research about SafeStrap, how to use it and how it works, it could save you headaches in the future.

Root methods for every version of firmware is linked to in the i537 Firmware Thread.

Just so you're aware, once you change your system files in any way (i.e. rooting) you will no longer be able to receive OTA updates. For some people this is a deal breaker, but you can always flash the 4.3 ML2 Odin package to return to a stock, untouched system that will be able to receive OTA updates again. The only downside to this is that the Odin package will completely wipe your phone when you flash it.

I hope this answered your questions, but my suggestion again is to look at all the links in the i537 Firmware Thread and read everything 3 or 4 times before you do anything. People have done everything you are trying to do and have run into the problems that you will inevitably run into. There are solutions for everything posted in this forum you just need to make sure you read about what you're going to attempt before you actually do it to minimize your risk.
[Galaxy S 4 Active General] namitutonka:
Thank you very much Devo7v. You answered everything clearly. I will take your advice to "read everything 3 or 4 times before you do anything." :good: Like this quote from another xda member: Maribou> "Also before flashing anything make sure you read, research, read, and read again. You should always fully understand whatever it is that you are trying to achieve with your device. If you don't fully understand, don't flash it."

So I'll be sort of like a 'soft bricked' phone, but instead of being in a boot loop, ...........I'll be in a wait and read, wait and read, wait and read loop. :o
[Galaxy S 4 Active General] unnamednm:
Hello

I have mine in the 4.2, if i do the OTA to the 4.3 or 4.4 i will lose the root of course but will i brick the phone?

It's safe to do the update?

Thanks
[Galaxy S 4 Active General] Devo7v:
If you're rooted you cannot update with the OTA, you have to flash the Odin package to get to 4.3. This will completely wipe your phone.
[Galaxy S 4 Active General] namitutonka:
USB Driver Problem may be solved

One of the biggest reasons for my holding off on Sunderwear's method has been a daily recurring failure of Samsung USB drivers.

Hopefully, I've found a solution:

Regedit > Find WUDFSVC, Continue search by pressing F3, until a little bit below the highlighted search item you see:

ServiceDllUnloadOnStop REDG_DWORD

Then modify this value from 1 to 2, which Changes 0x00000001 (1) to 0x00000002 (2)

I found two instances that I modified.

Thanks to SKGIRELAND at:

https://www.youtube.com/watch?v=WYuVG8kFMZ4 Kind of amusing to watch an eight minute half explanation, half rant, for such a brief solution.

:silly:

I have Windows 7 64-bit OS
[Galaxy S 4 Active General] namitutonka:
Almost ready for Sunderwear's method

SGH-I537 AT&T Official 4.3

This driver is working so far without a yellow entry in Windows Device Manager showing up after awhile. Driver (as before registry edit) was from "Kies 3", with driver date 3/10/2014 ver. 2.11.8.0

Only strange thing so far is that the 1st time phone was USB connected Device Manager showed "Samsung-SGH-537 Portable Media Player". Now, the 2nd time phone is USB connected that is gone and Device Manager shows "Samsung-SGH-I537 Mobile USB Modem." In both instances it showed up in the Kies program. Another anomaly, is that "Safely Remove Media and Eject Hardware" no longer shows my phone at all, but it shows up in My Computer as Samsung-SGH-I537 Portable Media Player.

Now that one stumbling block has been removed which prevented me from using Sunderwear's method, I'm kind of getting used to the Official 4.3 unrooted Touchwiz OS. But I'm almost ready to jump on the MOD wagon.

---------- Post added at 05:26 PM ---------- Previous post was at 05:07 PM ----------

Just turned on USB Debugging, and "Samsung Android ADB Interface" automatically installed. Plus I can now see my phone in "Safely Remove Media and Eject Hardware".
[Galaxy S 4 Active General] namitutonka:
I saved my contacts with Kies. Given a successful root with your Sunderwear method, do you believe Kies is capable of restoring my backed up contacts onto my newly rooted SGH-I537?

---------- Post added at 08:47 PM ---------- Previous post was at 08:28 PM ----------

Also, to prevent an OTA AT&T update, I'd need to rename some system apps as described in other threads, correct? Then if I ever wanted to update to a future AT&T UPDATE, then I would first Odin flash their official 4.3, right? One more thing, I did a clockwork mod backup when I had an official rooted 4.2.2 install. Could it be possible to get this back on the phone as well?
[Galaxy S 4 Active General] jkeuclid:
You absolutely can, I use Kies3 for this very reason.
[Galaxy S 4 Active General] namitutonka:
Booted Win7 today and there was one important update: Samsung Electronics driver, dated 2012. Checked my device manager, and "Samsung Mobile USB Modem" was still OK, but SAMSUNG-SGH-I537 was yellow again, details revealed the driver was dated 2006. Updated through Windows update and it is back to being OK. Sorry if any members think this is off topic for this thread, "4.3 OTA ML2 Root Method!" But, until I am assured of a stable phone to computer connection, Sunderwear's method may not work, because the Odin install on my PC is a necessary part which communicates from PC to phone. I'm waiting awhile to see if my USB phone drivers act up again, but I am still geared up to implement the instructions in the OP (Original Post). Heh-heh, just recently found out what OP meant.
[Galaxy S 4 Active General] jkeuclid:
Most that root their phones have the Android SDK installed and should you have issues with the driver, you can always fire up Kies3 and go to "Tools" and in the drop down, select "Reinstall device driver" for the most up to date driver, make sure also that under "Preferences" in that same drop down, select "update" tab, then check the "Notify when updates are available"
[Galaxy S 4 Active General] namitutonka:
http://xdaforums.com/showthread.php?p=52627312

Quote:

Originally Posted by dirrtpoor View Post

My friend's S4 was doing the same thing on his desktop. Every time he would try to transfer pics the phone would disconnect after a few files.

I tried different things from reinstalling drivers to trying to only copy over a couple of files at a time, nothing worked.

Finally I plugged his phone into one of the back usb ports and transferred over 2gb with no problem and no disconnects since.

My guess is the S4 is a power hog and some usb ports just don't supply enough juice. Try plugging it in to a usb port that comes off a motherboard. Don't use the front ports or usb hubs. Hope this helps someone.

Thanks man, been fighting with this for two weeks. Had been using front USB 3.0 port, before switching to a back USB 2.0 port. Seems to be working. Finally! see: http://xdaforums.com/show...690133&page=24

---------- Post added at 10:34 AM ---------- Previous post was at 09:54 AM ----------

Thank you jkeuclid. Had done that a few days ago, and had "Notify..." checked in Preferences as well. I hope changing to a USB 2.0 port on back of my PC from a front USB 3.0 works.
[Galaxy S 4 Active General] jkeuclid:
I'm running off of my USB 3.0 port on the rear of my Dell XPS17 L702X just fine, perhaps a driver issue.
[Galaxy S 4 Active General] namitutonka:
Ran services.msc, then started Windows Driver Foundation -User-mode Driver Framework. Then with 'properties' set it to Automatic. Cross my fingers, looks like my USB driver issues are fixed. :)
[Galaxy S 4 Active General] namitutonka:
Progress

Thank you Sunderwear. Progress is being made. :fingers-crossed: Right now I'm in a holding pattern, inclement weather is keeping my landing gear up. Odin 3v1.85 has been chugging along trying to flash originalkernel.tar.md5 for the past hour from the PDA slot. With the same file Odin 3.09 and Odin 3.07 failed several times from the AP slot.

Any suggestions to help me come to a 'safely rooted' landing?
[Galaxy S 4 Active General] namitutonka:
pwnedkernel.tar.md5 was successfully flashed with Odin v 3.09. Saferoot install.bat ran successfully. Installing SuperSU. :)

---------- Post added at 07:11 PM ---------- Previous post was at 06:48 PM ----------

Maybe quit Odin v1.85, try Odin 3.09 once more, then if it fails reboot my SGH-I537? Funny it now has SuperSU, and is still getting notifications while Odin is running. Plus I can still web browse, and both make and recieve telephone calls.

---------- Post added at 07:34 PM ---------- Previous post was at 07:11 PM ----------

I terminated Odin 1.85, then tried using "Safely Remove Hardware and Eject Media" which was unsuccessful because in task manager adb.exe is still running. Maybe I should terminate adb.exe as it may have been used by saferoot.bat, but might be interfering with Odin? Odin 3.09 just failed again. Terminated adb.exe, and another run of Odin 3.09 failed. Reboot the phone???

---------- Post added at 08:07 PM ---------- Previous post was at 07:34 PM ----------

Used "Safely Remove Hardware and Eject Media" to remove USB from phone. Moved from backpanel 2.0 USB to front 3.0 USB connector. Connection remains stable. Re-ran Odin 3.09 - failed, and after 25 minutes of Odin 1.85 I terminated that too.
[Galaxy S 4 Active General] namitutonka:
Rebooted phone. Custom logo now comes on. Phone is acting normal (pretty much) as far as looks and apps are concerned. But what is noticeably different in every screen, and possibly quite bothersome, is a constantly changing list of what I think are running programs on the right side of the screen, starting from the top right corner. The list varies in length from about 10 to about 18 entries. It is always there always changing, regardless of whether I receive calls or dial out. Regardless of any program like Google Translate or a calculator or a game, this constantly changing list is always there.

On the top line are three sets of numbers that are constantly changing in the following format, i.e. 3.47/3.48/ 2.85 > 3.5/2.7/3.52. The lines underneath the numbers are all single lines with entries like: kworker/1:1, com.sec.esdk.elm, system_server, StoryAlbum/1:1, kaudtid, com.google, com.android phone, mediaserver, mpdecision......... The location of this list obscures the top right "more" button when on the "Settings" screen. I can no longer find "Install from Unknown Sources" on the "Developer" settings.

I still have not been able to Odin flash originalkernel.tar.md5. I have yet to fix the now un-working wi-fi, but I expected that from reading the threads.

My old phone setup: Unrooted SGH-I537, Stock Official Android 4.3, Baseband I537UCUBML2, Kernel 3.4.0-2244695, Build JSS15J.I537UCUBML2, SE for Android status Enforcing SEPF_SAMSUNG-SGH-I537_4.3_0016, Secure boot status Type: Samsung

My now 'un-official custom' setup: All the same values except for Kernel version 3.4.0-1643958, and SE for Android status Enforcing SEPF_SAMSUNG-SGH-I537_4.3_0002

I need the most help now in Odin flashing originalkernel.tar.md5. Then I'll go on from there. This is quite an intriguing adventure! :)

---------- Post added at 09:53 PM ---------- Previous post was at 09:49 PM ----------

Also 4G LTE is quite a bit slower. Google Play Store has timed out several times. Loading messages from email are best viewed from my PC rather than the phone. Chin up ^, onward> ;)

---------- Post added at 09:59 PM ---------- Previous post was at 09:53 PM ----------

Also in "Settings" > "Developer Options" there is a grayed out entry "Wait for debugger" - The applicationyou have selected will open when the debugger has attached.

Does this reference adb.exe? I terminated adb.exe on my PC with Windows 7 "Task Manager"
[Galaxy S 4 Active General] namitutonka:
Yay! :D

Wi-Fi is back.

Powered down, took the battery out a while, then started DOWNLOAD mode, connected the USB, then used Odin 3.09 to flash

originalkernel.tar.md5

1. Still have that pesky always changing list of programs constantly running from the top right corner.

2. Still have a grayed out entry in in "Settings" > "Developer Options" > "Wait for debugger" - The applicationyou have selected will open when the debugger has attached.

3. Still have no entry in "Developer Options" to check or uncheck "Install from Unknown Sources"

Any suggestions are welcome. I'm very thankful to everyone for having a rooted phone! :victory:
[Galaxy S 4 Active General] namitutonka:
Sunderwear's method - saferoot - KnoxAgent - OTA prevention

During the Saferoot portion of Sunderwear's "4.3 OTA ML2 Root Method" there was a message displaying something about de-activating KnoxAgent, but I still see it in /system/app/

With ES File Explorer I've renamed wssyncmldm.apk to wssyncmldm.apk.bak in order to prevent an AT&T OTA update.

4. Do I need to also rename the .apk and .odex files of KNOXAgent? or did Saferoot during Sunderwear's method of running the saferoot install.bat take care of KnoxAgent?

So I now have 4 issues for which I am kindly requesting helpful suggestions.

---------- Post added at 11:43 PM ---------- Previous post was at 11:26 PM ----------

OOps! My bad. Scratch 3. Still have no entry in "Developer Options" to check or uncheck "Install from Unknown Sources".

This entry option is alive and well under "Connections" > more > "Security"

This noob bows in embarrassed ignorance. :o
[Galaxy S 4 Active General] jkeuclid:
Boy [MENTION=5647193]namitutonka[/MENTION], not sure but sounds like you have some driver/software(OS) issues going on, this service shouldn't have to be touched from it's default of "Manual". I may be available today later on to get this all sorted for you, I'd suggest to stand down for now until then so as not to get to far away from where you want to be.
[Galaxy S 4 Active General] namitutonka:
N/A
[Galaxy S 4 Active General] jkeuclid:
That looks to be some sort of overlay or trace running, not sure how you got to it? I'm looking now...
[Galaxy S 4 Active General] namitutonka:
I'd like to reverse the changes in my phone, and start over from the beginning to see if that 'overlay or trace' goes away.

Here's what I started with and what I've done to change things:

Starting with an unrooted SGH-I537, Stock Official Android 4.3,

Before

Baseband I537UCUBML2

Kernel 3.4.0-2244695

Build JSS15J.I537UCUBML2

SE for Android status Enforcing SEPF_SAMSUNG-SGH-I537_4.3_0016

Secure boot status Type: Samsung

Using Sunderwear's .3 OTA ML2 Root Method!

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

flashing pwnedkernel.tar.md5, rooting with saferoot , and then flashing originalkernel.tar.md5

After

Baseband I537UCUBML2

Kernel version 3.4.0-1643958

Build JSS15J.I537UCUBML2

SE for Android status Enforcing SEPF_SAMSUNG-SGH-I537_4.3_0002

Secure boot status Type: Samsung

To go back to where I started I want to reflash my phone with S4A 4.3 ODIN Files I537UCUBML2 from WiFi's OP at:

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

This is my last post on that Thread May 16th, 2014:

This is the current status of my AT&T S4a:

Baseband I537UCUBML2

Kernel version 3.4.0-1643958

Build JSS15J.I537UCUBML2

SE for Android status Enforcing SEPF_SAMSUNG-SGH-I537_4.3_0002

Secure boot status Type: Samsung

Do I need to flash all four of your files? [/QUOTE]

So until I find out the answer and reflash to Stock 4.3, I can't redo Sunderwear's method over again to see if it corrects my current 'overlay or trace'.
[Galaxy S 4 Active General] jkeuclid:
So until I find out the answer and reflash to Stock 4.3, I can't redo Sunderwear's method over again to see if it corrects my current 'overlay or trace'.[/QUOTE]Yep, since you never went to KK, first go into SuperSU and do a full unroot, then do a factory reset and whwn done with that, enable usb debugging after skipping past all of the AT&T setup stuff then flash the full ODIN 4.3 package. PM me if in need of further assistance, on the road currently.
[Galaxy S 4 Active General] namitutonka:
Have good travels.
[Galaxy S 4 Active General] namitutonka:
Be safe.
[Galaxy S 4 Active General] burton0929:
Had all kinds of problems flashing pwndkernel to my device. After numerous attempts, I found out my $.50 6' cable from China was the problem. Probably not the smartest thing I've ever done, but hopefully this helps someone else. :confused: Use quality cables and USB ports you know are working.
[Galaxy S 4 Active General] namitutonka:
Thank you so much for the advise jkeuclid. I no longer have any 'overlay or trace' problems with a constantly changing display of opening and closing programs running along the right hand side of every screen. Here is what I did.

First Time:

Did a factory reset/data wipe

Reboot from recovery straight into Download mode. <<<My first mistake

Flashed the full ODIN 4.3 package.

Everything worked, but I read your instructions again and started over.

Second Time:

Backed up my contacts with Kies3

Selected "full unroot" option in SuperSU

Renamed wssyncmldm.apk.bak to wssyncmldm.apk with ESFileExplorer.

Deleted busybox in "/system/xbin" folder according to ou812bkewl http://xdaforums.com/showthread.php?p=44495559

Powered off phone, removed battery for a minute.

Entered Recovery

Did a factory reset/data wipe

Let the phone reboot

Skipped past all of the AT&T setup stuff.

Enabled USB debugging

Flashed the full ODIN 4.3 package

Let the phone reboot.

Settings>Security> Checked "Unknown Sources"

Rebooted to Download mode to Odin flash pwnedkernel.tar.md5 according to Sunderwear's OP instructions.

Let the phone Reboot.

I ran cmd.exe as administrator in a separate window, changed to the D: drive then (changed directory) CD into the saferoot folder.

Ran install.bat from this command window from within the saferoot folder.

Had to follow instructions in the command window on my computer, and watch the phone to 'accept' changes.

Rebooted

Opened SuperSU and updated its binaries, 'accepted' and watched as it disabled KNOX with the adb shell automatically doing rename and chmod operations.

Rebooted to Download mode to Odin flash originalkernel.tar.md5 according to Sunderwear's OP instructions.

Watched phone to press OK when some kind of RSA key needed to be renamed in the flashing process.

A long wait of 2 minutes until Odin changed to green colored "PASS"

During this time the phone stayed with the blue and white AT&T logo on a white background. (Thought I might have bricked it during this wait, ha-ha)

Renamed wssyncmldm.apk to wssyncmldm.apk.bak with ESFileExplorer.

Now before anything else I will look into getting a reliable backup.
[Galaxy S 4 Active General] NoahWL:
Works!

Works perfectly on my GS4, thanks so much.
[Galaxy S 4 Active General] NoahWL:
I can second that
[Galaxy S 4 Active General] joe zack:
thank you sunderwear work perfect,,,,,,,,,,,,,,,,,good job
[Galaxy S 4 Active General] DL2000820:
I have my S4A 4.3 ML2 rooted and all that but now it's pestering me to update to 4.4.2 and i know is i update it i will lose root. Is there a way to stop the notification from popping up or upgrade to 4.4.2 and have it still rooted?
[Galaxy S 4 Active General] Devo7v:
Rename wssyncmldm.apk and wssyncmldm.odex to wssyncmldm.apk.bak and wssyncmldm.odex.bak respectively.

Or just update to 4.4.2 and root with towelroot. It's a lot easier than you think.
[Galaxy S 4 Active General] DL2000820:
(From Sunderwear's topic - http://xdaforums.com/showthread.php?t=2722073)

will this work too?

BTW: I have 4 wssyncmldm.apk and 4 wssyncmldm.odex, do i change them all to .bak?
[Galaxy S 4 Active General] novakorn:
Worked great! Thank you very much!
[Galaxy S 4 Active General] trulycountry:
new guy wanting to learn

I am completely new to rooting and android phones for that matter. I have had iphones and windows phones. Can you please give me some help on rooting my s4 active i537 .

first question what and where do I get odin

second what and where do i get pda

third will I loose anything that is currently on my phone, such as contacts and current apps that I have downloaded?

I greatly appreciate any information you can give. Thank you
[Galaxy S 4 Active General] Devo7v:
You don't need to do anything in this thread, it's outdated.

To root, it depends on what firmware you're currently on, start with this thread.

http://xdaforums.com/showthread.php?t=2629093
[Galaxy S 4 Active General] namitutonka:
SGH-i537 no longer visible on USB

Using Windows 7, I installed USB drivers for an old Note 4 SGH-i717. Now there is no longer any USB visibility for my SGH-i537. Oh well. Will just use ES File Explorer to wirelessly transfer files to and from the PC. No more Odin with the Samsung S4 Active. Working to my satisfaction on Android 4.4.2 I537UCUCNH4. Dialing *#0808# shows USB AP and USB settings MTP + ADB. I'm not asking for help with drivers. Just saying so if someone comes across my drivers post, then it is useless asking for my help to solve a driver issue with an SGH-i537 and Windows 7.
[Galaxy S 4 Active General] Devo7v:
Is there any reason that this wouldn't work with future Samsung releases? It seems like it should as long as we can flash the pwned kernel, this almost seems like a future-proof root method.
[Galaxy S 4 Active General] meraz9000:
I did downgrade my baseband to MF1 but it has nothing to do with the root...I downgraded becuase I needed to do IMEI repair and the ML2 baseband has newer security. You only need to flash the boot.img for the root..not the baseband.
[Galaxy S 4 Active General] meraz9000:
I doubt it. The reason why this works is because it is still a 4.3 kernel... I doubt it will work with a 4.4 System.Img etc..To root my galaxy s4 4.4 ATT I had to downgrade the system.img because downgrading the kernel didnt work
[Galaxy S 4 Active General] tet1:
Yes I hope so you upload the file .. and please also can you upload it NON.Hlos.bin file MF1 maybe will fix my wifI ..thanks
[Galaxy S 4 Active General] sagi232123:
Yep I can get my internal storage I think
[Galaxy S 4 Active General] tet1:
Sunderwear.. thank you I'm download the modem Mf1 file now I'll try it after finish the download ..