Is there a single ROM out there for someone who went from MDL(I am pretty sure), who then ODIN'd MF9 way back last year...who then ODIN'd NAE MODEM ONLY, and is able to use their phone or camera, on ANY ROM whatsoever?
ive tried Negalite and SACS...using philz and twrp respectively, full wipes and all...roms install, some better than others...but on neither can I use phone or camera...and in 12 hours I am going to be halfway across the ocean
if anyone who knows of a similar situation, and has an idea for a rom that I can use while currently on MF9 bootloader, but NAE modem...pls help
thanks
Youll have a wayyyy easier time just Odining a full NAE tar..
Daisflaque said:
Youll have a wayyyy easier time just Odining a full NAE tar..
Click to expand...
Click to collapse
okay...but my firmware and radio both say nae...whats a full nae tar gonna change?
That's the current version of the official ROM.
Sorry i meant MF9. Since your on MF9 bootloader than you should be able to flash the MF9 tar right? This way your at least back to a normally functioning firmware. Then just flash your favorite rom. I'm not sure about your specific situation. Its a little hectic. Lol but this would be my best guess and probably correct. Lol this way you'll at least have a funtioning device.. right?
Daisflaque said:
Sorry i meant MF9. Since your on MF9 bootloader than you should be able to flash the MF9 tar right? This way your at least back to a normally functioning firmware. Then just flash your favorite rom. I'm not sure about your specific situation. Its a little hectic. Lol but this would be my best guess and probably correct. Lol this way you'll at least have a funtioning device.. right?
Click to expand...
Click to collapse
true...so odin flash an mf9, like i was originally on, then find another rom thats working on mf9? suggestions? i loved sacs and negalite, but i believe ive got to be nae for those....
Im sure thats not a problem. NAE is simply the baseband/bootloader. This is not affected by rom.
TrickyD76 said:
true...so odin flash an mf9, like i was originally on, then find another rom thats working on mf9? suggestions? i loved sacs and negalite, but i believe ive got to be nae for those....
Click to expand...
Click to collapse
You could try and flash stick rooted nae ROM and if that works for you then dirty flash nega or sacs.
Related
Hello guys,
I installed the ROM under this post http://forum.xda-developers.com/showthread.php?t=2288531&page=13
The flashing of the ROM was successful but the only thing that it's not working with this flash is that I'm unable to turn on my wifi feature.
Is there a way to fix this without remodifying the ROM?
Any help will do. Thanks guys!!
tones160 said:
Hello guys,
I installed the ROM under this post http://forum.xda-developers.com/showthread.php?t=2288531&page=13
The flashing of the ROM was successful but the only thing that it's not working with this flash is that I'm unable to turn on my wifi feature.
Is there a way to fix this without remodifying the ROM?
Any help will do. Thanks guys!!
Click to expand...
Click to collapse
First just an FYI questions go in the QA section. This will be moved there by a Mod so just giving you a heads up. Were you on MDC or MDL before you flashed the rom?
crawrj said:
First just an FYI questions go in the QA section. This will be moved there by a Mod so just giving you a heads up. Were you on MDC or MDL before you flashed the rom?
Click to expand...
Click to collapse
My S4 was running on MDL already.
tones160 said:
My S4 was running on MDL already.
Click to expand...
Click to collapse
That's what I was thinking. That Rom is MDC based. So you have MDL Firmware but MDC System. If you want to stick with that rom here is what I would do. Make a backup. Odin the stock MDC tar twice, don't ask just better this way . Install custom recovery back on. Restore only the system. You should be fixed. Or you could probably get away with just installing the MDC Kernel. You can find the tar and kernel from here http://forum.xda-developers.com/showthread.php?t=2256514
Flash a custom kernel and your Wifi will work.
Sent from my SPH-L720 using Tapatalk 2
crawrj said:
That's what I was thinking. That Rom is MDC based. So you have MDL Firmware but MDC System. If you want to stick with that rom here is what I would do. Make a backup. Odin the stock MDC tar twice, don't ask just better this way . Install custom recovery back on. Restore only the system. You should be fixed. Or you could probably get away with just installing the MDC Kernel. You can find the tar and kernel from here http://forum.xda-developers.com/showthread.php?t=2256514
Click to expand...
Click to collapse
That's a great suggestion there crawjr. I will try the kernal suggestion first if anything. Even though i feel uncomfortable messing with the kernel system. Sorry for the noob questions I haven't been on this page for ages since the G2 was first released lol. :good:
ok i had the sprint gs4 but traded it for the htc one.. but i dont remember how i did it.. but he is still on MDL and he wants to be on MF9.. i rooted his phone months ago put twrp on it and flashed freegs4 rom.. i just went to his house to try and update it for him and i flashed the firmwear update in odin everything went great i looked in about phone and its still MDL?? so how do i update him to MF9 the rite way>? thanks
Grab the full Odin frimware tar and flash that. It'll bring it up to MF9 completely stock. Then use CF Autoroot to get root, install goomanager and install twrp or cwm.
http://forum.xda-developers.com/showpost.php?p=45574008&postcount=11
The baseband shows as MDL still?
Or the software version does? Or both?
If you're on an old version of freegs4, it's probably based off of a MDL build, and the software version would still show MDL.
Check the baseband.
TonyTurboII said:
The baseband shows as MDL still?
Or the software version does? Or both?
If you're on an old version of freegs4, it's probably based off of a MDL build, and the software version would still show MDL.
Check the baseband.
Click to expand...
Click to collapse
well sorry for got to say then i flashed the new sacs rom which is MF9 but it still said MDL.. everything still was MDL?? So he still MDL.. Just trying to get him on board with MF9
P.Mobile said:
well sorry for got to say then i flashed the new sacs rom which is MF9 but it still said MDL.. everything still was MDL?? So he still MDL.. Just trying to get him on board with MF9
Click to expand...
Click to collapse
Its better if you just flash him straight mf9 stock rather than just flash an mf9 rom. Could save him and you from any troubles. Like the one your encountering now.
P.Mobile said:
well sorry for got to say then i flashed the new sacs rom which is MF9 but it still said MDL.. everything still was MDL?? So he still MDL.. Just trying to get him on board with MF9
Click to expand...
Click to collapse
I think leader builder had the best solution then. A full reload of the MF9 firmware then reroot with chainfire.
Dam man can someone maybe help me.. Got the nite off of work and was going to fix my boys phone tonite but when I go to download that MF9 stock tar file it takes 2 hours to downoad Sucks!! does anyone have that file on hand that could send it to me..?? Please
I am trying to decide whether or not it is worth the effort to update to MJA without updating the bootloader per http://forum.xda-developers.com/showthread.php?t=2277480. I am now running 4.2.2 pretty much stock with root. I would like to run the same way on MJA, but don't want to have the wifi problem and would like the option of running stock kernel. I have not been able to find what is causing the wifi problem. Are people taking the OTA experiencing the wifi problem? If I were to install the update as described in the link above without the KT kernel, what is the difference between that and the OTA, other than the bootloader? Why would it experience the wifi problem and not the OTA?
From what I have read you should be fine. I am trying to make the same decision. I'm basically stock mf9 rooted and tweaked.
My understanding is that we could Odin the mja with root and be like we are currently with all the new goodness. The disadvantage, if it is one, is that we could not go back to a mf9 rom due to now having the mja bootloader. I am trying to wait for one of these amazing devs to get a tar or zip together that would be a one flash setup allowing us have all of the new stuff minus the mja bootloader. I don't think I would ever go backwards but I don't want to destroy that option. I probably won't be able to wait much longer and wind up jumping through all the hoops to get the mja modem, 4.3, and keep the mf9 bootloader.
I am in no way a developer and please someone correct me if I am mistaken. I hope this helps you in some way.
todivefor said:
I am trying to decide whether or not it is worth the effort to update to MJA without updating the bootloader per http://forum.xda-developers.com/showthread.php?t=2277480. I am now running 4.2.2 pretty much stock with root. I would like to run the same way on MJA, but don't want to have the wifi problem and would like the option of running stock kernel. I have not been able to find what is causing the wifi problem. Are people taking the OTA experiencing the wifi problem? If I were to install the update as described in the link above without the KT kernel, what is the difference between that and the OTA, other than the bootloader? Why would it experience the wifi problem and not the OTA?
Click to expand...
Click to collapse
I just did what you're thinking about doing and my experience has been great. I have the full MJA with out the bootloader. The phone runs stable and fast. No Wifi issues, LTE works, and clear phone calls.
It was more time-consuming than flashing a tar but I'm liking MJA a lot right now.
optimummind said:
I just did what you're thinking about doing and my experience has been great. I have the full MJA with out the bootloader. The phone runs stable and fast. No Wifi issues, LTE works, and clear phone calls.
It was more time-consuming than flashing a tar but I'm liking MJA a lot right now.
Click to expand...
Click to collapse
Are you running the stock kernel or KT kernel?
todivefor said:
Are you running the stock kernel or KT kernel?
Click to expand...
Click to collapse
The KT kernel with the wifi fix. I didn't mess with the KTweaker settings.
I'm currently running MDC rooted stock with stock kernal. if i update using the thread posted by the OP. Will i be using MJA or MF9 bootloader...i've read throught the instructions and don't see anything about flashing the MF9 bootloader, or would that be the step which removes Knox
alchemist.zim said:
I'm currently running MDC rooted stock with stock kernal. if i update using the thread posted by the OP. Will i be using MJA or MF9 bootloader...i've read throught the instructions and don't see anything about flashing the MF9 bootloader, or would that be the step which removes Knox
Click to expand...
Click to collapse
Before I started on the guide, I was on stock, rooted MF9. After the guide, I was MJA everything except the bootloader, which is MF9. As a result, Knox isn't triggered.
Since you're currently on MDC, perhaps you should start by flashing the OEM MF9 tar first through PC Odin.
optimummind said:
Before I started on the guide, I was on stock, rooted MF9. After the guide, I was MJA everything except the bootloader, which is MF9. As a result, Knox isn't triggered.
Since you're currently on MDC, perhaps you should start by flashing the OEM MF9 tar first through PC Odin.
Click to expand...
Click to collapse
damn...another slow 1GB+ download
Bear with me please. Upgraded to S4 from S3 that was running Task650 ROM.
I have searched and am a bit confused with the Locked, Loki Doki, MK2, etc. I have searched and cannot find info as far as what I can upgrade to without causing Locked Bootloader or other problems. I have read the FAQ's and they do not mention what to do if you are on MDB. Phone is 2 weeks old and all I have done to Root with Casual.
So what can I do with MDB without causing problems?
Thank you in advance!!!
You can do everything on mdb as you can on mdl. You can root and put a custom recovery on and use Odin. If it was me I'd use Odin to upgrade to mdl and then put cwm or twrp custom recovery on it. Then a custom Rom. You'll still need to use Loki.
jd1639 said:
You can do everything on mdb as you can on mdl. You can root and put a custom recovery on and use Odin. If it was me I'd use Odin to upgrade to mdl and then put cwm or twrp custom recovery on it. Then a custom Rom. You'll still need to use Loki.
Click to expand...
Click to collapse
Should have said. I do also have TWRP on it now.
What advantage to MDL is there?
o2man98 said:
Should have said. I do also have TWRP on it now.
What advantage to MDL is there?
Click to expand...
Click to collapse
Not much, it's just an update you can take without having to worry of locking the bootloader any tighter.
o2man98 said:
Should have said. I do also have TWRP on it now.
What advantage to MDL is there?
Click to expand...
Click to collapse
As jd said, you have freedom and you can take the MDL odin just fine. But never take any OTA's or use any other ODIN packages, and if you're running stock then freeze the OTA apps or it will force update. Other than that remember to use loki when you flash and you'll be fine.
Sent from Black<3's I337 running Hyperdrive
I thought I saw in some rom OPS a few months that devs were recommending to be on mdl before flashing their rom. Maybe when some 4.3s came out. But not sure.
I've been using the Negalite ROM 4.3 for a while and I like it a lot but recently my phone has been lagging hard for no reason and will reboot itself.
Does anyone know the cause and I was wondering to install 4.4 can I just system update it or flash the 4.4 ROM? Also is 4.4 worth it? I see people having battery problems. Give me some advice please
i7vSa7vi7y said:
I've been using the Negalite ROM 4.3 for a while and I like it a lot but recently my phone has been lagging hard for no reason and will reboot itself.
Does anyone know the cause and I was wondering to install 4.4 can I just system update it or flash the 4.4 ROM? Also is 4.4 worth it? I see people having battery problems. Give me some advice please
Click to expand...
Click to collapse
Go on the Negalite page and look at the last page i just posted my battery life and see if its something you may like. I'm on r6 and I'm sure an update will be coming out in the next few days. But i haven't updated my modem yet. And theres no hotspot as of rite now but soon!!!!!!!
How do you get NAE? I'm on MK2. I want to flash 4.4 tonight
Dont update the modem!!!!!!!! if you do, prepare yourself for better 4g signal but intence..i mean insane batt drain!!
Sent from my SPH-L720 using xda app-developers app
Negalite 4.4 had been running great for me, had it since the 20th so far. Battery is about the same I feel I had on cm11 before it.
What is the modem? Don't I just flash this like every other ROM?
http://forum.xda-developers.com/showthread.php?t=2521870
It is recommended that the modem/firmware be flashed via Odin prior to upgrading the rom.
Here us UF firmware thread with instructions/all firmware downloads.
http://forum.xda-developers.com/showthread.php?t=2338919
BTW, just got done upgrading from mf9 to nae (via mk2), keeping the mf9 bootloader.
Got lucky and dirty flashed all the way through. Now on Negalite r9 rom/r30 kernel.
All good except for the issue with lockscreen being greyed out.
ajmcedar said:
It is recommended that the modem/firmware be flashed via Odin prior to upgrading the rom.
Here us UF firmware thread with instructions/all firmware downloads.
http://forum.xda-developers.com/showthread.php?t=2338919
BTW, just got done upgrading from mf9 to nae (via mk2), keeping the mf9 bootloader.
Got lucky and dirty flashed all the way through. Now on Negalite r9 rom/r30 kernel.
All good except for the issue with lockscreen being greyed out.
Click to expand...
Click to collapse
Thank you. Now we are getting somewhere haha. How do I know which bootloader I have? I want 4.4 on a solid ROM with some performance tweaks. Why did chris say not to flash the modem/firmware? Is there a way to get 4.4 without doing that. I'm assuming I flash the NAE firmware before I install the ROM correct? Performance and battery life are my main priorities so if I should try a different ROM let me know. I don't leave my data on all day by the way so I don't think I should be affected too much. All help is appreciated
So let me get this process straight.
Flash the NAE firmware via Odin - http://forum.xda-developers.com/showthread.php?t=2338919
Then flash the ROM
Then the r30 kernal
correct??
Go here: http://forum.xda-developers.com/showthread.php?t=2663619
Follow the directions to ODIN the NAE tar **CAUTION** This includes the NAE bootloader and will cause Knox to trip as soon as you root it. Personally, I don't care; I'm only one year away from an upgrade if I want it.
ODIN the updated CF Autoroot.
ODIN Philz Recovery
Flash Negalite WondeROM NAE r6
Profit
I've flashed r10 (not released, but available on SVN) and it has a working WIFI tether. The only issue is that I had to flash KT instead of Nega's Kernel over it to stop a boot loop. Other than that it works great. This is my first day with r10, but no significant battery drain issues to report. My Negalite flash was a clean install.
---------- Post added at 12:29 PM ---------- Previous post was at 12:27 PM ----------
i7vSa7vi7y said:
So let me get this process straight.
Flash the NAE firmware via Odin - http://forum.xda-developers.com/showthread.php?t=2338919
Then flash the ROM
Then the r30 kernal
correct??
Click to expand...
Click to collapse
You need to ODIN CF Autoroot and Philz first before you can flash Negalite. You'll lose root with that tar
Easiest way to check your bootloader is to use one of the following apps.
Root Checker
Device Info
Nega's WondeROM has always been a stable performing ROM with great battery life.
Not sure why the hate for the NAE modem.
Also not sure about the mismatch between modem and ROM, I haven't seen many posts about it being anything bad.
Nega's NAE r10 (only available via SVN) already comes with the r30 kernel. I built the r9 after stuffing the services.odex from r7.
conradcbrown said:
Go here: http://forum.xda-developers.com/showthread.php?t=2663619
Follow the directions to ODIN the NAE tar **CAUTION** This includes the NAE bootloader and will cause Knox to trip as soon as you root it. Personally, I don't care; I'm only one year away from an upgrade if I want it.
ODIN the updated CF Autoroot.
ODIN Philz Recovery
Flash Negalite WondeROM NAE r6
Profit
I've flashed r10 (not released, but available on SVN) and it has a working WIFI tether. The only issue is that I had to flash KT instead of Nega's Kernel over it to stop a boot loop. Other than that it works great. This is my first day with r10, but no significant battery drain issues to report. My Negalite flash was a clean install.
---------- Post added at 12:29 PM ---------- Previous post was at 12:27 PM ----------
You need to ODIN CF Autoroot and Philz first before you can flash Negalite. You'll lose root with that tar
Click to expand...
Click to collapse
I already have Philz Recovery so Im good there. What is knox exactly. Is that just the words on the top left on startup that tells samsung your phone has been tampered with?
How did AJ manage to keep MF9 bootloader?
So Odin CF Autoroot.
Then I'm going to Stock NAE
NAE firmware then to the ROM and Kernal?
I need to flash the Stock NAE? I can't go from MK2 to NAE firmware then to ROM?
Thanks AJ. How would you recommend flashing this ROM from MK2 bootloader? I love my S4 and I just don't want to go through and bootloops or any other non sense. I'm just looking for another opinion. It looks like comrad gave me everything the safest way.
I had never taken any of the OTA updates since mf9, was still on the 4.2.2 no knox mf9 bootloader.
I kept MF9 bootloader (already rooted, Philz 6.08.9) by:
Odin the firmware for mk2 from UnknowForces thread, then rebooted to verify.
Went into Philz recovery, loaded Nega's mk5 r35 rom. Rebooted and let it settle.
Odin the firmware for nae, again from Unkown's thread, rebooted to verify firmware and baseband.
Philz recovery to load Nega's nae r6 rom. Rebooted, let it settle.
Nandroid backup using Philz with SE context checked (required since the 4.3 update) once I was sure all was good.
Setup SVN for any new commits from Nega.
Again, all this was doen via dirty flashing, YMMV.
i7vSa7vi7y said:
I already have Philz Recovery so Im good there. What is knox exactly. Is that just the words on the top left on startup that tells samsung your phone has been tampered with?
How did AJ manage to keep MF9 bootloader?
So Odin CF Autoroot.
Then I'm going to Stock NAE
NAE firmware then to the ROM and Kernal?
I need to flash the Stock NAE? I can't go from MK2 to NAE firmware then to ROM?
Click to expand...
Click to collapse
When/if you flash the tar, it'll flash the stock recovery as well, which is why you need to start over from scratch basically. The NAE tar from sammobile is the end-all be-all and includes the stock recovery, bootloader, modem, ROM, etc.
Yes, basically Knox just keeps track of how many times you've flashed a custom recovery and could void your warranty for software issues.
You can keep your bootloader if you decide to flash Negalite on top without pushing the tar over ODIN. I did that for a week or two with no significant issues, but did have a little lagginess in the phone (could have been subjective) and I couldn't resist seeing what the latest and greatest felt like. But no, I had no real issues flashing r6 over a MK2 bootloader and MF9 modem.
i7vSa7vi7y said:
Thanks AJ. How would you recommend flashing this ROM from MK2 bootloader? I love my S4 and I just don't want to go through and bootloops or any other non sense. I'm just looking for another opinion. It looks like comrad gave me everything the safest way.
Click to expand...
Click to collapse
Just Odin the nae modem from Unknown's firmware thread, then Philz recovery to flash Nega's nae rom/kernel, I believe that the only downloadable zip is his r6. Newer versions requires SVN to download the latest commits, then his scripts to create the flashable zips.
Ok. Thank you guys once again. Should I factory reset, wipe delvik and cache before all of this?
i7vSa7vi7y said:
Ok. Thank you guys once again. Should I factory reset, wipe delvik and cache before all of this?
Click to expand...
Click to collapse
I only did dalvik and cache. Others recommend full wipe/factory reset, but I like to live on the edge and wanted to keep my setup.
Originally I did the full wipe/factory reset/clean for an new rom, (after I did a nandroid of my current setup). all my apps/personalization got wiped.
I restored my previous nandroid and proceeded going forward with dirty flashes. It worked for me, but YMMV, each device/situation is different.
Good luck.
"I like to live on the edge" lmao!
I'm just going to start from scratch sense some app or something is destroying my RAM and pising me off. That's what made me want to update in the first place. That and I like the new features. Well anyways thank you guys for the help. I appreciate it a lot. I love this community. I'll report back how it goes.