yashsingh1/xdaforums huggingface dataset:
[T-Mobile Samsung Galaxy S 4] tekneekz:
Could you link me to the correct place that will suit my requirement's? I seem to keep hitting dead-ends from people posting in threads I think would work, saying it doesn't support devices that received the OTA update for the T-Mobile Samsung Galaxy S4 (SGH-M919 device) which updated the actual device to Android 4.3.

I want to root my fiancee's SGH-M919 Device as soon as possible and be able to have the options to flash the many, many custom roms available for the device found here and other palces, but it seems every place mentions that the 4.3 Android update for the SGH-M919 device makes it not stable or correct.

Off-topic (sort of related)...

My personal device is a AT&T HTC One M7 (rooted, unlocked, bootloader, s-off). With a flashed rom of Android Revolution HD 5.1 w/ HTC Sense5 (SuperSU by kosch), running Android KitKat 4.4.2 using Team Win Recovery Project (TWRP 2.6.3.3).

Reason why I mentioned this is I did see that TWRP is also now available on the Samsung Galaxy S4 device's to root them with, but I seen on a few threads and posts by users that have used it saying there is issues when updating to 4.3, or they lost root, or bricked their phone on update, or have to do certian methods and special things to keep triangle away to prevent the phone from updating to 4.3, etc. I know our phone is already had the update to 4.3; as we purchased it directly from T-Mobile after the update had came out.

Also, I would need a method I would be able to recovery and un-root the device with, for the S4. Meaning, that in a couple months I am able to restore the phone back to factory setup without root or running a custom rom so that when we take advantage of the T-Mobile Jump program that the device is enrolled in, when she wishes to Jump to a new device, I can unroot it and restore it back to factory, out-of-the-box state for the jump process...

Regards
[T-Mobile Samsung Galaxy S 4] lalec:
First, I didn't say that 4.3 or newer could be rooted, modified and then later returned to full stock without T-Mobile being able to see that you modified the phone. 4.3 can still be rooted and you can still install custom ROMs but with the new Knox "features" you will not be able to hide it unless/until the developers here figure out how to get around it. Having said that, some people say that T-Mobile told them rooting voids your warranty but not your eligibility for trade-in (as long as your phone is still functional and not water-damaged). I have not personally inquired into that so you may want to do it yourself. if you still want to root, Chainfire's CF-Auto-Root took me about 3 seconds to find by searching and it is here:

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

Yes, it works on 4.3 but read post #171 on page 18 for some tips on how to keep your root. CF-Auto-Root does not install a custom recovery; you have to install that right after you are rooted. I personally had better luck with PhilZ Touch which is based on CWM but try whichever recovery that you like.

Good luck.
[T-Mobile Samsung Galaxy S 4] thartley:
How to remove 4.3 firmware update request to install?

Hello,

I'm posting this here because I had hoped that following the instructions here for rooting and installing 4.2.2 would remove the request I keep getting to install 4.3 on my SGH-M919. If this is considered poor form, please relocate it to a more appropriate area.

A few days ago I received the notification to do the OTA firmware update for 4.3. I postponed it three times, but now it won't let me postpone it any more. It indicates that it has been downloaded to the phone and is now asking to install it. This evening I rooted the phone and installed the ROOTM919UVUAMDL.zip file following the instructions here. The Knox listing in the Application Manager is now gone from the All category (I didn't see a flag for it being installed when I checked the Download screen using Power/Home/DownVolume prior to rooting). Root Checker Basic verifies that I am rooted. But the notification to install the firmware still pesters me to install it. I have confirmed that I have 4.2.2 MDL installed and it now lists it as Custom. Some other posts mention either deleting or renaming a SDM.apk file to stop the request to install, but I don't appear to have that file on my phone (this was mentioned in a Verizon Galaxy S4 area). I have already disabled the notification by long-clicking on the notification in the notifications area and unchecking the notification checkbox, and clearing the cache (those being the only two things available to click on there). Everything else seems to be working fine with the phone - texting, calling, and wi-fi.

