yashsingh1/xdaforums huggingface dataset:
[X 2014 Android Development] mikeoswego:
Open the app drawer, find the Settings icon (the gear), touch and hold until the words "! App Info" appear at the top of the screen, drag the icon onto those words (they'll turn blue), the App Info should open, clear cache, clear data and then see if you can get into settings.

There is nothing wrong with these images and I don't think going back to 5.0 will fix this problem. I think that [MENTION=5983610]JulesJam[/MENTION] went back to 5.0 by just flashing the 5.0 mofo image but I can't find the post right now where that was said. It would be safest to use fastboot to flash the same files listed in post 2 but from the 5.0 image and then mofo flash your 5.0 mofo image.
[X 2014 Android Development] mikeoswego:
Wiping cache from recovery is fine it just takes longer than doing it with a file xplorer. Yes, /cache is in root not in /data.

TotalX used an older version of Xposed (alpha 2.) Did you update your Xposed Installer app to work with the newer version of Xposed (v65) in this image? Make sure you are using this version of the app: XposedInstaller_3.0_alpha4.apk You should just be able to install it over the old version.
[X 2014 Android Development] mikeoswego:
In case someone really wants to downgrade to 5.0 (not recommended), I've posted the set of files from the full factory file set needed to do that. You would delete everything in /data/dalvik-cache and /cache, then use the same fastboot commands as listed in post 2 but with the older files. Then flash your mofo 5.0 image.

Here is the link for the old 5.0 files: XT1096_5.0-Base.7z
[X 2014 Android Development] joshnat:
Thanks again. I have no doubt there's nothing wrong with the images. I just keep digging myself in deeper and deeper, and a return to 5.0 may help me clean the slate to begin again.
[X 2014 Android Development] JulesJam:
The instructions on how to flash back to stock 5.0 system are in the Noob Guide I wrote in General.

http://xdaforums.com/moto-x-2014/general/noob-guide-rooting-verizon-moto-x-2014-t3097375

To flash the rest of 5.0 stock, you enter these commands to flash the 5.0 files:

fastboot flash logo logo.bin

fastboot flash boot boot.img

fastboot flash recovery recovery.img

fastboot flash modem NON-HLOS.bin

fastboot erase modemst1

fastboot erase modemst2

fastboot flash fsg fsg.mbn
[X 2014 Android Development] joshnat:
Thanks, Jules. I tried that but I can't get it to boot. When it boots it shows the newer needle & thread boot animation, then goes black and never gets anywhere beyond that. Now I'm trying to flash a mofo 5.0 image to see if that will work. I've really messed this one up!
[X 2014 Android Development] mikeoswego:
I've added "fastboot erase cache" to my instructions to ensure people have a clean cache. I doubt that recovery would access /data/dalvik-cache but it must access /cache to find update files, etc. Doing the fastboot erasure might be helpful for people who overlook using their file explorer to clean out /cache.
[X 2014 Android Development] mikeoswego:
Add "fastboot erase cache" (without quotes) to your command list when you try again. Or just try that command now if you haven't done anything else.

Added: Looking at your post it sounds like you flashed the 5.0 files but not the 5.0 mofo image, that wouldn't work.
[X 2014 Android Development] joshnat:
I always do fastboot erase cache before and after flashing.

I've reflashed a mofo 5.0 image. I had previously tried to return to stock 5.0 by flashing the sparsechunks, but that resulted in no boot. Now, with the mofo 5.0 image, it's sticking at the boot animation. I'll try another mofo 5.0 image and see if I get different results.
[X 2014 Android Development] JulesJam:
I just did a reboot and now the same thing is happening to me. This is like what was happening to me on the rooted image I made. I thought I had done something wrong when I rooted the image.

I am back into fastboot now and will reflash stock 5.0 and see what happens.

You have to flash 5.0 stock logo.bin too, did you do that?
[X 2014 Android Development] mikeoswego:
If all else fails try "fastboot erase userdata" That will factory reset your device.

If you're still dead, try "fastboot erase customize"

More commands if still dead after those would be "fastboot erase clogo" and/or "fastboot oem fb_mode_clear" but you shouldn't need to do these (and these should be an absolute last resort.)
[X 2014 Android Development] mikeoswego:
Now you guys are freaking me out.. I just did a reboot without problems.
[X 2014 Android Development] JulesJam:
I flashed back everything to stock 5.0 including the 5.0 cache from the fxz, then booted into recovery and did a factory reset and that fixed it. I am going to start from scratch and see if we can figure out why this is happening to some people.

I did a bit of research and there may be a problem with the fastboot erase cache command. It looks like you are better off booting into recovery and wiping cache there but in the end a factory reset through recovery is what fixed everything for me.

As always, people need to back everything they care about up before they do any flashing as there are no guarantees that you won't lose your data.
[X 2014 Android Development] mikeoswego:
Agreed on the backup! I've removed the fastboot erase cache command from my instructions, thanks!
[X 2014 Android Development] JulesJam:
Try doing this if you are still stuck - download the fxz from here (takes a long time):

http://xdaforums.com/showpost.php?p=60330525&postcount=20

https://www.androidfilehost.com/?fid=96042739161892510

Then run these commands using mfastboot:

mfastboot flash logo logo.bin

mfastboot flash boot boot.img

mfastboot flash system system.img

mfastboot flash recovery recovery.img

mfastboot flash modem NON-HLOS.bin

mfastboot erase modemst1

mfastboot erase modemst2

mfastboot flash fsg fsg.mbn

mfastboot flash cache cache.img

Then boot into recovery and do a factory reset.

If that doesn't fix it please let me know. If you don't have mfastboot let me know.

---------- Post added at 08:15 PM ---------- Previous post was at 08:07 PM ----------

I think maybe the issue is that when you erase the cache you need to format it too. When you boot into recovery, it formats the cache. I am not sure when you do fastboot erase cache it formats the cache, so maybe that is the issue?

Idk but when you do a factory reset through recovery you format the cache and the data partition and in the end that is what fixed the issue for me.

I am fully stock 5.0 now and will start again fresh to see how it goes for me. First I will flash a 5.0 rooted image using Mofo and then delete only the /data/dalvik-cache. Then I will patch your base image and flash to 5.1 and then will wipe cache in recovery, which formats it too, and see how that goes.
[X 2014 Android Development] mikeoswego:
I noticed the fastboot erase cache command in the .xml files and thought it might be helpful.

For the record, I've never run fastboot erase cache and the only time I've used recovery to do anything was weeks ago just for testing (I've gone into it once since going to 5.1 to see if I had the same problem you had but didn't use any of its functions.)

For all the flashing I've done during this update and testing for 5.1 (and previously when doing the v65 Xposed update for the 5.0 images); all I ever do is use ES Explorer to delete everything in /cache and /data/dalvik-cache before flashing. No double erasing /cache or entering recovery before or after using mofo to flash an image.
[X 2014 Android Development] JulesJam:
I will try it both ways and see if we can figure this out.
[X 2014 Android Development] mdmogren:
Any chance you could get AirAudio working in this image? I think it's pretty easy, just need a file in system.

Instructions from the app developer are here: http://xdaforums.com/showpost.php?p=60942406&postcount=75

I paid ClydeDroid $20 for getting it working in his image but would be happy to send a few more bucks your direction to have it working with 5.1
[X 2014 Android Development] joshnat:
Fastboot erase customize allowed me to boot into 5.0. So far so good. Since I've already wiped I may flash the fxz anyway to start fresh.
[X 2014 Android Development] mikeoswego:
Another just for the record.. I haven't used mfastboot since the RAZR/Safestrap days. Currently I use fastboot from the Android SDK Tools Only page listed here: SDK Other Download Options on Windows (or fastboot from the android-tools-adb package on Ubuntu.)
[X 2014 Android Development] mikeoswego:
Interesting, thanks for the update!
[X 2014 Android Development] mikeoswego:
That should be easy. What image patch level are you using? I'll make a patch for you to test.
[X 2014 Android Development] joshnat:
Hi Jules, I don't know if I have the right file for mfastboot. It seems to behave exactly like fastboot, but flashing the system.img in sparse chunks...
[X 2014 Android Development] JulesJam:
mfastboot will flash the single file system.img from that fxz I linked to. It does break it down into sparsechunks to do the flash though. As long as it can flash the single file system.img it is fine.

---------- Post added at 09:29 PM ---------- Previous post was at 09:27 PM ----------

Ok well that is done in a factory reset so maybe that was the issue - we needed to erase the customize partition.

---------- Post added at 09:31 PM ---------- Previous post was at 09:29 PM ----------

But regular fastboot won't flash a single file system.img at least not any of the copies that I have found. If you have your system image broken down into sparsechunks, then regular fastboot works. But if all you have is a single file system.img, IME you need mfastboot.
[X 2014 Android Development] mdmogren:
I'm using XT1096_5.1-tether-root-bb-sqlite3-Xposedv65-DeBloat-AdAway.img

Thanks!
[X 2014 Android Development] mikeoswego:
Ok, never tried to fastboot flash the single file system.img aside from mofo. Good to know!

I've not erased my customize partition (yet) so that must be a variable. I wonder what is in there..
[X 2014 Android Development] mikeoswego:
Here are the Air Audio patch files. The one with your username patches the image your using. The other one patches the base image.

I've not tested this so let us know!
[X 2014 Android Development] JulesJam:
It has the custom wallpapers and your custom greeting if you picked one through MotoMaker. Once you do a factory reset, you lose those. It is so stupid b/c if you have a locked bootloader I don't think there is anyway to back up the customize partition. Anytime you factory reset you lose it. Luckily you can find the custom wallpapers online, but you can never get back your custom greeting with a locked bootloader.
[X 2014 Android Development] jrbmed08:
Thanks for the installer - I'll try that. Although deleting those folders and rebooting seemed to do the trick.
[X 2014 Android Development] alexkirsch:
I can confirm if you do not clear cache you will get "No command" flashing; To resolve I simply flashed 5.0 recovery, booted into recovery and cleared cache (with out factory resetting) to resolve.
[X 2014 Android Development] JulesJam:
What happens when you reboot now? Any issues on reboot?
[X 2014 Android Development] alexkirsch:
All is well; after clearing cache I booted into Android.. Restarted into fastboot (via adb) and updated recovery (back to 5.1).
[X 2014 Android Development] mdmogren:
Awesome, thank you! Will try this later tonight. Do you have a Bitcoin address or Paypal?
[X 2014 Android Development] JulesJam:
I was on 5.0 rooted with Xposed and deleted only /data/dalvik-cache. I did NOT delete /cache.

I then flashed the 5.1 logo. kernel/ramdisk, recovery and radios and used mofo to flash a 5.1 image with Xposed and Adaway. I attempted to boot into recovery and I got the blinking Android. I got back into bootloader mode and selected Factory from the bootloader menu and the phone booted but the phone didn't connect to the tower. My apps weren't gone either. I have no idea what that Factory item in the bootloader menu is b/c it didn't appear to be a Factory reset like I thought it would be.

Then I went back to the bootloader mode and booted into recovery and the android wasn't blinking any longer but it still said No Command. I was able to wipe cache through recovery and boot normally then.

So it looks like the best course of action is to delete both /data/dalvik-cache and /cache and THEN upgrade to 5.1. If you don't do that, you are going to run into problems.

I will flash back to 5.0 and try that to make sure that there are no issues.
[X 2014 Android Development] mikeoswego:
Deleted - bad info
[X 2014 Android Development] mikeoswego:
I remember seeing that No Command thing in the past (before 5.1 was out) and thought that was normal. Maybe meaning that no command was passed to recovery from a process before the phone rebooted, like when there is an OTA.
[X 2014 Android Development] JulesJam:
First please understand that maiko1 has configured each copy of mofo.exe to check not only for your device's serial number but for your bootloader version. So if you have taken the OTA, your bootloader has been upgraded to 5.1 bootloader and your copy of mofo.exe will not work.

According to maiko1, the exploit he was using that enabled mofo.exe to trick the bootloader into allowing unsigned system images to be flashed has been closed in the 5.1 bootloader. So even if mofo.exe would allow you to attempt to flash, the 5.1 bootloader would not allow the unsigned files to flash.

Some people who took the 5.1 soak OTA that upgraded them to the 60.14 bootloader claim they were able to flash back to the 60.11 bootloader (5.0 bootloader). But the official 5.1 OTA should upgrade you to the 60.16 bootloader and no one has reported being able to flash back to 60.11 bootloader from 60.16.

In theory, if you try to flash back both the 5.0 motoboot.img and gpt.bin, you should get a failure to flash, not a brick. But it is not something I am too keen on even trying because you could brick if the flash doesn't fail. I started a thread in General with a warning about downgrading bootloaders, and you can read everyone's experiences on that thread. No one has reported successfully flashing back to 5.0 BL (60.11) from 5.1 BL (60.16).

Also - bootloader/partition table version mismatches can cause problems. So if you ever attempt to downgrade a Motorola bootloader (which I don't recommend unless you know for sure it can be done safely), be sure to FIRST flash the corresponding partition table (gpt.bin) before you flash the bootloader (motoboot.img). There was an instance where this could be done safely on the Moto X 2013 - I think it was from 4.4.2 to 4.4 and jcase discovered it and used that to downgrade and root the MX13. But again, unless you know that it can be done safely, I wouldn't try to do it. It should fail to flash if it can't be done, but I know with the MX13, some people bricked even trying. Hopefully there are more safeguards now to prevent that but it all depends on the human beings who write this software to put the checks in.

According to Root Junky, [MENTION=5697730]maiko1[/MENTION] is working on trying to find an exploit in the 5.1 bootloader. It would be great if he could do that.
[X 2014 Android Development] mikeoswego:
Ah, I should have looked around a bit before posting about that. I deleted that post.
[X 2014 Android Development] JulesJam:
I created a thread on downgrading Motorola bootloaders in General if people want to read up on it. These are not Nexus devices. You have to be careful with the bootloader and the partition table of a Motorola device. Make sure you know what version you are on before you do any flashing of motoboot and gpt.

We are still under warranty so we could get warranty replacements but my qe = 1/1 in recovery and nothing I do changes that. Idk if they would or could check that if I bricked. I have MotoCare so I could drop my phone in a bucket of water and then pay the $39 deductible to get a new one since water damage is covered. And if it was submerged like that, I doubt they could turn it on to see the qe was 1/1.
[X 2014 Android Development] trimax84:
Interesting finding when I open xposed, yet everything except for gravitybox work fine

Edit. Updated to the latest apk. No longer looks like the screenshot I posted, but gravitybox still won't load (even after reboot).
[X 2014 Android Development] mikeoswego:
I'll make the first post more explicit about the need to upgrade the Xposed Installer! I use GravityBox for LP with no problems. Have you gone into the Xposed Installer / Download to check that you have the latest version? GravityBox shows up in Settings->Apps/Downloaded; have you tried clearing cache and data for it? Perhaps a removal and reinstall from the Xposed Installer would fix it.
[X 2014 Android Development] mikeoswego:
I see where the confusion lies about the Xposed Installer apk. When I released the 5.0 images with Xposed v65 framework, I told people to update the Installer apk. I didn't think that through when I wrote the upgrade to 5.1 instructions and was thinking that everyone would already have the new Installer.

Unless you did so recently (the new Installer was released on June 28), you need to download the alpha4 version of the Installer located here: XposedInstaller_3.0_alpha4.apk. You can install that over your existing version.

Sorry for the confusion about this part of the upgrade!
[X 2014 Android Development] JulesJam:
I flashed back to 5.0 stock again, then flashed a rooted 5.0 image then flashed a 5.0 image with Xposed. Got that up and working and then deleted BOTH the contents of /data/dalvik-cache and of /cache using ES File Explorer.

Then booted into BL mode and flashed all of the signed 5.1 files, then used MoFo to flash mike's base image patched with AdAway and Xposed as well as debloated. Booted fine, no issues. Adaway and Xposed working fine including Gravity Box. I have rebooted a couple of times with no issues.

Soooo - what this means is that you MUST delete the contents of BOTH /data/dalvik-cache and /cache BEFORE you upgrade to 5.1. And of course you need the most recent version of the Xposed Installer.

Nice work [MENTION=5849464]mikeoswego[/MENTION]!!!! So happy to be on 5.1 with root, free tether, AdAway and Xposed!! It's a shame that we didn't get VoLTE with this update and I fear we never will. I will keep hoping but the iPhone 5s isn't getting it and I worry that Verizon won't give it to us either.
[X 2014 Android Development] tyleras3:
The strange thing is, I didn't delete those folders and I booted fine with no issues along the way, maybe it's because I already had xposed installed from previous imgs
[X 2014 Android Development] JulesJam:
Well who knows then, but I can tell you when I did it, no problems and when I didn't do it, there were problems.

I think for the 30 seconds it takes to delete the contents of those 2 folders, it would be wise to do it before flashing to a new version of the OS. It may not be necessary but it can save you aggravation if it is necessary.
[X 2014 Android Development] mikeoswego:
Thanks!

I've heard that Verizon wants their customers to have VoLTE, voice calls on 1XRRT use a lot more bandwidth and they want to get rid of that. In my area there are still lots of places without LTE so I would be worried about enabling VoLTE due to the alleged problems with dropped calls when leaving LTE coverage, though.
[X 2014 Android Development] mikeoswego:
Where you running the recent 5.0 image with Xposed v65 or the original mofo 5.0 with Xposed alpha2?
[X 2014 Android Development] JulesJam:
If you are in a spotty LTE area, you simply turn Advanced Calling off on your phone.

The clarity of the HD Calling is fantastic. HD Calling only works if both callers are Verizon customers, both have a 4G LTE signal during the call, both have VoLTE enabled devices and both have Advanced Calling enabled on their lines. When it works it is great.

---------- Post added at 06:29 AM ---------- Previous post was at 06:27 AM ----------

I believe this is what I was running. It was an older image of yours.
[X 2014 Android Development] mikeoswego:
I agree. This was always important when flashing custom ROM's like CM on other devices. It was slightly easier to just press a button in TWRP to delete the cache and dalvik-cache.

There is something going on with Xposed and the dalvik-cache. If you run an image without Xposed, at first boot after clearing the dalvik-cache, it only optimizes somewhere around 60 apps on my phone. With Xposed, the optimization will be around 160 on the debloated image and over 200 on the full image. This ROM is odexed and I think the modifications Xposed makes causes the system to ignore the odex files and make a dalvik-cache item for everything. It wouldn't be surprising if there are differences in various Xposed versions as far as the dalvik-cache entries. This current version of Xposed does have some ART performance updates from upstream according to the release notes and maybe that affects the format of the dalvik-cache files.
[X 2014 Android Development] mikeoswego:
The newer version says XposedV65 in the image filename, the older one was just Xposed.
[X 2014 Android Development] JulesJam:
Yeah, I think the safest thing is just delete the contents of both /data/dalvik-cache and /cache. Takes 30 seconds and can save you a ton of aggravation. It may take longer to optimize apps on first boot but you don't lose your data or media.
[X 2014 Android Development] RashaMatt:
I have TotalX 1.3 installed (which is Android 5.0) and things seem to be working (except I can't boot into recovery).

Is that a good starting point for this mofo 5.1 upgrade process? Or do I need to start from one of your referenced 5.0 images?
[X 2014 Android Development] JulesJam:
I answered you about recovery in Clyde's thread.

---------- Post added at 03:55 PM ---------- Previous post was at 03:54 PM ----------

That's fine but make sure to delete the contents of both /data/dalvik-cache and /cache before you upgrade to the 5.1 image and download the most recent version of the apk for Xposed for lollipop if you use a patch with Xposed.
[X 2014 Android Development] tyleras3:
I was running your latest img with Xposed v65. I would have deleted the folders, but I forgot, again.
[X 2014 Android Development] JulesJam:
well then it might be like mike suspected and the issue is with different versions of Xposed - if you are running an older version you need to delete the folders but if you were running the newest version that is in the image then you don't.
[X 2014 Android Development] trimax84:
Deleted com.ceco.lollipop.gravitybox from /data/dalvik-cache and rebooting now to see if this alone fixes my Gravitybox issue of not loading despite having upgraded to the lastest version of xposed.....if it was from the dalvik-cache folder replicating when the older version of xposed was in there, then this should do the trick...

Edit... Nope, even after clearing the apps data and cache. No worries though, minor issue (which stemmed from me not following the directions)... I bet an uninstall/reboot/reinstall will fix it. My phone is actually running much more smoothly without gravitybox anyway
[X 2014 Android Development] redwings73:
Flashed a little while go...have not noticed any issues (reported here or otherwise) yet. Thanks!
[X 2014 Android Development] tacosrdelicioso:
Happy to see 5.1 running great!
[X 2014 Android Development] joshnat:
Running well right now. Thanks a million to Mike and Jules for all the help.

I'm using a debloated version of 5.1, but Gmail didn't have an Exchange account option. I installed Exchange Services from APK Mirror and it's working fine now.