yashsingh1/xdaforums huggingface dataset:
[Verizon Motorola Droid Turbo Android Development] neozen21:
If you use NOVA or APEX launcher then there are lots of themes for both launchers.

I have both, but prefer NOVA...
[Verizon Motorola Droid Turbo Android Development] RyanTillery:
Could be related to 4G lock, possibly... I know that even on pure, unrooted stock VzW rom a call made via Advanced Calling is dependant on LTE connection, so if that becomes unavailable the call drops. (Just speculating about 4G Lock there; not sure if it would affect the handoff to 3G or anything else Advanced Calling related.) I've noticed that same notification behaviour on mine, though... If I remember correctly, there doesn't seem to be an option of muting notifications for the app, either.
[Verizon Motorola Droid Turbo Android Development] rpitera:
I used to use nova but I've become committed to the Google launcher because of its integration of Google now. But thanks for you suggestion!
[Verizon Motorola Droid Turbo Android Development] CoreyWillWhat:
Quick suggestion, you can use nova and set a swipe up on the home screen to open the Google app. Makes it very similar to Google launcher.
[Verizon Motorola Droid Turbo Android Development] neozen21:
Yes, you can assign any shortcut or action to either swipe up, down, double tap, swipe up with two fingers, swipe down with to fingers..
[Verizon Motorola Droid Turbo Android Development] computerfreek274:
I will try to get back to you all soon. I am still at the hospital for testing and there running late. When I get home I will try and get back to you guys on here and the pm.
[Verizon Motorola Droid Turbo Android Development] johnbravado:
maybe. if i got time i will do some more testing on it tonight. then maybe flash the non 4g lock version and see if that clears it up and re flash 4g lock and see if it comes back. i can see how this might be the culprit. maybe it is trying to use the 1x line and cant because of the 4g lock.
[Verizon Motorola Droid Turbo Android Development] graymonkey44:
I apologize in advanced if this has already been said, but I just flashed 1.0C and now I'm unable to send MMS via hangouts. Is anyone else having this problem with this and is there a fix?
[Verizon Motorola Droid Turbo Android Development] computerfreek274:
If you did not already you need to do a full data wipe in recovery. Backup your photo music etc... This is the only was but if you search the forum for "mms" you will find out that doing a full wipe is the only fix. Sorry
[Verizon Motorola Droid Turbo Android Development] graymonkey44:
Yes I apologize for not stating that, but I did a factory reset and also cleared cache directly after without booting up. I just got my refurbished phone so it was straight from KitKat, but I did a full wipe. Should I try doing another one?
[Verizon Motorola Droid Turbo Android Development] computerfreek274:
I tested this the other day with Google hangouts and some other 3party massage app and they are working.

Try this uninstall hangouts. Then boot into the boot loader and do "fastboot erase cache" when done go to recovery and hit wipe cache. Reinstall hangouts. The check under settings that hangouts is your default message app under system settings. Other wise maybe the other guy that this happened to will chime in and see how he made out.
[Verizon Motorola Droid Turbo Android Development] graymonkey44:
I'll try that out, thanks for the quick replies. Can't wait for viper4a! Awesome work.

Edit: I also want to add it feels good to get back root back with lollipop!!! I was one of the ones to take the OTA early. I learned from that mistake. Feels good to be back my friends.
[Verizon Motorola Droid Turbo Android Development] computerfreek274:
Just retested it for you here is a screenshot. Try to use the Verizon message app send a pic then switch back to to hangouts
[Verizon Motorola Droid Turbo Android Development] dewie68:
Yeah, same WiFi. It's okay, I'll get it. Thanks for the help and amazing IMG.
[Verizon Motorola Droid Turbo Android Development] Mattish13:
Does this mean there is a way to root for those who took the ota?
[Verizon Motorola Droid Turbo Android Development] timmyk465:
A couple of other users had this same problem (myself included). For me it happened after my first clean flash of the original KK CF image. After a bit of forum searching, I discovered that for some reason something can get flipped on Verizon's end or your APN settings could have problems. Resetting APN didn't solve it for me. Neither did wiping and reflashing.

If you are getting the "destination address is invalid", and the problem isn't your APN settings, and wiping doesn't help, then the solution I found:

Call Verizon, explain to them that sms works, but mms doesn't.

Tell the tech that you've tried sending through the stock app, the verizon app, and through hangouts.

Tell them you searched the forums, and several people have commented that something may have been toggled on their end.

Tell them you would like to talk to a high level tech to see if they can reset whatever might have been switched with mms.