Any suggestions would be appreciated.

Thanks,
[T-Mobile Samsung Galaxy S 4] kammino:
:highfive:

Hi:

I just came from Galaxy S3 territory(MetroPCS CDMA version), I successfully rooted my new S4 but I would like to know what exactly is this file "m919_rootblockedStock_Boot.img.zip" before flashing it.

Also, Do I have to make an NV Backup or that's only for CDMA devices?

Thanks for your help.
[T-Mobile Samsung Galaxy S 4] lthaga:
PDA file?

Where is the link for the .tar file for T mobile Samsung s4 M919 model?
[T-Mobile Samsung Galaxy S 4] Skitts:
http://xdaforums.com/showthread.php?t=2258628
[T-Mobile Samsung Galaxy S 4] HaeSuse:
Stuck at Samsung Galaxy S4 Screen

I followed the directions in this post precisely, and the Odin install of CWM worked fine. I then booted into recovery mode, and it worked fine. CWM touch worked exactly as it should. I installed from SD the ROOT_M919UVUAMDL.zip file, and the log that runs on the bottom of the screen said everything passed/succeeded. However, when I then try to reboot, it just sticks on the Samsum Galaxy S4 screen. At the top left, in red is a line saying "KERNEL IS NOT SEANDROID ENFORCING", and then a yellow line saying "Set Warranty Bit : kernel.

What went wrong? I've been reading around, searching through all of these forums, with no luck, so far.

It's a T-Mobile Galaxy S4, that was recently purchased directly from T-Mobile, and has Android 4.3 installed. I used Odin 3.07. I downloaded CWM directly from the link in the OP of this thread, http://xdaforums.com/showpost.php?p=41163495&postcount=116 .

Thoughts?
[T-Mobile Samsung Galaxy S 4] Skitts:
This In Only For the original stock MDL(4.2.2) Pre-Knox firmware Your On the Latest MK2 (4.3) the problem was The File that you flashed was ROOT_M919UVUAMDL.zip which only for MDL because its Carries the Old Boot.img to stop the annoying notification..You Might want to start all over
[T-Mobile Samsung Galaxy S 4] MikeySmikey:
For those of you using this method to root stock NB4 firmware with the MDL bootloader and run into this issue (like I did) here's a solution: when you boot your phone it'll hang up on the Samsung splash screen. Pull the battery, reboot into download mode, open Odin, insert the recovery file of your choice in the PDA slot and hit start. It worked for me and everything is running fine now with root. Hope this helps.
[T-Mobile Samsung Galaxy S 4] chris83282:
I am very new to the world of rooting. I recently tried to root my t-mobile S4 m919 running 4.4.2. I rooted my phone with http://xdaforums.com/galaxy-s4-tmobile?nocache=1&z=9919900225941092#root I did everything exactly as on the video but when I rebooted after going through clockwork mod and flashing ROOT_M919UVUAMDL.zip It reboots to the galaxy s4 screen and at the top left it says kernel is not seandroid enforcing. Set warranty bit: kernel. It just stays on that screen. anyone help please. I would either like to get my phone working again or finish the root also When I try to try to boot into recovery it also stays on the galaxy s4 screen saying recovery booting... in the left corner stuck
[T-Mobile Samsung Galaxy S 4] chris83282:
I was finally able to unbrick phone had to get into recovery wipe everything and installed new 4.4.2 Kitkat through odin.
[T-Mobile Samsung Galaxy S 4] kaiya215:
just wondering... i just picked up this phone the other day... i belive it is fully updated to kitkat latest ota...

my build number reads:

kot49h.m919uvufnb4

is this method the proper one i should be using to gain root and flash a custom recovery

or is there newer way of going about it...

only reason im asking is that the build #s mentioned are differnt
[T-Mobile Samsung Galaxy S 4] kaiya215:
actually if u just were patient..... let it sit on the galaxy screen even tho it says that kernel warning in the corner it will still boot into the os...

the only warning that hangs on that screen is if it says something about the recovery... or system

