Database Users

WARNING: Android 5.0 Bootloader and KitKat Compatibility

Android 5.0 (Lollipop) Bootloader and KitKat Compatibility​
Everyone wants Lollipop, however it is worth considering some of the possible consequences of upgrading via OTA update.​
Flashable zip of Android 5.0.2 'Soak Test' now available and boots with KitKat Bootloader: http://forum.xda-developers.com/moto-g/development/rom-retail-brazil-lollipop-soak-test-t2998793
Downgrading to KitKat also possible even with Lollipop Bootloader.
Bootloader:
A new Bootloader (BL) will almost certainly be is included in the OTA update. It is also very likely no KitKat Kernel, stock or custom will be able to boot properly with the 5.0 BL. Perhaps the Kernel DEVs can find a workaround.
Root: (DONE)
It may take some time to gain root access on Lollipop as on other devices this has required a custom Kernel. A custom kernel itself may require kernel sources to be released - something that has taken weeks / months in the past.
Chainfire releases Android 5.0 Root for Moto G (2013) (All Models)
In addition; apps that use root access in KitKat, require further development to have functional root access in Lollipop.
Xposed Framework:
Developer has said he will wait for CyanogenMod based on Lollipop before properly starting development of an ART version of Xposed. CM12 may take a few weeks to release. Expect to do without Xposed for at least a month, probably longer since root is also required (see above.) Related: Alternatives to popular Xposed Modules
Custom Recovery:
This has not been an issue before, but it is always possible a new Bootloader could break compatibility with existing Custom Recoveries. Obviously, you would not be able to restore a CWM / TWRP backup without a functional custom recovery; but even then, it is unlikely you will [not] be able to boot your KitKat backup. CWM unaffected, TWRP not fully supported yet.
Custom ROMs:
This is another area that could be affected by a new Bootloader. It is unknown if existing custom ROMs will require new Kernels / system changes in order to work with the new BL - something that could take days, weeks or months. CyanogenMod 12 (Lollipop) for Moto G (Falcon) now available and does not appear to require a new BL.
Performance:
Currently the performance difference between KitKat and Lollipop is unknown. If the first release of Lollipop for Moto G has performance issues, you may be unable to revert back to stock KitKat.​Possible solution:
Wait for a flashable zip [NOT OTA Update zip] of Stock Moto G Lollipop ROM - this would mean your Bootloader remains at it's current version and potentially allowing you to change 'back and forth' between Stock KitKat and Stock Lollipop. However, it is currently unknown if the newer BL is a requirement for Android 5.0 Kernels. Flashable zip of Android 5.0.2 'Soak Test' now available and boots with KitKat Bootloader.

That is what I thought, since something like that happened because of the upgrade from JB to KK. Taking all of this into account, I'm not sure to upgrade immediately when the OTA comes out, maybe I'll try to still alive waiting for reviews from someone who dares to OTA right then.

You can be pretty sure it'll bring a bootloader update too because of all the fundamental changes lollipop brings in almost all areas of the OS. Major relase, as was gingerbread -> ICS.
It's pretty safe to say that once you upgrade, it won't be easy to downgrade, if at all possible... Many changes are in the security area and everything is getting tightened up a lot... Loads of tempting things we'll get in this upgrade, yes, but we'll have to give up much of what we're used to (in terms of rooting/etc), at least for a little while. I'll also wait until the dust settles a bit and it's clearer on where we stand with the upgrade once it gets released.

nice info

lost101 said:
Android 5.0 Bootloader and KitKat Compatibility​
Everyone wants Lollipop, however it is worth considering some of the possible consequences of upgrading via OTA update.
Bootloader:
A new Bootloader (BL) will almost certainly be included in the OTA update. It is also very likely no KitKat Kernel, stock or custom will be able to boot properly with the 5.0 BL. Perhaps the kernel DEVs can find a workaround.
Root:
It may take some time to gain root access on Lolipop as on other devices this has required a custom Kernel. A custom kernel itself may require kernel sources to be released - something that has taken weeks / months in the past.
Custom Recovery:
This has not been an issue before, but it is always possible a new Bootloader could break compatibility with existing Custom Recoveries.
Performance:
Currently the performance difference between KitKat and Lollipop is unknown. If the first release of Lollipop has performance issues on Moto G, you may be unable to revert back to stock KitKat.
Alternative solution:
Wait for a flashable zip of Stock Moto G Lollipop ROM - this would mean your Bootloader remains at it's current version and potentially allowing you to change between Stock KitKat and Stock Lollipop. However, it is currently unknown if the newer BL is a requirement for Android 5.0 Kernels.
Click to expand...
Click to collapse
UUUUUUHHHHHHHH iam afraight. a little. who needs bootloaders. i dont.

