yashsingh1/xdaforums huggingface dataset:
[X 2014 Android Development] mikeoswego:
The rooted rom image is all in /system. A factory reset wipes /data and will not affect the rom in /system.
[X 2014 Android Development] intx:
That would definitely be low for me. I average about 4 hours SoT and the longest I've stretched it out to is about 4.75 hour. I leave bluetooth and wifi on most of the time and stream music in my car over BT, read reddit and use some social media throughout the day, mixed with light calling and moderate texting.

I will say though, I don't have FB installed which I've always noticed to be a battery drainer.
[X 2014 Android Development] jrbmed08:
I almost always charge before I hit 20% to help maintain the longevity of the battery, but I'm usually at about 2.5 hours by the time I charge. Everything on my phone is optimized to prolong battery life. I don't have Facebook, Twitter, or Instagram installed. I keep location off unless I'm using GPS. I have Amplify, Greenify, and Power Nap installed and follow the Extreme Battery Life guide here on XDA.

Bottom line, I love this phone for everything except the battery life, which absolutely sucks. It did get better on 5.1 though.

Edit: I have a question regarding the TWRP image. Will we still be on the 5.0 bootloader and partition table, or will this bring us to a full stock 5.1 build? Also, is there any benefit to wiping data, i.e. a clean flash?
[X 2014 Android Development] mikeoswego:
The TWRP image is just like a CM rom, etc. It contains the 5.1 stock boot.img (kernel) and the slightly modified stock system image. It doesn't touch the bootloader or partition table so for those of us who where using mofo before the Sunshine unlock, we still have the 5.0 bootloader and partition table. I see no reason to worry about that. The bootloader allows flashing or starts either the recovery or system image and then exits. The 5.1 partition table has the same size partitions so there is no benefit in trying to update that. I also wonder if updating the bootloader to 5.1 would change how Sunshine sees the phone. It might invalidate your Sunshine license if it was based in some way on the 5.0 bootloader when purchased; that question would have to be asked in a Sunshine forum. This probably falls under the "if it ain't broke don't fix it" category!
[X 2014 Android Development] jrbmed08:
Perfect! I wasn't sure if it would be necessary to flash the 5.0 bootloader/partition table or not, so it's good to know it won't be necessary. At any rate, if we ever want to use mofo again, it makes sense to stay on 5.0 bootloader.

What about wiping data either before or after flashing; do you think that's helpful? I did wipe system and cache/dalvik via TWRP before flashing your latest image. I bought the phone on 5.0 but have never done a factory reset. On 3.1h, I started to have some issues with freezing and rebooting and wonder if a wipe might help. But if it's unlikely to do much, I hate to go through all that trouble, you know?
[X 2014 Android Development] sonic1675:
deleted
[X 2014 Android Development] jj62mtp:
Sorry if this is a dumb question but i used mofo and flashed the 5.1 3.1f img but the phone just goes through optimizing apps crashes and starts over. what am i missing?
[X 2014 Android Development] mikeoswego:
I've uploaded a new image for Mofo users that may fix this problem. The package is the rooted image with patches to debloat, add Viper4Android, debloat but keep CF.lumen, add v4a, debloat but keep Cf.lumen & Trebuchet.

The file is here: xt1096-5.1-v3.1g-pkg.7z
[X 2014 Android Development] mikeoswego:
Wiping cache and dalvik-cache is a good idea but probably not absolutely required unless there is a change in Xposed framework versions or other major changes have occurred. As for wiping data which is equivalent to a factory reset, there are some similarities between doing a wipe on our phones and doing a clean install on a windows system, there can be an accumulation of unneeded crud in the various config files especially if lots of apps are tried, then uninstalled etc. The data wipe is definitely on my list of things to try if a phone has bizarre symptoms or is sluggish.
[X 2014 Android Development] mulletcutter:
Any way to activate LED?
[X 2014 Android Development] mikeoswego:
There might be an Xposed module that does that. As you probably know, the CM roms for Victara use the led for a battery charged indicator.
[X 2014 Android Development] jrbmed08:
Search XDA for an app called "Moto X LED" - I use mine as a charging indicator.
[X 2014 Android Development] RyanBRZ:
It works flawlessly with Light Flow using the below settings.

Settings

