yashsingh1/xdaforums huggingface dataset:
[Verizon Motorola Droid Turbo Android Development] sovrce:
1 - Could you explain this a bit more? Although.. disregard ENTIRELY if the answer to my #2 is "no, you can't"....

2 - I went back to 1.2A-Base without V4A specifically because of this - the constant problems. That said, here's my question: Could we install V4A somehow and get it to work even if we installed the regular 1.2A Base IMG? (either way.. his statement here, in my relatively extensive experience, is 200% true. i just spent the last two solid days trying to get the 1.2A-Base+V4A IMG to work and it just kept crashing over and over and over, no matter what i tried or changed.)

3 - Very, very, VERY important. I'll post edited instructions from his HowTo file because, in my confusion, I messed up when flashing 1.2A+V4A and, if you read above, it caused a 48 hour headache. So, if it's OK for me to post this here, ComputerFreek, these are the steps I'd follow..

Step 1:

Left-click inside of the folder where the logo.bin, boot.bin etc files are located, then SHIFT+Right-click, click "Open command window here" and run these commands:

fastboot devices (if you see "SERIAL NUMBER HERE" followed by "FASTBOOT", your ADB is stable and ready to run the following commands...)

fastboot flash logo logo.bin

fastboot flash boot boot.img

fastboot flash modem modem.img

fastboot flash mdm1m9kefs3 fsg.mbn

fastboot erase mdm1m9kefs1

fastboot erase mdm1m9kefs2

fastboot flash recovery recovery.img

fastboot erase ddr

fastboot erase cache

fastboot reboot-bootloader

Step 2:

Flash the system image you've selected with MOFO (youtube.com/watch?v=AXAYjbf76II for a guide. it'll be slightly different this time around, but you'll get the idea)

Step 3:

Enter recovery and wipe cache.

(personally I've never been able to do this after a successful image flash, so I just run "fastboot erase cache". you'll almost always get stuck with the "blinking android icon" if you try to boot straight into Recovery Mode and will be unable to do much from there)

Step 4:

After you've cleared the cache, reboot.

4 - Wiping data and cache (personally I did each 3 times, 3rd time's a charm ;)) is VITAL to making things work smoothly and, ultimately, avoiding having to run the WHOLE process over and over from square one after you've got everything installed and set up. Trust me.. I've now had to restart/reinstall/customize everything FIVE TIMES and it gets increasingly more annoying everytime!

Thanks for everything, ComputerFreek. I now feel like I have a brand new phone capable of doing pretty much every single thing I'll ever need a phone to do. Newer processors, hard drives, GPUs, RAM.. they'll all come and go, but as it stands, I honestly can't think of anything I'd pay another $700-800 for (I have to buy off contract to keep Unlimited 4G) just to have access to. I'm a "power user" but don't do much gaming or anything graphically intensive so... I think I'm gonna skip the 2015, 2016 and possibly even 2017 models, thanks in no small part to you!

Take care man :)
[Verizon Motorola Droid Turbo Android Development] siegesoldier:
Would you consider creating a pure build without v4a? or allowing the editing of APNS in all of the builds?
[Verizon Motorola Droid Turbo Android Development] haevolution:
Whoops I didn't do this step went right from 4.4.4 to 1.2a and only flashed the modem that was in 1.2a. What should I do now?
[Verizon Motorola Droid Turbo Android Development] Ungo:
Posted this in the Q & A thread but I made it over 10 posts so I moved it here....

Finally made the switch from your KK rom to the LP rom. Love it and installed it with zero issues. My WIFI lag that I've had since I purchased the phone is finally gone as well. I forgot how fast home wifi can be since I've lived with the problem so long.

Only weird issues I noticed is after I installed Adaway and changed the settings it didn't work right away. I messed with it for about an hour, reinstalled it, tried wiping apps cache that had ads, but nothing worked. Gave up and went to bed. Six hours later when I picked my phone back up it was working. Thought that was strange.

Also, I froze Google Hangouts with TB. I've noticed every 4 hours or so I'll get a window that pops up saying "hangouts has stopped". Not sure what is trying to make GH run but I've been tinkering with it to find out.

Anyway, just making a post to say good work and so if others have similar problems with Adaway to maybe give it a few hours after install so it settles in.

---------- Post added at 02:23 AM ---------- Previous post was at 02:15 AM ----------

