yashsingh1/xdaforums huggingface dataset:
[Verizon Motorola Droid Turbo Android Development] Elysium1215:
Just finished setting everything up! I'm going to post a detailed walkthrough, Computerfreek feel free to copy/paste this to the OP

Download and unzip fastboot files and your favorite rooted LP image from OP

(Optional) If you want to factory reset, now would be a good time to backup your app data/SMS/etc

Plug your phone in to your computer, make sure you have drivers, adb, and fastboot ready to go

Run the following commands in order, one at a time:

adb reboot bootloader
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash radio radio.img
fastboot flash recovery recovery.img
fastboot erase ddr

Now flash your image

mofo flash <IMAGE NAME HERE>

Now press power to start your phone, it will go to the "DROID" bootscreen but will not boot

Hold down POWER + VOL DOWN until your phone turns off and then turns back on into bootloader

Press VOL DOWN to find the option "recovery mode" and press POWER. (This step is necessary because booting into recovery right after flashing LP results in a flashing dead android icon, so we want to boot normally then reboot into bootloader to get to recovery)

Hold down VOL UP and tap POWER to get into recovery commands. This step can be finicky, so keep trying different combinations and grips and lengths of holding down the buttons.

From the recovery menu, wipe cache or factory reset (which should wipe cache for you as well). Wiping cache can take a long time, for me it took around 20 minutes, be patient

Reboot, you should successfully be booted into Android in around 3 minutes or so

---------- Post added at 11:52 PM ---------- Previous post was at 11:48 PM ----------

Ah this is interesting, because I've heard the way mofo works is by overwriting cache which precedes the system partition (so the overflow from cache actually goes into the system partition). So the reason it might take so long is because the cache is completely filled by mofo...
[Verizon Motorola Droid Turbo Android Development] SSBMMASTER:
Okay so after hours of reflashing and wiping the cache through mofo i finally got it to boot.

Talk about a pain in the ass, wish we had a traditional method of this stuff, oh well, thank you everybody who took the time to help me out.
[Verizon Motorola Droid Turbo Android Development] gqskrub:
Any way to get custom boot animations?
[Verizon Motorola Droid Turbo Android Development] fireman928:
Does this image have the WiFi terher baked into it
[Verizon Motorola Droid Turbo Android Development] neozen21:
OK. I know what's the problem now.

In your OP, the Xposed paged you link contains the framework (SDK) that only works only Android 5.0.

There is a version of Xposed framework that works with 5.1 and the link is here:

http://xdaforums.com/xposed/super-alpha-posted-permission-xposed-t3072979

No wonder my images wouldn't boot up.

I was trying to use the V66 that works only on Android 5.0..

Looks like V65 is already the lastest for Android 5.1, so I don't need to update it :p

Thanks!
[Verizon Motorola Droid Turbo Android Development] PerCompLLC:
Yes.
[Verizon Motorola Droid Turbo Android Development] janitorjohnson:
Interesting. I never installed xposed again.... I wonder if that is why I never had any issues. I'm running the same xposed as I had with kk. It's version 58 and says it's not compatible but all my modules work.
[Verizon Motorola Droid Turbo Android Development] kasim1:
haven't look thru entire post,

any1 know if i can revert back to KK if i don't like Lollipop?

Thanks
[Verizon Motorola Droid Turbo Android Development] johnbravado:
Yes just fastboot the kk thigs and flash a kk image
[Verizon Motorola Droid Turbo Android Development] kasim1:
Thanks Mate !!!

:good:
[Verizon Motorola Droid Turbo Android Development] subhelix:
Just questioning if this is normal. Before I did anything, I wiped the dalvik-cache thru ES explorer. I then did the fastboot commands, flashed the dpi image, and then tried to get into recovery to wipe cache. I got the android logo flashing. I then rebooted and got back into recovery. Logo was not flashing, but I get no command, no matter how many times I reboot. So I finally just booted up. I'm on the android is starting screen.. optimizing my apps... 324. I acutally got past that and it changed to the message of opening apps. That message has been on there for like at least half an hour. Is that normal, or should something be done at this point?
[Verizon Motorola Droid Turbo Android Development] CoreyWillWhat:
From what I remember first boot with ART takes quite a while. With that many apps its possible it could take that long.
[Verizon Motorola Droid Turbo Android Development] nrgyitguy:
Thats normal, When finished optimizing reboot to bootloader and ultimately recovery to wipe the cache. You then need to boot back up normally and switch xposed modules (I think anyway, all my xposed stuff worked on the KK xposed but I upgraded to the lollipop xposed anyway) and alter adaway hosts file location.
[Verizon Motorola Droid Turbo Android Development] kasim1:
So i went to "unofficial " thread and what do i install?

