Database Users

Returning to stock

Wanting to go back to stock on the nexus 7. I have downloaded the factory image but for the life of me cannot figure out how to flash it. I am in the bootloader and i've extracted the image to my adb and fastboot directory. there is a "flash-all.sh" file but I'm unsure what to do with it. Any help would be appreciated. Thanks.

I personally don't remember how to use the .sh files.
But open the file with a text editor such as Notepad++, and you'll see the commands the script will run. You can run them manually.

sh files are purely for Linux users (it's the equivalent of batch files in Windows). Just run the commands in the sh file in your command prompt (or alter them so that it matches your fastboot).

I downloaded the images and looked at the script. Here is what it does.
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash bootloader bootloader-grouper-3.34.img
fastboot reboot-bootloader
<Wait for it to reboot>
fastboot -w update image-nakasi-jrn84d.zip
And you're done.

Thanks to all three of you. I am now back to stock. I appreciate the help at this crazy hour in the morning.

chris.wueste said:
Thanks to all three of you. I am now back to stock. I appreciate the help at this crazy hour in the morning.
Click to expand...
Click to collapse
Help asap....trying to flash stock file... in adb, I've typed all fast boot commands...I get an error at the " boot loader boot loader grouper" command. It says error, cannot load etc.

gmen78 said:
Help asap....trying to flash stock file... in adb, I've typed all fast boot commands...I get an error at the " boot loader boot loader grouper" command. It says error, cannot load etc.
Click to expand...
Click to collapse
Are you still stuck? What is going on at the moment? What have you tried? PM me if you would rather.

Ya I'm still stuck....tried using wugfresh toolkit to get back to stock but drivers ain't working correctly. I'd rather just flash stock Google image if possible and be done.
Sent from my Galaxy Nexus using Tapatalk 2

Can you use ADB and Fastboot???
Do you know how to use ADB and Fastboot???

If you are stuck returning to stock, I have just posted a full guide in the development section. I just did it myself to make sure that it works. Enjoy.

[Q] Can't install bootloader.img in adb

I have read the guide and searched for 5 hours and still can't find an answer.
I have a windows 7 computer with the SDK and all drivers installed properly and have both the factory images downloaded from Google. The extracted factory image has been placed in my SDK folder platform-tools. I have been trying to flash the bootloader via fastboot commands. The computer recognizes the nexus 7 and gives me the proper serial number when I do "fastboot devices". I then run through all the commands in the "Guide flashing a factory image", fastboot erase boot, fastboot erase cache, fastboot erase recovery, fastboot erase system, fastboot erase userdata and see that all the commands finish. When I get to fastboot flash bootloader bootloader-grouper-4.13.img the command prompt just hangs and does nothing. In the upper left corner of the Nexus 7 I see signature match but the command line reads sending 'bootloader' <2096 KB>...
OKAY [ 0.265s]
writing 'bootloader'....
I am lost as to what to do. Should I try the command fastboot reboot-bootloader even though I may not have properly flashed the bootloader.img????
Thanks for any help, I have been playing with this since yesterday.

Why did you erase cache, system, recovery etc? Weren't you just updating your hboot?
Usualy not wise to loose power while updating firmware, but if you've been at it for a day you soon will as I don't believe you can charge through bootloader mode.
When flashing through fastboot the update won't take effect until you reboot, if its hung for a while (I mean a real long while as this may not be safe) why not unplug usb, replug, then fastboot flash a recovery quick.
Now get a new download of whatever spl you can find with md5sums. Download and make sure the md5 matches
Now flash that hboot and see what happens
Sent from my HTC Vision using xda premium

I read a lot about problems with that 4.xx bootloader.
Try flashing one of the 3.xx bootloaders from 4.1.x factory images.

[Q] Possible Brick?

I'm selling my Nexus 7 and I think I got a little click happy while clearing it out.
I had reinstalled 4.3 and then for some reason I formatted the data. Got stuck in a boot loop.
When I try to install the image again I get the following:
Updating partition details...
E:error opening '/data/media'
E:error: no such file or directory
Any help would be appreciated!

"90% of the time, when someone says something's bricked, the only brick is their head." - Koush
All this means is that your userdata partition got all jacked up. It's restored when you boot into a rom, but of course you can't boot into a rom cause something else must have also went awry. So I suggest you wipe everything and start over. Follow along with me, this will be fun!
Boot into fastboot, send fastboot unlock command if your bootloader isn't already unlocked "fastboot oem unlock." Accept on screen. Reboot back into bootloader/fastboot. Issue FASTBOOT ERASE USERDATA, FASTBOOT ERASE RECOVERY, FASTBOOT ERASE CACHE, FASTBOOT ERASE SYSTEM. Then flash TWRP recovery using FASTBOOT FLASH RECOVERY [NAME OF TWRP GROUPER IMG]. Then adb push your rom and gapps back to your tablet using ADB PUSH [FILE] /SDCARD, then flash your rom and enjoy a fresh clean tablet!

That's why I prefixed with 'possible'...
Thanks - I followed this guide later in the evening and got it all up and going again.
http://goo.gl/BsiewY
0vermind said:
"90% of the time, when someone says something's bricked, the only brick is their head." - Koush
All this means is that your userdata partition got all jacked up. It's restored when you boot into a rom, but of course you can't boot into a rom cause something else must have also went awry. So I suggest you wipe everything and start over. Follow along with me, this will be fun!
Boot into fastboot, send fastboot unlock command if your bootloader isn't already unlocked "fastboot oem unlock." Accept on screen. Reboot back into bootloader/fastboot. Issue FASTBOOT ERASE USERDATA, FASTBOOT ERASE RECOVERY, FASTBOOT ERASE CACHE, FASTBOOT ERASE SYSTEM. Then flash TWRP recovery using FASTBOOT FLASH RECOVERY [NAME OF TWRP GROUPER IMG]. Then adb push your rom and gapps back to your tablet using ADB PUSH [FILE] /SDCARD, then flash your rom and enjoy a fresh clean tablet!
Click to expand...
Click to collapse

[Tutorial] Restore Nexus 9 to Stock

I have a defective device and in preparing to return it, I locked the bootloader and found a nasty little message at the top of the screen when booting:
Code:
This is a development device not intended for production use.
I was afraid that the N9 was like the N5 & 7 with the "tamper" flag, but after some digging (and advice from others out here), I decided to restore the factory image to see if that would overwrite the image. Yes! No more big fat red "I unlocked my bootloader and may have voided my warranty" message.
I can't take credit for this, but I thought I would consolidate everything I was finding in the Q&A threads into one spot, so I put this little tutorial together. Thank you @Pilz, @jd1639 & @PhilDX for your various posts.
Step 1 - Prepare your system
[Windows]
Since your bootloader is unlocked, you probably already have ADB and fastboot, but if not, grab the SDK from here, unzip and add the "platform-tools" directory to your PATH statement
If your drivers are set up properly and your device has Android debugging enabled, connect USB and execute `adb devices` from a command prompt you should see your device listed
Download the factory image for "volantis" here
The image is double zipped, so unzip, untar, then unzip the image-volantis-lrx21q.zip file into the same directory that contains the bootloader*.img file
Step 2 - Unlock bootloader
If you locked your bootloader, unlock again:
Code:
adb reboot bootloader
fastboot oem unlock
Step 3 - Flash stock image
The flash-all.bat script is broken, so you have to do it by hand:
Open a command prompt
cd into the directory where you unzipped the factory image files
Code:
fastboot flash bootloader bootloader-flounder-3.43.0.0114.img
fastboot reboot-bootloader
fastboot erase system
fastboot erase recovery
fastboot erase cache
fastboot erase boot
fastboot erase userdata
fastboot erase vendor
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash cache cache.img
fastboot flash boot boot.img
fastboot flash vendor vendor.img
Before rebooting, relock the bootloader:
Code:
fastboot oem lock
Your N9 will reboot and do another factory reset (even though an oem lock is not supposed to).

Typo: fastboot oem unlock

hirndurst said:
Typo: fastboot oem unlock
Click to expand...
Click to collapse
Hahaha! Thanks.

always good to know! thanks!

Just a question, I'm still a beginner at adb fastboot flashing.
But doesn't the oem unlocking and subsequent oem lock, erase everything anyway, so are the erase commands still required?

AjunNg said:
Just a question, I'm still a beginner at adb fastboot flashing.
But doesn't the oem unlocking and subsequent oem lock, erase everything anyway, so are the erase commands still required?
Click to expand...
Click to collapse
The erase commands are required. I believe that a factory reset only clears userdata (and probably cache). You need to run the others to clear those partitions to make room for the factory images. Each of those commands run pretty quick anyway.

DarthSudo said:
The erase commands are required. I believe that a factory reset only clears userdata (and probably cache). You need to run the others to clear those partitions to make room for the factory images. Each of those commands run pretty quick anyway.
Click to expand...
Click to collapse
You could also use fastboot -w instead of the erases
Sent from my Nexus 9 using XDA Free mobile app

Thanks for this thread. Great guide.

jd1639 said:
You could also use fastboot -w instead of the erases
Click to expand...
Click to collapse
According to the fastboot "help", -w only formats userdata and cache, does it actually format the other partitions as well? This wouldn't be the first time the documentation is wrong...
Code:
-w erase userdata and cache (and format
if supported by partition type)

Thanks for this. I RMA'd my Nexus 9 and sending it back tomorrow

DarthSudo said:
According to the fastboot "help", -w only formats userdata and cache, does it actually format the other partitions as well? This wouldn't be the first time the documentation is wrong...
Code:
-w erase userdata and cache (and format
if supported by partition type)
Click to expand...
Click to collapse
It only formats userdata and cache. But you don't need to erase the other partitions
Sent from my Nexus 5 using XDA Free mobile app

AjunNg said:
Just a question, I'm still a beginner at adb fastboot flashing.
But doesn't the oem unlocking and subsequent oem lock, erase everything anyway, so are the erase commands still required?
Click to expand...
Click to collapse
jd1639 said:
You could also use fastboot -w instead of the erases
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
jd1639 said:
It only formats userdata and cache. But you don't need to erase the other partitions
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
You guys are all right. I looked back at some of my notes and I've flashed plenty of devices w/o formatting the other partitions first. Just userdata and cache. Thanks!

Hey guys, just wanted to thank you for the fixed "script". This is now my flash-stock.sh script I use whenever I need to flash a nexus device as the one delivered by google just doesn't work (reboot loop due to crashing apps on startup or "missing system.img").
Works perfect and I always like to not dirty but rather make a clean flash as it just reduces the number of possible faults .
Cheers
Creamy

Just got my N9. First thing I did was to apply all updates, then unlock bootloader, boot into TWRP and make a system image. Then I flashed TWRP and rooted. Now if I want to take an OTA update, all I have to do restore the system image and flash the stock recovery, right? Am I missing anything? Thx.
Sent from my Nexus 6 using Tapatalk

bruce7373 said:
Just got my N9. First thing I did was to apply all updates, then unlock bootloader, boot into TWRP and make a system image. Then I flashed TWRP and rooted. Now if I want to take an OTA update, all I have to do restore the system image and flash the stock recovery, right? Am I missing anything? Thx.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
The OTA will run a check and will fail if the image isn't basically stock. For you, just do a full unroot in the SuperSU app (under Settings), then you need to replace TWRP with the stock recovery from fastboot:
Code:
fastboot flash recovery recovery.img
Reboot then take the OTA.
Of course, you will need to install TWRP and re-root again after the OTA...

DarthSudo said:
The OTA will run a check and will fail if the image isn't basically stock. For you, just do a full unroot in the SuperSU app (under Settings), then you need to replace TWRP with the stock recovery from fastboot:
Code:
fastboot flash recovery recovery.img
Reboot then take the OTA.
Of course, you will need to install TWRP and re-root again after the OTA...
Click to expand...
Click to collapse
Thx, that seems simple enough. But I made the initial system (stock) backup before I rooted. That's why I was thinking restoring that would work. I just wasn't sure about the recovery, whether the restore would put the stock recovery back or not.
Sent from my Nexus 6 using Tapatalk

DarthSudo said:
I have a defective device and in preparing to return it, I locked to bootloader and found a nasty little message at the top of the screen when booting:
Code:
This is a development device not intended for production use.
Your N9 will reboot and do another factory reset (even though an oem lock is not supposed to).
Click to expand...
Click to collapse
Hi,
is there a way to get rid of that red message if your bootloader is locked and you cannot boot into OS?
Thanks!

EDIT* Nevermind

Hey. Sorry for reviving this thread.
I installed Remix OS on my N9 and (after discovering that performance is horrible, with ~80% RAM usage on idle) after a reboot, Remix OS won't get past it's boot splash. I am attempting to flash my device back to stock.
I never touched the bootloader (never did any 'fastboot flash bootloader ...' or anything), so it it still necessary to flash the bootloader image, or can I just flash the system.img, boot.img, vendor.img etc.?

The bootloader had never changed so there is no reason to flash it.
Sent from my Nexus 9 using XDA Free mobile app

Help me : How to restore factory image

Hi guys. Sorry for being noob.
Wanna asking (confused).
My Nexus 7 (2012 Wifi) used Omni Rom 4.4.4
I wanna restore back to Stock Rom.
Do i need to Unroot & Unlock my nexus first before click " flash-all.bat " ??.
I worry might be soft brick if wrong step.
Many many thanks ^_^v

suaji said:
Hi guys. Sorry for being noob.
Wanna asking (confused).
My Nexus 7 (2012 Wifi) used Omni Rom 4.4.4
I wanna restore back to Stock Rom.
Do i need to Unroot & Unlock my nexus first before click " flash-all.bat " ??.
I worry might be soft brick if wrong step.
Many many thanks ^_^v
Click to expand...
Click to collapse
No, you were previously on OmniROM means your bootloader is already unlocked. You just need to boot into bootloader/fastboot mode and flash stock image. Do make sure you have the correct drivers installed. You could use the Universal Naked Drivers if you don't have the correct drivers installed.

rahimali said:
No, you were previously on OmniROM means your bootloader is already unlocked. You just need to boot into bootloader/fastboot mode and flash stock image. Do make sure you have the correct drivers installed. You could use the Universal Naked Drivers if you don't have the correct drivers installed.
Click to expand...
Click to collapse
Noted!.
TQ Sir for replying me ^_^v
i saw inside flash.bat got code :
so that mean i need to do manual oem lock right?.
Code:
fastboot oem unlock
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
sleep 10
fastboot -w update image-nakasi-lmy47v.zip

suaji said:
Noted!.
TQ Sir for replying me ^_^v
i saw inside flash.bat got code :
so that mean i need to do manual oem lock right?.
Code:
fastboot oem unlock
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
sleep 10
fastboot -w update image-nakasi-lmy47v.zip
Click to expand...
Click to collapse
If you mean re-lock the bootloader, yes, you will have to do that manually. It's supposed to be a risky procedure so do so at your own risk.
By the way, your signature shows Next 7 3G, that would be the Tilapia rather than Grouper. Make sure before you flash please.

rahimali said:
If you mean re-lock the bootloader, yes, you will have to do that manually. It's supposed to be a risky procedure so do so at your own risk.
By the way, your signature shows Next 7 3G, that would be the Tilapia rather than Grouper. Make sure before you flash please.
Click to expand...
Click to collapse
thanks for helping sir.
now I can use stock rom back..