yashsingh1/xdaforums huggingface dataset:
[Verizon Motorola Droid Turbo Android Development] GeoFX:
Lollipop with encryption is working!

Due to the fact you can only encrypt data on stock firmware (any mofo imgs will not let you encrypt data - the process will fail), I was initially hesistant to perform a "dirty flash" of the 5.1 IMG without a FDR as recommended (because once you FDR you need to re-encrypt again). Anyway I tried it a couple of nights ago and I was able to upgrade but there were a bunch of problems (sluggishness, a reboot would hang, recovery wouldn't work, advanced calling error, etc.). So yesterday i did the following knowing i had to reinstall everything and backup/restore my data.

1). Revert back to stock KK firmware

2.) Run the encryption routine (make sure you have inetwork access turned off! If not the phone starts downloading the OTA). Don't install xposed or anything else. Don't even sign into your Google account when setting up the phone. The only thing you need the stock KK for is the encryption process!

3) Delete /data/dalvik-cache and /cache contents. Reboot into bootloader.

4.) Mofo flash CFs awesome IMG. Power down.

5.). Power on into bootloader.. Go to recovery mode and wipe cache again.

6.) 5.1 is upgraded. Verified camera with multiple shots, vz messages, wifi tethering, advanced calling, etc. everything works! My exchange email works as well and 5.1 recognizes the data as encrypted.

7.). Installed the xposed installer for 5.1 - i used the alpha 3.0 version. Any tweak thats certified to be compatible with 5.1 works.

8.) Have a beer while enjoying rooted Lollipop!:D

Thanks again for everything ComputerFreek. Defintely will be happily flashing your updated Lollipop IMGs in the future!:highfive:
[Verizon Motorola Droid Turbo Android Development] Coronado is dead:
I did that CF, no change. The only thing that worked was installing the My Verizon Mobile App. Sent you a PM with quotes/confirmation on it so you don't have to read the whole topic :)
[Verizon Motorola Droid Turbo Android Development] Flowah:
Yeah but it's out of 53GB. Which means a few GB are already being allocated for the image... I think...

My understanding was that when connected to the computer, the phone only shows the storage actually available and not the parts allocated to the image.
[Verizon Motorola Droid Turbo Android Development] computerfreek274:
Baby Steps

Status update on lollipop 1.0B is uploading now base and 493 dpi.

Update

Build.prop with some other fixes and tweaks

Dns fix this helps if your ISP ad base dns servers helps if you use adaway.

Some other tweaks and net speed not a lot just baby steps.

Put My Verizon Back

Fixed 4g in build.prop this is for users that do not have the best of service. I did add this for me so I stayed on 4g here and not jumping over to 3g all the time.

But I removed it in 1.0B

Give it a try and let me know and please remember with some users that have flashed lollipop without a data wipe you may have a few bugs with xposed and other settings so please clear data under apps and all apps for some of the system apps and settings.

If your new and are going to upgrade I think the best think you can do is a full data wipe in recovery!

If you do not do a full data wipe I think be for you flash 5.1 uninstall xposed and all mods.

Please try it out and see if it fixes the few bugs.

I need time to test things myself but it is hard when we are not all on the same page. As both AC settings worked fine for me without my verizon and no 4g bugs. Both the test phones I used have had a full data wipe. When we work out the bugs we can start to work on tweaks and custom stuff. I am still working on V4A but I had to stop working on this today to fix the bugs found. I do not mind but if you guys just hold off for a few days I think I can get V4A build working. I try and read all the post and pm's from all of you and I try to jump on and help you all as much as i can.

So keep checking the same link OP for 1.0B If my internet stays up It will be up very soon and be for you all start to ask yes you have to wipe cache after flashing 1.0b.

Thank you for everything and all your great help, input and feedback You are all a part of making this better than just a stock phone.
[Verizon Motorola Droid Turbo Android Development] Metfanant:
remember...part of the problem is that TECHNICALLY 1GB = 1024MB....but storage manufacturers use 1GB = 1000MB...

so if youre looking for "64GB" you're fighting a losing battle right there because you're losing almost 1.5GB because different groups of people cant agree on what 1GB actually is...
[Verizon Motorola Droid Turbo Android Development] getupandbeit:
Computerfreek274 you are awesome. I'm running the 493dpi version dirty flashed and this phone is faster than ever.

52k in AnTuTu!

Sent from my Droid Turbo
[Verizon Motorola Droid Turbo Android Development] Flowah:
Right. I know that.

