Database Users

Nexus 7 Bricked??/Broken

Nexus 7 was rooted,unlocked bootloader and was running paranoid anroid 3.90+ i think . i plugged it into the computer to get a new rom using nexus root toolkit v1.7.2. i was asked to update a few things, so i clicked yes. i then tried to flash stock + unroot and chose 4.3 cause i wanted to try the new OS. but i guess something happened because when i turned my nexus 7 back on i was stuck on the load screen (GOOGLE image with a unlocked lock) i could cycle thru a few options using volume keys (start,recovery,power off) .all of them seemed useless as they would just bring me back to where i was.when clicking start "booting failed" come up on the upper left side. when trying to flash stock +unroot using NRT i get up to the sending "bootloader" part and my nexus 7 just freezes, how do i fix this. please and thanks

download the factory image from the google factory image and extract the archive.
try flashing the bootloader manualy with fastboot.
locate your fastboot binary and copy the bootloader image to that directory.
open a commandline in that directory and type
fastboot flash bootloader name-of-bootloader.img
after that you can try to flash the whole factory image with the flash-all.sh script.

Simple
dieselmonkeyy said:
i could cycle thru a few options using volume keys (start,recovery,power off) .all of them seemed useless as they would just bring me back to where i was.when clicking start "booting failed" come up on the upper left side.
Click to expand...
Click to collapse
Boot failed??? That's a bad flash of the stock ROM. I had the same problem at my first attempt trying to flash Stock ROM, but don't worry! Let's do this:
WARNING: Before you continue you are accepting that I'm not responsible of anything can happen to your Nexus and your battery is fully charged.
When you download the stock ROM you have to uncompress the zip file. You will find the bootloader and another zip.
Uncompress that zip file, put fastboot program, the bootloader and the files together.
Then start your Nexus into bootloader mode, connect it to your PC, open a console (cmd for Windows, Terminal for Linux and Mac OS X) and type this:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
WARNING: Your Nexus is FULLY EMPTY!!! Don't reboot it because it can get a full brick (It will not turn on any more).
Now type this:
fastboot flash bootloader bootloader-grouper-X.XX.img
NOTE: Replace X.XX with your version.
Now type:
fastboot reboot-bootloader
Your Nexus will reboot.
Type this:
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash recovery recovery.img
fastboot flash system system.img #Will take a very long time. DON'T INTERRUPT THE PROCESS!!!!!
fastboot flash userdata userdata.img
Now reboot again with:
fastboot reboot-bootloader
Re-unlock bootloader to get a full wipe:
fastboot oem lock
Reboot again:
fastboot reboot-bootloader
And then unlock the bootloader:
fastboot oem unlock
Press "Yes" to the petition screen and reboot:
fastboot reboot
Ready the Nexus!
I had the same problem and I did this.
I hope I can help you.
Sorry for my bad English. I'm from Argentina and I'm learning.
Well,
Good luck!

MlucianoEze said:
Boot failed??? That's a bad flash of the stock ROM. I had the same problem at my first attempt trying to flash Stock ROM, but don't worry! Let's do this:
WARNING: Before you continue you are accepting that I'm not responsible of anything can happen to your Nexus and your battery is fully charged.
When you download the stock ROM you have to uncompress the zip file. You will find the bootloader and another zip.
Uncompress that zip file, put fastboot program, the bootloader and the files together.
Then start your Nexus into bootloader mode, connect it to your PC, open a console (cmd for Windows, Terminal for Linux and Mac OS X) and type this:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
WARNING: Your Nexus is FULLY EMPTY!!! Don't reboot it because it can get a full brick (It will not turn on any more).
Now type this:
fastboot flash bootloader bootloader-grouper-X.XX.img
NOTE: Replace X.XX with your version.
Now type:
fastboot reboot-bootloader
Your Nexus will reboot.
Type this:
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash recovery recovery.img
fastboot flash system system.img #Will take a very long time. DON'T INTERRUPT THE PROCESS!!!!!
fastboot flash userdata userdata.img
Now reboot again with:
fastboot reboot-bootloader
Re-unlock bootloader to get a full wipe:
fastboot oem lock
Reboot again:
fastboot reboot-bootloader
And then unlock the bootloader:
fastboot oem unlock
Press "Yes" to the petition screen and reboot:
fastboot reboot
Ready the Nexus!
I had the same problem and I did this.
I hope I can help you.
Sorry for my bad English. I'm from Argentina and I'm learning.
Well,
Good luck!
Click to expand...
Click to collapse
what do i type into cmd inorder to be able to type
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
and get it to work. im a noob . thanks in advance

You have to be in the folder with fastboot inside else those commands will not work.
It will be easier if you put the images extracted from the zip into the zip together with the fastboot program.
If you don't understand yet I'll try to be more specific.
Sent from my Nexus 7 using xda app-developers app