Just "start over". Not sure how far you got in the process but factory reset and wipe the cache of your phone in the recovery menu. Flash all the files from 5.1 zip, one by one, the download is on the 2nd post about coming from KK to LP. You don't need to flash the actual 5.1 image rom though. Then flash all the 1.2 files, one by one, located in the new download. There is a readme file located in 1.2a. Open in notepad and...read it. Make sure you flash ALL of those files and in the order he has them in. You can actually copy and paste each command if you want. Each new command starts with "fastboot".

After you do that flash the image and make sure you do another factory reset and wipe the cache one more time before booting the phone up. If you did it right the phone will start up and start saying "initialing applications" or something of that nature and go through about 200 files.
[Verizon Motorola Droid Turbo Android Development] haevolution:
I got all the way through and everything seems to be working fine. That's why I'm wondering if I need to flash the 1.1 modem updates that were included in the 1.2a version.
[Verizon Motorola Droid Turbo Android Development] Ungo:
If backing up your data and apps isn't too much of a pain for you I would start over to be safe (I don't mean going back to KK or anything). Just factory reset and clear cache again, reflash everything in order from the 5.1 zip file except the actual rom image, then flash all the 1.2 files in order of the readme file, then the 1.2 rom again. If you don't I imagine you'll probably start to get random bugs, crashes, and apps not working right. Or you could start running into problems once this rom starts getting up to higher versions.
[Verizon Motorola Droid Turbo Android Development] smokeydriver:
Wow...this is awesome. So I did look at #1 previously but didn't read it enough. I'll read it carefully first thing tomorrow. 2- Thanks! 3- I've watched this video a few times and I'm confident I can knock that out easily once I hop back to #1. 4- Check. 5- I'll try to follow these directions after everything else is done. It's really weird but the 'Instructions' are different when I pull them up on my phone versus on the computer. I've never seen that before. If I have questions, I'll hit you up. THANKS!!!
[Verizon Motorola Droid Turbo Android Development] liquidthc:
I'm getting the same error but only in HDR mode. I get it on Google camera and the stock camera.
[Verizon Motorola Droid Turbo Android Development] GeoFX:
I'm getting errors when turning on HDR mode using the stock camera. Running 1.2A. Tried wiping caching and installing Google Camera as suggested by another poster but neither of those work. Can anybody else replicate this? Don't use Auto HDR but switch it to "On" before snapping a pic.
[Verizon Motorola Droid Turbo Android Development] Ungo:
Well if you just received a brand new Droid Turbo you have to see if its running KK or got the Lollipop update. If its still on KK go to Computerfreeks KK rom thread, use mofo and follow all the instructions to flash the newest version of his KK rom (just pick one of the first two), let it boot up and settle for awhile. I wouldn't bother installing any apps or anything just to save any potential headaches later. After doing that go to Computerfreeks LP rom thread and read the first two posts carefully. Then flash the 5.1 files that are in a zip file near the bottom of the first post, then flash 1.2A's files, then the actual 1.2A rom image.

Make sure you read everything carefully a few times before flashing since it is a little different then "normal" flashing people are used to. And all the threads say multiple times to wipe the cache! Don't forget that. It is one of the most important steps after going from KK to LP or you will have a load of problems.

If your phone came with LP then...you are screwed. Try to return it and get one with KK still on it.

---------- Post added at 03:51 AM ---------- Previous post was at 03:28 AM ----------

Hmm. I just tested it. Running 1.2A as well. When I turned HDR ON and took a picture, it stalls. The picture is saved to the gallery but the camera becomes unresponsive and you have to close it to use it again or wait 30 seconds or so and it asks you to restart the camera. I noticed if you close the camera and open it again in a few seconds it still is unresponsive. If I wait a minute or so and reopen it I can take another picture.

I also tried the Google Camera thing and it didn't fix it for me either.
[Verizon Motorola Droid Turbo Android Development] computerfreek274:
I am looking into finding a fix for HDR. But for now you just have to find a work a round that works for you.
[Verizon Motorola Droid Turbo Android Development] Ungo:
Sorry I didn't mean that to come off like a complaint. Was attempting to recreate the problem for another user. I honestly have zero idea what HDR does...I never even changed that setting until today. But anything with HD in the title is good. That's what advertising has taught me anyway..
[Verizon Motorola Droid Turbo Android Development] haevolution:
All of Computerfreek's versions are on android file host you just have to go back a level to find the older versions.

