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,

[Q] How to manually apply Android 4.4 update frm official factory image on to nexus 4

Hello,
I have recently bought the Nexus 4. Its running on official stock 4.3 JB, bootloader locked i.e. everything is stocked and never rooted.
As 4.4 update is not available OTA as of now(not in the coming few days), so how can i update my nexus 4 to 4.4???
I have downloaded the official factory image from google dev website. When i try to update it through adb, its not showing my device in the list when i issue adb devices command....please help me...!!
Your replies will be much appreciated if you help me solving my issue or if you can suggest me any other alternative method....!!

vinay28761 said:
Hello,
I have recently bought the Nexus 4. Its running on official stock 4.3 JB, bootloader locked i.e. everything is stocked and never rooted.
As 4.4 update is not available OTA as of now(not in the coming few days), so how can i update my nexus 4 to 4.4???
I have downloaded the official factory image from google dev website. When i try to update it through adb, its not showing my device in the list when i issue adb devices command....please help me...!!
Your replies will be much appreciated if you help me solving my issue or if you can suggest me any other alternative method....!!
Click to expand...
Click to collapse
Make sure you use the Google SDK drivers and not the default drivers Windows installs....that was my issue may work for you,

nnorton44 said:
Make sure you use the Google SDK drivers and not the default drivers Windows installs....that was my issue may work for you,
Click to expand...
Click to collapse
As mentioned in the screenshot, my nexus 4 is connected with USB debugging ON. As far as drivers are concerned, phone is geting detected in device manager, with USB debugging ON and OFF, both the ways.
After that when i open command prompt window, no adb command seems to work. When i run "adb devices" command(without using quotes), it doesn't show me my phone. I am using the google SDK drivers only, downloaded from google dev website. Kindly suggest.

But were those the drivers that windows installed for you when you plug the phone in, or did you manually choose the appropriate drivers?
It has been a while since I've been on Windows, so I'm not familar with the process. But what he is saying is important.

N1029676 said:
But were those the drivers that windows installed for you when you plug the phone in, or did you manually choose the appropriate drivers?
It has been a while since I've been on Windows, so I'm not familar with the process. But what he is saying is important.
Click to expand...
Click to collapse
Well i did some searching on various xda posts...found this cool and nice tutorial for nexus 4. Followed the exact procedure step by step.
Running Android KITKAT 4.4 ...Big Kudos to the senior moderator efrant for his excellent tutorial http://forum.xda-developers.com/showthread.php?t=2010312
Do check it out. I manually installed the drivers. But sadly adb is still not working.

Steps required to install 4.4 factory steps
@vinay28761
Here You are :
I would fully recommend unlocking your bootloader for this purpose, unlocking has many advantages and one disadvantage, that your waranty will be void, but if you do these steps correctly, you should be fine with it
1) Download the SDK from here : http://developer.android.com/sdk/index.html
2) Extract the folder to an appropriate location . I prefer C:/adt-bundle-windows-x86_64 , you will see sdk folder> platform-tools. This is the main folder, here u will get your fastboot and adb
3) Now when you first download the facctory image, it will be in .tgz file, Use 7-zip software (Google it) and extract it to the same folder where you have downloaded your factory image.
4) After extracting you will get .tar file, extract it again using 7 zip . All files will be extracted to a folder called occam-krt160o and you will get img files like bootloader-mako-makoz20i and radio img's . Now Copy these files namely : bootloader-mako-makoz20i , radio-mako-m9615a-cefwmazm-2.0.1700.84 and image-occam-krt16o.zip
5) Now copy the img files that i mentioned from the occam-krt160o folder and paste into platform-tools folder present in your adt bundle
For the connection part :
1) On the nexus 4 go to settings > about phone and tap on build number 2-3 times , it will say now you are a developer, now you should see a developer option in your setting menu, go into developer options and enable USB debugging.
2) Now go to storage option in the nexus 4 and tap on sought of options button present there it will say connection option or something like that when u tap it will ask MTP or PTP (basically two connection modes for your N4 when connecting to the PC), uncheck MTP
3) Now On your PC, go to device manager on you PC (Google it) and look for Nexus 4 , right click it and click uninstall and if a option is there to delete the drivers put a check on it or if there is no option just uninstall the phone.
4) Connect your phone via a USB cable it will say installing driver (It should install ADB by default).
For Unlocking bootloader connecting Fastboot and installing images.
* You will lose all data on the internal memory that is films,music, apps (Back it up )
1) Switch off your phone.
2)Hold the pwerbutton and volume down to enter into fastboot ( Phone should be connected to PC)
3) You will see a start button on top and droid icon like a repair tool ) . You will also see bootloader lock status
4) Now on your PC , browse to your platform-tools folder . hold shift-rightclick and open a command prompt.
5) Now type fastboot oem unlock on your command prompt . Now your bootloader is unlocked and all your data is wiped.
6) Now reboot your bootloader by : pressing volume down/up and press the power-button to select (when u browse by volume up/down it will show resrat bootloader or reboot bootloader)
7) After N4 comes back to your bootloader, Type in your command prompt :
fastboot flash bootloader bootloader-mako-makoz20i
fastboot reboot-bootloader
fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1700.84
fastboot reboot-bootloader
fastboot -w update image-occam-krt16o
fastboot reboot-bootloader
Note: I recommend restarting the bootloader manually after flashing each image.
Now you should have a android 4,4 running on your nexus phone.
To install recovery on the N4 , Go to ClockWorkMod homepage ( Google it ) and choose N4 touch recovery download it and rename it as recovery and paste in to into platform-tools folder.
To flash type on your command prompt fastboot flash recovery recovery,img
You should have a CWM recovery now.

