I just got a S4, and am currently running rooted stock, and already have a nandroid created. I want to try out some different ROMS...I've noticed that there are some issues with MF9 and MJA.
1. Does anyone know if TriangleAway works with MF9 and MJA?
2. How hard would it be to go back to my rooted stock if something goes wrong
3. Is it any harder to unroot after upgrading?
Triangle away does work with MF9, make sure you are on the stock recovery to use it. MF9 is the most stable of the builds. MJA is great for me but some have had problems. If you do the upgrade to MJA and the bootloader is upgraded to the MJA bootloader than you will not be able to downgrade your bootloader. People have successfully installed 4.2.2 roms and AOSP roms once upgraded to MJA which is 4.3 but you have to make sure you know what you are doing before you screw around with it. Since there is not a full tar file for MJA if you soft brick your phone there isn't an easy odin fix to get back up. It is a much more complicated procedure so be careful.
cruise350 said:
Triangle away does work with MF9, make sure you are on the stock recovery to use it. MF9 is the most stable of the builds. MJA is great for me but some have had problems. If you do the upgrade to MJA and the bootloader is upgraded to the MJA bootloader than you will not be able to downgrade your bootloader. People have successfully installed 4.2.2 roms and AOSP roms once upgraded to MJA which is 4.3 but you have to make sure you know what you are doing before you screw around with it. Since there is not a full tar file for MJA if you soft brick your phone there isn't an easy odin fix to get back up. It is a much more complicated procedure so be careful.
Click to expand...
Click to collapse
Thanks cruise...so I take it any 4.3 ROMS that are out are using the MJA (Knox) bootloader?
Related
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
is there one floating around?
i looked but didnt see one
Most Roms are MJA or MK2 now as devs always stay on top of the latest updates. Download stock rooted MF9 and debloat it yourself. I can't remember which ROM might still be on MF9,
Sent from my SPH-L720 using Tapatalk
daniel4653 said:
Most Roms are MJA or MK2 now as devs always stay on top of the latest updates. Download stock rooted MF9 and debloat it yourself. I can't remember which ROM might still be on MF9,
Sent from my SPH-L720 using Tapatalk
Click to expand...
Click to collapse
i have done the domestic lock so i thought it was good to stay on mf9 with mdc modem. thought about flashing modem back to mf9 as the modem will still stay unlocked but if i goto mja or mk2 i think i loose the unlock carrier mod and plus how do you all deal with knox?
figured most people would still want to stay on a firmware you could downgrade when you want and flash what you want without to much trouble
you think i should stay on mf9 considering my needs or is mja and mk2 ok to upgrade to now?
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 have a L720 running the MK2 4.3 Stock(ish) and the PhilZ Touch ver 6. I want to remove all of these and reinstall the stock MK2 in advance of the new kitkat release. How do I remove all of these before reloading the stock MK2?
[email protected] said:
I have a L720 running the MK2 4.3 Stock(ish) and the PhilZ Touch ver 6. I want to remove all of these and reinstall the stock MK2 in advance of the new kitkat release. How do I remove all of these before reloading the stock MK2?
Click to expand...
Click to collapse
Flash the stock MK2 file found here: http://forum.xda-developers.com/showthread.php?t=2601443 and your phone will be back to stock unrooted and ready for the OTA. Your data will still be in tact.
I'm hoping this is the right thread.
I'm fairly new to the S4 coming from an S2. I did root MK2 using SafeRoot method. I should not have tripped Knox or anything like that. I unrooted with SuperSU unroot option. Everything looks OK except the Device Status shows Custom. I haven't gotten the OTA yet, but when it comes in, is it safe to try, or am I going to have problems?
Thanks,
Dennis_H
Dennis_H2 said:
I'm hoping this is the right thread.
I'm fairly new to the S4 coming from an S2. I did root MK2 using SafeRoot method. I should not have tripped Knox or anything like that. I unrooted with SuperSU unroot option. Everything looks OK except the Device Status shows Custom. I haven't gotten the OTA yet, but when it comes in, is it safe to try, or am I going to have problems?
Thanks,
Dennis_H
Click to expand...
Click to collapse
It all depends if you modded or disabled anything in the system partition. Including the hotspot mod. If you have, the ota will fail and you need to Odin the stock mk2 tar.
Sent from my icrap 2 using Tapatalk HD
cruise350 said:
It all depends if you modded or disabled anything in the system partition. Including the hotspot mod. If you have, the ota will fail and you need to Odin the stock mk2 tar.
Sent from my icrap 2 using Tapatalk HD
Click to expand...
Click to collapse
As far as I know, nothing in the system partition got changed with saferoot, and I never got around to installing any new recoveries or adding the hotspot mod. The hotspot mod was the real reason i rooted, but got a little concerned/confused after reading about it.If the custom in device status doesn't cause issues, I'll wait to get the OTA and then start reading about the HS mod again to see how to implement in 4.4.2 without tripping knox if possible.
Thanks for the info.
Dennis_H
Looking to unroot and want to know when did they introduce the knox bootloader. Basically I want to downgrade and let my phone upgrade back to nae with ota's. I'm currently nae modem sac's 4.4 rom..
MJA I think. Once you take OTAs to NAE you will have Knox.
Sent from my SPH-L720 using Tapatalk
Why take the ota when you can just install the full nae tar and be updated in one quick and easy step.