If they ask to remote into your phone through myverizon, kindly decline, and ask for the high level tech. Over the phone, they had this resolved for me in 5 minutes. The high level tech reset something, and I was instantly able to send mms again.
[Verizon Motorola Droid Turbo Android Development] computerfreek274:
Yes there is ! Call Verizon and get a replacement phone ! Soon real soon or there going to start to ship them with 5.1.

A buddy of mine has found a way to flash a kind of patch but that's as far as he got so far. He is working on it but he works full time and only gets a few hours a week to test what he has so far. He thinks he can patch the boot loader so mofo will work or something like this.
[Verizon Motorola Droid Turbo Android Development] computerfreek274:
Well I have been working almost nonstop to get V4A and other audio mods out to you guys. It is not easy I have tested 100+ Img's so far in the last few weeks. There is a lot more to V4A with 5.1 . I am trying to make it easy on your end when i do release it. I am still testing trying to make it stable not an easy task. So I hope test let a test build out to just a few of you the guys that know there way around android and commands and stuff. I am flashing right now my phone for what I hope to be the last v4a test. If not I may have to step back from v4a for a week or so and maybe try to fit lollipop with some other audio mod for now. something that is easy on your end to get get working. I am busting my ass and have spent hours on this I will keep you all posted. Well have to run flash is 100% lol
[Verizon Motorola Droid Turbo Android Development] wavygravee:
Hey guys, I have a situation where I took the Lollipop OTA on my phone and so I got another phone that still has KitKat on it and now I got moforoot for it.

Now should my next step be putting my sim card into the KitKat phone and "activate" it (meaning sign into my google account and sync all my apps/data) and then flash 1.0C (will require a full wipe)

or can I flash 1.0C first to a phone that has no google account, no app data, before I add my google account to the phone?

If I signed into my google account and start downloading all my previously used apps and app data, I would want to use TiBu to make a back up of all my user apps (and app data) but I need to flash so I have root, to use TiBu. And to flash I would probably need to do a full wipe.

I'm not sure what to do...

Edit: I think the best course of action may be the following,

Activate my phone, sync accounts, apps and app data

Flash CF's KK 1.5.5C (Following instructions here) I reread the instructions and it only specifically mentioned to wipe cache before reboot (after flash) but not a complete full wipe.

Back up user apps with TiBu.

Flash CF's Lollipop 1.0C (or more recent version? soon hopefully?) with a full wipe.

Restore TiBu's backup.

Edit2:

Step 1 FLASH 5.1 files, FLASH 1.0C

Step 2 Activate phone, pop in sim card

Step 3 Finally enjoy wifi tether and Xposed and everything else computerfreek274 has baked on!
[Verizon Motorola Droid Turbo Android Development] Slartibartfast_:
If your new phone is still unactivated, why would you install apps and configure anything on it before flashing 5.1 and only then doing all that? Full wipe is not mandatory but it's definitely recommended.
[Verizon Motorola Droid Turbo Android Development] wavygravee:
So with the new phone, should I just flash 1.0C? And then start syncing my apps? That shouldn't cause any issues would it?

With flashing experience, I've probably always done a dirty flash (if permitted) or a flash with a full wipe. Never on a "new" or unused phone.

Hmm, now that I think about it, when a full wipe is done on a phone, it's essentially like a "new" phone, without any downloaded apps, am I thinking of this correctly?
[Verizon Motorola Droid Turbo Android Development] neozen21:
If you are getting a fresh phone with stock KK installed, then it wouldn't make sense to have it sync your apps+data or even flash the rooted KK image.

Don't even bother activating your phone. Just go straight to Bootloader, then flash the required files (stated in the OP), then mofo flash the rooted LP image (1.0c) . I would just do a data & cache wipe as well, because you are going from KK to LP.

Enjoy!
[Verizon Motorola Droid Turbo Android Development] wavygravee:
Thank you so much for working on this for our community. This lollipop image is kind of keeping my Droid Turbo afloat for much longer than I thought!

---------- Post added at 12:01 PM ---------- Previous post was at 11:59 AM ----------

Yeah I figured this to be the most logical solution. Duh!!! Thanks neozen21!
[Verizon Motorola Droid Turbo Android Development] JakeDHS07:
New official update is apparently being pushed if its possible to change the base?
[Verizon Motorola Droid Turbo Android Development] neozen21:
I haven't seen any one upload the .zip or .img yet.