thats just a flag for the staff to look for when a phone is returned or in for repair under warranty
[T-Mobile Samsung Galaxy S 4] chris83282:
Thanks
[T-Mobile Samsung Galaxy S 4] Asadullah:
I've currently got an at&t galaxy s4 but it comes with a locked bootloader so I can't flash cyanogen on it (which is killing me). So I'm planning on buying the tmobile version and selling mine but before I do I wanna make sure that the tmobile version has an unlocked bootloader even on the latest software. Can anyone tell me if the tmobile version runnning the latest software has an unlocked bootloader
[T-Mobile Samsung Galaxy S 4] The Doctor 9173:
Help

I used OUDHS and did everything as stated but after Reboot rooted device on the M919UVUAMDL firmware I get this at the top of my screen

KERNEL IS NOT SEANDROID ENFORCING

SET WARRENTYBIT: KERNEL

and it will not go past the start screen
[T-Mobile Samsung Galaxy S 4] kiruba8:
same here

same thing here.
[T-Mobile Samsung Galaxy S 4] Shaftamle:
Read first. MDL is not 4.4.2. Your just gonna trip your Knox flag, you can't go back and can't take ota's either according to Chainfire and many others.

http://omegadroid.co/wanted-knox-void-warranty-0x1/

Sent from a Shaftamle Galaxy S4

"Thanks Button" is always appreciated!

http://mycolorscreen.com/Shaftamle/
[T-Mobile Samsung Galaxy S 4] wolfen1086:
I followed every step exactly as stated in the instructions, thanks a lot for the brick, my phone is now totally useless
[T-Mobile Samsung Galaxy S 4] Shaftamle:
What android version was your phone on when you tried this thread?

Sent from a Shaftamle Galaxy S4

"Thanks Button" is always appreciated!

http://mycolorscreen.com/Shaftamle/
[T-Mobile Samsung Galaxy S 4] wolfen1086:
Android 4.3
[T-Mobile Samsung Galaxy S 4] neshwanalamery:
thank

thank you very much.this work is nice:good::good::good::good::good::good::good::good:
[T-Mobile Samsung Galaxy S 4] Shaftamle:
I have Verizon so I'm not positive but I don't think 4.3 is MDL. I believe its mk2. This method is for the MDL boot loader which is 4.2.2. It was posted about the update on May 7, 2013. This might explain the brick.

Sent from a Shaftamle Galaxy S4

"Thanks Button" is always appreciated!

http://mycolorscreen.com/Shaftamle/
[T-Mobile Samsung Galaxy S 4] wolfen1086:
I don't kow, all I know is it took some doing to fix the phone, but I'm rooted fully now acording to root checker unlocked, and running Wicked rom V10, with no problems or hangs, I had to flash another rom cause the darn original one got wiped away.

So a factore reset will do nothing, but the nandroid backup is there :)

Which I really prefer anyway.
[T-Mobile Samsung Galaxy S 4] Shaftamle:
That's good glad you got it working. I know you said you read over the whole post, in the future, maybe read read twice before blaming the author for a brick. I don't mean to sound like a jerk but its is stated in the first line of this thread what boot loader its meant for. [MENTION=4370056]mattlgroff[/MENTION] I'm sure spent a decent amount of time putting this together and its not really fair to blame him for an oversight. Just a thought.:thumbup:

Sent from a Shaftamle Galaxy S4

"Thanks Button" is always appreciated!

http://mycolorscreen.com/Shaftamle/
[T-Mobile Samsung Galaxy S 4] wolfen1086:
yea but the way I got it working was the old fashioned way, Now I have a bigger problem I have four rooted doorstops cause teh region away DID NOT unlock the sim llike theyou tube video says it does.

I pissed Tmobile off when I told them I wasn't paying teh bill until they straightened it out and the suspended my service, so now all I have is an old Spring Epic that I can use only on Wifi, until I either buy unlock codes from the internet or buy new phones, and personally for the price of the unlock codes, I can but a flip phone, cause it turns out 500 pages on teh internet about unlocking are worthless garbage pages
[T-Mobile Samsung Galaxy S 4] bluejeanstv:
Is this 100% stock?

