yashsingh1/xdaforums huggingface dataset:
[Moto X Android Development] mrvirginia:
alright, i'll need some information since i'm not on the device.

for example, i've read that the bootloader is Motoboot.img (bootloader). is this still the case? i don't see this in the OTA zip

edit: this variant really doesn't need to worry about upgrading the bootloader. this process needs to be done for the following devices:

Locked Bootloader – Verizon, AT&T, Republic Wireless
[Moto X Android Development] cannondale0815:
Responding to my own post, the culprit is the Xposed framework (of course).
[Moto X Android Development] kpetrie77:
Probably better not to have multiple versions of this update anyway. Less confusing if there is one clear set of instructions and it will prevent someone for downloading and flashing the wrong version by mistake.
[Moto X Android Development] Iceman248:
I intend on using Xposed Framework when I finally root my new Moto X which will be running 4.4.2 before I do so. Is there something I need to know?
[Moto X Android Development] mrvirginia:
correct. i would do it for those devices and their OTA's instead.
[Moto X Android Development] cannondale0815:
You can use it for as long as you don't switch to ART.
[Moto X Android Development] Jayrod1980:
My question: is full release ota the same as the soak test ota? I would assume yes but you never know.
[Moto X Android Development] jimmypop13:
Droid life confirmed that it was indeed the same build as the soak test
[Moto X Android Development] kpetrie77:
I imagine it would be. Soak tests are supposed to be for final software.
[Moto X Android Development] Gus194:
I'm just waiting for Motorola to release the Factory Images for 4.4.2. I have the XT1503 but I updated to the UK 4.4.2 so I can't install this OTA. .-.
[Moto X Android Development] flashallthetime:
Let us know what happens, the UK boot loader is 30.B3 and T-Mobile has the 30.B4 boot loader for 4.4.2, wondering if you can't move from B3 up to B4 . I would like to add the info to my boot loader thread, if you don't mind , when and if you can flash the b4 boot loader

Sent on my Gummy running Lenoto X
[Moto X Android Development] SymbioticGenius:
Does anyone have the SBF files for T-Mobile 4.4.2?

MotoX GSM Developer Edition, Bootloader Unlocked, Rooted, Stock 4.4.2 Great Britain on T-Mobile !
[Moto X Android Development] geekabilly:
Have not seen it yet

tapped out via XT1053 DE
[Moto X Android Development] jakeo423:
Does this update fix all of the bluetooth issues people have with 4.4?
[Moto X Android Development] cannondale0815:
Any way to downgrade the baseband / radio in this to the 4.4 version? I have noticeably worse data reception with 4.4.2.
[Moto X Android Development] mistoffelees:
Can't speak for anyone else, but it fixed my issues with bluetooth!
[Moto X Android Development] :
Could I trouble someone for a zip file of the wcnss.* files in the modem partition of this update?
[Moto X Android Development] kpetrie77:
wcnss.b01, .b02, .b05, and .mdt were patched. The others remained the same as 4.4.

These are off the phone from /firmware/image/

https://www.dropbox.com/s/t5dhv3hohzipz7e/wcnss.zip

Sent from my fastboot oem unlock XT1053
[Moto X Android Development] sarshadd:
anyone with a rooted dev edition upgrade?

someone please confirm my understanding:

1)Flash stock recovery-- upgrade will not work with TWRP

2) Flash xposed disabler zip to get rid of all xposed modules.

Is there a way to back xposed up or something, so I can restore all my modules after the fact?

3) I don't have any weird permissions, system files, or frozen apps so no action needed.

4) Accept OTA and reflash TWRP. Root should remain and be unaffected.

Am I missing anything?
[Moto X Android Development] cajunflavoredbob:
Titanium Backup can restore all your Xposed modules with their data after upgrading. You'll need to reinstall Xposed Installer first, then restore the modules with TiBu.
[Moto X Android Development] jjl468:
I just took the OTA and I didn't actually uninstall any of the modules. I just uninstalled the framework via the app then flashed the disabler. Then, I took flashed stock recovery via Recovery Tools and took the OTA. After the update finished, I just went back into Xposed and re-installed the framework and all of my modules were working after a reboot with all of my previous settings saved.
[Moto X Android Development] psychohistry:
Ok so following the steps here lets you upgrade to 4.4.2 and preserve root but will you still have write protection off? Someone said on another thread that WP won't be off anymore if you upgrade to 4.4.2 which, among other things, means that Xposed framework won't work well/at all. Seeing as how my main reason for rooting was to use Xposed, I want to make sure I can still do that before deciding to upgrade to 4.4.2.
[Moto X Android Development] kpetrie77:
Assuming you are talking about with a locked bootloader? What specifically disables WP on 4.4?
[Moto X Android Development] psychohistry:
Yes, I followed the instructions for how to get root on 4.4 with a locked bootloader (i.e. I downgraded to 4.2.2 camera update, used RockMyMoto to get root, MotoWPNoMo to get write protection off, then SlapMyMoto to maintain root and WP off while upgrading to 4.4). I just want to know if I will keep WP off if I upgrade to 4.4.2 according to the method outlined in this thread.
[Moto X Android Development] zewone:
EDIT: I was able to fix my phone, but does anyone have the stock recovery.img for 4.4.2?
[Moto X Android Development] kpetrie77:
It did not change, use the 4.4 recovery.
[Moto X Android Development] Scotlac:
Absolutely brilliant KP!