Abhiheart said:
@vinay28761
Here You are :
I would fully recommend unlocking your bootloader for this purpose, unlocking has many advantages and one disadvantage, that your waranty will be void, but if you do these steps correctly, you should be fine with it
1) Download the SDK from here : http://developer.android.com/sdk/index.html
2) Extract the folder to an appropriate location . I prefer C:/adt-bundle-windows-x86_64 , you will see sdk folder> platform-tools. This is the main folder, here u will get your fastboot and adb
3) Now when you first download the facctory image, it will be in .tgz file, Use 7-zip software (Google it) and extract it to the same folder where you have downloaded your factory image.
4) After extracting you will get .tar file, extract it again using 7 zip . All files will be extracted to a folder called occam-krt160o and you will get img files like bootloader-mako-makoz20i and radio img's . Now Copy these files namely : bootloader-mako-makoz20i , radio-mako-m9615a-cefwmazm-2.0.1700.84 and image-occam-krt16o.zip
5) Now copy the img files that i mentioned from the occam-krt160o folder and paste into platform-tools folder present in your adt bundle
For the connection part :
1) On the nexus 4 go to settings > about phone and tap on build number 2-3 times , it will say now you are a developer, now you should see a developer option in your setting menu, go into developer options and enable USB debugging.
2) Now go to storage option in the nexus 4 and tap on sought of options button present there it will say connection option or something like that when u tap it will ask MTP or PTP (basically two connection modes for your N4 when connecting to the PC), uncheck MTP
3) Now On your PC, go to device manager on you PC (Google it) and look for Nexus 4 , right click it and click uninstall and if a option is there to delete the drivers put a check on it or if there is no option just uninstall the phone.
4) Connect your phone via a USB cable it will say installing driver (It should install ADB by default).
For Unlocking bootloader connecting Fastboot and installing images.
* You will lose all data on the internal memory that is films,music, apps (Back it up )
1) Switch off your phone.
2)Hold the pwerbutton and volume down to enter into fastboot ( Phone should be connected to PC)
3) You will see a start button on top and droid icon like a repair tool ) . You will also see bootloader lock status
4) Now on your PC , browse to your platform-tools folder . hold shift-rightclick and open a command prompt.
5) Now type fastboot oem unlock on your command prompt . Now your bootloader is unlocked and all your data is wiped.
6) Now reboot your bootloader by : pressing volume down/up and press the power-button to select (when u browse by volume up/down it will show resrat bootloader or reboot bootloader)
7) After N4 comes back to your bootloader, Type in your command prompt :
fastboot flash bootloader bootloader-mako-makoz20i
fastboot reboot-bootloader
fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1700.84
fastboot reboot-bootloader
fastboot -w update image-occam-krt16o
fastboot reboot-bootloader
Note: I recommend restarting the bootloader manually after flashing each image.
Now you should have a android 4,4 running on your nexus phone.
To install recovery on the N4 , Go to ClockWorkMod homepage ( Google it ) and choose N4 touch recovery download it and rename it as recovery and paste in to into platform-tools folder.
To flash type on your command prompt fastboot flash recovery recovery,img
You should have a CWM recovery now.
Click to expand...
Click to collapse
Thanks for your steps.....I already followed the tutorial http://forum.xda-developers.com/show....php?t=2010312 and running Android KitKat 4.4 now

