yashsingh1/xdaforums huggingface dataset:
[X 2014 Android Development] JulesJam:
But this issue never occurred on 5.0 and MoFo.exe hasn't changed. The issue may be that the cache needs to be reformatted for 5.1 and wiping it isn't good enough. If Mofo is using the fastboot erase cache command that may be the problem.

The issue only occurs when flashing 5.1 images using MoFo. It did not occur when we were flashing 4.4.4 and 5.0 images using MoFo. And my copy of MoFo.exe is the same.

---------- Post added at 09:44 AM ---------- Previous post was at 09:40 AM ----------

From all I have read, the fastboot erase cache command is problematic. It doesn't reformat /cache. I think that is the problem - mofo.exe is using the fastboot erase cache command. It wasn't a problem on 4.4.4 and 5.0 but it is a problem on 5.1.
[X 2014 Android Development] Haxxa:
Could I request a patch please for the following :)

- Debloat based Image

- Xposed Included

- CF.lumen Included

- CM's AudioFX Included

- CM's Trebuchet Launcher Included

- Viper4Android Included

(Basically, all extras with bloat apps removed),

Thanks - Haxxa
[X 2014 Android Development] mikeoswego:
AudioFX and Moto Audio Effects are not compatible with Viper. Attached is your patch minus the AudioFX inclusion.
[X 2014 Android Development] Haxxa:
Thank You so much! Also out of interest how come patch files don't stack - I get a checksum mismatch on attempt? After trying CM Launcher and CF Lumen I ultimately chose to for-go them, and stick to just Viper and Debloat but when I attempted to create an image based from two patch file ( 3.1f--3.1f-v4a.patch & 3.1f--3.1f-de.patch) it failed. :/

In any case thanks so much for many quick updates, really advancing experience well beyond what Verizon ever offered and allows me in Australia to disable Verizon Sim and other CDMA warnings! :D
[X 2014 Android Development] terminal5527:
I apologize for the noob question, but can I still flash the rooted 5.1 image if I I already took the 5.1 OTA? I'm unrooted with a locked bootloader and took the update a while ago. I just want to root and get Xposed on this. Thanks in advance!
[X 2014 Android Development] AlienZombieEater:
Unfortunately, you're SOL. The method used by Mofo to achieve root was patched with 5.1.
[X 2014 Android Development] mikeoswego:
It's not that it needs to be formatted. There needs to be certain files and folders in the /cache directory for the the 5.1 recovery to function. Perhaps the 5.0 recovery did not need those files and folders or maybe it had the ability to create them if not existing. So, you're correct that Mofo hasn't changed but apparently the recovery has changed. In any event, there is just no reason to go into recovery aside from certain very rare situations and that should be removed from your noob guide if it is still in there.

Over the years, I've heard people talk about wiping the dalvik 3 times or the cache 3 times and all of those ideas are, well, nonsense. An erased /cache is just as good, no it is identical to a formatted /cache. In both cases there is nothing there. The fastboot erase command is not problematic, it does exactly what is needed by getting the garbage put there by the mofo flashing process which would probably cause even more problems since /cache would be completely full if it wasn't erased. It is only our expectation that the Motorola 5.1 recovery image is going to work like a custom recovery. The stock recovery is really just there to execute an update script found in /cache/recovery automatically and a last resort means to do a factory reset. Sure the format cache option is there but Moto was anticipating invalid data being stored there, not all the normal folders being stripped out and that formatting does not restore the folders and files in /cache; that part is in one of the init scripts when the phone first boots to create them if they don't exist.
[X 2014 Android Development] Haxxa:
Ok, Wow I didn't realize how tedious of a task it was, just more props to you for spending all this time on it. It sounds symlink if achievable would be the way to go, as it would make it much simpler both in terms of your maintenance and in terms of flashing patch files for new users. Furthermore, you could possibly automate this process on a linux server, with a deploy like affect (if you still needed to use xdelta or something disk intensive) for example it could build an image upload and repeat and this could be left running and simple changes could be made remotely (VPS)? Saving you the hassle of dual booting and any changes would not be so tiresome. Then again I'm not familiar with the workflow involved, but anything to save tedious tasks would be great long-term for both your own sanity and for ease of deployment. But once more, I must give my sincere appreciation, this Rom is great and is made great by your dedication, Thank You for your time and your effort.
[X 2014 Android Development] Aroch925:
I'm having trouble switching to iOS emojis. When I try to copy that iOS font file to the one in the /data/data one, it doesnt copy over the file, it just adds it to the /data/data folder. So I tried just adding the iOS one and deleting the original one but that didn't do anything and when I rebooted the file just came back. I'm using ES File explorer. Maybe I just dont know how to use it well enough
[X 2014 Android Development] mikeoswego:
I plan to automate this process in the next release..

