yashsingh1/xdaforums huggingface dataset:
[Moto X General] tyrone1:
Trying to update to 4.4.4, disabled/uninstalled xposedframework and all its modules.

flashed stock recovery

I tried to update, it starts installing and maybe 1/3 of the way there it says error and reboots back into system.
[Moto X General] EvilDragonEX:
flash stock system and try again...
[Moto X General] tyrone1:
Thanks my friend, flashed back to stock 4.4.3 and now update is going through....
[Moto X General] davedigerati:
wanted to try this instead of the stock recovery path, flashed from twrp to philz, uninstalled xposed, back to recovery & found update in cache, but fails on "getprop("ro.product.device") == "ghost", which is weird since I am on a stock ROM 212.44.21.ghost_row.Retail.en.US. Oh well, time to go looking for a stock recovery I guess... just my experience in case anyone else is trying/wondering
[Moto X General] EvilDragonEX:
thats because you can only do OTAs by stock recovery
[Moto X General] davedigerati:
I know that's how it traditionally works, but post http://xdaforums.com/showpost.php?p=55746068&postcount=78 had me hoping otherwise;)
[Moto X General] xd1936:
The update is now public. OP has been updated.
[Moto X General] mandrsn1:
It did work for me with PhilZ. However, I didn't flash from the recovery. I used flashify, and just let flashify know I was using a CWM-based recovery. It proceeded to flash correctly.
[Moto X General] quickstang:
I may try it this way. I flashed back to stock recovery & when I got in the fast boot section & hit vol up for recovery, I got the Android with red triangle & exclamation saying No Command below it. Not sure what that's all about.
[Moto X General] quickstang:
Tried the above & the error I get is... Verify current system... "/system/framework/core.odex has unexpected contents.
[Moto X General] da_enlightener:
I get something similar "/modem/image/dsps.b00" has unexpected contents

I'm back to stock recovery and I enabled all the apps that I had previously disabled.
[Moto X General] quickstang:
I re enabled everything as well. I did have a modded play store, so I reverted to stock. Still tried flashing with Philz & no luck. Same error. I'm going to try & flash stock recovery & try again.

If not I may have to reflash 4.3.3

No luck. Booted into fastboot, selected recovery & then I get the same deal as the first time. Android on his back, red triangle with exclamation & No command in text below it.
[Moto X General] captaingrandpa:
Are you holding the Volume UP key for 10-15 seconds and then tapping the power key while still holding the Volume UP key? Try doing this when you get to the little dude on his back

---------- Post added at 04:49 PM ---------- Previous post was at 04:39 PM ----------

I'm running into a problem with my systemUI.apk from stock 4.4.3 having "unexpected contents." I assume something I did rooted caused some change in the file. I've since wiped/factory reset the phone. My question is can I just steal the systemUI.apk.p file from the 4.4.3 OTA and drop it in the Priv-apps folder on my phone and then sideload the 4.4.4 OTA?

thanks!
[Moto X General] SamuriHL:
A lot of people seem to be struggling with this OTA. (You custom recovery guys and gals are just a glutton for punishment IMO).

1) Grab the 4.4.3 FXZ

2) Grab RSD Lite 6.1.6

3) Optionally grab my RSD Flasher utility

If using RSD Lite:

4) Extract the FXZ, edit the TMO_RETAIL_XT1053_4.4.3-KXA21.12-L1.21_MR4_CFC.xml file with Notepad ++, and remove this line:

<step operation="erase" partition="userdata" />

5) Save the TMO_RETAIL_XT1053_4.4.3-KXA21.12-L1.21_MR4_CFC.xml file

6) Flash with RSD Lite

If using RSD Flasher:

4) Run the RSD Flasher, select the FXZ, and then use the KEEP DATA option

Once that's done, flash the OTA. Flash your custom recovery back, then flash supersu zip to re-root.
[Moto X General] mrvirginia:
apparently your core.odex is not the 4.4.3 one. when verifying, it is basically checking to make sure it's the file that it should be for the patch

