{"id":216,"date":"2014-12-23T19:19:46","date_gmt":"2014-12-24T03:19:46","guid":{"rendered":"http:\/\/eyedtentea.com\/?p=216"},"modified":"2015-08-18T12:48:27","modified_gmt":"2015-08-18T19:48:27","slug":"android-errors-archive-does-not-contain-boot-sig-archive-does-not-contain-recovery-sig","status":"publish","type":"post","link":"https:\/\/eyedtentea.com\/?p=216","title":{"rendered":"Android errors: archive does not contain ‘boot.sig’ & archive does not contain ‘recovery.sig’"},"content":{"rendered":"

I tried updating my Nexus 5 with the latest Lollipop 5.0.1 version. My phone is rooted, so I can’t use the OTA (over-the-air) updater. I attempted to use the same process that I used to update from Kit Kat (4.4.4) to Lollipop 5.0.\u00a0I’ll recap the process:<\/p>\n

    \n
  1. I downloaded the 5.0.1 factory image (hammerhead) from\u00a0https:\/\/developers.google.com\/android\/nexus\/images<\/a><\/li>\n
  2. unpackaged the .tgz<\/code> file<\/li>\n
  3. executed the flash-all.sh<\/code> program (note: I’m on a Mac)<\/li>\n<\/ol>\n

    During step three, I encountered a problem:<\/p>\n

    archive does not contain 'boot.sig'\r\narchive does not contain 'recovery.sig'\r\nfastboot(99706) malloc: *** mmap(size=1006034944) failed (error code=12)\r\n*** error: can't allocate region\r\n*** set a breakpoint in malloc_error_break to debug\r\nfailed to allocate 1005027540 bytes\r\nerror: update package missing system.img<\/pre>\n
    I thought this was due to my phone being encrypted. I tried to troubleshoot, but\u00a0I ended up soft-bricking my phone. I got myself up and running by flashing the Kit Kat 4.4.4 factory image. I also reverted back\u00a0to the\u00a05.0 Lollipop backup I made before attempting the update. I later figured out, this is not an encryption issue (I was able to update my encrypted Nexus 7 to Lollipop 5.0.1 using\u00a0flash-all.sh<\/code> program).<\/p>\n
    From a forum post on XDA (link here<\/a>) suggested flashing the files within the image-XXX.zip<\/code> individually (comment from manasgirdhar<\/em>). I found another forum that clearly state the steps and flashing order of factory images. The steps are found here<\/a>\u00a0(drill down to “Method 2”). Quick recap of the process:<\/p>\n
      \n
    1. expand the\u00a0image-hammerhead-lrx22c.zip<\/code> file<\/li>\n
    2. flash the bootloader.img<\/code> file<\/li>\n
    3. flash the radio.img<\/code> file<\/li>\n
    4. flash the system.img<\/code> file<\/li>\n
    5. flash the userdata.img<\/code>\u00a0file<\/li>\n
    6. flash the boot.img<\/code>\u00a0file<\/li>\n
    7. erase the cache<\/li>\n
    8. from the phone, boot into Android recovery<\/li>\n
    9. from recovery, select “Wipe data\/factory data reset”<\/li>\n
    10. reboot<\/li>\n<\/ol>\n
      I got hung up on step 9. I held down the Volume Up + Power buttons too long and ended up rebooting to the system. The system won’t boot until you do the data wipe\u00a0step. The trick is to push the\u00a0Volume Up + Power buttons simultaneously or, push and hold Volume Up, then press the Power button, making sure not to hold the buttons down too long. If you get stuck in the boot animation, just boot back up into bootloader (hold down: Volume Up + Volume Down + Power), then continue with step 8.<\/p>\n
      As with any system mod you perform on your phone, you and only you are responsible for the outcome. So, please be very careful. If you do not understand how to flash<\/code> a file from your computer to your Android phone, then you shouldn’t attempt to do any of the stuff I’ve posted here. I posted\u00a0procedural steps not literal computer commands. Simply copying and pasting the steps into a command prompt will not work. If you decide to proceed with “Method 2”, please follow the procedure thoroughly as stated in the XDA forum post.<\/p>\n