I hate to beat a dead horse here but i've been having nothing but troubles trying to upgrade my modem to NAE.
The modem it self flashes fine --- my baseband show NAE and firmware also. However, i have no audio output. As other users have described my dialer freezes (assuming from no audio output), playing music FCs DSP Manager, etc,etc.
I've tried flashing a 4.3 ROM then the modem then boot and then flash a KK rom. - No Luck
I've tried a NAE kernel after modem update (KTs Kernel) - No Luck
I just dont know what to do to get the NAE modem functional for me.
Thanks as always.
Have you tried to hard reset after the flashing? Anytime I've had major issues I would revert all the way back to mdl, update ota to mk2, root, custom recovery, backup then flash nae modem, recovery, reset, Rom, kernal if needed. Backup again if everything is working. I've never had any sound issue within any of my flashing. Odin version also plays a big deal, make sure you're running the most updated version. I hope this helps in some way. Good luck
Sent from my SPH-L720 using xda app-developers app
Having the exact same issues. =(
Ya I had the same ****ty luck guys.
I was on mdl. Did the mf9 full update tar. Then flashed nae modem. All went find to then find out I lost sound.
Is updating OTA the ONLY way to get to mf9 before flashing the modem that will work?
I wanted to reflash sacs kk rom and get it working
Sent from my SPH-L720 using xda app-developers app
I've tried hard reseting after flash. Im on MF9 Bootloader, Im pretty sure.
I used Odin V 3.07 to flash, Im not sure if thats the most recent version.
Ive read too that other people uncheck the F Reset Time and Auto-Reboot Options to get the modem to stick. I've done this too and the modem flashes (fine) when I pull up the page in settings.
Still I cant get any audio, or dialer(guessing because of the touch tones) on any ROM.
Any else find a resolution to this? I think I've seen a handful of us with this issue.
Having the same issue
Rather than start a new thread, i will post my issues here
Not sure what im doing wrong or what can be done to fix my issues. Originally was on the MDL baseband with stock rooted rom. I used the all in one MF9 (Modem/Kernel/Bootloader/ROM) to get all my parts running on MF9. At this point everything was running Great
I used this method: http://forum.xda-developers.com/show....php?t=2277480
made sure to follow every instruction carefully and updated to 4.4.2 NAE while keeping my baseband MF9
The Rooted Stock NAE rom gave me many issues:
1) No Sound
2) Very long/ sometimes unresponsive wake
3) Screen lag/delay when swiping left/right through apps
4) I could not use the camera
5) When i would press the volume rocker it would make my phone freeze and be very delayed
6) Could not make a phone call, I could receive a call but would no be able to Talk to or Hear the other Person
7) Screen would lag or sometimes freeze and go black when i enter my pin or pattern to unlock
8) I could not use wifi (solved this issue by using KToonsez latest Kernel)
I decided to change the rom and see if that would help.
I Flashed to CandyKat 4.4.2 rom and I noticed a great improvement
All of my lag issues were resolved, wifi was working without changing the Kernel
the only issues that still remained were:
1) No sound
2) Could not make a phone call, I could receive a call but would no be able to Talk to or Hear the other Person
3) Camera would sometimes work. but mostly would crash or give me an error
Sorry for the wall of text but i tried to include all the details for you. Anyone know what i am doing wrong or if there is a way to resolve these issues?
Yes, the is a very easy way to fix this, install the full NAE stock tar and enjoy a fully functioning kit kat phone. When you piecemeal an install like this, you have nothing but problems. I love when people claim everything's working great, except when I try to make a call, use camera, etc, etc. Just install the full tar, root, and enjoy your phone. And if your worried about Knox, suck it up, Knox does nothing to hamper you from customizing your phone.
sandman121383 said:
Ya I had the same ****ty luck guys.
I was on mdl. Did the mf9 full update tar. Then flashed nae modem. All went find to then find out I lost sound.
Is updating OTA the ONLY way to get to mf9 before flashing the modem that will work?
I wanted to reflash sacs kk rom and get it working
Sent from my SPH-L720 using xda app-developers app
Click to expand...
Click to collapse
what did you do? im currently in same boat, neglalite AND sacs roms don't work for me, that is, no phone, no camera....I odin'd mf9 way back, and just odin'd nae modem in the hopes of catching the latest from sacs...but now im stuck with nae and no rom that works with phone or camera????
---------- Post added at 12:50 AM ---------- Previous post was at 12:48 AM ----------
cruise350 said:
Yes, the is a very easy way to fix this, install the full NAE stock tar and enjoy a fully functioning kit kat phone. When you piecemeal an install like this, you have nothing but problems. I love when people claim everything's working great, except when I try to make a call, use camera, etc, etc. Just install the full tar, root, and enjoy your phone. And if your worried about Knox, suck it up, Knox does nothing to hamper you from customizing your phone.
Click to expand...
Click to collapse
uh, yeah...can you help me in less than 12 hours accomplish this? I am in the exact boat you are describing...I got negalite and sacs newest to install, what with my original MDL, then MF9, then just yesterday the NAE modem in the hopes of updating my older sacs 4.2.2 rom...and now I have a phone that's not a phone or a camera...its dead weight, and I need something fast, im leaving country in 18 hrs.
thank you, hope you can help
Related
Well, I've made a huge mistake not backing up my phone immediately after rooting it and now I have to suffer the consequences for my dumb actions. I didn't think I'd run into much trouble, as I never have with either my Galaxy S3 or Desire HD before that and flashing countless roms.
Well, after rooting my phone with chainfire auto-root, I immediately flashed this rom and it was working fine, until I decided to flash my favorite Android Revolution HD rom.
Immediately after flashing it I received an error and ended up without Wi-Fi, or sound. There was a file posted called Wi-Fi fix, but it didn't work for me after flashing it, trying another modem did help with the WiFi (but still no sound) and it wont let me unlock my SIM.
I'm at a loss here, and not really sure what to do (other than trying to flash all of the modems available for 9505).
Tried flashing stock firmware through odin, but ended up with a failure to write.
If anyone could share some light on this matter, it would be greatly appreciated.
Yes, it happens a lot. On what rom are you excactly?
Can you try this?
1. Make sure you are on modem MJ5
2. Do a full wipe in recovery.
3. Flash this rom http://forum.xda-developers.com/showthread.php?t=2372286
According to that chef, you shouldn't need to flash any fixes after.
Or you can just try to flash this kernel. But i'm not sure on what rom you are:
http://forum.xda-developers.com/showthread.php?t=2273437
I did flash that ROM, and the modem, but it ended up freezing as soon as I opened the phone app and I still had no sound, wifi was working though.
Ended up flashing I9505XXUDMHB_I9505PHNDMHB_I9505XXUDMHB_HOME.tar.md5 through odin and that seems to have fixed my problems, phew.
Same problem After flashing leneageOS,
Device Mi note 4, karnel 3.18.
Could anyone help ! Please..
Have tried flashing back to a previous rom that worked and still no sound,
I've tried numerous modems, does any one have any suggestions?
No sound in calls which causes freeze, no sound in youtube so no video playback, no sound on menu or anywhere else, but everything else works fine.
Please assist it's driving me crazy and I'm at a loss with what to do.
EvilM0narch said:
Have tried flashing back to a previous rom that worked and still no sound,
I've tried numerous modems, does any one have any suggestions?
No sound in calls which causes freeze, no sound in youtube so no video playback, no sound on menu or anywhere else, but everything else works fine.
Please assist it's driving me crazy and I'm at a loss with what to do.
Click to expand...
Click to collapse
I'm having same problem.
i9505 international unlocked.
currently running hlos xxumk8, modem xxuemke, janjan's pure google pre rooted 4.4 v2.
if someone has any idea where I went wrong or what I should try, by all means let us know
dimaqq said:
I'm having same problem.
Click to expand...
Click to collapse
Finally I was able to regain sound!
I tried loads of firmware combinations without luck, so finally had to go back to stock fw and up to 4.4 again.
Here are the crucial steps
Phone was not knoxed up
Flash with XXUBMEA (stock 4.2.2) using heimdall/odin.
Flash HLOS again manually, despite having done that in previous step, as phone was still showing newest modem version, (XXUBMEA or XXABMEA md5 0d8d7a23751956cfef0974cc611e71ec)
got sound at this point!
cf auto root, reboot, install philz touch, both via download mode
flash with Pure Google pre rooted 4.4 v2
Flash modem with recommended version XXUEMKE
dimaqq said:
...
Click to expand...
Click to collapse
My device has Knox enabled, I can't revert back to XXUBMEA as Odin fails when writing system.ext4.img
System Specs: Galaxy S4 Canadian i337m OTA 4.3 (jfltecan), carrier is Bell, stock Samsung firmware, stock kernel (use wicked rom 9.1 sometimes too)
WARNING:
lot's of reading so go grab a coffee and have a cigarette before you sit down to read this, you'll probly be here for awhile
The rom/fix in question: MDOB rom/i337m fix - here's a link to both.
http://forum.xda-developers.com/showthread.php?t=2280556
first off i'd like to mention this phone was 100% perfect on stock Samsung rom 4.2.2 using Ktoonsez KT-SGS4 kernel for many months, until the day I installed this dreaded MDOB 4.2.2 rom and the "fix" that came with it
everything went bad on me back while I was running 4.2.2 stock unlocked boot loader and could never get it back to normal so this isn't a issue caused by 4.3 knox or 4.3 itself that i'm currently using. (i'm stuck on 4.3 roms but had this issue way before 4.3 existed)
i'm having an extreme amount of issues AFTER installing the MDOB rom, even after changing rom back to stock (flashed back to stock rom with ktoonsez kernel which is what I was using before I installed MDOB rom and phone has been royaly screwed ever since that day) more specifically I think it happened from the "i337M fix" that's included with the rom, either way after installing this rom I've never been able to get my phone back to normal.
everything runs fine except until I install a custom kernel (Ktoonsez KT-SGS4 kernel) then all hell breaks loose.
I don't blame the kernels or my current rom since I've ran this before for many months until the day i installed MDOB rom on my phone my phone was a dream machine.
issues since this rom has been installed include:
Issues:
A. RANDOM SLEEPS OF DEATH (phone shuts off or freezes)
B. random freezing while trying to turn on phone or enter recovery
C. some kernels won't work proper (specifically ktoonsez KT-SGS4 kernel) example gpu stuck at max while idle and downclocking when screen is touched with this kernel
D. wifi won't work with custom kernel on stock 4.3 rom without build prop edit to ro.securestorage.support, although it should
E. weak wifi and mobile signals
F. bad battery life
G. bad call quality
H. More that I can't remember off the top of my head
here's my flashing process, in attempts to remove as much as possible:
I know a few of these steps are probly pointless but hey can't blame me for trying.
step 1. enable usb debugging & unknown sources
step 2. install root & recovery
step 3. fresh boot phone let files settle so they can save (5mins or more) then plug into computer while turned on and delete everything
step 4. reboot into TWRP recovery (version 2.6.3.1) and clear everything, full advanced wipe, factory reset, format data than clear cache/dalvik afterwards just to be sure
step 5. remove SD card plug into computer and format to make sure there's nothing
step 6. install rom
step 7. (sometimes) clear cache/dalvik/permissions after rom install, although fix permissions seems to break my permissions rather than fix them or maby my permissions just break during flashing and I just can't fix them (haven't tested enough to be 100% sure)
i'm SOOO temped to try a full nand erase since i noticed there ARE still lot's files on my phone directory even after wiping, but i know that isn't a good idea;(
once stock kernel is back on my phone these issues are all gone.
Ktoonsez says it's not his kernel (used to work before, so i have no reason not to believe him), he says it's the rom well i'm on 100% stock Samsung rom (exception of kernel) and the rom was built to act the way it does so you can't really blame the rom so who do i blame??
until i went to go try wicked rom and flash back to stock I didn't realize these things were still on here, but now they emerge! wicked rom was giving me some (unrealated?) issue so i decided ima go back to stock so i flashed stock rom via odin (pc) and right away i noticed the 4G symbol, Samsung wallet, desktop not setup proper (no shortcuts) this ONLY happens when switching from wicked rom to stock rom on the first flash, i flash again everything looks how it should, and in order to get it to do this again i have to flash back to wicked rom and flash stock rom again and BAM it happens.
i knew my issue started on the same day that i installed this MDOB rom but after doing a full wipe and MANY "fresh" stock rom installs later i stopped questioning the rom and just lived with a crap phone that reboots itself all the time and has bad battery life, AS SOON AS I SEEN THE SAMSUNG WALLET bam it hit me like a truck, IT WAS THE MDOB ROM INSTALL.
UNLESS stock Samsung rom comes with wallet preinstalled and hidden on stock/wicked roms than the ONLY other way it coulda got on my phone is from the MDOB rom.
I can wipe/delete/factory reset/flash with twrp & odin on pc all I want, my roms are still messed up after FRESH installs. I believe there is still left over files from this rom/fix, I didn't think there would be anything until I noticed when i'm flashing from wicked rom back to complete stock rom using odin on pc I experience things from MDOB rom (while It should be 100% stock after odin (pc) flash, but it's not)
after the first flash from going from wicked rom back to stock I always experience the following "bug" i'll call it a bug since these things ALL HAPPEN AT THE SAME TIME: once I flash AGAIN all these symptoms go away until I go back to wicked rom and flash back to stock rom than right there after this first flash going from wicked rom BACK TO stock ALL these symptoms come back until I flash stock firmware AGAIN, a second time (even though I just flashed it)
Symptoms:
1. Samsung wallet appears in my apps (this was only EVER on my phone once, when I had the MDOB rom on my phone), this thing shoulda never somehow appeared back on my phone in any way shape or form after ditching the MDOB rom, but again is comes back after the first flash going from wicked rom to stock rom.
2. I get the 4G icon from MDOB rom (not the LTE icon I SHOULD have while on stock, when on wicked rom I have a little LTE icon with a tiny 4G above it, the only time I've ever had just a 4G icon (without LTE) like this is when I had MDOB rom on my phone (which is the only other rom I've run other than wicked rom and stock rom).
3. this icon ONLY shows up after the FIRST flash from wicked rom back to stock, once I install stock AGAIN than it returns to it's normal LTE icon.
4. now i'm not just *****in about an icon here, this is just a part of my problem (indicator if you will), when my rom is "bugged" after first install from wicked rom to stock rom my wifi works normal how It used too. but once corrected (flashing again) AND using custom kernel on STOCK firmware it breaks my wifi 100% broken until I use this little build prop edit fix, set ro.securestorage.support = true to false, bam wifi now working but the rest of my problems are still there (wifi used to work 100% on custom kernels and everything until MDOB rom touched my phone and left this "bug" behind)
5. when this 4G icon appears after this "first" flash back from wicked rom to stock rom I also experience something else, my wifi button works during first boot setup and auto enables itself and I have no issues with my wifi connecting (as soon as I see this toggle on I already know once my phone locks onto the network it's gonna give me a 4G icon and not an LTE icon like it should and sure as shiznit it does, as soon as I get my icon back to how it's supposed to be (LTE icon) all of a sudden wifi won't auto connect on a first boot anymore, never, 100% never. (back before installing MDOB rom I used to auto connect 100% of the time on first boot) like it does now only when it's "bugged" out.
6. apps are missing, when this "bug" appears there's no app shortcuts on the desktop of my phone by default after fresh flash like there should be, sometimes they appear on first flash once in awhile (some apps might not even be installed? or just shortcuts missing, have yet to verify)
7. it feels like the phone flashes way too fast (second flash takes longer, I think?) and more/all? apps get installed on second flash, and Samsung wallet get's REMOVED (how'd it even get there? other than bein left behind from MDOB rom, same with the 4G icon, that icon isn't in either of the two roms I use so how does it get there? and ONLY at the same time the wallet magically appears and the rest of this stuff)
8. when this 4G icon appears my phone seems to be great except for the fact that I know my rom didn't install properly since i'm still missing apps ect, once I flash again, apps appear, Samsung wallet DISappears, 4G icon gets replaced with LTE icon and everything is A-OK until custom kernel is installed, remember this is NOT the kernels fault as it ran 100% perfect for many months ON THIS PHONE until the day this MDOB rom was installed, and it's had these issues ever since.
some of the things I've tried:
- Countless wipes, including full advanced wipe, restore to factory, data wipes
- Ton's of fresh installs of BOTH versions of 4.2.2 - now doing same with 4.3 and wicked rom 9.1
- Tried wiping using TWRP and odin mobile (flashed mobile odin via TWRP, it works incase anyone didn't know)
- Tried flashing roms using odin (pc) v1.85, v3.07, v3.09
- Downloaded new copys of roms from new sources to make sure my roms weren't corrupted in anyway
i'll hopefully edit this post and get some pics up soon and simplify my text to help you guys better understand my situation and i'll also add a list of things I've tried to fix this problem when i have time.
any thought would really be welcome, there's sooo many of us s4 users with random sleeps of death, i'm sure if we could fix this it would help out a lot of S4 users.
thanks, dustin
Amb669 said:
System Specs: Galaxy S4 Canadian i337m OTA 4.3 (jfltecan), carrier is Bell, stock Samsung firmware, stock kernel (use wicked rom 9.1 sometimes too)
WARNING:
lot's of reading so go grab a coffee and have a cigarette before you sit down to read this, you'll probly be here for awhile
The rom/fix in question: MDOB rom/i337m fix - here's a link to both.
http://forum.xda-developers.com/showthread.php?t=2280556
i'll hopefully edit this post and get some pics up soon and simplify my text to help you guys better understand my situation and i'll also add a list of things I've tried to fix this problem when i have time.
any thought would really be welcome, there's sooo many of us s4 users with random sleeps of death, i'm sure if we could fix this it would help out a lot of S4 users.
thanks, dustin
Click to expand...
Click to collapse
Have you tried to flash the stock firmware in Odin. You can get it off the Samsung Updates site.
The guy who puts MDOB together generally makes great rom's. If everyone had the same issues then no one would use it... you really could have gotten a bad download, user error somewhere or one of many other problems.
With apps' just "appearing" are you certain once you log into your google account that it not set up to automatically start downloading apps ?
hednik said:
Have you tried to flash the stock firmware in Odin. You can get it off the Samsung Updates site.
The guy who puts MDOB together generally makes great rom's. If everyone had the same issues then no one would use it... you really could have gotten a bad download, user error somewhere or one of many other problems.
With apps' just "appearing" are you certain once you log into your google account that it not set up to automatically start downloading apps ?
Click to expand...
Click to collapse
don't get me wrong, i'm sure it's a great rom but my battery drain was worse than stock so I went back to stock, I REALLY appreciate his hard work towards our community. I just dislike what it possibly did to my phone is all.
and I don't have issues with the MDOB rom itself, it's AFTER that rom has been on my phone EVERY other rom ever since then now has issues in some way shape or form, no matter what I do.
if it's user error I put down the steps on how I flash in OP, I dunno what's going wrong
i'm gathering screenshot's to better show my situation.
I am 100% positive GAPPS is NOT installing anything after rom installs (I don't connect to wifi until after setup is done spacificlly to prevent this from happening, my rom just flashes this way (only on first flash from wicked rom going to stock rom) once I flash again a second time my symptoms part goes away and I get the issues part of my OP
if i'm on wicked rom and flash to stock = symptoms listed above
if i'm on stock rom and flash to stock = issues listed above
I can replicate this problem all day long.
I've flashed his rom on and off. Never had the issue. The rom doesn't invade anything a full wipe wouldn't cure. If it doesn't full wipe then it's the recovery. It helps once in awhile if you Odin back to stock or even copy your sdcard contents and format your sdcard to make it fresh. read up on it first.
Sent from my SGH-I337 using Tapatalk
---------- Post added at 01:45 PM ---------- Previous post was at 01:44 PM ----------
Also I recommend doing 9 wipes when swapping roms. It sound ridiculous I know but I do it and have never had issues.
Sent from my SGH-I337 using Tapatalk
Amb669 said:
don't get me wrong, i'm sure it's a great rom but my battery drain was worse than stock so I went back to stock, I REALLY appreciate his hard work towards our community. I just dislike what it possibly did to my phone is all.
and I don't have issues with the MDOB rom itself, it's AFTER that rom has been on my phone EVERY other rom ever since then now has issues in some way shape or form, no matter what I do.
if it's user error I put down the steps on how I flash in OP, I dunno what's going wrong
i'm gathering screenshot's to better show my situation.
I am 100% positive GAPPS is NOT installing anything after rom installs (I don't connect to wifi until after setup is done spacificlly to prevent this from happening, my rom just flashes this way (only on first flash from wicked rom going to stock rom) once I flash again a second time my symptoms part goes away and I get the issues part of my OP
if i'm on wicked rom and flash to stock = symptoms listed above
if i'm on stock rom and flash to stock = issues listed above
I can replicate this problem all day long.
Click to expand...
Click to collapse
Just odin back to stock and set if that clears things up. It should solve any odd problems. The thing with flashing rom's is that someone's issues cannot always be replicated.
Going back to Odined stock will take it back to factory stock then do a factory reset in stock 3e recovery and you should be fine
Hello.
I followed the instructions here http://forum.xda-developers.com/showpost.php?p=51955929&postcount=1 to downgrade from NC5 to MK2 and then rooted.
After all was done, rooted and booted, my sound doesn't work, the phone call app lags big time and/or crashes, and I can't do speech-to-text for messaging cause mic won't activate (says can't reach Google but I have Internet connection).
I already tried clearing cache partition.
I'm unclear on how to flash fixes with safestrap or if that's even a solution. Any help is appreciated and thanked.
Thanks!
emTr0 said:
Hello.
I followed the instructions here http://forum.xda-developers.com/showpost.php?p=51955929&postcount=1 to downgrade from NC5 to MK2 and then rooted.
After all was done, rooted and booted, my sound doesn't work, the phone call app lags big time and/or crashes, and I can't do speech-to-text for messaging cause mic won't activate (says can't reach Google but I have Internet connection).
I already tried clearing cache partition.
I'm unclear on how to flash fixes with safestrap or if that's even a solution. Any help is appreciated and thanked.
Thanks!
Click to expand...
Click to collapse
Did you flash fixed kernel ?
Not sure about the kernel but I figured it out. I skipped optional step because I thought it was optional. It wasn't. I flashed nc2 modem hlos file and that fixed sound, phone app and mic for messaging.
New issue now though. WiFi doesn't work. I tried flashing bypass as it said in thread but no joy.
Thanks.
emTr0 said:
Not sure about the kernel but I figured it out. I skipped optional step because I thought it was optional. It wasn't. I flashed nc2 modem hlos file and that fixed sound, phone app and mic for messaging.
New issue now though. WiFi doesn't work. I tried flashing bypass as it said in thread but no joy.
Thanks.
Click to expand...
Click to collapse
You have version form Verizon so I'm not sure about this kernel, but in every tutorial for downgrade we have this kernel which fix sound and wifi.
emTr0 said:
Not sure about the kernel but I figured it out. I skipped optional step because I thought it was optional. It wasn't. I flashed nc2 modem hlos file and that fixed sound, phone app and mic for messaging.
New issue now though. WiFi doesn't work. I tried flashing bypass as it said in thread but no joy.
Thanks.
Click to expand...
Click to collapse
What ****ing mania of downgrade! Flash android 4.4.2 again and bye bye problems.
not just their obsession they hope to get rid of Knox but will not succeed. the only option is to make that be replaced motherboard with warranty in Samsung service centre
Volume is absolutely up, I don't have it on silent mode or priority mode only or anything, plus alarm doesn't make sound and some other things, just to clarify I'm not being dumb.
Any app that tries to produce sound crashes, like if I play a video on YouTube or in Chrome, if I open anything like AudioFX or what have you.
I think the most important thing is that this is occurring on every ROM, and I don't know what to do. I just fixed my data issue that was persistent on every ROM, but this is more important to me because I need my phone for an alarm clock among other things.
I have wiped, wiped, and wiped again. I flashed stock Touchwiz, tried older nightlies of CM12 I know were fine, tried other ROMs, etc. It doesn't make a difference, the effect is still the same no matter what.
I have tried pluggging in and unplugging headphones over and over. There isn't even an indication it's plugged in. There's also no way in hell I damaged the speaker or anything, and that wouldn't really explain crashes on YouTube and so forth anyway.
I have reset, without a charger plugged in over 10 times. Powered off and on 10 times. This was apparently a solution to a similar issue with the Nexus 5 on Lollipop. But do note that this issue isn't even restricted to Lollipop.
Please, if anyone has any ideas, even if they probably won't work, I'm pretty desperate to get this working again.
I solved it. It's caused by the NAE modem for some reason. Flashing any previous modem has working audio, and flashing NAE again breaks it again (just to verify that was the cause).
I don't know much about it, but how does the modem have any effect on audio?
PwnCloud said:
I solved it. It's caused by the NAE modem for some reason. Flashing any previous modem has working audio, and flashing NAE again breaks it again (just to verify that was the cause).
I don't know much about it, but how does the modem have any effect on audio?
Click to expand...
Click to collapse
Dang had I seen this earlier I would a told you exactly what you found. I had same issue going from MF9 modem to NAE. Trick is to flash MK(whatever number) boot up normally, then reboot and flash NAE modem and boot. Cheers!
Sent from my SPH-L720 using XDA Free mobile app
I had similar problem...had tried everything and then some. Was about to flash odin that revererted everything to stock unrooted. Was going to take in to sprint. Noticed files to download mismatched mine so odin back to mk2 and had sound so moved on up to NAE and still had sound. Then on to 4.4.2 rom and NG2 and all good. Go figure...was coming on here to tell you Glad u got it.