But my computer only detects ~53GB total to begin with. I assume that 11GB difference is the 1GB=1024MB and the untouchable system image. I assume that because I don't see how it could be anything else and because on my fresh KK install when I first had the phone I had about 50GB/53GB available.
[Verizon Motorola Droid Turbo Android Development] Metfanant:
Yes, I would imagine you're correct. Your PC/Mac only sees what is formatted as internal storage
[Verizon Motorola Droid Turbo Android Development] computerfreek274:
I need you to stay on topic in here I get an email for this forum so I can stay on top of things and help you guys out. I do not think this has anything to do with my IMG. can you please move over to here or my Q&H forum.

Thanks

PS: I had to stop working on the update to post this.
[Verizon Motorola Droid Turbo Android Development] computerfreek274:
Update

Baby Steps

Status update on lollipop 1.0B is uploading now base and 493 dpi.

Update

07/10/2015 12:36PM Update

Build.prop with some other fixes and tweaks

Dns fix this helps if your ISP ad base dns servers helps if you use adaway.

Full boot animation is back for now with sound.

Some other tweaks and net speed not a lot just baby steps.

Put My Verizon Back

Fixed 4g in build.prop this is for users that do not have the best of service. I did add this for me so I stayed on 4g here and not jumping over to 3g all the time.

But I removed it in 1.0B

Give it a try and let me know and please remember with some users that have flashed lollipop without a data wipe you may have a few bugs with xposed and other settings so please clear data under apps and all apps for some of the system apps and settings.

If your new and are going to upgrade I think the best think you can do is a full data wipe in recovery!

If you do not do a full data wipe I think be for you flash 5.1 uninstall xposed and all mods.

Please try it out and see if it fixes the few bugs.

I need time to test things myself but it is hard when we are not all on the same page. As both AC settings worked fine for me without my verizon and no 4g bugs. Both the test phones I used have had a full data wipe. When we work out the bugs we can start to work on tweaks and custom stuff. I am still working on V4A but I had to stop working on this today to fix the bugs found. I do not mind but if you guys just hold off for a few days I think I can get V4A build working. I try and read all the post and pm's from all of you and I try to jump on and help you all as much as i can.

So keep checking the same link OP for 1.0B If my internet stays up It will be up very soon and be for you all start to ask yes you have to wipe cache after flashing 1.0b.

Thank you for everything and all your great help, input and feedback You are all a part of making this better than just a stock phone.
[Verizon Motorola Droid Turbo Android Development] trikotret:
Can someone check to see if you can send MMS with textra in the new 1B build please. I did 3 clean flashes yesterday. I want to make sure textra works before I flash and wipe data. :)
[Verizon Motorola Droid Turbo Android Development] my2cents:
You should add this info to your second post under the OP. Thanks for the great work!
[Verizon Motorola Droid Turbo Android Development] computerfreek274:
Working fine I will pm you a screen shot. It maybe your account is blocking 3rd party apps. You will need to call verizon and get a high level tech on the phone to unlock it.
[Verizon Motorola Droid Turbo Android Development] computerfreek274:
Thanks I will later I need to get them both uploaded and I have to go out.
[Verizon Motorola Droid Turbo Android Development] trikotret:
I called them yesterday and nothing is on my acct. I used textra fine with the base root image
[Verizon Motorola Droid Turbo Android Development] computerfreek274:
Well I started over with 1.5b give it a shot I also sent you 2 pm's.
[Verizon Motorola Droid Turbo Android Development] trikotret:
I replied back to you. If you can send yourself a picture please
[Verizon Motorola Droid Turbo Android Development] DragonRyderX:
Please assist if you can...

I have posted this in Q&A, but maybe someone here can help also.

http://xdaforums.com/droid-turbo/help/droid-turbo-mofo-connects-flashes-t3154347

I have also tried the reboot computer like 50 times.

Thank you ahead of time.
[Verizon Motorola Droid Turbo Android Development] savagebunny:
Don't post your own thread in someone else's thread. It's not even on topic of his current images, it's a tech issue which is meant for Q&A
[Verizon Motorola Droid Turbo Android Development] gqskrub:
What is the benefit of 493 dpi? and is that the only difference between the 1.0B's?
[Verizon Motorola Droid Turbo Android Development] savagebunny:
From what I can see, yes that's the only difference
[Verizon Motorola Droid Turbo Android Development] neozen21:
But I looked at the Build.Pro... both versions have ro. sf.lcd_density = 640 ... wierd??

