Hey all, I need some help trying to troubleshoot what went wrong. Note between every flash I did clear cache and full formats of the whole phone.
I was on SACS 4.3 ROM, MK2 and already had CWM recovery
I ODINed the NAE modem, it stuck - my baseband and software say L720VPUFNAE
I flashed SACS 4.4.2 ROM, it went well booted up and setup, but could not provision the network (I had wifi)
I reflashed SACS 4.4 a couple times, same problems. Tried AOKP 4.4, glitchy and froze a lot.
Flashed stock NAE from sprint, installed, but stuck on provisioning again. I checked and it didn't show I had NAE, it showed my baseband and software was UNKNOWN.
Flashed back to SACS 4.3 and everything works well again. Still shows NAE as the baseband and whatnot.
I would have thought I had a bad modem flash, but everything works and shows NAE. What is the issue?
Have you tried a complete ODIN of NAE firmware?
hAvAAck said:
Hey all, I need some help trying to troubleshoot what went wrong. Note between every flash I did clear cache and full formats of the whole phone.
I was on SACS 4.3 ROM, MK2 and already had CWM recovery
I ODINed the NAE modem, it stuck - my baseband and software say L720VPUFNAE
I flashed SACS 4.4.2 ROM, it went well booted up and setup, but could not provision the network (I had wifi)
I reflashed SACS 4.4 a couple times, same problems. Tried AOKP 4.4, glitchy and froze a lot.
Flashed stock NAE from sprint, installed, but stuck on provisioning again. I checked and it didn't show I had NAE, it showed my baseband and software was UNKNOWN.
Flashed back to SACS 4.3 and everything works well again. Still shows NAE as the baseband and whatnot.
I would have thought I had a bad modem flash, but everything works and shows NAE. What is the issue?
Click to expand...
Click to collapse
go to the Phone dial pad and punch in ##786# to pull up the RTN screen, It'll show you more accurate info on than what your Baseband and Software ect. The first time I flashed Sacs 4.4 V1 I flashed it using Phils 6.0.4.7, had the same problem. got it to flash flawlessly using the same process, but using Philz 6.0.4.6. just to be sure that was the issue i repeated process using 6.0.4.7, same problem, wouldnt provision network, just wifi, everything said unknown. couldnt make it work using 6.0.4.7. Tried again using 6.0.4.6, and again everything worked perfect ALSO try flashing the stock NAE.tar.md5 first, then Sacs 4.4 v2. Ive read that worked for many, Your problem is most likey CWM. flash Philz 6.0.4.6 then re try, let me know how it goes
VandyCWG said:
Have you tried a complete ODIN of NAE firmware?
Click to expand...
Click to collapse
Agree with @bioshocked I've ended up with unknown baseband before as well. Flashed nae firmware before the installation worked out perfect.
Sent from my SPH-L720 using xda app-developers app
hAvAAck said:
Hey all, I need some help trying to troubleshoot what went wrong. Note between every flash I did clear cache and full formats of the whole phone.
I was on SACS 4.3 ROM, MK2 and already had CWM recovery
I ODINed the NAE modem, it stuck - my baseband and software say L720VPUFNAE
I flashed SACS 4.4.2 ROM, it went well booted up and setup, but could not provision the network (I had wifi)
I reflashed SACS 4.4 a couple times, same problems. Tried AOKP 4.4, glitchy and froze a lot.
Flashed stock NAE from sprint, installed, but stuck on provisioning again. I checked and it didn't show I had NAE, it showed my baseband and software was UNKNOWN.
Flashed back to SACS 4.3 and everything works well again. Still shows NAE as the baseband and whatnot.
I would have thought I had a bad modem flash, but everything works and shows NAE. What is the issue?
Click to expand...
Click to collapse
it's the exact same story for me .had to go back to 4.3 but my only issue is now i am unable to watch video in any form (personal vids ,Netflix,youtube,vine even cutscenes in games) i really dont know what to do .even tried to Odin back to MF9 but no success.I neeed HELP
@hakeem0996
.even tried to Odin back to MF9 but no success.I neeed HELP
Click to expand...
Click to collapse
If you were on MJA/MK2 bootloader you CANNOT Odin to anything before that - MF9 etc.
You'll need to PC Odin MK2 full tar to get back to stock. That tar is here.
For the others if you have a MK2 or NAE bootloader why not flash the full .tar of either one (MK2 or NAE) - both are available here. Full .tar will restore baseband and ALL partitions.
The for both the above root via CF-Autoroot, install recovery via PC Odin or goomanager - I'd go with Philz via PC Odin.
Then install what ever you want following the developer's instructions.
bioshocked said:
go to the Phone dial pad and punch in ##786# to pull up the RTN screen, It'll show you more accurate info on than what your Baseband and Software ect.
Your problem is most likey CWM. flash Philz 6.0.4.6 then re try, let me know how it goes
Click to expand...
Click to collapse
pontif said:
Agree with @bioshocked I've ended up with unknown baseband before as well. Flashed nae firmware before the installation worked out perfect.
Sent from my SPH-L720 using xda app-developers app
Click to expand...
Click to collapse
Thanks, I'll try a full NAE firmware ODIN tonight, but I'm not sure where to get it. Is it this?
hAvAAck said:
Thanks, I'll try a full NAE firmware ODIN tonight, but I'm not sure where to get it. Is it this?
Click to expand...
Click to collapse
No, download the full tar file from Random45's thread in the android development thread. His has great download speed.
Sent from my icrap 2 using Tapatalk HD
cruise350 said:
No, download the full tar file from Random45's thread in the android development thread. His has great download speed.
Sent from my icrap 2 using Tapatalk HD
Click to expand...
Click to collapse
Thanks. Link
hAvAAck said:
Thanks. Link
Click to expand...
Click to collapse
Yup that it.
Sent from my SPH-L720 using Tapatalk
Go back and follow the instructions exactly: Here they are so thanks them and i'll take one too:
thanks goes to travisw0204 and GhostTac for this
This is a step by step instruction guide for those having issues flashing this ROM using a MF9 Bootloader and wanting to keep their bootloader Knox free. This should only be attempted if you have tried the first install option multiple times and are following the instructions completely (unless you are already rooted) and are getting hung up at the Sprint Splash screen. Read these instructions carefully and all the way through BEFORE you do this processes and make sure you are not cutting corners.
1. You need to be on MF9 bootloader
2. You need to flash a stock MDC .tar file. Once downloaded you have to extract the .tar file using 7zipper or a program similar. I got mine from RWilco's site found here..
http://www.rwilco12.com/downloads.ph...9/Stock ROMs
3. Once you have the stock .tar file you can then boot to download mode to prepare for Odin. Power down completely. Then press and hold Power + Vol down. You will see a warning page and then press vol up to get to download mode.*
4. Now plug your phone into your computer and open *Odin. I use 1.85 but some may use a later version. They all work.
5. Once connected to Odin the box in the middle to upper left should be yellow to let you know your phone is connected.*
6. Now click on PDA and find the .tar file for the stock rom that was obtained from rwilco's site. Hit start and let it run its course.*
7. Once Odin says Pass, the phone will reboot and you WILL get a yellow Sprint screen and nothing else. Don’t freak out. Press and hold the Power button and reboot the phone. Then press and hold power + vol up to boot into the stock recovery. From there do a factory reset and then the phone will boot up.*
8. Once fully booted you will have a small OTA update followed by the MF9 OTA update. This is the last OTA you should take.*
9. Once you go through those 2 updates you can then root using cf auto root through Odin (do the steps to get to download mode from above). Let it do its thing and the phone will reboot.*
10. Once you're booted up check to make sure you're rooted by looking for the super SU app in the app drawer.*
11. Now it's time for your custom recovery. Go back into download mode as mentioned above, plug the phone into the computer and open Odin once again to flash the CWM 6.0.4.4 recovery.*
12. Let the phone boot back up after the recovery flash.*
13. Now power down fully again and boot back into download mode.
14. Flash the mk2 modem found here (http://forum.xda-developers.com/show....php?t=2338919) through Odin and boot back up.*
15. Go to Settings and About Device and make sure the baseband and version both match and end with mk2.
16. Now power down again and boot back into download mode. At this point it's time to flash the NAE modem to get you ready for Kit Kat. That modem also can be found at the above link for Unknown or in the OP in this thread.
17. Once you flash the modem through Odin follow Sacs instructions on how to flash the 4.4.2 rom.
It sounds like a lot but really isn't and it will assure you that you're starting with a clean slate and a Knox free bootloader.*
*You can use PDA for all your .tar files for this process in Odin or AP for later Odin programs.*
**This process will also work for those on MJA and MK2 bootloaders with Knox. You can follow the same steps but instead of going back to MDC you have to go to MJA and work up from there. There will only be one OTA update taken and that's from MJA to MK2. Once on MK2 follow Sacs instructions on how to flash the rom and you'll be good to go.
Thanks go out to Unknown and rwilco for their hard work and dedication
hAvAAck said:
Hey all, I need some help trying to troubleshoot what went wrong. Note between every flash I did clear cache and full formats of the whole phone.
I was on SACS 4.3 ROM, MK2 and already had CWM recovery
I ODINed the NAE modem, it stuck - my baseband and software say L720VPUFNAE
I flashed SACS 4.4.2 ROM, it went well booted up and setup, but could not provision the network (I had wifi)
I reflashed SACS 4.4 a couple times, same problems. Tried AOKP 4.4, glitchy and froze a lot.
Flashed stock NAE from sprint, installed, but stuck on provisioning again. I checked and it didn't show I had NAE, it showed my baseband and software was UNKNOWN.
Flashed back to SACS 4.3 and everything works well again. Still shows NAE as the baseband and whatnot.
I would have thought I had a bad modem flash, but everything works and shows NAE. What is the issue?
Click to expand...
Click to collapse
---------- Post added at 01:59 PM ---------- Previous post was at 01:55 PM ----------
I bet you a buck you are not on the right bootloader. Check this using Device info which you can get from the app store. Then foolow the previous instructions i attached.
hAvAAck said:
Hey all, I need some help trying to troubleshoot what went wrong. Note between every flash I did clear cache and full formats of the whole phone.
I was on SACS 4.3 ROM, MK2 and already had CWM recovery
I ODINed the NAE modem, it stuck - my baseband and software say L720VPUFNAE
I flashed SACS 4.4.2 ROM, it went well booted up and setup, but could not provision the network (I had wifi)
I reflashed SACS 4.4 a couple times, same problems. Tried AOKP 4.4, glitchy and froze a lot.
Flashed stock NAE from sprint, installed, but stuck on provisioning again. I checked and it didn't show I had NAE, it showed my baseband and software was UNKNOWN.
Flashed back to SACS 4.3 and everything works well again. Still shows NAE as the baseband and whatnot.
I would have thought I had a bad modem flash, but everything works and shows NAE. What is the issue?
Click to expand...
Click to collapse
KC6UFO said:
]I bet you a buck you are not on the right bootloader. Check this using Device info which you can get from the app store. Then foolow the previous instructions i attached.
Click to expand...
Click to collapse
I was on MK not MF.
bioshocked said:
go to the Phone dial pad and punch in ##786# to pull up the RTN screen, It'll show you more accurate info on than what your Baseband and Software ect. The first time I flashed Sacs 4.4 V1 I flashed it using Phils 6.0.4.7, had the same problem. got it to flash flawlessly using the same process, but using Philz 6.0.4.6. just to be sure that was the issue i repeated process using 6.0.4.7, same problem, wouldnt provision network, just wifi, everything said unknown. couldnt make it work using 6.0.4.7. Tried again using 6.0.4.6, and again everything worked perfect ALSO try flashing the stock NAE.tar.md5 first, then Sacs 4.4 v2. Ive read that worked for many, Your problem is most likey CWM. flash Philz 6.0.4.6 then re try, let me know how it goes
Click to expand...
Click to collapse
I flashed stock NAE and then SACS, same problem. Where can I find Philz 6.0.4.6? All I see are 6.07 and 6.19
Now I'm back stock NAE not rooted and I can't seem to charge the phone. Everytime the screen goes to sleep it wakes back up to reconnect the charger..
leaderbuilder said:
@hakeem0996
If you were on MJA/MK2 bootloader you CANNOT Odin to anything before that - MF9 etc.
You'll need to PC Odin MK2 full tar to get back to stock. That tar is here.
For the others if you have a MK2 or NAE bootloader why not flash the full .tar of either one (MK2 or NAE) - both are available here. Full .tar will restore baseband and ALL partitions.
The for both the above root via CF-Autoroot, install recovery via PC Odin or goomanager - I'd go with Philz via PC Odin.
Then install what ever you want following the developer's instructions.
Click to expand...
Click to collapse
Thanks for your advice I flashed MK2 and flashed 4.3 scas rom and i'm no longer on NAE thank i can play videos again on my phone now my new problems is that my data is really weak now my phone can't even go to the play store without loading for what seamed an eternity . Is there a way i can fix that ? is there a code i can punch in tha reset my signal to make my data stronger .Sorry for nugging you guys .
hakeem0996 said:
Thanks for your advice I flashed MK2 and flashed 4.3 scas rom and i'm no longer on NAE thank i can play videos again on my phone now my new problems is that my data is really weak now my phone can't even go to the play store without loading for what seamed an eternity . Is there a way i can fix that ? is there a code i can punch in tha reset my signal to make my data stronger .Sorry for nugging you guys .
Click to expand...
Click to collapse
update the PRL and Profile in System Updates
leaderbuilder said:
update the PRL and Profile in System Updates
Click to expand...
Click to collapse
i did that already
hakeem0996 said:
i did that already
Click to expand...
Click to collapse
What modem/baseband are you on?
Related
Ok. After 24hours of no sleep i finally recovered my phone from the soft brick state it was after i flashed the wrong kernel when i was in stock 4.3.Now am back to sacs 8 though no wifi works and phone is rebooting and fc everything. I want to flash back to stock 4.2.2 but odin refuses. If you need any logs to be generated so you might help please tell me exactly what you need and ill provide
tasked28m said:
Ok. After 24hours of no sleep i finally recovered my phone from the soft brick state it was after i flashed the wrong kernel when i was in stock 4.3.Now am back to sacs 8 though no wifi works and phone is rebooting and fc everything. I want to flash back to stock 4.2.2 but odin refuses. If you need any logs to be generated so you might help please tell me exactly what you need and ill provide
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2508411
Sent from my SPH-L720 using xda app-developers app
what did you do? im trying to use KIES but i dont have the serial.. can you msg me your serial so i can atleast get KIES to download the software? msg me
Kies won't work if u updated to 4.3. Kies 3 won't work either. If u soft bricked ur phone flash the cf auto root tar. It will fix ur error. We're just stuck with 4.3 for now.
Sent from my SPH-L720 using XDA Premium 4 mobile app
kies wont do anything. After 4.3 update we can not downgrade. My issue is i cant boot into stock 4.3. I can only flash octos or other roms but with phone not working and problems as such.
ok somehow i fixed this. I followed the instructions using twrp recover. Only difference is that after i recovered modem and radio through custom twrp method, i used cf autoroot to get stock recovery back then used the update.zip posted in another forum, to update through sideload and it worked. Back in stock 4.3.
tasked28m said:
ok somehow i fixed this. I followed the instructions using twrp recover. Only difference is that after i recovered modem and radio through custom twrp method, i used cf autoroot to get stock recovery back then used the update.zip posted in another forum, to update through sideload and it worked. Back in stock 4.3.
Click to expand...
Click to collapse
which update.zip?
slackwaresupport said:
which update.zip?
Click to expand...
Click to collapse
the 4.3 update.zip that got pulled out of someones phone before he fully updated from 4.2.2 to 4.3. You can find the zip file in the General section i think.
I was on stock 4.2.2 got the update and went to 4.3. Then i flashed a 4.3 tw kernel and everything got screwed. After that i went followed the instructions found here http://forum.xda-developers.com/showthread.php?p=47113608#post47113608. First i recovered boot , then system , then modem then radio through twrp using the files found there. After that i booted used the cf auto root to go back to stock recovery. Phone was still doing the boot loop up to this point. Then i figured out that the backup was probably a 4.2.2 backup so i used adb sideload to install update.zip. After that i wipe data/factory reset and it booted just fine. Ok lost everything but phone works now like new.
Hello everyone I have a weird issue here and I am in need of some help. I was running a stock MK2 rooted rom, with the modem/firmware MK2 with the MF9 bootloader. When the first NAE (4.4) ROM popped up I decided to give it a try and installed it without getting the NAE modem first. The ROM wouldn't get past the splash screen and other users experienced this too, I figured I should get the NAE modem so I installed it and rebooted hoping it would get past the splash screen. I came to a conclusion that it probably isnt going to work right now so I did a nandroid restore back to my stock MK2 ROM. Upon booting it up I had no data, signal bars with a red X and in About Device section it says baseband unknown and in the status section everything is unknown or has no field. I thought my modem was broken so I tried a 4.4 kitkat ROM OctOS which worked perfectly and I got signal on that ROM. So this brings to me another hypothesis that my modem is fine as I could make calls and what not, no issues. However I tried reinstalling stock MK2 and for some reason I get no signal...
I am not sure whats going on here, I tried a MF9 Stock Tar and formatted the whole phone, tried installing MK2 and MF9 modem and I get no signal on the stock MK2 ROM. I am a little lost here and asking the XDA community for help, I really want to go back to my old setup. Please help me out here.
My situation is kinda similar to yours. I also had no service and got an Unknown baseband message in Settings when I went from stock rooted MK2 (with stock MK2 kernel and MF9 bootloader) to the new NAE ROM and NAE baseband.
I suspect that NAE requires a Knox bootloader for service to work.
Anyhow, to go back to a fully functional MK2 state, here's what I did:
1. Restored my MK2 Nandroid using Philz's recovery.
2. Booted directly into Download mode from Philz and flashed back the MK2 modem with Odin 3.07.
3. Rebooted phone and everything fully works again.
Sent from my Nexus 5 using Tapatalk
modem didn't stick maybe?
Had issues playing with the new modem and nae ROMs. Unknown baseband and no days. Even a ##72786# led to a blank screen with no option to reset. So I played around with different install techniques and got a ROM to fully function.
Unknownforces stock rooted nae. From android development forum.
1. Clean to install new ROM using Philz 6.0.8.9(what I used) said any can be used
2. Even of you have already flashed new modern do it again now
A. Power completely off
B. Go into download mode
C. Odin new NAE modem(auto reboot and freset unchecked)
D. After Pass reboot into recovery
3. Clean wipe for new install
4. Install unknown forces ROM
5. Reboot and enjoy data working and WiFi working
I am currently on Sacs custom rom 4.3_v5.6 (latest build) trying to get back to stock 4.4.2 NAE. I have been flashing roms on a pretty consistent basis for about 2 years not but I am stumped this time. I open ODIN and run as an administrator as always, load my stock .tar file into the PDA slot and let it go through the checking process and then I hit start. It starts going for 2 seconds and then fails. I then have to do a battery pull to restart the phone and then my phone hangs up on the "Firmware update was interrupted, please connect to kies screen and that's as far as I can get. I have factory reset phone at least 10 times today. Like I said, I am stumped...any advice would be appreciated.
omahaguy said:
I am currently on Sacs custom rom 4.3_v5.6 (latest build) trying to get back to stock 4.4.2 NAE. I have been flashing roms on a pretty consistent basis for about 2 years not but I am stumped this time. I open ODIN and run as an administrator as always, load my stock .tar file into the PDA slot and let it go through the checking process and then I hit start. It starts going for 2 seconds and then fails. I then have to do a battery pull to restart the phone and then my phone hangs up on the "Firmware update was interrupted, please connect to kies screen and that's as far as I can get. I have factory reset phone at least 10 times today. Like I said, I am stumped...any advice would be appreciated.
Click to expand...
Click to collapse
You need to get back to compete stock to take ota. Go here http://forum.xda-developers.com/showthread.php?t=2660607
Read that thread on how to get to mja stock, then run system/fitness update on the phone: in settings. And take the ota
Sent from my SPH-L720 using XDA Premium 4 mobile app
omahaguy said:
I am currently on Sacs custom rom 4.3_v5.6 (latest build) trying to get back to stock 4.4.2 NAE. I have been flashing roms on a pretty consistent basis for about 2 years not but I am stumped this time. I open ODIN and run as an administrator as always, load my stock .tar file into the PDA slot and let it go through the checking process and then I hit start. It starts going for 2 seconds and then fails. I then have to do a battery pull to restart the phone and then my phone hangs up on the "Firmware update was interrupted, please connect to kies screen and that's as far as I can get. I have factory reset phone at least 10 times today. Like I said, I am stumped...any advice would be appreciated.
Click to expand...
Click to collapse
Were you already on NAE from the OTA before you installed Sacs rom?? If you were, then you can't go back to NAE stock until we have a full tar file for NAE. You can try to install one of the Stock NAE roms in the development section, but until we have the full tar file for NAE you can't odin back to stock, If you weren't already on the NAE OTA, and still have the MK2 bootloader, then odin the full MK2 tar and apply the NAE OTA.
Here is a good place to download MK2: http://forum.xda-developers.com/showthread.php?t=2601443
Remember, if you already are on NAE, you cannot odin older tar files so you have to wait until the full NAE tar is available.
cruise350 said:
Were you already on NAE from the OTA before you installed Sacs rom?? If you were, then you can't go back to NAE stock until we have a full tar file for NAE. You can try to install one of the Stock NAE roms in the development section, but until we have the full tar file for NAE you can't odin back to stock, If you weren't already on the NAE OTA, and still have the MK2 bootloader, then odin the full MK2 tar and apply the NAE OTA.
Here is a good place to download MK2: http://forum.xda-developers.com/showthread.php?t=2601443
Remember, if you already are on NAE, you cannot odin older tar files so you have to wait until the full NAE tar is available.
Click to expand...
Click to collapse
I was on the stock NAE update, so I guess I am stuck until then, not a big problem.
Sacs 4.4.2
Hi all,
Noobie here,
So I couldn't wait either- a junkie per say for a half a dozen Roms but find Sacs Rom to be most impressed with. As Sacs pointed out in the step by steps instructions- when quite successful, as others have pointed out with the camera issue which is a very small and all most not relevant at this time, with wifi I had no issues at all- did run across a small blurb about android.- something was crashing---- But I'm still enjoying it- don't plan to fall back- I am noticing the battery drains a little faster on use- did fix the toggle battery size through 3mint- awesome... Now I'm just waiting on to mods/themes as previous Sacs roms- I've tried loading the pervious versions but found it crashed the Samsung keyboard- so I reflashed 4.4.2------ Thanks for being ahead on this Sacs- great work...
Hello.First post here.
I currently have been using CM11 for a few months now but miss some features on stock. (multiwindow, air view) so I installed Sacs ROM.
Everything was working great today except a known problem is wifi will not work due to radio opbstructions (i believe). So i attempted to change the baseband to MF9.
At first, Odin started then immidately it failed. The error read 'Fused 4 Binary 1'
So i assumed it was a connection error. I loaded back into download mode and tried again. Failed.
At this point i thought screw it, and took the battery out. tried to reboot and stuck at the soft brick "Firmware upgrade encountered and issue. Please select recovery mode in Kies and try again"
I installed Kies. Plugged in my phone. Drivers installed but Kies will not connect. Try to do 'Firmware Upgrade and Initialization'
However Kies will NOT accpet my S/N number. i tried everything. writing it all out or with a space every 3 numbers or with 'DEC' at the front. nothing worked.
I even called sprint to double check S/N (ESN/DEC)
so basically I'm soft bricked and Kies is screwing me over. Any ideas?
Have you tried to odin back to stock?
Sent from my SPH-L720 using XDA Premium 4 mobile app
ROMANTiC KiD said:
Have you tried to odin back to stock?
Sent from my SPH-L720 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
thats the one thing i want to avoid.
by reverting to stock wont i lose root access? i have a backup of my old CM ROM from before i flashed sacs. should i revert to stock then restore to CM then reinstall Sacs?
whatthe_fuzz said:
thats the one thing i want to avoid.
by reverting to stock wont i lose root access? i have a backup of my old CM ROM from before i flashed sacs. should i revert to stock then restore to CM then reinstall Sacs?
Click to expand...
Click to collapse
Yes but it takes all but about 30 seconds to root again
You could go straight to sacs after rooting.
Sent from my SPH-L720 using Tapatalk
daniel4653 said:
Yes but it takes all but about 30 seconds to root again
You could go straight to sacs after rooting.
Sent from my SPH-L720 using Tapatalk
Click to expand...
Click to collapse
ok that might leave me with a cleaner install also.
wheres the stock file i can flash on Odin?
also how should i update the radio if it didnt work the first time?
Thank you for the help
whatthe_fuzz said:
ok that might leave me with a cleaner install also.
wheres the stock file i can flash on Odin?
also how should i update the radio if it didnt work the first time?
Thank you for the help
Click to expand...
Click to collapse
If you flash a full stock tar you won't have to flash radio.
Do a search please for the tar.
Sent from my SPH-L720 using XDA Premium 4 mobile app
leaderbuilder said:
If you flash a full stock tar you won't have to flash radio.
Do a search please for the tar.
Sent from my SPH-L720 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
i searched around and eventually found a working .md5 file. its apparently is stock. got my phone to start booting but it got stuck at the yellow sprint screen. im going to try to boot into safe mode. any ideas how to access my recovery file? i have one form CWM and one from Ti Backup
which tar did you flash through Odin? MF9, MK2 or NAE?
IF you were on MF9 and flashed the full MF9 tar you can try and flash again. Just power off phone completely, go to download mode, attach and run Odin. (same for MK2 or NAE) BUT if you tried flashing MJA/MK2 or NAE you cannot go back to MF9. Things you should have read about already.
If it hangs on boot after flashing, power off completely, boot to stock recovery and do a factory reset and then let it restart first reboot can take 5 to 10 earth minutes.
You can then root via CF-Autoroot or Saferoot, install goomanager to grab a custom recovery (CWM or TWRP) OR Odin said recoveries (Philz, TWRP etc.)
leaderbuilder said:
which tar did you flash through Odin? MF9, MK2 or NAE?
IF you were on MF9 and flashed the full MF9 tar you can try and flash again. Just power off phone completely, go to download mode, attach and run Odin. (same for MK2 or NAE) BUT if you tried flashing MJA/MK2 or NAE you cannot go back to MF9. Things you should have read about already.
If it hangs on boot after flashing, power off completely, boot to stock recovery and do a factory reset and then let it restart first reboot can take 5 to 10 earth minutes.
You can then root via CF-Autoroot or Saferoot, install goomanager to grab a custom recovery (CWM or TWRP) OR Odin said recoveries (Philz, TWRP etc.)
Click to expand...
Click to collapse
I think i fixed it.
Problems resolved.
The issue was i had Sacs v4 which didnt support wifi and i read that it needed MF9 firmware.
i had a lapse in judgement and without thinking tried to go back from MJA. didnt catch it until now.
I eventually found the correct stock file. eventually got into the phone. rerooted and in the process of install the proper sacs ROM (v5.6)
this was a simple error that i shouldve caught thanks guys!
hopefully this ROM will work with wifi...
BTW, all my backups were wiped
Your backups weren't on your external sd? Ooo, that sucks. Glad you got it.
Sent from my SPH-L720 using XDA Premium 4 mobile app
I followed the instructions in the thread that describes how to update to NAE from MF9 while keeping the MF9 bootloader: http://forum.xda-developers.com/showthread.php?t=2277480
I was on MF9 stock rooted (with TWRP recovery installed when I flashed the NAE modem via odin 3.0.7, not sure if that makes a difference).
All the steps seemed to go okay. As far as I can tell the versions look good. However, the device is super sluggish at times, especially the dialer. Sometimes I have trouble waking it. I can't toggle the WiFi on. I have not set the hotspot mod or sd card mod yet.
The device is essentially unusable. Every so often I will get a request to force close some app (like the dialer) because it is hanging.
I tried repeating the steps described in the thread above over and still get the same behavior. The second time I also did some more checking in the intermediary MK2 step after everything was set up and I did notice that sometimes it was doing the weird hanging problems there too (i.e. even before the NAE rom was installed).
I had no problems whatsoever with the device when it was on MF9.
Help! Any ideas??
Have you tried to install the nae modem. Its been observed that you need to install it in order to get full use of a NAE rom
Sent from my SPH-L720 using Tapatalk
daniel4653 said:
Have you tried to install the nae modem. Its been observed that you need to install it in order to get full use of a NAE rom
Sent from my SPH-L720 using Tapatalk
Click to expand...
Click to collapse
Yes, that is the very first step in the instructions. For good measure I even went back and reinstalled the NAE modem (even though it appeared to be successful).
I am thinking maybe I should go back and try to install/downgrade back to the MF9 modem to see if that would help.
Update: Everything seems okay now. I went back and flashed the MK2 modem, then reinstalled the MK2 ROM, then the NAE modem, booted into MK2 to see that it was okay, then installed the NAE rom. So far so good :fingers-crossed:
Reverting back to MF9 from NAE
myphone12345 said:
Yes, that is the very first step in the instructions. For good measure I even went back and reinstalled the NAE modem (even though it appeared to be successful).
I am thinking maybe I should go back and try to install/downgrade back to the MF9 modem to see if that would help.
Update: Everything seems okay now. I went back and flashed the MK2 modem, then reinstalled the MK2 ROM, then the NAE modem, booted into MK2 to see that it was okay, then installed the NAE rom. So far so good :fingers-crossed:
Click to expand...
Click to collapse
Anyone got the instructions to revert back to MF9 from NAE, I installed 4.4.2 and NAE but it is very buggy, slow , sometimes unresponsive. Like to get back to MF9.
This is the link to what steps I took. http://forum.xda-developers.com/showthread.php?t=2277480
Thank you
zeplman said:
Anyone got the instructions to revert back to MF9 from NAE, I installed 4.4.2 and NAE but it is very buggy, slow , sometimes unresponsive. Like to get back to MF9.
This is the link to what steps I took. http://forum.xda-developers.com/showthread.php?t=2277480
Thank you
Click to expand...
Click to collapse
You could flash a MF9 stock rooted zip. Or Odin MF9 tar.
Sent from my SPH-L720 using Tapatalk
myphone12345 said:
I followed the instructions in the thread that describes how to update to NAE from MF9 while keeping the MF9 bootloader: http://forum.xda-developers.com/showthread.php?t=2277480
I was on MF9 stock rooted (with TWRP recovery installed when I flashed the NAE modem via odin 3.0.7, not sure if that makes a difference).
All the steps seemed to go okay. As far as I can tell the versions look good. However, the device is super sluggish at times, especially the dialer. Sometimes I have trouble waking it. I can't toggle the WiFi on. I have not set the hotspot mod or sd card mod yet.
The device is essentially unusable. Every so often I will get a request to force close some app (like the dialer) because it is hanging.
I tried repeating the steps described in the thread above over and still get the same behavior. The second time I also did some more checking in the intermediary MK2 step after everything was set up and I did notice that sometimes it was doing the weird hanging problems there too (i.e. even before the NAE rom was installed).
I had no problems whatsoever with the device when it was on MF9.
Help! Any ideas??
Click to expand...
Click to collapse
I had the same exact problem and I found a way to fix that so I can run NAE.. I read someone post and I just did these step to have a perfect running NAE stock rom.
Steps How To Install NAE (Odex) properly with MF9 Bootloader
1. Back-up apps with Titanium Backup or MyBackup
2. Download the following tools and files to have on-hand
A. Odin 3.07
B. CF-Root
C. Philz Recovery [I used the latest one 6.41.6.tar.md5]
D. MF9.tar Official
E. MK2 Modem.tar (No Firmware)
F. Stock MK2 Odex ROM (No Bootloader)
G. NAE Modem.tar (No Firmeware)
H. Stock NAE.Odex Rom (No Bootloader)
I. SDCard Fix for NAE
J. Hotspot Mod NAE (Odex) [If you want Hotspot]
3. Put the following files on your External SDcard from Step 2 (E,G,H,I)
4. Start by opening up Odin 3.07, and flashing MF9.tar (Make sure everything is unchecked but Auto Reboot)
5. Once flashed let the phone boot up and skip all the steps of setting up your phone. Then check to see if your baseband and firmeware is on MF9. If thats all okay completely shut down your phone.
6. Go back to Download Mode and to Odin. Then flash CF-Root (Make sure everything is unchecked but Auto Reboot)
7. Once its booted shut down and back to Download Mode and to Odin then flash MK2 Modem.tar (Make Sure Everything Is Unchecked) Once that is done Hold the power button for 10 seconds.
8. Boot up and check your baseband and firmeware in About Phone. Once everything is okay shut down the phone.
9. Boot your phone into Philz Recovery Mode then find and Install Stock MK2 Rom
10. Boot up the phone and skip all the steps setting up your phone, Do the lockscreen fix shut down your phone.
11. Go back to Odin and Flash NAE.Modem tar file (Make sure everything is unchecked) Hold the power button for 10 seconds
12. Reboot into Philz Recovery Do the wipe to do a Clean Install of Rom
13. Install Stock NAE Rom then Boot Up
14. Shut down and go back to recovery and install the SDCard Fix and Hotspot then Reboot
Then you can get Triangle Away and wipe your counter clean.
This is what I did and it worked perfect several times without problems.
(Optional part if you want to reset custom ROM counter)
1. Odin flashed a full stock firmware (ROM and all) MF9 or below (I had MDL tar already so just used that)
2. CF-Root the installed rom.
3. Run Triangle Away to reset boot counter.
(Main part)
1. Odin flash TWRP recovery .tar and did a full wipe.
2. Odin flash Mf9 AIO .tar
3. Odin flash MK2 modem only .tar (NAE won't stick unless you do this first)
4. Odin flash NAE modem only .tar
5. Odin flash TWRP (You can use other recoveries for some other ROMS, but most NAE roms including Sacs Custom ROM and NAE stock rooted need TWRP to install properly or you get no cell. I haven't tried it on CWM, but know when I tried it wouldn't work on PhilZ Touch)
7. full data wipe using the recover for good measure (not necessary, it should be clear already)
6. Flash your ROM in recovery (I used stock rooted NAE)
8. Flash your add-ons, mobile hotspot, boot screen, kernel , etc. (I just flashed the odex mobile hotspot for NAE and a boot screen, left the kernel at stock because of a camera issue ktoonsez seemed to be presenting)
9. Reboot and enjoy.
(Note, only if using NAE stock rooted)
If your using the NAE stock rooted you will need and want to run and let the pre-installed supersu app disable Knox, then using an SE linux status changing app from the app store you will need to temporarily change your SE linux status. From there you can install the Xposed Framework and Wanam Xposed. In Wanam Xposed you can set the SE linux status so it wont reactivate after a reboot. Now you can uninstall the SE linux switcher you downloaded before. Next you can download an app that will do it, or manually fix the SD card write permissions. Finally using a root exploring file manager you can fix the permissions to make the lock screen work.
CatFood said:
This is what I did and it worked perfect several times without problems.
(Optional part if you want to reset custom ROM counter)
1. Odin flashed a full stock firmware (ROM and all) MF9 or below (I had MDL tar already so just used that)
2. CF-Root the installed rom.
3. Run Triangle Away to reset boot counter.
(Main part)
1. Odin flash TWRP recovery .tar and did a full wipe.
2. Odin flash Mf9 AIO .tar
3. Odin flash MK2 modem only .tar (NAE won't stick unless you do this first)
4. Odin flash NAE modem only .tar
5. Odin flash TWRP (You can use other recoveries for some other ROMS, but most NAE roms including Sacs Custom ROM and NAE stock rooted need TWRP to install properly or you get no cell. I haven't tried it on CWM, but know when I tried it wouldn't work on PhilZ Touch)
7. full data wipe using the recover for good measure (not necessary, it should be clear already)
6. Flash your ROM in recovery (I used stock rooted NAE)
8. Flash your add-ons, mobile hotspot, boot screen, kernel , etc. (I just flashed the odex mobile hotspot for NAE and a boot screen, left the kernel at stock because of a camera issue ktoonsez seemed to be presenting)
9. Reboot and enjoy.
(Note, only if using NAE stock rooted)
If your using the NAE stock rooted you will need and want to run and let the pre-installed supersu app disable Knox, then using an SE linux status changing app from the app store you will need to temporarily change your SE linux status. From there you can install the Xposed Framework and Wanam Xposed. In Wanam Xposed you can set the SE linux status so it wont reactivate after a reboot. Now you can uninstall the SE linux switcher you downloaded before. Next you can download an app that will do it, or manually fix the SD card write permissions. Finally using a root exploring file manager you can fix the permissions to make the lock screen work.
Click to expand...
Click to collapse
Thanks fir this. I flashed one modem than the next one right after and wifi fixed. Been working on this all day glad I found this thread
Cheryl