Database Users

[Q] How Do I Prevent OTA 4.3 Update

So my Nexus 7 has downloaded the OTA firmware before I realized that Google was doing a roll-out. The Nexus 7 want me to reboot and do the FW upgrade but I don't want to upgrade the tablet. There does not appear to be a easy way to retain Root, and i'm not interested in teh steps for CFW, etc so it easier for me to stay on v4.2.x. Is there a way to prevent the upgrade? can I delete the downloaded OTA update or something? What is the path to the OTA update files? I would like to know before rebooting as I'm not sure if rebooting will just force the update. I have rooted the tablet but no other hacks such as unlocked boot loader have been performed on the device. I did a web search but did not see a in dept conversation on how to refuse the update once it has been downloaded onto the device

You could try a root keeper app that will retain root after the update. As for preventing the update, I'm not sure how that would work. Should be easy enough to keep root though.
Sent from my Nexus 7 using Tapatalk 4 Beta

A RootKeeper does not work with 4.3 due to the way that secuirity is implemented in the new FW. This has been noted in the description of the RootKeeper app on the Play store

The OTA file is in /cache and should be called ab67ca07c4b2e03eca795ada10ff041b77fbb7bf.signed-nakasi-JWR66V-from-JDQ39.ab67ca07.zip (that is, if you're using wifi-only device, otherwise the name will be slightly different)
But in another thread it came up, that at some time the update will spring up again, so you should keep an eye on it
p.s. that should be the update file, but still take this with a grain of salt, i don't have much experience messing with ota updates.

Sound Anarchist said:
The OTA file is in /cache and should be called ab67ca07c4b2e03eca795ada10ff041b77fbb7bf.signed-nakasi-JWR66V-from-JDQ39.ab67ca07.zip (that is, if you're using wifi-only device, otherwise the name will be slightly different)
But in another thread it came up, that at some time the update will spring up again, so you should keep an eye on it
p.s. that should be the update file, but still take this with a grain of salt, i don't have much experience messing with ota updates.
Click to expand...
Click to collapse
I checked the cache folder using es explorer and it showed no data files(zip) in that folder. maybe the file was not downloaded yet or was already applied and the device is just waiting for a reboot to consummate the upgrade

Or you could just flash CleanROM and have 4.3 and root.
Sent from my NookColor using xda app-developers app

u could take a look at this thread:
http://forum.xda-developers.com/showthread.php?t=1998378

Thanks for all of the input. I resolved this issue. I just enabled root in es explorer which showed the hidden OTA zip file in the Cache folder. I renamed the file, but the OS deleted it after the rename so I could not even save a copy of the file. I have since rebooted and the OTA did not re-download (which is a good thing) although I still get an icon in notification indicating that the OTA is ready to install.
I'm just not interested in updating to the latest 4.3 build due to lack of time. I have many Android devices and spending the time to Root and or unlock the boot loader on each device is just taking to much of my time. So I'll just stay on the current build until I have time to tinker again. Thanks again everyone for your input

I clicked the update (stupid I know) and because I was stock 4.2.2, but rooted, got bootloop. I had to use fastboot to update to the stock 4.3, now hunting for root instructions. I post this so folks running anything non-stock don't blindly accept the OTA update or headaches will ensue.

downwiththebanksters said:
I clicked the update (stupid I know) and because I was stock 4.2.2, but rooted, got bootloop. I had to use fastboot to update to the stock 4.3, now hunting for root instructions. I post this so folks running anything non-stock don't blindly accept the OTA update or headaches will ensue.
Click to expand...
Click to collapse
It's a shame I saw your warning too late, couldn't resist the OTA update.
Now I'm stuck at logo.
Do I have to use fastboot as well to manually update to 4.3? What instructions did you use?
Thanks.

timnik said:
It's a shame I saw your warning too late, couldn't resist the OTA update.
Now I'm stuck at logo.
Do I have to use fastboot as well to manually update to 4.3? What instructions did you use?
Thanks.
Click to expand...
Click to collapse
I wish I had seem this warning earlier too. I blindly accepted the OTA update yesterday thinking "Oh hey Android 4.3! Awesome!" and now I'm running in a whole load of problems and glitchs. I'm also not rooted yet which makes another problem because I can't find anything to root 4.3 yet. Also can't find anything on how to restore back to stock Android 4.2.2. Does anyone know anything about this? Will factory reset do the trick? I have all my stuff backed up.

[Q] rooted LG G2 update OTA

how to do you update a rooted lg g2 over the air. everything is stock on the phone.

MAGICEA_EA said:
how to do you update a rooted lg g2 over the air. everything is stock on the phone.
Click to expand...
Click to collapse
From what I understand, you will still be able to get updates thru OTA.

hd-renegade said:
From what I understand, you will still be able to get updates thru OTA.
Click to expand...
Click to collapse
the recovery "kill" the otas, not the root.
so you have costom recovery you will get the ota but you will be unable to install it, if you use jest a root and have stock recovery - you fine and will get the ota.

So i can update rooted lg g2 over the air when a new update comes out

liorra3 said:
the recovery "kill" the otas, not the root.
so you have costom recovery you will get the ota but you will be unable to install it, if you use jest a root and have stock recovery - you fine and will get the ota.
Click to expand...
Click to collapse
I my self do not have a custom recovery. I am just rooted and running stock ROM. I had asked the same question maybe a month ago, and I was told that I would still be able to get OTA updates. If I am wrong, feel free to tell me.

ota
hd-renegade said:
I my self do not have a custom recovery. I am just rooted and running stock ROM. I had asked the same question maybe a month ago, and I was told that I would still be able to get OTA updates. If I am wrong, feel free to tell me.
Click to expand...
Click to collapse
Im new to this, so if you have rooted lg g2, will ota still work. Everything is stock on the phone

hd-renegade said:
I my self do not have a custom recovery. I am just rooted and running stock ROM. I had asked the same question maybe a month ago, and I was told that I would still be able to get OTA updates. If I am wrong, feel free to tell me.
Click to expand...
Click to collapse
you right.
if you use stock recovery you will get OTAs

if its stock and merely rooted then OTA should work

For the OTA to be accepted, you'll need the stock recovery for your device. Rename it to recovery.img (if it already isn't named that) and then move it to sdcard root (/sdcard).
Now, use a terminal emulator (https://play.google.com/store/apps/details?id=jackpal.androidterm&hl=en) and open a command prompt. The command we're using has two parameters. The the "if" parameter refers to your input file, in this case, this is the recovery.img file you moved to your sdcard root to flash. This could be any recovery (TWRP, CWM, stock, etc). The "of" parameter is the output file and is the actual physical path to the recovery image your device uses. At the command prompt type this:
Code:
su
dd if=/sdcard/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
If you already have the stock recovery then all you need to do is press "Accept" or "OK" or whatever the dialog asks when it pops up letting you know about the update. I'm not sure if the stock recoveries are different for each carrier, so you'll have to find that yourself.
Edit: By the time I finished typing this I see that you already are on stock recovery, so you should be good to go

Idk mines flashed to stock and rooted
Sent from my LG-D800 using Tapatalk

Just bought a g2 and am thinking of rooting to enable the auto hide of the on screen menu buttons. So correct me if im wrong but if all i do is root, leave the stock rom and do nothing apart from root i will still get ota updates.

But the update can remove root right? So is there any way I can keep my phone from automatically updating and losing root? I don't want to lose root... Mainly cuz i love not having software keys.
Sent from my LG-LS980 using xda app-developers app

SuperSU Pro has an OTA survival Mode. You can try it out, it should work

o0adam0o said:
But the update can remove root right? So is there any way I can keep my phone from automatically updating and losing root? I don't want to lose root... Mainly cuz i love not having software keys.
Sent from my LG-LS980 using xda app-developers app
Click to expand...
Click to collapse
Try the above or remove/freeze whatever the apk your carrier uses for the OTA. There's a couple threads around with more info.
Sent from my LG-D800

Another question: (don't want to start a thread for this)
If you have custom recovery (In my case TWRP) when an OTA lands, obviously I won't be able to accept it.
I'll need to flash it through TWRP correct?
If this is the case will this simply apply as OTA's do and not delete any of my data on the phone etc?
Also is there a stock recovery I can download just to make things easier??
First time I've had a phone rooted and with recoverybefore it's update cycle is over, and Google isn't really being all that helpful

How to backup stock recovery?

I just picked up the G2 two days ago and rooted pretty much immediately (via ioroot10) but other than that, I'm still running completely stock. I saw some recent posts stating that it was now possible to install TWRP or CWM on the D80010o firmware, so I decided I would go ahead and take the OTA update and then install a custom recovery. However, I have tried install the OTA several times now and every time, when the phone reboots after downloading the update, I get error "0x1117008" when the OTA tries to install, and then the phone reboots to system and I get a popup stating something to the effect of "This device is suspected of rooting. Software updates will not be available for rooted devices." Checking the software version I see that I'm still on D80010d and the 10o OTA update is still available and has to be downloaded again.
Anyone else have this issue?
And no, I have not installed a custom recovery yet.

m4570d0n said:
I just picked up the G2 two days ago and rooted pretty much immediately (via ioroot10) but other than that, I'm still running completely stock. I saw some recent posts stating that it was now possible to install TWRP or CWM on the D80010o firmware, so I decided I would go ahead and take the OTA update and then install a custom recovery. However, I have tried install the OTA several times now and every time, when the phone reboots after downloading the update, I get error "0x1117008" when the OTA tries to install, and then the phone reboots to system and I get a popup stating something to the effect of "This device is suspected of rooting. Software updates will not be available for rooted devices." Checking the software version I see that I'm still on D80010d and the 10o OTA update is still available and has to be downloaded again.
Anyone else have this issue?
And no, I have not installed a custom recovery yet.
Click to expand...
Click to collapse
Nice to see you here dude.. may remember me from the rocket? Anyways, i'd just skip the OTA. It's nothing life changing. I'm still stock/rooted on 10d. Waiting for bugs to get squashed on 4.4.2 before I start flashing. Rather enjoying stock for the time being. Not really sure why 10o won't take. Haven't seen anyone else mention this. The only thing that has been brought up repeatedly is bootloops in twrp after taking the 10o OTA.

m4570d0n said:
I just picked up the G2 two days ago and rooted pretty much immediately (via ioroot10) but other than that, I'm still running completely stock. I saw some recent posts stating that it was now possible to install TWRP or CWM on the D80010o firmware, so I decided I would go ahead and take the OTA update and then install a custom recovery. However, I have tried install the OTA several times now and every time, when the phone reboots after downloading the update, I get error "0x1117008" when the OTA tries to install, and then the phone reboots to system and I get a popup stating something to the effect of "This device is suspected of rooting. Software updates will not be available for rooted devices." Checking the software version I see that I'm still on D80010d and the 10o OTA update is still available and has to be downloaded again.
Anyone else have this issue?
And no, I have not installed a custom recovery yet.
Click to expand...
Click to collapse
I am having the same error but don't remember seeing the same pop-up, just says install failed or something like that. I'm on Verizon stock Rom rooted. I've done plenty of mods by manually pushing them through, but I have the stock recovery and no custom recovery.... So safe to say, looks like you can't update with root. Gonna start searching for unroot then re root after update is installed. Doesn't seem like there is another way to do it. Anybody know if the temp unroot via superuser apk will work?
Sent from my VS980 4G using Tapatalk

thricerocks86 said:
I am having the same error but don't remember seeing the same pop-up, just says install failed or something like that. I'm on Verizon stock Rom rooted. I've done plenty of mods by manually pushing them through, but I have the stock recovery and no custom recovery.... So safe to say, looks like you can't update with root. Gonna start searching for unroot then re root after update is installed. Doesn't seem like there is another way to do it. Anybody know if the temp unroot via superuser apk will work?
Click to expand...
Click to collapse
I am still investigating. I've unrooted via Voodoo OTA Rootkeeper and a little extra housekeeping, and the Rooting Status does show "unrooted" in the About Phone section. However I still get 0x1117008 when trying to install the OTA. So perhaps the "unrooted" in About Phone may be a prerequisite, but is not sufficient for a successful OTA update. Maybe either the update is doing more checks for rooting evidence than the RCT daemon, or perhaps there is some other change that is triggering the error.

No AT&T OTA update if rooted?

Tried to take the ota cause I read that after the update you can just reroot with the io tool. When I tried to take the update it said this device is suspected of rooting or something along those lines and the update failed to download and install. Has this happened to anyone else?

Jspeer said:
Tried to take the ota cause I read that after the update you can just reroot with the io tool. When I tried to take the update it said this device is suspected of rooting or something along those lines and the update failed to download and install. Has this happened to anyone else?
Click to expand...
Click to collapse
I didn't have this issue. I downloaded the update, but my problem was that I had a custom recovery installed and when my chromecast rebooted my phone, it sent it into a bootloop that wouldn't get out of recovery. I found an article here to fix that, but needless to say that I won't be doing OTA's with custom recovery again.

If you take the update, your recovery will loop. There is a fix for it in the root thread by @thecubed. So, the choice is yours.
Sent from my LG-D800

I was just rooted on the stock rom. Forgot to mention that. I did however have "survive ota" checked in superuser though, I wonder if that had anything to do with it. I haven't tried it again with that unchecked. The update just isn't important enough to me to justify messing with it, I just took it because I was out of postpone attempts. But now the message is completely gone and not nagging me anymore and everything still works fine root and all.

Jspeer said:
Tried to take the ota cause I read that after the update you can just reroot with the io tool. When I tried to take the update it said this device is suspected of rooting or something along those lines and the update failed to download and install. Has this happened to anyone else?
Click to expand...
Click to collapse
OTA update from Phone will fail if you are rooted. Either on custom recovery or rooted status. Don't use update from phone, but connect phone to PC and use LG Support Tool. This one doesn't care of root, it will download full 10c update 1.9GB and update your phone. I just did it this way (rooted + TWRP). No problem, no data lost.
But of course, you need to root it again and install custom recovery as well.

p.valenta said:
OTA update from Phone will fail if you are rooted. Either on custom recovery or rooted status. Don't use update from phone, but connect phone to PC and use LG Support Tool. This one doesn't care of root, it will download full 10c update 1.9GB and update your phone. I just did it this way (rooted + TWRP). No problem, no data lost.
But of course, you need to root it again and install custom recovery as well.
Click to expand...
Click to collapse
Where can I download the lg support tool? Do you have a link?

Jspeer said:
Where can I download the lg support tool? Do you have a link?
Click to expand...
Click to collapse
You can get it from LG website. Or for example in this thread.

Don't do it!
Unless you NEED the ISIS functionality, I STRONGLY urge you to postpone or even disregard D80010o altogether. I don't know what "bug fixes" their release notes talked about as I've not seen one single improvement over D80010d, yet battery drain, battery drain. Once you update you'll notice your battery going downhill and all of a sudden "Android System" takes up about 50% of your battery usage. It's happened to 2 LG G2s I've owned, battery was phenomenal before the update, after the update... like I said. You'll learn to hate "Android System". I'd either wait for 4.3 or KitKat altogether.

Wife possibly soft bricked??

Ok
So the wife has the ATT version.I am not 100% sure if she was on JB or KK. Last night we were going to bed and she said that a notification popped up to update an app (well she says it said to update an app) and so she hit ok. the phone rebooted and went right to recovery.. the phone will not boot up.. every time it boots it goes right to twrp... i tried to restore her old stock backup and it still wont boot...
so, what I am thinking might have happened was she was on JB and it came up saying an update for phone was avail (going to KK) and she hit yes.. and since she was rooted, it failed or something and soft bricked it. does this sound about right?
What I am wondering is will using this method http://forum.xda-developers.com/showthread.php?t=2663369 work... i downloaded the kitkate D80020C one and wondering if that process will fix it? or, do I need to do one of the JB ones?
I appologize, but unfortunately I don;t really use the phone and not familiar with it.. all i did was root it for her and get rid of some bloat and then boom.. she F's it up
appreciate any feedback... hate to run that and make it worse if it does..
Zug
edit: so.. other issue is can't seem to get it to boot into download mode... i plugged the cable into laptop , held the vol up button, then plugged the other end into the phone and it still only boots into twrp...
any ideas?

Zugshad said:
Ok
So the wife has the ATT version.I am not 100% sure if she was on JB or KK. Last night we were going to bed and she said that a notification popped up to update an app (well she says it said to update an app) and so she hit ok. the phone rebooted and went right to recovery.. the phone will not boot up.. every time it boots it goes right to twrp... i tried to restore her old stock backup and it still wont boot...
so, what I am thinking might have happened was she was on JB and it came up saying an update for phone was avail (going to KK) and she hit yes.. and since she was rooted, it failed or something and soft bricked it. does this sound about right?
What I am wondering is will using this method http://forum.xda-developers.com/showthread.php?t=2663369 work... i downloaded the kitkate D80020C one and wondering if that process will fix it? or, do I need to do one of the JB ones?
I appologize, but unfortunately I don;t really use the phone and not familiar with it.. all i did was root it for her and get rid of some bloat and then boom.. she F's it up
appreciate any feedback... hate to run that and make it worse if it does..
Zug
edit: so.. other issue is can't seem to get it to boot into download mode... i plugged the cable into laptop , held the vol up button, then plugged the other end into the phone and it still only boots into twrp...
any ideas?
Click to expand...
Click to collapse
ok first I would suggest to give this a try if it does not work than yes booting into download mode and flashing the d80020c firmware will work

XxZombiePikachu said:
ok first I would suggest to give this a try if it does not work than yes booting into download mode and flashing the d80020c firmware will work
Click to expand...
Click to collapse
thanks... i actually managed to somehow find that post and was just about to update..
so, her phone had the old twrp without adb,, so i did the instructions for the terminal command and did that command and the phone boots..
here is what i posted there and maybe possibly you might know as well..
now question is what else do i need to do to her phone ... its hers (sorry note3 guy here ;P)
i am in her about phone and this is what she has.
4.4.2
kernel 3.4.0
build kot49l.D80020u
D80020u
i
is she on the latest? do i need to update twrp, if so, what would be best method...its bee a while since i rooted it and not sure what i did.. in my downloads i have ioroot24, so guessing that is what i did.. not 100% sure if she took the ota to KK or not.. as that is what I am thinking happened ad she came from JB, but does it make sense that the ota stuck after i did that command? all her apps are still there that she recalls, but i can't be 100% certain wtf happened
do I need to do anything further for her? again, i appreciate the help
:good::good::good::good::highfive:

Zugshad said:
thanks... i actually managed to somehow find that post and was just about to update..
so, her phone had the old twrp without adb,, so i did the instructions for the terminal command and did that command and the phone boots..
here is what i posted there and maybe possibly you might know as well..
now question is what else do i need to do to her phone ... its hers (sorry note3 guy here ;P)
i am in her about phone and this is what she has.
4.4.2
kernel 3.4.0
build kot49l.D80020u
D80020u
i
is she on the latest? do i need to update twrp, if so, what would be best method...its bee a while since i rooted it and not sure what i did.. in my downloads i have ioroot24, so guessing that is what i did.. not 100% sure if she took the ota to KK or not.. as that is what I am thinking happened ad she came from JB, but does it make sense that the ota stuck after i did that command? all her apps are still there that she recalls, but i can't be 100% certain wtf happened
do I need to do anything further for her? again, i appreciate the help
:good::good::good::good::highfive:
Click to expand...
Click to collapse
what the command form that thread does is delete the ota file from a partition where it stores itself on your wifes device so it could stop trying to ota and boot normally
well if she is running d80020u then she has updated to kk before(jb was d80010d>d80010o> and then kk update was d80020c>d80020k>280020u>d80020y) with 20y being the latest(and the one it asked her to update to befor brick) if you want ot be able to ota to the latest than you would need to use download mode to go to stock and then do ota process until d80020y and for root on new update you need to use stump root with the brute force method and then use autorec if you want custom recovery again and if you decide to use autorec you will need to flash a custom kernel with knock code support for d800(I suggest dorimanx kernel) because autorec will break knock on/knock code

XxZombiePikachu said:
what the command form that thread does is delete the ota file from a partition where it stores itself on your wifes device so it could stop trying to ota and boot normally
well if she is running d80020u then she has updated to kk before(jb was d80010d>d80010o> and then kk update was d80020c>d80020k>280020u>d80020y) with 20y being the latest(and the one it asked her to update to befor brick) if you want ot be able to ota to the latest than you would need to use download mode to go to stock and then do ota process until d80020y and for root on new update you need to use stump root with the brute force method and then use autorec if you want custom recovery again and if you decide to use autorec you will need to flash a custom kernel with knock code support for d800(I suggest dorimanx kernel) because autorec will break knock on/knock code
Click to expand...
Click to collapse
thanks... yeah she just wants to leave it alone lol.. so told her to pay attn to what its wanting to update ;P but at least now I know how to fix if she does that again.. thanks again )

Zugshad said:
thanks... yeah she just wants to leave it alone lol.. so told her to pay attn to what its wanting to update ;P but at least now I know how to fix if she does that again.. thanks again )
Click to expand...
Click to collapse
well a heads up it will be happening again, att pushes the update and after ignoring it a couple of times it will force install the update; if you want to avoid it then there are a few options:
1)if you are a titanium backup pro user then just freeze the ota app(I think it was something with dms in the name but I have not used att rom in a couple of moths and forgot the name sorry)
2)if you don't own tibu pro than using a root explorer just delete the ota app(once again I don't remember the name, sorry)