vinay28761 said:
Thanks for your steps.....I already followed the tutorial http://forum.xda-developers.com/show....php?t=2010312 and running Android KitKat 4.4 now
Click to expand...
Click to collapse
i am golad you are now running KitKat but to be honest searching for the instructions that you found should of been the first thing you did prior to starting a thread. There are a few tutorials out there. Hopefully your next venture into android you will take a moment to search...
Glad you are now on 4.4 enjoy my friend

Hi can you not just use the flash all.bat file contained in the factory image files instead of flashing the images separately?
Sent from my Nexus 4 using Tapatalk

(Solved) Error while flashing 4.4 - failed to allocate memory
Tried installing KitKat on Nexus4. The package was downladed from google's page, the checksum verification was also fine. But when I tried to flash the the new firmware got the below error.
E:\kitkat\occam-krt16o>fastboot -w update image-occam-krt16o.zip
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
failed to allocate 717312552 bytes
error: update package missing system.img
If any of you have seen this before, let me know how to overcome this.
Thanks in advance!
EDIT: The issue was with the PC - It had low memory and thus failed to allocate memory. My initial thought was that it failed to allocate memory on the phone!

Stock Nexus 7 (2012) soft bricked

Hello all this is my first post here, please be nice
I have absolutely no knowledge of computing/ IT, but after tearing my hair for the past two days (and a lot of googling) I have come here hoping for a solution
I have a stock nexus (see I have learnt new terms) which is now soft bricked and stuck on the X screen
Been looking for solutions including nexus root kit but none have really helped
eg one solution says step 1: install latest android SDK (and in the process of installing I have to ensure usb debugging is turned on, too late already soft bricked)
I am assuming that I have failed because
I have not rooted the device
I have not enabled usb debugging
I have not enabled changes previously eg unlocking
I am however able to enter bootloader mode
I have cleared cache partition and also tried to factory reset but to no avail
Could some one please please help me as it is out of warranty

docians said:
Hello all this is my first post here, please be nice
I have absolutely no knowledge of computing/ IT, but after tearing my hair for the past two days (and a lot of googling) I have come here hoping for a solution
I have a stock nexus (see I have learnt new terms) which is now soft bricked and stuck on the X screen
Been looking for solutions including nexus root kit but none have really helped
eg one solution says step 1: install latest android SDK (and in the process of installing I have to ensure usb debugging is turned on, too late already soft bricked)
I am assuming that I have failed because
I have not rooted the device
I have not enabled usb debugging
I have not enabled changes previously eg unlocking
I am however able to enter bootloader mode
I have cleared cache partition and also tried to factory reset but to no avail
Could some one please please help me as it is out of warranty
Click to expand...
Click to collapse
flash factory image via fastboot, since you can access bootloader and already install adb debugging.. follow step 6 (6.you can verify...) onward from this post http://forum.xda-developers.com/showthread.php?p=32075129
Sent from my Nexus 7

usb debugging
dexviajiboy said:
flash factory image via fastboot, since you can access bootloader and already install adb debugging.. follow step 6 (6.you can verify...) onward from this post http://forum.xda-developers.com/showthread.php?p=32075129
Sent from my Nexus 7
Click to expand...
Click to collapse
Unfortunately I do not have usb debugging enabled
And my tablet is soft bricked
Is there a way around this?
Please any help is appreciated
thanks

Try this from youtube. I have also softbrick my nexus when ota to kitkat. Use this methods and it works. Also before flash the factory image, unlock your bootloader first. I think this method did not required to enable usb debuging.
http://m.youtube.com/watch?v=-E-EF0QC0Gc
I hope this will help
Sent from my Nexus 7 using xda premium

You don't need usb debugging enabled to flash images via fastboot -- you just need to be able to get into the bootloader screen.

