• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root Manual update... do I need to flash the bootloader...?

pthubbard

Lurker
Nov 11, 2015
5
3
I have an unlocked/rooted Nexus 7 (2013) running 6.0.0 (mra58u). I want to update to the latest build (mra58v). I have been using NRT but the latest version 2.06 has a bug that doesn't recognize the unlock state of the bootloader (http://www.wugfresh.com/forums/thread/nexus-7-2013-boot-lock-status-issue/). So I thought I would do this manually. I don't want to wipe the data. I have all the .img files. The question is do I need to flash the bootloader or just the system.img, boot.img, recovery.img, & cache.img? I've read the thread on doing a manual update but I'm not clear about this. Obviously, I'm a nube, so any other advice would be welcome.
 
Welcome to our AndroidForums, @pthubbard :).

First off, I'm going to move your thread over to the N7 (2nd gen) root area for you.

Secondly, here's a good guide to show you how to manually flash the factory image for any Nexus device:


Notice that I emphasized "guide" since the latest versions of the images available obviously change over time, so you'll have to substitute the current and/or one you want to use for the one referenced in the guide.

I'm pretty sure that if you don't want to wipe your data, then in Step 11, omit the "-w" switch from the fastboot -w update "name of zip file" command.

You can (and maybe should...;)) take a Nandroid backup first and squirrel it off to a safe place (PC, external USB, etc.) just for insurance purposes.

Hope that helps...if I missed anything, I'm sure others will chime-in :).

Cheers!
 
  • Like
Reactions: iowabowtech
Upvote 0
Thanks for the reply. The guide you refer to is the one I'm trying to understand. It starts out by assuming that the bootloader is locked. Mine isn't so I'm wondering if step 9 (reflash the bootloader) is necessary. I'm a little leary of doing this if it isn't required. Also, I think I'd like to do the 'alternative' method mentioned in step 11;

"Alternatively, you could extract all the .img files in the zip file and flash them manually one at a time. This makes things really handy if you're using the factory image to act as an update rather than a complete return to stock. If trying to update using the factory image, extract the .img from the zip file into the same directory as your bootloader and radio img files and execute the following commands in order:"
I'm thinking this is better suited to what I want to do which is basically just update to the latest build without loosing data.

Thanks again.
 
Upvote 0
Okay, cool...if your bootloader is unlocked, then you just have to skip the part (step #7) where you would do the "fastboot oem unlock".

Also, after you unpack the factory image, you'll see a flash-all.bat (for Windows) and a flash-all.sh (for Linux or the Mac) that contain / show all of the same commands that @jhawkkw outlined in his excellent guide (he just elaborates and explains the entire process for you in a very understandable way).

So, you can basically just copy/paste the commands directly from these files to your command prompt--just be sure to omit the "-w" on the last command where you see the fastboot -w update image-*.zip.

Make sense?

(also, the Nandroid backup thing, too :))
 
  • Like
Reactions: iowabowtech
Upvote 0
Ok. So the 'flash-all.bat' includes the 'fastboot flash bootloader' command. You're saying that it is necessary do flash the bootloader to do the update? Can you explain what this will do? I'm just not sure why the bootloader needs to be flashed too. According to that guide, flashing the bootloader incorrectly could brick the device. I will do another backup before I begin, of course.
 
  • Like
Reactions: scary alien
Upvote 0
Yeah, the bootloader gets updated occasionally, too--flashing a new version won't affect your bootloader lock state, so no worries there.

I think the cautions / warnings about flashing of the bootloader (which actually applies to all of the other partitions, too, IMO) is that you don't want to interrupt that flashing operation (or write / flash the wrong file) since it could leave you with a device that you can no longer boot or flash to.

If you copy/paste the commands, you''ll be fine :).
 
Upvote 0

BEST TECH IN 2023

We've been tracking upcoming products and ranking the best tech since 2007. Thanks for trusting our opinion: we get rewarded through affiliate links that earn us a commission and we invite you to learn more about us.

Smartphones