yashsingh1/xdaforums huggingface dataset:
[G 2014 General] Seriously Ponies?:
Received the 5.02 OTA today on my XT1063 (US). installed fine. I was rooted, but unrooted using SuperSU (strangely, "full unroot" hung, but "unroot for installing a different SU app" worked just fine). I was using stock recovery, and the OTA installed perfectly fine.

Bonus: forgot to revert to original hosts from adaway before installing the OTA. Still worked! So now, I don't have root, but am ad-free!!

So looks like (for now) "Lolipop OTAs require an untouched /system" is a bit of an exaggeration. Hooray!

(haven't re-rooted yet).
[G 2014 General] Android The Greek:
I am really impressed with Motorola. I know there have been some hiccups with different variants of the same phone but wow already on 5.0.2
[G 2014 General] draztikrhymez:
Downloading now
[G 2014 General] devsk:
They haven't moved to the block level deltas for the /system partition as yet. They are still patching file to file. So, as long as the files being patched are not touched by you, you are ok.
[G 2014 General] Traediras:
From here:

This could potentially mean Moto G users as a whole may be getting Lollipop by the end of the month, if all goes well. :D
[G 2014 General] zman01:
In EU we didn't received even 5.0 for our dual-sim models, not even a soak test.
[G 2014 General] Seriously Ponies?:
Have Google given any indication when they'll be moving to the new patching system?
[G 2014 General] devsk:
They probably already have. Some people claimed they got OTA in the partition block diff format for Nexus series phones. May be motorola is keeping the current method alive on its own. After all, its just packaging and OEMs choose the packaging.
[G 2014 General] Seriously Ponies?:
Hopefully Moto keeps using the old patching system as they haven't been particularly forthcoming with providing factory images for the Moto G 2014.
[G 2014 General] devsk:
It honestly doesn't make much of a difference. Keep a bare stock backup always handy, with pretty much empty /data partition. So, basically the update procedure is (and would continue to be):

0. Capture the OTA zip from /cache.

1. Take a full TWRP back up of the current ROM, with your changes etc.

2. Restore to previous bare stock ROM including the stock recovery.

3. Sideload the OTA zip and make sure to boot at least once (and skip account setup if this is the first OTA ever).

4. Flash TWRP recovery partition

5. Take a TWRP backup of new bare stock ROM for use for the next OTA.

6. Restore your /data.

7. Install SuperSU.zip, and optionally busybox.

8. Profit!

This means all your changes to the /system partition are lost. But you should not be making changes to /system partition anyway (apart from the SuperSU and busybox).

Note that you can not afford to miss an OTA...:) The above procedure breaks. So, keep up with OTAs.
[G 2014 General] LoneStarPhD:
I got a bad bootloop after rooting. I've read that eventually it will boot up. Are you having any issues? Do you have an XT1064?
[G 2014 General] devsk:
SuperSU 2.44 should work fine on XT1064. It should not lead to any bootloops.
[G 2014 General] LoneStarPhD:
Thanks! Latest version of TWRP okay?
[G 2014 General] qudsbeat:
must unlocked boot loader used to get an OTA update lolliop ?

my device XT1063
[G 2014 General] Android The Greek:
No not if you had you phone on 21.11.17. If you are on 21.11.23 there is no update that I know of for XT1063.
[Huawei Ascend P7] ibeqa:
Hello people,

These are the latest updated apk's of Huawei preinstalled apps on our devices. I got them when I installed Huawei App Store, so whoever is interested can get them. Just remember that you need Huawei ID (so you can log-in) also.

1. Media app

2. File manager app (cloud included)

3. Huawei ID

Enjoy
[Huawei Ascend P7] ibeqa:
Due to size upload limitation, I had to put these last two apk's here:

1. Backup app and

2. Hi Space (Huawei app store)

Cheers
[Huawei Ascend P7] ArnoJeroen:
I have a HuaweiID, I registred that at their website.

But when I want to use the Cloud etc, I get a error-message that "this service is not available in your region".

