Device behaving badly after updating to NAE while keeping MF9 bootloader - Sprint Samsung Galaxy S 4 Q&A, Help & Troubleshoot

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

Related

Baseband Unknown on MK2 based ROM

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

[Q] NAE but can't run KitKat

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?

Upgrading from MJA to latest(NG2?)

Hello,
I have a MJA rom (with TRWP) and rooted. I never updated it in past, but i want to upgrade now.
I understand, we need to have stock recovery to flash the new updates. I searched a lot and couldnt find it. Could someone please help me out with this?..
I dont have any issues with KNOX .. etc
Just need safe route to upgrade to new version on my s4(and root it back).
thanks!!:good:
You first need to upgrade your phone to NAE via Odin to return your phone to an unaltered stock condition. You can get the tar file from random45's thread in the android development section. You will not lose data with the update, but I do recommend you use Odin 3.07 or 3.09. After you are updated to NAE you will have to goto settings menu and select samsung software updates to check if NG2 is available for download. After you update you can then use cfautoroot or towel root to reroot your phone. If your rooting to use the hotspot hack, just upgrade to NAE, since there isn't a hack for NG2 yet.
Sent from my icrap 2 using Tapatalk HD
Thankyou for the detailed post. I was finally able to update without any serious issues.
1) flashed NAE through odin. No issues, no errors. successful flash.
2) downloaded ng2 update.zip from here and tried installing it from recovery. Errored out. (dont remember the exact error)
3) went back to recovery -- factory reset, wipe cache, restart and try update.zip . same error.
4) started up phone and checking if all is ok, saw the baseband still showed MJA while software showed NAE.
5) Odin'ed the modem/firmware of NAE.
6) checked the status and it showed upgraded baseband.
7) I then went to recovery and retried NG2 update.zip again & updated successfully.
8) rooted with CF auto & restored apps and data from titanium.

Flipping Back to Use SafeStrap

I am currently running Optimal ROM with OD5 bootloader. Just got back into the rooted world last week after a warranty replacement stroke of luck. To be able to access SS to flash a different ROM, do I just flash the NCG kernel I have and boot?
Edit: Been out of the loop for a while and don't want to bork this thing
Anybody?
You can use flashfire which is a mobile odin and is in the playstore [root]Flashfire or you can safestrap. http://forum.xda-developers.com/verizon-galaxy-s5/general/guide-safestrap-access-odin-t3126686. Install busybox and and the safestrap bo3 in the link I provided. Make sure you install ss after busybox. The NI2 kernal flasher when used will install a kitkat kernel and bring you into ss.
Before all this download this zip and extract it.https://www.androidfilehost.com/?fid=24052804347777436 What you are looking to keep are the firmware and kernel zips. YOU MUST FLASH A KERNEL OR FIRMWARE AS THE LAST THING BEFORE EXITING SS. Otherwise you will get a blank screen.
Solution if you forget - battery pull - restart phone - ss symbol will appear - hit it and reenter ss.
Place everything I've told you to download on your ext sd. When you wipe - do not wipe ext sd.
example - If you're going from od5 to og5 you will ant to flash the og5 kernel as the last thing before leaving ss- just follow the rom's installation instructions to the letter
SS is already installed. I am running Optimal w/OD5 bootloader. I was wondering if just flashing NCG kernel would boot me back to SS screen. I'm old school and have been using Odin haven't tried FF and seem to see more posts of bricks with peeps using FF.
can flash kernel via odin
Chopstix9 said:
SS is already installed. I am running Optimal w/OD5 bootloader. I was wondering if just flashing NCG kernel would boot me back to SS screen. I'm old school and have been using Odin haven't tried FF and seem to see more posts of bricks with peeps using FF.
Click to expand...
Click to collapse
can flash kernel via odin if you are more comfortable with it... i would use the ni2 kernel that was mentioned in the earlier post

Really old modem and bootloader, what are my options from here?