juanchotazo99 said:
You can be pretty sure it'll bring a bootloader update too because of all the fundamental changes lollipop brings in almost all areas of the OS. Major relase, as was gingerbread -> ICS.
It's pretty safe to say that once you upgrade, it won't be easy to downgrade, if at all possible... Many changes are in the security area and everything is getting tightened up a lot... Loads of tempting things we'll get in this upgrade, yes, but we'll have to give up much of what we're used to (in terms of rooting/etc), at least for a little while. I'll also wait until the dust settles a bit and it's clearer on where we stand with the upgrade once it gets released.
Click to expand...
Click to collapse
Will you be able to wait when you see that little notification saying there's a new system update awaiting you?? I'll eat my nails until then!

Can i still get the OTA update even though my bootloader is unlocked and rooted? (Kitkat 4.4.4.)

Drift0r said:
Can i still get the OTA update even though my bootloader is unlocked and rooted? (Kitkat 4.4.4.)
Click to expand...
Click to collapse
I don't think so....

Drift0r said:
Can i still get the OTA update even though my bootloader is unlocked and rooted? (Kitkat 4.4.4.)
Click to expand...
Click to collapse
Bootloader doesn't matter. Root doesn't matter. What does matter is the software on your phone that checks for OTA updates. As long as that is functioning; you will get the notification.
You can ignore the update notification and will not be forced to install it.

Drift0r said:
Can i still get the OTA update even though my bootloader is unlocked and rooted? (Kitkat 4.4.4.)
Click to expand...
Click to collapse
The only real thing you need to install the OTA is stock recovery, doesnt matter bootloader or root, only stock recovery to install the OTA! :good:

As always, very informative thread @lost101.

lost101 said:
Bootloader doesn't matter. Root doesn't matter. What does matter is the software on your phone that checks for OTA updates. As long as that is functioning; you will get the notification.
You can ignore the update notification and will not be forced to install it.
Click to expand...
Click to collapse
MarckozZ said:
The only real thing you need to install the OTA is stock recovery, doesnt matter bootloader or root, only stock recovery to install the OTA! :good:
Click to expand...
Click to collapse
How do I know what recovery I am on? I entered recovery and it is like this http://i.gyazo.com/1c3fa4923e85db7042ad6e36b97a31cc.png then when I click recovery on that screen I am on CWM, does that mean I can't or can do it?
Also I am not using any roms or anything, just rooted it for Xposed.

Drift0r said:
How do I know what recovery I am on? I entered recovery and it is like this http://i.gyazo.com/1c3fa4923e85db7042ad6e36b97a31cc.png then when I click recovery on that screen I am on CWM, does that mean I can't or can do it?
Also I am not using any roms or anything, just rooted it for Xposed.
Click to expand...
Click to collapse
You need stock recovery and rid of xposedand any modules

MarckozZ said:
The only real thing you need to install the OTA is stock recovery, doesnt matter bootloader or root, only stock recovery to install the OTA! :good:
Click to expand...
Click to collapse
And another real thing is pure/stock system. Which means no system apps were deleted or frizzed no mods were installed through custom recovery no custom kernels no luckyputcher stuff. And I think you have to delete xposed framework (manually via xposed installer).
And a lot of users think that it's enough just to flash back stock recovery and install ota. But then they are just wondering why is it can not install. So, untouched system block is mandatory for applying ota as well as stock recovery.
Root, unlocked bootloader and custom boot logo are things you could keep.

Is stock recovery and stock firmware same? If not how do i get stock recovery back?

S0bes said:
And another real thing is pure/stock system. Which means no system apps were deleted or frizzed no mods were installed through custom recovery no custom kernels no luckyputcher stuff. And I think you have to delete xposed framework (manually via xposed installer).
And a lot of users think that it's enough just to flash back stock recovery and install ota. But then they are just wondering why is it can not install. So, untouched system block is mandatory for applying ota as well as stock recovery.
Root, unlocked bootloader and custom boot logo are things you could keep.
Click to expand...
Click to collapse
How about if you are using Adaway?
I know this will change something to the file hosts.
Do you need to get this original hosts file as well?

Drift0r said:
How do I know what recovery I am on? I entered recovery and it is like this http://i.gyazo.com/1c3fa4923e85db7042ad6e36b97a31cc.png then when I click recovery on that screen I am on CWM, does that mean I can't or can do it?
Also I am not using any roms or anything, just rooted it for Xposed.
Click to expand...
Click to collapse
I'd reccomend to you this: when the OTA comes up, restore stock 4.4.2 firmware, then OTA to 4.4.4 and then to 5.0... Or if you find a 4.4.4 firmware just flash it and then OTA to 5.0... But the best you could do is to install the Lollipop OTA in a fresh new installed system.
S0bes said:
And another real thing is pure/stock system. Which means no system apps were deleted or frizzed no mods were installed through custom recovery no custom kernels no luckyputcher stuff. And I think you have to delete xposed framework (manually via xposed installer).
And a lot of users think that it's enough just to flash back stock recovery and install ota. But then they are just wondering why is it can not install. So, untouched system block is mandatory for applying ota as well as stock recovery.
Root, unlocked bootloader and custom boot logo are things you could keep.
Click to expand...
Click to collapse
Yes, maybe the best thing is to backup everything and restore all things to stock... then OTA to Lollipop... :good:

