Moto G (1st gen) won't install Android 5.1 update

  • 1
  • Question
  • Updated 2 years ago
  • Answered
Hello,

I own a 1st gen (Nov. 2013) Moto G. About a year ago I unlocked the bootloader and rooted it so that I could install a firewall. I haven't "messed around" with any settings otherwise.

If I recall correctly, sometime during the last year an OS update was 'pushed' and my phone had no trouble updating. However, with the most recent OS update (Lollipop 5.1) my phone continuously goes through the installation motions (briefly) but fails to update. I get a message telling me the install/update was unsuccessful.

 I thought disabling the firewall before updating might help but it had no effect. I am considering a factory rest but am hesitant to do this. Does anyone out there have any advice on how I could make this update work? I would appreciate it!

Oh, by the way - I have not received any message regarding insufficient memory/space - I have approximately 2.5GB free.

Thanks in advance! 
Photo of Chad Wick

Chad Wick

  • 320 Points 250 badge 2x thumb

Posted 2 years ago

  • 1
Photo of Paul Deschamps

Paul Deschamps, Mobile Master

  • 199,448 Points 100k badge 2x thumb
Are you running a custom ROM.?Are you trying to install it OTA?
(Edited)
Photo of Chad Wick

Chad Wick

  • 320 Points 250 badge 2x thumb
Hi Paul,

No custom ROM and yes - trying to install it OTA.
Photo of Tayeb A

Tayeb A, Employee

  • 18,164 Points 10k badge 2x thumb
Hey Chad,

Since you are trying an over-the-air (OTA), you probably need to install the Motorola Update Services app as it's necessary to enable the upgrade to Android 5 on the Moto G (1st Gen.) and some other devices.  Here's the link: http://koo.do/1vQFpBC

Hope this helps!
Photo of Chad Wick

Chad Wick

  • 320 Points 250 badge 2x thumb
Hi Tayeb,

Thanks for the suggestion. I already have the Motorola Update Services app installed so I guess that means this isn't the problem?
Photo of rikkster

rikkster, Mobile Master

  • 67,080 Points 50k badge 2x thumb
If you've left everything as is, no custom recovery, then it should just be a matter of re-locking the bootloader via fastboot (fastboot oem lock) and you should be able to get the OTA upgrade.
(Edited)
Photo of Chad Wick

Chad Wick

  • 320 Points 250 badge 2x thumb
Thank you Rikkster. Could you provide me with specific instructions on how to do that or direct me to a reputable website? Also, would the process of re-locking (and potentially unlocking again) erase any of my current data (pics, apps, etc.)?

Thanks. 
Photo of rikkster

rikkster, Mobile Master

  • 67,080 Points 50k badge 2x thumb
Hi Chad,

I'll be honest, it has been awhile since I've played around with the Moto G 1st. gen and flashing firmware. I do appreciate your patience. I just downloaded a Canadian retail copy of 5.0.2 and it does show the sparsechunk entities as having the decimal point. Unfortunately, my Moto G 1st gen is long gone and most of the information is based on memory and information available on the internet.

mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3 - added or omitted.

Check the Telus factory image you downloaded originally and see if the decimal points are in fact included. I'm continuing my research should that method fail. I still have the recollection that the last sparsechunk line was omitted for some reason. Give it a try either way.
Photo of Chad Wick

Chad Wick

  • 320 Points 250 badge 2x thumb
Hi Rikkster,

I really appreciate the support. I decided to give your latest advice a try a short time ago. Just as you've recognized, the decimals do exist. I eventually realized this and decided to methodically go through the commands one by one. These specifically:

fastboot oem lock begin
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot oem lock

The outcome was a little different this time. Upon entering the last command (fastboot oem lock) the computer displayed, "FAILED <status read failed <Too many links>>" However, I did see the phone display, "Locked!"

Could you please clarify what this means?

The phone then appeared to become locked on the initial screen I see at boot up ("Warning Bootloader unlocked"). I was able to put it back into the fastboot screen where I noticed the following: "Device is LOCKED. Status code: 2" I think this may be some good news?

I selected "Normal power up" from the screen and a new problem may have just emerged - the phone seems stuck on the "powered by android screen" - has been displaying this for the last 10-15 minutes.

What is your take on where I'm at in the process and what I should do next? I am a little worried that the phone seems "stuck" but perhaps this is an easy fix?

Thank you!
Photo of Chad Wick

Chad Wick

  • 320 Points 250 badge 2x thumb
UPDATE:

Rikkster,

I have good news!

After writing my last message I realized that the issue I was having would likely be resolved by flashing the factory image. After entering the following commands and rebooting my phone I was able to download and install Lollipop 5.1 successfully (OTA)!

mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3

I think I'd like to once again root my phone (unless you'd advise against this). The reason being I like having a firewall installed (which requires rooting).

I did this previously by following the steps outlined here:

http://www.cultofandroid.com/46848/rooting-the-moto-g/

http://www.modaco.com/forums/topic/366771-root-your-moto-g-option-1-superboot/

Is there another method you'd recommend? Do you know off hand if I will need a new unlock code? Does rooting necessitate wiping my phone?

Many thanks once again - I really appreciate your diligence and expertise!
Photo of rikkster

rikkster, Mobile Master

  • 67,080 Points 50k badge 2x thumb
You’re welcome Chad and congratulations on getting your Moto G up and running!

To answer an earlier question, your phone is locked. Code 2 means that the bootloader was re-locked. A new unlock code is required because you now have a locked bootloader. Unlocking the bootloader wipes the device as mentioned on Motorola’s bootloader unlocking site.

Rooting normally doesn’t require a factory reset or wipe, if that’s what you’re asking. If the firewall provides an enhanced layer of security, then by all means root the phone. It’s unlikely that the Moto G 1st. gen will get another Android update, so you won’t have to repeat the process of re-locking the bootloader anytime soon.

I’ve departed from the realm of rooting phones for some time now, simply because the phones I’ve been using lately have little if any need for root. My best advice, if what worked previously was easy to understand and worked for you, continue using those methods.
Photo of Chad Wick

Chad Wick

  • 320 Points 250 badge 2x thumb
Thanks again Rikkster. I think I'll hold off on re-rooting for now and see how things go - if I can confidently monitor/restrict data use with the existing android/google settings that should suffice!
Photo of Chad Wick

Chad Wick

  • 320 Points 250 badge 2x thumb
Hi again Rikkster,

Thanks for the comprehensive information! I will give this a go (hopefully in a few days) and report back!