unlock bootloader
deny_kei said:
Try this from youtube. I have also softbrick my nexus when ota to kitkat. Use this methods and it works. Also before flash the factory image, unlock your bootloader first. I think this method did not required to enable usb debuging.
I hope this will help
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Thanks for the video
I have followed everything until it (the video) tells me that the process will only work if I unlock my bootloader
Now I can access my bootloader but it states Lock State- Locked
My difficulty is how do I unlock my bootloader as my nexus is stuck at boot loop
I have tried the unlock function on Rootkit, but it says I have to enable usb debugging
To summarise my understanding:
My nexus will get out of bootloop if I flash the ROM
To flash the ROM I have to unlock the bootloader (as per the video)
To unlock the bootloader I have to enable usb debugging (as per nexus root kit)
To enable usb debugging I have to get out of bootloop
To get out of bootloop I have to flash the ROM............
Any simple way of unlocking the bootloader on a soft bricked nexus?
Any help appreciated thanks

like jfmcbrayer said.. if you can access bootloader, you can flash via fastboot either you enabled or not usb debugging, the important thing fasboot can verify your device before start flashing..
Sent from my Nexus 7

bootloader locked
dexviajiboy said:
like jfmcbrayer said.. if you can access bootloader, you can flash via fastboot either you enabled or not usb debugging, the important thing fasboot can verify your device before start flashing..
Sent from my Nexus 7
Click to expand...
Click to collapse
Absolutely agree
However when I try to follow your instructions
> fastboot devices
# the following output should be returned
<device serial number> fastboot
I do not get a device serial number
I suspect it is because the bootloader is locked, the device will not be recognised
Happy to be proven wrong because I need a means to get my nexus working

docians said:
Absolutely agree
However when I try to follow your instructions
> fastboot devices
# the following output should be returned
<device serial number> fastboot
I do not get a device serial number
I suspect it is because the bootloader is locked, the device will not be recognised
Happy to be proven wrong because I need a means to get my nexus working
Click to expand...
Click to collapse
seen like you got problem with adb driver on you pc..
Sent from my Nexus 7

adb driver
dexviajiboy said:
seen like you got problem with adb driver on you pc..
Sent from my Nexus 7
Click to expand...
Click to collapse
Indeed! Perhaps because the first step in installing an adb driver in my pc is this:
1. Enable usb debugging on your device (found under Settings > Developer Options)
As I have been saying from the start
My nexus is stuck in boot loop
I do not have usb debugging enabled
Is there anyone who can help me with unlocking my bootloader (on my soft bricked stock nexus) so I can flash rom
Thanks in advance

docians said:
Indeed! Perhaps because the first step in installing an adb driver in my pc is this:
1. Enable usb debugging on your device (found under Settings > Developer Options)
As I have been saying from the start
My nexus is stuck in boot loop
I do not have usb debugging enabled
Is there anyone who can help me with unlocking my bootloader (on my soft bricked stock nexus) so I can flash rom
Thanks in advance
Click to expand...
Click to collapse
goodluck ?
Sent from my Nexus 7

bricked
dexviajiboy said:
goodluck ?
Sent from my Nexus 7
Click to expand...
Click to collapse
thanks bud
I will need all the luck in the world now that I have to deal with Asus/ google now that the tablet is out of warranty

docians said:
thanks bud
I will need all the luck in the world now that I have to deal with Asus/ google now that the tablet is out of warranty
Click to expand...
Click to collapse
dont you try flash factory with guide from this thread http://forum.xda-developers.com/showthread.php?t=1907796
pm me with part you stuck.. I'll try assist you