MarckozZ said:
I'd reccomend to you this: when the OTA comes up, restore stock 4.4.2 firmware, then OTA to 4.4.4 and then to 5.0... Or if you find a 4.4.4 firmware just flash it and then OTA to 5.0... But the best you could do is to install the Lollipop OTA in a fresh new installed system.
Yes, maybe the best thing is to backup everything and restore all things to stock... then OTA to Lollipop... :good:
Click to expand...
Click to collapse
Almost always it is enough to flash only system img files without erasing userdara. It should rewrite system block so it becames stock

MarckozZ said:
I'd reccomend to you this: when the OTA comes up, restore stock 4.4.2 firmware, then OTA to 4.4.4 and then to 5.0... Or if you find a 4.4.4 firmware just flash it and then OTA to 5.0... But the best you could do is to install the Lollipop OTA in a fresh new installed system.
Yes, maybe the best thing is to backup everything and restore all things to stock... then OTA to Lollipop... :good:
Click to expand...
Click to collapse
How do I restore it to 4.4.3? Im currently downloading this file to flash via mfastboot RET-EU-SS_4.4.3_KXB21.14-L1.31_cid7_CFC_1FF.xml.zip from this guide. http://forum.xda-developers.com/showthread.php?t=2542219 would this work?
my phone moto g 4g lte - xt1039

Drift0r said:
How do I restore it to 4.4.3? Im currently downloading this file to flash via mfastboot RET-EU-SS_4.4.3_KXB21.14-L1.31_cid7_CFC_1FF.xml.zip from this guide. http://forum.xda-developers.com/showthread.php?t=2542219 would this work?
my phone moto g 4g lte - xt1039
Click to expand...
Click to collapse
You can try the guide I've done with some help from other users here at XDA...
http://forum.xda-developers.com/moto-g/general/guide-restore-moto-firmware-gpe-t2914884

[newbie] galaxy s4 att UCUAMDL

hi all , sorry but my english is so bad
i just bought a galaxy s4 att secondhand , this had bassband UCUAMDL . and i checked the lastest version of it is 4.2.2
can i upgrade my phone up to 4.4 ?
and i dont know terminology about "MF3 - MK2 ............."
could you tell me ?
thanks so much :victory::victory::victory:

Root. Install TWRP recovery. Flash a rom 4.4.4 or try some lollipop love!! You are lucky enough to have an unlocked bootloader..

HORiZUN said:
Root. Install TWRP recovery. Flash a rom 4.4.4 or try some lollipop love!! You are lucky enough to have an unlocked bootloader..
Click to expand...
Click to collapse
thanks so much ,
can you get me links :crying:
but MF3 - MK2 ............. what is it ?
when i flash rom , what i have to notice ?

I hope you don't have MF3. If that's the case, I'm pretty sure that SafeStrap is your only recovery option.

HORiZUN said:
I hope you don't have MF3. If that's the case, I'm pretty sure that SafeStrap is your only recovery option.
Click to expand...
Click to collapse
but i dont know MF3 >"<
what is it ?
how check it on my phone ?

HORiZUN said:
I hope you don't have MF3. If that's the case, I'm pretty sure that SafeStrap is your only recovery option.
Click to expand...
Click to collapse
i am in 4.2.2

sonluyen94 said:
but i dont know MF3 >"<
what is it ?
how check it on my phone ?
Click to expand...
Click to collapse
I have the same question. hopefully someone will be able to explain it to us.

MF3 would be the last three digits of your system software version

HORiZUN said:
MF3 would be the last three digits of your system software version
Click to expand...
Click to collapse
my baseband : I337UCUAMDL
kernel version : 3.4.0-453947 - [email protected] #1
android version : 4.2.2
build number : JDQ39.I337UCUAMDL
it is my phone >"<

You don't have MF3, and that's a good thing. You can install a custom recovery. You need to root, install a custom recovery, and then you can start flashing roms.

