Database Users

[GUIDE] Flashing a Factory Image with fastboot / return to stock

Notice: If you are going to flash the nakasi android 4.3 JWR66Y factory image, you will need to download the bootloader from JWR66V and replace the one from the factory image. The bootloader in JWR66Y will fail flashing with a signature mismatch error on the device and InvalidState on fastboot.
The objective of this thread is to provide detailed instructions on flashing a factory image using fastboot rather than a toolkit. As good as toolkits can be, I recommend using adb and fastboot directly. This will allow you to see what is happening every step of the way and is a good opportunity to learn about the process. The following instructions assume some basic Windows command prompt skills.
Read all the directions before you begin and perform the steps at your own risk.
Overview
This will restore your Nexus 7 to it’s factory state. All user data will be deleted, so now is a good place to stop and backup anything you don’t want to lose.
This guide is in three parts - basic knowledge and obtaining the required software, driver installation, and flashing the factory image. This and any following verbosity is not to be condescending, but rather not to assume anything.
Basic Knowledge
This guide assumes some basic Windows command prompt skills - changing directories, etc and is written primarily for Windows users. Make sure that you have file extensions enabled in Windows Explorer.
Software Requirements
Android SDK - adb, fastboot, usb drivers
Java SE Development Kit - required by Android SDK
A Nexus 7 factory image
7-Zip - used to extract factory images from a .tgz file
Download and install 7-Zip - http://www.7-zip.org/download.html
Download the Nexus 7 factory image - https://developers.google.com/android/nexus/images#nakasi and save it somewhere you can easily retrieve it.
Make sure to download the correct image for your device variant (Wi-Fi vs GSM/HSPA+; nakasi vs nakasig)
Download and install the Java SE JDK - http://www.oracle.com/technetwork/java/javase/downloads/index.html
Download and install the Android SDK - http://dl.google.com/android/installer_r21-windows.exe
NOTE: Notice the install location. This defaults to C:\Users\<user name>\AppData\Local\Android\android-sdk the platform tools (adb, fastboot) and usb drivers will be downloaded to this location. This will be referred to from here on as your sdk directory
Run the SDK Manager
Under Tools, check the box labeled "Android SDK Platform-tools" - this provides adb and fastboot
Under Extras, check the box labeled "Google USB Driver"
Press the "Install # packages..." button and follow the on-screen instructions.
The platform tools will be installed at <your sdk directory>\platform-tools and the usb drivers will be in <your sdk directory>\extras\google\usb_driver
Driver Installation
This seems to be the most confusing part for many people. Be patient and thoroughly read all the instructions.
Huge thanks to @tetakpatak for taking the time to put together a video showing this process! http://www.youtube.com/watch?v=bhA5CN4335U&feature=player_detailpage..
Enable usb debugging on your device (found under Settings > Developer Options)
NOTE: Since Android 4.2 the Developer Options are hidden by default.
To enable them, go to Settings > About Phone, and tap on build number around seven times. A small dialog will appear letting you know "You are now a developer!"
Install the abd driver - detailed instructions for installing or upgrading and existing driver on your version of Windows can be found at http://developer.android.com/tools/extras/oem-usb.html
Once the driver is installed open a command prompt and change directories to <your sdk directory>\platform-tools (see #2). From the command prompt run "adb devices". This will list any adb-capable devices that are connected to the computer by their serial number assuming your drivers are installed correctly. Recap:
Code:
> cd \Users\<user name>\AppData\Local\Android\android-sdk\platform-tools
> adb devices
# the following output should be returned
List of devices attached
<device serial number> device
Use adb to boot the device to the bootloader:
Code:
> adb reboot-bootloader
The device should now be in fastboot mode and Windows should be attempting to install the fastboot driver. NOTE: if you had drivers previously installed, you may need to upgrade them. This is the same procedure described at http://developer.android.com/tools/extras/oem-usb.html
You can verify that the driver has been installed by running the following command:
Code:
> fastboot devices
# the following output should be returned
<device serial number> fastboot
Do not proceed further if fastboot can not recognise your device. You are in driver hell and this must be resolved before continuing.
Extract the Factory Image
In order to extract the necessary files from the factory image archive, we will use 7-Zip because it can do this reliably. At this point you should have already installed 7-Zip and downloaded the factory image archive.
Use 7-Zip to open the factory image .tgz file. You should see a single .tar file. Open this file with 7-Zip as well.
Inside the .tar file is a directory that will resemble “nakasi-jwr66y”. Open that directory and extract the contents to <your sdk directory>\platform-tools.
The extracted files should be as follows: bootloader-grouper-4.23.img, image-nakasi-jwr66y.zip, flash-all.sh, flash-base.sh
Flashing the Factory Image
Put the device into fastboot mode by running the following adb command:
Code:
> adb reboot-bootloader
In order to do anything useful in fastboot, the bootloader must be unlocked. To do this, run the following fastboot command:
Code:
> fastboot oem unlock
Follow the directions on the device, using the volume and power buttons to select "Yes". NOTE: this will wipe all personal data.
In fastboot with your device's bootloader unlocked, run the commands listed in flash-all.sh in sequence, waiting for each command to finish.
Follow the commands for your device variant - Wi-Fi (nakasi) or GSM/HSPA+ (nakasig). For convenience I have them here:
NOTE: you will see some messages about the archive not containing boot.sig, recovery.sig and system.sig. That is normal, dont worry.
Wi-Fi devices (nakasi)
Code:
> fastboot erase boot
> fastboot erase cache
> fastboot erase recovery
> fastboot erase system
> fastboot erase userdata
> fastboot flash bootloader bootloader-grouper-4.23.img
> fastboot reboot-bootloader
> fastboot -w update image-nakasi-jwr66y.zip
GSM/HSPA+ devices (nakasig)
Code:
> fastboot erase boot
> fastboot erase cache
> fastboot erase recovery
> fastboot erase system
> fastboot erase userdata
> fastboot flash bootloader bootloader-tilapia-4.23.img
> fastboot reboot-bootloader
> fastboot flash radio radio-tilapia-1231_0.18.0_0409.img
> fastboot reboot-bootloader
> fastboot -w update image-nakasig-jwr66y.zip
After the final command completes, the device will reboot.
If you are sending the device in for warranty work, you may want to re-lock the bootloader
Code:
> fastboot oem lock
Finally, reboot the device
Code:
> fastboot reboot

Fantastic work!

Thank you for this tutorial! It allows us to learn how to do things via adb and learn how not to depend on a toolkit. I hope everyone that does not know how to flash things manually read this thread! Thank you for taking the time to help us learn!

comminus said:
Overview
This will restore your Nexus 7 to it’s factory state. All user data will be deleted, so now is a good place to stop and backup anything you don’t want to lose.
This guide is in three parts - basic knowledge and obtaining the required software, driver installation, and flashing the factory image. This and any following verbosity is not to be condescending, but rather not to assume anything.
Click to expand...
Click to collapse
Could I suggest adding a fourth section to you guide that you only alluded to. Backing up and restoring "anything you don’t want to lose." Detailed as your guide is, you've started with the assumption that a user knows how it back and reinstall the data they would likely want to save.
I don't even know how to do this so I'm stymied even before starting your guide.

Pariah3000 said:
Could I suggest adding a fourth section to you guide that you only alluded to. Backing up and restoring "anything you don’t want to lose." Detailed as your guide is, you've started with the assumption that a user knows how it back and reinstall the data they would likely want to save.
I don't even know how to do this so I'm stymied even before starting your guide.
Click to expand...
Click to collapse
You can always hook your phone up to your PC and copy your folders before this process. You can also make a nano back up and copy it to your computer and then drag it to the SD of your replacement phone and restore it after you get set up and rooted. Titanium back up is another good app to save your apps and data but you will still need to copy that folder to your pc before performing this and then re root your phone so you can restore from titanium back up. Best bet if you are happy with your set up is do a nano back up save that to your PC and now you have a back up to get back to where you were before.

Pariah3000 said:
Could I suggest adding a fourth section to you guide that you only alluded to. Backing up and restoring "anything you don’t want to lose." Detailed as your guide is, you've started with the assumption that a user knows how it back and reinstall the data they would likely want to save.
I don't even know how to do this so I'm stymied even before starting your guide.
Click to expand...
Click to collapse
The backup and restore of user data was intentionally left out because it is out-of-scope for this guide. You bring up a valid point about users needing direction for backing up and potentially restoring user data and files. I'd be more than happy to link to some existing guides that cover this topic in detail. I'll take a look around to see what I can find.
Sent from my Nexus 7 using Tapatalk 2

Thank you very much for this! Worked perfect and this gave me the confidence to do it manually and stay away from toolkits. Back to stock and locked bootloader ready to go back to the store.

sikagoon7 said:
I'm surprised this is just coming up. Thanks though!
Click to expand...
Click to collapse
I know I read your thread sorry about your loss. These tutorials help us learn how to do things manually and safe from making mistakes. Thanks again to the OP.

Excellent work comminus.... very well written!

Help help help!!! Lol
im running into problems..... fastboot wont work.... i have unlocked using fastboot no problem and can also use erase commands no problems.
however when it comes to " flash" or "update" commands, all i get is sending data and the size of what it is sending, but nothing happens. it just hangs there and nothing flashes up on my tablet either. the device hasnt hung as can still use vol keys to change options.
can anybody help me out with a solution here because im going insane!!
---------- Post added at 02:46 PM ---------- Previous post was at 02:31 PM ----------
im running into problems..... fastboot wont work.... i have unlocked using fastboot no problem and can also use erase commands no problems.
however when it comes to " flash" or "update" commands, all i get is sending data and the size of what it is sending, but nothing happens. it just hangs there and nothing flashes up on my tablet either. the device hasnt hung as can still use vol keys to change options.
can anybody help me out with a solution here because im going insane!!

Thanks for this guide I am following it for installing stock image. I'm getting until the last stage but when doing the fastboot -w update xxx.zip file I'm getting error messages saying 'image does not contain recovery.sig, image does not contain system.sig, image does not contain boot.sig' and then it fails to install.
Any idea what I'm doing wrong here?
Thanks
Edit: got it to work using a different windows machine - probably a driver issue somehwere it must have been

Glad to hear you got it working. Those sort of issues are almost always related to drivers.
Sent from my GT-I9100 using Tapatalk 2

Thanks for the excellent explanation. Got my N7 working again. (messed up the upgrade to 4.1.2)
Also got the error 'image does not contain recovery.sig, image does not contain system.sig, image does not contain boot.sig' but installation still worked.

Eeprom78 said:
Thanks for the excellent explanation. Got my N7 working again. (messed up the upgrade to 4.1.2)
Also got the error 'image does not contain recovery.sig, image does not contain system.sig, image does not contain boot.sig' but installation still worked.
Click to expand...
Click to collapse
I will update the instructions to mention that this is normal. Glad to hear you were able to get you N7 working again!

Great Sticky..
Thanks for the work on this.. my N7 was acting strange with one of the installed ROMs and
this guide helped me restore the device easily. :good::good::good::good::good::good:

This guide is great, I did a factory flash some weeks ago just to see how the procedure works and it is pretty easy if you know this stuff, but as a galaxy S3 owner I wonder why there's nothing equivalent to odin for the nexus 7? Afaik odin works for the gnexus. Odin makes reflashing stock images ridiculously easy.
Sent from my Nexus 7 using xda app-developers app

mertzi said:
This guide is great, I did a factory flash some weeks ago just to see how the procedure works and it is pretty easy if you know this stuff, but as a galaxy S3 owner I wonder why there's nothing equivalent to odin for the nexus 7? Afaik odin works for the gnexus. Odin makes reflashing stock images ridiculously easy.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Thanks for the comments. Once someone has their computer set up to work with fastboot the process is just as simple as using Odin. The factory image archive contains batch and shell scripts which allow you to flash the images in one command - arguable just as easy as using Odin or Heimdall. But then, it's all personal preference anyway

do i have to do the erase commands before the flashing

I suppose its not technically required but I recommend you follow the steps as they've been laid out.
Sent from my GT-I9100 using Tapatalk 2

What if I can't go to fastboot because my nexus now only can be booted in cwr . Do you have any solutions regarding my matters?
Thanks,

Update android 4.4.2 fail/error7

Lots of people having the same problem, they get an error when they install the update on there rooted nexus.
I tried this, and i wanna share it with you guys.
First download the update file from google. (The occam-kot49h-factory-02e344de file)
Then extract it, when you get the zip extract this too. (Till you get the image-occam-kot49h folder, in this folder you can find: android-info.txt, boot.img, recovery.img, system.img and userdata.img)
Connect your device to the pc.
Now you have to use adb,
Open your terminal or cmd for Windows : cd C:\Users\YOUR_DIRECTORY\sdk\platform-tools
Then get into the bootloader:
Adb reboot-bootloader ( or start manually: Volume up + unlock button.)
Enter this in cmd:
fastboot erase system
(fastboot erase data)
(fastboot erase userdata)
fastboot erase boot
Now you can flash Android Kitkat 4.4.2:
fastboot flash system system.img
(or Fastboot flash system C:\YOUR_DIRECTORY\occam-kot49h-factory-02e344de\occam-kot49h-factory-02e344de\occam-kot49h\image-occam-kot49h\system.img)
fastboot flash boot boot.img
(or again Fastboot flash boot C:\YOUR_DIRECTORY\occam-kot49h-factory-02e344de\occam-kot49h-factory-02e344de\occam-kot49h\image-occam-kot49h\boot.img )
And reboot.
This worked for me, I'm not responsible for anything. I used this method and it worked for me. Personally I didn't use the fastboot erase, just fastboot erase system and fastboot flash system system.img and fastboot flash boot boot.img. I updated from android 4.4 to 4.4.2.
Sorry for my bad english, still learning..
Sent from my Nexus 4 with kitkat 4.4.2using xda app-developers app

I hope this solves the problem for you, leave some feedback or hit thanks when I helped you.
Have a nice day
Sent from my Nexus 4 using xda app-developers app

Thanks, there is nothing wrong with your English. Unfortunately I am too much of a noob to understand what you are saying. I have had the Error 7 twice now with failed automatic updates and it's scaring me.
I followed step by step instructions to make Flash run on my N5 - which were hard, but worth it because it meant the phone would actually work on the internet, even though Dolphin has that much-hatedl dolphin button right in the way that I hit at least 200 times a day when I scroll.
Can anyone please re-write these instruction into TOTAL noob-speak, including things like 'this next step will trash all your apps, data and photos so back up you phone first by doing X, Y and Z'.
Many thanks

G1MFG said:
Thanks, there is nothing wrong with your English. Unfortunately I am too much of a noob to understand what you are saying. I have had the Error 7 twice now with failed automatic updates and it's scaring me.
I followed step by step instructions to make Flash run on my N5 - which were hard, but worth it because it meant the phone would actually work on the internet, even though Dolphin has that much-hatedl dolphin button right in the way that I hit at least 200 times a day when I scroll.
Can anyone please re-write these instruction into TOTAL noob-speak, including things like 'this next step will trash all your apps, data and photos so back up you phone first by doing X, Y and Z'.
Many thanks
Click to expand...
Click to collapse
Follow this gudie using the latest occam images: http://forum.xda-developers.com/showthread.php?t=2010312
I have restored the occam 4.4 stock image and it upgraded to 4.4.2 with no issues.

G1MFG said:
Thanks, there is nothing wrong with your English. Unfortunately I am too much of a noob to understand what you are saying. I have had the Error 7 twice now with failed automatic updates and it's scaring me.
I followed step by step instructions to make Flash run on my N5 - which were hard, but worth it because it meant the phone would actually work on the internet, even though Dolphin has that much-hatedl dolphin button right in the way that I hit at least 200 times a day when I scroll.
Can anyone please re-write these instruction into TOTAL noob-speak, including things like 'this next step will trash all your apps, data and photos so back up you phone first by doing X, Y and Z'.
Many thanks
Click to expand...
Click to collapse
Hey I rewrote some things, when you don't use the commands: (fastboot erase data) and (fastboot erase userdata) you won't lose any data, but i recommend you to make a full backup with CWM or something like that.
I used android adb from the sdk kit.
https://developer.android.com/sdk/index.html
Start your phone with volume up + unlock button to enter the bootloader

I had actually this problem too, but then decided not to flash the update, as lots of people complaining from it being buggy. Thanks for the quick guide though!

[GUIDE]Nexus 9 back to stock guide - Unbrick - Restore factory firmware

The aim of this thread is to make an easy guide to flashing stock firmware. Owners of previous nexus devices already know all this stuff, this thread is aimed at making the process as simple as possible for new users. This will work regardless of what modifications you've done to your device. Remember to backup all your important data and do this with the knowledge that all flashing activity carries some risk.
Download
Factory image here
(for windows users) Minimal adb & fastboot
(for mac users) adb & fastboot for mac
Follow the instructions to install adb on your computer.
Prepare your tablet
Enable developer options in settings > about tablet and tapping build number 7 times
Open developer options and enable usb debugging. (If you haven't unlocked your bootloader yet, tick enable oem unlock)
Extract images
Place the downloaded factory image inside your adb folder and extract with 7zip.
A new folder will be there called something like volantis-lrx21. Open and extract "image-xxxxx-zip" to your adb folder. We are interested in these files:
bootloader-flounder-xxxxxx.img
boot.img
recovery.img
cache.img
system.img
vendor.img
Place these files directly into your adb folder.
# I recommend renaming the 'bootloader-flounder-xxxxxx.img' to just 'bootloader.img' to make it easier to type.
Now that everythings set up, we can start flashing
Plug in your device. Open the adb folder, hold shift and right click and select open command window here
(if your having driver issues try using Pdanet)
Run these commands one at a time
Code:
adb devices
adb reboot bootloader
if you haven't unlocked the bootloader yet run
Code:
fastboot oem unlock
and follow the instructions using the volume keys to scroll through the menu. This procedure will wipe all data.
Run the following commands one at a time
Code:
fastboot flash bootloader bootloader-flounder-xxxxxxx.img
[B] [I](replace 'bootloader-flounder-xxxxx.img' with full name of bootloader image[/I])[/B]
fastboot reboot-bootloader
fastboot -w
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash cache cache.img
fastboot flash system system.img
fastboot flash vendor vendor.img
(OPTIONAL) At this stage you can relock the bootloader if you want by running the command
Code:
fastboot oem lock
finally reboot the device by running
Code:
fastboot reboot
Thats it. Enjoy your tablet in factory condition

Great. Is it possible to make a batch file to run all the commands at once?

albsat said:
Great. Is it possible to make a batch file to run all the commands at once?
Click to expand...
Click to collapse
There is already a flash all batch script that comes with the firmware files but I've noticed that some people have problems with it so I decided not to include it. It should work fine most of the time.

i am long-time familiar with htc,but new to nexus. i was looking thru a couple downloaded factory image files and having noticed that "rebootRUU" is an oem command,and that "image-xxxxx-zip" contains an android info document,i am curious if anyone has tried flashing image-xxxxx-zip as a zip file,in ruu mode?

Cool, thanks for the information.

Thanks for creating this! Will come in handy. Saving this for later

This has been useful as the update from 5.0.1 to 5.0.2 kept failing on my rooted device. It was successful and educational.

scotty1223 said:
i am long-time familiar with htc,but new to nexus. i was looking thru a couple downloaded factory image files and having noticed that "rebootRUU" is an oem command,and that "image-xxxxx-zip" contains an android info document,i am curious if anyone has tried flashing image-xxxxx-zip as a zip file,in ruu mode?
Click to expand...
Click to collapse
I indeed tried this as a last chance hoping it would bypass bootloader lock protection. It didn't work since I think the factory image is not signed by HTC as RUU are . It also lead to a fastboot crash. Now sending my nexus 9 for RMA
Sent from my HTC One using XDA Free mobile app

remedya said:
This has been useful as the update from 5.0.1 to 5.0.2 kept failing on my rooted device. It was successful and educational.
Click to expand...
Click to collapse
Same here. The manual flash method worked very well. Here's hoping that Google doesn't muck 5.1

cant flash stock rom
I'm trying to downgrade my nexus 9 from DU rom 5.1.1 to stock for everything. I'm running the flash-all.sh on linux while my tablet is in bootloader mode. Tab makes and few checks and reboots automatically in bootloader mode. I reboot tablet and still has the DU rom. Any tips

nyasha1935 said:
I'm trying to downgrade my nexus 9 from DU rom 5.1.1 to stock for everything. I'm running the flash-all.sh on linux while my tablet is in bootloader mode. Tab makes and few checks and reboots automatically in bootloader mode. I reboot tablet and still has the DU rom. Any tips
Click to expand...
Click to collapse
The flash all script doesn't seem to work on linux. You shouldn't have a problem if you write the commands out manually.

nyasha1935 said:
I'm trying to downgrade my nexus 9 from DU rom 5.1.1 to stock for everything. I'm running the flash-all.sh on linux while my tablet is in bootloader mode. Tab makes and few checks and reboots automatically in bootloader mode. I reboot tablet and still has the DU rom. Any tips
Click to expand...
Click to collapse
Art Vanderlay said:
The flash all script doesn't seem to work on linux. You shouldn't have a problem if you write the commands out manually.
Click to expand...
Click to collapse
As indicated, the flash all script doesn't work very well on any system. Flash each .img separately via fastboot.

cam30era said:
As indicated, the flash all script doesn't work very well on any system. Flash each .img separately via fastboot.
Click to expand...
Click to collapse
Problem is that the tgz is too big for the device's buffer, so it craps out before it actually writes the images. Its been this way for a while over several different nexus devices. Kind of like nobody at google ever even bothered to test the process.

doitright said:
Problem is that the tgz is too big for the device's buffer, so it craps out before it actually writes the images. Its been this way for a while over several different nexus devices. Kind of like nobody at google ever even bothered to test the process.
Click to expand...
Click to collapse
I agree.

I also used Linux but I executed the commands individually rather than using the script. It worked.

remedya said:
I also used Linux but I executed the commands individually rather than using the script. It worked.
Click to expand...
Click to collapse
I cant flash system.img I get error
sending 'system' (1108544 KB)...
FAILED (remote: data length is too large)
finished. total time: 0.105s

nyasha1935 said:
I cant flash system.img I get error
sending 'system' (1108544 KB)...
FAILED (remote: data length is too large)
finished. total time: 0.105s
Click to expand...
Click to collapse
Update your Android SDK.

These instructions also worked with 5.1.1

im trying to install back to facctory i erased my system and recovery and data and now when i try to flash bootloader i get error cannot open bootloader someone please im stuck in bootloader mode

maxtcee said:
im trying to install back to facctory i erased my system and recovery and data and now when i try to flash bootloader i get error cannot open bootloader someone please im stuck in bootloader mode
Click to expand...
Click to collapse
Are you writing the full name and file path for the bootloader img?

Using System Image to Update your Nexus 6 (no data loss)

Tired of waiting for the OTA? Can't use it because you're rooted? Don't want to wipe your entire phone? No problem! Here's how you can upgrade with Google's Nexus factory images without wiping your apps or sdcard.
NOTE: You must have your bootloader unlocked. If you've never unlocked your bootloader, I don't think there's any way to do this without wiping your data.
STEP 1: Install fastboot
Fastboot is Google's utility for flashing factory images. You can also use it to flash custom recoveries like TWRP and CWM. The standard way to get is is through Google's Android SDK, but that's a bit heavy-duty, so you can also download just the most important tools (fastboot and adb) separately, packaged by users. Here are some links:
Official Google Android SDK (cross-platform): http://developer.android.com/sdk/index.html#Other[1]
Unofficial for Windows: http://developer.android.com/sdk/index.html#Other[2]
Unofficial Mac/Linux: http://code.google.com/p/adb-fastboot-install/[3]
Windows users might also need to install drivers: http://developer.android.com/sdk/win-usb.html[4] (can any Windows users confirm whether it's necessary?)
STEP 2: Prepare factory image
Download the latest Nexus 6 factory image at https://developers.google.com/android/nexus/images#shamu[5]
Unzip it and open the resulting folder
Unzip the "image-shamu-*.zip" file in there
You should now be looking at something like this: http://i.imgur.com/mzrfwrP.png [6]
STEP 3: Flash! (Ah-ahhhhh! [7] )
Connect your phone to your computer via USB, and enter the bootloader. You can enter the bootloader by holding down the power and volume-down buttons to boot. Once you see the bootloader, you can release the buttons.
Open a terminal/command prompt. The syntax might be slightly different on Windows than on Mac or Linux, but basically the same. Anything you see in <> you need to replace, e.g. with the actual path to your factory image folder. The rest you should be able to copy and paste. (Tip: you can easily enter a folder path into your terminal/command prompt by simply dragging the folder onto your terminal window. This works on Mac, Windows, and the vast majority of Linux GUIs.) Enter these commands:
cd </path/to/shamu-lmy47d>
fastboot flash bootloader bootloader-shamu-moto-apq8084-71.08.img
Reboot the bootloader.
fastboot flash radio radio-shamu-d4.0-9625-02.95.img
cd <image-shamu-lmy47d>
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash system system.img
If you DO NOT use a custom recovery (like TWRP or CWM), then also: fastboot flash recovery recovery.img
Don't worry if you see messages like "target reported max download size of 1073741824 bytes". Just wait and let it finish.
Reboot your phone and enjoy. It's normal for the first boot to take a while. Going from Kitkat to Lollipop took about 20 minutes. Going from 5.0 to 5.0.1 took 5-10, I think. YMMV.
A WORD OF WARNING: If you're moving between ROMs, you generally should do a complete reset, including wiping data. Many users have reported problems going from KitKat to Lollipop without wiping data and recommend a factory reset anyway. If you're okay with wiping everything, you can simply use Google's included flash-all scripts, or flash the userdata.img file yourself. Personally, I'm not going to bother wiping adta for an incremental update like 5.0.1->5.1. As always, be sure to back up your data!
Shamelessly stolen from: http://www.reddit.com/r/Nexus5/comments/2phqy7/howto_upgrade_android_using_nexus_factory_images/

Shouldn't you also fastboot reboot bootloader after radio flash?

This is the scenic route.

I tried to update using wugz, without unlocking the bootloader. failed. Oh well, I'll wait to receive ota
Unless this method doesnt require unlocking?

If you have an OTA zip file, this is different than using a System Img?
I do not think you need to lose data or unlock your bootloader?
Found a link for the OTA zip file.
If I remember right you can copy the zip to you phone with a USB cable.
Go into the bootloader, Volume Down and Power.
Select the zip.
I did not think you needed a terminal and all the commands if you had the OTA zip on your phones SD card.
Am I wrong does something like this not work?
or
I can just wait.....

This worked great.
I was unbranded with VZ sim, unlocked, rooted with TWRP recovery. Didn't want to lose all that nor my apps or data. This method upgrades to 5.1 without any loss.
When I was done with the flashing, I rebooted to TWRP recovery (not system) in order to wipe dalvik and cache (just to be certain). I wiped and then rebooted to system. TWRP noticed I didn't have SuperSU installed so it installed it for me. Meaning, once I got my system rebooted, I still had root too.
All in all, this process worked great for me. Thanks.

I run the first two commands
fastboot flash bootloader bootloader-shamu-moto-apq8084-71.08.img
fastboot reboot-bootloader
they worked, then i moved to the radio
fastboot flash radio radio-shamu-d4.0-9625-02.95.img
but it failed.
Any idea?
---------- Post added 14th March 2015 at 12:17 AM ---------- Previous post was 13th March 2015 at 11:53 PM ----------
Nikos2k said:
I run the first two commands
fastboot flash bootloader bootloader-shamu-moto-apq8084-71.08.img
fastboot reboot-bootloader
they worked, then i moved to the radio
fastboot flash radio radio-shamu-d4.0-9625-02.95.img
but it failed.
Any idea?
Click to expand...
Click to collapse
This is the message after the radio flash command:
fastboot flash radio radio-shamu-d4.0-9625-02.95.img
target reported max download size of 536870912 bytes
sending 'radio' (85422 KB)...
OKAY [ 2.697s]
writing 'radio'...
(bootloader) flashing modem ...
(bootloader) flashing modem ...**☺
FAILED (unknown status code)
finished. total time: 3.721s​
Why the failed message?

I'm decrypted. Will this re encrypt my Nexus or do I have to flash a non enforce img?

Thank you, this really helped.
Since my bootloader was locked i had to unlock it as well.
Had a bit of a scare with the whole erasing screen staying on for too long.
Went back and redid the process, and went downstairs for 5 minutes, came back and phone was booted.
Anyway, thank you again

Will this work on an encrypted phone?

mikeadamz said:
Tired of waiting for the OTA? Can't use it because you're rooted? Don't want to wipe your entire phone? No problem! Here's how you can upgrade with Google's Nexus factory images without wiping your apps or sdcard.
<<snip>>
Click to expand...
Click to collapse
I don't suggest that anyone read and follow someone else's instructions when doing something like this. Not because the instructions are wrong or anything, but because blindly following instructions doesn't involve *understanding* anything.
So rather than reading and following instructions, read and UNDERSTAND the process of installing factory images as delivered with the factory images (flash-all.sh). If you UNDERSTAND the process and what everything does, then (a) you *already know* what needs to be adjusted to do what you want, and (b) if something starts going wrong in the middle of it, you will understand why, and what to do to correct it.

mikeadamz said:
cd </path/to/shamu-lmy47d>
fastboot flash bootloader bootloader-shamu-moto-apq8084-71.08.img
Click to expand...
Click to collapse
First, thanks for the write up, I do greatly appreciate it. Second, thanks for the tip on dragging file locations into the command prompt. Very helpful.
Now my question. When I did this I tried using exactly the steps above and had no luck whatsoever. I'd cd to the location of the img files as noted and it would say fastboot is unrecognized as an internal or external command. I moved the file into the fastboot location and got the same issue. I finally ran the fastboot from the adb folder location and just referenced the full file path for each img file (using the drag and drop method) and everything went swimmingly. My question is just about using fastboot. Should it have worked when I used cd to go to the img file location? Is there something I need to do to make it work as you described?
Thanks!
Nick

Nick D said:
First, thanks for the write up, I do greatly appreciate it. Second, thanks for the tip on dragging file locations into the command prompt. Very helpful.
Now my question. When I did this I tried using exactly the steps above and had no luck whatsoever. I'd cd to the location of the img files as noted and it would say fastboot is unrecognized as an internal or external command. I moved the file into the fastboot location and got the same issue. I finally ran the fastboot from the adb folder location and just referenced the full file path for each img file (using the drag and drop method) and everything went swimmingly. My question is just about using fastboot. Should it have worked when I used cd to go to the img file location? Is there something I need to do to make it work as you described?
Thanks!
Nick
Click to expand...
Click to collapse
Install this:
http://forum.xda-developers.com/showthread.php?t=2588979
Now ADB and fastboot are installed system wide. Put your files anywhere, I use the desktop. Hold shift and right click on wherever your files are and select "open command prompt here" and flash away. Simplified, no more dragging and dropping.

Will try with the new update (5.1.1 (LMY48M)) to ensure it works. Thanks!

[/COLOR]
handyarrow said:
Will this work on an encrypted phone?
Click to expand...
Click to collapse
Have been flashing this zip in twrp after the fastboot stage without an issue for the last few updates - http://forum.xda-developers.com/nexus-6/development/mod-disable-force-encryption-rom-kernel-t3000788

Flashed LMY48M with fastboot method and it works great.
My phone is encrypted.

Stock ROM for YB1-X90F

Where I can I download the stock ROM for this model of Yoga Book? I hosed up my machine trying to root. I can boot into recovery mode, hopefully I can flash a new ROM to recover.
Thanks,,,

This could help ...
Edit: 2017/02/21: Link has expired
You can try this one: http://s55.filefactory.com/get/f/osm8z9hwyrz/1844e07b49cb41c8/YB1-X90L_USR_S000155_1609272258_WW06_BP_ROW-flashfiles.zip
It is for YB1-X90L, however, I had success with my X90F. Download just lasts 10 hours if you don' t want to subscribe

yoga-user said:
you can try this one: (http) s55.filefactory.com/get/f/osm8z9hwyrz/1844e07b49cb41c8/YB1-X90L_USR_S000155_1609272258_WW06_BP_ROW-flashfiles.zip
It is for YB1-X90L, however, I had success with my X90F. Download just lasts 10 hours if you don' t want to subscribe
Click to expand...
Click to collapse
Be aware that you'll lose use of the touchpad/halo kb if you flash this stock. Can't find any way of resolving this problem.

No - I' ve full access to all features!
Halo keybord has all functions and can be used without any restrictions. There' s nothing in stuck Only rooting with supersu isn' t possible and the machine is now identified as YB1-X90L and has some additional functions like symbol in toolbar for missing smartcard etc.
From stock-rom I flashed boot.img, bootloader, factory.img, recovery.img and system.img and first of all there where two updates ...

yoga-user said:
Halo keybord has all functions and can be used without any restrictions. There' s nothing in stuck Only rooting with supersu isn' t possible and the machine is now identified as YB1-X90L and has some additional functions like symbol in toolbar for missing smartcard etc.
From stock-rom I flashed boot.img, bootloader, factory.img, recovery.img and system.img and first of all there where two updates ...
Click to expand...
Click to collapse
I reflashed the stock ROM (using Intel PhoneFlash Tool), then allowed the two updates. Still no sketchpad/halo function at all. Do I understand from your last paragraph that you then flashed those imgs after the two updates?

zamzenos said:
I reflashed the stock ROM (using Intel PhoneFlash Tool), then allowed the two updates. Still no sketchpad/halo function at all. Do I understand from your last paragraph that you then flashed those imgs after the two updates?
Click to expand...
Click to collapse
Hi,
I used regular adb / fastboot. As my Yoga was totally stucked I flashed all the images and then installed the updates. Now it' s build LenovoYB1-X90L_S000241_161209, Kernel-Version 3.14.55-x86_64-ga6a34be.
Last of all I locked Bootloader and restored all my Apps.
Good luck!

yoga-user said:
Hi,
I used regular adb / fastboot. As my Yoga was totally stucked I flashed all the images and then installed the updates. Now it' s build LenovoYB1-X90L_S000241_161209, Kernel-Version 3.14.55-x86_64-ga6a34be.
Last of all I locked Bootloader and restored all my Apps.
Good luck!
Click to expand...
Click to collapse
My only options to flash any of the img files is through adb sideload or placing them on the sdcard and installing via recovery. Every attempt fails with an E:footer is wrong; E:signature verification failed message. I can't find any way around the errors.

booneb50 said:
My only options to flash any of the img files is through adb sideload or placing them on the sdcard and installing via recovery. Every attempt fails with an E:footer is wrong; E:signature verification failed message. I can't find any way around the errors.
Click to expand...
Click to collapse
Have you tried the Intel PhoneFlash Tool? So far I've managed to flash the Stock twice, but with the pad/halo problem I described above.

booneb50 said:
My only options to flash any of the img files is through adb sideload or placing them on the sdcard and installing via recovery. Every attempt fails with an E:footer is wrong; E:signature verification failed message. I can't find any way around the errors.
Click to expand...
Click to collapse
Hi,
with this procedure I could restore my bricked device:
- like described at this thread: https://forum.xda-developers.com/showthread.php?t=2588979, I downloaded and installed universal adb / fastboot and fixed fastboot drivers
- then unzipped YB1-X90L_USR_S000155_1609272258_WW06_BP_ROW-flashfiles.zip and copied boot.img, bootloader, factory.img, recovery.img and system.img to my adb-folder (%UserProfile%\adb)
Caution: The next steps will wipe all your personal data! It' s a complete reset to factory settings!!!
- rebooted my device with "Volume up" and "Power" to bootloader (fastboot mode) and then connected it via usb
- opened cmd and navigated to my adb-folder
- tested fastboot mode with command "fastboot devices" with success and
- then flashed all the images (as referred to above) with fastboot commands: fastboot flash boot boot.img, fastboot flash bootloader bootloader and so on.
- after it I rebooted my device to system - be patient, don't power off, it can last very long time before first boot .
- as I had no success with supersu, at this point I decided for myself to relock bootloader - this was the second reset to factory settings
-then I re-installed all my apps manually and restored settings, contacts and calendar from my google-account
I hope, this helps

yoga-user said:
Hi,
with this procedure I could restore my bricked device:
- like described at this thread: https://forum.xda-developers.com/showthread.php?t=2588979, I downloaded and installed universal adb / fastboot and fixed fastboot drivers
- then unzipped YB1-X90L_USR_S000155_1609272258_WW06_BP_ROW-flashfiles.zip and copied boot.img, bootloader, factory.img, recovery.img and system.img to my adb-folder (%UserProfile%\adb)
Caution: The next steps will wipe all your personal data! It' s a complete reset to factory settings!!!
- rebooted my device with "Volume up" and "Power" to bootloader (fastboot mode) and then connected it via usb
- opened cmd and navigated to my adb-folder
- tested fastboot mode with command "fastboot devices" with success and
- then flashed all the images (as referred to above) with fastboot commands: fastboot flash boot boot.img, fastboot flash bootloader bootloader and so on.
- after it I rebooted my device to system - be patient, don't power off, it can last very long time before first boot .
- as I had no success with supersu, at this point I decided for myself to relock bootloader - this was the second reset to factory settings
-then I re-installed all my apps manually and restored settings, contacts and calendar from my google-account
I hope, this helps
Click to expand...
Click to collapse
Hi, I also meet the same problem and need this X90L_USR_S000155_1609272258_WW06_BP_ROW-flashfiles.zip file for recovery, but it seems the link which you shared before expired, can you help to share with me your copy or create another link? Thanks a lot!

Even_xf said:
Hi, I also meet the same problem and need this X90L_USR_S000155_1609272258_WW06_BP_ROW-flashfiles.zip file for recovery, but it seems the link which you shared before expired, can you help to share with me your copy or create another link? Thanks a lot!
Click to expand...
Click to collapse
... you have PM

can i get the link as well?

it would be very nice if someone can help with a download link for yb1-x90l complete rom or even only recovery.img

can you please share the link again?

All the firmware for both models are available at: http://www.easy-firmware.com/index.php. You have to take a subscription to be able to download the files. Files are exclusive downloads. Subscription at $15. Latest versions are the november firmware.
Verstuurd vanaf mijn Lenovo YB1-X90L met Tapatalk

vogemic said:
All the firmware for both models are available at: http://www.easy-firmware.com/index.php. You have to take a subscription to be able to download the files. Files are exclusive downloads. Subscription at $15. Latest versions are the november firmware.
Verstuurd vanaf mijn Lenovo YB1-X90L met Tapatalk
Click to expand...
Click to collapse
I find this very strange this site charges to download the firmware that cannot be found from any other reputable site that I have searched on. It may well be legit but I will steer clear anyway.

keybord
zamzenos said:
Be aware that you'll lose use of the touchpad/halo kb if you flash this stock. Can't find any way of resolving this problem.
Click to expand...
Click to collapse
you need to input country code to enable keyboard. There are several steps as below :
a) Open ‘’contacts’’ app, create a new local contact ” test”
b) Click search button at contact
c) Input ####6020# code into search bar
d) Browser the country code list, then chose country code you want to use, such as US
e) Then DUT will reboot

vimalbhimani said:
you need to input country code to enable keyboard. There are several steps as below :
a) Open ‘’contacts’’ app, create a new local contact ” test”
b) Click search button at contact
c) Input ####6020# code into search bar
d) Browser the country code list, then chose country code you want to use, such as US
e) Then DUT will reboot
Click to expand...
Click to collapse
Long time coming. Thanks for taking the trouble to detail the method. However, in order to update to lastest firmware I was obliged to input a cc. I assumed then that I had got the Halo etc working simply by updating the firmware(!). Even so, good to know why I didn't have Halo. This info is sure to be of benefit to others. Thank you.

yoga-user said:
... you have PM
Click to expand...
Click to collapse
Can you please send me the link as well?

wait for new link download
need stock recovery backup
I will try install windows on android version
I think same Mipad2 (android version can install Windows ) install windows
http://en.miui.com/thread-248564-1-1.html