After you copy the file using ES file explorer and delete the /data/data/NotoColorEmoji.ttf file, rename the newly copied NotoColorEmoji.ttf.iOS in /data/data to NotoColorEmoji.ttf then reboot
[X 2014 Android Development] Aroch925:
It worked! Thanks!
[X 2014 Android Development] mikeoswego:
At this point, I'm just a few steps away from creating the various requested versions/patches automatically. For now, I just browse the web or whatever while 7zip does its' thing, etc. After my recent debacle with both of my Win systems barfing on the Win10 upgrade, I'm tempted to ditch Windows completely. On my dual boot box, everything is the same on both sides. I use Chrome which syncs the bookmarks on both sides. Thunderbird for email accessing the windows side mail store while running it in Ubuntu. I might switch to a money manager that works in both Windows and Thunderbird like GnuCash.

Anyway, I've made headway on symlinking the cf.lumen and viper files and that will drop the number of patches need to 1 again and then it will be easy to have occasional updates with new GApps, Xposed versions, stagefright patch, etc.
[X 2014 Android Development] AlienZombieEater:
I couldn't find all the apps listed in your debloat list but didn't see too much of a difference. I tried to keep all the same apps I had in my debloated version.

V3.1f full image (with CF Lumen) on Google Now launcher: 46406 average, 46785 was the highest. One run was significantly lower than the others, dropping the average.

V3.1f full image (with CF Lumen) on CM Trebuchet launcher: 46772 average, 47326 was the highest.

Again, I wasn't able to freeze all the apps that were debloated but these numbers are only about 1.5% lower than the debloated runs I did. I doubt that anyone would actually notice a difference.

I think after all these runs that it's safe to say that the Moto X does perform slightly better with the Trebuchet launcher. The user experience - runtime is pretty much the same but the multitasking scores significantly better with Trebuchet.
[X 2014 Android Development] JulesJam:
But when I first flashed the 5.1 system along with 5.1 logo, kernel and the radios but not the 5.1 recovery, the same exact thing happened - blinking dead android. And if there needs to be certain files in /cache for the 5.1 recovery to function, MoFo writes to /cache and it isn't writing those files. My 5.1 recovery works fine as long as after I flash I boot into system first. After that I can boot into recovery any time I want to and it works fine.

---------- Post added at 07:32 PM ---------- Previous post was at 07:29 PM ----------

Ok well then that explains it - when you boot into system first, the files are created. Then later you can boot into recovery fine. But what you can't do is boot into recovery first after flashing to 5.1. I will update the noob guide but this is only an issue in 5.1, it was not an issue in 5.0 or 4.4.4.
[X 2014 Android Development] braves10:
Unfortunately, BLANK has stopped.

So I tried to flash v3.1f over the original 5.1 img (from July 5th) and upon boot I'm bombarded with a multitude of apps force closing. Also, when it was building the cache on initial boot it didn't list the normal amount off apps (59 instead around 194). Surely I missed a step. Sorry if it's a simple fix. It's been smooth sailing with MoFo and getting to Lollipop for me thus far.
[X 2014 Android Development] drewski_1:
pretty sure this is from the update of some of the /system apps so you'll need to delete contents of /data/dalvik-cache/ and reboot so everything rebuilds.
[X 2014 Android Development] redwings73:
I still get FC's when I try connect the Connect Chrome extension to the Connect app.... Can you explain how you got it to work?
[X 2014 Android Development] mikeoswego:
Interesting numbers. Thanks for putting that together!
[X 2014 Android Development] mikeoswego:
Did you go into Settings->Apps->All, find the Connect app and delete the cache and data? Cleared the dalvik-cache? It does work here without any special steps.
[X 2014 Android Development] drewski_1:
delete contents of /data/dalvik-cache/ directory and reboot.