XxZombiePikachu said:
well a heads up it will be happening again, att pushes the update and after ignoring it a couple of times it will force install the update; if you want to avoid it then there are a few options:
1)if you are a titanium backup pro user then just freeze the ota app(I think it was something with dms in the name but I have not used att rom in a couple of moths and forgot the name sorry)
2)if you don't own tibu pro than using a root explorer just delete the ota app(once again I don't remember the name, sorry)
Click to expand...
Click to collapse
thanks. i have tibu pro, but she doesnt..i do have root explorer for her and went through and i see a LGDMSClient.apk in there..does that sound right? gonna google it and double check to see if that is right.. appreciate the feedback.. yeah i figured it would end up just updating again and again but had tried to find/freeze and realized she wasn't pro don't feel up to the 10ish bucks on it again for her lol when that would really be the only use of it for her
edit... ok that is the ota file.... thanks again )

Zugshad said:
thanks. i have tibu pro, but she doesnt..i do have root explorer for her and went through and i see a LGDMSClient.apk in there..does that sound right? gonna google it and double check to see if that is right.. appreciate the feedback.. yeah i figured it would end up just updating again and again but had tried to find/freeze and realized she wasn't pro don't feel up to the 10ish bucks on it again for her lol when that would really be the only use of it for her
Click to expand...
Click to collapse
yep that should be it; just delete and goodbye updates should stop working as a whole (if you want to get tibu to freeze you can always log in with your play account on her device and download the pro version)
edit: just noticed you solved it