and how?

I really need xposed.
[Verizon Motorola Droid Turbo Android Development] nrgyitguy:
Download xposed version 65. I unistalled version 66 and installed version 65 and then rebooted to recovery and wiped cache again (probly didnt have to but wipe cache againI did), also make sure your modules are for lollipop as well. You might uncheck any KK modules in current version, reboot, then unistall 66 and install 65 and reboot again, probly wouldnt need to wipe cache that way (might not need to anyway)
[Verizon Motorola Droid Turbo Android Development] savagebunny:
I'm getting a crazy amount of battery life ATM. Problem is the refresh times are super low.. Meaning they refresh sooner than later. I'd recommend anyone to check out Amplify. It's a Xposed module. I've upped all my values. I still have auto sync on but only does it every 3600s IF any data source is on. It will be 2 days of battery life in a few hours and I'm at 73%.

Also, since CF is taking a break, I'll try and pop in here more and help out. I've made a ton of my own images so I hope I can help anyone while he takes a break.
[Verizon Motorola Droid Turbo Android Development] Sleeper69:
OK I rebooted apps optimized. Shut it down went to recovery mode and have the broken andoid with no command. below it. I have held the volume up button for 10 seconds then tapped the power button still doesnt go to recovery commands so i can wipe.
[Verizon Motorola Droid Turbo Android Development] kasim1:
Great instaractions, but i'm still fighting with "recovery mode" step,

broken android flushing but can get to recovery menu to wipe cache?

what are the options?
[Verizon Motorola Droid Turbo Android Development] kasim1:
Having the same problem. :confused: :crying:

WTF
[Verizon Motorola Droid Turbo Android Development] Sleeper69:
This is where I am at.
[Verizon Motorola Droid Turbo Android Development] Elysium1215:
You just need to keep trying with different grips and combinations. It took me a long time to get it to actually work
[Verizon Motorola Droid Turbo Android Development] Sleeper69:
To be correct it it still volume up and tap the power?
[Verizon Motorola Droid Turbo Android Development] Elysium1215:
Yep, sometimes holding power and volume up at the same time works but you might also restart the phone if you hold power for too long. What worked for me seemed be holding the phone sideways, screen up, against my chest and pressing power with one hand and volume up with the other, does that make sense?
[Verizon Motorola Droid Turbo Android Development] Sleeper69:
Holding them together worked but only hold them a second.
[Verizon Motorola Droid Turbo Android Development] kasim1:
So, you got into recovery mode? to wipe your cache?

but holding power + Vol Up for a second?

i did try that, nothing.

I think by accident i click on "Factory" so my phone is resetting right now.

again, not sure wtf i broke :)
[Verizon Motorola Droid Turbo Android Development] CoreyWillWhat:
I think the best way to do this, the way I did it. Is to wipe the cache/factory reset from the recovery before you even run the fastboot commands to flash the new recovery. This way you don't have to get into the recovery to wipe cache after you flash the new image. Doesn't help anyone who already has flashed the fastboot recovery but will help anyone who is doing this first time.
[Verizon Motorola Droid Turbo Android Development] kasim1:
Where did you find 65?

i can't find it, can you post a link?

it's just a regular APK? or something else?
[Verizon Motorola Droid Turbo Android Development] savagebunny:
Going into recovery mode, you have to keep clicking Vol Up + Power Button at the same time. It won't work on the first try. Hell, it took me more than a minute to get into recovery, but it worked sooner or later. Just keep pressing them at the same time. The Image flash has nothing to do with getting into recovery mode. The only thing that messed with recovery mode was the 5.1 fastboot flash of the recovery bin
[Verizon Motorola Droid Turbo Android Development] nrgyitguy:
I had to hold both vol up and vol down for like 10 seconds I the pushed the power button while still holding volume up and down. It took me many times of different combos but it will work...

---------- Post added at 04:11 PM ---------- Previous post was at 04:09 PM ----------

http://xdaforums.com/xposed/super-alpha-posted-permission-xposed-t3072979

