5.0.1 Update

kingdave · Dec 17, 2014

My Nexus 5 has alerted me twice this evening that the update us available. When I download it then hit the restart and install button my phone switches off, restarts and then I get an unspecified error message that looks like a dead Android with his chest open and a red triangle on top.

If I then hold the power button it restarts the phone but with version 5 and a couple of hours later tells me the 5.0.1 update is available and the whole error process starts again.

I'm on stock, no rooting or other modifications are present on my device.

Any ideas how to solve this?

BynoUK · Dec 18, 2014

That's a strange one, I've got that issue too but it's because I am rooted (it's a little task for me to sort later because the notification is beginning to annoy me)

Usually you only see that error because the OTA won't install due to system files being altered. I've no idea why you're experiencing this, hopefully someone with knowledge will be along soon bud.

nedsram · Dec 18, 2014

9878 said:
I received the update OTA on Sprint San Antonio yesterday. Don't notice anything good or bad, yet....

Lollipop 5.0.1 fixed a nasty problem on my Nexus 5. Since the original Lollipop release, I had been unable to connect to my Windows PC via the USB cable. (Nothing happened.) Now the disk appears in Windows Explorer as it used to.

rhray · Dec 18, 2014

After running 5.0.1 for a few days, I can tentatively state that all of my battery woes have been erased. Even with location settings on high, my device sleeps like a champ and discharges normally!

326 · Dec 18, 2014

So curious as I'm not very knowledgeable with the rooting/flashing process. I did however get 5.0 Lollipop on my device prior to OTA using a tool to help. My device went from 32gb to 16gb after the update. I understand that I'm supposed to delete the user cache which makes sense yet I'm not familiar with the process. Damn my impatience.

So my question is, if I wait for the 5.0.1 update OTA and let it do it's normal update will the new image on my Nexus 5 when installed restore to 32gb or will I have to root it and delete the user cache still?

Thanks in advance,
326

rhray · Dec 18, 2014

326 said:
So curious as I'm not very knowledgeable with the rooting/flashing process. I did however get 5.0 Lollipop on my device prior to OTA using a tool to help. My device went from 32gb to 16gb after the update. I understand that I'm supposed to delete the user cache which makes sense yet I'm not familiar with the process. Damn my impatience.

So my question is, if I wait for the 5.0.1 update OTA and let it do it's normal update will the new image on my Nexus 5 when installed restore to 32gb or will I have to root it and delete the user cache still?

Thanks in advance,
326

You probably need to start from scratch and download the factory images for 5.0.1 and redo the whole phone.

Go here: https://developers.google.com/android/nexus/images and download the factory images and then...

Read this thread because you didn't install 5.0 correctly the first time: http://androidforums.com/threads/guide-how-to-flash-a-nexus-factory-image-manually.706533/

Good luck!

Edit: take my advice with caution, I'm usually formatting and reflashing things all the time. I don't think I've allowed an ota upgrade to my phone since android version 2.3. I much prefer a fresh install

Hook · Dec 18, 2014

326 said:
So curious as I'm not very knowledgeable with the rooting/flashing process. I did however get 5.0 Lollipop on my device prior to OTA using a tool to help. My device went from 32gb to 16gb after the update. I understand that I'm supposed to delete the user cache which makes sense yet I'm not familiar with the process. Damn my impatience.

So my question is, if I wait for the 5.0.1 update OTA and let it do it's normal update will the new image on my Nexus 5 when installed restore to 32gb or will I have to root it and delete the user cache still?

Thanks in advance,
326

You may just need to Factory reset once or twice. I had to do it once on my Nexus 5 and twice on my Nexus 7 to get the right internal memory size, but then everything works fine.

kingdave · Dec 18, 2014

Well that's curious.

The update that was unable to install previously was 13Mb, and tonight I've got a notification of the update still being available, however this time it's 33Mb.

I've installed it and no errors so far. Has just finished rebooting and optimising my apps.

Fingers crossed!

Hook · Dec 18, 2014

kingdave said:
Well that's curious.

The update that was unable to install previously was 13Mb, and tonight I've got a notification of the update still being available, however this time it's 33Mb.