Can someone please share if you have it?
[Verizon Motorola Droid Turbo Android Development] computerfreek274:
I am in no rush when there is a full zip or IMG out I will update my base to it.
[Verizon Motorola Droid Turbo Android Development] JakeDHS07:
Wasn't trying to rush. Just giving a heads up. I haven't even been able to find a changelog
[Verizon Motorola Droid Turbo Android Development] GeoFX:
LOL at all these people turning in their phones for "warranty replacement" cuz they ignored all the warnings and took the OTA :p
[Verizon Motorola Droid Turbo Android Development] trikotret:
It's only a small update. I wonder if it can be implemented in these images
[Verizon Motorola Droid Turbo Android Development] fireman928:
I have notice after I flashed 1.0c that xposed would not work said its installed but not active so I went back to 1.0b and same thing. Also I noticed that on 1.0c when I make phone call it drops from 4g down to 1x and horrible reception so I went down to 1.0b have no issue with phone calls dropping down from 4g to 1x.
[Verizon Motorola Droid Turbo Android Development] gqskrub:
First... DID YOU WIPE DATA?

Second ... DID YOU WIPE DATA?

Third ... maybe factory reset and start over? My exposed worked on both 1.0c and 1.0b.

Also.... did you restart your phone after installing Xposed?
[Verizon Motorola Droid Turbo Android Development] fireman928:
Did that did that and did that but I will do it all again and try that
[Verizon Motorola Droid Turbo Android Development] computerfreek274:
Anyone see a change log yet for the new update ? I block updates on my img's I hope! So if you see it telling you there is an update JUST SAY NO!
[Verizon Motorola Droid Turbo Android Development] DucatiMon:
I had the same issue with xposed before. Try wiping data for busy box and the reinstalling. That resolved it for me and its worth a shot before you wipe.
[Verizon Motorola Droid Turbo Android Development] Butcher98:
Anyone able to get betterbatterystats to work properly with LP? The Xposed module with BATTERY_STATS permission doesn't seem to work.

---------- Post added at 08:24 AM ---------- Previous post was at 08:22 AM ----------

How has your battery been since doing this? Any you didn't limit in the guide? Just curious. May do this later today.
[Verizon Motorola Droid Turbo Android Development] wavygravee:
I'm posting with a huge grain boulder of salt but based on page 3 of this topic (here) it seems like it may possibly be an update to set up for 5.1.1.
[Verizon Motorola Droid Turbo Android Development] computerfreek274:
Yeah I have seen that also I don;t think the download on that page is any good it was posted a few days ago but I am downloading it anyways.

I am uploading 1.1 now this will not have the newest update from verizon in it. This ver is in hope will fix any bugs some users have had. Please remember if you have not done a full wipe data in recovery please do so.

For uses that have already done a full wipe and is going to be updating to 1.1 do it this way.

Flash via mofo !

When mofo is 100%

Do "fastboot erase cache"

Then enter in to recovery and wipe cache/format. In my testing looks like mofo uses up cache and with the new recovery when you think your doing a wipe/format it is not doing it looks like it did but seems to be not released after mofo. So doing fastboot erase cache seems to be working well for this..
[Verizon Motorola Droid Turbo Android Development] PerCompLLC:
Looks like it's going to have to be baked into the /system/app folder to get it to work properly since there isn't a working xposed module. Any chance of this CF? :D
[Verizon Motorola Droid Turbo Android Development] computerfreek274:
I can test it I am working on img's not. What ver of my img do you use ? Also send a link to the repo. Thanks
[Verizon Motorola Droid Turbo Android Development] PerCompLLC:
1.0C - As far as I know it's just an APK. I can send it to you if you need.
[Verizon Motorola Droid Turbo Android Development] computerfreek274:
I will find it and test it later.
[Verizon Motorola Droid Turbo Android Development] PerCompLLC:
Thank you sir! Not a high priority at all, just a nice to have.
[Verizon Motorola Droid Turbo Android Development] GeoFX:
I've been able to install this in xposed and am getting the updated battery stats in GSAM in 1.0-1.0C IMGs.

http://xdaforums.com/xposed/modules/xposed-module-enablebatterystatsx-t3064688