-In LED Control, enable charging control. This should be the only LED you have enabled.

-In Device Settings and Root, I have the following set:

Root Mode

Run every command as root

Show LED while screen on (which doesn't work so I don't know if it matters having this set)

Then in the individual notification settings, under 'Light' settings do:

Set the color to the most basic green that you can, close to what the LED looks like.

LED flash rate = Always on

charging LED = Solid

charging Brightness = 20
[X 2014 Android Development] mulletcutter:
I'm trying to delete my twrp folder, but any file explorer I use says I can't access that folder. Its there and has 4gigs in it. Any other way to delete it from my phone without a computer
[X 2014 Android Development] mikeoswego:
That folder has your backups in it (for the ones stored to sdcard.) It also contains your settings for TWRP. I remember that I had this problem, but now I can access that folder with a file explorer; I forget what I changed. Have you tried accessing it via the file manager in TWRP? Have you tried the 2.8.7.1 version of TWRP that was recently posted? I am and maybe that is what fixed the access to that folder.
[X 2014 Android Development] jrbmed08:
I can't access the folder on my phone, but I can access it via my computer over MTP. Hope that helps.
[X 2014 Android Development] mulletcutter:
I have 2.8.7.0, I went into recovery file manager and deleted each file. Have to DL and flash 7.1.
[X 2014 Android Development] nola5712:
Hey man, I've been super busy for awhile, but just now getting some time to get to 5.1 without losing root. Where can I find these steps to follow for moving from 5.0 to 5.1? Thanks in advance again for the great utility!

EDIT: Sorry checking the OP as it looks like it's been changed and there are some instructions there! Thanks again

---------- Post added at 05:47 PM ---------- Previous post was at 05:22 PM ----------

So I'm confused, do I NEED to use Sunshine to unlock the bootloader and move to 5.1? Or can I just flash if I'm already 5.0 Mofo rooted? Apologies if I'm missing something here. Also, if I do NOT need to use Sunshine, what benefits would I be missing out on by omitting that part of the process? Thanks in advance!
[X 2014 Android Development] drewski_1:
You don't need Sunshine and can mofo flash a 5.1 image after updating the 5.1 base files as outlined in the OP.

Sunshine unlocks the Bootloader, so you can install a custom recovery like TWRP and have R/W access to the /system partition.

Sent from my Lollipop TF700T
[X 2014 Android Development] nola5712:
Okay...

EDIT: Thanks [MENTION=259002]Drewski[/MENTION] for the reply - I typed the following before you replied.

Well those instructions are pretty unclear on how to upgrade, what's required, what's not, what 29 things I need to download etc. Can I not just go into fastboot, and flash the base zip??

This seems like a million things I have to do to upgrade, which is fine, I'm not complaining. But my only main goal here is to make this stupid install update reminder go AWAY! That's IT. I don't care about 5.1 at all, and am perfectly fine rooted on 5.0. If my device already downloaded the OTA for 5.1 on it's own, but has NOT installed it, how do I make this daily pain in my ass reminder go away permanently? Do I HAVE to upgrade? Or can I disable that somehow?
[X 2014 Android Development] mikeoswego:
You don't need to use Sunshine. The instructions in the OP where written before the Sunshine unlock was available. I would suggest that you upgrade to 5.1 using those instructions and then unlock your bootloader using Sunshine if you want.

Unlocking your bootloader with Sunshine lets you install TWRP as your recovery instead of the stock recovery. TWRP allows you to make full backups of your phone which is good for a disaster or if you like to experiment and want the ability to go back to exactly where you were before the experiment. TWRP also allows you to flash other roms like CM or the others that are available. The stock rom is very good, there is nothing wrong with it but there can be benefits to using one of the other roms. For instance, the CM rom (and those derived from it) had the Stagefright exploit fixed weeks ago while we are still waiting for Moto/Verizon to release their fixes.

At some point in the future, Moto/Verzion will drop support for this phone while CM and the others will probably continue providing updates and new Android versions. If you can afford the $25, I would definitely recommend the Sunshine unlock for the options it opens up even if you might not use them right away.
[X 2014 Android Development] mikeoswego:
I know it may look hard but you only have to download 2 files, use fastboot to flash the files contained in 5.1bins.7z and then use mofo to flash the image in xt1096-5.1-stock-20150820.zip. No data will be lost, you will have the benefits of the 5.1 upgrade like better battery life, etc. Added: Don't forget to delete everything in /data/dalvik-cache !

