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.
Related
I have read through the forums and found some helpful posts, but want to be clear so any concise help on this would be great. I am on stock MDL, rooted, with stock recovery. The only mod I have done is the hotspot hack. What is the easiest way to update to MF9 and not lose any of my apps, settings, data etc? Is this even possible. Can I do the update while rooted without losing anything?
legasus233 said:
I have read through the forums and found some helpful posts, but want to be clear so any concise help on this would be great. I am on stock MDL, rooted, with stock recovery. The only mod I have done is the hotspot hack. What is the easiest way to update to MF9 and not lose any of my apps, settings, data etc? Is this even possible. Can I do the update while rooted without losing anything?
Click to expand...
Click to collapse
Yes, you should be able with a version that doesn't wipe your data...check out:
http://forum.xda-developers.com/showthread.php?t=2357471
and here's a couple for reference
http://forum.xda-developers.com/showthread.php?t=2356431
http://forum.xda-developers.com/showthread.php?t=2277480
I don't know why, but this **** confuses the hell out of me. Normally I understand this stuff, but apparently the MDL to MF9 transition is rocket science for me.
I seem to not be able to find a straight forward and easy answer on how I should get myself on MF9.. one guide says JUST FLASH IT, and then another guide says "will not work with custom recovery."
I don't get it... and it's not worth potentially bricking my phone.
I'm running a custom MDL rom with TWRP. Some people say I have to remove TWRP before I can do anything. Why?! And why does Odin have to be used? Why not just wipe everything with TWRP and flash a custom MF9 rom that's already rooted and has the MF9 modem and kernel?
Maybe it's just the medicine I'm on right now, but this is so confusing.
If I'm on the Sprint MDL ROM + root/twrp, which version should I use (odex or dedodex, no wipe) to upgrade? I'm hoping to not lose any data or have to set up my phone again. Thanks.
Cytality said:
I don't know why, but this **** confuses the hell out of me. Normally I understand this stuff, but apparently the MDL to MF9 transition is rocket science for me.
I seem to not be able to find a straight forward and easy answer on how I should get myself on MF9.. one guide says JUST FLASH IT, and then another guide says "will not work with custom recovery."
I don't get it... and it's not worth potentially bricking my phone.
I'm running a custom MDL rom with TWRP. Some people say I have to remove TWRP before I can do anything. Why?! And why does Odin have to be used? Why not just wipe everything with TWRP and flash a custom MF9 rom that's already rooted and has the MF9 modem and kernel?
Maybe it's just the medicine I'm on right now, but this is so confusing.
Click to expand...
Click to collapse
Dude, I'm totally with you - I did the 1-touch and am on MDL with TWRP and shabbypenguin kernel (which was part of the 1-touch). I dont want to brick my phone and theres like 7 different ways people are saying on how to do this...wtf
What exactly are you guys trying to update to mf9? The baseband? If that's the case just download and flash.
Sent from my Sprint Galaxy S4 using Tapatalk 4 Beta
---------- Post added at 10:27 AM ---------- Previous post was at 10:24 AM ----------
Check out this thread, it's really not too difficult http://forum.xda-developers.com/showthread.php?t=2357471 you can either wipe your days or not, it's up to you. I always wipe personally.
Sent from my Sprint Galaxy S4 using Tapatalk 4 Beta
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 stayed on 4.2.2 rooted with TWRP and never took the MJA/MK2 OTAs, to avoid knox. I've been waiting for KitKat, and I'm ready to take the plunge. I've read through a bunch of threads, and have thoroughly confused myself. I have a few basic questions, so I can determine what my options are:
1) Is it possible to go from MF9 (rooted) to NAE, and retain my data? What happens to the modifications I made to MF9 (hotspot, xposed, etc.)?
2) If the answer to 1 is no, is it reasonable to assume that there will be a flashable NAE rom in the near future, so that I wouldn't have to odin to MK2 before going through the OTA update to NAE?
3) Should I give up on trying to keep my existing bootloader, and just suck it up and take knox? It seems like there's probably enough differences in the rom and modem that the bootloader is probably a necessary evil at this point.
Thanks in advance for your help.
There have been several reports of people whose WiFi and data have worked just fine with the NAE ROM plus older bootloader like MF9. I'd wait until a stock rooted NAE ROM appears so we can try it with the knox-free MF9 bootloader.
Sent from my Nexus 5 using Tapatalk
I am in the same situation and currently on a stock rooted MF9 with a custom recovery as well. I would like to know the best upgrade path to 4.4.2 and hopefully stay on a knox free boot loader.
Sent from my GT-N5110 using Tapatalk 4
Once Warboy releases the updated stock, rooted NAE, I'm gonna flash it with Philz recovery to see whether everything's compatible with the Knox-free MF9 bootloader. In the meanwhile, I'm gonna flash just the NAE modem. Cant wait for Kitkat~! (Even though I've had the 4.4.2 update for a long time through my Nexus 5, I'm still very excited, LOL~)
Sent from my Nexus 5 using Tapatalk
Im still on mdl lol.....maybe I should atleast update to mf9? Haha
Sent from my SPH-L720 using xda app-developers app
cfendrick said:
I am in the same situation and currently on a stock rooted MF9 with a custom recovery as well. I would like to know the best upgrade path to 4.4.2 and hopefully stay on a knox free boot loader.
Sent from my GT-N5110 using Tapatalk 4
Click to expand...
Click to collapse
I'm in same boat
on MF9 , didnt even go to 4.3, still sitting at 4.2.2 (with the update icon in my status bar, but i assume its for 4.3 not kit kat)
Im rooted and have exposed installed
would rather have a knox free loader too!
if anybody can advise on the best route to take would be lovely
would like to have kit kat on my phone today!!
I was on this boat but last night flashed the gummy Rom. It is okay but I would love to have the stock Rom. I don't like few things on the Gummy.
icuc said:
I was on this boat but last night flashed the gummy Rom. It is okay but I would love to have the stock Rom. I don't like few things on the Gummy.
Click to expand...
Click to collapse
so you had MF9 bootloader? (and do you keep that one or switch to the knox one?)
just flashed rom with TRWP? (that'll update radio too?)
and what things dont you like on Gummy?
sandman121383 said:
Im still on mdl lol.....maybe I should atleast update to mf9? Haha
Sent from my SPH-L720 using xda app-developers app
Click to expand...
Click to collapse
Lol I've been wondering if anyone else stayed on 4.2.2. Lol Im rooted with custom recovery. I hit the update button the other night and it wouldn't install and that icon went away, so I got that going for me. But I can't wait for kit kat, just waiting on the whole knox deal.
Sent from my SPH-L720 using xda premium
SayWhat10 said:
so you had MF9 bootloader? (and do you keep that one or switch to the knox one?)
just flashed rom with TRWP? (that'll update radio too?)
and what things dont you like on Gummy?
Click to expand...
Click to collapse
Yeah I have MF9 and I could keep the same.
I had issues with BT connection with my BMW but works fine with BT headset.
Home screen kind of wacky and you can't select the one that you like.
I just went back to 4.2.2 again until I find a good one.
Yikes
I'm in the same situation, living on my phone with MF9, have TWRP/Custom Recovery installed, and am interested to upgrade to Kitkat. I'm very interested to know what will be the upgrade method for me to 4.4.2, similar to many others in this thread.
I'm on slimkat now and all is working great. Only drawback is no theme chooser
---------- Post added at 07:48 PM ---------- Previous post was at 07:48 PM ----------
I just simply flashed the KitKat rom with twrp
SayWhat10 said:
I'm on slimkat now and all is working great. Only drawback is no theme chooser
---------- Post added at 07:48 PM ---------- Previous post was at 07:48 PM ----------
I just simply flashed the KitKat rom with twrp
Click to expand...
Click to collapse
Which KitKat rom did you use? Did it just upgrade your OS or did you have to start from a clean install? Any issues with Knox?
asuh said:
Which KitKat rom did you use? Did it just upgrade your OS or did you have to start from a clean install? Any issues with Knox?
Click to expand...
Click to collapse
i used Slimkat, but it froze occasionally. now im on CM 11 and its FLAWLESS
did clean install (but had some apps backed up with Titanium)
to my knowledge the whole Knox thing is with Touchwiz based roms
both slimkat and CM 11 are not,so no worries about Knox
I am still on MF9 modem and bootloader
gonna get around to flashing the NAE modem later though
SayWhat10 said:
i used Slimkat, but it froze occasionally. now im on CM 11 and its FLAWLESS
did clean install (but had some apps backed up with Titanium)
to my knowledge the whole Knox thing is with Touchwiz based roms
both slimkat and CM 11 are not,so no worries about Knox
I am still on MF9 modem and bootloader
gonna get around to flashing the NAE modem later though
Click to expand...
Click to collapse
Alright. I'm personally looking to update only to official rom and NAE modem, not custom rom. Hoping I can do upgrade instead of clean install but hoping to get root access back or keep it at least.
Ok so i dont think i care about the knox thing anymore.. So with that said i would like to upgrade to 4.4.2 with the stock sprint rom. What is the best way to go about that? Sorry im just confused with the bootloader and modem flashes.. Its been awhile since ive had a samsung phone.. Im assuming i cant do the OTA due to TWRP....
I am running completely stock and rooted with saferoot,
4.2.2
baseband mf9
bootloader mf9
TWRP installed
please help
Can you just unroot and install the NAE ota then reroot with cf auto root? This is coming from stock rooted mk2.
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.