How can I solve this?
[Huawei Ascend P7] ibeqa:
With P7, I don't have that kind of problem, but when I used those updates on my G700 apps, I started getting that error!
[Huawei Ascend P7] moviehunter2009:
Same problem here...P7 L00
[Huawei Ascend P7] ibeqa:
I checked again and all Huawei apps work fine on my P7.

My G700 is a different story. App Center, Music and Cloud Sync works (meaning I can log in), on File manager and Backup I can't log in (service not available in your region).

This is strange, why some apps will let me log in and some no?
[Motorola Droid Bionic] Oggie7797:
I ported OctOs using the CM12 device tree by [MENTION=3457922]stargo[/MENTION] to targa and have since ported it for our OMAP4 brothers.

Features: (will be added onto)

-CM based so expect those features

-Tentacles settings for more personalization

-SuperSu as primary su binary handler

-Omniswitch

-CM12 Theme Engine

-Fast.

-Snappy.

-Clean.

-Amazing.

Downloads:

The ROM is on my Gdrive.

I recommend PA Gapps.

Install:

Flash on a new ROM slot on the new SELINUX enabled SafeStrap by [MENTION=3457922]stargo[/MENTION]

Updates:

Since Lollipop is in early development, I suggest doing a clean install. If you wanna wipe system and caches only that's fine too but don't report bugs.

Bugs:

-LTE has a hard time sticking but my latest build *should* patch that. If you have issues (especially after reboot) go into settings and switch preferred network from 3g to 4g a couple times and/or toggle airplane mode. Hopefully this will be completely fixed in the near future, but it isn't as annoying as the orange data indicator on KitKat.

-Same bugs as CM12

If you encounter bugs please make sure that you clean install on a virgin ROM slot and include a step-by-step on how to repeat the bug and also include a syslog (get the apk from play).

Hope you enjoy the ROM :)

XDA:DevDB Information

Oct-L, ROM for the Motorola Droid Bionic

Contributors

Oggie7797

ROM OS Version: 5.0.x Lollipop

ROM Kernel: Linux 3.0.x

ROM Firmware Required: New SafeStrap by Stargo

Based On: Cyanogenmod12

Version Information

Status: Beta

Beta Release Date: 2015-01-11

Created 2015-01-12

Last Updated 2015-01-12
[Motorola Droid Bionic] rfresh:
Thanks for your great effort, and I am on Recurr ROM, LTE data connection is very stable and no need to set APN

Could you please tell what is the difference between this ROM and Recurr one?
[Motorola Droid Bionic] Oggie7797:
Different features and stuff lol IMA build again tonight if I have time and maybe it'll fix lte for good
[Motorola Droid Bionic] The Doctor04:
installing now
[Motorola Droid Bionic] Oggie7797:
[MENTION=1975745]Grommish[/MENTION] is helping with the APN issue. to bypass the phone fc on boot do the voice dialer trick same as CM12
[Motorola Droid Bionic] The Doctor04:
So I have the latest and greatest GApps running, but I cannot get into the ROM. I keep getting a FC for Google Play Services. Push ok and it takes you back to WiFi. Rebooted, reinstalled GApps, cleared cache, etc. Still no dice. I don't have too much to monkey around with it today, will try a new build once uploaded
[Motorola Droid Bionic] Oggie7797:
What Gapps? I didn't have this issue on PA Gapps...try setting up without gapps first and flash gapps on a diff session. You're using as a wifi only device right? If so use the radio disable build.prop tweak. On initial boot turn airplane mode on to stop phone fc and add the build.prop line and reboot and flash gapps. that'll fix phone and most other issues if running as a wifi only ROM.
[Motorola Droid Bionic] The Doctor04:
I tried both the slimmed down PA GApps, and I also tried DHacker's GApps from 12/21/14. I cannot get past the FC from Google Play Services. Will maybe give it the old college try later this evening. I am not seeing any issues really with CM12 based roms using them as a WiFi device, so I haven't felt the need to do all the things you are suggesting. If I have some time tonight, I will give it a go
[Motorola Droid Bionic] Oggie7797:
Try flashing on a brand new virgin slot lol idk why but sometimes that fixes stuff
[Motorola Droid Bionic] The Doctor04:
No luck, even after a fresh install in slot 2. I flashed [MENTION=3457922]stargo[/MENTION] latest build just a short time ago and zero Play Services FC. Very weird
[Motorola Droid Bionic] Oggie7797:
I'm making progress with getting LTE stable. Expect another build late Sunday/Monday.
[Motorola Droid Bionic] rfresh:
Thanks and really appreciated!
[Motorola Droid Bionic] Oggie7797:
[MENTION=2199371]rfresh[/MENTION] mind sending me build.prop from RR? Or copy/paste it into a pastebin and send me the link..I don't feel like downloading an entire ROM and I need to compare some settings I've made. Thanks.