same as above except you need a dsps.b00 (this is, according to the directory you listed, a modem part). either you don't have an XT1053 or you have flashed another modem

this is why i do a full system.img pull before messing around (with the exception being root). when time to update to a new version, i create a zip file that contains the framework, priv-app and app parts and include any other directories i may have tweaked, and i flash it to get me stock again.
[Moto X General] captaingrandpa:
For starters, RSDLite is out, I'm on Mac (I could run a VM I guess but that's an extra step I'd rather avoid)

Before I go through the trouble of figuring out how to execute the .jar file, can I just mfastboot flash the system.img alone to solve my problem? do I need to flash everything in the zip?
[Moto X General] SamuriHL:
You could use my House of Moto as it works on the Mac. But to answer your question, yes, you can just fastboot system.img and recovery.img from the FXZ and then take the OTA and you should be good to go.
[Moto X General] captaingrandpa:
That certainly did it.

Thanks for all your help! I'm up to 4.4.4 finally.
[Moto X General] SamuriHL:
Awesome! Glad I could help!
[Moto X General] quickstang:
This worked for me. I used the flasher, then flashed the OTA zip from the link. After that I downloaded the Moto X toolkit, launched command prompt, adb reboot bootloader & then fastboot flash recovery (philz touch recovery) then went into recovery, flashed SuperSU 2.02 & all is well.

Also all data is in tact.

I did have to read your tutorial on your site to figure out how to use RSD, but it was straightforward with pictures & worked flawlessly. Thank You!
[Moto X General] SamuriHL:
You're most welcome!
[Moto X General] Bendezium:
Smooth sailing

I had no problems following this method on a Windows 8 machine and I did not lose root:

Disable Xposed modules

Uninstall Xposed framework (not the app, the framework from within the app)

Flash stock 4.4.3 recovery using fastboot. I used the recovery file in 4.4.3 FXZ posted by quickstang.

Install update OTA.

Flash back to twrp recovery with fastboot.

Reinstall Xposed

Renable modules.
[Moto X General] tKoHaXoR:
I was on T-Mobile 4.4.3 rooted and disabled xposed and decided to flash system.img and recovery.img from FXZ to not have issues flashing the 4.4.4 ota zip.

Did the following.

fastboot flash system system.img

fastboot flash recovery recovery.img

Once i flashed system.img and recovery.img it would no longer boot to either recovery or system anymore. Tried flashing back a custom recovery but it just gets stuck at the Moto splash screen.

Can anyone help me get back to a bootable system?

Edit: Im still able to get into my bootloader and I am bootloader unlocked.
[Moto X General] SamuriHL:
What was the output when you flashed recovery and system? And I'm HOPING you used motofastboot not just regular fastboot from the platform tools....right? It matters. A lot.
[Moto X General] tKoHaXoR:
I used regular fastboot

Here is the output

C:\Users\Server\Desktop\Work Station\Android\sdk\platform-tools>fastboot flash system C:\Users\Server\Desktop\system.img

(bootloader) Variable not supported!

target reported max download size of 805306368 bytes

Invalid sparse file format at header magi

error: write_sparse_skip_chunk: don't care size 89259280 is not a multiple of the block size 4096

sending sparse 'system' (751978 KB)...

error: write_sparse_skip_chunk: don't care size 89259280 is not a multiple of the block size 4096

error: write_sparse_skip_chunk: don't care size 89259280 is not a multiple of the block size 4096

OKAY [ 49.722s]

writing 'system'...

(bootloader) Sparse image is malformatted

FAILED (remote failure)

finished. total time: 86.301s

Edit: Downloaded mfastboot now. So just reflash using mfastboot?

Edit 2: Used mfastboot and all is good. Lesson learned. Don't use regular fastboot (I'm sure you guys already knew this, but for those who don't make sure you use mfastboot so you don't panic and sweat like I did)
[Moto X General] SamuriHL:
Yup. You're good to go and that's what I figured (and hoped) the problem was. Easy fix. :)
[Moto X General] tKoHaXoR:
Thanks [MENTION=2812087]SamuriHL[/MENTION]

