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.
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: (ETA: Unknown)
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.
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.)
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 be able to boot your KitKat backup.
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.
Performance:
Currently the performance difference between KitKat and Lollipop is unknown. If the first release of Lollipop for Android One 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 Android One 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.
This is taken from the Moto G thread and all credits goes to @lost101.The sole motive of this is to create awareness about the new bootloader included in 5.0
Thanks For The Info @DC07 :highfive:
Thanks For The Information Bruda !!
This thing is only for device like motorola, samsung etc.. As I never saw same thing for nexus.. Motorola does not allow to downgrade so they update bootloader in every android version update.. I dont think it will be same for sprout
Let it arrive ,no point in discussions on thongs that are not confirmed
Sent from my A1 using XDA Free mobile app
coolkoushik07 said:
This thing is only for device like motorola, samsung etc.. As I never saw same thing for nexus.. Motorola does not allow to downgrade so they update bootloader in every android version update.. I dont think it will be same for sprout
Click to expand...
Click to collapse
Nope. The bootloader was updated on my nexus 7 flo for the 4.4.2 OTA. Since this update is much bigger I think we'll have a bootloader update too.
littleromeo said:
Nope. The bootloader was updated on my nexus 7 flo for the 4.4.2 OTA. Since this update is much bigger I think we'll have a bootloader update too.
Click to expand...
Click to collapse
Does it stop u from downgrading to any previous version?
Sent from my Xperia Z1 Compact
yes..
coolkoushik07 said:
Does it stop u from downgrading to any previous version?
Sent from my Xperia Z1 Compact
Click to expand...
Click to collapse
yes... once u update boot loader , you can never even think of downgrading ..
experience :/
startracker said:
Is varun working with lollipop
Sent from my A1 using XDA Free mobile app
Click to expand...
Click to collapse
Yes,according to the ss posted in the fb group.But this doesn't mean everyone starts spamming his pm.
Let him take his time.This will make our lollipops taste more sweet
doubts about lollipop arise
Just wanted to let everyone know today is the day official lollipop support is available on Exposed.
http://forum.xda-developers.com/xposed/official-xposed-lollipop-t3030118
Nice, having exposed is a must!
Known issues:
- It seems to boot loop on Samsung stock ROMs.
Yeah... Stay away from this until it's tested to work with the new L update.
As with previous versions of Xposed, it may take a wee while more to be fully compatible with Samsung stock ROMs, but the good news is that at least it is now working on Lollipop.
Hi!
I have a Samsung Galaxy S4 (GT-I9505) running android 4.4.2.
It's rooted and with CWM.
Is there a way to put xposed on it without updating the android version?
I really really really would want to keep 4.4.2 and not change android version.
By looking around I have seen that samsung phones with stock roms sometimes have trouble with xposed. Is that true for android 5.0 and newer versions only? Or for 4.4.2 as well?
I am scared of making a test "just to see how it goes" because it's the only phone I got, even if I have backup from Cwm and all ...
Thanks in advance.
U will not have issues or any need to update your Android version
Xposed for kitkat is 2.6.1 and 2.7 build
Happy installing
Scorpionea said:
U will not have issues or any need to update your Android version
Xposed for kitkat is 2.6.1 and 2.7 build
Happy installing
Click to expand...
Click to collapse
Thanks a lot dude
Which version of the Xposed framework would I use for kitkat 4.1?
Are all of the latest versions backwards compatible?
Thanks...Randy
RC54 said:
Which version of the Xposed framework would I use for kitkat 4.1?
Are all of the latest versions backwards compatible?
Thanks...Randy
Click to expand...
Click to collapse
You could either use the one from the Xposed repo or - if the official didn't work - use the one from this thread that fixes compatibility issues with latest security fixes on Android KitKat.
The newer versions for Lollipop/Marshmallow won't work on KitKat.
I have a Samsung Galaxy S3 running 4.2.2 and the latest update that I have and can get is v54. I see there's v86 out for Android 5.0+, is there a newer update for older Androids?
Most likely not as xposed is but against the current aosp code. So with each new release the older android versions are abandoned.
zelendel said:
Most likely not as xposed is but against the current aosp code. So with each new release the older android versions are abandoned.
Click to expand...
Click to collapse
Darn. So it looks like my old ass phone won't work for a module that I run.
Thanks.