Edit:

Sync'd up and started another build with the phone patch in it. I'll check back in a few hours or in the morning to check build progress, with CM12 TE being merged along with lots of new code, there's always a possibility for a fail. Will build maserati and/or spyder tomorrow.
[Motorola Droid Bionic] Oggie7797:
Uploading a new build+md5 using new commits from Octos and [MENTION=3457922]stargo[/MENTION] this build should be flashed on a NEW rom slot to avoid any bugs! This build also uses my phone fc patch. Oh and also has new theme chooser ;)
[Motorola Droid Bionic] antennaman1969:
Getting Better

Flashed first build, got API problems.

Flashed latest build, API is solid, but having Google Play fc with nano, pico, and normal gapps. Same with CM12. Flashed onto clean slot each time. SS 3.75. Also flashed ROM first, then rebooted and flashed gapps.

I remain optomistic.
[Motorola Droid Bionic] Oggie7797:
Sorry man it's a chromium issue and it's being worked on! For now if you flash the first one and change the line ro.telephony.default_network=10 to a 6 in build.prop it will fix api issue but after each reboot you will have to toggle 4g as preferred network under settings...that's what I done and I'm using it as a daily. Again, sorry bout the issue and it is being worked on. Thanks for the report.
[Motorola Droid Bionic] antennaman1969:
Cool. Thanks for the reply. I will get some sleep and reflash after breakfast. It looks great; might keep the Bionic relevant until I find my "can't miss" new phone!

Update:

Reflashed in Slot 3. Used pico, nano, mini, and full. All fc on Google Play Services. Radios are solid. Exact opposite of CM 12- I get com.android.phone fc and wifi network is forgotten at random. If I had a clue on how to code, I could figure out how to combine the working parts and make one good Lollipop for Targa!

Will try a different slot. Can I try a different .apk for Play Services?

If so, I can push it to the SD card and flash from there.
[Motorola Droid Bionic] antennaman1969:
To elaborate on my idea:

If I flash the ROM first, it goes wonderfully. That's why I was thinking about just flashing the .apk's and building from there. If the Play Services, then Play Store work, then maybe onward and upward?

Some guidance on what to sideload first would be appreciated.

To Google I go!
[Motorola Droid Bionic] Oggie7797:
I've already pulled a log bud it's a chromium issue and its not our device it's a Lollipop issue and I think Grommish made a fix and I'm going to try it out and build tonight after I make clobber. Do what I suggested about the first build inside build.prop. I use it as a daily.

It's nothing you can do about it it has to be done on my end while I build.
[Xperia Z2 General] AbdwGTK:
Hey Everyone :D

i have Sony Z2 D6502 Bulid num end 167

i need a root for it

i tried many ones by nothing worked

and i didn't find anything alike on the fourms

pls help :\ i need the root access ASP!
[Xperia Z2 General] o0 Matt 0o:
That's either

1. A lie

2. You didn't search

3. Your searching another forum

To root your phone (as said many many times in the z2 section)

1. Downgrade to 4.4.2 to root

2. Unlock your bootloader
[Xperia Z2 General] Pandemic:
Unlock the bootloader is not needed for root, thats also a lie then, i have root on locked bl with 4.4.4 ^^

Sent From Somewhere On Earth With My Z2 ^^
[Xperia Z2 General] core_x:
There is no root for it!

To have root on 4.4.4 follow these steps:

Downgrade to 4.4.2 and root your phone:

http://xdaforums.com/showthread.php?t=2759934

Create a rooted update package:

http://xdaforums.com/xperia-z2/general/4-4-4-creating-rooted-update-package-t2933155
[Xperia Z2 General] AbdwGTK:
a LIE ????

why would i lie for -_-

i searched the fourms and there is NO Z2 4.4.4 ROOT -___-
[Xperia Z2 General] o0 Matt 0o:
They're options. I may not have made that clear.

If you have 4.4.4 and want root you have two options. You either downgrade or unlock bootloader.

My point is there are a lot of threads with people saying how do I root 4.4.4 and everytime the response is the same.

Choose one of the options below:
[Xperia Z2 General] AbdwGTK:
so the only way is to downgrade

do you advice me to do so ? :\ ??
[Xperia Z2 General] Pandemic:
If you want to keep the DRM Keys then yes because when you unlock your bootloader then you will lose those keys ;)

Sent From Somewhere On Earth With My Z2 ^^
[Xperia Z2 General] Ambor:
YES

so because today is the realized

Installing 4.4.2 do root

and installing

stock-4-4-4-23-0-1-0-167-bug-free
[Xperia Z2 General] Isley_:
Maybe is my headache but to root we can simply Flash Recovery in fastboot and then SuperSU in recovery? Or why not? Thanks
[Xperia Z2 General] Moscow Desire:
Just a notice to some folks,

1) take a look at the "root" threads, and yes, there are several pertaining to trying to get root on 4.4.4.

2) Don't call people "liars", please. We know it's sometimes difficult for new users to find the appropriate information.

3) Be a little more precise in your answers. Not everybody is a technical genius :D

Now, for some folks who are new to the Z2 forums, and this includes Z2 tablets as well.

There is no "Easy" root for 4.4.4. This is well known to most folks. So basically it leaves 2 options.

1) Downgrade your OS to 4.4.2, then you can use the Towelroot based root application, and a few other things. Then you can flash a pre-rooted 4.4.4 ROM and still retain root and DRM keys.

2) Downgrade to 4.4.2 and Back-up your DRM keys using the available app, with root. Upgrade to 4.4.4 and unlock your bootloader, and install a modified Boot.img, flashboot boot a recovery.img, and let it install SU and binary (or use ADB). This way, if you honestly need your DRM keys, you can re-install DRM (and go back to 4.4.2), then migrate to 4.4.4

Honestly, other than some proprietary Sony music, and the loss of Playstation controller, I really can't see a need for the DRM keys anyhow.

Those are pretty much the 2 options. And Lollipop 5.0.x will offer no other options as well.

Bottom line, be nice folks....

MD
[Xperia Z2 General] kamalmawa:
Actually you will loose some camera functionality such as Sony Bionz image processing that helps to reduce the low light camera noise. I know there's a thread that restore this but I doubt that works 100%. Camera is the only thing stopping me from unlocking the bootloader to root, luckily we have an exploit which works on older kernels ?
[Xperia Z2 General] chesterr:
zxz0O0 just released "in dev version for Z3/Z3C/Z3CT. I hope that this should work on Z2 on 4.4.4.

Have any of you tried? damn I am on CM otherwise woulda given a shot and see.
[T-Mobile Samsung Galaxy S 5] dpshptl:
So when you go into setting and go to battery where it shows how long the phone has been up and what apps use how much battery. Shouldn't that get cleared if you take out the battery? Right now it says my phone has been on battery for 6 hours and 47 mins. I take my battery out for several mins and then put it back and go to settings it shows the phone running for the same exact time. I did this several times and each time I turn the phone back on it starts the timer at 6 hours 44 min I thought this should get cleared since the battery was out?
[T-Mobile Samsung Galaxy S 5] SSJSim2:
When you take out your battery, the phone shuts off so a turned off phone can't read a detached battery. Therefore, it assumes you just powered down your device and it'll resume your battery life's stats when you boot your phone up.

Hope that helps!
[T-Mobile, Samsung Galaxy SIII] fenixus:
Reserved