I'm now on 4.4.4 but now I have another issue now with custom recovery not sticking.

I've tried both fastboots to flash these recoveries

mfastboot flash recovery philz_touch_6.57.9-ghost.img

and

fastboot flash recovery philz_touch_6.57.9-ghost.img

When i try to reboot to recovery from bootloader menu it simply boots to system

When i do:

adb reboot recovery it boots to stock recovery now

Am i missing something?
[Moto X General] SamuriHL:
Yes. You are indeed.

You have to flash recovery from AP Fastboot mode as you know. DISCONNECT IT FROM USB once it's flashed. This is the key. Then boot directly to recovery WITHOUT BOOTING SYSTEM first. That is the second key. Once you do that, you're golden.
[Moto X General] tKoHaXoR:
[MENTION=2812087]SamuriHL[/MENTION]

Seriously all I was missing was unplugging the darn thing haha man this Moto is one picky bastard. Thanks again!
[Moto X General] SamuriHL:
HAHAHA. Yea, it can be a bit touchy.
[Moto X General] tom_goro:
hi, I've got Dev. Ed and tried to follow exact same steps as tKoHaXoR. I have never had any custom ROM installed and never tampered with modem (see below).

I flashed system.img and recovery.img from the same source (FXZ). my OTA failed to flash though - "/modem/image/dsps.b00" has unexpected content and flash aborts.

xposed is uninstalled, recovery is stock. I reflashed the system.img again, just to be sure, unplugged USB cable, rebooted, redownloaded OTA ... and failed again. system boots fine, however clearing cache from stock recovery hangs the phone.

any ideas how to proceed towards 4.4.4?
[Moto X General] tKoHaXoR:
[MENTION=5686467]tom_goro[/MENTION] Are you on the T-Mobile 4.4.3 stock rooted rom? Maybe your baseband modem isn't updated? What baseband modem do you currently have?

My device has the MSM8960PRO_BP_2323.038.123.00R baseband

That is the baseband I was on when I did the update and didn't receive the "/modem/image/dsps.b00" has unexpected content"

Verify the baseband you are on and if it doesn't match up with the one I have that can be the cause of that error message and you will need to update your baseband before applying the 4.4.4 update.
[Moto X General] tom_goro:
Sorry, don't remember original baseband - I flashed modem just now (extracted from FXZ), Currently my baseband is the same as yours and I have signal as well. I am not sure what it read before, could very well be the same.

I was on stock ROM (not sure how much Dev Ed. and T-Mob differ, my understanding is that they are the same).

I will now try to take OTA again and report back.

i am now at 4.4.4. must have been corrupted or old modem file. thnx again.
[Moto X General] tKoHaXoR:
Great just double check your root since my root was removed when I updated.

To fix this I just reflashed TWRP 2.8.0.1 recovery.img after i succesfully updated. Unplugged my phone after reflashing recovery and booted to TWRP recovery. A message popped up that super user wasn't working and TWRP reflashed superuser files automatically and I rebooted to system and finally everything was back to normal. Enabled xposed and all my modules and all is well in the world.
[Moto X General] toiin3ron:
Hi, I've installed the OTA, but now I want to install TWRP... but didnt work.