edit: nevermind just realized this was rooting
[T-Mobile Samsung Galaxy S 4] delsolro:
4.2.2 Rooted

Im currently on 4.2.2 rooted, ive been having issues with MMS texts from iPhone users coming in blank with the "Unknown Address". Apparently Samsung states to have fixed this bug in 4.4.3 which according to a thread on the tmobile support site a user was able to install it via Kiev yesterday. Has anyone here been able to verify this? I tried but i must have removed something while i was cleaning out the phone from bloatware that Kiev just force closes.
[T-Mobile Samsung Galaxy S 4] njpatel4:
4.4.4

Would this method work for a T-Mobile Samsung Galaxy S4 that runs 4.4.4?
[T-Mobile Samsung Galaxy S 4] chirojunkie:
I'm wondering the same thing.
[T-Mobile Samsung Galaxy S 4] serio22:
No. Use cf-auto-root
[T-Mobile Samsung Galaxy S 4] chirojunkie:
I've been searching and having trouble finding the right cf auto root file any help anyone could give if appreciate it
[T-Mobile Samsung Galaxy S 4] serio22:
Use the NH7 version from chainfire's site
[T-Mobile Samsung Galaxy S 4] njpatel4:
Will I still be able to use mobile data, messaging, wifi ect?

What about KNOX? Do I have to do anything special with it to bypass KNOX? Will KNOX block all rooting attempts?
[T-Mobile Samsung Galaxy S 4] serio22:
Of course, otherwise it would be pointless

just open supersu once the phone is finished booting and it will ask if you want to disable Knox. Just click yes and it will do it for you. If it hangs, you might have to reboot and do it again but it will work
[T-Mobile Samsung Galaxy S 4] dwiz88:
Please help, Tmobile Galaxy S4 is soft bricked

Hello,

I followed the original procedure for rooting my tmobile galaxy s4 and now it's soft bricked. I've been trying to recover by flashing the stock files using odin but am not having any luck. Each time I try I get a failure notice in odin. Can someone please help? I'm new to these post so I'm sorry if I might have missed an already posted answer.

To recover my device I've been trying these instructions: http://xdaforums.com/showthread.php?t=2335109 and using the "How to Unroot T-Mobile Galaxy S4 using Windows" instructions.

I am able to get my phone into downloading mode.

My devices is a Samsung Galaxy S4 Model SGH-M919

Android version 4.2.2 Baseband version M919UVUAMDL

I am running Windows 7 on my PC and using Odin3 v3.07

For the stock file I am using M919UVUAMDL_M919TMBAMDL_M919UVUAMDL_HOME.tar.md5

Here's what I've been doing: I connect my device then load Odin. I select PDA then browse to and select the MD5 file. I only leave Auto Reboot and PDA checked then click start.

Here are the messages I received in Odin

<ID:0/006> Added!![/SIZE]

<OSM> Enter CS for MD5..

<OSM> Check MD5.. Do not unplug the cable..

<OSM> Please wait..

<OSM> M919UVUAMDL_M919TMBAMDL_M919UVUAMDL_HOME.tar.md5 is valid.

<OSM> Checking MD5 finished Sucessfully..

<OSM> Leave CS..

<ID:0/006> Odin v.3 engine (ID:6)..

<ID:0/006> File analysis..

<ID:0/006> SetupConnection..

<ID:0/006> Initialzation..

<ID:0/006> Get PIT for mapping..

<ID:0/006> Firmware update start..

<ID:0/006> sbl2.mbn

<ID:0/006> NAND Write Start!!

<ID:0/006> sbl3.mbn

<ID:0/006> rpm.mbn

<ID:0/006> aboot.mbn

<ID:0/006> FAIL! (Auth)

<OSM> All threads completed. (succeed 0 / failed 1)

[IMG="odin"]C:\Users\Donald\Downloads\root galaxy s4\odin image.jpg[/IMG]
[T-Mobile Samsung Galaxy S 4] k8108:
Try 1) another USB cord, 2) another computer 3) another download. This link has several.

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