Reserved
[T-Mobile, Samsung Galaxy SIII] jonesin:
Thanks for this! downloading now and will report back if there are any issues. I know you are a new dev but are you looking for us to provide logcats and bugreports for you?
[T-Mobile, Samsung Galaxy SIII] fenixus:
Thanks and hopefully all works well for you just as it does for me :)

Yes, I am fresh meat totally. I'm afraid I wouldn't even know what to do with logcat and bugreports ;) ...

Since this ROM is based on unmodified LS-LP-v4.0 sources, I believe the android OS problems would refer to code in LS tree, unless that is related to Samsung hardware strictly then it would point at CM12 source code. In short, unless CM or LS update their sources there is not much I can fix myself anyways, sadly.

I did this ROM build only to run true d2tmo and fix/enable the baseband issue in original CM sources (which didn't work, you'd get no baseband). After modification all works for me normally!

I promise to build a fresh copy from time to time, after LS-LP updates their code to keep it fresh :)
[T-Mobile, Samsung Galaxy SIII] TheGeekyNimrod:
Way to go dude! Noob or not, you did some things to make it work that I still hadn't figured out in a couple of weeks of trying. A big tip of the cap to you on that one.
[T-Mobile, Samsung Galaxy SIII] fenixus:
Thanks man! :) Worth noting, that I wouldn't even start making it if not for your help with initial compilation errors :)
[T-Mobile, Samsung Galaxy SIII] fenixus:
no more volunteers to test out LS-LP on d2tmo? It works great for me, no bugs whatsoever except for 2 mentioned in first post :)

Camera problem is widespread. The Advanced Reboot to Recovery might be my fixable by me if I get to look into it.

Will be uploading more screenshots soon. So far it's an awesome 5.0.2 d2tmo lollipop :D
[T-Mobile, Samsung Galaxy SIII] Sugartibbs:
Great, changing my TWRP to tmo, give it a run!:laugh:
[T-Mobile, Samsung Galaxy SIII] fenixus:
go for it, I love it and it runs great! :)

I've been running LS-LP d2att builds (since 5.0.0) for weeks without issues, but got tired of editing build props to match my T999 after every update from d2att branch. The official d2tmo build from LS-LP (dated 12/21/2014) had a broken baseband, so it broke my heart too LOL ... This one here fixes it and is built from official sources, nothing else modified ;)
[T-Mobile, Samsung Galaxy SIII] cresch07:
I'd like to give it a run, are there any features that I would have access to that aren't included in the 5.0.2 Validus ROM I'm running?
[T-Mobile, Samsung Galaxy SIII] ad.hoc:
I'm willing to test it out, hell I thought LiquidSmooth for d2 was done, since I hadn't seen a build since December, but I really appreciate you doing this! Do you plan on making weekly builds or just whenever you have time?
[T-Mobile, Samsung Galaxy SIII] fenixus:
not sure, I don't know Validus ROM or what if has. This build here is built from full Liquid Smooth sources, so if you tried it in past then this is what it is . Mind that not all LS features (e.g. as known from v3.2) might be yet available in LS-LP-v4.0 as Lollipop is still fairly new and LS devs are updating it frequently.

Refer to screen shots I attached to first post to see what is in settings.
[T-Mobile, Samsung Galaxy SIII] fenixus:
Thanks! :)