though currently i'm having trouble connecting to the Chrome Extension, there are no longer FC's
[X 2014 Android Development] mikeoswego:
Yeah, I was never in the recovery more than once or twice while I was on 5.0 (and sorely miss TWRP from previous phones!) I have encountered the dead android more than a few times in testing with 5.1 though!
[X 2014 Android Development] JulesJam:
the dead android is normal, it is the blinking dead android that is the problem.
[X 2014 Android Development] redwings73:
Thanks. I've deleted those, too, which stops the FC's, but still won't allow a connection to the Chrome extension.
[X 2014 Android Development] mikeoswego:
Yes, like I described in the write up for getting the CF.lumen files by deliberately breaking recovery.
[X 2014 Android Development] mikeoswego:
Try this: http://forums.androidcentral.com/moto-x-2013/385042-moto-x-motorola-connect-not-working-3.html#post4142723
[X 2014 Android Development] redwings73:
Will do when I get back home.... Let you know how it goes.
[X 2014 Android Development] Sleeperxr:
Does it work for the XT1092?
[X 2014 Android Development] mikeoswego:
The XT1096 is a Verizon phone and this rom is probably not compatible with the XT1092 (but I'm willing to be proven wrong on that.)
[X 2014 Android Development] Aroch925:
Every time I reboot some of my system apps are deleted (chrome, Google plus, Google wallet)
[X 2014 Android Development] mikeoswego:
It's not actually possible for any of the system apps to be deleted since the file system is read only. You probably mean that they are not showing in your app drawer.

Are you using the debloat patch? Is it only the 3 you mention that have this happening? Do you restore them be going to the playstore?

Presuming this is the case, before going to the playstore to restore them. Go into Settings->apps. Swipe the applist to your left and see if there are any disabled apps listed in the furthest right hand page. If you find any of those 3 in the disabled list tap on each one and select enable.

If this is not the case please use your root file explorer to find the file /data/system/packages.xml and copy it to your Download folder (/sdcard/Download) and send me a copy of it either by attaching it to a post here or via pm.
[X 2014 Android Development] mikeoswego:
< Deleted for now >
[X 2014 Android Development] Haxxa:
I was sent into recovery a couple of times when booting after flashing, was getting quite nervous. Forth boot worked without issues. Is this the reboot procedure?
[X 2014 Android Development] mikeoswego:
No, that isn't normal. It should have shown the boot logo, buzzed like normal and 2 seconds later, before the boot animation started, went black and started all over again. Then continuing on like normal.
[X 2014 Android Development] Haxxa:
Hmmm.... odd normally as you say it kicks to boot logo and it should have followed procedure - this time it went straight to recovery (like no bootlogo - very quick) - maybe something went wrong and was one off? In any case probably just something odd happened on my end...
[X 2014 Android Development] drewski_1:
tl;DR - is it the logo.bin that is the boot animation?

------------

Full Story: after my phone shut down while i was taking a picture, i thought it had just crashed so i rebooted. it booted normally and then fizzled out when i entered the OS b/c of battery @ 0% . . . must not have been paying attention to any low battery warnings.

upon charging for a bit and next reboot my phone rebuilt my Dalvik and then all i could get was Black Screen.

phone was on (holding power brought up the "power off" dialog). other things seemed to have gotten reset in my low/no power debacle because i could no longer connect via ADB to try and reset the Dalvik.

re-flashing the 5.1-3.1f,img didn't help.

so i went back to 5.0 stock and re-mofo'd to 5.0 rooted and deleted /dalvik and then did the upgrade to 5.1

long story short, things are working AOK (though i did lose some data with the return to stock), but i have the old Boot Animation. i thought all the 5.1 prep steps looked good in fastboot, but is this the Boot Animation replacement? if so, i'll do that again

fastboot flash logo logo.bin

if not, how to get the current animation installed?

longer story short - DON"T LET YOUR BATTERY DIE and if it does, charge before attempting a reboot.
[X 2014 Android Development] mikeoswego:
Is it possible that you accidentally changed the menu selection in the bootloader menu with the volume down key before hitting volume up to choose your selection?
[X 2014 Android Development] mikeoswego:
This was on 5.1f not the 5.1g from earlier this morning?

The boot logo is that first light blue M logo that appears immediately, then the boot animation is loaded. The boot animation with the blue & yellow threads was in the /data/local/moodle directory and would be lost if there was a factory reset or /data was wiped. I do not have a copy of that since I did a factory reset a couple of weeks ago to test something. If anyone would pull that file (/data/local/moodle/bootanimation.zip) and post it here, that would be great.

BTW, I have an idea on how to safely install & test run new boot animations for the next version and there is also a copy of the stock animation in the phone without the Verizon logo part that I'll change to be the default.
[X 2014 Android Development] drewski_1:
this happened on Tuesday and was 5.1f
[X 2014 Android Development] tbacba:
So I noticed this morning while I was talking to someone on my phone that I couldn't check the web while on the call. It gave me a message something like "data not available during call". Since I mofo'd this phone pretty much right after I got it, I don't know if this is normal or not. Does stock 5.1 not allow data anymore when on a call? Thanks.

Tbacba
[X 2014 Android Development] mikeoswego:
The first gen Moto X would do voice and data at the same time. The 2nd gen will not (at least on Verizon.)
[X 2014 Android Development] Haxxa:
Doubtful as it happened after I flashed again with same outcome, but its possible. Also exciting news bootloader unlocked - https://twitter.com/firewaterdevs/status/631874466407059456 .
[X 2014 Android Development] redwings73:
That's great news!
[X 2014 Android Development] Haxxa:
Somewhat... It's by sunshine team so it will cost $25 USD, so I won't be going ahead unless this rom changes to zip package mechanism or big benefits arise.
[X 2014 Android Development] mikeoswego:
That's interesting. Having TWRP and the ability to make backups would be nice!
[X 2014 Android Development] jrbmed08:
Bootloader unlock for custom recovery, backups, and removal of write protection would be awesome. I've never felt the desire to run a custom ROM on this phone, but I'm excited by the idea of flashing a ROM to get the latest version of Android once Motorola eventually stops giving us updates.

Also, hopefully Sunshine will be a good option for the people who took the 5.1 OTA and haven't been able to use Mofo, although I don't know if 5.1 will be supported.
[X 2014 Android Development] tbacba:
OK thanks, but what a stupid move. Taking away functionality? Only Verizon!
[X 2014 Android Development] jrbmed08:
It's actually not Verizon's fault. The Moto X 2014 only has one antenna, so it's actually Motorola's fault. What is Verizon's fault, however, is not giving us VoLTE, which was promised to us for months and would fix this problem.
[X 2014 Android Development] redwings73:
Looks like it's official: http://xdaforums.com/showpost.php?p=62329562&postcount=3847
[X 2014 Android Development] GatorsUF:
So I am probably not the only one looking so I will ask. What is a good image to flash so we can use sunshine bootloader unlock? I am currently running a 5.1 img with xposed and likely a lot of other addons. Is there a stock base image that has no additional addons we can use for sunshine? Obviously root would be necessary.
[X 2014 Android Development] jrbmed08:
I'm thinking one of the older images that required a patch to insert xposed. They should probably still be up on the android file site?
[X 2014 Android Development] joshnat:
Good question. Looks like SunShine won't run with Xposed installed, so we would probably have to roll back to one of the versions for which there was an Xposed removal patch.

That being said, I wonder if we can use other devices' roms on the XT1096? The radios are definitely different, so until some devs start cooking up custom roms for our VZW device, it may not be of much use. Except for nandroid backups, of course. What MikeOswego and JulesJam have done for us with Mofo can't be appreciated enough!
[X 2014 Android Development] GatorsUF:
So I am testing this img right now....booting up.

---------- Post added at 03:25 PM ---------- Previous post was at 02:50 PM ----------

So bad news, that IMG doesn't work either... But it got closer.

---------- Post added at 03:26 PM ---------- Previous post was at 03:25 PM ----------
[X 2014 Android Development] jrbmed08:
We might need to roll back to 5.0?
[X 2014 Android Development] Aroch925:
Yeah I tried the earliest 5.1 .img and it didnt work either
[X 2014 Android Development] jrbmed08:
And if there's nothing on 5.0 with root but not xposed, we can revert to 5.0 stock and try kingroot.
[X 2014 Android Development] Aroch925:
Can we just flash an old 5.0 image or is there anythin special we need to do first?
[X 2014 Android Development] mikeoswego:
Either of the two images here:http://xdaforums.com/showpost.php?p=61672409&postcount=37 should work. My images are based from these and the first one is bone stock, the second only has the build.prop edit for tether.

These are 5.1, you should be able to mofo flash them, run sunshine, then flash whatever 5.1 image you want afterward.
[X 2014 Android Development] Aroch925:
Are both of these images rooted? Sunshine says it requires root to work
[X 2014 Android Development] mikeoswego:
I don't think you have to be rooted and in their FAQ it says that just unlocking won't root your phone. You have to install TWRP, which will install root for you. (Or just flash an image that has root already.)
[X 2014 Android Development] redwings73:
I think you might have to be rooted, if I read this correctly: http://xdaforums.com/showthread.php?p=62329562
[X 2014 Android Development] GatorsUF:
You do have to be rooted to use sunshine, I tried the bond stock rom and it is not rooted thus it didn't work.

[MENTION=5849464]mikeoswego[/MENTION] any chance you could make a bone stock 5.1 img with just root?
[X 2014 Android Development] drwhitney:
Has anyone tried [MENTION=2278321]btdownloads7[/MENTION]'s 5.0 root+tether only img? This was one of the first rooted 5.0 mofo images, if I remember correctly.

http://xdaforums.com/moto-x-2014/development/img-xt1096-victara-lollipop-images-mofo-t3100601

---------- Post added at 09:54 PM ---------- Previous post was at 09:48 PM ----------

Are there any risks in flashing back to a 5.0 image when we've upgraded our modem, etc to the versions that came with 5.1?
[X 2014 Android Development] GatorsUF:
I have not tried this, but I'm curious if you need to flash all the other files to go with it (modem, vector, recovery etc..). If so where do you get these files.
[X 2014 Android Development] jrbmed08:
The Sunshine app has been updated and now works on our images. I'm now unlocked! Give it a try.
[X 2014 Android Development] JulesJam:
So will Sunshine work on any rooted MoFo image?
[X 2014 Android Development] redwings73:
Sunshine worked for me.... I'm on Mike's 3.1f image.
[X 2014 Android Development] Haxxa:
+1 - Worked with no hassle - going to flash logo.bin to remove bootloader unlock message now...

---------- Post added at 02:47 PM ---------- Previous post was at 02:30 PM ----------

Installed TWRP successfully - ignore mismatch error f you install via fastboot - "mismatched partition size" is nothing wrong, it is basically just saying, that the TWRP image is smaller than the stock recovery one.
[X 2014 Android Development] mikeoswego:
Yes, it worked for me with the rooted/xposed image.

You'll have the unlocked bootloader warning at boot. Here is the fix for that: http://xdaforums.com/moto-x-2014/general/warning-message-unlocked-bootloader-t2871478

The playstore install of TWRP doesn't work so it has to be installed manually. Here is the TWRP page for our phone: https://twrp.me/devices/motorolamotox2014.html

The link for the actual download of TWRP 2.8.7.0 is here: https://dl.twrp.me/victara/twrp-2.8.7.0-victara.img.html
[X 2014 Android Development] JulesJam:
Thank you!
[X 2014 Android Development] jrbmed08:
Thanks, the logo flash worked great, but when I tried to flash TWRP, it said "mismatched partition size." Any idea what I did wrong?

Edit: Despite that warning, it actually works fine, so I guess there's nothing wrong.
[X 2014 Android Development] mikeoswego:
Yes, I forgot to mention that there would be that error message and that it can be ignored.

I'm working on getting /system to be automatically r/w without any apps needed. For now, if you want to set it r/w until the next reboot you can go into adb shell or terminal on the device and enter su, then "mount -o remount,rw /system" (without quotes.)
[X 2014 Android Development] Aroch925:
Ok so some questions since the bootloader can be unlocked now. I want to put cyanogenmod 12.1 on my phone now but when I tried earlier today it said my sim card could not be detected. I tried multiple different builds and after some googling I found out that I need to update my bootloader and radio. I googled around and I couldn't find where to download these things. So how would I go about doing this stuff? Would updating my bootloader relock it? Where do I find the files to download? Any suggestions would be great. Thanks!
[X 2014 Android Development] Haxxa:
Ok, so your missing something here mate the two phones Moto X XT1096 (Verizon Version) and the Moto X Pure XT1095 (Pure Edition) are not the exact same phone, the Verizon version uses a CDMA/GSM Radio which is completely different to the one found in the pure edition (GSM Only). For this reason alone current Rom's will not work with the Moto X XT1096, nothing you will do can fix this, you'll need to wait until a build of CM12.1 is compiled with the necessary drivers for the CDMA radio.

The fact that the rom even booted is quite impressive, but for now you'll need to wait until rom development kicks off with support for the CDMA radio.

PS: On a further note, flashing your bootloader is very dangerous if you don't know what your doing, please refrain from flashing it or you will likely brick your phone. The issue with CM12 has nothing to do with the bootloader.