I already try with the mfasboot and the fastboot inluded in the Android SDK, it sems be ok... but dont change the stock recovery.
[Moto X General] tom_goro:
[MENTION=3539089]toiin3ron[/MENTION] did you try this?
[Moto X General] productofusa:
hmm mfastboot flashed stock recovery then update and got an "error: package has no android-info.txt or android-product.txt" for some reason the ota wont flash, tried twice?:confused::confused:
[Moto X General] zarxic:
Did you use regular fastboot or the motorola fastboot?
[Moto X General] SamuriHL:
For recovery it doesn't matter. motofastboot is required when flashing system because it needs to be broken into chunks when sent to the device. Recovery is small enough to not need that.
[Moto X General] Bendezium:
I used the fastboot that comes with Android SDK.
[Moto X General] kcbboy:
I'm still having problems trying to install this. I disabled xposed and flashed the stock recovery and it still fails. I noticed my baseband is not the same as what's posted on the screenshot in this thread http://xdaforums.com/moto-x/development/rom-stock-flashable-t-mobile-t2773675. Would having a different baseband cause it not to flash and if so where can I get just the baseband itself?
[Moto X General] tom_goro:
[MENTION=2660256]kcbboy[/MENTION]: in my case old modem file prevented me taking OTA - it failed to flash. Updating modem did the trick. You can get modem files in the FXZ image posted earlier, then manually flash them.

Be advised that in case you flash incorrect modem files you might screw your signal (i.e not having any). Thus the same applies:
[Moto X General] kcbboy:
the droid developers site does not seem to be working??? is there another link?
[Moto X General] kcbboy:
can someone please mirror the FXZ if you have it please? the droid developers.org is down right now.
[Moto X General] EvilDragonEX:
https://drive.google.com/folder/d/0B9OOu95ubGiUaktjV196UVdnblk/edit

download the TMO_Retail... ignore my other files (4.4.4 is still not available yet)
[Moto X General] c1nd3r:
what do you do with this zip file?
[Moto X General] SamuriHL:
Install it in stock recovery.
[Moto X General] c1nd3r:
how, what are the commands? it is in zip form.
[Moto X General] SamuriHL:
These instructions have been posted to death. A simple search could have given you this information...

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

Those instructions are for the Nexus 7 but the principle is the same....

o) Reboot into recovery

o) When the android icon comes up, press volume up + power to bring up the recovery menu

o) Connect the phone to USB

o) Select the adb sideload option

o) From your PC, open a command prompt to where you downloaded the OTA zip. NOTE: If ADB is not in your path, copy the OTA zip to where you installed platform tools and open the CMD prompt there.

o) Run the command: adb sideload Blur_Version.212.44.21.ghost_row.Retail.en.US.zip

Allow it to install.
[Moto X General] c1nd3r:
thanks... done tons of patchings since the original Nexus and never heard of "sideload" until now.
[Moto X General] gcbxda:
where exactly can you find the 4.4.3 official download?

when i go to that Motorola Dev edition stock image support site i only get 442 and 422!

---------- Post added at 12:24 PM ---------- Previous post was at 12:14 PM ----------

anyone knows the origin/source of RDS lite? I'm on Linux, but even if on windows I'd have reservations of random binaries...

thanks
[Moto X General] SamuriHL:
Then flash it with fastboot. RSD Lite was leaked from Motorola by those who have access to it. RSD Flasher is a java utility I personally wrote that works in conjunction with the FXZ and RSD Lite to flash customized versions of the FXZ on the fly. But if you have reservations about it, you can manually flash it with fastboot or you can use my House of Moto scripting that has a Linux/Mac version.
[Moto X General] Razgriz:
Can I unzip this over the 4.4.3 full firmware and use it to flash? Having issues with my phone and the 4.4.4 full firmware isn't out yet.
[Moto X General] SamuriHL:
Ummmmmm. No.
[Moto X General] jshinn1:
Has there been any news on the 4.4.4 FXZ seems like its taking awhile.
[Moto X General] SamuriHL:
The SBF site hasn't been updated in over a month and some change, so, no.
[Moto X General] jshinn1:


Dang it lol thanks for the response.
[Moto X General] n0obpr0:
Hello,

I tried installing the OTA posted in the first page and I kept getting an error. I'm rooted, unlocked, and my phone is a tmobile moto x running stock 4.4.3. I keep getting an error mentioning something about my SystemUI.apk. I have stock recovery installed.