I used the method that you outlined in your video and I didn't lose root or any data.

Thanks so much for taking the time to put this together for us!
[Moto X Android Development] sarshadd:
i tired to flash stock recovery from http://sbf.droid-developers.org/phone.php?device=0.

i picked the firmware that matches my current 4.4 build.

i used recovery tools to flash it and when i try to boot into recovery i just get the open android with the exclamation point and nothing else.-- sounds like the recovery flash didn't work properly, right??

i don't remember what stock recovery looks like, but im sure there is supposed to be some words and a little UI to do simple things like reboot and the like...
[Moto X Android Development] kpetrie77:
Worked fine, that is what you are supposed to see. Press/hold Volume Up and tap Power to bring up the stock recovery menu.
[Moto X Android Development] sarshadd:
Great! I uninstalled xposed framework from within the xposed framework app and rebooted to make sure it stuck. Is there anything else I need to do before I accept the OTA? Talking about a GSM Dev; unlocked and rooted.
[Moto X Android Development] kpetrie77:
Re-read everything and go from there if you're comfortable. If not, hold off and ask for clarification.
[Moto X Android Development] bongostl:
You will not be able to turn wp off if you upgrade.

You can use xposed by installing the framework and then doing a soft reboot from within the app. However, everyone you so a full reboot, you will need to reinstall the framework and do the soft reboot again.
[Moto X Android Development] kpetrie77:
Can you confirm if write protection is on or off post update? Thanks, K
[Moto X Android Development] Sangredelsalvador:
After getting myself in a pickle and kpetrie77 helping get back to stock 4.4, I get say that this method worked perfectly. 4.4.2 rooted and running well. Good job
[Moto X Android Development] Kenichi:
I can confirm that the locked boot loader does have write protection. Everything has been working accordingly though. Make sure all files and system are restored to stock, root will carry over however.

Just realized your from DFW area! Muhahaha weather is getting warmer, thankfully!

Kenichi
[Moto X Android Development] markwebb:
I have an unlocked rooted 1053. Upgraded fine but now exposed installer won't work despite repeated uninstalls and fresh installs.

Anyone else having an issue?
[Moto X Android Development] needleyepoke:
No mine works fine with xposed but I used an un rooted stock rom backup before updating to 4.4.2. Cleared user data and cache fully rebooted flashed twrp then rooted. Restored everything with titanium backup

sent from my XT1053 unlocked bootloader 4.4.2
[Moto X Android Development] DBBGBA:
Can this update be made into a flashable zip for custom recoveries?

I don't remember what files I changed from the system when I was trying to make tethering work so I can't go on with the standard OTA procedure.
[Moto X Android Development] ken1645:
Mine's unlocked rooted xt1053 as well. Xposed works fine after 4.4.2.
[Moto X Android Development] jakeo423:
I have a stock, unrooted moto x on att. Would this work to flash onto that since the phones are essentially the same thing, or would it screw things up? I'm just not sure. I'm just really wanting this update to fix my bluetooth problems. But any info or insight is appreciated.
[Moto X Android Development] kpetrie77:
Wouldn't flash, even if you wanted it to. Go back to the OP and check the link about patches and what they are.
[Moto X Android Development] scott62185:
I hope this isn't a stupid question or hasn't been covered already... I have a nandroid of my original stock build. Can I restore that and then flash this OTA from there? Thanks
[Moto X Android Development] kpetrie77:
Should work.
[Moto X Android Development] scott62185:
Cool. Thanks!
[Moto X Android Development] Gus194:
So have the T-Mobile 4.4.2 factory images been uploaded yet?
[Moto X Android Development] byt3b0mb:
Check here.. http://sbf.droid-developers.org/phone.php?device=0

And no the full sbf isn't available yet unless it is somewhere else