Hopefully it's ok to share this link directly on here:

https://www.androidfilehost.com/?w=files&flid=32218

This is for all the versions including 1.1.
[Verizon Motorola Droid Turbo Android Development] someguyatx:
So I just got my turbo yesterday and it was on 4.4.4 out of the box! so I bought mofo and put on the Computerfreek kitkat image and ran kitkat for the rest of the day. Last night I followed the directions upgrading to 1.2Abase and once I got tho this step

"Once that finishes, you want to try to boot the phone. Select Boot to System from the bootloader and then go grab a snack - chances are, it will sit at the Motorola boot screen for some time. After about five minutes, press and hold power to turn the phone off. "

My phone actually booted right into lollipop after about 5 minutes. I tried rebooting into recovery several times to wipe cache and factory reset but couldn't even get there so I just did a factory reset from lollipop and configured. For now everything seems good to go but is there some sort of trick to get into recovery or did I mess up something in the process? I was able to get into recovery before upgrading by holding down vol Up & pressing and releasing power button but that didn't work. I tried every combination of Vol up and power I could think of with no luck.
[Verizon Motorola Droid Turbo Android Development] computerfreek274:
Go to the bootloader! Then select from the bootloader menu with VOL up or down find recovery and tap power.
[Verizon Motorola Droid Turbo Android Development] smokeydriver:
Ok. So now that I'm on 4.4.4 quark unrooted, I just run Mofo but at the step to install the ROM, I install 1.1A? Then I can move on to the beginning of this thread?
[Verizon Motorola Droid Turbo Android Development] someguyatx:
Thanks I should have mentioned that I did that and got to the dead android screen then just couldn't get into recovery no matter what combo of Vol Up and power I tried.
[Verizon Motorola Droid Turbo Android Development] firstEncounter:
Data wipe isn't required, but recommended for best battery life/performance.
[Verizon Motorola Droid Turbo Android Development] JakeDHS07:
So rooted 5.1 and instructions for flashing have been posted. But I want to stay loyal to CompFreek and his awesome images and content so hopefully we can get a 5.1 of that soon.
[Verizon Motorola Droid Turbo Android Development] janitorjohnson:
And you can do that....flashing one image from another and then trying another will not cause hard feelings I'm sure. CF would want us to be happy. :)
[Verizon Motorola Droid Turbo Android Development] JulesJam:
The 5.1 rooted images that have been posted don't do much for you as write protection is NOT disabled. They are just starting points pretty much.
[Verizon Motorola Droid Turbo Android Development] JakeDHS07:
No different than the 4.4.4 builds have been.

---------- Post added at 12:30 AM ---------- Previous post was at 12:30 AM ----------

Wait you mean ENABLED right??? They didn't actually manage to disable wp did they?
[Verizon Motorola Droid Turbo Android Development] JulesJam:
Forgot the NOT.

You would have to unlock the bootloader to disable write protection.
[Verizon Motorola Droid Turbo Android Development] JakeDHS07:
Lmao yeah I figured. You had me for a second. I was like HOW DID I MISS THAT!?!?! LMAO
[Verizon Motorola Droid Turbo Android Development] siegesoldier:
Image still uploading? Folder shows empty for me. Thanks for all the hard work [MENTION=6076132]computerfreek274[/MENTION], mattlgroff, and firstEncounter!
[Verizon Motorola Droid Turbo Android Development] nishant.gaidhani:
anything for xt1225

Do you also plan to release this for xt1225 which is moto maxx?

I'd love to see that.

Thanks,

