yashsingh1/xdaforums huggingface dataset:
[X 2014 Android Development] firewater88:
OK, read everything at least 3 times, then read again. Got all my files in order, cleared both folders, double checked they were deleted (used root explorer), rebooted to bootloader. Fast boot flashed ask the pre stuff, made a modified image, mofo'd the new image. Rebooted- went right to blinking Android. Bummed. Tried rebooting several times, back to blinky. Booted to recovery, selected boot normal and it went to stock boot animation. Got to upgrading part, had 266 files. Booted in and confirmed I'm on 5.1. All works, exposed, root, bb, ad away... Not sure what happened, but I'm on 5.1 and that's what I wanted...

Edit: rebooted, went to no command Android, not blinking. Powered off then powered on and booted.

Do I need to redo the process again?
[X 2014 Android Development] RashaMatt:
Having a little difficulty...

I started from working TotalX 1.3 install. Deleted the dalvik folders, fastboot-cleared cache, mofo-flashed my patched 5.1 image, and fastboot-cleared the cache.

It booted up and went through the "Optimizing apps" phase, but as soon as it hits "Android is starting", I just get a black screen, and can't turn it on.

ADB can connect, so the kernel's running, but I cannot turn on the screen.

After a minute it soft-reboots, and then IT DOES THE OPTIMIZING-APPS ALL OVER AGAIN, and then the process repeats.

I tried clearing the cache via fastboot - no difference.

Any suggestions?

---------------- EDIT: FIXED ----------------

My problem was, I missed an entire BIG step from the instructions (hidden in a "Click to Show" section) - I neglected to flash the images from XT1096_5.1-Base.7z.

Such a noob - way too tired for this!

So I went all the way back to stock, then to TotalX 1.3, then to 5.1, and this time it worked. Yay!

Thank you everyone for your patience.
[X 2014 Android Development] tacosrdelicioso:
Weird how many people are having issues. I just got a new replacement phone from Motorola and had absolutely no issues with the install from stock unrooted 5.0. Of course I mofo'd 5.0 first and did all the procedures required to install 5.1. Had no glitches or complications. No failed boots of any sort. And the optimizing apps went by really fast. Maybe redownload and reflash. Try a base unpatched 5.1 image and if that goes smooth then try images with a patch done to it
[X 2014 Android Development] alexkirsch:
See if you can boot into recovery; If you can clear your cache from within recovery (not from fastboot). If you can not boot into recovery you can try flashing the older version of recovery.

You can download the 5.0 base files (which includes recovery) here:

http://xdaforums.com/showpost.php?p=61727871&postcount=253

---------- Post added at 11:41 PM ---------- Previous post was at 11:38 PM ----------

Try clearing cache from within recovery; if that is no-go I would do a factory reset.
[X 2014 Android Development] RashaMatt:
More and different problems now...

Things work fine until a reboot. Then it gets stuck forever on the Verizon logo. If I clear cache in recovery, then it will boot successfully (reoptimizing everything again).

I'm trying to narrow this down by disabling stuff (e.g. XPosed modules), but it's taking forever - disable a module, reboot, get stuck on Verizon, reboot to recovery, clear cache, reboot, rebuild cache, rinse and repeat.

Anyone know what might be causing this? TIA

--------- FIXED ------------

(This is great - all I have to do is ask for help and then I find the solution myself ;)

I had inadvertently restored a KitKat version of GravityBox.
[X 2014 Android Development] otakta:
stuck in a rut

I'm stuck and have come out of the lurking woodwork to ask for assistance.

I was MoFo rooted on the 5.0 image and wanting to make the upgrade to 5.1 . I wiped the dalvik and cache and flashed the 5.1 base files, but when I attempted to utilize MoFo to flash the 5.1 image, MoFo couldn't find my device. Adb devices showed the device was still connected. I ran MoFo as admin, to no avail. At this point I was using my desktop for the procedure and decided to try my luck on my laptop (as this has resolved issues in the past). I powered down my device and restarted the steps on my laptop, minus flashing the 5.1 base files. Only this time, adb was unable to find my device as well. I reinstalled drivers, but was again met with "no devices found" in MoFo and no connection through adb. Neither my desktop nor my laptop can connect to the device via adb now.

Results: My phone will boot, run through the long 5.0 boot animation, pause for 10 seconds or so, then shows my lockscreen. Immediately apps and processes crash and stop which stops me from being able to even unlock the phone. The phone takes 15 more seconds of crashing apps and processes before it shuts off or freezes entirely.