I did some research and it looks like I get that error because I used Softkeyz and I forgot to back up my SystemUI.apk. Can somebody help me get the 4.4.3 stock SystemUI.apk? Thank you in advance
[Moto X General] gcbxda:
i'm pretty sure the 'flash over 4.4.3' was covered somewhere in this lenght thread... but to solve the issue for good, please, participate on this http://xdaforums.com/moto-x/general/please-part-to-official-4-4-4-4-4-3-t2913603

we will only get 4.4.3 and 4.4.4 official images if we ask for it.
[Moto X General] kenosis:
I installed 4.4.3 first. connected WiFi and updated to 4.4.4 via system update. Currently, I am running Stock 4.4.4, Stock kernel and recovery with xposed installed. Battery life is very good.
[Moto X General] SamuriHL:
I have a concern, guys and gals. Without a proper FXZ, installing custom recovery is problematic because there's no stock recovery from 4.4.4 for you to install on the next update.
[Moto X General] Carrzy:
running into same issue. successfully reverted back to stock for OTA but cannot install twrp. device is unlocked.

Thanks in advance guys!
[Moto X General] tom_goro:
Are you sure that after flashing TWRP you are actually booting to recovery instead to system? Plenty people (myself including) boot accidentaly into system after flashing recovery. Make sure you do not press Power button but Volume Up when selecting it.
[Moto X General] texm3x:
OK so I see a bunch of people are having issues w these files

OK I read op and it says he's rooted and downloaded by moto but my question is what tool did u upload with if any?? Or did you simply use fastboot commands if so which ones worked for you ?? :confused:

BTW ur the man of success if you can help me save time figuring it out I always love to donate or return favors.:highfive:
[Moto X General] texm3x:
This update is only for tmo only phones I assume it erased my modest files but I found way better!!! To all you haters that couldn't help :p

For the unknowing ones email me I'll send u copy 4.4.4 msd lite flashable.:good:

Not vzn crap w slow 1g services. Lol
[Moto X General] gavron:
Much appreciated. One minor nit: you do not have to be running the stock recovery. If you choose not to run the stock recovery here are the easy suggestions:

0. Make a complete backup

1. use file-roller (linux) or your other tool and

a. remove the checkes for product-id or device-type to be "ghost". My TWRP ids as XT1060.

b. remove the stuff that deals with recovery, recovery.img creation, recovery restore scripts, etc.

c. I like the modem version I had on 4.4.3 so I didn't flash it with moto-fastboot which also meant the modem check files need to be commented out or removed

2. Copy the updated file to /sdcard

3. Reboot e.g. TWRP/CWRM in recovery and install the zip from where you put it in step 2

4. If you have any errors, wipe and restore from step 0

E

VZW XT1058 4.4.4 TWRP

TMO XT1060 4.4.4 TWRP <-- I ran this on CM, then Liquid... and honestly, when it comes time to move up to Lollipop I'll probably use the TMO image on both phones. Battery life and hands-free access make the stock images superior. TMOs lacks the bloat VZW has.
[Moto X General] MC FLMJ1G:
If I already have 4.4.4 Tmo and I simply want to restore to stock, this should work, right?

Thanks in advance.
[Moto X General] EvilDragonEX:
no... it wont work... you will have to flash stock zip