Be forewarned though, that when Moto/Verizon release their Stagefright exploit patches, you are going to be pestered to upgrade again (and you will want to do it for security!)

If you really want to just disable the update process, it may work to go into Settings->Apps->All find the Motorola OTA or Update app, select it, and then select Disable.
[X 2014 Android Development] nola5712:
Thanks again for the reply. First question, I didn't see anything about cost on SunShine's site, nor was I alerted of anything when downloading the apk, so there is a cost involved? Second, on SunShine's website, it only says it supports Moto X 2013 not 2014, but I assume that it will work either way? Third, thanks, I am very familiar with TWRP and am aware of the capabilities there. Fourth, I was not aware that Moto/Verizon hadn't released a Stagefright fix yet so that's good to know.

FIFTH: So you're saying the best course of action is to fastboot the base 5.1 image. And then after that use SunShine to install TWRP? What the other responder said above confused me. I don't understand about "updating those files first". I don't have any files outside of the 5.1 base image I downloaded, so what am I supposed to update prior to flashing? Are these other files I need to download and THEN update before flashing the 5.1 zip?
[X 2014 Android Development] mikeoswego:
To upgrade to 5.1 without Sunshine, you need these 2 files:

5.1bins.7z - Kernel, modem and other 5.1 update files

xt1096-5.1-v3.1g-pkg.7z - Base image

Use your root file explorer and delete both folders in /data/dalvik-cache.

Extract the files from the 5.1bins.7z archive and then run these commands:

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

Then, immediately use mofo to flash the 5.1 image. Reboot your phone and enjoy Android 5.1!