Rogers 4.4.4 roll out has begun!

Just got the notice. Updating now!
About damn time.
Sent from my XT1058 using XDA Free mobile app

Yep, bought mine outright through Fido, updated tonight.
I'm using it on Bell, nice to see you can finally get rid of your carrier label in the status bar.

Yay, now do I unroot and try the OTA or do I wait for the full image.

ChrisAG said:
Yep, bought mine outright through Fido, updated tonight.
I'm using it on Bell, nice to see you can finally get rid of your carrier label in the status bar.
Click to expand...
Click to collapse
You can? How? I didn't save the link to the release notes, and can't find them now.

thedosbox said:
You can? How? I didn't save the link to the release notes, and can't find them now.
Click to expand...
Click to collapse
Removing provider name from the Status bar:
Settings > Wireless & Networks > More > Mobile Networks > Show Mobile Network (check on or off)

I completely forgot about the carrier being removed. Really cool.
Sent from my XT1058 using XDA Free mobile app

Install went fine, I unrooted, upgraded and then rooted again with no problem. The show carrier on/off is a great upgrade, I don't have to mess with modifying APK's anymore.
The new dialer will take some time to get used to.

Steve-x said:
Install went fine, I unrooted, upgraded and then rooted again with no problem. The show carrier on/off is a great upgrade, I don't have to mess with modifying APK's anymore.
The new dialer will take some time to get used to.
Click to expand...
Click to collapse
Ugh... I have TWRP on mine. Can I just unroot, or I need to remove TWRP? (read: flash stock 4.4.2...)