Now, if you want to enable the "Alarms" function in the Better Battery Stats application, the apk needs to be installed in the /system/priv-app file. The app will still give you additional info with the xposed module but that function won't work. The developer has a xda version of the app on the BBS XDA page but not sure if he wants it freely distributed in another person's IMG. :cyclops:
[Verizon Motorola Droid Turbo Android Development] McDastardly:
I've been adding the app to the system image on every version so far manually and it works fine.
[Verizon Motorola Droid Turbo Android Development] PerCompLLC:
I'm assuming that you are just taking CF's image, mounting it in Linux and adding the apk. Correct?
[Verizon Motorola Droid Turbo Android Development] wavygravee:
Or could you change the user app to a system app in TiBu?
[Verizon Motorola Droid Turbo Android Development] McDastardly:
Yes sir
[Verizon Motorola Droid Turbo Android Development] PerCompLLC:
Can't as it won't stick after a reboot. Remember that the /system folder is still write protected...
[Verizon Motorola Droid Turbo Android Development] Butcher98:
Nice, hope to see this added. ????
[Verizon Motorola Droid Turbo Android Development] PerCompLLC:
I'll give it a try. I created my Linux VM but I still haven't been able to mount the image properly, and then life got in the way. Maybe I'll tackle it again tomorrow... :good:
[Verizon Motorola Droid Turbo Android Development] johnbravado:
how do we flash a zip? can we fastboot flash it? and what is command sorry kinda new. Also which arm do we flash the arm or arm64 or armx86
[Verizon Motorola Droid Turbo Android Development] neozen21:
The only way you can flash a .zip file is to use a custom recovery, such as TWRP, which we don't have because of the locked bootloader.

Now, you can try to do what the .zip file does by looking at the script inside and manipulate the .img

However, that's probably something you wouldn't know how to do...:p

---------- Post added at 12:10 PM ---------- Previous post was at 12:02 PM ----------

I'm looking into the quark_verizon-user_LCF23.80_release-keys_firmware_upgrade_SVC.xml.zip that was posted on RootJunky's website.

Initial analysis indicate it could be Android 5.1.1 but I'd like to look at the full system.img to be sure.

However, I don't have access to a full Ubuntu system here at work (I only have a Lunbuntu box running RK3288 box) and I'm having a hard time compiling the simg2img utility needed to reconstruct the system sparsechunk files. Not to mention I'm supposed to be working.. not messing around with Android stuff :P

Anyone know a quick way to reconstruct the full system.img from the sparsechunk files?
[Verizon Motorola Droid Turbo Android Development] siegesoldier:
https://github.com/KinglyWayne/simg2img_win will give you a compiled simg2img keep all the files it comes with in the same directory. I know it needs that .dll at the very least.
[Verizon Motorola Droid Turbo Android Development] graymonkey44:
Well I got MMS to work again. Can't really explain how, but I originally was trying to send MMS through a chat room with two of my friends. I decided to just test MMS in general and sent a picture to my sister. Worked perfectly, then I decided to resend the original texts from my chat that wouldn't go through and they went through without an issue. No troubles with MMS since. Thanks for helping out though.
[Verizon Motorola Droid Turbo Android Development] neozen21:
Well... I was finally able to extract the build.prop from the quark_verizon-user_LCF23.80_release-keys_firmware_upgrade_SVC.xml.zip file by rebuilding the system sparsechunk files.

I was only able to extract the content in Windows using ImgExtractor_1_3_4.

Couldn't convert the .img to ext4 to mount in Linux. For some reason simg2img won't work... it says "Bad magic".

It does look like it is indeed Android 5.1.1 for XT1254.

Here is part of the build.prop

# begin build properties

# autogenerated by buildinfo.sh

ro.build.id=LCF23.80

ro.build.display.id=LCF23.80

ro.build.version.incremental=80

ro.build.version.sdk=22

ro.build.version.codename=REL

ro.build.version.all_codenames=REL

ro.build.version.release=5.1.1

ro.build.date=Tue Jun 30 10:14:48 CDT 2015

ro.build.date.utc=1435677288

ro.build.type=user

ro.build.user=hudsoncm

ro.build.host=ilclbld96

ro.build.tags=release-keys

ro.build.flavor=quark_verizon-user

ro.product.model=XT1254

ro.product.brand=motorola

ro.product.name=quark_verizon

ro.product.device=quark

ro.product.board=APQ8084

# ro.product.cpu.abi and ro.product.cpu.abi2 are obsolete,

# use ro.product.cpu.abilist instead.

ro.product.cpu.abi=armeabi-v7a

ro.product.cpu.abi2=armeabi

ro.product.cpu.abilist=armeabi-v7a,armeabi

ro.product.cpu.abilist32=armeabi-v7a,armeabi

ro.product.cpu.abilist64=

ro.product.manufacturer=motorola

ro.product.locale.language=en

ro.product.locale.region=US

ro.wifi.channels=

ro.board.platform=apq8084

# ro.build.product is obsolete; use ro.product.device

