yashsingh1/xdaforums huggingface dataset:
[Sprint Samsung Galaxy S 4 Android Development] Suntar:
To make sure you have the MK2 bootloader Jim told me to check a file from the app store called Device Info and it will tell you what bootloader you have for sure. I thought that I might have messed up but when I checked I am still on MF9.

If you did everything correctly your wifi should be fine and I have exposed installed and it seems to be working ok but I haven't played with it that much yet. I had to work all day and no time to play. The camera I can't help you with I do photography and I use a real camera lol...

---------- Post added at 11:17 PM ---------- Previous post was at 11:14 PM ----------

U2 check what I posted for Zander. If you got Knox for sure then you can just take the OTA's I would imagine but before you do take 5 minutes and go get Device Info from the app store to make sure...
[Sprint Samsung Galaxy S 4 Android Development] Jim M:
It's in the details

[RANT] Knox software (.apk) that Samsung includes in the ROM will be present, it does not mean you have a Knox Bootloader. Remember this thread is about updating your ROM, Modem and Firmware from MF9 to NAE without updating your Bootloader from MF9. If your Bootloader is MJA, MK2, or NAE it has Knox, you can't change it anymore, it is Locked Down by Samsung... sorry.

If you have followed the instructions in the OP you will have a Knox free Bootloader (MF9), you will have the Knox software for the NAE ROM which has Knox, you need to run a Knox software removal tool or freeze Knox software or remove the Knox software from your ROM (I used Titanium Back Up). None of these things will remove Knox from the Bootloader, if it has Knox.

READ, READ, READ, understand completely what you are doing. Know what ROM, Modem and firmware your phone is installed with and running before attempting to change things. Remember, we can try to help you better before you do something to your phone, but once you do it, sometimes it can't be undone, we can't fix stupid.

Some people are so anxious to get an update (for some odd reason) that they jump right on and install an OTA update... NEVER take an OTA if you like to change your phone around. [/RANT}
[Sprint Samsung Galaxy S 4 Android Development] u2live79:
Suntar,

Thanks! Device info says bootloader is still mf9! I am however having trouble getting my baseband and software back to mf9 from mk2.

It's weird knox is under applications but it doesn't show anything about knox in download mode.

Any advice on how to get back to stock mf9 for baseband and software?

---------- Post added at 08:57 PM ---------- Previous post was at 08:53 PM ----------

These are the exact instructions I followed. I think there is something i'm missing when I load the NAE modem and NAE ROM because everything works after MK2 modem and Rom but as soon as I load NAE stuff. Wifi stops working. Any advise?

1.Odin 3.07 to flash PhilzTouch 6.08.9

2.Reboot straight into Download Mode flashed MK2 modem.tar

3.Reboot in to Philz recovery and "Factory Reset>Wipe to install a new Rom"

4.Stay in Philz recovery and installed MK2 Rom.zip

5.Rebooted normal into MK2 Rom. Added security pin for lock screen.

6.Rebooted into PHilz recovery and wiped system, cache, preload and dalvik Cache

7.Reboot from Philz straight into Download mode to flash NAE modem.tar

8.Reboot straight into Philz recovery and installed NAE Rom.zip.

9,Stayed in Philz to install HotspotNAE.zip and SDcardNAE.zip

Rebooted normal and can't turn on wifi or hotspot.
[Sprint Samsung Galaxy S 4 Android Development] Suntar:
Well it looks like you followed the plan but it was after you did it after the fact. Now don't quote me on this but this is how I did it. After each mess up I actually went back to my beginning and started from SPH-L720_MDC_Stock_Restore.tar.md5 and worked back up from there. I did the OTA updates until MF9 and then proceeded from there with the modem then then the rom. I generally do things the hard way since I do them on my own and process of alimination so this might not be the way you want to do it. The good news is your still on MF9 so thats a win. Also this file I used for the wifi fix at the end HotSpotMod_NAE_Odexed so it just might be the deal breaker but not sure. Sorry I don't have the links for you I just have the files on my Tablet. Good Luck

---------- Post added at 05:35 PM ---------- Previous post was at 04:41 PM ----------

Well said Jim and I do like the part "you can't fix stupid" ...
[Sprint Samsung Galaxy S 4 Android Development] u2live79:
Thanks for the reply and the help!