I guess my question is: what can I do at this point if none of my available PC's are able to connect with my device via adb? What steps can I take in as far as at least making my phone functional again?

Thanks to [MENTION=5849464]mikeoswego[/MENTION], [MENTION=5983610]JulesJam[/MENTION], and [MENTION=1576439]Slack3r[/MENTION] for all the hard work you guys put in!
[X 2014 Android Development] JulesJam:
First, are you sure you didn't mess with the bootloader? Are you still on 5.0 BL (60.11)?

---------- Post added at 09:45 AM ---------- Previous post was at 09:43 AM ----------

This happened to me at one point. I flashed so much though that I cannot remember specifics of what I did other than to say a full flash back to stock 5.0 followed by a factory reset cures everything. You lose all of your data/settings/media of course and that sucks but that will cure everything IME.

Unless you messed with the BL or PT then all bets are off.
[X 2014 Android Development] otakta:
AFAIK I didn't do anything to the BL. I simply wiped Dalvik-cache and cache and flashed the 5.1 base files. I wasn't even able to flash the 5.1 image. So maybe it's due to the fact that I'm still on a 5.0 image? How would you recommend I flash back to stock 5.0 without the ability to utilize adb? For some reason, Factory doesn't function on my device, when I select it from fastboot my device simply powers down :/

so frustrating...
[X 2014 Android Development] JulesJam:
Get into bootloader mode and flash back to stock 5.0 logo.bin, boot.img, system.img, recovery.img and modem (NON-HLOS) and basebands (fsg) - then boot into recovery and do a factory reset. Be sure and erase modemst1 and modemst2 before you flash fsg.

---------- Post added at 09:55 AM ---------- Previous post was at 09:53 AM ----------

You can tell what version of the BL you are running by booting into Bootloader mode. The 5.0 BL is 60.11.
[X 2014 Android Development] otakta:
[/COLOR]You can tell what version of the BL you are running by booting into Bootloader mode. The 5.0 BL is 60.11.[/QUOTE]

Yup, still on 60.11
[X 2014 Android Development] JulesJam:
You don't need adb.

Download the official 5.0 firmware (link is in my noob guide in General forum). Get into bootloader mode with the buttons. Then flash the following commands using the 5.0 firmware:

fastboot flash logo logo.bin

fastboot flash boot boot.img

fastboot flash system system.img_sparsechunk1

fastboot flash system system.img_sparsechunk2

fastboot flash system system.img_sparsechunk3

fastboot flash system system.img_sparsechunk4

fastboot flash system system.img_sparsechunk5

fastboot flash system system.img_sparsechunk6

fastboot flash system system.img_sparsechunk7

fastboot flash system system.img_sparsechunk8

fastboot flash system system.img_sparsechunk9

fastboot flash modem NON-HLOS.bin

fastboot erase modemst1

fastboot erase modemst2

fastboot flash fsg fsg.mbn

then boot into recovery and do a factory reset. Then boot into Android.
[X 2014 Android Development] otakta:
Oh, duh. downloading the 5.0 basefiles now, will update with progress.

---------- Post added at 10:31 AM ---------- Previous post was at 10:06 AM ----------

So after flashing using the commands, I have been unable to boot into recovery. I get the No Command android. Is it inadvisable to proceed without factory reset?

---------- Post added at 10:47 AM ---------- Previous post was at 10:31 AM ----------

I booted up without factory and have basic phone functions for the time being. I'm gonna do my best to figure it out and report back depending on any issues I may come across. Thanks for your time and help [MENTION=5983610]JulesJam[/MENTION]
[X 2014 Android Development] JulesJam:
When you get the dead android, you press and hold the power button and then tap and release the volume up button to get into the recovery menu. That is in the noob guide.

[MENTION=5849464]mikeoswego[/MENTION] - can you please put a link to the noob guide in your OP? Thanks!

http://xdaforums.com/moto-x-2014/general/noob-guide-rooting-verizon-moto-x-2014-t3097375
[X 2014 Android Development] firewater88:
Thanks, clearing cache worked. Not sure why I didn't think of that. Maybe should have cleared it after I flashed everything. All is good now!
[X 2014 Android Development] RashaMatt:
FYI: If you flash/upgrade the ROM while you have NO SIM CARD in the phone, then when you later put in a SIM card, the phone may hang at the Verizon logo during boot. Mine did, anyway.

I fixed this by performing the following steps with the SIM card installed:

SET fastboot=c:\adb\fastboot.exe
%fastboot% erase cache
%fastboot% flash logo logo.bin
%fastboot% flash boot boot.img
%fastboot% flash modem NON-HLOS.bin
%fastboot% erase modemst1
%fastboot% erase modemst2
%fastboot% flash fsg fsg.mbn
%fastboot% flash recovery recovery.img
%fastboot% erase cache
[X 2014 Android Development] mikeoswego:
Done!
[X 2014 Android Development] mikeoswego:
Thanks for this info, I've added it to the instructions.
[X 2014 Android Development] JulesJam:
FYI - a dev on the DT forums figured out how MoFo works. I thought it was interesting to know.

http://xdaforums.com/showpost.php?p=61672253&postcount=4

If you fill up the /cache partition, the overflow gets written to /system no matter what you are flashing. Motorola closed that exploit with the 5.1 bootloader.
[X 2014 Android Development] mdmogren:
OK finally had a chance to patch and flash this - AirAudio works! Thanks so much.

The only thing I'm missing now is Visual Voicemail. Is there any way to get that back while still on the de-bloat image? Something I can install? If not can we get a non-debloated AirAudio patch or could you consider leaving Voicemail in the de-bloat? I found an apk (VVM3.apk) for it elsewhere on XDA and installed it but it just gives errors when I try to launch.
[X 2014 Android Development] JulesJam:
I think Verizon visual voice mail is an app you can download from the playstore.
[X 2014 Android Development] fabiozon:
Can I use this on an Pure Edition (XT1095) that's already on 5.1?
[X 2014 Android Development] JulesJam:
No - the firmware for the XT1095 is different from the XT1096 due to the different radios. Even if you don't flash the XT1096 radios, your XT1095 won't work as a phone if you flash an XT1096 /system because the hardware is different.

I flashed both the XT1097 and XT1095 /system to my XT1096 and it didn't work as a phone. The wrong device firmware will boot, but you can't connect to the network.

Is your bootloader unlocked? If so, you can add/delete to the /system partition yourself - you don't need an image like this. Those of us with XT1096 have locked bootloaders so we must use MoFo.
[X 2014 Android Development] mdmogren:
Forgot to mention, I tried that. It exists in the play store here:

https://play.google.com/store/apps/details?id=com.motorola.visualvoicemail&hl=en

But just shows "incompatible with your device"
[X 2014 Android Development] JulesJam:
There is a Verizon Wireless Visual Voicemail app by Verizon that I could download and install but when I opened it, for some reason it cannot check my account status. Maybe it needs MyVerizon to be installed to work?
[X 2014 Android Development] tacosrdelicioso:
There is a vzw sign in apk that probably got axed
[X 2014 Android Development] RadOD1:
Two questions:

1. When you say 'either of the above downloads', I don't see any downloads above that point. Do you mean 'XT1096_5.1-tether-root-bb-sqlite3.img'?

2. Can someone confirm that this is what I want to do in order to 'unpack the files': http://xdaforums.com/showthread.php?t=2294909

Coming from TotalX 5.0 with no problems flashing from mofo previously but this part of it is new to me.
[X 2014 Android Development] JulesJam:
These are the logo, kernel/ramdisk (boot.img), recovery, modem (NON-HLOS.bin), basebands (fsg.mbn):

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

You can use 7zip to unpack.

http://www.7-zip.org/
[X 2014 Android Development] infernohit:
I'm having trouble patching the base image. I have everything in one folder and run the command, but it always gives me an error saying xdelta3 failed or could not open the file specified. Not sure what I'm doing wrong.
[X 2014 Android Development] mikeoswego:
That's interesting. I always wonder how much time it takes for people to find these things!
[X 2014 Android Development] mikeoswego:
Verizon Visual Voicemail probably requires some of the other Verizon stuff like the SSOEngine for logins and maybe MyVerizon as well. Unless you're low on RAM (like with a 16gb device) you can just disable apps using Titanium Backup or the latest version of ES Explorer with the same results.

I'll make you an AirAudio full image version. I'm redoing everything due to a minor problem I found in the base image so it will be a few hours.
[X 2014 Android Development] mikeoswego:
I changed the instructions a day or so ago to remove the wording about "either of the above downloads" Before I was telling people to either get the full Verizon download or the smaller XT1096_5.1-Base.7z file. Now I'm not mentioning the other larger file, it just leads to confusion.

So, first download the XT1096_5.1-Base.7z file and the XT1096_5.1-tether-root-bb-sqlite3.img.7z file.

Use 7zip to unpack them. Download 7zip from here: http://www.7-zip.org Once you install the software, you will be able to open and extract the files from the 7zip archive.