Odin can be finicky. I've had to try all 3 of the things I mentioned at times to get a successful load of the file.
[T-Mobile Samsung Galaxy S 4] serio22:
Are you positively sure you are on MDL firmware? That error message occurs when you try to flash an older firmware than your current if you have 4.3 and newer. Which also explains the soft brick while using this root method
[T-Mobile Samsung Galaxy S 4] dwiz88:
I'm happy to say that I was able to unbrick my phone by using a combination of odin3 v3.09 and stock file M919UVUFNB4. I am almost sure I was on MDL firmware. I'm very thankful for the quick responses and having my phone back but don't know where I went wrong. I followed the video instructions exactly. All I want is to root my phone to allow me to run apps that require root access. I found there is another process to root the S4 using odin 3.09 and CF-Auto-Root. Is that the process I should have used and is recommended? Is there a thread with the most up-to-date instructions and files?
[T-Mobile Samsung Galaxy S 4] serio22:
http://xdaforums.com/showthread.php?t=2294005

[SGH-M919] CF-Auto-Root

NB4 is 4.4.2. You might as well update to NH7 or MK2 which are 4.4.4. Same root method
[T-Mobile Samsung Galaxy S 4] 9v9:
Update the thread

The instructions are kinda outdated.
[T-Mobile Samsung Galaxy S 4] socalborn:
4.4.4 help

Will this work for 4.4.4? Thanks for your help in advance!!
[T-Mobile Samsung Galaxy S 4] serio22:
No. Use cf-auto-root or towelroot
[T-Mobile Samsung Galaxy S 4] pstacks05:
i have followed these instructions to the letter. i have downloaded the .tar file. downloaded the zip with the su bin, and everything worked perfectly when connected my phone to odin. after the i flashed the custom cwt recover, i removed the battery. after booting into the recovery mode and installing the zip file and rebooting the phone i am stuck in a reboot loop. There is a message that says Kernel is not SEAndroid Enforcing in red and Set Warranty Bit Kernel. what should i do?
[T-Mobile Samsung Galaxy S 4] fbueller:
Thanks, mattlgroff, it looks like this current root method isn't ready for prime time.
[T-Mobile Samsung Galaxy S 4] mattlgroff:
It works. If its not up to your standards then don't go with it. I'll update the OP if I make any progress. Personally, I'll be using the blocked-root kernel for now to avoid that notification.
[T-Mobile Samsung Galaxy S 4] fbueller:
Wifi not working != my standards :)

Joking aside, I really appreciate all you've done to help and to troubleshoot this. If you need anything, please PM me!
[T-Mobile Samsung Galaxy S 4] MisterEdF:
This is probably all happening, and will probably get worse, due to the fact the US Gov't has accepted the GS4 into their fold of secure devices for Pentagon use and has to meet gov't security specs.

http://defense-update.com/20130506_samsung-is-now-cleared-for-use-in-the-u-s-government.html

Samsung KNOX addresses platform security with a comprehensive three-pronged strategy to secure the system: Customizable Secure Boot, ARM TrustZone-based Integrity Measurement Architecture (TIMA), and a kernel with built-in Security Enhancements for Android (SE for Android) access controls.
[T-Mobile Samsung Galaxy S 4] jntdroid:
Good point - I never thought about that... :(

---------- Post added at 07:39 AM ---------- Previous post was at 07:20 AM ----------

Though the bootloader is still technically unlocked right? This new kernel simply blocks root on the stock system? i.e. custom software can still be flashed... Unless I'm looking at it all wrong, which is probable.
[T-Mobile Samsung Galaxy S 4] Disconn3ct:
Not sure what I did differently but I flashed the original update.zip (the OTA) booted it and then bounced back to recovery, flashed the old boot.img and my wifi works fine.

I still get those warnings, but I'm on wifi. (Tested by hitting some internal sites, it isn't lying to me - it is legitimately on wifi..)
[T-Mobile Samsung Galaxy S 4] miaan:
Fwiw I initially flashed the update via Kies and my wifi was borked. I then flashed the same update in Odin and now my wifi works well. Ymmv of course
[T-Mobile Samsung Galaxy S 4] vlad2277:
Guys, if this T-Mobile update is such a problem