I finally got it! My nae modem only wouldn't take because I lost usb debugging mode after flashing mk2 rom. Strange but glad it's fixed.

Appreciate these forms and the folks that take the time to help!
[Sprint Samsung Galaxy S 4 Android Development] Suntar:
Glad you got it working and yes that is strange. Have fun ...
[Sprint Samsung Galaxy S 4 Android Development] TheZander:
Thanks, I downloaded Device Info. Seems I have MK2 so may as well do the full NAE update right? KNOX is KNOX.

I think when I switched out my phone the replacement already had it.
[Sprint Samsung Galaxy S 4 Android Development] Suntar:
Yea your goose is cooked. Once you have it there is no going back. The replacement would be the problem I would venture. Hey the way I look at it if it is over a year old the warranty is gone I think so have some fun. Now I am not sure but since you have know you might as well just do all the OTA's and call it a day. Before you do that check with someone or another thread and make sure. Good Luck...
[Sprint Samsung Galaxy S 4 Android Development] pcmanager:
Batter UP! Hi All, im about to jump into this, doing my nands and backups now... wow these android TW files have gotten large... not to mention how huge a DCIM file can get...

Im on MF9 baseband, bootloader, and firmware as I see it in device info. I think about 3 months ago i tried to go from MF9 modem to NAE and had the no sound or call problem and quickly nanded back to a working MF9 backup. I see where updating modem and then rom to MK2 then NAE could be the solution for that. just one thing has me a bit confused. In the unknownforce firmware thread he states that the second choice is the modem and firmware... with bootloader and Knox removed. DO I NEED TO USE the one with the modem including firmware bootloader? I dont want to make any mistakes being that it seems to be a lot of work to keep the MF9 bootloader including options of going back to other firmware. Will that or any of the rooted tars in the op of this thread install anything other then the MF9 bootloader, and modems and stock rooted roms as advertisied?

Thanks for keeping this train wreck from happening!
[Sprint Samsung Galaxy S 4 Android Development] Suntar:
Well PC the way I did mine was to do each step and its a bit of work but I was like you and didn't have any sound or calls. If you look at the threads here if you go from MF9 to MK2 modem and then the rom and the same with NAE it will all work. I was going from MF9 to NAE and right away no sound. Do each step but if you have no sound going into MK2 I think you did something wrong. I am just going by how I did it. Make sure you get the correct files and not the knox ones so choose carefully.
[Sprint Samsung Galaxy S 4 Android Development] pcmanager:
Thanks for the advice Suntar. I started my update a little late and this is what i have so far. I was and still am on Sac's version 5.6 android 4.3 Rom. I was on mf9 bootloader, baseband and software. I updated to the mk2 modem only tar. Held power button after odin flash to reboot to os. I checked baseband, software were both mk2, bootloader was still mf9. I made a call to voice mail and had sound. checked WiFi and data, both were working and loading web pages. I then powered off phone.... here is where i got lazy lol. I really just wanted to see how the nae modem could work better for me and plan on updating to kit kat soon but not tonight. So I powered down the phone again and then put in download mode, I then odin the nae only modem tar in pda slot of odin v 3.07, after it passed i pulled the usb cord and held the power button until the phone powered off, about 15 seconds. I then booted the phone to the os and checked about phone. I still had the mf9 bootloader, now im on nae baseband (modem) and nae software. I checked a call to a live person this time and had sound and they could hear me. I checked data and wifi, both are working, my download speed is about 20 meg at present time. There is a tower about 1/4 mile from my house so i usually get good coverage at home. I checked GPS is working good too. :laugh: ::good::good::good: :laugh:
[Sprint Samsung Galaxy S 4 Android Development] Suntar:
So far you seem to be in good standings. The way that I see it if all is working it really doesn't matter how you got there as long as you did. Nice d/l speed as well I wish I was that close to a tower but I still do well. Also I was on stock MF9 your on a custom so that might be a difference but its working so that's a win. and yes its ::good::good::good: Keep us updated ...
[Sprint Samsung Galaxy S 4 Android Development] JBone821:
Big thanks to Mudavo for this and wwjoshdew for the video!!! Worked perfectly for me on the first try.:good::good::good:

One quick question though. When installing both zips in recovery (MK2 & NAE) I got this message:

Using Legacy Property environment for update binary...

Please upgrade to latest binary..