read the op and download the correct zip, unzip it and the apk wiull be available.
[Verizon Motorola Droid Turbo Android Development] kasim1:
here's my discovery, it was a painful 2 hours to get into Recovery Mode.

My android broken/exclamation image was flushing and what ever i press nothing worked to get into recovery.

on first screen i press "by accident" factory, then after reboot i saw boot/Droid image for 20 min, so i thought it's to long and booted again,

when i went to recovery, my broken/exclamation WASN'T flushing,

then i press quickly both power and VOL UP and got into recovery mode

FYI

to clear cache took a while, don't panic.

Keep going ............

---------- Post added at 06:16 PM ---------- Previous post was at 06:12 PM ----------

all files are ZIP

no Apk, unless i'm blind(again)

can you post direct link?

and i just booted my phone and old xposed that i had with 4.4.4 is installed and working, not sure if all modules a properly working.

should i uninstall old one?

and install new/65?
[Verizon Motorola Droid Turbo Android Development] savagebunny:
I actually had that same issue, but wasn't his image flash. I had the flashing screen issue also when trying to go into recovery. Which was odd, because I've never seen it.

What I did do what get back into fastboot, and reflash recovery.bin, then instead of going directly into recovery, I just hit start. Loaded up fine. Then rebooted, loaded. Shut off, Vol Down + Power back into fastboot then into recovery and didn't have the "flashing" screen issue
[Verizon Motorola Droid Turbo Android Development] activeservo:
Does anyone elses WiFi have a ! after it and keeps dropping off and switching to 4Glte?
[Verizon Motorola Droid Turbo Android Development] johnbravado:
The no command is normal. It is reversed to get into recovery. Instead of holding up and hitting power. Hold power and hit up
[Verizon Motorola Droid Turbo Android Development] fireman928:
So how do you get xposed to work. I downloaded the apk from where it says and I open it and it says that version 65 is active but the install/update, uninstall and classical installation mode are grey. Can't do anything there. Is all I needed to do was the apk. Seems to easy lol. I tried to use the apm module but it don't work. Maybe that one just don't work for lp idk.
[Verizon Motorola Droid Turbo Android Development] CoreyWillWhat:
Install the apk and you're good to go. It's not too good to be true. It's that easy! :)
[Verizon Motorola Droid Turbo Android Development] fireman928:
OK sweet. Went through and read a bunch on here but not gonna go though 50 pages lol. Thanks bud I was making sure. So easy a caveman can do it
[Verizon Motorola Droid Turbo Android Development] Slartibartfast_:
I've been on the fence with Mofo in the last few months, mostly because I knew 5.1 was coming and didn't want to risk having to choose between 5.1 and having root. Thanks to you, I could get both with about an hour work on my part.

Thanks so much for all the work you've been putting into these images and for all the extra time you've been taking to answer questions and help people troubleshoot their individual issues.

A small donation is coming your way. It's not a lot but I hope it helps a bit. Keep up the good work!
[Verizon Motorola Droid Turbo Android Development] computerfreek274:
I was off xda for only a few hours and there like 2 or 3 pages added on here

One more time on recovery and I just tested it.

When you see the dead Android guy! Stop and hold on for 10 seconds or so. Then hold VOL up keep holding it then just tap power key as you are still holding the power key! Do all this very as low between steps like hold VOL up for 3 or so seconds the tap power. I do this and get into recovery every time and always the 1st time. There is no other ways we all have the same recovery after you flash the new one.

Please even if you have already updated you phone and it is all set please go test this way out. If it works please hit thanks on this post. I have 12 pm's asking hot to do this. I am getting burned out guys and as most of you know I am also sick. So please I am sorry I can not respond to all the post in the last hours. I hope you guys that where having trouble I hope you guys got it working. I have updated 6 phones my self 1st time on each phone and and my phone has been flashed so many times I lost count after 30.

Thank you guys for all your support. I am very grateful to all of you.
[Verizon Motorola Droid Turbo Android Development] savagebunny:
Good stuff man. Get better. Like I said, I'll try and be more proactive in here since I worked along side a bit and tore into these images like crazy since KK because I wanted the best.

I'll lost a few updates regarding tweaks, new updated images, further progress in this post. This isn't 100% correct, but basing off what [MENTION=6076132]computerfreek274[/MENTION] in past posts, I'll reiterate it.

