Root Can't flash 5.0 image

egernant

Well-Known Member
Factory images for Android 5.0 have been released, as I'm sure you all know by now. I have done this before on the developer preview, so I know the process.

Every time I try to flash this, I get the following error: "error: update package missing system.img". I have followed the step by step instructions manually several times and have even tried it using the Nexus Root Toolkit to automate the process. No luck whatsoever. I used the toolkit to flash 4.4.4 factory image just to make sure it wasn't an issue with my phone. I've checked the md5 sum.

What could possibly be going wrong?
 

NYCHitman1

Gun for Hire
Factory images for Android 5.0 have been released, as I'm sure you all know by now. I have done this before on the developer preview, so I know the process.

Every time I try to flash this, I get the following error: "error: update package missing system.img". I have followed the step by step instructions manually several times and have even tried it using the Nexus Root Toolkit to automate the process. No luck whatsoever. I used the toolkit to flash 4.4.4 factory image just to make sure it wasn't an issue with my phone. I've checked the md5 sum.

What could possibly be going wrong?

It's possible that Google forgot to include the system.img in the image.
 

egernant

Well-Known Member
Thread starter
I think I got it to work... I extracted EVERYTHING to the same platform-tools folder (including the image.zip file), then manually flashed every .img file sequentially instead of using the flash-all.bat file. It's booting up now with the 5.0 boot animation, so God willing, I'll be off to the races shortly.
 

sonyboyj

Well-Known Member
I've been trying to sideload the stupid thing for 2 hour. And always says not verified and aborts install. I don't wanna flash it cause I don't wanna lose all my data. So guess I'll have to wait for the OTA. Which I hope not to far as I have the 4.4.4 image flashed from the the Dev site.
 

Rxpert83

Dr. Feelgood
I had issued with the first time. Redownloading it solved it.

Check the md5 and make sure it matches what google posted.
 

GrenW

Android Expert
Rebooting into bootloader after flashing bootloader and radio (and before flashing the rest of the rom) is the solution from what I've heard.
 
Top