I used 7zip because it resulted in a 100mb reduction in the size of the image file archive compared to .rar. Another nice thing about 7zip is that it handles practically every archive format out there.
[X 2014 Android Development] mikeoswego:
Are you running the correct vesion (x86/32-bit or 64-bit) for your version of windows? You could try the 32-bit (x86) version if the 64-bit isn't working.

Sometimes in windows, depending on where you placed the files, the path/filename string may be to long. Try making your work folder directly on C:/ . (Click start, then Computer, then double-click on the (C: ) drive, make a new folder there, put the xdelta3.exe and your working files in that directory. Before running xdelta3 make sure your in the right directory by entering "dir" (without quotes) in the command window and you should see your files listed.)

If these two things don't help, please give the exact error that your are seeing.
[X 2014 Android Development] RadOD1:
Thanks for the clarification. FYI - just accessed the second post and it currently says "Unpack the files from either of the above downloads"
[X 2014 Android Development] mdmogren:
I'm OK without the de-bloat, could you make a patch for AirAudio by itself? That way I can just patch the base with all the patches I want and flash that, right?
[X 2014 Android Development] betarepeating:
Worked fine for me on 5.1 using a bootanimation.zip from here. You should put these instructions in the OP somewhere so people don't have to search the thread for it.

Btw, took a Stock 5.0 XT1096 up to 5.1 Rooted with your image with no issues at all. Instructions were clear and easy to follow all the way through. Only (minor) mistake i made was some confusion before realizing I needed both XT1096_5.1-Base.7z and the XT1096_5.1-tether-root-bb-sqlite3.img.7z files, I thought I only needed the base file but it became clear quickly when there was nothing to patch!

I ran a stopwatch of my bootup time over 3 runs before and after flashing, and I was getting ~45 seconds on stock 5.0 and ~38 seconds on your debloated 5.1 image. Nice!

Thanks a lot for all your work.
[X 2014 Android Development] mikeoswego:
Fixed, thanks for pointing it out!
[X 2014 Android Development] mikeoswego:
No, unfortunately xdelta doesn't work that way. The patch can only work against the file it was originally created for. It would be nice if it did work that way, to have one patch that would apply something like AirAudio to any version!
[X 2014 Android Development] mikeoswego:
I'll do that!
[X 2014 Android Development] drocny87:
5.1

i have successfully updated from 5.0 to 5.1 with root. I am a little confused on how to get xposed to work again. i had the new apk active before 5.1...how do you use the patch files to get xposed to work again? thank you

btw, has anyone experienced awful battery life after rooting?
[X 2014 Android Development] mikeoswego:
See post 2 for how to use the patch files.

My battery life has been good if not great.
[X 2014 Android Development] drocny87:
i followed the steps but am getting an error when using cmd saying ----'xdelta3' is not recognized as an internal or external command,

operable program or batch file.
[X 2014 Android Development] mikeoswego:
You have not opened your command window in the folder where the xdelta3 file and image/patch files are located. Enter "dir" (without quotes) and you should see your files. All 3 files have to be in the same folder (unless you are using Linux.)
[X 2014 Android Development] drocny87:
i created a folder on my desktop with all 3 files needed to create the new image.
[X 2014 Android Development] mikeoswego:
New version

I've upgraded the files for use with mofo on the XT1096. The base files for updating from 5.0 remain the same. The base mofo image has been changed. Here is a changelog:

Release 2 - 07/09/2015

- Base file name: XT1096_5.1_mofo-base.img
- Correct security context on /system/etc/install-recovery.sh to value
in original ROM instead of value as set by SuperSU installer which
was causing script to not run at boot.
- Make AdAway support the default. Added functionality to create
/data/data/hosts file on boot if it doesn't exist. (For users who
don't wish to use AdAway ensuring there will be no problems in
resolving localhost for apps/processes that might use that.)
- Shorten and simplify names of base and patch files.
- Upgrade SuperSU from v2.46 to v2.49

Initial Release - 07/05/2015

- Base file name: XT1096_5.1-tether-root-bb-sqlite3.img

Updated on 07/10/2015 - see post 374 for the newest files.

Post 2 has been updated with this info and some other tips.
[X 2014 Android Development] RyanBRZ:
How do you apply a patch? Can you add that to the OP?
[X 2014 Android Development] mikeoswego:
The instructions are in post 2.
[X 2014 Android Development] drocny87:
thanks for the update. xdelta has created the new image with the patch. i ran it twice and did notice the image is not the same size as the original base.
[X 2014 Android Development] mikeoswego:
What is the name of your base file and of the patch file you are trying to use?
[X 2014 Android Development] drocny87:
im trying to get xposed patched into the new base image you created.