sonluyen94 said:
my baseband : I337UCUAMDL
kernel version : 3.4.0-453947 - [email protected] #1
android version : 4.2.2
build number : JDQ39.I337UCUAMDL
it is my phone >"<
Click to expand...
Click to collapse
nogods said:
I have the same question. hopefully someone will be able to explain it to us.
Click to expand...
Click to collapse
Ok, use TowelRoot.com to root the phone, and use TWRP manager to install TWRP on your device. After that check out the development section of this very forum and flash any ROM you wish. 4.2.2 or 4.4.4 or 5.0 or anywhere in between (Just read the thread and instructions first!!!). Whatever you do, never update using the OTA updater on the stock ROM! Also, dotn ever flash an image in Odin that isn't MDL, because if you go higher than MDL, you lose the ability to have a custom recovery. You are one of the lucky ones, cherish the ability, and read through threads before flashing, stuff. Good Luck!
Also, you don't have to worry if the ROM says safestrap compatible, because you don't have to use Safestrap, you can have TWRP instead (which is better), because all Safestrap ROMS are TWRP compatible, but not vice-versa.

npjohnson said:
Ok, use TowelRoot.com to root the phone, and use TWRP manager to install TWRP on your device. After that check out the development section of this very forum and flash any ROM you wish. 4.2.2 or 4.4.4 or 5.0 or anywhere in between (Just read the thread and instructions first!!!). Whatever you do, never update using the OTA updater on the stock ROM! Also, dotn ever flash an image in Odin that isn't MDL, because if you go higher than MDL, you lose the ability to have a custom recovery. You are one of the lucky ones, cherish the ability, and read through threads before flashing, stuff. Good Luck!
Also, you don't have to worry if the ROM says safestrap compatible, because you don't have to use Safestrap, you can have TWRP instead (which is better), because all Safestrap ROMS are TWRP compatible, but not vice-versa.
Click to expand...
Click to collapse
thanks so much :fingers-crossed:
but can you talk to me what rom is good about battery ?

sonluyen94 said:
thanks so much :fingers-crossed:
but can you talk to me what rom is good about battery ?
Click to expand...
Click to collapse
Most if not all. They're all built from either GPE or CM.

All good advice. Plus when you root and get Twrp recovery installed do a backup thru Twrp (Nandroid) and keep on phone and put a copy on pc. That way you have something to restore if you get in trouble. Also, your bootloader is not unlocked. No Att i337s are. Instead devs use an exploit called Loki-Doki to bypass Sammy's security checks to allow custom roms/kernels etc to flash. You can google Loki Doki and read up on it. If the rom or kernel is not loki'd you will have to flash the zip thru recovery to allow the rom or kernel to flash. You will come across this when flashing International roms and kernels. I don't have link any more so maybe someone else can link it. Keep it on SD card. Like noted read OP carefully and last 20 pages of rom thread. Builds newer than MDL are blocked by Att from using Loki and require SafeStrap. Which you don't need to worry about. Although you can read up on it. Good Luck. [emoji1]
Sent from my iPhone 6 Plus using Tapatalk

I hope you won't mind me jumping in your thread.,
I've recently had to odin my mdl phone back to stock. I haven't done that in a long time. I have root, and supersu, and busybox. The TWRP Manager app is malfunctioning and I cannot use it to install recovery. They list the crash I am experiencing in the play store as a known problem, and they say it will take time to fix. I have a good loki'd copy of twrp but the stock recovery doesn't want to install it. I even changed the name to "update.zip" and it fails. So my problem is I need a recovery. I am considering installing Clockworkmod's ROM Manager to install their recovery, and then using their recovery to install the good loki'd twrp that I want. Does this sound like a good plan? I have been away from this hobby for a while.

plasticglock said:
I hope you won't mind me jumping in your thread.,
I've recently had to odin my mdl phone back to stock. I haven't done that in a long time. I have root, and supersu, and busybox. The TWRP Manager app is malfunctioning and I cannot use it to install recovery. They list the crash I am experiencing in the play store as a known problem, and they say it will take time to fix. I have a good loki'd copy of twrp but the stock recovery doesn't want to install it. I even changed the name to "update.zip" and it fails. So my problem is I need a recovery. I am considering installing Clockworkmod's ROM Manager to install their recovery, and then using their recovery to install the good loki'd twrp that I want. Does this sound like a good plan? I have been away from this hobby for a while.
Click to expand...
Click to collapse
You can flash a recovery zip in a custom recovery. So if you have the loki'd twrp in a zip file, flashing cwm first will work
Sent from my Nexus 9 using XDA Free mobile app

jd1639 said:
You can flash a recovery zip in a custom recovery. So if you have the loki'd twrp in a zip file, flashing cwm first will work
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks man, that's exactly what I was planning. I remember avoiding CWM last year due to some issue on this device so I just wanted to make sure it wasn't going to do more harm than good. :good:

plasticglock said:
Thanks man, that's exactly what I was planning. I remember avoiding CWM last year due to some issue on this device so I just wanted to make sure it wasn't going to do more harm than good. :good:
Click to expand...
Click to collapse
ROM manager didn't work. It said it installed cwm recovery but it didn't. I was able to install the latest TWRP with this ROM Installer and it worked like a charm! I then installed my custom TWRP from there, rebooted recovery, and installed Danvh's Google edition. I'm setting it up right now. I'm so happy to get my phone back. I just hope the odin flash fixed my problems.
To the OP try ROM installer to get your custom recovery going. Also if you like simple and fast AOSP check out Danvh's google edition rom, but stick to 4.4.4 for now. 5.0 is out but its buggy. Here's a link to the custom version of twrp that I use. https://www.dropbox.com/l/iDQQqlzNbyiFbQrMF4XcRc It's already loki'd so you can flash it if you have any problems with the latest build.

Change to custom Rom - Help needed

Hi Friends
I have Samsung -SGH-I337 (AT&T) i already rooted it by KingRoot.
Baseband: I337UGUGOC3
KNOX: 2.3
I need to install Cynogenmod or similar rom, bcoz stock samsung rom drains battery like anything and have lot of Bloatware from AT&T
So friend let me know how to install recovery like Clockworks and then custom rom suitable got I337

vazeer said:
Hi Friends
I have Samsung -SGH-I337 (AT&T) i already rooted it by KingRoot.
Baseband: I337UGUGOC3
KNOX: 2.3
I need to install Cynogenmod or similar rom, bcoz stock samsung rom drains battery like anything and have lot of Bloatware from AT&T
So friend let me know how to install recovery like Clockworks and then custom rom suitable got I337
Click to expand...
Click to collapse
Your baseband is OC3 so you have OC3 modem. What is your bootloader?
If you bootloader is newer than MDB or MDL you can not install the custom recovery like CWM or TWRP. You are limited to Safestrap or Flashfire for flashing the custom rom.

sway8966 said:
Your baseband is OC3 so you have OC3 modem. What is your bootloader?
If you bootloader is newer than MDB or MDL you can not install the custom recovery like CWM or TWRP. You are limited to Safestrap or Flashfire for flashing the custom rom.
Click to expand...
Click to collapse
Hi,
My Bootloader is "I337UGUGOC3" is same as my baseband.
So what im suppose to do now ?

vazeer said:
Hi,
My Bootloader is "I337UGUGOC3" is same as my baseband.
So what im suppose to do now ?
Click to expand...
Click to collapse
You have a locked bootloader so you option to install the custom rom is limited to using either safestrap or flashfire.
This guide explain how to install custom using safestrap.
This guide explain updating, rooting and using safestrap. It is also useful if you screwed up and bricked your phone while flashing or tweaking.
Flashfire is newer thing and there is no separate guide written for how to use it but you can find the flashfire instructions in the custom rom that is written as flashfire friendly.

sway8966 said:
You have a locked bootloader so you option to install the custom rom is limited to using either safestrap or flashfire.
This guide explain how to install custom using safestrap.
This guide explain updating, rooting and using safestrap. It is also useful if you screwed up and bricked your phone while flashing or tweaking.
Flashfire is newer thing and there is no separate guide written for how to use it but you can find the flashfire instructions in the custom rom that is written as flashfire friendly.
Click to expand...
Click to collapse
I already went on that post but its very confusing to me, as i have OC3 bootloader, rooted with Kingroot what next, should i use Odin if yes that in put AP slot, and someplace it says OC3 to NJ4 what is that.
Can u plz tell me how to get safestrap installed (as i have rooted already) and then latest rom (that has working mobile data tethering )

vazeer said:
I already went on that post but its very confusing to me, as i have OC3 bootloader, rooted with Kingroot what next, should i use Odin if yes that in put AP slot, and someplace it says OC3 to NJ4 what is that.
Can u plz tell me how to get safestrap installed (as i have rooted already) and then latest rom (that has working mobile data tethering )
Click to expand...
Click to collapse
My first reference explains all the steps starting from the Kitkat NB1.
Since you'd already have OC3 and rooted you need to follow the step #4 Install your CUSTOM Lollipop ROM . step 4.1 explains how to install safestrap. 4.2 explains how to invoke safestrap and 4.3 explains how to install the custom rom.
I did not see OC3 to NJ4 that you were referring to though.
This thread is for installing S6 port using either safestrap or flashfire. I am just showing you as an example how to install the custom rom.

vazeer said:
Hi Friends
I have Samsung -SGH-I337 (AT&T) i already rooted it by KingRoot.
Baseband: I337UGUGOC3
KNOX: 2.3
I need to install Cynogenmod or similar rom, bcoz stock samsung rom drains battery like anything and have lot of Bloatware from AT&T
So friend let me know how to install recovery like Clockworks and then custom rom suitable got I337
Click to expand...
Click to collapse
I recommend you to do all process from NB1 to OC4/OK2 keep root (Avaliable on the INDEX) bcuz I was lazy and used kingroot to root OC4 and when I finally was into safestrap it doesn't flashed any ROM and was just a waste of time.