1. The "bloated apps". This wasn't a top concern when the image was released technically. In the past Me and CF both agreed on providing the best images we can upload, flash with 0 issues. When 5.1 came out everyone was looking for a image. CF worked his ass off to push one out, got delayed by V4A due to what I assume are permissions, security, and kernel checks Google implemented in. Thus what I assume he had a backup clean image, threw that hella tweaked one away which was probably messed up somewhere along the road due to trying to configure V4A, and freshly released a stable image for everyone.

2. Removing bloated apps, keeping tethering in the ROM are important. Xposed is running seemingly for the time being. Install the latest .apk from the link he provided. Open up, install modules. You're done. Very easy.

3. I noticed he didn't put Busybox 1.23.3 in the image, I did this myself. I'm pretty sure its on the to-do list with removing bloated apps, but then again, refer to #1.

4. We all have the same logo, recovery, image versions.. Literally everything. What other users say, CF, me etc, it will work due to no variation in different versions which can cause bugs.

Please, before you blow up his inbox, ask here, use the search function. The most common things I've seen is Xposed, recovery, flashing screen going into recovery (which I've mentioned a fix).

So please go back a few pages, if your question isn't truly answered, then ask away here. I'm not saying don't ever PM CF, but he is a busy man, has kids, needs 1v1 time with his wife. We all don't need a tired worn out dev.

Disclaimer: I'm straight and blunt to the point. I don't sugar coat anything when I provide answers so I may come off as a asshole, blame my military service for that.
[Verizon Motorola Droid Turbo Android Development] Butcher98:
[MENTION=3376265]savagebunny[/MENTION] are there any tutorials you recommend for getting the most out of Amplify? I have always used greenify. Just wondered if using them together will cause problems or not or what settings will help with just using Amplify. TIA
[Verizon Motorola Droid Turbo Android Development] Slartibartfast_:
For me it was actually holding power and tapping the volume up. I tried it the way you describe a few times without success.

Also, I learned that after flashing with mofo I should have hit "start" in fastboot and let the phone boot up and only then go into recovery. Otherwise I got the flashing dead android logo again and again and couldn't get into recovery.
[Verizon Motorola Droid Turbo Android Development] savagebunny:
I've never actually found one tbh. The dev who wrote the app included descriptions of each wakelock, what it did, and what you can safely set higher for better battery life. You're only able to block this specific one with a small donation, but damn is it work. It changes all the times.

Greenify still works well and I'd still recommend it. Which sleeps the apps and has nothing do to with certain system wakelock we all hate.
[Verizon Motorola Droid Turbo Android Development] ahaynes42:
So on KK when I turned Wifi on, the 4gLTE symbol would go away and the wifi symbol would take the place of it. The cell service signal level would still be there, but the 4gLTE symbol would be hidden because once on wifi we don't need to know what cell data connection we have. Does anyone know if this is standard practice in Lollipop or is it just this image?
[Verizon Motorola Droid Turbo Android Development] Butcher98:
Thanks, I had donated so I made that change. Are there any others that you made? Your battery life sounds crazy!
[Verizon Motorola Droid Turbo Android Development] savagebunny:
Currently the only wakelocks I have limited. Time in seconds is totally your choice. I can post them if you'd like. I just set a few new ones this morning due to battery drain overnight which killed my 3 day spree but oh well.
[Verizon Motorola Droid Turbo Android Development] savagebunny:
This the same for this image (Plus all Lollipop images iirc). Whenever I get a MMS and I have WiFi on, the little 4G icon pops on which I know I'm receiving MMS, then goes off
[Verizon Motorola Droid Turbo Android Development] Butcher98:
Seeing your setup would be great! Thanks!
[Verizon Motorola Droid Turbo Android Development] savagebunny:
* NetworkStats - 1600 Seconds (26.6 minutes). 1600 sounded cool at the time. I'll see how it works out, but like it says in the description, I don't see it being a issue.

* Icing - 240 seconds. Just kept it default. If it wakelocks more next time when I'm checking battery life I'll up the time to 5 minutes

* GCoreFlip - 1500 seconds

* NfcService:mRoutingWakeLock - Don't mess with this unless you use NFC. I never have nor will I ever. Set to 86400 seconds (24hrs)

* SyncLoopWakeLock - If you wanna keep auto-sync on for your apps, but hate how fast it auto syncs your stuff, change this time to what's comfortable for you. Mine is set to 3600 seconds (1hr)

* StartingAlertService - Calendar, I don't use it. 86400 (24hrs)

* NlpWakeLock - the dreaded famous NLP. I set it to 500. In the safe range