Is it really worth updating at all?

Does it really improve stuff in phone?
[T-Mobile Samsung Galaxy S 4] bikrame:
Its not big improvement so I am also skipping this.
[T-Mobile Samsung Galaxy S 4] jntdroid:
It does seem to help things run smoother with less lag. The phone easily felt bogged down at times before the update.
[T-Mobile Samsung Galaxy S 4] Gadianton:
Thanks for helping me get root back.

FYI, see this post to disable the annoying security notification.

http://xdaforums.com/showpost.php?p=41114436&postcount=131
[T-Mobile Samsung Galaxy S 4] mattlgroff:
This does the trick! And I got a way to get WiFi working too. Updating OP with results in a few.
[T-Mobile Samsung Galaxy S 4] djfreaq:
Precisely. I determined this independently from you and it worked for me as well.

I let ODIN reboot the phone, but before I hit the "START" button in Odin, I hold down the Volume UP button so that immediately after ODIN reboots the phone it dumps into the custom recovery!
[T-Mobile Samsung Galaxy S 4] mattlgroff:
OP changed with the updated method which fixes:

Wi-Fi Not Working ---- Fixed

Device Modified - Reboot? Notifications ---- Fixed

Root and flashing old boot.img/modules is now one file to flash.
[T-Mobile Samsung Galaxy S 4] fbueller:
I...Love...You.

Works great, thanks!
[T-Mobile Samsung Galaxy S 4] vlad2277:
Now that this workaround been found,

Would you recommend waiting for more permanent fix to the new Kernel or it's really doesn't matter?

Does anyone knows if new files that are also blocking root, actually do anything good for the phone in regards to speed, smoothness, etc. ?
[T-Mobile Samsung Galaxy S 4] mattlgroff:
The only thing(s) stopping me were just fixed, so I am personally going to run this. If someone still wants to make a fixed kernel though I'd probably switch over when that comes out, if one does.
[T-Mobile Samsung Galaxy S 4] djarcanus:
success

This thread totally saved my ass. I tried flashing steps from other sites yesterday and I thought I bricked my phone. I did more searching today and came across this thread. I was able to unbrick the phone. A little more work got me to the point where Super User was installed, but it couldn't load the binary. The permission on the file was stuck at -r- . I reloaded the page and saw this: Flash ROOT_M919UVUAMDL.zip. THIS did the trick.

I had CWM installed. I thought about switching to OUDHS because someone said their WiFi works with that. I can say that for me CWM did not affect my WiFi. So far everything is great! Titanium Backup is up and running. Time to go merge stuff.

Thanks!
[T-Mobile Samsung Galaxy S 4] dheimann42:
For some reason my Wi-fi still isn't working, i don't have the annoying error or anything, but my wi-fi switches off as soon as you turn it on.

Any ideas?
[T-Mobile Samsung Galaxy S 4] mattlgroff:
Are you sure you are the new OTA (MDL)?
[T-Mobile Samsung Galaxy S 4] dheimann42:
Build number: JDQ39.M919UVUAMDB

kernel 3.4.0-440244

edit: got it through kies
[T-Mobile Samsung Galaxy S 4] KaneHusky:
Sounds like you may have the same problem I, and many others out there, have. My wifi was broken (will not stay connected more than a few seconds without WiFi Power Save Mode turned off manually) right out of the box and I tried numerous methods of fixing it with no luck after a week of trying everything imaginable. Alas, my attempts did not resolve the issue so I'm assuming it to be hardware related. I shipped my phone off to Samsung today for warranty repair.
[T-Mobile Samsung Galaxy S 4] dheimann42:
I know for a fact its not hardware related, before updating wi-fi was perfect.
[T-Mobile Samsung Galaxy S 4] ddizzy81:
Working perfect over here

Sent From My GSIII