David_RD said:
I recommend you to do all process from NB1 to OC4/OK2 keep root (Avaliable on the INDEX) bcuz I was lazy and used kingroot to root OC4 and when I finally was into safestrap it doesn't flashed any ROM and was just a waste of time.
Click to expand...
Click to collapse
Thanks a lot guys, still my confusion is what to put in AP slot in Odin as my bootloader is OC3 and after that how to install safestrap
As David u have OC4 can u please guide me through ?

vazeer said:
Thanks a lot guys, still my confusion is what to put in AP slot in Odin as my bootloader is OC3 and after that how to install safestrap
As David u have OC4 can u please guide me through ?
Click to expand...
Click to collapse
I'm not the most indicated to show you the way because I haven't tried the keep root method yet, S4 it's my personal phone, was finishing semester and needed to be contactable.
I'm gonna try it right now and if I have success I will let u know in a couple hours?
I'm now on Albe95 LolliROM v8 ? and I'm pretty noob on this. I'll tell you step by step tomorrow cause now I'm tired ??

So did everything is working perfectly, what steps u went through ?

vazeer said:
So did everything is working perfectly, what steps u went through ?
Click to expand...
Click to collapse
Proceed at your own risk. I'm not responsible for any damage caused to your device
First we must put all the archives we will need on the SD card (Stock rooted OC4, the Custom ROM we want, OC4 modules, OC4 kernel and all we gonna need)
Make sure to read this complete, understand it and then proceed
1. I used Odin to flash back to NB1 (the rootable one)
2. Rooted with TowelRoot and installed SuperSU and FlashFire directly from PlayStore (worked for me).
3. Opened Flashfire, granted root permissions and did the Muniz_ri Keep Root Method (4.4.x to OK2) but instead of using OK2 replaced all OK2's with OC4 files because I couldn't find the OK2 modules and will be needed to flash custom ROM.
4. At this point we have OC4 rooted so we just install BusyBox (install the 'things'), then install Safestrap and inside the app install the recovery and at last install the NC1 app flasher.
5. We will automatically reboot into Safestrap recovery and there we just have to wipe (all except SD card) then we proceed to install the ROM (if the ROM has aroma installer at the end we don't reboot into system we have to go back to recovery), after modules and at last we flash (install) the Kernel (we re using OC4 base so modules and Kernel must be OC4 too).
6. From here we just have to wait, and the Safestrap robot will appear like 4 times, we just press continue and deodexed custom ROMs will take about 15-20 minutes to do the first boot.
All archives can be found here on the different threads== > http://forum.xda-developers.com/showthread.php?t=2616221 <== Remember to thank all those posts and their respective devs :good:

5.0.1 OC4 to OctOS 6.0.1 ?

i have rooted OC4 installed on my phone and have i've been reading up on OCTos and their 6.0.1 custom firmware (found a good link too: http://www.teamandroid.com/2016/01/20/update-att-galaxy-s4-i337-android-601-octos-marshmallow-custom-rom/ ) . and now am more confused.
it should be simple from what i am reading.
1) backup everything
2) revert to 4.3 (mk2), root, and install ClockworkMod 10.2+
3) install custom rom 6.0.1 OCTos
however, i'm reading on this page (http://forum.xda-developers.com/galaxy-s4-att/general/guide-odin-to-stock-updating-rooting-t2926642) but it states >> Once you flash NB1, you CANNOT go back to MK2. <<
So now I'm trying to figure out exactly how i can get the OCTos onto my phone. what guide should i follow !?!?!?!
:silly:

They meant the MK2 boot loader based devices, same with MDL. Aside from a few exploited boot loaders.. it's been the general consensus that they're all locked up, therefore.. only stock roms. The lowest boot loader you can possibly be on is NB1. Download "Terminal Emulator" for the Play Store and then when you open it up, type the following:
getprop ro.bootloader
^ exactly like that, then see what it says. The last three characters (MDK, MDL, MK2, NB1, NC1, OC3, OC4)--that's how you can figure out which boot loader you are using. I am on NB1's bootloader but I can still downgrade to MK2, i.e. Android 4.3, and still have it work.. only because of how the roms in these threads are rooted and the fact that they're stock, aside from a few other small details. When they say OC3 or MK2, or NB1... whichever.. then typically they mean the boot loader when saying you cannot revert. Definitely cannot revert to MK2 bootloader after taking an OTA update.

pr3dicament said:
getprop ro.bootloader
Click to expand...
Click to collapse
i337ucugoc4