I can make those builds as often as official LS-LP releases some commits, once a week shouldn't be a problem, it takes about an hour to build it from sources and some minutes to upload it :) ... that is if no problems happen heh :D
[T-Mobile, Samsung Galaxy SIII] cresch07:
eh what the hell I'll give it a whirl lol. Downloading now!
[T-Mobile, Samsung Galaxy SIII] fenixus:
That's the spirit! :D
[T-Mobile, Samsung Galaxy SIII] cresch07:
Does the AOSP Keyboard work out of the box? I assume the camera doesn't, most LP ROMs have broken cameras for some reason.
[T-Mobile, Samsung Galaxy SIII] Sugartibbs:
Keyboard works, I like Liquid better than Valadius. FWIW, I use Swiftkey
[T-Mobile, Samsung Galaxy SIII] fenixus:
works OK for me, no probs.Yes, camera broken is a widespread issue on d2. Disable the stock Camera app and download Open Camera from Play Store - it works very well for pics (just don't use tap to focus LOL), video recording is still broken.
[T-Mobile, Samsung Galaxy SIII] cresch07:
ok sweet continuing with flashing.
[T-Mobile, Samsung Galaxy SIII] lazepr:
Loving it! Only 5.0 rom without problems for the t-mobile so far! Thanks. Hope to see more features and camera fix soon. For now ima stick with it. ?
[T-Mobile, Samsung Galaxy SIII] champion9124:
Awesome, I'll install it then, thanks! :D
[T-Mobile, Samsung Galaxy SIII] FatBastid:
This rom has straight brought new life into my old phone. Thanks for your impressive work. Lollipop is pretty impressive in itself, I look forward to following this thread and its nightly builds. The only issue Ive run into is that I got the sim card issue (flashed a bootloader, no dice, reflashed rom and updated to the latest modem). All is good. The camera is a non issue really.
[T-Mobile, Samsung Galaxy SIII] fenixus:
All credit goes to Liquid Smooth team effort ☺

I only provide builds more frequently than official channel ;)
[T-Mobile, Samsung Galaxy SIII] fenixus:
D2lte broken! All seems working until somebody tries calling in. Wait for revised unified build or use my d2tmo for now.

EDIT:

uploaded fresh d2tmo 1/22/2015 and updated OP information to resolve some "issues" I ran into.
[T-Mobile, Samsung Galaxy SIII] cameron_taylor:
needed ..

any camera fix ??? other than open camera fix .. would really like da stock camera so i can video n take pics ... hmm sighs .... and any theme fix ???
[T-Mobile, Samsung Galaxy SIII] lazepr:
I only use my device on WiFi. Is it work fine other than that?
[T-Mobile, Samsung Galaxy SIII] fenixus:
For WiFi only it should be OK!

mtb3000gt will be working on updating the unified tree tonight, so possibly he will post another revision of it tonight or tomorrow.
[T-Mobile, Samsung Galaxy SIII] ad.hoc:
I just wanted to say that I really appreciate you continuing to build LiquidSmooth for this phone. This ROM really makes this phone fly!
[T-Mobile, Samsung Galaxy SIII] snrbobo:
wow i JUST picked up my s3 again because my xperia z3 broke. Figured i'd see about lollipop on this little guy, and man this rom is awesome! thanks for keeping it up to date! works like a charm!
[T-Mobile, Samsung Galaxy SIII] khulet12:
Hi my s3 now is on 4.3 stock rom is it fine to. Jump here/flash this rom? Thanks
[T-Mobile, Samsung Galaxy SIII] mp3deviant721:
Just make sure you completely wipe the device before flashing.

GS³: CyanideL + ShiftKernel Edition™

ギミチョコ！！
[T-Mobile, Samsung Galaxy SIII] khulet12:
Wipe. The system too? But not internal card?
[T-Mobile, Samsung Galaxy SIII] fenixus:
If using Philz Remove SD card (or it will get wiped) and do factory reset from recovery. Philz doesn't delete user data regardless, just cleans app settings from it, not sure about twrp been a while since I used it.
[T-Mobile, Samsung Galaxy SIII] mp3deviant721:
Yes. System too. Internal is up to you. You want a clean slate when you are making a big jump in Android versions like that.

GS³: CyanideL + ShiftKernel Edition™

ギミチョコ！！
[T-Mobile, Samsung Galaxy SIII] khulet12:
Thanks ill do that
[T-Mobile, Samsung Galaxy SIII] Doble Woyo:
Nav Bar

First, thanks for all the work on this. Outstanding rom.. Been using it from the start and I have no complaints. Did have one question. It may be due to the horrible day at work or plain blindness, but I'm lost. Updated when I got home to the 1/22 build and for some reason cannot activate the nav bar. I found the nav bar editor and settings menu under navigation and left handed mode under buttons menu. Where/how is the nav bar turned on? Am I just blind, need a Zanex from work, or work in progress? Thanks again for an awesome rom for D2tmo...