04-28-2015 11:45 AM
26 12
tools
  1. Jerry Hildenbrand's Avatar


    Waiting is never fun, and this time Google made sure folks with a Nexus 10, Nexus 7, Nexus 4 and GSM Galaxy Nexus don't have to. Once you've done this, you're left with a clean, factory-style device -- this means everything is erased and all your pictures, music and everything else is gone. Back that all up before you start!

    [WARN]Make sure your bootloader is unlocked. Check your device section for more help. You can't continue with a locked bootloader![/WARN]

    The process is actually pretty simple, and setting up your Windows computer is the hardest part. Let's dig in.

    I. - Set up adb and fastboot on your computer

    This isn't really hard, but it's often device specific (Windows drivers and all that) so if you need any help, check the hacking sub-forum for your device. The gist of it is:


    • Install adb and fastboot drivers in you're using Windows
    • Install the adb and fastboot binaries from the Android SDK for your platform (Win, Mac and Linux are supported)
    • adjust your PATH parameter or keep track of where you've installed adb and fastboot.


    Once that's done, you've finished half the battle.

    II. Download the factory image for your device

    You can find them all here: Factory Images for Nexus Devices. Once you've downloaded it, you need to unpack the tar file. On Windows, use a program like 7-zip. On a Mac or a Linux computer, the included archive tool will extract them.

    Once extracted, place the content of the folder in the same directory you have the fastboot binary installed. Keep the same file names.

    III. Boot to the bootloader, and flash the images

    Connect your Nexus to your computer via the USB port. Make sure you have USB debugging enabled. See here for more information about that.
    Once connected, open the terminal or command prompt on your computer. Make sure you're in the folder where you have the fastboot binary and the files from the factory image download. While your phone is connected, run the following command:

    Windows:
    Code:
    adb devices
    Mac and Linux:
    Code:
    ./adb devices
    Look at the screen on your Nexus. You will have to authorize the USB connection if this is the first time you've connected your phone to your computer with debugging enabled. Choose YES to authorize it.

    Your command line should return a serial number telling you everything is connected and communicating. If it doesn't, ask for assistance in your device section -- there are plenty of folks there who can help. If it does show you the serial number, proceed to the next step.

    At the command line, enter the following command to boot into the bootloader:

    Windows:
    Code:
    adb reboot-bootloader
    Mac and Linux:
    Code:
    ./adb reboot-bootloader
    Don't unplug anything. Your Nexus should reboot into the bootloader, and you'll see the green robot and colorful text on a black screen. This is what you want.

    Next, try this command to see if fastboot is set up correctly.

    Windows:
    Code:
    fastboot devices
    Mac and Linux:
    Code:
    ./fastboot devices
    As before, you're looking for the device serial number. If you don't see it, hit your device section. This is always the trickiest part when using Windows. If you see the serial number, carry on.

    Look at the files you extracted from the image download. You're looking for the following: flash-all.bat (Windows) or flash-all.sh (Mac and Linux). These are the scripts that will flash the new boot image, system image, radio, or whatever other image files are needed for your device. Once you start them, never unplug your phone or interrupt the process in the command line!

    If you're using Windows, enter the following in your terminal:
    Code:
    flash-all.bat
    If you're using a Mac or Linux, use this command:
    Code:
    ./flash-all.sh
    You'll see all sorts of scrolling text, and your Nexus will restart at least once. You'll know when it's done because your command line will tell you it's finished and return you to the prompt.

    [TIP]Protip: If you open the flash-all scripts with a text editor, you can see the individual commands they carry out. If you're familiar with scripting for your platform, you can modify these a little. Often folks will change the -w switch in the last command to keep their device from getting wiped clean. Do this sort of thing at your own risk, especially on the Nexus 7. You'll see it's flashing script is a little different than the others and it requires a bit more wiping and erasing your partitions. Per personal conversation with JBQ, this should be done every time you reinstall the factory images to your N7.[/TIP]

    As usual, all the warnings about bricking devices and taking responsibility for your actions apply. Don't attempt this if you don't understand these instructions -- it's not worth bricking your Nexus because you were impatient.

    Have fun, and good luck!
    07-24-2013 09:39 PM
  2. cjshino's Avatar
    Why dont you just wait for the OTA update to get 4.3? Unless im missing something
    anon(9005341) likes this.
    07-24-2013 11:00 PM
  3. andr0idralphie's Avatar
    Waiting? Wait? Like... not getting it now?
    ಠ_ಠ






    Side note: I had SERIOUS Wi-Fi problems after the 4.3 update, it turned out a firmware update to my router had everything running like butter again! ASUS RT-N66U
    gnr_2 and digitalslacker like this.
    07-24-2013 11:08 PM
  4. Golfdriver97's Avatar
    Why dont you just wait for the OTA update to get 4.3? Unless im missing something
    This is for those that do not want to wait.
    07-24-2013 11:21 PM
  5. Paul627g's Avatar
    Thanks for this Jerry. This should save a few repetitive questions on the subject.

    Android 4.3 woo!

    Sent from my Galaxy Nexus using AC Forums mobile app
    07-25-2013 12:15 AM
  6. lethalgorman's Avatar
    jeeees, you called that easy
    07-25-2013 04:49 PM
  7. cjshino's Avatar
    i cant get cmd to recognize my nexus 4. i get this message 'not recognized as a internal or external command, operable program or batch file'
    also on windows 8
    07-25-2013 11:25 PM
  8. andr0idralphie's Avatar
    i cant get cmd to recognize my nexus 4. i get this message 'not recognized as a internal or external command, operable program or batch file'
    also on windows 8
    At what point of the flash are you? What procedure are you following?
    07-25-2013 11:33 PM
  9. cjshino's Avatar
    At what point of the flash are you? What procedure are you following?
    I downloaded the factory image of 4.3. So then I go to bootloader on my N4 plug it in my laptop then go to cmd and type abd devices but it wont go through
    also I put the factory images in the SDK , platform tools folder. when i plug my N4 in my laptop and I go to device manager i see it as Google Nexus 4 device and i try to update the drivers but its up to date.
    07-25-2013 11:36 PM
  10. 2defmouze's Avatar
    i cant get cmd to recognize my nexus 4. i get this message 'not recognized as a internal or external command, operable program or batch file'
    also on windows 8
    I downloaded the factory image of 4.3. So then I go to bootloader on my N4 plug it in my laptop then go to cmd and type abd devices but it wont go through
    also I put the factory images in the SDK , platform tools folder. when i plug my N4 in my laptop and I go to device manager i see it as Google Nexus 4 device and i try to update the drivers but its up to date.
    Sounds like your command prompt is not IN the folder it needs to be. Hold shift and right-click in the platform-tools folder, and I believe you should see an option to Open command prompt here (I'm rusty with Windows so I'm going from memory here...). The first line of the command prompt should indicate that it is open in the correct, or incorrect, directory. Then proceed with the commands...
    adb devices

    etc

    07-26-2013 05:33 AM
  11. cjshino's Avatar
    Sounds like your command prompt is not IN the folder it needs to be. Hold shift and right-click in the platform-tools folder, and I believe you should see an option to Open command prompt here (I'm rusty with Windows so I'm going from memory here...). The first line of the command prompt should indicate that it is open in the correct, or incorrect, directory. Then proceed with the commands...
    adb devices

    etc

    Thanks for the help but I still get the same message
    07-26-2013 10:14 AM
  12. cjshino's Avatar
    Thanks for the help but I still get the same message
    Im guessing its my abd drivers? When I rooted I used Wugfresh to get automatically get my drivers. Since im one Windows 8 maybe I should uninstall those drivers and download Koushs universal drivers? or maybe its the windows 8 driver sign problem.
    07-26-2013 10:40 AM
  13. 2defmouze's Avatar
    Im guessing its my abd drivers? When I rooted I used Wugfresh to get automatically get my drivers. Since im one Windows 8 maybe I should uninstall those drivers and download Koushs universal drivers? or maybe its the windows 8 driver sign problem.
    Could be driver issues.. Those are pesky and I don't use my Windows system for these kind of things for that reason. I have some info in the Unlock and Root thread dealing with drivers and Windows 8 but it's just what I've culled from others' experiences as I haven't had to deal with it myself. See if that info helps and either way let us know any progress you make as I'd like to be able to steer people in the right direction..

    Sent from my Nexus 4 using Tapatalk 2
    07-26-2013 11:03 AM
  14. cjshino's Avatar
    Could be driver issues.. Those are pesky and I don't use my Windows system for these kind of things for that reason. I have some info in the Unlock and Root thread dealing with drivers and Windows 8 but it's just what I've culled from others' experiences as I haven't had to deal with it myself. See if that info helps and either way let us know any progress you make as I'd like to be able to steer people in the right direction..

    Sent from my Nexus 4 using Tapatalk 2
    So i uninstalled my drivers then installed universal drivers by koush and cmd still doesnt recognize my nexus 4
    07-26-2013 05:50 PM
  15. jellymann's Avatar
    You actually need the adb.exe and fastboot.exe in your working directory when you use cmd. The error message you are getting is windows' way of telling you that it doesn't recognise the command "adb". It is NOT a driver issue.

    To fix your problem, download the Mini-SDK from androidforums.
    07-27-2013 04:22 AM
  16. cjshino's Avatar
    You actually need the adb.exe and fastboot.exe in your working directory when you use cmd. The error message you are getting is windows' way of telling you that it doesn't recognise the command "adb". It is NOT a driver issue.

    To fix your problem, download the Mini-SDK from androidforums.
    i already had abd.exe and fastboot.exe in the directory and still doesnt work
    07-28-2013 05:26 PM
  17. PhoenixMike's Avatar
    It seems like I've been getting excessive bad luck with trying to get 4.3. OTA and manual downloads kept giving me an error and now no longer get push notifications of any kind. I now try to download the factory images and they stop downloading at around 30 MB. EVERY TIME. I tried both on my phone and PC.

    EDIT:
    After flashing stock 4.2.2 image (no data wipe occurred) I was able to pull and successfully download the OTA.
    07-30-2013 10:26 PM
  18. andr0idralphie's Avatar
    It stops at 30MB on your comp and phone? Weird. Tried resetting the router? At this point I still don't think everyone is getting the OTA 4.3 update but if you're impatient as I am you might want to weigh the risk of flashing the 4.3 image.
    07-31-2013 12:03 AM
  19. PhoenixMike's Avatar
    It stops at 30MB on your comp and phone? Weird. Tried resetting the router? At this point I still don't think everyone is getting the OTA 4.3 update but if you're impatient as I am you might want to weigh the risk of flashing the 4.3 image.
    Yep, reset didn't help. I already installed the OTA and everything is fine except that I still can't get any notifications... I feel like something went wrong when the update failed the first time.

    Sent from my Nexus 4 using AC Forums mobile app
    07-31-2013 04:45 PM
  20. andr0idralphie's Avatar
    I know some people erase some file to force the OTA to be available to them, if you happened to have done that the only fix for the wonkiness that might ensue, from what I've read, is to remove and re-add your Google account.
    07-31-2013 05:43 PM
  21. mrgnex's Avatar
    I downloaded the factory image of 4.3. So then I go to bootloader on my N4 plug it in my laptop then go to cmd and type abd devices but it wont go through
    also I put the factory images in the SDK , platform tools folder. when i plug my N4 in my laptop and I go to device manager i see it as Google Nexus 4 device and i try to update the drivers but its up to date.
    You're using adb in fastboot mode. You must type ``fastboot devices``..
    08-13-2013 05:39 AM
  22. Septro's Avatar
    I'm trying to update my N5 and I'm getting stuck on update failed due to mismatch on the baseband version. Looks like version M8974A-2 is reqiuired to complete the update and my phone is still on M8974A-1.

    Anyone else getting this error?
    06-02-2014 06:23 PM
  23. Anjith Sasindran's Avatar
    Guys like me!
    06-03-2014 01:54 AM
  24. theonlyskates's Avatar
    after getting past the windows 8.1 signed driver issue everything went smoothly on my nexus 7 (2012)
    06-03-2014 03:25 AM
  25. DAVID ARGENTIERI's Avatar
    Used good ol' reliable wug nexus toolkit...directed it to the rar and flashed it no prob. Maybe placebo effect, but my N4 is very smooth. I think I'm staying on stock, I've grown tired of toying around with my phone. Clean android is really well-integrated these days. I can throw another launcher on if I want to put on some different icons and stuff, but I really like ok google being available from all screens.
    06-03-2014 12:17 PM
26 12

Similar Threads

  1. Replies: 163
    Last Post: 09-09-2014, 09:22 PM
  2. New nexus 7 hdmi question
    By Dizzo1992 in forum Google Nexus 7 Tablet (2013)
    Replies: 20
    Last Post: 01-13-2014, 02:16 PM
  3. Replies: 3
    Last Post: 12-03-2013, 03:40 AM
  4. Nexus 4 : HOW TO : UPDATE to 4.3 frm STOCK 4.2.2 ( STOCK recovery, Locked/Unlocked Bootloader)
    By Phalgun Gujjar in forum Android 4.1 / 4.2 / 4.3 Jelly Bean
    Replies: 0
    Last Post: 07-24-2013, 08:33 PM
  5. Replies: 0
    Last Post: 07-24-2013, 08:13 PM
LINK TO POST COPIED TO CLIPBOARD