XDA Premium - Moto X
[Moto X Android Development] kpetrie77:
Not yet.
[Moto X Android Development] scott62185:
Question : When you say that you can't downgrade to 4.4 after flashing this update, do you mean that even if I restore a 4.4 nandroid I can't go back?
[Moto X Android Development] needleyepoke:
I was able to restore my 4.4 backup from twrp

sent from my XT1053 unlocked bootloader 4.4.2
[Moto X Android Development] flashallthetime:
OK now if you accept the ota you'll end up with a hard bricked device and do not flash this ota either, be warned

The only safe way to go back to 4.4.2 is flashing only the system.img and boot.img only

Or with a nandroid

Sent on my Gummy running Lenoto X
[Moto X Android Development] needleyepoke:
I went back to stock unrooted 4.4 with stock recovery accepted the ota. Flashed twrp, made a backup of updated 4.4.2... Then restored my twrp backup of 4.4. Then went and checked to see if I had an update and my phone said up to date.. Then restored 4.4.2

sent from my XT1053 unlocked bootloader 4.4.2

---------- Post added at 12:24 AM ---------- Previous post was at 12:20 AM ----------

I wouldn't suggest accepting update after already doing it though

sent from my XT1053 unlocked bootloader 4.4.2
[Moto X Android Development] flashallthetime:
Maybe moto got it right and it checks your boot loader, baseband version?instead of the os version, Or you just got lucky

Would not advice anyone to accept an ota after upgrading , hard bricks are known to happen

Sent on my Gummy running Lenoto X
[Moto X Android Development] needleyepoke:
Boy do I really hope luck had something to do with it. I could use some. Just anything you do with your phone double think it read read read before asking questions and backup

sent from my XT1053 unlocked bootloader 4.4.2
[Moto X Android Development] jeepon02:
I am not sure where to find the stock recovery file for US Cellular, I pulled the recovery.img file out Android 4.4

Blur_Version.143.44.2.ghost_usc.USC.en.US, and put it in recovery tools. I then tried to flash that "recovery.img" file and all i get is the android with the exclamation as well. nothing i can do from there except hold down the power and vol up to get the handset to reboot. any help?
[Moto X Android Development] kpetrie77:
That is what you are supposed to see. Hold Volume Up and press, not hold, Power to make the menu come up.
[Moto X Android Development] jeepon02:
Thank you, yes that does work, so here is what I get. I flash the recovery.img file with recovery tools, i then boot into the stock recovery. I reboot the phone and take the OTA 4.4.2 update and proceed with install. It starts to flash for about 30 - 40 seconds like normal then i get the android with the error, phone then automatically reboots and tells me the update was unsuccessful. I followed the video exactly from the OP. I am on 4.4, rooted with TWRP, and unlocked... what did i miss?

thanks all
[Moto X Android Development] kpetrie77:
You are missing or tampered with a system file. Recovery log should list which one.
[Moto X Android Development] jeepon02:
here is apart of the log file I found interesting - see attached
[Moto X Android Development] kpetrie77:
Winner.
[Moto X Android Development] jeepon02:
Oh yah, i had disabled an app with TiBu..... duh..... but I learned though all of this.. thanks for helping me...... props KP

---------- Post added at 11:40 PM ---------- Previous post was at 11:28 PM ----------

Looks like a made a mistake awhile ago, i uninstalled Synchronoss TEDC using TiBu and dont have a backup. what would be the easiest way to get that back?

thx
[Moto X Android Development] kpetrie77:
fastboot flash the 4.4 system image. Will need to reinstall superuser when done, but that will get you good.
[Moto X Android Development] Valnomien:
need stock kernel image

can someone tell me how do i extract the stock kernel image I can't find boot.img anywhere in this OTA

i ran faux123 updater and it flashed the mainline kernel but is messed up

i had no idea it's still only meant for 4.4 rom

