yashsingh1/xdaforums huggingface dataset:
[Moto X Themes and Apps] Ctrl-Freak:
I did this for myself, and thought I would share. I got tired of the "Raise volume above safe level?" warning, and I removed it. I like to learn, so rather than use the existing xposed framework mod, I built a flashable zip to make the change via framework-res.apk.

WARNING: I AM NOT RESPONSIBLE IF YOU MESS UP YOUR PHONE

Prerequisite:

ATT Moto X running stock official 4.4 kitkat (140.44.5)

TWRP or CWM (safestrap for those who don't have an unlocked bootloader, thanks Hashcode)

backup all of your data in case something goes horribly wrong

Instructions:

using your choice of file manager, backup /system/framework/framework-res.apk

Download or copy flashable zip (below) to sdcard

Reboot to [safestrap] TWRP recovery

flash zip file

Below are the 'broad strokes' of how I did this in linux: (Each of these steps below require various skills, and my intent is not to do too much 'hand holding.')

DUMP AND DECOMPILE framework-res.apk

make sure java 7 is installed

download/extract apktool_2.0.0b7.jar (thanks brut.all)

move /system/framework/framework-res.apk to apktool directory

install framework: java -jar apktool_2.0.0b7.jar if framework-res.apk

dump framework-res.apk: java -jar apktool_2.0.0b7.jar d framework-res.apk

--

CHANGE SETTING IN TWO FILES:

edit this file: framework-res/res/values/bools.xml

search for the line with this info: config_safe_media_volume_enabled

change the value to: false

repeat with framework-res/res/values-mcc310/bools.xml

--

DELETE DIRECTORY STRUCTURE (not sure why framework wouldn't compile with this, but it is unused on AT&T phones)

delete this directory: framework-res/values-mcc310-1

--

RECOMPILE AND COPY EXISTING SIGNATURE:

recompile: java -jar apktool_2.0.0b7.jar b framework-res -o framework-res-new.apk

move META-INF structure from inside the original framework-res.apk to the new framework-res-new.apk (I used 7z)

--

ZIPALIGN NEW FILE:

zipalign -f -v 4 framework-res-new.apk framework-res.apk

--

CREATE FLASHABLE ZIP WITH NEW framework-res.apk

you can use mine as a template and just replace my framework-res.apk under /system/framework

TWRP/CWM flashable zip: http://www.androidfilehost.com/?fid=23252070760973197

(Replaces /system/framework/framework-res.apk with my modified version.)
[Moto X Themes and Apps] slimdizzy:
Trying this now on my Rogers ATT KK based Moto X. Ill update soon.
[Moto X Themes and Apps] slimdizzy:
Updated script brakes at device check.
[Moto X Themes and Apps] Ctrl-Freak:
Do you mean the updater-script in the flashable zip? If so, you can modify those checks for your phone if you can see the error. I used twrp->advanced->copy logs to /sdcard to see the error messages.
[Moto X Themes and Apps] slimdizzy:
Will do. Ill post shortly.

Update:

Installing '/sdcard/motox-att-140.44.5-framework-res-1.zip'...

Checking for MD5 file...

I:Cannot find file /sdcard/motox-att-140.44.5-framework-res-1.zip.md5

Skipping MD5 check: no MD5 file found.

I:Zip does not contain SELinux file_contexts file in its root.

script aborted: This package is for "ghost" devices; this is a "xt1060".

This package is for "ghost" devices; this is a "xt1060".

E:Error executing updater binary in zip '/sdcard/motox-att-140.44.5-framework-res-1.zip'

My build.prop shows 1058 for the record.
[Moto X Themes and Apps] Ctrl-Freak:
Did you build this from your Rogers framework? (If not, keep in mind my framework-res if from an AT&T phone. I have no idea if there are any differences.)

To continue, you can edit the updater-script and make the change from "ghost to "xt1060".
[Moto X Themes and Apps] slimdizzy:
I have a rogers phone but ATT firmware. This is just what happens when I flash your zip. Your updated script asks for a 1058, which is my model but breaks and says my device is a 1060. That is nowhere in my prop. This should flash no problem and it doesn't. I even tried to manually overwrite using root explorer and my phone wouldn't boot after. I replaced original file and all is well.
[Moto X Themes and Apps] tal.aloni:
Thanks, this worked like a charm for my Moto G.

I used Advanced ApkTool v2.0.0 to decompile 'framework-res.apk',

I used Notepad++ to set all 'config_safe_media_volume_enabled' entries to false,

After the recompilation, I extracted the content of the original 'framework-res.apk' with 7-zip, and just replaced 'resources.arsc' with the modified one. (can be found in the '\build\apk' directory)

Recompressed again with 7-zip (compression level: store) and used adb to replace the file:

adb push framework-res.apk /sdcard/Download/framework-res.apk

adb shell

su
mount -o remount,rw -t ext4 /dev/block/platform/msm_sdcc.1/by-name/system /system
mv /system/framework/framework-res.apk /system/framework/framework-res.apk.bak
cat /sdcard/Download/framework-res.apk > /system/framework/framework-res.apk
chmod 644 /system/framework/framework-res.apk
sync
reboot
[Nexus 5 Q&A, Help & Troubleshooting] shampiaj:
I have a N5 stock/rooted. Does this mean I will have to unroot just to update my phone to KitKat 4.4.1 when it comes out? I would prefer to keep the stock ROM but want the camera upgrades that 4.4.1 is supposed to offer.
[Nexus 5 Q&A, Help & Troubleshooting] simms22:
so reroot if you are going to have to unroot, big deal. if you want to update from the stock update, you will lose root. then all you have to do is flash a custom recovery then flash the latest supersu in your recovery. it takes about 3-4 minutes of work(without toolkits)..
[Nexus 5 Q&A, Help & Troubleshooting] shampiaj:
Ok. So you are saying that I can unroot, upgrade to 4.4.1, then flash a backup recovery from something like TWRP and be all set? I was under the impression that flashing a custom recovery will also wipe out the current OS version.
[Nexus 5 Q&A, Help & Troubleshooting] simms22:
flashing a custom recovery doesnt wipe anything(except the stock recovery). unlocking the bootloader wipes data, not the recovery
[Nexus 5 Q&A, Help & Troubleshooting] shampiaj:
Thanks.
[Nexus 5 Q&A, Help & Troubleshooting] jt3:
Doesn't ADB side-loading still work with custom recovery?
[Nexus 5 Q&A, Help & Troubleshooting] LMedina270:
You need to unroot

Yes, you need to unroot to recive the OTA, in my case, i have a custom rom, so i will go stock if the update improves perfomance,because i have installed the camera fix v 1.3 and I'm happy with it
[Nexus 5 Q&A, Help & Troubleshooting] AceKingNYC:
I was just about to copy the steps you posted before your edit! If side loading works for OTAs (which i need the answer for as well), that writeup you had posted would've been clutch!
[Nexus 5 Q&A, Help & Troubleshooting] jt3:
Yeah, sorry. I posted them, then started thinking whether I'd ever actually done it with a custom recovery. Here are the steps for side-loading with a STOCK recovery. I'd be curious to see if it works with custom. I KNOW it works to install the OTA update (which, you'll need to download, so... not technically an OTA, but you get the idea), since I always seem to be at the back of the OTA list, so I never wait. Once the OTA zip is posted, I've always side-loaded it.

Download the update.zip from Google to your PC that you would like to install on your Nexus.

Move the file into your Platform-Tools folder.

Plug in your android device to your Windows machine. Make sure USB Debugging is enabled.

To test that you have adb up and running, and that your device is recognized, open a command prompt and change to the folder where ADB is installed.

Type: adb devices

You should get a serial number followed by “device.” (like this: 0a1b2c3d4e5f6789 device). This shows that you have a good connection to your device.

Still at the command prompt, type:	adb reboot bootloader

Your device will now reboot to the bootloader.

Use Volume Down on your device to until you see “Recovery.”

Select it with the Power button.

Your device will boot to an Android logo with a exclamation mark.

To jump past this, press Volume Up and Power at the same time (Hint: Push Power first, then push Volume Up).

You will now be in stock recovery.

With Volume Down, highlight “apply update from ADB.” Press Power to choose it.

Back to your PC command prompt, type:	adb sideload <filename of update.zip>

If your adb is working properly, you should see the file transfer to your device in adb.

Once that finishes, your device will begin to update. Be patient, it takes a bit.

Once it has finished, simply reboot and enjoy the update.

EDIT: In my original response post, I'd noted that the OP was obviously familiar with ADB, since he'd rooted his Nexus, I left that out of this post, so if you're wondering what the heck ADB is, that's why this post seems incomplete. ADB is part of the Android SDK. There are many other threads that cover its installation and use, but it's a good tool to have, even if you don't root (for side-loading updates, via the above steps, for example... no root required!).
[Nexus 5 Q&A, Help & Troubleshooting] shampiaj:
That would be key if this works... guess we shall have to wait and see. So with this method you theoretically won't have to unroot/re-root or lose any data/settings, correct?
[Nexus 5 Q&A, Help & Troubleshooting] jt3:
If it works, that's correct. ADB side-loading works on a stock, unrooted device (even with locked bootloader), so it doesn't mess with anything. It's possible that it won't work with a custom recovery. Even if it does, you may lose root in the process, but since rerooting your phone doesn't wipe the data (since the bootloader is already unlocked), that wouldn't be a big deal.

Also... even if it DOESN'T work, as stated before, it's unlocking the bootloader that wipes your device, so flashing a stock recovery THEN following these steps should certainly work with no data loss. Having said that... a nandroid backup is always your friend.

---------- Post added at 12:34 PM ---------- Previous post was at 12:11 PM ----------

Hate to respond to my own post, but after doing some checking, it looks like adb sideloading will still work with a custom recovery, assuming your recovery supports it. Both TWRP and CWM supposedly have supported this for quite awhile, so any version new enough to work with a Nexus 5 should certainly work.

Keep in mind that sideloading is not the same as flashing a custom ROM. Think of it more as a manual way to launch an update. So... you'll need to comply with any prerequisites of that update. So... say you're flashing from KRT16M to KRT16Z (or whatever). You'd need to get the correct KRT16M-to-KRT16Z update for your device. That update is certainly going to assume that you're bone-stock, so if you've added any mods or otherwise screwed around with your system files after rooting, the update may fail, or it may simply undo your mods (including unrooting your device). As I said before, a current nandroid backup is always your friend.
[Nexus 5 Q&A, Help & Troubleshooting] shampiaj:
Yeah, I'm stock/rooted but have flashed some mods. Luckily I keep all the .zip files so it sounds like the worst case scenario is that I'd have to re-flash the mods and re-root, which isn't a big deal. And I always make a nandroid before I do something. I'm more worried about data loss since it's taken me weeks to get to where I am now :)

Thanks for all this information, dude.
[Nexus 5 Q&A, Help & Troubleshooting] nikon120:
There's going to be boat loads of these exact same threads all over General, Q/A and Development when the update is released. Not sure why there isn't a sticky pertaining to OTA updates with regard to root, recovery, etc to curb all these posts.

To the OP, just use ADB and manually flash the images you want. Then simply flash SuperSU in recovery. Done.

If you don't know how to use ADB, then you need to do yourself a favor and learn about it. It'll save you time in the long run and you'll realize that GUI and CLI toolkits aren't necessary.
[Nexus 5 Q&A, Help & Troubleshooting] AceKingNYC:
This is super clutch ! I thanks alot for this

Im rooted/unlockled BL and have TWRP. I havent done ANYTHING else, not even Titanium backup for fear it would affect my ability to OTA. So it seems that I should be good right?
[Nexus 5 Q&A, Help & Troubleshooting] TJCacher:
I will almost certainly sideload the update, as I've never had a device get an OTA less than a week after it has gone live.

Assuming a bone-stock, unrooted Nexus 5, should I consider returning the phone to the factory-set Dalvik JIT instead of the ART compiler (been using this since day one) prior to side loading the downloaded OTA update (when that becomes available)?
[Nexus 5 Q&A, Help & Troubleshooting] l3s:
Guys, maybe I missed something, but I did a totally different thing on my Nexus 7. When The first release of 4.4 released, I flashed manually with flash-all.sh. Then I flashed TWRP, and rooted my N7. Couple of days later I received OTA update, I didn't do anything just clicked to the flash update. It is reboot my device, and the OTA successfully installed automatically from the TWRP, and rebooted my N7. After this I reboot my device to TWRP and flashed the superuser.zip. I rebooted the N7 and everything works well.

This way is not possible to receive and install the next OTA for N5?
[Nexus 5 Q&A, Help & Troubleshooting] jt3:
Okay, got the 4.4.1 update. Here's the scoop.

My N5 is unlocked and rooted with CWM. I've installed one root application, which increases my vibrate intensity to 100% (N5 is defaulted to 63%), otherwise, i'm bone stock.

Applied sideload via directions I posted previously. There are a couple steps that change due to the different recovery, but they were easy to figure out (like, where to choose "update from sideload"). Once I rebooted after the sideload, I got the "Android is upgrading" message (good sign). Once it finished, I was running 4.4.1. (KOT49E).

I did lose root though. A quick reboot into recovery mode showed that I'd lost CWM too, and was back to the stock recovery. Reinstalled CWM and rerooted. Back to normal.

Here's the link, for anyone who wants it: KRT16M to KOT49E Update.
[Nexus 5 Q&A, Help & Troubleshooting] thekow:
I have it on root and CWM also. I get to the step of install from sideload. I use CWM to say "install from sideload" and it starts ADBd but i can't connect to it via the pc. If i am in just android i can ADB. So something is up there.
[Nexus 5 Q&A, Help & Troubleshooting] WiteFlash:
So steps 13 and 14 in your list were done in CWM recovery instead of the stock recovery, correct? So if you're attempting the sideload using a custom recovery (I have TWRP), step 14 will be just choosing "apply update from ADB" or similar depending on which recovery you use. Everything else should be the same. Just wanted to make sure I understood your steps before attempting it myself.

Thanks!

---------- Post added at 01:12 PM ---------- Previous post was at 01:02 PM ----------

Alternatively, could we just grab the stock recovery image for 4.4 and reflash that using fastboot and apply the OTA when it lands on the phone? I'm thinking about doing that for my wife's Nexus 4.
[Nexus 5 Q&A, Help & Troubleshooting] BCSC:
Has anyone else lost 'reboot' from the power menu? I did have the Advanced 4 way reboot menu mod installed, but restored stock menu before TWRPing the update. It this a side effect of that or just 4.4.1?
[Nexus 5 Q&A, Help & Troubleshooting] WiteFlash:
OK. So 4.4.1 is up and running, but I didn't sideload it as outlined by jt3. Here's what I did:

Preparation

:

Downloaded platform tools zip from the following post and extracted the folder onto my desktop. The attachment is at the bottom of the first post: http://xdaforums.com/showthread.php?t=2010312

Downloaded the latest recovery image of TWRP for the Nexus 5 (hammerhead) from their website and placed it in the platform tools folder on the desktop. I renamed the file twrprecovery.img so it was shorter and easier to type later: http://teamw.in/project/twrp2/205

Downloaded the OTA zip linked by jt3 in post #17 and transferred it to my phone.

Downloaded the latest SuperSU from the following post and transferred it to my phone. http://xdaforums.com/showthread.php?t=1538053

Updated TWRP

Rebooted phone into bootloader mode (by turning it off, then holding volume down and pressing and holding power).

Plugged phone into computer. Windows initially failed to install the drivers. I got the drivers from part A of this post: http://xdaforums.com/showthread.php?t=2010312

Flashed the TWRP recovery to my phone using fastboot --> I opened the platform tools folder on my desktop, right clicked in the empty space and chose "open command window here." In the command window, I typed: fastboot flash recovery twrprecovery.img

Erased the cache partition by typing: fastboot format cache <--- not sure if this was necessary

Rebooted by typing: fastboot reboot

Flashed the OTA

Used this post from the Nexus 4 forum as a guide: http://xdaforums.com/showthread.php?t=2145848 . EDIT: the Nexus 5 thread is here: http://xdaforums.com/showthread.php?t=2523217 . I was Scenario #2, so I followed Section B.

Booted into recovery (TWRP)

Flashed the OTA zip file by choosing "Install" and picking the OTA zip file. This may take a minute or two.

When it completed, I was still in TWRP and immediately flashed the SuperSU zip (same method as with the OTA zip) to make sure I had root.

Rebooted the system

I expected to lose the TWRP recovery after the reboot, but it actually stuck around after the update. Although this may seem more complicated than the adb sideload method, it really isn't that bad, especially if you already have an updated version of your custom recovery. It's basically just applying the zip in the custom recovery and reapplying root.
[Nexus 5 Q&A, Help & Troubleshooting] jt3:
A couple things here.

First, the stock power menu doesn't have "Restart." That came form that "4 way" app, which requires root, which is likely lost when you upgrade, so the first thing to check is whether or not you still have root and, if necessary, restore that.

Second, any mod that makes system level changes when it installs (as a lot of root applications do), can be reverted by an update such as this. So, if you DO have root, but this app still doesn't work, try uninstalling and reinstalling it. That should do the trick.

Of course, it's always possible that something in 4.4.1 is different, and the app no longer works. If the above two steps don't fix it, you'll probably have to wait until the app is updated by the dev.

As to some other comments:

Yes, my instructions assume a stock recovery, and while they're still more or less valid for TWRP and CWM, anything actually referring to actions performed in recovery mode will have to be adjusted. Mostly, this means finding where you choose to install via sideload.

Also, the install from zip is also a valid method, but it's trickier, because all of the recoveries differ. Some only let you choose files named "update.zip," others let you select from a list. Not to mention, on my Nex5 with CWM, finding the "sdcard" directory is tricky (it's actually under "\sdcard\legacy\0"). There are simply way too many variables to try to list in a set of instructions, whereas the sideload instructions are pretty straightforward. In short, there are many ways to go about this. Once you find a way you like, do that.
[Nexus 5 Q&A, Help & Troubleshooting] WiteFlash:
Found this thread by El Daddy in the general section:

http://xdaforums.com/showthread.php?t=2523217

I always referred to the Nexus 4 counterpart to this thread when I had that phone and needed to apply updates. I didn't initially find the one above probably because the Nexus 4 thread is in Q&A/Troubleshooting and the Nexus 5 thread is in General. Anyway, if you're reading this thread and still can't figure things out, I would visit the thread above since the directions go over multiple situations and they are more complete.
[Nexus 5 Q&A, Help & Troubleshooting] Pumpino:
I've tried flashing the update on my N4 and N5 in the latest TWRP, and it fails on both. I'm running stock 4.4. The only thing that could be interfering with the update is the fact that I have the Xposed Framework with GravityBox and Advanced Power Menu instaled on both handsets. I disabled all of these, and then even uninstalled them, so that changes were reverted, and the update still fails. Any tips?
[Nexus 5 Q&A, Help & Troubleshooting] jd1639:
It's 4.4.1
[Nexus 5 Q&A, Help & Troubleshooting] WiteFlash:
I don't use either of those, but my guess is that the changes weren't fully reverted, leaving behind some change in the system that the OTA doesn't agree with. Visit El Daddy's thread here (and subscribe to it while you're there):

http://xdaforums.com/showthread.php?t=2523217

I would consider you Scenario #3, and I think Special Scenario #1 (2nd post on the above thread) would probably work for your situation. Basically it involves (re)flashing the 4.4 system.img and boot.img so that the 4.4.1 OTA will update successfully. Just be sure to use the correct OTA file for the N4 and the N5 since they are different.
[Verizon Samsung Galaxy S 4] m1k3d:
I recently just purchased a tablet from verizon with a data plan. I am wondering if I can take the 4G LTE sim card from my tablet and put it into a verizon Galaxy S4 that has a bad esn. If it works I know that it would only receive LTE and not 3G or voice which is fine because I use google voice and make calls via Voip.

From everything I have researched I think it should work but I am looking for someone that has put a Verizon LTE sim into a verizon phone with a bad esn to verify that it does or does not work.

Thanks in advance!
[One (M7) Q&A, Help & Troubleshooting] Sebz4n:
Hello!

I am using the smart launcher pro, which doesn't have the folder support I desperately need!

I have tried half of the apps on the play store, but they are all old and have the Damn menu 3-dot at the bottom when i open the folder, which is really annoying!

Also it doesn't support Widgets on the front page so I need an app that can open the folder via a shortcut

I am using 4.4 Play Edition
[One (M7) Q&A, Help & Troubleshooting] GinLemon:
Hi, I'm the developer of Smart Launcher. Some hours ago I released a new version of SL Pro that allow to create folder in the flower, the update is rolling out and if you didn't receive it yet, probably it will come tomorrow, just wait :)
[Android Apps and Games] nr1:
Hello,

please check my latest app called 'Clear Cache':

With Clear Cache you can clear all the Android caches on your device. Just hit the button and the corresponding cache on your device will be cleared. This can speed-up your device and of course it also helps to get more free internal memory.

Features:

-Clear App cache

-Clear Partition cache (needs root)

-Clear Dalvik cache (needs root)

-Show the current sizes of all those three caches (needs root)

Google Play

Maybe it's useful to someone :)
[Android Apps and Games] mauam:
Very useful indeed. Thanks:good:
[Android Apps and Games] sinkster:
Seems pretty effective. Nice and simple too. Thanks.
[Android Apps and Games] nr1:
thx for your replies :)

On my old android device with low free internal memory clearing the caches helped to speed to it up a bit.

That's why i created this app finally ;)
[Android Apps and Games] mindfck1337:
after clearing dalvik im stuck on my boot logo (N7000 4.1.2 XXLT4) :/

is it building a new cache or what because after i cleared the cache the phone was really laggy and thats why i "killed" it so now its not booting :/ but i still have access to cwm
[Android Apps and Games] flexihopper1:
Thanks man
[Android Apps and Games] nr1:
The app only clears the caches (=removes the cached files).

If you cleared the Dalvik-Cache the first boot after clearing could take a while, because Android will create this cache again. For example on Android 4+ this rebuilding process then is shown as something like "Optimizing Apps".

App and partition cache will be rebuilt on the fly by Android (if the system needs something cached).
[Android Apps and Games] mindfck1337:
yup thought that

it booted now after waiting for like 10 minutes and its faster now :)
[Android Apps and Games] nr1:
ok, great :)
[Android Apps and Games] archz2:
I got fed up with Clean master app. Should I use this one instead or is there a better one too?