I've installed it and no errors so far. Has just finished rebooting and optimising my apps.

Fingers crossed!

Sounds like you initially got a bad download.

Deleted User · Dec 22, 2014

g01851 said:
You can also use WUG's toolkit to automate the process. Fairly easy to use, but still requires a bit of techie talent.

http://www.wugfresh.com/nrt/

Forgot to mention that i use a MacBook Pro, so Wug's is a no go.

lunatic59 · Dec 22, 2014

grunt0300 said:
Forgot to mention that i use a MacBook Pro, so Wug's is a no go.

It's a little more work to flash it manually with fastboot, but it's pretty much the same process on Win/Mac/Nix.

This article has got the links to everything you'll need.

Deleted User · Dec 22, 2014

lunatic59 said:
It's a little more work to flash it manually with fastboot, but it's pretty much the same process on Win/Mac/Nix.

This article has got the links to everything you'll need.

O.K., let's see if i have this right. I have the .tgz file(hammerhead 5.0) on my desktop, within a folder named "android", and then "platform-tools". So, after unlocking the bootloader, and letting the phone reboot, i flash this command in terminal on my Mac... ./all-sh/desktop/android/platform-tools/hammerhead.tgz. Does that sound right? o_O

lunatic59 · Dec 22, 2014

If you're flashing system images, why not go right to 5.01?

In any event, assuming you've copied the images to the platform-tools folder, that will flash everything.

Deleted User · Dec 22, 2014

lunatic59 said:
If you're flashing system images, why not go right to 5.01?

In any event, assuming you've copied the images to the platform-tools folder, that will flash everything.

I didn't know that i could go from 4.4.4 to 5.0.1. I was also told to do a factory reset after installing 5.0 and then 5.0.1. What's your advice on that?

jj14x · Dec 22, 2014

grunt0300 said:
I didn't know that i could go from 4.4.4 to 5.0.1. I was also told to do a factory reset after installing 5.0 and then 5.0.1. What's your advice on that?

If you are flashing factory images, there is no reason to go to 5.0 and then to 5.0.1 using OTA - there are factory images for 5.0.1 - save yourself some time and just flash the 5.0.1 directly.

Usually, a factory reset isn't required, but for this major update (4.x to 5.x), a factory reset is recommended (several people are reporting issues without the reset - though I'm sure there are a lot of people who are happy without the factory reset). If you are ok with starting clean with a fresh install, I'd highly recommend it.

Edit: I'm not familiar with the commands on a Mac, so can't confirm the command you listed there. On Windows, I'd either flash the individual images one by one in the right sequence, or just use the flash-all.bat instead. Just need to verify that Windows has the right drivers (and latest fastboot) before anything.

vandyman · Dec 22, 2014

on another note 5.01 is old news... moving on to 5.02....

vandyman · Dec 22, 2014

vandyman said:
on another note 5.01 is old news... moving on to 5.02...(hopefully before January) .

Deleted User · Dec 22, 2014

jj14x said:
If you are flashing factory images, there is no reason to go to 5.0 and then to 5.0.1 using OTA - there are factory images for 5.0.1 - save yourself some time and just flash the 5.0.1 directly.

Usually, a factory reset isn't required, but for this major update (4.x to 5.x), a factory reset is recommended (several people are reporting issues without the reset - though I'm sure there are a lot of people who are happy without the factory reset). If you are ok with starting clean with a fresh install, I'd highly recommend it.

Edit: I'm not familiar with the commands on a Mac, so can't confirm the command you listed there. On Windows, I'd either flash the individual images one by one in the right sequence, or just use the flash-all.bat instead. Just need to verify that Windows has the right drivers (and latest fastboot) before anything.

Well, at least i've got this bootloader unlocked. Can't figure out how to flash the 5.0.1 from my Mac. Tried different commands, with no luck. Any help would be greatly appreciated. Thanks.

thisISjoel · Dec 22, 2014

grunt0300 said:
Well, at least i've got this bootloader unlocked. Can't figure out how to flash the 5.0.1 from my Mac. Tried different commands, with no luck. Any help would be greatly appreciated. Thanks.