how do i get the stock 4.4.2 boot.img
[Moto X Android Development] piccit:
Take it from one of the 4.4.2 sbf zips (someone can correct me if I'm wrong, but kernel should be the same regardless of carrier or region).

I don't think OTAs ever contain directly flash-able files
[Moto X Android Development] Valnomien:
so the problem is like you said OTA doesn't contain boot.img file it's a packed file boot.img.p and there are no official image files of 4.4.2 that I can find it's only the OTA not even motorola has 4.4.2 yet on there website

I could not use a 4.4 boot.img so I had to nandroid back to 4.4 and reapply OTA which sucks since all my data was wiped oh well someone should be smart enough to extract a working boot.img of 4.4.2 and make it flashable or easier to search for
[Moto X Android Development] kpetrie77:
I am not running stock any longer but went ahead and patched the 4.4 boot.img manually on my internal storage. If anyone still needs it, let me know and I'll PM a link.
[Moto X Android Development] scott62185:
Question : since I am going to restore my stock nandroid in order to flash this update, do I still need to disable my Xposed framework that is on this rom I'm on now (stock rooted)? I imagine not as it won't be on my original rom. Thanks
[Moto X Android Development] kpetrie77:
Should be okay. That would write over any changes made to system by Xposed.

Sent from my fastboot oem unlock XT1053
[Moto X Android Development] scott62185:
Attempting to flash this... So, I'm in my original nandroid, unrooted (with just a few apps installed) but I apparently don't have the stock recovery? When I went unto the bootloader and chose recovery it gave me TWRP. How do I get the stock recovery? Its showing an OTA update available to me. Can I just update like that? What would be the difference between doing that and flashing the file the OP provided? Sorry for the noob questions!
[Moto X Android Development] kpetrie77:
Check PM for recovery. Flash with recovery tools linked in the OP. Pulled from the 4.4 sbf.

The OTA message is for the same zip linked in the OP. Go either way after stock recovery is flashed.

Sent from my fastboot oem unlock XT1053
[Moto X Android Development] scott62185:
I did install recovery tools (from the Play store) but is says I need root to use it...is the one in the OP different?
[Moto X Android Development] kpetrie77:
Didn't catch that, use mfastboot to flash instead.

Sent from my fastboot oem unlock XT1053
[Moto X Android Development] scott62185:
Stupid question: what us mfastboot?
[G2 Original Android Development] dr87:
A kernel for AOSP roms based on 4.2.2 source​

Main features:

- Based on both Nexus 5 4.4.2 kernel source and G2

- In kernel thermal (Bricked)

- In kernel mpdecision hotplug (Bricked)

- Powersuspend, Dynamic Fsync, Intellidemand, Intelliactive, FauxSound (Faux123)

- Overclocking (2.8ghz), Underclocking, Voltage control

- RGB color control

- Additional Gov's and I/O scheds

- All TCP congestion types

- Many other Improvements

--------------------------------------------------------------------

Additional Info:

Trickster stock thermal / mpdecision settings are already tuned.

Don't turn on mpdecision in the main trickster menu (Defaults off) . Don't set a touchboost on cpu0

It is recommended you don't mess with any thermal/mpdecision settings unless you are 100% sure you know what you are doing and why you are doing it. I tuned stock to be good and will always improve it.

Please do not post anything about battery life in this thread. If you have battery issues check your apps and wake locks. Also please keep Sod reports to a minimum, some device variants have issues with Sods on all kernels and its something I'm always trying to fix. Currently CM rom has many issues, please do not report issues related to CM here.

-------------------------------------------------------------------

Current Release Downloads

Downloads Mirror

Source

Changelog ([I]specifics found on git[/I])

V7

- Add overclocking up to 2.8 GHZ
- Add Faux sound (Shouldn't cause audio issues but I will be watching)
- Reverted overvolted tables, now follows standard voltages based on your PVS
- Misc Improvements

V6:

- Add support for PAC / CM (phone UI crash fix)
- Intelliactive fix
- Misc improvements found on my git

V5:

- Updates to board specific source files from 4.4 kernel
- Remove some junk debugging from the kernel
- Ramdisk updates
- Power updates
- Misc updates

V4:

- Enable all TCP congestion control options (Use Google to find out what they do)
- Faux's brand new governor, Intelliactive. Read more [URL="https://github.com/faux123/Nexus_5/commit/7067c4bdd043ff8fe53fef61a47f3d374e452b47"]here[/URL] at the top of the page
- Power and voltage 4.4 updates everywhere, I suggest you try this if you get sod's and reboots on kitkat

Bug fixes:
Enabled Dynamic Fsync again

V3:

- CPU Hotplug improvements
- Revert exp sound, will fix sound issues for people who tried v2(exp)
- Lower temp throttle a bit
- Enable BFQ i/o sched on all variants - Accidentally only on d801 before
- Update CPU voltages to one stock table - this could be no change, +25 or +50 depending on what your chip is binned. This may help sod's and reboots on AOSP.
- Misc optimizations

Bug Fixes:
- Max volume bug
- Attempt to fix occasional mount bug in recovery

Credits:
Faux123
Houstonn
FranciscoFranco
Savoca
Showp-1984
RMCC
Many other android/linux devs
[G2 Original Android Development] dr87:
reserved.
[G2 Original Android Development] razrlover:
Oooohhhh. Nice another feather in your hat sir_, cheers
[G2 Original Android Development] Jank4AU:
Awesome, bro! Thanks for the love! It's always good to have options! :good:
[G2 Original Android Development] JRJ442:
[MENTION=5232783]dr87[/MENTION] Kernel seems really smooth so far. Definitely like it. I made a little screen record. Minimum clock speed doesn't seem to be sticking for me. https://www.youtube.com/watch?v=E8DJfiNsvPs&feature=youtube_gdata_player
[G2 Original Android Development] dr87:
Yea the touchboost on cpu0 (default 300mhz) will always override the min freq

This is why I set cpu1 to do the touchboost and cpu0 is on stock setting.

It's something I'm going to fix, have a lot of other stuff to do on the kernel also :good:
[G2 Original Android Development] JRJ442:
Awesome. The only reason I bump it up is because V4a acts up sometimes if I clock under 652. Thanks so much for this :)
[G2 Original Android Development] dr87:
For a fix go into mpdecision settings and bump the cpu0 boost to the min freq you want :)

