Hi,
My wifes old phone is a Moto G 4g, she kept it on KitKat and never updated it to Lolipop. I'm looking to root it and put lineage OS on it, but I need to update it first to make sure the radio firmware is correct. When I try and do a system update now it keeps saying its already on the latest version, but its on KitKat so this cant be right. My wife was getting this popup before years ago but ignore it because she wanted to stay on KitKat, just wondering why its not working now ?.
Thanks in advance
Related
Hi,
I have received the kitkat update notification for my moto G a couple of weeks ago, and postponed the update several times, suddenly the notificaiton stopped showing (since I wanted to develop an app in 4.3). The problem is my phone does not find the update now. When I try to manually look for the OTA, it says I have the latest version, which is still 4.3. I even factoryr reset the phone once but no help. Any Idea how to activate the update again.
I have a moto g that was originally a boost model i hve flashed it to verizon then activated on page plus I am rooted but on stock 4.4.2 everything works well i have custom twrp recovery but still am getting software is up to date when i try to ota update to 4.4.4 what am i doing wrong?
bunkerboy69 said:
I have a moto g that was originally a boost model i hve flashed it to verizon then activated on page plus I am rooted but on stock 4.4.2 everything works well i have custom twrp recovery but still am getting software is up to date when i try to ota update to 4.4.4 what am i doing wrong?
Click to expand...
Click to collapse
try doing offline update instead
OTA's
I have a Boost Moto G that has the Verizon Firmware on it & I had no ISSUEs letting it OTA as it normally would everything works fine.
I get this may be a bit old but others may be looking for the answer as well
OTA's will not work with custom recoveries (and maybe even anything non-stock).
Here is a flashable zip for 4.4.4 for Verizon's Moto G.
Hey guys
Been reading about the new 4.4.4, but no clear info on it
Picked up a Boost Mobile Moto G to use with Page Plus
unlocked the bootloader
installed CFC-fastboot_falcon_verizon_user_4.3
installed recovery-clockwork-6.0.4.7-falcon.img
rooted
I'm up to CFC-fastboot_falcon_verizon_user_4.4.2
my question is do I flash to CFC-fastboot_falcon_verizon_user_4.4.4
are there problems with the new 4.4.4
right now I have 3G data, and everything works.
anyone flash 4.4.4 to Page Plus, any issues ?
Thanks
lionedas said:
Hey guys
Been reading about the new 4.4.4, but no clear info on it
Picked up a Boost Mobile Moto G to use with Page Plus
unlocked the bootloader
installed CFC-fastboot_falcon_verizon_user_4.3
installed recovery-clockwork-6.0.4.7-falcon.img
rooted
I'm up to CFC-fastboot_falcon_verizon_user_4.4.2
my question is do I flash to CFC-fastboot_falcon_verizon_user_4.4.4
are there problems with the new 4.4.4
right now I have 3G data, and everything works.
anyone flash 4.4.4 to Page Plus, any issues ?
Thanks
Click to expand...
Click to collapse
I just flashed 2 of the Boost phones last week... immediately after flashing the Verizon firmware, it updated to 4.4.4 and I let it go. This before I even flashed the NV stuff to get data & 3G. It has been flawless for me. I came to this phone from a Rezound which was much harder to get onto PP properly. I have already rooted my phone and put on TWRP 2.7.1.0... I am trying to make myself wait a while before I really get into flashing different ROMs because this stock variant is working so smoothly. Hope this helps a bit.
No Issues Here
I had flashed my device when it was on 4.3 as well and on July 30th it updated to 4.4.4 & everything works as it should so just let it do the update no need to do it manually unless you are rooted I guess would be the only reason
Okay I know your probably gonna think outright this an Android L page right, I'll not lie yes but in a different way.
Okay right now I'm running Motorola Stock Android 4.4.4, yes I have messed around flashed to GPE came back; back and forth. You get my point
So here's my question (its a big staged one)
If history is going to repeat itself that means the GPE edition of the G will get the update faster than the
Moto stock G. So if i were to say flash to GPE and keep it like that, the bootloader being unlocked would the Lollipop update work on the GPE or can I lock my bootloader to GPE (keep in mind mine is a XT1033) which i think isn't possible.
Why the concern on GPE and unlocked is cause Lollipop is the going to be the most secure android release and bootloader and secure go hand in hand..
Thanks for any insight/help
siddharthnair96 said:
Okay I know your probably gonna think outright this an Android L page right, I'll not lie yes but in a different way.
Okay right now I'm running Motorola Stock Android 4.4.4, yes I have messed around flashed to GPE came back; back and forth. You get my point
So here's my question (its a big staged one)
If history is going to repeat itself that means the GPE edition of the G will get the update faster than the
Moto stock G. So if i were to say flash to GPE and keep it like that, the bootloader being unlocked would the Lollipop update work on the GPE or can I lock my bootloader to GPE (keep in mind mine is a XT1033) which i think isn't possible.
Why the concern on GPE and unlocked is cause Lollipop is the going to be the most secure android release and bootloader and secure go hand in hand..
Thanks for any insight/help
Click to expand...
Click to collapse
I'm afraid that if you have GPe and OTA to Lollipop, maybe you wont be able to flash KitKat, something like that happened when KitKat arrived and people wasnt able to flash Jelly Bean anymore because some things changed inside software. So I think this will happen when Lollipop arrives, some changes in the software will prevent downgrading Android versions. Later on, firmware images of Lollipop will appear and then maybe it will be possible to flash Moto Lollipop but with no more posibility to go back to KitKat.. IMHO I preffer waiting for Moto Lollipop...
And yes.. The Lollipop update is going to work on GPe only if you have stock recovery on it, and you will loose root access since a major system update means all system files being erased and replaced with brand new files, that also means formatting system partition and root files being formatted as well. So if you want, keep GPe but with stock recovery to make the OTA work properly.
siddharthnair96 said:
If history is going to repeat itself that means the GPE edition of the G will get the update faster than the
Moto stock G.
Click to expand...
Click to collapse
Non gpe moto G got update from 4.3 to 4.4.2 faster than gpe one. So we can't say for sure which one will get L first.
Okay, so I recently bought a used Moto G LTE, seller said it would be on Lollipop 5.1. When I received it, it had been rolled back to 4.4.4. Hence the screen ripple at every boot up (which persists until the phone is locked and then unlocked) that almost gave me a heart attack the first time. A little googling later I learn this happens because while you can downgrade android the upgraded version's bootloader remains. So last night I finally got around to rooting since I just can't go from a rooted phone to living with a non rooted one, feels like my phone has a noose around it. Anyway I wanted to know if it's safe to flash CM on my phone now or should I reupgrade to 5.1 first? And if I should is there a way to get it to update OTA again? If not any suggestions where to find the firmware? I just want to feel free to flash roms without bricking my phone. Here is a screenshot of my About Phone, in case someone needs it to help, imgur.com /v8iLOU7
electriceccentric said:
Okay, so I recently bought a used Moto G LTE, seller said it would be on Lollipop 5.1. When I received it, it had been rolled back to 4.4.4. Hence the screen ripple at every boot up (which persists until the phone is locked and then unlocked) that almost gave me a heart attack the first time. A little googling later I learn this happens because while you can downgrade android the upgraded version's bootloader remains. So last night I finally got around to rooting since I just can't go from a rooted phone to living with a non rooted one, feels like my phone has a noose around it. Anyway I wanted to know if it's safe to flash CM on my phone now or should I reupgrade to 5.1 first? And if I should is there a way to get it to update OTA again? If not any suggestions where to find the firmware? I just want to feel free to flash roms without bricking my phone. Here is a screenshot of my About Phone, in case someone needs it to help, imgur.com /v8iLOU7
Click to expand...
Click to collapse
Hi.
In my xt1040, i can flash CM 12 lollipop or a stock rom based from kitkat 4.4.4 without problems (I have a updated bootloader), to get OTA updates again, its necessary flash the stock rom (KK or LP), without root, PURE stock (with all "bloatware").
Now im using a optimized rom from:
http://forum.xda-developers.com/moto-g/4g-development/rom-stock-motorola-4g-lollipop-rom-t3142816
No bugs, amazing battery life, and a pure stock, no "bloatware", great ram management.
Sorry for bad english.
electriceccentric said:
Okay, so I recently bought a used Moto G LTE, seller said it would be on Lollipop 5.1. When I received it, it had been rolled back to 4.4.4. Hence the screen ripple at every boot up (which persists until the phone is locked and then unlocked) that almost gave me a heart attack the first time. A little googling later I learn this happens because while you can downgrade android the upgraded version's bootloader remains. So last night I finally got around to rooting since I just can't go from a rooted phone to living with a non rooted one, feels like my phone has a noose around it. Anyway I wanted to know if it's safe to flash CM on my phone now or should I reupgrade to 5.1 first? And if I should is there a way to get it to update OTA again? If not any suggestions where to find the firmware? I just want to feel free to flash roms without bricking my phone. Here is a screenshot of my About Phone, in case someone needs it to help, imgur.com /v8iLOU7
Click to expand...
Click to collapse
You'll have to wipe the system anyway, updating it will be a waste of time...