They both installed fine and I have been using the phone for over 12 hours with no issues. Anyone know what that means and do I need to fix anything?

Thanks
[Sprint Samsung Galaxy S 4 Android Development] screaming01l:
Little issue Ive run into. Everything works fin, except instagram FC's, but I'm thinking a reinstall will solve that. BUT my Visual Voice mail no longer lets me save messages to my SD card. Says unable to move. And I've run the SD card write fix twice from twrp. Camera will save to the sd card as will Titanium backup. so I don't think its an issue on the card
[Sprint Samsung Galaxy S 4 Android Development] pcmanager:
Have you tried Folder mount app from the play store. I have read upon the first run it will detect and fix issues that apps are having accessing, reading and writing to the external SD card.
[Sprint Samsung Galaxy S 4 Android Development] screaming01l:
That did the trick. Found one faulty module.and fixed it. Now I can archive my visual voice mails again
[Sprint Samsung Galaxy S 4 Android Development] bradr00lzd00d1:
Will this guide work if I'm still on MDL?
[Sprint Samsung Galaxy S 4 Android Development] Blivit:
I haven't seen this asked here yet...and maybe it is a stupid question....

I haven't really touched my phone much since rooting it last year. All I did was root it so that I could remove bloat. I also, at some point used the guide here and did a sim unlock as I travel to China often for work. Everything is working still.

I haven't accepted any of the OTA updates since. If I followed the steps here to update to NAE would I have to redo the sim unlock?
[Sprint Samsung Galaxy S 4 Android Development] cwb1231:
I updated and am in Poland using my phone now
[Sprint Samsung Galaxy S 4 Android Development] Suntar:
Hi Brad and you should be fine to start at MDL. The trick here is to stay at MF9 and not go over it with the wrong bootloader but follow all the steps here and you will be fine.
[Sprint Samsung Galaxy S 4 Android Development] bradr00lzd00d1:
Awesome! thanks for the reply.
[Sprint Samsung Galaxy S 4 Android Development] Suntar:
If you have any problems just post them here and someone or myself will help you. Good luck and just do everything letter for letter...
[Sprint Samsung Galaxy S 4 Android Development] samsmith5:
I did this but wifi not working. I still have mf9 bootloader but I now have nae modem and baseband. Android version 4.3. I'm just using the stock mk2 odex rom from this thread. How do I go back to using sacs23 4.3 rom?

Thanks for all the hard work guys!
[Sprint Samsung Galaxy S 4 Android Development] Suntar:
Hi Sam It sounds as if you didn't do one of the modem updates if it is either MK2 or with the NAE. Your baseband is right where you want it to be without KNOX so don't mess with that. Try doing the modem file again and that might do the trick. First off before you go to sacs I would get your wifi working. If it isn't working now I doubt it will work with sacs. I just do a ton of trial and error since I enjoy the pain.
[Sprint Samsung Galaxy S 4 Android Development] samsmith5:
Suntar,

I would like to go back to using the mf9 because even with the wifi not working I'd like to use sacs23 4.3. More stable at least in my phone. Would following the instruction below do this?

www.droidviews.com/root-sprint-galaxy-s4-sph-l720-on-android-4-3/

Thank you Suntar for helping us all out with this.
[Sprint Samsung Galaxy S 4 Android Development] samsmith5:
I was able to go back to mf9 baseband but wifi still not working. however sound is working (didn't realize it wasn't). I still have android 4.3 incremental mk2 version. How do I get that back to mf9?

---------- Post added at 10:28 PM ---------- Previous post was at 10:21 PM ----------

Btw i used this link to down grade the baseband but still no wifi

www.galaxys4root.com/galaxy-s4-radiomodems/
[Sprint Samsung Galaxy S 4 Android Development] samsmith5:
Solved how to go back to MF9 after trying NAE

I figured it out. As you said, Suntar, I just needed to mess around a bit. For those having the same issues this is what I did:

Note: I was able to do this because I had kept my mf9 bootloader during the entire process of testing out the NAE

1. I used Philz recovery (the one in this thread) to install the modem/baseband for MF9.

2. My modem didn't come on line yet and I was still using the stock MK2 ODEX rom from this thread.

3. Wiped cache, delvick, system and preload.

4. Installed custom rom. I choose Saces 4.3 v 5.6.

From this, I got back my baseband and software to MF9. My Incremental Version is MK2 and my wifi and hotspot are back working. Sacs did really well with this version.