the name is-- xt1096-5.1-mofo-base
[X 2014 Android Development] mikeoswego:
And the patch is named base-to-base_xp.patch? I've just re-tested that and it is working here.
[X 2014 Android Development] drocny87:
yes that is the name of the patch. i created the patched image twice but both times they are not the same file size as the original base file.
[X 2014 Android Development] mikeoswego:
For windows users.. I'll add the following to post 2. Here are some instructions that might help.

Sometimes windows has a problem with long path/filenames. This problem can occur when you try to use a program like xdelta3 in a folder on your desktop, in My Documents, etc.

Follow these instructions to avoid this problem.

Click Start, then Computer.
Double click on the C: drive icon.
Create a folder there named work.
Copy the xdelta3 program, image file, and patch file into this folder.
Open a command window and then enter the following commands:
cd /work
dir	(You should see your files listed including xdelta3)
xdelta3 -d -s [image filename] [patch filename]
ex: xdelta3 -d -s xt1096-5.1-mofo-base.img base-to-base_xp.patch
[X 2014 Android Development] mikeoswego:
If you're using the 64-bit version of xdelta3, you might try the 32-bit (x86) version.
[X 2014 Android Development] drocny87:
I am using the 32bit version. 64 bit didnt work. Is it possible to upload a file with xposed patched in?
[X 2014 Android Development] chairman011:
sorry if this has been answered already

ive been reading as much as I can i took the update 5.1 on my xt1096 mofo gives me the failed to detect purchase error when I already bought it so that means it doesn't work it you took the ota 5.1 correct? so im screwed for now huh?
[X 2014 Android Development] nola5712:
Help please :/ I had been rooted using mofo for 5.0 on xt1096. I woke up the other day, and my phone had automatically accepted and installed the OTA for 5.1 (side question: how do I disable this for future updates? Couldn't find anything in the settings that would allow this). THAT BEING SAID, post #2 says upgrading to 5.1 rooted 'assumes' I have already gone through the mofo process for rooting 5.0., which I have...BUT, now the OTA puts me back to 5.1 stock. So I don't know if that's saying, "To obtain root on 5.1, you must be on mofo rooted 5.0 first.", or, "You should be familiar with the mofo process etc.".

Therefore my question is what is meant by that statement? Am I okay to follow the same directions in post #2 having (unbeknownst to me) updated to 5.1 stock? Or do I need to do anything differently. I've been through this process enough times to know better than to assume, and to cross my t's and dot my i's before making that move.

Thanks in advance for any help, and most of all thanks to the dev who made this possible!
[X 2014 Android Development] mikeoswego:
If your phone has been upgraded to 5.1 by the OTA, you can no longer use mofo to flash these images. You would have had to disable the OTA by either using the debloated 5.0 image or freezing the OTA app with Titanium backup. Sorry.
[X 2014 Android Development] chairman011:
=( ok thank you so much for responding ima try and trade it or get a warranty replacement with older update thanks man.
[X 2014 Android Development] amd_h4x0r:
can you add a system patch for BetterBatteryStats as well? or tell us how to create our own patch files to include apps we want?
[X 2014 Android Development] mikeoswego:
What does it need aside from root? It's on the play store and the apk is in this forum: [APP] BetterBatteryStats
[X 2014 Android Development] mikeoswego:
Other full images

It seems there may be a need and the bandwidth was cooperating tonight; here are some full images for download for those that can't patch..

xt1096-5.1-mofo-base_xp.img.7z - Base image + Xposed

xt1096-5.1-mofo-base_de.img.7z - Base image with some apps removed

xt1096-5.1-mofo-base_xp-de.img.7z - Base image + Xposed with some apps removed
[X 2014 Android Development] amd_h4x0r:
It needs to be installed as a system app to function.

EDIT: hmm, maybe it still works without being installed as system app...I will test some more
[X 2014 Android Development] mikeoswego:
To create a patch, you would mount the image as a disk drive on your Linux box, make whatever mods you want. Then you would either just flash the image to your phone or use xdelta to make a patch if you want to distribute it. (xdelta3 -h tells you the command to create a patch from the base image to a new image.)
[X 2014 Android Development] JulesJam:
yes, that is correct.

---------- Post added at 06:57 AM ---------- Previous post was at 06:53 AM ----------

What version of the bootloader are you on now? If you are on 60.16 then Mofo won't work for you and there is nothing you can do about that. You can't downgrade the bootloader.

What version of the bootloader are you running?