Nevermind... there is a 2nd 1.0b now with the 493dpi...
[Verizon Motorola Droid Turbo Android Development] ahaynes42:
I'm on the original 1.0 build and got MMS working with Textra. I just had to go into cellular networks and switch from Global to LTE/CDMA and then back to Global. Seems to have done the trick for me. Also, I was having MMS issues before on KK before flashing this build.
[Verizon Motorola Droid Turbo Android Development] GeoFX:
1.0 vs. 1.0B differences

Just installed 1.0B and it includes VZ Navigator, NFL Mobile, and some other apps plus it the orginal Droid Turbo animation w/sound. Intentional? Thanks!
[Verizon Motorola Droid Turbo Android Development] computerfreek274:
Yeah I did a bit of a start over. So I will be removing some of that stuff I like to add in a short bootanimation with no sound. If this build works good now for you guys I will move on to testing tweaks and stuff. I did not give up hope yet on v4a I have one kind of working on my phone right now it is buggy still and I had to go out. Maybe later I will post a test build with v4a.
[Verizon Motorola Droid Turbo Android Development] GeoFX:
Cool. The build is working well now but it has been since 1.0. Was able to mofo flash 1.0B, power off, power on to bootloader, go to Recovery, wipe cache, and boot up. Everything seems to be working as before including the xposed tweaks. Thanks!
[Verizon Motorola Droid Turbo Android Development] X_man.:
Hmmm Well the new build seemed to flash just fine but now I have the original stock boot animation. Don't really matter to me much tho as long as it runs good LOL
[Verizon Motorola Droid Turbo Android Development] PittAussie:
If V4A keeps giving issues, I don't know if the Dolby drivers and/or Beats Audio drivers that were in my old Bionic ROM have issues with 5.1. They weren't as good as V4A, but better than stock, so it may be a good interim solution.

Dolby Audio: http://tiptrk.blogspot.com/2014/09/quick-guide-how-to-install-dolby-mobile.html

Beats: http://xdaforums.com/showthread.php?t=1525168.

I can't remember what ROM it was that I was using on the Bionic (which eventually died), but I know both drivers coexisted on it.

I just found a post about eXtremeBeats which seems to have both incorporated:

http://xdaforums.com/showthread.php?t=2634729
[Verizon Motorola Droid Turbo Android Development] computerfreek274:
Yeah I was thinking of that. I got it working today and it held the driver in this build but as soon as I go to use it. Starts to crash and or the audio cuts in and out. Not looking good. But this is the 1st build on 5.1 that I got the driver to stick so we will see.
[Verizon Motorola Droid Turbo Android Development] arohrmann:
I checked V4A on other 5.1 and always I got battery drain + reboot.

At the moment there's not working version for 5.1...
[Verizon Motorola Droid Turbo Android Development] trikotret:
Textra and other 3rd party messaging apps work with this build. Thank you
[Verizon Motorola Droid Turbo Android Development] Sleeper69:
in the OP can someone please instruct or guide me how to fasboot the 5.1 images in adb its been too long since I used to know. One of those things if you dont use it you loose the skill. IM just needing help running the fastboot files
[Verizon Motorola Droid Turbo Android Development] janitorjohnson:
So is there a way to fix the moto blink notification lock screen from being off alignment?
[Verizon Motorola Droid Turbo Android Development] Coronado is dead:
So, when I pick up my phone and turn it on with the power button I get the lollipop lock screen (the swipe one, not the PIN one) even if I am connected to a smart unlock device. I assume that's a 5.1 issue and not a rom one?
[Verizon Motorola Droid Turbo Android Development] JakeDHS07:
Turn on power button shows screen lock and you won't have this problem. One screen instead of two. Took me a bit to find this.
[Verizon Motorola Droid Turbo Android Development] Coronado is dead:
Tried, still shows the swipe screen instead of immediately taking me to my home screen.
[Verizon Motorola Droid Turbo Android Development] neozen21:
OK. I must be cursed or what?

I was able to successfully upgrade my Turbo to 5.1 yesterday using ComputerFreek's version 1.0.

However, after that I decided to try a custom system image of my own and have been getting stuck at the Motorola logo, no matter how many times I reflash the 4 files (logo, boot, radio, recovery) and start over fresh. I wipe data & cache every time!