Assuming you've got the android sdk downloaded and your phone in fastboot mode (to check this open terminal and type in "fastboot devices" and your device serial number should show up).

You then need to change your directory to wherever you have the factory image file (it's easiest if the folder is on the desktop). To do this type into terminal "cd <location of the folder containing the factory image file>"

If you're going to be flashing each image individually you must unzip the image and make sure you change the directory in the terminal to the folder containing the separate image files recovery.img, cache.img etc.).

Once you've got terminal looking in the right place and your phone is connected in fast boot mode it's pretty simple.

The commands are all prefaced by "fastboot" so for example to flash the recovery you type into terminal "fastboot flash recovery recovery.img" this will flash the new recovery. Do this for every .img file EXCEPT user data then use command "fastboot reboot" to reboot your phone.

The initial boot will take a few minutes, don't panic.

Deleted User · Dec 22, 2014

thisISjoel said:
Assuming you've got the android sdk downloaded and your phone in fastboot mode (to check this open terminal and type in "fastboot devices" and your device serial number should show up).

You then need to change your directory to wherever you have the factory image file (it's easiest if the folder is on the desktop). To do this type into terminal "cd <location of the folder containing the factory image file>"

If you're going to be flashing each image individually you must unzip the image and make sure you change the directory in the terminal to the folder containing the separate image files recovery.img, cache.img etc.).

Once you've got terminal looking in the right place and your phone is connected in fast boot mode it's pretty simple.

The commands are all prefaced by "fastboot" so for example to flash the recovery you type into terminal "fastboot flash recovery recovery.img" this will flash the new recovery. Do this for every .img file EXCEPT user data then use command "fastboot reboot" to reboot your phone.

The initial boot will take a few minutes, don't panic.

O.K., this is what i have. A folder on my desktop named "android". A subfolder within android, named "platform-tools. In the platform-tools folder i have...hammerhead lrx22c...tgz, image-hammerhead lrx22c...zip, radio-hammerhead-m8974a....2.22.img, adb & fastboot. This is what i flashed the first time... ./flash-all.sh/desktop/android/platform-tools/hammerhead.tgz Was i supposed to start the commands with the word "fastboot"?

thisISjoel · Dec 23, 2014

grunt0300 said:
O.K., this is what i have. A folder on my desktop named "android". A subfolder within android, named "platform-tools. In the platform-tools folder i have...hammerhead lrx22c...tgz, image-hammerhead lrx22c...zip, radio-hammerhead-m8974a....2.22.img, adb & fastboot. This is what i flashed the first time... ./flash-all.sh/desktop/android/platform-tools/hammerhead.tgz Was i supposed to start the commands with the word "fastboot"?

What happened when you ran that command?

The way I have always done it is as follows:

1. Ensure all relevant files/folders are downloaded and easily accessible (and, if necessary, unzipped) (i.e. on the desktop).

2. Put phone in fastboot mode and connect to macbook via USB.

3. Open terminal and check that phone is available as a fastboot device (command "fastboot devices").

4. Change termial directory to relevant file location (command "cd Desktop/<name of folder>/<name of subfolder>/").

5. Flash whatever I want to flash (commad "fastboot flash <type of image> <name of image>" for example to flash a recovery image the command is "fastboot flash recovery recovery.img")

If done correctly the terminal will print a bunch of text and stuff will be happening on the phone too, if done incorrectly errors such as "command not found" or "no such file" type stuff can happen.

Just a quick note, I have used the "flash-all.sh" thing once, amd I'm pretty sure it was just "./flash-all.sh" so as far as I know as long as you have changed your directory to the correct location BEFORE running that command it should work. Recently I have been flashing each image seperately as to preserve my user data

I hope this post has been somewhat helpful

Any further questions do not hesitate to ask, although I can't promise to be helpful, this is pretty much the extent of my knowledge.

Happy Flashing!!!

Deleted User · Dec 23, 2014

thisISjoel said:
What happened when you ran that command?

The way I have always done it is as follows:

1. Ensure all relevant files/folders are downloaded and easily accessible (and, if necessary, unzipped) (i.e. on the desktop).

2. Put phone in fastboot mode and connect to macbook via USB.

3. Open terminal and check that phone is available as a fastboot device (command "fastboot devices").

4. Change termial directory to relevant file location (command "cd Desktop/<name of folder>/<name of subfolder>/").

5. Flash whatever I want to flash (commad "fastboot flash <type of image> <name of image>" for example to flash a recovery image the command is "fastboot flash recovery recovery.img")

If done correctly the terminal will print a bunch of text and stuff will be happening on the phone too, if done incorrectly errors such as "command not found" or "no such file" type stuff can happen.

Just a quick note, I have used the "flash-all.sh" thing once, amd I'm pretty sure it was just "./flash-all.sh" so as far as I know as long as you have changed your directory to the correct location BEFORE running that command it should work. Recently I have been flashing each image seperately as to preserve my user data

I hope this post has been somewhat helpful Any further questions do not hesitate to ask, although I can't promise to be helpful, this is pretty much the extent of my knowledge.

Happy Flashing!!!

When i put phone in "bootloader mode", the red arrow says Restart bootloader. Am i supposed to hit the power button to restart that process? I'm having a hard time with the terminal commands. Thanks. :thinking:

lunatic59 · Dec 23, 2014

"flash-all.sh" is just a shell script to automate the commands. It's probably a good thing that it failed because it also flashes the user data image, which would wipe all your data.

This is what the script for 5.01 contains ...

Code:

fastboot flash bootloader bootloader-hammerhead-hhz12d.img
fastboot reboot-bootloader
sleep 5
fastboot flash radio radio-hammerhead-m8974a-2.0.50.2.22.img
fastboot reboot-bootloader
sleep 5
fastboot -w update image-hammerhead-lrx22c.zip

What it does is flash the bootloader and restart it. Then it flashes the radio and restarts again. Finally, it flashes the factor image, but that "-w" option instructs it to wipe and format the user data partition. Without that it will simply overwrite the system rom and leave the user data intact.

You can issue the following commands from the command line one at a time

Code:

fastboot flash bootloader bootloader-hammerhead-hhz12d.img
fastboot reboot-bootloader
fastboot flash radio radio-hammerhead-m8974a-2.0.50.2.22.img
fastboot reboot-bootloader
fastboot update image-hammerhead-lrx22c.zip

and then reboot your phone. You should then be on 5.01

lunatic59 · Dec 23, 2014

grunt0300 said:
When i put phone in "bootloader mode", the red arrow says Restart bootloader. Am i supposed to hit the power button to restart that process? I'm having a hard time with the terminal commands. Thanks.

If this is the screen you see, then just plug it in to your Mac and set it down ... this is fastboot mode.

Deleted User · Dec 23, 2014

typed in commands exactly as written, and getting "no such file exists". This is day two of trying to flash the update. My frustration level is definitely rising. It took all of about 15 seconds to unlock the bootloader!
Terminal keeps telling me that the .img file doesn't exist, or can't be found. I don't have that .img file in my folder.

5.0.1 Update

Android Enthusiast

Android Enthusiast

Lurker

Well-Known Member

Newbie

Well-Known Member

Ever since DU... ;-)

Android Enthusiast

Ever since DU... ;-)

Deleted User

Guest

Moderati ergo sum

Deleted User

Guest

Moderati ergo sum

Deleted User

Guest

Android Expert

Android Expert

Android Expert

Deleted User

Guest

Android Enthusiast

Deleted User

Guest

Android Enthusiast

Deleted User

Guest

Moderati ergo sum

Moderati ergo sum

Deleted User

Guest

BEST TECH IN 2023

Smartphones

Best Android Phones

Upcoming

Best iPhones

Upcoming

Tablets

Best Tablets

Upcoming

Laptops

Best Laptops

Upcoming

Televisions

Best TVs

Upcoming

Game Consoles

Best Game Consoles

Upcoming

Wearables

Best Wearables

Upcoming

Smart Home

Smart Home Tech

Upcoming

Similar threads