egiblock said:
i have rooted OC4 installed on my phone and have i've been reading up on OCTos and their 6.0.1 custom firmware (found a good link too: http://www.teamandroid.com/2016/01/20/update-att-galaxy-s4-i337-android-601-octos-marshmallow-custom-rom/ ) . and now am more confused.
it should be simple from what i am reading.
1) backup everything
2) revert to 4.3 (mk2), root, and install ClockworkMod 10.2+
3) install custom rom 6.0.1 OCTos
however, i'm reading on this page (http://forum.xda-developers.com/galaxy-s4-att/general/guide-odin-to-stock-updating-rooting-t2926642) but it states >> Once you flash NB1, you CANNOT go back to MK2. <<
So now I'm trying to figure out exactly how i can get the OCTos onto my phone. what guide should i follow !?!?!?!
:silly:
Click to expand...
Click to collapse
Even though it was not mentioned, the article appears to be written for the SGH-i337 with old bootloaders (MDB, MDL). These are the only two bootloaders that can be exploited and installed the custom recovery like CWM or TWRP.
Since your bootloader is OC4 you can not install the CWM or TWRP. You could try flashing with safestrap though. If that custom rom is not written with Aroma then you could also try to flash with flashfire. These are the only two options for you.

egiblock said:
i337ucugoc4
Click to expand...
Click to collapse
Okay, yeah.. you're not on MDK or MDL, not even NB1.. you're simply on OC4. You aren't going to be able to do any flashing of any Custom Roms that are not Safestrap compatible (touchwiz)
Good luck.. you can't go anywhere backwards, not even OC3. That really sucks. I'm sorry. It looks like you took the OTA's.
I can still ODIN to NB1 and that was because I never took the OTA update. I got lucky.. I can still choose between kitkat and lollipop. You can't. You might be able to with someone's help.. but your bootloader is OC4.. that's a problem. You more than likely will have trouble doing anything unless it's not MDK/MDL or even NB1 based.
---------- Post added at 08:23 PM ---------- Previous post was at 08:21 PM ----------
sway8966 said:
Even though it was not mentioned, the article appears to be written for the SGH-i337 with old bootloaders (MDB, MDL). These are the only two bootloaders that can be exploited and installed the custom recovery like CWM or TWRP.
Since your bootloader is OC4 you can not install the CWM or TWRP. You could try flashing with safestrap though. If that custom rom is not written with Aroma then you could also try to flash with flashfire. These are the only two options for you.
Click to expand...
Click to collapse
Yeah.. You might have a shot with FlashFire. I might test that via the NB1 bootloader that I'm on but I don't think it matters that much aside from being able to Odin back to 4.3 software.

sway8966 said:
Even though it was not mentioned, the article appears to be written for the SGH-i337 with old bootloaders (MDB, MDL). These are the only two bootloaders that can be exploited and installed the custom recovery like CWM or TWRP.
Since your bootloader is OC4 you can not install the CWM or TWRP. You could try flashing with safestrap though. If that custom rom is not written with Aroma then you could also try to flash with flashfire. These are the only two options for you.
Click to expand...
Click to collapse
FlashFire came out with another release (0.32) that seems to have an AROMA emulation option.. my guess is that it's still in testing, but it's worth a shot even without it. The way I have OC3 with the NB1 boot loader is because of FlashFire.. Safestrap.. it's been awhile since I've used it. I've tried recently for other ROMS but you can't do a custom kernel.. that's the reason most custom roms aren't able to work, i.e. CM v13 runs a totally different kernel. It's not just TouchWiz now.. now it's just stock kernels.. at least via SafeStrap. So far I've gotten none to work with SafeStrap aside from Stock rooted roms. OC3, OC4, and if I felt like it, OK2.. but why even bother with OK2, I'm not gonna see any difference given all of the patches you can use with Xposed.. including any memory leak bull****, that's all good now in 5.0.x -- 5.1+ has that patched up.. and OK2 certainly isn't 5.1. I don't see any difference between OC3 and OC4.. and if my opinion counts for anything.. the one thing that I noticed (bloatware script ran and other apps not needed were frozen for both) is a very high amount of battery usage with OC4.. same userdata, same everything.. and when you flash the kernel, the modules, and move up to OC4.. it's still the same looking.. feels the same.. more ram used.. OC3 is superior in this instance. I'd love to try and give an AOSP rom a shot.. but.. via SafeStrap (someone made a guide for those not on the MDK or MDL boot loaders) .. eh.. no luck. That was all via SafeStrap. I'm just putting in my two cents. I think development for this phone is finished.. no one has come out with anything new aside from the SafeStrap kernel workarounds.. not many FlashFire users.. and the one that used to find every single exploit is now EMPLOYED by Samsung so his development.. gone. That was a huge kick in the ass to this entire community. Plenty of people around, just.. they don't give a **** about the S4 with boot loader all locked up. NB1 was an accident for me.. I was on MDL for a long, long time.. I really ****ed that up or I'd be running MarshMallow already It seems to run best with KitKat, but a lot of AOSP roms have shown huge differences in MarshMallow.. oh well. Can't try it at the moment.