this is just an OTA update not a complete system
[Moto X General] MC FLMJ1G:
Thank you. Trying to find full 4.4.4 and cannot find :(
[Moto X General] SamuriHL:
https://motorola-global-portal.cust...edirect/standalone/bootloader/recovery-images

Did you try motorola? :D
[Moto X General] MC FLMJ1G:
ROFL

I always thought it said 4.4.2!!! I have no clue why I see it as 444 ROFL

I need sleep heh heh

Thanks
[Moto X General] SamuriHL:
It was just recently posted within the last couple weeks.
[Moto X General] crusher1908:
So, if the lollipop update comes and i'm on a rooted 4.4.4, just need to flash this version and i'll be able to update without issues to 5.0? thanks!!
[Moto X General] SamuriHL:
Yup, exactly!
[Moto X General] trdrjeff:
Do recovery images erase user data? The misses X is stuck on the M logo water drop animation. I've wiped cache but no change. Hoping not to lose all her data.
[Moto 360] Deathsnuggle:
I'm noticing from time to time my 360 is randomly waking up without any reason. Similar to a wakelock on a phone. I've tried resetting my phone and my device to no avail. Anyone else experiencing this?
[Moto 360] akellar:
It's likely just responding to movement. Also, that is not what a wakelock is. A wakelock keeps a device from going to sleep, has nothing to do with display turning on or not.
[Moto 360] KidCuda:
If anything I can't keep my watch awake long enough *rimshot*

When I had the G Watch, I noticed that DND mode would actually keep the screen off no matter what, until you physically touched it. I wish it was the same for the 360.
[Nexus 4 Q&A, Help & Troubleshooting] TheRedViper:
i have a nexus 4 running CM 11 M10 and i flashed the roam around 2 weeks ago and now this strange bug has showed up, the wifi doesnt work.

The device connects to wifi but the connection is only partial, the icon doesnt go from brown to white and thus i lose access to many features like the play store and google now. This bug has showed when my phone was running Paranoid Android and CM 11 M8, has anyone else had this issue? It happens for mobile data as well. Anyone know a fix?

My phone has been factory reset and everything. Ive also recently installed and used freedom, could that have caused the issue?
[Nexus 4 Q&A, Help & Troubleshooting] Ravzz_Sv:
Are u using any custom kernel ?
[Nexus 4 Q&A, Help & Troubleshooting] paultbear:
network issues

Uninstall freedom - that is directly using your network hardware -- if that doesn't affect the problem you could re-install it.

Have you tried it with another network router - or just on another network you have access to? You could restart your local router, clearing any ip assignments that may be blocking your phone from connecting.

IF you have access to your router and admin rights you could TEMPORARILY disable encryption to see if the problem goes away.

To test the likelihood of hardware failure, you might want to restore the phone to factory software -- NO custom roms/kernals no extra apps and then see if the problem occurs.

Cheers.. hope this helps
[Nexus 4 Q&A, Help & Troubleshooting] TheRedViper:
Well okay.

I uninstalled freedom but it didnt help, im still facing the same problem. and whenever i switch to a new rom this problem shows up. it doesntoccur initially but after 10 days or upto a month after i flash the rom. i faced it on Paranoid Android and 2 versions of CM 11. is it a software based issue? it occurs on all networks i try to connect to.
[Nexus 4 Q&A, Help & Troubleshooting] audit13:
Are you running the latest modem? I believe the most recent version is 1.03.
[Nexus 4 Q&A, Help & Troubleshooting] TheRedViper:
im not sure

as you probably noticed im a novice at this, i dont know how to check if mines the latest and how to update should it not be.
[Nexus 4 Q&A, Help & Troubleshooting] audit13:
Go to settings, about phone, and look under baseband. The last 3 digits will tell you the baseband. Mine says 1.03.
[Nexus 4 Q&A, Help & Troubleshooting] TheRedViper:
Yeah

Yeah! mines 1.02. how do i update?
[Nexus 4 Q&A, Help & Troubleshooting] audit13:
1.02 is a very recent modem and that probably isn't the problem. I suggest flashing back to a stock ROM and test it.

The radios are flashable from CWM or TWRP: http://xdaforums.com/nexus-4/general/ref-mako-modem-collection-t2087227
[Moto X Q&A] murso74:
Not sure where to put this, but i'd like to request a stock ATT rom flashable with custom recovery. figure since we got the BL ball rolling, it might be nice to get these out
[Captivate Q&A, Help & Troubleshooting] scottmcm:
Does anyone know if any of the KK ROMS out there will work with the Cappy's TV Out? I have tried a couple and the option is either not present or present but not available. (grayed out) I may just need to go on a DL/Flash bender but before spending all that time I wanted to ask the group here. Thanks!