ro.build.product=quark

# Do not try to parse description, fingerprint, or thumbprint

ro.build.description=quark_verizon-user 5.1.1 LCF23.80 80 release-keys

ro.build.fingerprint=motorola/quark_verizon/quark:5.1.1/LCF23.80/80:user/release-keys

ro.build.characteristics=nosdcard
[Verizon Motorola Droid Turbo Android Development] computerfreek274:
Guys do not flash the new radio from 5.1.1. or any files just yet! Seems Verizon maybe trying to stop custom ROM/IMG by hiding stuff in the boot and radio. Just HOLD OFF A bit right now I have no WIFI and things are not going right I am flashing back I hope! I am working on 5.1.1 But I have to go back for a bit to check that we can flash back. After I flashed the new radio things where OK then I went back to the old radio and lost wifi and crashes the phone if you turn it on.
[Verizon Motorola Droid Turbo Android Development] wavygravee:
Would this warrant an OP edit to include as an FYI? Seems like another potential game-breaking update. Now my old droid turbo (took the 2nd update yesterday) will possibly never see root.
[Verizon Motorola Droid Turbo Android Development] kitcostantino:
edit: I'm out of the loop. there's a second update?

I did the initial lp mofo img. holding off altogether for a bit.
[Verizon Motorola Droid Turbo Android Development] computerfreek274:
Nope! I got back fine just do not take ota or flash any boot loader.

Update on 5.1.1 I have the system.img all set just need to root and xposed and test I think we will be good. Off to work look out for an update maybe even tonight. You will have to reflash boot radi and recover but I will post up everything asap.
[Verizon Motorola Droid Turbo Android Development] wavygravee:
You're seriously pretty awesome right now.
[Verizon Motorola Droid Turbo Android Development] TheSt33v:
Just FYI, I tried flashing boot and recovery of 5.1.1. Fastboot wouldn't let me do it. I'm in the process of seeing if the 5.1.1 system image will boot anyway, but I haven't had much luck yet.
[Verizon Motorola Droid Turbo Android Development] siegesoldier:
if computerfreek was able to flash them and you aren't I imagine you are having some fastboot driver issues or file corruption.
[Verizon Motorola Droid Turbo Android Development] TheSt33v:
I think he was speaking hypothetically, as in "you should be able to flash those things." I can flash the other images just fine, but boot and recovery both give me a (bootloader) Preflash validation failed error. I tried a fresh download, and that did not solve the problem.
[Verizon Motorola Droid Turbo Android Development] johnbravado:
Are we going to have to wipe data again for 5.1.1 since we are upgrading everything like radio and recovery and such?
[Verizon Motorola Droid Turbo Android Development] neozen21:
I find that hard to believe, because the update batch file (quark_verizon-user_LCF23.80_release-keys_firmware_upgrade.bat) is the same as every other, it flashes radio, boot, bootloader, logo and recovery using fastboot..
[Verizon Motorola Droid Turbo Android Development] TheSt33v:
You mean fb_mode_set? Nope. That didn't fix it either. I guess it's possible that I'm not getting the 5.1.1 files from the same source as computerfreek and mine are corrupt somehow, but it seems suspicious that it would only be those two files...
[Verizon Motorola Droid Turbo Android Development] firstEncounter:
It definitely looks like it should work, but it doesn't. Not sure if the boot/recovery images were signed with development keys (even though it says release) or what.

As far as I know, no one's been able to flash them successfully. (Unless they have another source, the zip I have is named quark_verizon-user_LCF23.80_release-keys_firmware_upgrade_SVC.xml.zip)

Also, the full image has a build number of 23.1.80, Android version 5.1.1 and built on June 30th, whereas the latest OTA is 23.11.38 but still 5.1 and built on July 10th. So I'm not really sure what this image is supposed to be.
[Verizon Motorola Droid Turbo Android Development] neozen21:
I have the files, but I'm not brave enough to flash them just yet :)
[Verizon Motorola Droid Turbo Android Development] TheSt33v:
Haha well if it makes you feel any better, I've tried this twice now and I've been able to flash the 5.1 files and go back to 5.1 with no issues. Try flashing boot and recovery. You won't be flashing much of anything.

---------- Post added at 08:43 PM ---------- Previous post was at 07:55 PM ----------

On an unrelated note, can anyone tell me how to add back the original boot animation? I've tried just placing bootanimation.zip into its proper place with proper permissions into /media, but that didn't work.
[Verizon Motorola Droid Turbo Android Development] BZguy06:
Make sure you change the permissions rw-r--r--