As far as Sunshine.. If you run the app, it will test your phone and make sure their exploit will work, then, it passes, it will offer the option to unlock the app and actually perform the needed steps to unlock the bootloader. It costs $25 to unlock the app. Again, you don't need Sunshine but the option is there should you want to use TWRP, flash other roms, have /system mounted R/W; otherwise you might not want it.
[X 2014 Android Development] jrbmed08:
If you want to save $20, skip mofo and use kingroot to obtain temp root and go directly to sunshine (which is $25).
[X 2014 Android Development] mikeoswego:
I think he already has mofo since he is running the 5.0 rooted image.
[X 2014 Android Development] jrbmed08:
Oh, thanks! I skimmed the posts and missed that part. Never mind then!
[X 2014 Android Development] nola5712:
Okay I got tied up with some things, but thanks again for the reply. So I'm getting ready to try this, but one question: I remember when I originally mofo'd, the image had to match the system version, so this base image file (which I'm assuming I extract to get the .img file) will be the correct version correct?

EDIT: Also where do I need to extract those files to? Should they be in the adb folder? Sorry for all the questions, this is obviously a much different process than anything I've encountered on my D1, D2, D2G, Bionic, or DNA.
[X 2014 Android Development] mikeoswego:
Yes, the files linked in my previous post go together. Both of them are for Android 5.1

I always found that the .img file (extracted from the xt1096-5.1-v3.1g-pkg.7z archive) is best put in the same folder with mofo. Then the other files depend on how you installed adb/fastboot; if fastboot is in your path, put everything in the mofo folder for simplicity.

Navigate to your mofo folder, click on the address bar at the top of the folder window and type cmd to open a command window in that folder. Then, just enter fastboot by itself and see if it runs. If it does, fastboot is in your path and you can put everything in the mofo folder. If not, you will have to put the files from the 5.1bins.7z archive into the adb/fastboot folder, run those commands in that folder then go to the mofo folder and run mofo from there with the xt1096-5.1-v3.1g.img file placed there..

I'm going to add here that if you do get into trouble, the original 5.0 files are still up on filehost. You can fastboot flash the 5.0 binary files and mofo flash a 5.0 image to get back to where you are now. The old set of 5.0 bin files is here: XT1096_5.0-Base.7z and a 5.0 mofo image is here: XT1096_5.0-tether-root-bb-sqlite3-XposedV65.img.7z

Please don't forget to use your root file explorer and delete both folders in /data/dalvik-cache before putting your phone in bootloader mode!
[X 2014 Android Development] nola5712:
Hey dude, thanks again for the reply as I'm sure I'm annoying the crap out of you. I went ahead and took the plunge before you responded, and I think all is going well so far. I'm at the Android is Upgrading screen currently so I'm sure everything will work itself out. I've just been conditioned by the android community to follow directions to a T for years you know? So going forward with something like this, if there's even a small detail left out I freak and hold off. But it looks like everything is going well so far. That SunShine process will be next provided this goes off without a hitch. Thanks again man.

EDIT: Lol and of course after all that talk about following directions to a T, I had the 2 folders checked in Root Explorer to delete, but was testing fastboot and just went right into the bootlader, and flashed everything. Well derp haha. Still on the Android is Upgrading screen so we'll see what happens. What does happen if I don't delete those? Worst case scenario I'll just start over :P Thanks again though for the help.

EDIT 2: Just finished and my phone is all kinds of unhappy with me haha. I'll go back to 5.0 and try this again without the derping :)

---------- Post added at 01:32 AM ---------- Previous post was at 12:53 AM ----------

Okay now I need help... So I went back and flashed those 5.0 files to start over, and the phone went through the whole process, but never got to the Android is upgrading screen. And now I can't get it to even boot. Ideas?

---------- Post added at 01:39 AM ---------- Previous post was at 01:32 AM ----------

Now it's just constantly rebooting never even finishing the animation. It gets to the soccer ball being hit then just turns off and starts over....please tell me I can do something to fix this...
[X 2014 Android Development] mikeoswego:
Factory reset.. Get your phone into the bootloader screen. Press volume down to highlight recovery, the volume up to select it. After a bit, you should see a "dead android" Press and hold the volume up button and tap the power button to get to the recovery menu. use the volume up/down keys to select Factory reset and then press the power button to select the option.

Edit: and since your doing the factory reset, you might as well use the 5.1 files instead of configuring 5.0 and then trying to upgrade again!
[X 2014 Android Development] nola5712:
I managed to get into the bootloader screen once, but can't get back. When I got there I got to the dead android, but holding volume up then power didn't do anything :( If I manage to get back there do I just go through the same process? Delete the 2 folders, get into fastboot, fastboot the files, then mofo the image?

---------- Post added at 02:06 AM ---------- Previous post was at 01:58 AM ----------

I can get back to the dead android, but volume up then tap and release power is doing nothing, it just sits on the dead android screen :(
[X 2014 Android Development] mikeoswego:
Ok, to get into the bootloader when things are messed up. Hold the volume down/power button combo for longer than you think is needed. When you release them, if it doesn't go into bootloader mode but starts to boot, press and hold them both again for even longer (for like 10 seconds after the screen goes dark.) Eventually, you will be able to get into the bootloader. Sometimes, after you release the buttons, nothing happens for a few seconds, don't get impatient and wait for at least 10 seconds before trying again.

You can't delete the 2 folders now because you can't boot and run your root file explorer (unless I'm misunderstanding you.) All you can do now is the factory reset which deletes everything in /data including those 2 folders. If you have allowed backups to Google, after you sign back in,your contacts will be restored and it will offer to restore your apps along with most of the settings (at least on 5.1 it does that.)

After the factory reset, go back into bootloader mode, fastboot flash the 5.1 bins and then mofo flash the 5.1 image file. If you still have trouble, you could try mofo flashing an older 5.1 image file like this one: xt1096-5.1-v3.1a.img.7z or this one: xt1096-5.1-v3.1e.img.7z
[X 2014 Android Development] mikeoswego:
Ok, while in bootloader mode fastboot flash all the 5.1 bins files including recovery.img. Then try to enter recovery again. If still not working, power down the phone, then try again to get into recovery from bootloader. If still not working try to mofo flash the 5.1 image again and then see if the phone will boot up normally. Wait 4-5 minutes. If still nothing, go back to the bootloader and try to get into recovery again.
[X 2014 Android Development] nola5712:
Dude you are a saint for putting up with me. Okay I FINALLY managed to get to the recovery screen, wiped data/factory reset, and am rebooting now. So now I just follow the original instructions MINUS deleting the two folders? Or I still need to delete those?

EDIT: Probably going to charge to full if and when this actually boots, so that I don't lose power during the next process.
[X 2014 Android Development] mikeoswego:
If the phone boots up now (on 5.0?) then yes, you need to delete the folders in /data/dalvik-cache before upgrading to 5.1 If it was me, I'd probably go in and do the factory reset again, fastboot flash the 5.1 bins, mofo flash the 5.1 image and then let the phone start up fresh in 5.1 It does take 4-5 minutes before you will get to any setup screens when you do this, it will appear to be stuck on the boot animation.
[X 2014 Android Development] nola5712:
Oh lord I finally got booted up, thank you so much dude, you are a saint.
[X 2014 Android Development] mikeoswego:
Excellent! Thanks for the update!
[X 2014 Android Development] nola5712:
Thanks again for your help man! I woke up early to finish the process, and got 5.1 loaded, maintained root, and I'm good to go this morning :D
[X 2014 Android Development] mbkintner:
Since you still have root I would go ahead and use Sunshine to unlock your bootloader. Then you can get away from needing to use MoFo and not have to worry about losing root in the future.
[X 2014 Android Development] drwhitney:
[MENTION=5849464]mikeoswego[/MENTION] Are there any other updates or features you have on the horizon for building into this ROM, or are you satisfied with the mostly stock, debloated, rooted, and unlocked state that it's in now? (Personally I'm extremely content, grateful, and pleased; more just curious than anything else.)
[X 2014 Android Development] mikeoswego:
I do plan to integrate the Stagefright exploit patches that are supposed to be in the pipeline. If there are future updates while I still have this phone, I'll probably do those as well.

I'll commit to making a mofo flashable image for the Stagefright update if there is a demand but the whole process is kind of messy compared to making the TWRP flashable image. I think it would be wise for everyone to unlock their bootloader with Sunshine so they can use the TWRP flashable images and have other options for the future.
[X 2014 Android Development] AntsInMyPants:
Any chance of creating a copy of the your modified 5.1 that can be flashed via TWRP?

The stock 5.1 ROM does not allow tethering and since unlocking my bootloader, Mofo says my device is not valid anymore. There are no other ROMS that work on my XT1096 at this time. This includes CM which for some reason is not working on some XT1096 phones.
[X 2014 Android Development] AiahKnead:
It says in the first post that the twrp rom is tether-enabled and it works for me.
[X 2014 Android Development] mikeoswego:
The TWRP flashable version of the image is linked in the first post of this thread. The second post has links to zips to flash afterwards to debloat, add Viper4Android, etc. I guess naming the image stock might be confusing but it is the stock image with tether enabled, and SuperSU root, busybox, etc. already added in.

Added: How did you upgrade to 5.1? With the OTA? Mofo still works for me with the unlocked bootloader though I haven't used it since figuring out how to compile the TWRP flashable zip.
[X 2014 Android Development] AntsInMyPants:
Thanks for the info.

I went back to stock 5.0 to run Sunshine to unlock the bootloader. After that, I could not get your 5.1 image to work no matter what I did (I had it running fine on two different XT1096's) so I resorted to taking the 5.1 OTA and then flashed SuperSU and TWRP. After that, Mofo told me my device was not valid and to purchase it.
[X 2014 Android Development] mikeoswego:
Ok, the OTA process replaced the motoboot.img file that mofo (in part) bases it's licensing on. Since your unlocked it doesn't matter. I was just curious!
[X 2014 Android Development] gunit25:
If we do not buy sunshine but had previously Mofo'd ourselves, is there any image we can continue to flash without TWRP?
[X 2014 Android Development] mikeoswego:
The latest Mofo flashable image is here: xt1096-5.1-v3.1g-pkg.7z. The archive includes patches to debloat, add Viper4Android, etc.
[X 2014 Android Development] AiahKnead:
Are there any plans of adding custom CPU governors like smartmax and voltage control?
[X 2014 Android Development] mikeoswego:
I don't have any plans for an updated kernel, that isn't in my current skill set. [MENTION=5438598]RenderBroken[/MENTION] might be willing to get his kernel to work on the stock ROM if enough people where to ask him. His thread is here: Render Kernel.
[X 2014 Android Development] SomniusX:
does these work for 1092 models?
[X 2014 Android Development] slogar25:
I think you should read the op