dieselmonkeyy said:
what do i type into cmd inorder to be able to type
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
and get it to work. im a noob . thanks in advance
Click to expand...
Click to collapse
It can be intimidating... and the so-called tool-kits don't help you learn
I assume you are using Windows.
follow the unzip instructions from the previous poster. (not quoted here). note the directory.
find the directory containing your android tools... ADB.exe and FASTBOOT.exe.
transfer your unzipped files to this directory. Open your CMD prompt window and change to this directory if necessary.
plug in your Nexus.
type fastboot device at the prompt. MAKE SURE YOUR NEXUS 7 is listed (serial number)
proceed with the complete instructions from the previous poster.
that should do it.

YES!!!
thanks alot for the instructions, it worked!!! i hope people use ur instructions as reference if they have the same problem. THANKS ALOT!!!

dieselmonkeyy said:
thanks alot for the instructions, it worked!!! i hope people use ur instructions as reference if they have the same problem. THANKS ALOT!!!
Click to expand...
Click to collapse
I'm glad the problem is solved. Do not forget to click the THANKS button.
Sent from my Nexus 7 using xda app-developers app

Hello. My brother's Nex 7 is also has this issue. I cannot follow any of the steps as it gets stuck on erasing any of the partitions. I tried erasing those partitions in any order and they still get stuck. His device was stock and bootloader locked too. When I try to unlock the bootloader, it gets stuck as well at the erasing userdata part. I suspect a bad memory chip. Anyone else experience this?

Yes, mine is sticking on the (bootloader) erasing userdata on bootloader unlock as well.
It also sticks on any fastboot ERASE command.
Factory reset had a bunch of errors and no longer comes up. none of the FLASH commands work because the BOOTLOADER is locked.
And since it freezes on the unlocking bootloader commands I believe I am screwed.
This was a factory installed, never flashed, unlocked or rooted Nexus 7 wifi 2nd gen. After installing the 4.4.2 that popped up it loaded once then crashed and never loaded again
I have tried every tool I can find. They all stick on the erase part.

jophisdrazin said:
Yes, mine is sticking on the (bootloader) erasing userdata on bootloader unlock as well.
It also sticks on any fastboot ERASE command.
Factory reset had a bunch of errors and no longer comes up. none of the FLASH commands work because the BOOTLOADER is locked.
And since it freezes on the unlocking bootloader commands I believe I am screwed.
This was a factory installed, never flashed, unlocked or rooted Nexus 7 wifi 2nd gen. After installing the 4.4.2 that popped up it loaded once then crashed and never loaded again
I have tried every tool I can find. They all stick on the erase part.
Click to expand...
Click to collapse
Send your device for repair. My brother did so. My suspicions were correct. A faulty chip. They replaced the whole board, according to my brother.
Sent from my Nexus 7 using Tapatalk

[Q] Stock flashable JWR66Y downlaod

Hello Community.
I have searched and searched and searched. Can some one link me to a full ODEX of JWR66Y ROM? I am trying to restore my N4 back to stock. Thanks will be given...

jgentry151 said:
Hello Community.
I have searched and searched and searched. Can some one link me to a full ODEX of JWR66Y ROM? I am trying to restore my N4 back to stock. Thanks will be given...
Click to expand...
Click to collapse
Here you are. Flash it using fastboot commands
DOWNLOAD

luiseteyo said:
Here you are. Flash it using fastboot commands
DOWNLOAD
Click to expand...
Click to collapse
Thanks!!! Do you happen to know the fastboot command? Or an instructional for this? Will I have to use stock boot loader and so on?

jgentry151 said:
Thanks!!! Do you happen to know the fastboot command? Or an instructional for this? Will I have to use stock boot loader and so on?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2010312
Sent from my Nexus 4 using xda app-developers app

jgentry151 said:
Thanks!!! Do you happen to know the fastboot command? Or an instructional for this? Will I have to use stock boot loader and so on?
Click to expand...
Click to collapse
this is my favourite guide.
Follow this steps:
1. Fastboot mode.
2. Type:
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
done!

Why download from random place when you get it officially from Google: https://developers.google.com/android/nexus/images#occam
And if you open the package it has the bat script file that will run all the commands to flash the phone automatically, you just have to put it in fastboot mode and unlock the bootloader first, or you can read the script file and manually type in the commands.

luiseteyo said:
this is my favourite guide.
Follow this steps:
1. Fastboot mode.
2. Type:
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
done!
Click to expand...
Click to collapse
Muchisimas Gracias!!!

eksasol said:
Why download from random place when you get it officially from Google: https://developers.google.com/android/nexus/images#occam
And if you open the package it has the bat script file that will run all the commands to flash the phone automatically, you just have to put it in fastboot mode and unlock the bootloader first, or you can read the script file and manually type in the commands.
Click to expand...
Click to collapse
Mine was the link from google. And I prefer to do it manually.