* NlpCollectorWakeLock - same as above, 500, safe range

* I had a massive leak or stuck ProximitySensorManager, I hope this fixes this issue (also a reboot fixes it too). Set it to 3600 seconds 1hr. This is a testing one for me, says safe to limit in Amplify
[Verizon Motorola Droid Turbo Android Development] johnbravado:
what is the wakelock program you are using? all i can ifnd are wakeloke viewers. i was interested in trying this out to see if i can improve battery life
[Verizon Motorola Droid Turbo Android Development] savagebunny:
Amplify :) - http://xdaforums.com/xposed/modules/mod-nlpunbounce-reduce-nlp-wakelocks-t2853874

Those other settings I mentioned you can only do if you do a small donation. You can still kill some major ones like NLP etc.
[Verizon Motorola Droid Turbo Android Development] Tru7h:
This might be a stupid question, but I'll ask it anyways. If I am upgrading from 1.0 to 1.0B do I need to flash those images through fastboot, or can I just run mofo flash <name.img>? And, can I get by with just wiping cache, or do I need to do a full wipe?
[Verizon Motorola Droid Turbo Android Development] savagebunny:
My memory is crap, but 1.0 was the initial release of his 5.1 image. 1.0B is the update stable release with some fixes. All you gotta do like you said is mofo flash <image.img>

Before that, make sure you clear cache, that's paramount. If you do run into any bugs, weird crashes, you may have to do a full system wipe, but you should be fine. I've been flashing new images on top for a while now on this phone and haven't had a issue.
[Verizon Motorola Droid Turbo Android Development] josephpalozzi:
Just mofo flash and wipe cache. Although if you haven't done a full wipe since 4.4, I would recommend it.
[Verizon Motorola Droid Turbo Android Development] janitorjohnson:
This is off topic I know.......but do you notice big battery improvements by donating and doing some of those other wakelocks you listed or not really sure yet?
[Verizon Motorola Droid Turbo Android Development] savagebunny:
It's pretty much been self-maintained. I donated when I was running my Galaxy S3 which was a god damn plague of wakelocks which helped out a metric ton for battery life. My device stats shows it has stopped some wakelocks. Which is always good. I don't run a ton of stuff in the background. I only turn on stuff when I need it (now I leave auto-sync running since I have it set to a different refresh time).

I can't tell you that I've had a massive increase in battery life, but it's the small things. Try it out and see how you like it. I originally got it for the 3 big offenders, the NLP wakelocks.

I only got it setup the other day, so I'm gonna run it for a few days, and I'll post results. I just got done de-bloating a image for myself, gonna upload the new bootanimation for anyone that wants to bake it in
[Verizon Motorola Droid Turbo Android Development] Slartibartfast_:
Do you mean a silent one? I would love to replace the original animation. Will we be able to flash it or would we have to add it to a full image and then flash everything?
[Verizon Motorola Droid Turbo Android Development] savagebunny:
Yup, the very minimalistic one. I'm trying to get it ATM.

Nope, you're gonna have to add it to a full image and flash it :/. No recovery flashes with this phone
[Verizon Motorola Droid Turbo Android Development] Slartibartfast_:
Much appreciated. I wonder why CF didn't include it in his image. I think he did for the 4.4.4 images.
[Verizon Motorola Droid Turbo Android Development] savagebunny:
I'm unsure. I mentioned the reasons in my posts way above. It was more of a rush upload stable image for the community.

Funny thing is about the boot animations, they are .mp4 videos. 1080x1980 @ 5.5-6MBps bit-rate. If I'm understanding it correctly, I can make whatever video I want into a boot animation lol
[Verizon Motorola Droid Turbo Android Development] Slartibartfast_:
Makes sense. After waiting so long for LP I definitely appreciate the speed in which the community released working mofo images for it.

And yeah, it would be cool to use a short video from the bluray of your favorite band or something like that!
[Verizon Motorola Droid Turbo Android Development] Metfanant:
Apologies if this has been covered...but is it normal for the notification "shade" to not cover the whole notification bar when in landscape?
[Verizon Motorola Droid Turbo Android Development] savagebunny:
You mean that small dark bar in between the WiFi notification and the date box element?
[Verizon Motorola Droid Turbo Android Development] Metfanant:
Nah, the notifications themselves when you pull down...where it says "connected to TWC WiFi" I could have sworn in KK that it stretched across the whole screen