Thanks Unknownforce and Sacs for all your amazing work.
[Sprint Samsung Galaxy S 4 Android Development] Suntar:
Glad it all worked out and you got everything working. Basically if you miss one step the whole train comes to a halt.
[Sprint Samsung Galaxy S 4 Android Development] rsngfrce:
Am I safe to use this method?

I've done some searching on this thread and think I am OK, but want to be SAFE rather than SORRY!

ABOUT DEVICE on my phone lists:

Software version: L270VPUEMK2

Android version: 4.2.2

Baseband version: L270VPUEMK2

Build number: JD039L720VPUAMF9

The Device Info app lists my bootloader as: L720VPUAMF9

At one point I upgraded from a method on this forum past MF9, but developed issues and did a Nandroid back to MF9. I have Knox on my phone, but I have it frozen with Titanium Backup.

Since my bootloader is L20VPUAMF9, I should be able to upgrade as specified in this thread even though Knox is on my phone, am I correct in understanding that? Thanks!

(ONE ADDITIONAL QUESTION): My phone is out of the 12/12 warranty, so is there any point in using this method to keep my expired warranty valid, or would I be better off using one of the other methods, which I believe will allow me to upgrade while keeping my data (which is a plus for me...)?
[Sprint Samsung Galaxy S 4 Android Development] Jim M:
The reason in doing it this way is to keep the ability to go back to older ROMs. The Knox you have right now is only software. If you update your bootloader past MF9 your bootloader will have Knox too, then there is no going back.
[Sprint Samsung Galaxy S 4 Android Development] rsngfrce:
Thanks. Yeah, actually the ability to go back to MF9 did cross my mind, because I noticed in wwjoshdew's YouTube video that he says he went back to MF9 because NAE was too buggy (Any comments? Any threads I should refer to on what is currently the 'best' version?). Don't want to divert this thread with that question...

Whatever the update I did before was, apparently it did not update the bootloader beyond MF9 which I was on, so, while I realize you are pretty much saying this in your reply, I SHOULD be good use the method in this thread, correct? (Not trying to be dense, just want to be sure...:rolleyes:)
[Sprint Samsung Galaxy S 4 Android Development] Jim M:
Yep using this method from the OP of this thread, you will keep your MF9 bootloader.

I have no bugs running NAE and having the MF9 bootloader. YMMV.
[Sprint Samsung Galaxy S 4 Android Development] cherylbaker:
Looking for some help here before I totally brick my husband's phone :(

ok.. well followed the instructions the other day and had everything all set but wifi like others said did not work.

had some troubles today trying to redo everything (arrrrrrrrrrrrrrrrrgg husband gave me his phone with low battery and I didnt notice and that gave me issues till I noticed and charged it).

so redid everything installing the modem right before flashing the nae rom but still no wifi..

any thoughts???

phone has no sound on bootup and once booted is very very slow..

Cheryl
[Sprint Samsung Galaxy S 4 Android Development] cherylbaker:
No one has any ideas on how to get wifi back?

Cheryl
[Sprint Samsung Galaxy S 4 Android Development] Jim M:
Sorry for the slow reply, been away. Wifi problems are mostly going to be a kernel problem. I would suggest using one of the KT kernels and see if that fixes it.

Also, make sure to use a good Samsung USB cable when transferring files or running Odin on the phone.
[Sprint Samsung Galaxy S 4 Android Development] rsngfrce:
I think the reason I went back to MF9 after whatever pre-NAE update I did (I believe it was MK2) was because WiFi was working at first, then stopped and I could not get it back. I am using an AGAT kernel though, which is probably outdated and I figure I will change to the KT kernel once I perform the NAE update. I'll let you know how it goes...

(I noticed in the KT kernel thread, regarding the Touchwiz KitKat 4.4 version of the kernel, it says, "To make wifi work when it wont turn on or connect, change this in the build.prop: ro.securestorage.support=true TO ro.securestorage.support=false"... that might be worth a try anyways...)
[Sprint Samsung Galaxy S 4 Android Development] vadyr56:
In order to fix the WiFi issue related to NAE, you need to edit your build.prop file with a text editor. Look for the line that reads "ro.securestorage.support=true" and change it to read "ro.securestorage.support=false". I'm not saying that fixes the issue for everyone but it fixed it for me and seems to fix it for everyone I've talked to. Its an issue with the WiFi information storage and permissions as far as I can tell. Good luck, hope this helps.