luiseteyo said:
Mine was the link from google. And I prefer to do it manually.
Click to expand...
Click to collapse
How do I flash stock Android without deleting any of my apps/data/settings?
Do I need to skip or remove any of those lines from the script??

The process will wipe your entire device. You have to back up your stuff and move it out of your phone. You can use the Helium app to back up apps data, if you don't have root you also need to install this http://www.clockworkmod.com/carbon for it to work.
You could leave your data alone and only flash certain partitions though. Don't run the scripts, do it all manually. Skip "fastboot erase userdata" which will wipe your apps data. Also skip "fastboot -w update image-nakasig-jwr66y.zip".
Extract the *.img files from "image-occam-jwr66y.zip" and flash them manually, skipping userdata.img of course, the other three files you want to flash would be:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
However, depending on the Android version and configuration, you might run into issues by doing this.

[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

YD201 Hardbrick...?

Hi everybody...I'm in trouble with my Yotaphone YD201.
I done format data with TWRP.
Then, I run these commands with Win10 for clean flash of RU144:
Code:
fastboot flash boot {Directory_firmware/boot.img}
fastboot flash -S 512M system {Directory_firmware/system.img}
fastboot flash recovery {Directory_firmware/recovery.img}
fastboot flash cache {Directory_firmware/cache.img}
fastboot flash modem {Directory_firmware/radio/NON-HLOS.bin}
fastboot flash sbl1 {Directory_firmware/radio/sbl1.mbn}
fastboot flash rpm {Directory_firmware/radio/rpm.mbn}
fastboot flash tz {Directory_firmware/radio/tz.mbn}
fastboot flash userdata {Directory_firmware/userdata.img}
fastboot flash aboot {Directory_file__emmc_appsboot.mbn}
fastboot reboot
After the last one, Screen gone black and nothing appends...
Now, adb and fastboot can't contact with Yota ("adb devices" give "<waiting for devices") .
Now, In Win devices, I can find " QHSUSB_BULK".
After some search, I found out that my phone is in a recovery mode of Qualcomm. Does anybody know how to unblock it? Problably I need of specific driver to contact with this phone. Thanks so much!
P.S.: do not esitate to contact me if my english is not clear =)

How about a method like this https://forums.oneplus.net/threads/solution-bricked-oneplus-one-recovery.306306/ but use Yotaphone files instead?

evilracer123 said:
How about a method like this (...) but use Yotaphone files instead?
Click to expand...
Click to collapse
This discussion uses Msm8974DownloadTool.exe from the directory of ColorOS but the wire connection does not work (the file is no longer available, from Mega).
Also, not sure if I can use Msm8974DownloadTool.exe with Yotaphone. Alternatively, what can I use?

Amazon Prime G4: Cannot install Nougat OTA, stuck at fastboot screen.

So I tried to install the nougat update, but my phone, which has been booting to fastboot ever since I messed around a little with it on RSD Lite, will not turn all the way off and the Nougat update fails. I have tried several times. My bootloader is locked and I am running completely stock with the ads. It shows up in the boot logs as "fastboot reason: utag bootmode configured as fastboot" . Anyway to fix this so I can upgrade to nougat? Thank you.

enter into fastboot mode and run this
Code:
mfastboot oem fb_mode_clear
mfastboot reboot

lerg96 said:
enter into fastboot mode and run this
Code:
mfastboot oem fb_mode_clear
mfastboot reboot
Click to expand...
Click to collapse
Thank you so much. That fixed the problem!

Where did you find the nougat update ,my xt1625 prime is bricked and I need that to try unbrick it .

If anyone else reads this; I had the issue and I just selected reboot recovery so I could manually tell the phone to apply the update. When it booted into recovery, it actually continued to install it automatically.

Does anyone have a backup of boot and recovery images for nougat xt1625 amazon?
Sent from my Moto G (4) using Tapatalk

hmm
lerg96 said:
enter into fastboot mode and run this
Code:
mfastboot oem fb_mode_clear
mfastboot reboot
Click to expand...
Click to collapse
Does this command have to be run from a specific directory?
'mfastboot' is not recognized as an internal or external command.
Thanks

andnewb1 said:
Does this command have to be run from a specific directory?
'mfastboot' is not recognized as an internal or external command.
Thanks
Click to expand...
Click to collapse
You have to open the cmd in the folder where you have the fastboot and run fastboot or mfastboot depend or which version you r using .

andnewb1 said:
enter into fastboot mode and run this
Does this command have to be run from a specific directory?
'mfastboot' is not recognized as an internal or external command.
Thanks
Click to expand...
Click to collapse
You have to download this file and use CMD and go to the mfastboot directory and the run the commands.