Nishant
[Verizon Motorola Droid Turbo Android Development] computerfreek274:
Just out came out of anesthesia after a procedure so when I get home I will be working on it all day.
[Verizon Motorola Droid Turbo Android Development] GSUS969:
You are allowed to take time to recover - we can wait! :good:
[Verizon Motorola Droid Turbo Android Development] computerfreek274:
Thanks but they told me to rest so I am resting. the 1st img is uploading now with the system imgs if you guys need it. V4A build is what i am working on now and 493 dpi. but v4a on lollipop is not liking v4a right now. tell you the 1st img that is going up it has it all busybox root xposed adaway and some killer tweaks. you guys are going to love it. it is flying. I did have to do a full system wipe as the phone did not boot without it. So please backup your data.
[Verizon Motorola Droid Turbo Android Development] GhostRider5666:
Can't wait for lollipop but take your time.
[Verizon Motorola Droid Turbo Android Development] Coronado is dead:
So, this wipe. You did the Data wipe that is in the recovery above cache, right? Not the one accessed through settings? Just want to be super clear :)
[Verizon Motorola Droid Turbo Android Development] Flowah:
I feel like a kid at Christmas. Not a candy store because I don't much care for candy, but Christmas. So excited! Thanks for all your hard work, man!
[Verizon Motorola Droid Turbo Android Development] computerfreek274:
Recovery
[Verizon Motorola Droid Turbo Android Development] Coronado is dead:
You have a link in the OP to the Xposed APK. That link states that it only works with 5.0 and not yet 5.1. I assume you have tested though and that is simply not the case? XposedInstaller_3.0_alpha4.apk is what we should grab, correct?

Thanks again :D
[Verizon Motorola Droid Turbo Android Development] PittAussie:
[MENTION=6076132]computerfreek274[/MENTION]: It has been stated multiple times in other threads that it is necessary to clear the Dalvic Cache and Cache folders before running any other fastboot commands. The main symptoms caused by not clearing those are poor battery life and notification problems. Please add the cache clearing to the instructions.
[Verizon Motorola Droid Turbo Android Development] johnbravado:
after i installed image using mofo i wanted to go into recovery and clear cache just because and the recovery robot just flashed at me. is this normal? or has this been seen before?
[Verizon Motorola Droid Turbo Android Development] soccertolive:
I got the same thing. I went ahead and rebooted with volume down and power and so far so good. I dont have any problems so far. All my apps are there and I don't notice any downside.
[Verizon Motorola Droid Turbo Android Development] computerfreek274:
Go back into it now if you can. When you see the dead Android guy. Do not start clicking like crazy this is a one step thing . dead Android guy! Stop count to 5! Then Hold down power key then hit VOL up. Do this slow and you will be good to go. Unless your VOL up key is not working like the other guy on here. Test VOL up key in bootloader. Also from boot loader you can erase data too "fastboot erase cache" and for data "fastboot erase userdata"
[Verizon Motorola Droid Turbo Android Development] X_man.:
I have been running every new build ever since root. I did a wipe when I first started LP. Every other build has ran great. I actually ran the new build for a couple days. And it ran well. Just had a problem when I had to reboot. I had to try to start it several times before it would finally boot. I would wait about 15 minutes per attempt. And when it finally did boot it ran fine. This wasn't a one time thing mind you. Like I said I had been running it for a while and didn't know about this until installed a xposed app that required a reboot. After that I would run the phone for a while and would reboot every now and then just to see if it would work itself out but it never got any better. I've been doing this stuff pretty hardcore for many years now and I'm well aware of the risk believe me I know all to well from experience ;) It takes a lot to scare me nowadays LOL And btw no prob. I know you didn't mean anything by that. I know how it is and for all you know I could be a newbie lol. So tell me. If I have wiped since KK I shouldn't have to wipe again should I? I may just try again. Maybe something just didn't go right with the flash the first time. It does happen sometimes
[Verizon Motorola Droid Turbo Android Development] smokeydriver:
I hate to be bugging everyone....but is anyone around that can assist me? I've installed MoFo, but I don't know how to get from there to this thread as I believe I need to do something with installing a 4.4.4 ROM first. I have not set up the phone at all yet and would really like to get it all set up instead of getting my refurbished phone set up and then tinkering with it.
[Verizon Motorola Droid Turbo Android Development] X_man.:
Is the phone you are setting up still on kitkat?
[Verizon Motorola Droid Turbo Android Development] smokeydriver:
Yes. I got it refurbished with kitkat. I installed Mofo. That's it...other than that, nothing on the phone.
[Verizon Motorola Droid Turbo Android Development] PerCompLLC:
Based on the info provided it does indeed sound like something might have gone haywire with the flash. I haven't heard of it happening (I figured it is pretty much black or white - either it works or it doesn't), but I'm sure that it could (and probably did). If/when you re-flash from scratch, be sure to fastboot flash all of the radio, recovery and stuff included with CF's zip. I'm not sure that the order matters, but I just copy/past the commands in order just to make sure.
[Verizon Motorola Droid Turbo Android Development] X_man.:
So you dont have the rooted 4.4 image file yet right?

