Tag Archives: android

Android Marshmallow

Android Lollipop to Marshmallow (6.0)

I received an over-the-air notification on my Nexus 5 for Marshmallow (Android 6.0) a few days ago. I put off on doing the update until today. I wanted to make sure I had enough time to migrate all my apps and time to troubleshoot any issues.

In this post, I’m just going to give a quick overview of my update from Lollipop (5.1.1) to Marshmallow (6.0.0). I’ll also provide links to the downloads.


I ran a backup of all user apps using Titanium Backup. Instead of re-downloading the apps from Google Play, I reinstalled the apps  from the backup.

Since this is a major upgrade, I also ran a full Nandroid backup of Lollipop via TWRP.


My Nexus is rooted. I’ve had issues with updating the various Lollipop versions. My resolve was to manually flash each of the system files. I approached the Marshmallow upgrade with the same technique. I downloaded the factory image and ran through the steps (see this post for the steps). Here’s the link to the factory image.


This was also a straight forward process. I used the most current version ( This is the same version I used on the last Lollipop update. Here’s the TWRP Nexus 5 (hammerhead) link.


Reestablishing root was where I came across a problem. I used the Lollipop rerooting method (see this post). I was able to boot into Marshmallow without any issues. The problem was when I tried to update SuperSU via Google Play–it failed. I did a quick search and found Chainfire’s SuperSU 2.52 beta file. I sideloaded that… bad decision. I was stuck in Marshmallow’s boot animation (boot loop). I had to do more digging and found that there is a corresponding boot.img file that needs to be flashed in tandem with the SuperSU beta file.

I got out of my boot loop by holding the volume up & down, and the power buttons together. The resulting key combo boots into bootloader. I connected my Nexus to my Mac and flashed the boot.img file. I then booted into recovery, and installed Chainfire’s SuperSU beta file.

Here’s the XDA post that has a link to the boot.img file. The beta file is found here.

Bonus: workaround for Android Pay credit card input issue

To input a credit card to the Android Pay app, you’ll need to disable root (there’s a checkbox that needs unchecking; check the settings in SuperSU app). Input the credit card info and then reestablish root by checking the box again. I was able to input my credit card using this method. I haven’t tested Android Pay. There’s a possibility this will still fail.

Nexus 5 manual update to 5.1

I encountered issues when I updated my rooted Nexus 5 from 5.0 to 5.01:

archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'

(You can read about that here: blog post). For the 5.1 update, I decided to manually flash all the files, so as to avoid running into the same errors.

The following is a step by step process of how I updated my rooted Nexus 5.

Notice: If you don’t know how to use adb and fastboot, you should just stop right here. You’ll have to reference another tutorial. For those that proceed, you are responsible for your phone. If you brick it, it’s on YOU!


  • download and install adb & fastboot
  • download latest TWRP recovery (openrecovery-twrp-
  • download 5.1 factory image (“hammerhead”)
  • download and prep Chainfire’s CF-Auto-Root (XDA link)
  • run a Nandroid backup and transfer a copy of the backup to your computer
  • (optional) run a full Titanium backup of all your apps and transfer the copies to your computer

Prep of 5.1 factory image

  1. expand the hammerhead-lmy47d-factory-6c1ad81e.tgz file
  2. expand the image-hammerhead-lmy47d.zip file
  3. rename the folder for easier reference (e.g.: extractedZip)
  4. move/copy bootloader-hammerhead-hhz12f.img and radio-hammerhead-m8974a- files to the extractedZip folder
    • the img files are found in the expanded tgz file from step 1
expanded hammerhead-lmy47d-factory-6c1ad81e.tgz

This is the expanded hammerhead-lmy47d-factory-6c1ad81e.tgz file with the three important files highlighted

final modified folder

The folder contents of the extracted zip file, including the relocated bootloader & radio .img files from the .tgz factory image

5.1 update via manual flash

  1. connect computer to phone via USB and boot phone into bootloader
    • command: adb reboot bootloader
  2. install bootloader-hammerhead-hhz12f.img
    • command: fastboot flash bootloader bootloader-hammerhead-hhz12f.img
  3. install radio-hammerhead-m8974a-
    • command: fastboot flash radio radio-hammerhead-m8974a-
  4. install system.img
    • command: fastboot flash system system.img
  5. install userdata.img
    • command: fastboot flash userdata userdata.img
  6. install boot.img
    • command: fastboot flash boot boot.img
  7. install recovery.img
    • command: fastboot flash recovery recovery.img
  8. delete the cache
    • command: fastboot erase cache
  9. from the phone, boot into Recovery
    • background image is of an Android on its back with chest open and red triangle (default system recovery)
  10. press Power + Volume Up buttons to enter into Recovery options
    • note: do NOT press and hold the buttons too long, as this will result in booting into the system (the phone), which will not boot… you’ll be stuck with the boot animation
      • if done accidentally, reboot back into bootloader: Volume Up + Volume Down + Power and continue from step 9
  11. select Wipe data/factory data reset
  12. reboot phone when data wipe is completed
    • booting into a newly installed system will take awhile — be patient!

After installing 5.1 update: Re-root & install custom Recovery

After the update, your phone has a fresh and clean install of Android 5.1… meaning there is no custom recovery, nor root access. However, Bootloader will still be unlocked. The default settings will not have USB Debugging enabled. USB Debugging enables you to run commands from your computer to your phone via USB.

Install TWRP recovery and Chainfire SuperSU:

  1. setup the phone with your existing Gmail account
    • recommend setting up as a new device and use Titanium Backup to reinstall your apps
  2. setup USB Debugging
  3. connect computer to phone via USB and reboot phone into bootloader
  4. flash TWRP recovery: openrecovery-twrp-
    • command: fastboot flash recovery openrecovery-twrp-
  5. execute Chainfire’s CF-Auto-Root
    • Mac command: ./root-mac.sh
      • on a Mac, this will require the admin password of the Mac computer
    • the background will have a red pirate android
    • when complete, the phone will automatically reboot
  6. in Google Play store, update SuperSU to the current version
  7. SuperSU requires updating binary
    • select “Normal” and reboot when finished

Reinstall apps & check phone settings

To reinstall apps, download Titanium Backup and restore from there. If you have issues, I would recommend also using Nandroid Manager (Google Play Store Link). I resolved most of my issues by using Nandroid Manager to install the app and Titanium Backup to install the data.

I recommend checking the phone settings. I’m on Ting (MVNO provider on the Sprint network; CDMA), so I updated my PRL and profile. The default for “Preferred network type” is set to Global; I had to update that to LTE.

factory image errors

Android errors: archive does not contain ‘boot.sig’ & archive does not contain ‘recovery.sig’

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. I’ll recap the process:

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

During step three, I encountered a problem:

archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
fastboot(99706) malloc: *** mmap(size=1006034944) failed (error code=12)
*** error: can't allocate region
*** set a breakpoint in malloc_error_break to debug
failed to allocate 1005027540 bytes
error: update package missing system.img

I thought this was due to my phone being encrypted. I tried to troubleshoot, but I 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 to the 5.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 flash-all.sh program).

From a forum post on XDA (link here) suggested flashing the files within the image-XXX.zip individually (comment from manasgirdhar). I found another forum that clearly state the steps and flashing order of factory images. The steps are found here (drill down to “Method 2”). Quick recap of the process:

  1. expand the image-hammerhead-lrx22c.zip file
  2. flash the bootloader.img file
  3. flash the radio.img file
  4. flash the system.img file
  5. flash the userdata.img file
  6. flash the boot.img file
  7. erase the cache
  8. from the phone, boot into Android recovery
  9. from recovery, select “Wipe data/factory data reset”
  10. reboot

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 step. The trick is to push the Volume 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.

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 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 procedural 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.

adb push & adb pull to transfer from Mac to Android device

Here’s a screencast of a tip/tutorial on how to transfer files or folders between an Android device and a Mac. There is a GUI utility called Android File Transfer that’s more intuitive. The only problem is that it sometimes fails [read: crashes] on transferring large files. I found adb technique to be consistent and fast.

I also used adb shell to establish a shell in the Android device. I would then locate the target file or the target directory. Once found, I would copy and paste the path to complete the command:

adb pull /pathOfFolder_onAndroidDevice/filename /pathToMacFolder
adb push /pathToMacFolder/filename /pathOfFolder_onAndroidDevice

Using a two terminal window allows me to copy the path onto the other terminal window containing the command. This saves from exiting the shell in order to type the command.