It's been a while since I've flashed anything; at least a year, though more likely two. Whatever I have now I'm guessing is a rom called stock(ish)v06, since that's what is listed in my bootloader. I guess the modem (baseband?) is NAE, and I'm still using a very old version of TWRP (2.6.3 according to my signature, haven't checked).
Obviously, the development that still exists for this device has moved well past me. But given how temperamental my device has been lately, I want to give flashing something newer a shot before buying a new device.
Trouble is, I'm not sure how to go about flashing roms and finding the right modem/firmware when everything I have is so out of date.
Suggestions?
beerindex said:
It's been a while since I've flashed anything; at least a year, though more likely two. Whatever I have now I'm guessing is a rom called stock(ish)v06, since that's what is listed in my bootloader. I guess the modem (baseband?) is NAE, and I'm still using a very old version of TWRP (2.6.3 according to my signature, haven't checked).
Obviously, the development that still exists for this device has moved well past me. But given how temperamental my device has been lately, I want to give flashing something newer a shot before buying a new device.
Trouble is, I'm not sure how to go about flashing roms and finding the right modem/firmware when everything I have is so out of date.
Suggestions?
Click to expand...
Click to collapse
Download latest fully stock firmware so you will have latest bootloader and modem from http://www.sammobile.com
which is Lollipop, then flash latest TWRP. If you like stock, there is a stock deodex ROM, there is the awesome Wicked X (heavily modified Lollipop stock), or if stock is not your thing you can get CM12(Lollipop) or CM13 official(Marshmallow)
Sent from my SCH-R220
mattzeller said:
Download latest fully stock firmware so you will have latest bootloader and modem from http://www.sammobile.com
which is Lollipop, then flash latest TWRP. If you like stock, there is a stock deodex ROM, there is the awesome Wicked X (heavily modified Lollipop stock), or if stock is not your thing you can get CM12(Lollipop) or CM13 official(Marshmallow)
Sent from my SCH-R220
Click to expand...
Click to collapse
I want to make sure I understand what you're telling me to do, so a few clarifying questions:
1) I am meant to be updating TWRP first, then using it to flash stock firmware to update the bootloader and modem, and then flashing a rom of my choosing?
2) Why is that method preferable to using Odin to update the modem?
3) If I flash this newer official firmware, am I going to lose root?
4) In flashing the newer firmware, won't my bootloader lock, making it not possible to flash a new rom?
beerindex said:
I want to make sure I understand what you're telling me to do, so a few clarifying questions:
1) I am meant to be updating TWRP first, then using it to flash stock firmware to update the bootloader and modem, and then flashing a rom of my choosing?
2) Why is that method preferable to using Odin to update the modem?
3) If I flash this newer official firmware, am I going to lose root?
4) In flashing the newer firmware, won't my bootloader lock, making it not possible to flash a new rom?
Click to expand...
Click to collapse
1) No, use Odin to flash full stock that you downloaded from sammobile.com, you cannot flash full stock from recovery.
2) Because some if not most newer ROMs require you to be on Lollipop bootloader.
3) Yes you will lose root, but this flashing of stock firmware is to update your bootloader and modem so you can flash the newest ROMs. The lack of root doesn't matter since you will be flashing latest TWRP via Odin and modified ROMs soon after.
4) if you have Sprint L720 the bootloader isn't locked. Check I'm 'about phone' to make sure you have an L720 and not another variant of S4
Make sure Samsung drivers are installed on your computer.
So your flashing steps go as follows:
1) Download everything you need first:
a) Full stock from http://www.sammobile.com to your computer
b) Latest TWRP tar file to your computer
c) The custom ROM of your choice (and correct gapps if AOSP or CM based) saved on external SD card on your phone since it will be flashed via recovery.
2) Turn phone off completely. I pull the battery then put it back in then boot directly to download mode: power + volume down. (Rebooting to download mode doesn't always allow a proper flashing)
3) Start Odin (uncheck reboot and reset time) and then plug phone into computer.
4) If COM lights up green in Odin click AP and select the file you downloaded from sammobile (it will be PDA instead of AP if you are using an older version of Odin) and click OK or start (I don't remember which it has)
5) If it flashes successfully pull the battery and then put it back in and turn the phone on normally. It will take a while to boot, like 15-20 minutes possibly. Flashing stock myself I have seen it say it was successful and it wasn't and the fix for me was to leave reset checked and let it do it's thing.
6) Once you have booted into your newly flashed stock OK3, do step 2 and 3 again, so you can flash TWRP.
7) When you go to flash TWRP in Odin uncheck reset time and DEFINITELY have reset unchecked (if Odin reboots your phone TWRP doesn't stick). Do step 4 again except this time select the TWRP tar file. Once it flashes successfully pull battery put it back in and boot directly to recovery (power + volume up) from there do a backup if you want, if not you can flash the custom ROM and gapps if necessary that you downloaded earlier.
Sent from my SCH-R220
mattzeller said:
1) No, use Odin to flash full stock that you downloaded from sammobile.com, you cannot flash full stock from recovery.
2) Because some if not most newer ROMs require you to be on Lollipop bootloader.
3) Yes you will lose root, but this flashing of stock firmware is to update your bootloader and modem so you can flash the newest ROMs. The lack of root doesn't matter since you will be flashing latest TWRP via Odin and modified ROMs soon after.
4) if you have Sprint L720 the bootloader isn't locked. Check I'm 'about phone' to make sure you have an L720 and not another variant of S4
Make sure Samsung drivers are installed on your computer.
So your flashing steps go as follows:
1) Download everything you need first:
a) Full stock from http://www.sammobile.com to your computer
b) Latest TWRP tar file to your computer
c) The custom ROM of your choice (and correct gapps if AOSP or CM based) saved on external SD card on your phone since it will be flashed via recovery.
2) Turn phone off completely. I pull the battery then put it back in then boot directly to download mode: power + volume down. (Rebooting to download mode doesn't always allow a proper flashing)
3) Start Odin (uncheck reboot and reset time) and then plug phone into computer.
4) If COM lights up green in Odin click AP and select the file you downloaded from sammobile (it will be PDA instead of AP if you are using an older version of Odin) and click OK or start (I don't remember which it has)
5) If it flashes successfully pull the battery and then put it back in and turn the phone on normally. It will take a while to boot, like 15-20 minutes possibly. Flashing stock myself I have seen it say it was successful and it wasn't and the fix for me was to leave reset checked and let it do it's thing.
6) Once you have booted into your newly flashed stock OK3, do step 2 and 3 again, so you can flash TWRP.
7) When you go to flash TWRP in Odin uncheck reset time and DEFINITELY have reset unchecked (if Odin reboots your phone TWRP doesn't stick). Do step 4 again except this time select the TWRP tar file. Once it flashes successfully pull battery put it back in and boot directly to recovery (power + volume up) from there do a backup if you want, if not you can flash the custom ROM and gapps if necessary that you downloaded earlier.
Sent from my SCH-R220
Click to expand...
Click to collapse
Thanks for the very detailed response. This totally clears up my questions. I'll charge my phone this evening and give it a shot in the morning when my battery is at 100%. :good:
beerindex said:
Thanks for the very detailed response. This totally clears up my questions. I'll charge my phone this evening and give it a shot in the morning when my battery is at 100%. :good:
Click to expand...
Click to collapse
Feel free to post back here or PM me if you have any more questions or problems, it wouldn't be the first time walking someone through the process via pm here or other methods
Sent from my SCH-R220

Categories

Resources