OK. Ended up flashing the whole damn phone again.
So which root method works for us, Rogers users?

R3dbeaver said:
OK. Ended up flashing the whole damn phone again.
So which root method works for us, Rogers users?
Click to expand...
Click to collapse
I removed root using the option in Super SU and then flashed the system.img and recovery.img from 4.4.2 in fastboot.(probably didn't need to do anything with Super SU because I reflashed system.img)
I then let the phone update. When it was done I went back into fastboot and flashed TWRP to recovery, went into recovery and let it begin the root process. From there boot up and update Super SU and finish rooting.
Overall a pretty painless way to go from 4.4.2 to 4.4.4 without losing any data or settings. All of this assumes you have an unlocked bootloader of course.

Steve-x said:
I removed root using the option in Super SU and then flashed the system.img and recovery.img from 4.4.2 in fastboot.(probably didn't need to do anything with Super SU because I reflashed system.img)
I then let the phone update. When it was done I went back into fastboot and flashed TWRP to recovery, went into recovery and let it begin the root process. From there boot up and update Super SU and finish rooting.
Overall a pretty painless way to go from 4.4.2 to 4.4.4 without losing any data or settings. All of this assumes you have an unlocked bootloader of course.
Click to expand...
Click to collapse
Ah you used TWRP's.
OK cool. Will give it a shot. Will try. I'm assuming I need SuperSU and BusyBox installed beforehand? Remember, I'm starting clean here.

R3dbeaver said:
Ah you used TWRP's.
OK cool. Will give it a shot. Will try. I'm assuming I need SuperSU and BusyBox installed beforehand? Remember, I'm starting clean here.
Click to expand...
Click to collapse
If your bootloader is unlocked then it is very simple. Just go to fastboot and flash the TWRP recovery, once flashed you can access it from fastboot. TWRP will load, then you can just select to restart the phone from it and it will ask if you want to root the phone, swipe to confirm and it will do it and restart the phone for you. Once the phone is booted you will need to finish the process - it should prompt you to update SuperSU, I selected the play store option, it downloaded and installed and was done. From there do yourself a favor and install AdAway

waiting for the firmware image..... anybody knows where to get it?

It has been posted to one of the various sites. I grabbed it the other night but couldn't tell you which site it was from as I am at work right now. Enough searching should find it.

Steve-x said:
It has been posted to one of the various sites. I grabbed it the other night but couldn't tell you which site it was from as I am at work right now. Enough searching should find it.
Click to expand...
Click to collapse
Would you please send the download link when you are convinient? I searched and find this http://www.filefactory.com/folder/dd05c058d3ff8dbe/?sort=created&order=DESC&show=25, but looks something wrong with the system.img.

Steve-x said:
I removed root using the option in Super SU and then flashed the system.img and recovery.img from 4.4.2 in fastboot.(probably didn't need to do anything with Super SU because I reflashed system.img)
I then let the phone update. When it was done I went back into fastboot and flashed TWRP to recovery, went into recovery and let it begin the root process. From there boot up and update Super SU and finish rooting.
Overall a pretty painless way to go from 4.4.2 to 4.4.4 without losing any data or settings. All of this assumes you have an unlocked bootloader of course.
Click to expand...
Click to collapse
Thanks, works a charm, went from rooted 4.4.2 to 4.4.4.
PS- I grew up in Langley.

I don't know if it's dumb luck or not, but I didn't even unroot and was able to accept OTA to 4.4.4.
This is what I did to prepare the phone:
- Uninstall Xposed Framework from within the Xposed installer itself. Left the installer app in place.
- Changed recovery from TWRP back to factory.
- Enabled all apps previously disabled.
At this point my phone was still rooted. I accepted the OTA and everything worked fine.
Afterwards, I re-installed Xposed from the installer app, and re-disabled the apps I don't use. But left the factory recovery in place since I don't have a need to go into TWRP for now.
Everything is working fine.

No Rogers Update?
I just picked up a Moto X (Brand New) It came with 4.2.2 Im with Rogers, It is a Rogers phone , its been 2 hours now still no software update notification. When I try to check manually in about phone, system update. Keeps telling me my device is up to date??
Any one experienced this before? Or am I being to impatient

Now, a dummy question: what is Rogers?

Rogers is the Canadian phone company that's selling the original Moto X