How to Get Nexus 9 Working Well Again

You are using an out of date browser. It may not display this or other websites correctly.
Y'all should upgrade or utilize an alternative browser.

• #1

The aim of this thread is to brand 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 every bit simple as possible for new users. This volition work regardless of what modifications you've washed to your device. Call back to backup all your of import 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 estimator.

Prepare your tablet

Enable developer options in settings > near tablet and tapping build number vii times
Open developer options and enable usb debugging. (If you haven't unlocked your bootloader however, tick enable oem unlock)

Extract images

Place the downloaded mill image inside your adb binder and excerpt with 7zip.
A new folder volition be there called something like volantis-lrx21. Open up and excerpt "image-xxxxx-zippo" to your adb folder. Nosotros are interested in these files:

bootloader-flounder-xxxxxx.img
kick.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 get in easier to type.

Now that everythings prepare, nosotros can start flashing

Plug in your device. Open up the adb binder, hold shift and correct click and select open command window here
(if your having driver bug try using Pdanet)

Run these commands one at a time

                                  adb devices  adb reboot bootloader                                

if y'all haven't unlocked the bootloader yet run
and follow the instructions using the volume keys to scroll through the menu. This procedure will wipe all data.

Run the following commands ane at a time

                                  fastboot wink bootloader bootloader-flounder-xxxxxxx.img         [B]  [I](supervene upon 'bootloader-flounder-xxxxx.img' with full name of bootloader image[/I])[/B]  fastboot reboot-bootloader  fastboot -w  fastboot flash kick boot.img  fastboot wink recovery recovery.img  fastboot flash cache cache.img  fastboot flash system organisation.img  fastboot flash vendor vendor.img                                

(OPTIONAL) At this stage you can relock the bootloader if you want past running the control

finally reboot the device by running

Thats information technology. Enjoy your tablet in manufactory status

Last edited: Dec xx, 2014

• #2

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

• #3

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

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 then I decided not to include it. It should work fine most of the time.

• #4

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

• #5

Absurd, thanks for the information.

Last edited: Dec 27, 2014

• #half dozen

Thanks for creating this! Volition come up in handy. Saving this for later

• #7

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

• #8

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 paradigm-xxxxx-zip as a zip file,in ruu mode?

I indeed tried this every bit a terminal chance hoping it would featherbed bootloader lock protection. It didn't work since I think the factory image is not signed by HTC as RUU are . It also atomic number 82 to a fastboot crash. Now sending my nexus nine for RMA

Sent from my HTC One using XDA Free mobile app

• #9

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

Same here. The transmission flash method worked very well. Here's hoping that Google doesn't muck 5.ane

• #10

cant wink stock rom

I'm trying to downgrade my nexus 9 from DU rom 5.i.1 to stock for everything. I'm running the wink-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

• #xi

I'k trying to downgrade my nexus 9 from DU rom 5.1.1 to stock for everything. I'grand running the wink-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 even so has the DU rom. Any tips

The flash all script doesn't seem to work on linux. You shouldn't accept a problem if you write the commands out manually.

• #12

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

The flash all script doesn't seem to piece of work on linux. You shouldn't have a problem if you write the commands out manually.

Every bit indicated, the flash all script doesn't work very well on whatever organization. Flash each .img separately via fastboot.

• #13

Equally indicated, the flash all script doesn't work very well on any system. Flash each .img separately via fastboot.

Trouble is that the tgz is too large 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 fifty-fifty bothered to examination the procedure.

• #14

Problem is that the tgz is too big for the device'south buffer, so it craps out earlier it really writes the images. Its been this mode for a while over several dissimilar nexus devices. Kind of like nobody at google ever even bothered to test the process.

I agree.

• #15

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

• #xvi

I as well used Linux simply I executed the commands individually rather than using the script. It worked.

I cant wink organization.img I get fault

sending 'system' (1108544 KB)...
FAILED (remote: data length is too big)
finished. total time: 0.105s

• #17

I cant wink organisation.img I get error

sending 'organization' (1108544 KB)...
FAILED (remote: data length is besides large)
finished. total time: 0.105s

Update your Android SDK.

• #18

These instructions besides worked with 5.1.1

• #19

im trying to install dorsum to facctory i erased my organisation 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

• #xx

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

Are y'all writing the full name and file path for the bootloader img?

Similar threads

davidwrin1973.blogspot.com

Source: https://forum.xda-developers.com/t/guide-nexus-9-back-to-stock-guide-unbrick-restore-factory-firmware.2975668/

Share this post