---------- Post added at 02:28 PM ---------- Previous post was at 02:26 PM ----------

Yeah I think I'll just try it agian this weekend. I'll let yall know the results.
[Verizon Motorola Droid Turbo Android Development] PerCompLLC:
And the files and instructions are actually bundled with the 1.2A versions of the CF builds if he is going that route...
[Verizon Motorola Droid Turbo Android Development] X_man.:
Oh yeah thanks.
[Verizon Motorola Droid Turbo Android Development] smokeydriver:
This is just silly. I'm not computer illiterate. But, I know sometimes when you've done something a million times, you forget how a simple step isn't so simple for some people.

I want to flash the radios. I want to flash the modem. And I want to install this ROM. But I can't get the freaking filename in the command prompt. Yes, it's a dumb ass problem, but telling someone 'Flash ASDF' does not tell them how to flash a file. I don't care about the $35, but I don't want you to do it for me. I want to learn to do this.

I do appriciate the help everyone's trying to give me, but it's very hard to understand when 1 person says I need to install another ROM first, another says I don't, another says I need the radio/modem, and another (The OP) says no...skip all that. If it should be skipped, then why does everyone else do it? This is why I asked if I can just call someone so I can get a few questions answered. So, OP, I'll HAPPILY give you the $35. But I don't want it done for me. I want help.
[Verizon Motorola Droid Turbo Android Development] computerfreek274:
Pm me a number I can call you at! Have your phone in bootloader mode and connected to your pc. Open a command windows to all the files unziped in the same folder as fastboot.exe.
[Verizon Motorola Droid Turbo Android Development] roman.ramirez.12:
When you say wipe did you wipe cache and factory reset? Because I know for a fact when rooted or not if you're going from KitKat to lollipop those two things you must wipe cuz it's a completely new system image. I believe it's only the bootloader still KitKat. That being said it does take a while to reboot the first time. If you don't do those two wipes there's no telling what can happen if you can be caught in a bootloop taking fine and then later on down the line give you problems. Also with exposed it's a whole new format for lollipop so not all modules are going to work I don't know the link but there is somewhere on here where you can find which modules work. I would do like CF once said to go back to the app and delete the one that you think caused the problem and see if that fixes it if not delete all modules and start over....Good luck?
[Verizon Motorola Droid Turbo Android Development] X_man.:
Thanks.

I wiped cashe and did a factory reset btw.
[Verizon Motorola Droid Turbo Android Development] newskate9:
DELETED............................
[Verizon Motorola Droid Turbo Android Development] computerfreek274:
DELETED............................
[Verizon Motorola Droid Turbo Android Development] newskate9:
YIKES - that was not my intention - thought I was helping. I DELETED my post. CF, you may want to delete your response to me so no issues are caused.

So sorry if I've caused issues.:crying:
[Verizon Motorola Droid Turbo Android Development] GeoFX:
Is the HDR problem an issue with forcing HDR on in the camera or is it more of a problem with HDR itself not working at all? I usually set my HDR mode to Auto and have no issues but don't know if it's actually doing anything.

Thanks!

EDIT: I flashed the latest stock rooted IMG from First Encounter and the HDR mode works fine. Hope this info helps you debug.
[Verizon Motorola Droid Turbo Android Development] computerfreek274:
Update: I will be posting 1.2B v4a builds this is only a v4a update this is to help with the lag on v4a build. This is not a new ver for 1.2a this is just forv4a users.

My Internet is up and down right now and very slow. So it maybe 5 hours before it shows up. I will keep you updated.
[Verizon Motorola Droid Turbo Android Development] trikotret:
Should I get on the new v4a build even if I don't use viper? Is it better on battery?
[Verizon Motorola Droid Turbo Android Development] computerfreek274:
NO if you do not use or do not care. Then do not run v4a builds.

It is funny I almost put your questions and answers to it be for you posted it. So noone asked.
[Verizon Motorola Droid Turbo Android Development] Koneesha:
Has anyone else experienced what appears to be a memory leak? My phone will be working fine on build 1.2a with V4A the will jut get very sluggish, and eventually restart itself. This has happened maybe about 5 or 6 times over the past couple of days, and I completely wiped the phone before using this build.

Is this related to the stability of the 1.2b image that is about to be released Computerfreak, or does this sound like user error?

Thanks. Just wondering if I need a reflash, or if it could just be the image?