Unfortunately I can't remember what I did in the past to this phone, but I have never had luck with OTA updates. I'll have to see if I can find my note to see what I originally did on this stupid thing.

egiblock said:
Unfortunately I can't remember what I did in the past to this phone, but I have never had luck with OTA updates. I'll have to see if I can find my note to see what I originally did on this stupid thing.
Click to expand...
Click to collapse
Since you are on OC4, the lowest you can go is NB1 (kit-kat).

note 3 still on 4.3 towelroot - now need to flash custom recovery but uncertain

After rooting my Note 3 (not branded or simlocked) many moons ago with Towelroot, I've come to the point of wanting to update things a tad. I never installed a custom recovery so it's just a root.
However, looking through the multiple threads here and not wishing to make a bad mistake I'm a little confused and could do with some clear pointers.
I am currently on 4.3 Jellybean BL: N900XXUBMJ3 so most threads deal with later versions and I really want to know what the best path is to now being able to start trying out custom roms such as the DarkWolf ROM or just get this to Lollipop. Obviously now Knox 1x0 is no longer a problem as it's out of warranty.
I assume that the step should really be to install a custom recovery and for that there is a confusion of whether I can do that directly on my current bootloader or do I have install 4.4.2 as some threads suggest?
Probably due to my misunderstanding I am not sure if a 4.4 bootloader is separate from the firmware. If it comes to having to update the bootloader do I have to completely upgrade to Kitkat or can I just update the bootloader only?

louiscar said:
After rooting my Note 3 (not branded or simlocked) many moons ago with Towelroot, I've come to the point of wanting to update things a tad. I never installed a custom recovery so it's just a root.
However, looking through the multiple threads here and not wishing to make a bad mistake I'm a little confused and could do with some clear pointers.
I am currently on 4.3 Jellybean BL: N900XXUBMJ3 so most threads deal with later versions and I really want to know what the best path is to now being able to start trying out custom roms such as the DarkWolf ROM or just get this to Lollipop. Obviously now Knox 1x0 is no longer a problem as it's out of warranty.
I assume that the step should really be to install a custom recovery and for that there is a confusion of whether I can do that directly on my current bootloader or do I have install 4.4.2 as some threads suggest?
Probably due to my misunderstanding I am not sure if a 4.4 bootloader is separate from the firmware. If it comes to having to update the bootloader do I have to completely upgrade to Kitkat or can I just update the bootloader only?
Click to expand...
Click to collapse
You can flash custom recovery for 4.3 but all 5.1.1 and 6.0 roms require 5.0 bootloader to make the camera to work correctly.
Flash 4.3 custom recovery. Then flash the rom of your choice. Then flash 5.0 bootloader. After that flash 4.4.2/5.0 recovery.
Or flash 5.0 firmware. Flash 4.4.2/5.0 custom recovery. Flash the rom of your choice.
Sent from my SM-G925F using XDA Free mobile app

Rosli59564 said:
You can flash custom recovery for 4.3 but all 5.1.1 and 6.0 roms require 5.0 bootloader to make the camera to work correctly.
Flash 4.3 custom recovery. Then flash the rom of your choice. Then flash 5.0 bootloader. After that flash 4.4.2/5.0 recovery.
Or flash 5.0 firmware. Flash 4.4.2/5.0 custom recovery. Flash the rom of your choice.
Sent from my SM-G925F using XDA Free mobile app
Click to expand...
Click to collapse
Thanks for that Rosli,
I actually found that OTA was working still so I let it update. This went through a lot of updates one by one till it got to the latest 4.3. All this left root intact. Then it downloaded the kitkat but that failed. I had figured that if I let it update to Lollipop I could then root it with CF Autoroot but as it's not going any further (probably due to the fact that I'm rooted .. maybe), I will have to manually update via Odin.
I would probably in that case prefer your advice of flashing 5.0 directly then custom recovery, however, do I have to CF autoroot or can I flash recovery without root and then root after that?

louiscar said:
Thanks for that Rosli,
I actually found that OTA was working still so I let it update. This went through a lot of updates one by one till it got to the latest 4.3. All this left root intact. Then it downloaded the kitkat but that failed. I had figured that if I let it update to Lollipop I could then root it with CF Autoroot but as it's not going any further (probably due to the fact that I'm rooted .. maybe), I will have to manually update via Odin.
I would probably in that case prefer your advice of flashing 5.0 directly then custom recovery, however, do I have to CF autoroot or can I flash recovery without root and then root after that?
Click to expand...
Click to collapse
Can flash custom recovery then root. But if you're going to flash custom rom no need to root after custom recovery.
Sent from my SM-G925F