I was able to go back to 4.4.4 again, but every time I try to go to 5.1, I get stuck at the M logo... no matter what system image I use ... any ideas?

Update:

Hmmm.. I just tried again with version 1.0 and I got past the M logo now and was able to finally boot up!

Could my phone just work with version 1.0? and not 1.0B?? Strange!

Thanks!
[Verizon Motorola Droid Turbo Android Development] Sleeper69:
Is there a simple batch file that can be used to falsh the logo,boot,radio,and recovery files
[Verizon Motorola Droid Turbo Android Development] neozen21:
In windows, just create a .bat file and put all the commands in there.
[Verizon Motorola Droid Turbo Android Development] Sleeper69:
apologies

Thank you for your response , but I don't know how to do that.
[Verizon Motorola Droid Turbo Android Development] neozen21:
using notepad, type or copy and paste the following:

fastboot flash logo logo.bin

fastboot flash boot boot.img

fastboot flash radio radio.img

fastboot flash recovery recovery.bin

fastboot erase ddr

then save the file in the same directory as those 4 files, and change the extension from .txt to .bat

then you can run the .bat file in a command prompt or straight from windows explorer.
[Verizon Motorola Droid Turbo Android Development] computerfreek274:
Yeah you install the 493 Dpi ver of the img. You need to set it with an xposed mod. I did not get up the how to on this OP. But if you look under my KK post you will find the how to.
[Verizon Motorola Droid Turbo Android Development] computerfreek274:
Nope not your phone I have flashed 5.1 like 30+ times now trying to test and get v4a working. When you get the black Moto screen like that hold down the power then VOL down and get back to the boot loader then go to recovery and from there 1st you can try a wipe cache but I found I had to wipe data a few times. It is picky rom if you play around to much it gets stuck on old data. Good luck.
[Verizon Motorola Droid Turbo Android Development] savagebunny:
I got a major headache with V4A, and I needed the phone to contact people. Got it stable enough for now. I'm know my way around Linux, but not well enough with Linux and whatever Google did with 5.1 vs 5.0. It's ridiculous
[Verizon Motorola Droid Turbo Android Development] Sleeper69:
I did as above ran it from windows the C: prompt popped up for a split second then shut. How do I know if the files were transferred?
[Verizon Motorola Droid Turbo Android Development] computerfreek274:
Well if you ran it from CMD then you can see what it is doing.
[Verizon Motorola Droid Turbo Android Development] Sleeper69:
from the CMD im in the folder that the .bat file is in what is command line to run .bat file?
[Verizon Motorola Droid Turbo Android Development] computerfreek274:
So did you get your V4A loading at all ? This one I have is no good. It crashes all the time and audio cuts in and out mostly out. I have to reboot over and over. I did find on the V4A crash on boot up if you reboot sometimes it works. real pain in the ass.

I hope you not giving on V4A ? Check this out I found all the files in one zip but I must have deleted it. Give this a try if you have time.

http://www.reddit.com/r/Nexus5/comments/2mdt04/how_to_get_v4a_working_again_on_lollipop/ not as easy on the turbo without full root.
[Verizon Motorola Droid Turbo Android Development] janitorjohnson:
Ok, I went searching for a how to, but having no luck. I have xposed running fine, but which mod do I need?
[Verizon Motorola Droid Turbo Android Development] dewie68:
Dude. Just do what all of us did. You can an automated process that opens and closes CMD quickly. I'm about 80% sure it completed because the files get flashed quickly. So, just continue the process, and you'll be fine. So long as you backed up your data, you'll be able to work through anything that gets thrown your way, even a boot loop.
[Verizon Motorola Droid Turbo Android Development] computerfreek274:
This build has a DPI of 493 stock was 640 is gives you a lot more room on the screen also 5 rows on the home page. But this will make the moto display (active display) off-centered!!! this is the black clock screen when you wave your hand over. there is a fix to there you have to use xposed.

Fix for moto display in DPI 493 build.

Install "App Settings" from Xposed repository (or google it)

Set the DPI to 640 for Moto Display app.

Unlock button and clock will be unaffected!

Credits to Dareal and Jaocagomez
[Verizon Motorola Droid Turbo Android Development] computerfreek274:
Run the filename.bat ! But seeing you sound like your kind of new at this. Please so you do not kill your freaking phone! Please just t do it one line at a time giving it time to flash each file.
[Verizon Motorola Droid Turbo Android Development] computerfreek274:
I updated the OP how to.

How to get into recovery in one step every forum has it backwards and so did I.