Edit: didn't see rsngfrce's post prior to mine, apologies! Repeat advice is better than none I guess haha
[Sprint Samsung Galaxy S 4 Android Development] Jim M:
[MENTION=276587]cherylbaker[/MENTION] I think rather than trying a KT kernel, you should Odin the modem/firmware again. Did you use Philz recovery? The more information you give the better.
[Sprint Samsung Galaxy S 4 Android Development] 2WhiteWolves:
Thanks for the guide and video to do this, first try nothing went wrong and everything works :) Followed instructions to the T, I hit the thanks button.
[Sprint Samsung Galaxy S 4 Android Development] draghn:
Thanks to everyone involved in figuring this out and providing it for everyone. When I first tried this, I had lag waking up my phone, had no sound, and could not make phone calls. I read through the thread and eventually ended up searching this thread (after searching other threads) and my solution was adding the extra step of flashing the MK2 Modem only tar. I found the steps that [MENTION=2675913]Suntar[/MENTION] did after finding the steps that worked for him (quoted below). Thank you very much Suntar for stating what worked for you and helping me with mine. Trying going straight from the MF9 modem to the NAE modem without using the MK2 modem as a stepping stone was my issue.

The only variant from what Suntar did was when I booted into the MK2 Rom, the MF9 firmware and modem were still showing as installed, so after setting up the pin (wifi wasn't working), I shut down the phone and flashed the MK2 modem only, booted back into the MK2 Rom to verify that the mk2 modem was there, and it was (and wifi was working again). Once I got to the step that says to boot into the NAE ROM, I checked to see what baseband version it was showing, and it was still the MK2 version (wifi was still working), so I rebooted the phone, flashed the NAE modem only and booted back into the NAE ROM and everything showed up as expected, sound and phone calls were working perfectly.

Just thought I'd share my experience. I was close to giving up and sticking with MF9 until my search lead me to what worked for Suntar with the no sound, no phone call issue.
[Sprint Samsung Galaxy S 4 Android Development] Chuntay:
WIFI and Hotspot Mod not working - Assistance Needed

Help Please!

Thank you so much for sharing this updated information. It was very helpful in allowing my phone to make calls again.

I followed the updated step posted below by Suntar to flash MK2 Modem prior to NAE modem. This allowed me to get my phone and sound back but now my WIFI is not working. Please advise if there's a solution. I have already modified the build.prop file ro.storagesolution = false.

Software version: L720VPUEMK2

Hardware version: L720.08

Android version: 4.4.2

Baseband version: L720VPUEMK2

Kernel version: 3.4.0-481102 dpi@SWDD5908 #1 Tues Jan 28 22:02:38 2014

Build number: KOT49H.L720VPUFNAE
[Sprint Samsung Galaxy S 4 Android Development] pcmanager:
Hi Chuntay, looks like your still on mk2 modem (baseband). Your on a stock mk2 rom and kernel? If you are on a custom nae rom try Odin just the nae modem, now that you have already flashed mk2 the upgrade to nae modem should work and you should get your WI FI back.
[Sprint Samsung Galaxy S 4 Android Development] Chuntay:
WIFI problem fixed

Thank you very much pcmanager! I didn't know what my problem was I had flashed the NAE modem but apparently it didn't take.

I flashed it again this morning and no changes so I tried again with the Note listed in the posting "NOTE: With MJA/MK2/NAE Firmware, some people report better success with turning Auto Reboot and F. Reset Time unchecked. Do the same flash, but when you see PASS on Odin, unplug the phone and Hold the Power key for 10 seconds to reboot" and it worked PERFECT.

I used all the files and ROMs from post #1 including the stock rooted NAE rom. I was able to flash just the modem as you said and not redo any other steps. Once WIFI was working the Hotspot Mod was functional also.

Thank you Thank you again! :laugh::good:
[Sprint Samsung Galaxy S 4 Android Development] pcmanager:
EXCELLENT JOB Chuntay, glad you have your wi fi back! This phone needs files flashed in a very specific order it appears.
[Sprint Samsung Galaxy S 4 Android Development] Suntar:
Hi Chuntay, Glad you got everything working and glad I could help. Sorry for the delay but was on vacation. Good luck