soft brick
dexviajiboy said:
dont you try flash factory with guide from this thread http://forum.xda-developers.com/showthread.php?t=1907796
pm me with part you stuck.. I'll try assist you
Click to expand...
Click to collapse
just to be absolutely sure were on the same page I've copied all the instructions from your link
[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
1.Download and install 7-Zip - http://www.7-zip.org/download.html
2.Download the Nexus 7 factory image - https://developers.google.com/androi.../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)
3.Download and install the Java SE JDK - http://www.oracle.com/technetwork/ja...ads/index.html
4.Download and install the Android SDK - http://dl.google.com/android/installer_r21-windows.exe
5.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
6.Run the SDK Manager
7.Under Tools, check the box labeled "Android SDK Platform-tools" - this provides adb and fastboot
8.Under Extras, check the box labeled "Google USB Driver"
9.Press the "Install # packages..." button and follow the on-screen instructions.
10.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=bhA5C...yer_detailpage..
1.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!"
2.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
3.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
4.Use adb to boot the device to the bootloader:
Code:
> adb reboot-bootloader
5.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
6.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
7.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.
1.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.
2.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.
3.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
1.Put the device into fastboot mode by running the following adb command:
Code:
> adb reboot-bootloader
2.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
3.Follow the directions on the device, using the volume and power buttons to select "Yes". NOTE: this will wipe all personal data.
4.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.
5.If you are sending the device in for warranty work, you may want to re-lock the bootloader
Code:
> fastboot oem lock
6.Finally, reboot the device
Code:
> fastboot reboot
Click to expand...
Click to collapse
Following the thread this is precisely where I get stuck
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=bhA5C...yer_detailpage..
1.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!"
Will pm you with the same as I need your help in Driver Installation

docians said:
Following the thread this is precisely where I get stuck
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=bhA5C...yer_detailpage..
1.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!"
Click to expand...
Click to collapse
You're welcome, mate....
Installing drivers is not difficult, you must read the post by comminus carefully.
I tought it is too a boring part to film it....
@docians take your time to read step by step mate, that guide can help you to unbrick.
Guys, just be aware, that the drivers will have to be instaled two times: once for normal boot mode in OS, another time in fastboot mode.
What might confuse you: the ADB drivers get installed within the SDK and not as usual with downloaded drivers from the website of the manufacturer.

Did this end up being solved?
In the same situation where my Nexus 7 (2012) 4.4.4 is soft bricked and stuck in a bootloop.
Not sure how to go about installing the drivers. Just lost. :silly:

deanomalino said:
Did this end up being solved?
In the same situation where my Nexus 7 (2012) 4.4.4 is soft bricked and stuck in a bootloop.
Not sure how to go about installing the drivers. Just lost. :silly:
Click to expand...
Click to collapse
Yes, solved
You will find them in google, search for "google USB drivers for Windows"
Download the zip, unzip it and run the install/setup.exe
After that, boot your N7 into the bootloader mode and connect your tab with the USB cable and wait for 1 minute until it gets installed.
After that you will can execute all fastboot commands. Then just follow the guide by comminus how to flash factory image with fastboot.
tetakpatalked from N7100

tetakpatak said:
Yes, solved
You will find them in google, search for "google USB drivers for Windows"
Download the zip, unzip it and run the install/setup.exe
After that, boot your N7 into the bootloader mode and connect your tab with the USB cable and wait for 1 minute until it gets installed.
After that you will can execute all fastboot commands. Then just follow the guide by comminus how to flash factory image with fastboot.
tetakpatalked from N7100
Click to expand...
Click to collapse
Awesome, thanks.
Have run into another problem now.
Got to the part "fastboot flash bootloader bootloader-grouper-4.23.img"
And I get a message in cmd saying "FAILED <remote: <Invalid State>>"
Then on the tablet it says "Signiture Mismatch".
I'm using the 4.4.4 (KTU84P) from the Factory Images website if that's any help....

deanomalino said:
Awesome, thanks.
Have run into another problem now.
Got to the part "fastboot flash bootloader bootloader-grouper-4.23.img"
And I get a message in cmd saying "FAILED "
Then on the tablet it says "Signiture Mismatch".
I'm using the 4.4.4 (KTU84P) from the Factory Images website if that's any help....
Click to expand...
Click to collapse
Doesn't 4.4.4 image need a KitKat bootloader? Ver 4.23 was used for Jelly Bean 4.3 AMAIK
tetakpatalked from Nexus 7 flo

tetakpatak said:
Doesn't 4.4.4 image need a KitKat bootloader? Ver 4.23 was used for Jelly Bean 4.3 AMAIK
tetakpatalked from Nexus 7 flo
Click to expand...
Click to collapse
Hmmm
Well that was the bootloader that was in the 4.4.4 download when I unzipped everything. :/
Is there meant to be another one?
Should I maybe just try and flash a Jelly Bean image onto the tablet then?
Thanks again for your help.

Downgrade Orea beta to Nougat

Orea beta is great but battery drain so much.
for 30 min of screen use it used 11%, is it normal ?
and I am looking to go back to Nougat, could any one please tell me how can I go back.
Thank you.

are this instructions for downgrading ?
Set up your computer for flashing
Download the fastboot tool from the Android SDK Platform-Tools package
Add it to your path so the flash scripts can find it
Connect your Essential phone to your computer with a USB cable
Enable unlocking
Before you can flash a new image, ensure Developer options are enabled and OEM unlocking is turned on. To do this:
Tap Settings, then tap System > About phone
Scroll to the bottom of the page, then tap Build number multiple times until you see the pop-up message “You are now a developer” (It usually takes seven taps)
Go back one screen to System, then tap Developer options
Find the option: OEM Unlocking and turn it on
Fastboot mode
Put your Essential Phone into fastboot mode by doing either of the following:
Use the ADB tool packaged above to run the command: adb reboot bootloader
Reboot your phone while holding the Volume-down button
Unlock your bootloader
NOTE: Installing the factory image will erase all information from your device. So remember to backup your phone before continuing.
Run the command: fastboot flashing unlock
Press the Volume-down button to navigate to the YES option, then press the Power button to confirm
Flash your factory image
Download the factory image to your computer
Unzip the downloaded file
Go to where you unzipped the images
For Linux / Mac OS X - Run the command: flashall.sh
For Windows - Run the command: flashall.bat
https://forum.xda-developers.com/essential-phone/help

Yup those are them, I just did it yesterday.
Just an FYI, I found that putting Oreo on the phone resulted in ADB not working 100% anymore, such as attempting to reboot into recovery/etc. It would just reboot back into the O.S..
Here is what I did.
- download the current release you want to flash. (e.g. NMJ32F), then unzip it into a new folder.
- on your phone, verify that USB debugging and OEM unlocking are turned on in the developers menu.
- reboot your phone into the fastboot mode (power and volume down buttons)
- from your adb command line: type: fastboot flashing unlock
- This will make your phone show a new screen asking if you want to unlock the bootloader. Use the volume down to select YES, and hit the power button. It will now reboot and erase the phone. It will eventually end up booting up too request you setup the phone. (that is what it did for me.)
- reboot the phone back into the fastboot mode (power and volume down buttons)
- you should now see the bootloader listed as unlocked (vs locked)
- from your adb command line: type: fastboot devices (which should show your phones serial number and fastboot next too it.
- on your computer, using the command line, go to the unzipped folder of the NMJ32F build you downloaded
- in the folder there is a batch file you will run called flashall.bat. run it
- your phone will start flashing the NMJ32F build
- when it completes it will reboot a couple of times, erase the phone, and end up at the "lets get started" screen.
- reboot the phone back to the fastboot mode
- from your adb command line: type: fastboot flashing lock
- select the option to lock your bootloader. The phone will reboot/erase I believe, and then end up back to the "lets get started" screen.
- after you setup your phone, you can go back into the developers menu to turn off the oem unlocking
The above steps pretty much follow essentials instructions. (the essential instructions don't give some specifics.)
You are all done. (I recommend you review my instructions and the essential instructions carefully, don't copy paste commands as I may have spelled something wrong, etc.. Just wanted to give you a flow of the process.)
vjyrdy said:
are this instructions for downgrading ?
Set up your computer for flashing
Download the fastboot tool from the Android SDK Platform-Tools package
Add it to your path so the flash scripts can find it
Connect your Essential phone to your computer with a USB cable
Enable unlocking
Before you can flash a new image, ensure Developer options are enabled and OEM unlocking is turned on. To do this:
Tap Settings, then tap System > About phone
Scroll to the bottom of the page, then tap Build number multiple times until you see the pop-up message “You are now a developer” (It usually takes seven taps)
Go back one screen to System, then tap Developer options
Find the option: OEM Unlocking and turn it on
Fastboot mode
Put your Essential Phone into fastboot mode by doing either of the following:
Use the ADB tool packaged above to run the command: adb reboot bootloader
Reboot your phone while holding the Volume-down button
Unlock your bootloader
NOTE: Installing the factory image will erase all information from your device. So remember to backup your phone before continuing.
Run the command: fastboot flashing unlock
Press the Volume-down button to navigate to the YES option, then press the Power button to confirm
Flash your factory image
Download the factory image to your computer
Unzip the downloaded file
Go to where you unzipped the images
For Linux / Mac OS X - Run the command: flashall.sh
For Windows - Run the command: flashall.bat
https://forum.xda-developers.com/essential-phone/help
Click to expand...
Click to collapse

I cannot get past the flashall.sh command, says permission denied everytime. I am able to execute every command to that point with out any issues. I have downloaded the latest android platform tools, and my mac is on the latest version of macOS . I have also tried to flash every single image that is available on the essential dev webpage. Any ideas would be awesome, is in possible to side load using the adb commands from the recovery menu and avoid the fastboot mode all together.

swagglepuff said:
I cannot get past the flashall.sh command, says permission denied everytime. I am able to execute every command to that point with out any issues. I have downloaded the latest android platform tools, and my mac is on the latest version of macOS . I have also tried to flash every single image that is available on the essential dev webpage. Any ideas would be awesome, is in possible to side load using the adb commands from the recovery menu and avoid the fastboot mode all together.
Click to expand...
Click to collapse
unlock_critical.
You can't flash all the partitions is you have not performed and unlock AND and unlock_critical.

tech_head said:
unlock_critical.
You can't flash all the partitions is you have not performed and unlock AND and unlock_critical.
Click to expand...
Click to collapse
I have ran both unlock commands successfully and still get permission denied

swagglepuff said:
I have ran both unlock commands successfully and still get permission denied
Click to expand...
Click to collapse
And you checked the OEM unlock in developer options?
Hmmmm

tech_head said:
And you checked the OEM unlock in developer options?
Hmmmm
Click to expand...
Click to collapse
The issue has something to do with Mac and the platform tools. I was able to downgrade with no problem using a friend's Windows PC.

Sorry for the silly question, but what does this statements means?
"Add it to your path so the flash scripts can find it"
Is there any better instructions for first time user which dont include instructions like above? Thanks.

trizon2016 said:
Sorry for the silly question, but what does this statements means?
"Add it to your path so the flash scripts can find it"
Is there any better instructions for first time user which dont include instructions like above? Thanks.
Click to expand...
Click to collapse
Nothing confusing about that statement for Windows, MacOS or Linux.
A command path needs to exist so that when you type the command it can be found.

OnePlus 8 TMO Magisk boot image IN2017_11_C.43

It took a bit of work to root OnePlus 8 T-Mobile version on the latest Android 12 update. I am a long time lurker and simply I wished someone else had posted the boot image to save me time. Can be simply flashed using fastboot commands.
Please check to make sure you are on the latest update from T-Mobile and that software version is: IN2017_11_C.43 Android 12 Security update November 5, 2022.
Installation instructions:
*You must have your phone unlocked for any carrier otherwise OEM unlocking will be unable to set.*
#1 go to settings, about device. TAP software version five times to enable developer options under system settings. Go to developer options and tick the following options:
a OEM Unlocking
b Enable USB debugging
#2 Download the OnePlus 8 Windows drivers and ADB fastboot drivers if your using a PC or Termux from F-Droid if using another rooted phone.
PC instructions:
Go to the directory you installed ADB and Fastboot. Open the command prompt by either right click on an empty space in that folder and finding command prompt or going to the directory tree and typing cmd and hit enter. Inside the Windows command prompt the root directory should be the same folder as your ADB and fastboot executables. Move the attached boot image to the same folder as your ADB and fastboot executables and rename it boot.img. Attach your phone to your PC and run the following commands:
adb devices
This command is so you can check to see if your PC is correctly configured and it should send you a notification on your phone to allow debugging from your PC, make sure you will allow it always.
adb reboot fastboot
This command will reboot your phone into fastboot mode. Do not select any you on your phone and only type in the following commands on your PC.
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
This command will flash the magisk modified boot image which will grant you root access to your phone.
fastboot reboot
This command will reboot your phone. Congrats, your now rooted on the latest Android 12 update for your T-Mobile Oneplus 8!

what attached boot img?

zeromonarch said:
what attached boot img?
Click to expand...
Click to collapse
I must've somehow missed it too. I cant find any boot image to download

If only there were the elusive boot image...
It could have saved my ass from the current double-slotted brick I sit upon!

Does anyone have the boot image for the latest T-Mobile update?
IN2017_11_C.45
in fact this isn't even the latest as there is a new update waiting for me with the new security release or security update but I haven't updated yet also does this wipe data?