This will get you into it one the 1st click

Holding the VOL UP tap the power key !

I got that after 5 or so times into recovery saying to my self it can not be this hard.

Added the info for 493 dpi build

This build has a DPI of 493 stock was 640 is gives you a lot more room on the screen also 5 rows on the home page. But this will make the moto display (active display) off-centered!!! this is the black clock screen when you wave your hand over. there is a fix to there you have to use xposed.

Fix for moto display in DPI 493 build.

Install "App Settings" from Xposed repository (or google it)

Set the DPI to 640 for Moto Display app.

Unlock button and clock will be unaffected!

Credits to Dareal and Jaocagomez
[Verizon Motorola Droid Turbo Android Development] Sleeper69:
This is what shows up. I agree I dont want to chase my tail fn it up the fist time.

not new just havent done it in years. from the CMD line in the folder what is the command to push the file?

in the cmd they all say fasboot is not recoginzed as an internal or external command.

ive been rooted and used the mofo since it was available.

just not sure where to put the 5.1 files and what commands to push them
[Verizon Motorola Droid Turbo Android Development] savagebunny:
This is what I had before I got pissed off, and taking a break from it. I'm literally out of ideas.

Also if you had it running and audio cutting in and out, make sure you have these in your build.prop for V4A

lpa.decode=false

tunnel.decode=false

lpa.use-stagefright=false

Re-packed the .apk and removed the .sh so it would stop the driver install loop - failed

Got SELinux running before Viper so I can get it to permissive which didn't change anything

Got Viper to install and didn't have the loop of "Viper has crashed"

Was able to run Viper but constantly got "Install drivers"

I did have it running in /System/Priv-App by making sure SELInux was in Permissive on boot, then after a few clicks of "Viper has crashed" it would go away, but then again would have the driver install loop.

I forget what other configurations I had. I do truly think that the combination of Lollipop "5.1" and WP On, and whatever new security measures Google put in, is screwing us over. 5.0 is a wholenother animal which is relatively to get running with V4A
[Verizon Motorola Droid Turbo Android Development] computerfreek274:
Yeah I did all the same even the build.prop just like you and I did on KK. Sucks I have a lot of hours into v4a on KK and LP. This sucks.
[Verizon Motorola Droid Turbo Android Development] savagebunny:
It feels like the OS is checking for authentic UUID's (UID's) that are in 5.1 itself. Which was easily just switched around 5.0 and older, that wasn't a big deal. 5.1 turned into a big security OS.

I have no idea how to force the APK just to read the sound driver and have all the audio_policy and audio_effects setup. File permissions is far beyond our problems from the looks of it. I don't wanna abandon it. May have to step back, further develop the 5.1 root images and see what comes about.

I'm still gonna keep reading the V4A OP thread and checking various other phones who are 5.1 and newer, specially Android M since some users got it working on Android M.
[Verizon Motorola Droid Turbo Android Development] Sleeper69:
Im sorry to be a pain. When I use mofo it ecogizes my phone. When I try and use CMD prompt with the 5.1 files in the patform tools dir i try and fastboot the exact command in OP and it wont find the phone.

C:\Android\android-sdk\platform-tools>fastboot flash logo logo.bin

'fastboot' is not recognized as an internal or external command,

operable program or batch file.

ANy help would be appreciated.
[Verizon Motorola Droid Turbo Android Development] roman.ramirez.12:
OK OK guys I'm not savvy as you all are . Just bare with me but I downloaded and extracted 5.1 images to the desktop put my phone in fast boot , looked up and opened thru the start button, CMD. I typed "fastboot flash logo logo.bin" and got a "waiting on device " message and it just stays stuck there. Any clue what I'm doing wrong?
[Verizon Motorola Droid Turbo Android Development] savagebunny:
Your folder looks like this right? http://i.imgur.com/snV5RoI.png

Make sure you have the Motorola drivers installed. Use the USB cable supplied with your phone too unless you know that cable works correctly.
[Verizon Motorola Droid Turbo Android Development] roman.ramirez.12:
Make sure you have the Motorola drivers installed. Use the USB cable supplied with your phone too unless you know that cable works correctly.

Yeah they all should be good I ran mofo and rooted my turbo and my computer does recognize a phone when I plug it in it just says that message when I use the command prompt
[Verizon Motorola Droid Turbo Android Development] GhostRider5666:
How big is 1.0B? I keep downloading 1.34GB