I will work on unlinking them soon!
[G2 Original Android Development] philsfan:
[MENTION=5232783]dr87[/MENTION] i get a loki error when flashing vs980. TWRP 2.6.3.3

?
[G2 Original Android Development] JRJ442:
Got it! That worked. :)
[G2 Original Android Development] dr87:
What does the error say? it might be because you are using old twrp, I will update the binary to something that will work on older twrps... give me a few mins
[G2 Original Android Development] philsfan:
i thought 2.6.3.3 was the standard/accepted recovery? i've been using it all along.

i derped and accepted 12B baseband OTA about a month back. I remember I was getting this same loki flash error in recovery immediately after that before devs updated their scripts. I was told it's an easy fix but I have zero clue what to do on my own :(
[G2 Original Android Development] dr87:
http://www.mediafire.com/download/t4nd4bh28mgdb3p/vs980-dr87-v1-test.zip

let me know if that works before I update all the binaries
[G2 Original Android Development] philsfan:
failed :(

assert failed: run_program(" /tmp/loki.sh") ==0

E:error executing updated binary in zip
[G2 Original Android Development] dr87:
Which rom are you able to flash? I will try using their update binary
[G2 Original Android Development] JRJ442:
Are you using the TWRP for 12B? There's a specific thread for it in the vzw section
[G2 Original Android Development] philsfan:
Mahdi :good:

DU :good:

nameless, vanir, carbon, CM11. honestly all of them. but i know people who took the 12B update had trouble a while back when ayysir first introduced PAEK 5.2

---------- Post added at 12:21 AM ---------- Previous post was at 12:20 AM ----------

i'll give it a shot.

do you have the 12B OTA bootloader tho?
[G2 Original Android Development] JRJ442:
[MENTION=2418012]philsfan[/MENTION] I edited my reply because I reread yours. No I don't have the 12B bootloader. I just flashed the radio. Still if you haven't I'd try that 12B TWRP
[G2 Original Android Development] philsfan:
thanks [MENTION=3520986]JRJ442[/MENTION]

i tried flashing that a few weeks back but it didn't take. flashed successfully but wouldn't boot into recovery after a reboot. not sure what else to do. Don't wanna cause too much of a headache for the Dr if I'm the only one with this problem! :good:
[G2 Original Android Development] datsyuk:
Does the Aospa kernel stay up to date with CM kernel source?
[G2 Original Android Development] chrisexv6:
Dont forget Dirty Unicorns :)
[G2 Original Android Development] jesssiii:
The only good type, imo! Thanks.

Verizon G2 VS980
[G2 Original Android Development] jameseytickner:
This is true

---------- Post added at 09:22 PM ---------- Previous post was at 09:20 PM ----------

Yeah i think so, but this kernel works sweet with it
[G2 Original Android Development] ender4212:
Is there any way to get sound control settings to stick? I'm using Trickster and turning volumes to 0 but the next song I play is blaringly too loud again and when I go back to trickers, the settings have reverted.

edit: I'm using Viper4Android if that helps with my issue.
[G2 Original Android Development] gusly:
Just flashed on D803, and the max frequency keeps going haywire and it's making my battery temp hit 45°C. Just thought you should know XD

Edit: Omni build 1.8, if that matters
[G2 Original Android Development] adhitarecoming:
dr87 is ur kernel also based from houston newer kernel ?
[G2 Original Android Development] darkobas:
[MENTION=5232783]dr87[/MENTION] in the exp kernel there is a system/lib/modules folder but its empty... just noticed, probably unrelevant.
[G2 Original Android Development] razrlover:
I run ondemand plus with sio and cubic and cpu freq distribution is perfect. Great battery % and no sod or lag. Always bump minimum to next tier and maximum cpu frequency.