Database Users

who know's what i can do next to bring my 7 back to life?

Ok I just need a little help and advice so if you one of you out there in XDAland can help I’ll be truly grateful…
I’ve got the 32gb Nexus 7 which I rooted via the Wugfresh method and added I CWM for my recovery and did the OTA update to Jelly Bean 4.2.1. The last 6 months life have been peachy. Even the misses and her iDevices are jealous of my little corner of Android heaven.
So last night pick up the 7 and notice it’s running a tad sluggish and I also notice the battery is low and flashing red, so I plug in the power cable and attempted to shut it down and it just hangs… I give it 5 minutes and still not shut down so I hold power & volume down and get in to the Bootloader from here I select start and the tablet just hangs on the Google cross (red, blue, yellow, green). This now happens every time I power down even though there has been a good charge (6 hours) done. If I now go back in the Bootloader and try selecting the Recovery Mode I get the Android robot with the red warning triangle and the words “No Command” and that’s it. If I try the factory reset of power button & volume up from recovery mode I get nothing.
From the bootloader I see
Fastboot Mode
Product Name - grouper
Variant - grouper
HW version - ER3
Bootloader Version - 4.13
Baseband Version - n/a
Serial Number xxxxxxxxxxxxxxxxxxxx
Signing - not defined yet
LOCK STATE - UNLOCKED
Can someone advise what the best thing I can do to revive the 7? I don’t mind losing the data but I’m just unsure what to do next. I’ve read a few threads but none pointed me in the direction I think I need to be in…
Thanks in advance for any help given.

That's funny as I put my 16gig nexus 7 on charge a couple of hours ago and just went to pick it up and it was on the bootloader screen, but I managed to reboot and everything is fine, its funny cos I've had similar experience with galaxy s3 but that was dead after a night on charge. I've sent the s3 of for repair under warranty thinking it was the sudden death syndrome on the s3, but now I'm worried the charger might be at fault.
Has anyone heard of a charger frying an android phone or putting nexus 7 in bootloader mode? Or is it just a coincidence?
Sent from my Nexus 7 using xda premium

@OP
The recovery you describe is the stock recovery. If you used an OTA process after rooting, probably that is what overwrote the CWM install you did previously - so that explains why you see what you do when you boot to recovery via the bootloader menu.
When you use the "reset by holding the power button down for 30 seconds" you are crashed the running OS and potentially corrupted any filesystems which are mounted "rw" (read-write). So, that might explain the bootloops that occurred thereafter.
You have a couple options, but before you try any of them, I would suggest that you observe the "power state animation" that occurs for about 10 seconds when you plug the tablet in to the charger with the tablet turned off: it shows you graphically how much charged the battery has. If the animation starts with a nearly all black battery, and then "fills up", the battery is still deeply discharged; if it is all white, or mostly all white, and the animation only "tops off" the battery, it has a good charge.
If that animation shows a battery which is still discharged, I would try to solve that problem before doing anything further. It was a low battery condition that got you into trouble in the first place; no point in making things even worse.
OK. Well, if you weren't a toolkit user, I would suggest a couple things that could be done manually using a custom recovery to attempt a repair of the /data filesystem, or rescuing your raw data for a later data recovery effort. But they involve command-line stuff, so me mentioning it is a waste of time. Suffice it to say that if you still have an unlocked bootloader and functioning drivers on your PC, you can re-install whatever custom recovery you want (using either fastboot or Wugfresh) and then use the capabilities of that custom recovery. Given that you didn't even realize that your custom recovery went missing until now, that's probably also a waste of time too - I probably can safely assume you don't know what its' full capabilities are.
So, flash a custom recovery and perform a reformat of the userdata partition ("Wipe Data" in TWRP, don't know what it is in CWM). You could even try taking a Nandroid backup before doing this, but the problem with doing this is that by default it will try writing to /data - so under the presumption that your userdata partition is hosed up, writing a whole lot of stuff to it (the backup) may not create a reliable backup image(s). With TWRP you could write backups to an external device, though.
That leaves a factory reset. If you do it with the stock recovery (simultaneously press power and vol-up for about 1 second after the recovery splash screen shows up to get the menu), it will erase EVERYTHING in the /data partition - including your everything in the psuedo-SD card.
Without any further learning on your part (abandonment of toolkits), it seems like the stock recovery factory reset is the least-effort solution for you. As I said, this will destroy ALL of your data on the device, but your device should return to a bootable condition. If you made any Nandroid backups and got them off the tablet, you could restore them after installing the custom recovery which made those same backups.
good luck

As last user said, if you have any nandroids you could restore them. And honestly it'd be so much easier to just boot an img. Not that hard.
Sent from my Motorola XPRT

Defibrillator...
Sent from my Nexus 7 using xda app-developers app

@bftb0
Thanks for the response and I’m going to follow your advice… I have done the command line root method twice with this my phones the HTC Desire and the then Sensation so I have experience in the dark art… it was just I couldn’t see a way of enabling the ADB drivers so my PC and 7 could look at/see each other but I have found the following http://forums.androidcentral.com/ne...1477-guide-nexus-7-factory-image-restore.html
and this goes over what I need to do so I’ll give this a try and see how it goes. Like I say I don’t really need the data, I only used the 7 as a media hub and social media tool so I don’t mind putting the music and films back on it and the few apps and games is no big deal.
@FitAmp if this don’t work I may be taking your advice hahahahahaha!!!

bricked

slybunda said:
bricked
Click to expand...
Click to collapse
@slybunda May I ask why you say bricked?

Another case where the N7 seems to overly discharge the battery and not be able to recharge it. I've heard of this several times, it just won't charge the battery once it gets too low.
I bet if you can get the battery to charge it'll be fine. Or failing all else, this place has the battery for $30.
http://www.portatronics.com/product...oogle-Asus-Nexus-7-Original-Battery-Part.html
It is NOT bricked.

Dr Asqueroso said:
@slybunda May I ask why you say bricked?
Click to expand...
Click to collapse
Hi, Dr Asqueroso...
'Bricked' is a certainly a bit pre-emptive... if the BOOTLOADER is still good (and from your description, it sounds like it still is), then you have a very good chance of resurrecting your tablet.
The thing is, from your description, you're only 'bootlooping'... which is trivial to get out of... if you have a recent NANDROID backup (or for that matter, a flashable ROM .zip), on your internel storage and you know how to FASTBOOT FLASH a CUSTOM RECOVERY.
Your options are threefold...
----------------------
1) Use the STOCK FACTORY recovery to perform a factory reset. (As detailed by bftb0, earlier).
2) FASTBOOT FLASH a custom recovery (CWM or TWRP).
-- http://www.teamw.in/project/twrp2/103
-- http://www.clockworkmod.com/rommanager
I note you used CWM previously, so fastboot flash this recovery, and restore your last NANDROID backup. If you didn't make any NANDROIDs, then flash some other CUSTOM ROM. Or better still, use the 'wipe data' option in your Custom Recovery. I've had 'bootloops' and other weird egregious behavior myself, and this usually fixes it. (Sometimes, even wiping 'CACHE' and 'DALVIK' can make mysterious problems vanish!.)
3) Restore back to FACTORY stock.
-- http://developers.google.com/android/nexus/images
(You need the 'nakasi' version for your 'grouper' tablet).
This last option carries some risk, because it reflashes the BOOTLOADER, which is always a risky procedure (a corrupt flash will hardbrick the tablet). So, ABSOLUTELY make sure your tablet is fully charged AND you have a good USB connection to your PC.
I note you're still on bootloader v4.13, so you could edit the 'flash-all.*' script from Factory Stock JellyBean 4.1.2 (JZO54K) to remove the command to flash the bootloader. Flash as normal (by running the script), and then take the OTA update to 4.2.2 (JDQ39) over WiFi... this will still update the bootloader (to v4.18), but because of the way OTAs work, the risk is significantly reduced.
----------------------
But before you contemplate doing any of this... you need to ascertain if your battery is in good shape.
Here's what I would recommend if the battery is failing to charge correctly...
1. Plug the Nexus 7 into a wall charger.
2. Immediately press Volume Down and Power at the same time to reach the Bootloader
3. From the Bootloader menu, press Volume Down until you see “Power Off Device.”
4. Press the Power button to select the "Power Off Device" option.
5. Once your device is off, unplug the charger and then plug it back into the device.
If you see a large white battery shaped logo, that is flashing nearly all white, then you have a good level of charge... if it's flashing nearly all black (with only a bit of white), then the charge level is low... and fastboot flashing anything is not recommended.
Good luck... and hope this helps.
Rgrds,
Ged.

GedBlake said:
Hi, Dr Asqueroso...
'Bricked' is a certainly a bit pre-emptive... if the BOOTLOADER is still good (and from your description, it sounds like it still is), then you have a very good chance of resurrecting your tablet.
The thing is, from your description, you're only 'bootlooping'... which is trivial to get out of... if you have a recent NANDROID backup (or for that matter, a flashable ROM .zip), on your internel storage and you know how to FASTBOOT FLASH a CUSTOM RECOVERY.
Your options are threefold...
----------------------
1) Use the STOCK FACTORY recovery to perform a factory reset. (As detailed by bftb0, earlier).
2) FASTBOOT FLASH a custom recovery (CWM or TWRP).
-- http://www.teamw.in/project/twrp2/103
-- http://www.clockworkmod.com/rommanager
I note you used CWM previously, so fastboot flash this recovery, and restore your last NANDROID backup. If you didn't make any NANDROIDs, then flash some other CUSTOM ROM. Or better still, use the 'wipe data' option in your Custom Recovery. I've had 'bootloops' and other weird egregious behavior myself, and this usually fixes it. (Sometimes, even wiping 'CACHE' and 'DALVIK' can make mysterious problems vanish!.)
3) Restore back to FACTORY stock.
-- http://developers.google.com/android/nexus/images
(You need the 'nakasi' version for your 'grouper' tablet).
This last option carries some risk, because it reflashes the BOOTLOADER, which is always a risky procedure (a corrupt flash will hardbrick the tablet). So, ABSOLUTELY make sure your tablet is fully charged AND you have a good USB connection to your PC.
I note you're still on bootloader v4.13, so you could edit the 'flash-all.*' script from Factory Stock JellyBean 4.1.2 (JZO54K) to remove the command to flash the bootloader. Flash as normal (by running the script), and then take the OTA update to 4.2.2 (JDQ39) over WiFi... this will still update the bootloader (to v4.18), but because of the way OTAs work, the risk is significantly reduced.
----------------------
But before you contemplate doing any of this... you need to ascertain if your battery is in good shape.
Here's what I would recommend if the battery is failing to charge correctly...
1. Plug the Nexus 7 into a wall charger.
2. Immediately press Volume Down and Power at the same time to reach the Bootloader
3. From the Bootloader menu, press Volume Down until you see “Power Off Device.”
4. Press the Power button to select the "Power Off Device" option.
5. Once your device is off, unplug the charger and then plug it back into the device.
If you see a large white battery shaped logo, that is flashing nearly all white, then you have a good level of charge... if it's flashing nearly all black (with only a bit of white), then the charge level is low... and fastboot flashing anything is not recommended.
Good luck... and hope this helps.
Rgrds,
Ged.
Click to expand...
Click to collapse
First of all a massive Thank You all so much for the advice...
I think I've got it in the respects of each step but I'm just stuck with getting the drivers to work. I've installed the Java Dev Kit, the latest SDK from the Android site and successfully installed both the Tools and the Google USB Drivers. I also got the Asus drivers for the 7 and I have unziped the stock recovery JZO54K which ready to go. However can't get my 7 to show up in CMD Prompt via ADB devices string but if add my sensation it pops up everytime...
I've tried this process on a Windows 8 machine and a XP install too and the 7 is never picked up.
Does this mean the 7 is dead and stuck in the factory boot menu? What am I doing wrong?
This is killing me... :crying:

Dr Asqueroso said:
First of all a massive Thank You all so much for the advice...
I think I've got it in the respects of each step but I'm just stuck with getting the drivers to work. I've installed the Java Dev Kit, the latest SDK from the Android site and successfully installed both the Tools and the Google USB Drivers. I also got the Asus drivers for the 7 and I have unziped the stock recovery JZO54K which ready to go. However can't get my 7 to show up in CMD Prompt via ADB devices string but if add my sensation it pops up everytime...
I've tried this process on a Windows 8 machine and a XP install too and the 7 is never picked up.
Does this mean the 7 is dead and stuck in the factory boot menu? What am I doing wrong?
This is killing me... :crying:
Click to expand...
Click to collapse
No... it just means you're stuck in what is ubiquitously called 'driver hell'. Windows has always been a pain in the arse when it comes to drivers.
If you have a Windows XP box, you could try the following...
Download my copy of the FASTBOOT/ADB files for XP...
http://dl.dropboxusercontent.com/u/...orXP-MD5_8e02ab9b4b8463b9ee5c2063477b01ec.zip
Unzip to a folder on the Windows Desktop.
Unzip and copy the files from nakasi-jzo54k into the same folder.
You should now have a folder with the following files in it...
adb.exe
fastboot.exe
AdbWinApi.dll
AdbWinUsbApi.dll
bootloader-grouper-3.41.img
image-nakasi-jzo54k.zip
flash-all.bat
flash-all.sh
flash-base.sh
Delete 'bootloader-grouper-3.41.img' and edit 'flash-all.bat' to reflect this... that is to say, remove the line...
Code:
fastboot flash bootloader bootloader-grouper-3.41.img.
This is to avoid unnecessarily flashing the BOOTLOADER partition, and which in any event will only downgrade your current BOOTLOADER.
-----
Boot your Nexus 7 into BOOTLOADER mode, by pressing Vol. Down (& hold) and the Power Button.
Connect your Nexus 7 to your Windows XP PC, via a USB cable (preferably the one that shipped with the N7 originally).
Open a command prompt window on the folder into which you have copied all of the aforementioned files, and type...
Code:
fastboot devices
It should return a SERIAL NUMBER... if it does, you have a working FASTBOOT connection, and you're free to run flash-all.bat
This should restore JellyBean 4.1.2... and upon a successful reboot and a WiFi connection, an OTA upgrade will be proffered.
Allow this, and your Nexus will be upgraded to JellyBean 4.2.2 (JDQ39).
Good luck.
Rgrds,
Ged.

Okay so I have a folder with the following
adb.exe
fastboot.exe
AdbWinApi.dll
AdbWinUsbApi.dll
bootloader-grouper-3.41.img
image-nakasi-jzo54k.zip
flash-all.bat
flash-all.sh
flash-base.sh
But I'm stuck on the edit line?? sorry for being a pain can you explain this bit.. how do you edit the flash-all.bat??
Delete 'bootloader-grouper-3.41.img' and edit 'flash-all.bat' to reflect this... that is to say, remove the line...
Code:
fastboot flash bootloader bootloader-grouper-3.41.img.
This is to avoid unnecessarily flashing the BOOTLOADER partition, and which in any event will only downgrade your current BOOTLOADER.

Open the bat file in notepad.
Sent from my Galaxy Nexus

Done the edit and ran the flash-all.bat... The serial number has appeared after the fastboot command but now I seem stuck on the sending system command of 446268 been like this for 20+ minutes and somehow my bootloader is showing 3.41 on the tablet.
What next?

Dr Asqueroso said:
Okay so I have a folder with the following
adb.exe
fastboot.exe
AdbWinApi.dll
AdbWinUsbApi.dll
bootloader-grouper-3.41.img
image-nakasi-jzo54k.zip
flash-all.bat
flash-all.sh
flash-base.sh
But I'm stuck on the edit line?? sorry for being a pain can you explain this bit.. how do you edit the flash-all.bat??
Click to expand...
Click to collapse
Sometimes it's easier to 'just do' than explain 'how to do'...
Here is the modified 'flash-all.bat' script, with the line removed.
http://dl.dropboxusercontent.com/u/37483979/flash-all-MD5_ a687082ef3179feb40ba108436dc5768.zip
------
Maybe I'm just being overcautious when it comes to BOOTLOADER stuff...
It's entirely possible you could just run the original 'flash-all.bat' as is... without problems... as many people do, and as Google intended.
So, it's not critical you delete bootloader-grouper-3.41.img or run the modified .bat file... just ensure you have a damn good USB connection and power to both devices before you do.
Rgrds,
Ged.
---------- Post added at 12:55 AM ---------- Previous post was at 12:41 AM ----------
Dr Asqueroso said:
Done the edit and ran the flash-all.bat... The serial number has appeared after the fastboot command but now I seem stuck on the sending system command of 446268 been like this for 20+ minutes and somehow my bootloader is showing 3.41 on the tablet.
What next?
Click to expand...
Click to collapse
Sending /system has always been problematic for me as well... you need to change to a different USB port on your PC.
Using the Vol. Keys navigate to RESTART BOOTLOADER... disconnect and reconnect to a different USB port, and try again.
If you're BOOTLOADER is showing 3.41, don't worry about it. The issue was never about the version, but about flashing it.
This will be taken care of later, with the OTA upgrade.
Rgrds.
Ged.

There must be something else going wrong as every step I've taken thus far has worked but the final sending bit... currently on my machine see the following... it's been like this for 2 hours...

Dr Asqueroso said:
There must be something else going wrong as every step I've taken thus far has worked but the final sending bit... currently on my machine see the following... it's been like this for 2 hours...
Click to expand...
Click to collapse
2 hours is way too long... it should take less than 5 minutes to flash back to stock.
I suspect a USB connectivity issue... open another command prompt window, and type
Code:
fastboot devices
If you don't see a SERIAL NUMBER, then your FASTBOOT connection has died...
Try again, from a different USB port... and maybe a different USB cable.
----
You are actually getting somewhere though... your screenshot indicates that 'boot' went over successfully.
Don't give up hope - persevere!
Rgrds,
Ged.

Ok I'll try it again when I get home from work...

Okay followed all the steps but I think the tablet is not going to play nice... I just can't get past the sending system bit.
The 7 is now showing
Fastboot Mode (in red)
Product Name - grouper
Variant - grouper
HW version - ER3
Bootloader Version - 4.18
Baseband Version - n/a
Serial Number xxxxxxxxxxxxxxxxxxxx (now showing my number)
Signing - not defined yet
LOCK STATE - UNLOCKED
My CMD prompt window is yet again just showing sending system and nothing. Been like this for the past 30 mins or so... I've swapped my USB ports over tried and the process a few times and still no joy. I think I've been defeated.
It looks like the 7 will have to go back... but can I make a warranty claim from Asus in it's current state or will I have to lock it somehow??
Failing that I'll "lose" it and claim off the house insurance.
Oooops the CMD window is doing something different...
checking product...
OKAY [ 0.031s]
checking version-bootloader...
OKAY [ 0.016s]
sending 'boot' (4944 KB)...
OKAY [ 0.656s]
writing 'boot'...
OKAY [ 0.203s]
sending 'recovery' (5446 KB)...
OKAY [ 0.719s]
writing 'recovery'...
OKAY [ 0.219s]
erasing 'system'...
OKAY [ 0.094s]
sending 'system' (471804 KB)...
FAILED (data transfer failure (Too many links))
finished. total time: 5264.891s
C:\android-sdk\platform-tools>fastboot reboot-bootloader
< waiting for device >
rebooting into bootloader...
FAILED (command write failed (Unknown error))
finished. total time: 0.656s
C:\android-sdk\platform-tools>
Anyone with any suggestions as to my next move?

[Q] I have a broken N7.

*** Returned my N7 (2012) as faulty and swapped with a 2013. Thread Ended. ***
I've been having trouble with my N7 (2012) for a while now.. Ever since the 4.3 update.. Slow response, hangs, and so on.
The latest 4.3 update would not install. Just a lying down droid with '!'.
My tablet was rooted using Wugfresh toolkit and was perfect before 4.3.
So i thought i'd go back to the start and use the toolkit to go back to root and flash stock+unroot.
Went through all instructions, it got to the part where it says ' You tablet will now reboot a few times. Please wait.'
Waited for 30 mins and nothing..
Now got a tablet with the google name and the unlock symbol. Options available are start, bootloader, recovery, off
All bring back to same screen.. Bootloader option displays -
Fastboot mode
PRODUCT NAME - tilapia
VARIANT = tilapia
HW VERSION - PR
BOOTLOADER VERSION - 4.13
BASEBAND VERSION - 1231_0.18.0_0409
SERIAL NUMBER - 015d88ffa8540a1c
SIGNING - not defined yet
LOCK STATE - UNLOCKED
During the flash boot to stock it wiped all directories etc so I now have an empty tablet..
Any ideas what I can do now? I would prefer to go back to stock 4.2 if possible... but if not, any help would be nice...

filking said:
I've been having trouble with my N7 (2012) for a while now.. Ever since the 4.3 update.. Slow response, hangs, and so on.
The latest 4.3 update would not install. Just a lying down droid with '!'.
My tablet was rooted using Wugfresh toolkit and was perfect before 4.3.
So i thought i'd go back to the start and use the toolkit to go back to root and flash stock+unroot.
Went through all instructions, it got to the part where it says ' You tablet will now reboot a few times. Please wait.'
Waited for 30 mins and nothing..
Now got a tablet with the google name and the unlock symbol. Options available are start, bootloader, recovery, off
All bring back to same screen.. Bootloader option displays -
Fastboot mode
PRODUCT NAME - tilapia
VARIANT = tilapia
HW VERSION - PR
BOOTLOADER VERSION - 4.13
BASEBAND VERSION - 1231_0.18.0_0409
SERIAL NUMBER - 015d88ffa8540a1c
SIGNING - not defined yet
LOCK STATE - UNLOCKED
During the flash boot to stock it wiped all directories etc so I now have an empty tablet..
Any ideas what I can do now? I would prefer to go back to stock 4.2 if possible... but if not, any help would be nice...
Click to expand...
Click to collapse
Hi, filking...
I have no experience with toolkits, so I can only advise you to download the Factory Image for your 'tilapia'/'nakasig' Nexus 7, and fastboot flash it.
Using fastboot isn't that difficult, and I'm at a loss to understand why toolkits have become so popular, when fastboot is so easy to use. Maybe people don't like command line interfaces...??
Anyway, there's a thread here which explains it all in detail.
Good luck.
Rgrds,
Ged.

Hi, thanks for the reply.
I think, in the world it is now, everyone is used to menus/mouse clicks to perform functions.
Anyway, I have read that thread already and my problem is when I get to the commands. All 'adb' commands don't work.
'adb devices' shows nothing.
I've tried in bootloader mode and recovery mode... All show a droid lying down. Fastboot mode shows the above message. Rest show, 'boot failed'
Help.....

filking said:
Hi, thanks for the reply.
I think, in the world it is now, everyone is used to menus/mouse clicks to perform functions.
Anyway, I have read that thread already and my problem is when I get to the commands. All 'adb' commands don't work.
'adb devices' shows nothing.
I've tried in bootloader mode and recovery mode... All show a droid lying down. Fastboot mode shows the above message. Rest show, 'boot failed'
Help.....
Click to expand...
Click to collapse
You don't need ADB to flash a stock image. ADB only works with a fully booted Android tablet. Indeed, if you have no bootable OS on your tablet, ADB is redundant and will not work.
You need to use fastboot...
What do you see when you type fastboot devices? (whilst the N7 is booted into the bootloader).
Rgrds,
Ged.

An update....
I went through wugs full driver setup part and deleted existing drivers. Installed the drivers again...
The device is detected on my PC.. But, seeing as it is stuck on the bootloader screen and I can't get into the system to turn on debugging, no adb commands work.
Device is listed as an 'unknown' android device when plugged in..
Seen a few other posts similar, but a lot say, 'it's ok, i've fixed it' without saying how.
anyone?

sorry, our posts must've been at same time..
Fastboot devices shows
015d88ffa8540a0c fastboot
*EDIT* Looks like i've misread the instructions in the post linked to above...
It got to the part where is said 'type in adb devices'... I read that, it didn't work, and I stopped.
BUT, I was already in bootloader mode, so didn't need that bit..
My error. (it's been a hot day!!! is that a good enough excuse.)
Continuing with the fastboot commands now... I'll update how it goes..
Thanks for replies.....

Update. All resolved.
I tried with the 4.3 img, but for some reason, it went through all the steps correctly. fastboot reboot resulted in the bootloader screen again.
Weird I thought, so I downloaded the 4.2.2 img and tried that and it worked perfectly..
Many thanks all who did, and it's a reminder to all. Re-read instructions..
:highfive::good:

Help: Fastboot Not Receiving Files

Wanting to go back to a factory image on my Nexus 10 so that I can take the update for Android 4.4. Being the lazy guy that I am, I tried to take the easy way out and used the WugFresh tool to go back to the factory image and unroot. It didn't work. Now I have no recovery or system so I can only boot into the bootloader. When I try and flash a new bootloader the command prompt just sits on "sending boot" and never gets there. I am noticing that on the Nexus when I initiate the command a cyan colored box comes up that says "FASTBOOT STATUS - DATA00140000" Sometimes the numbers after the data part are different but that's it. I'm not sure how to fix it because I can't send files to it. Any help would be appreciated.
EDIT: completely uninstalled and reinstalled (for the second time) adb, fastboot, and universal drivers and then rebooted my machine Nexus started connecting just fine.

jcrss13 said:
Wanting to go back to a factory image on my Nexus 10 so that I can take the update for Android 4.4. Being the lazy guy that I am, I tried to take the easy way out and used the WugFresh tool to go back to the factory image and unroot. It didn't work. Now I have no recovery or system so I can only boot into the bootloader. When I try and flash a new bootloader the command prompt just sits on "sending boot" and never gets there. I am noticing that on the Nexus when I initiate the command a cyan colored box comes up that says "FASTBOOT STATUS - DATA00140000" Sometimes the numbers after the data part are different but that's it. I'm not sure how to fix it because I can't send files to it. Any help would be appreciated.
EDIT: completely uninstalled and reinstalled (for the second time) adb, fastboot, and universal drivers and then rebooted my machine Nexus started connecting just fine.
Click to expand...
Click to collapse
I the same happens but with Android L. and you say you fix reinstalling drivers?

[Q] Update to 4.4 brick

Hello, after updating my Nexus 7 (Wi-FI) via OTA my nexus wouldn't turn on... it just got stuck on the nexus logo.
I tried wiping, flashing the OTA via sideload, also tried flashing the factory image also via sideload, but I kept getting an error (error 7 I think).
After that, I used the fastboot update image-nakasi-krt16s.zip but it got stuck on sending system < 611886 KB >.
I don't know what else to do, any help would be appreciated!

Same problem here. I'm running a pure stock. In rooted device and it bricked on me.
Sent from my SGH-M919 using XDA Premium 4 mobile app

theblackout said:
Hello, after updating my Nexus 7 (Wi-FI) via OTA my nexus wouldn't turn on... it just got stuck on the nexus logo.
I tried wiping, flashing the OTA via sideload, also tried flashing the factory image also via sideload, but I kept getting an error (error 7 I think).
After that, I used the fastboot update image-nakasi-krt16s.zip but it got stuck on sending system < 611886 KB >.
I don't know what else to do, any help would be appreciated!
Click to expand...
Click to collapse
Speaking of getting stuck with the "sending system" process, It was also mentioned in this thread.
It seems that you could go back to 4.3 by flashing factory images and flash 4.4 factory image again, then you are good to go.
Just for you information.

noradoor said:
Speaking of getting stuck with the "sending system" process, It was also mentioned in this thread.
It seems that you could go back to 4.3 by flashing factory images and flash 4.4 factory image again, then you are good to go.
Just for you information.
Click to expand...
Click to collapse
Same thing using that thread, I.
fastboot erase system
fastboot flash system system.img (old 4.3 img)
stuck on sending system <529061 KB>
getting nervous here, any other ideas?

OK, I finally got it back to life!
I fastboot cwm recovery, then adb sideload this rom: http://forum.xda-developers.com/showthread.php?t=2222374
That should do it

theblackout said:
OK, I finally got it back to life!
I fastboot cwm recovery, then adb sideload this rom: http://forum.xda-developers.com/showthread.php?t=2222374
That should do it
Click to expand...
Click to collapse
I will try this when i get home from work and see how it goes.

Ksealy03 said:
I will try this when i get home from work and see how it goes.
Click to expand...
Click to collapse
Hi, Ksealy03...
Erm... but before you do that... Whilst fastboot flashing stock Android 4.4 (KitKat), you might want to try changing the USB cable that connects your Nexus 7 to your PC to a different USB port on your PC. Or, possibly even changing the USB cable completely.
The 'stuck on sending image' problem is a commonly reported one here on XDA.
Indeed, I myself don't recall NOT having the problem, whenever I fastboot flash factory stock... it's always the same, "Oh no, here we go again... still sending system image" after five minutes. It's almost predictable - I just expect it happen now.
Anyway... I then disconnect my USB cable from my PC, reboot the Nexus 7 bootloader... reconnect my USB cable TO A DIFFERENT USB PORT on the PC - and begin the flash procedure all over again... and then it works! System image goes over.
Quite why this happens, I've no idea... but I suspect it has something to do with the size of system image, 'cos everything else (recovery, etc) goes over quite happily, without problems. At some point the fastboot connection dies (times out?), and you have to re-establish it.
Rgrds,
Ged.

GedBlake said:
Hi, Ksealy03...
Erm... but before you do that... Whilst fastboot flashing stock Android 4.4 (KitKat), you might want to try changing the USB cable that connects your Nexus 7 to your PC to a different USB port on your PC. Or, possibly even changing the USB cable completely.
The 'stuck on sending image' problem is a commonly reported one here on XDA.
Indeed, I myself don't recall NOT having the problem, whenever I fastboot flash factory stock... it's always the same, "Oh no, here we go again... still sending system image" after five minutes. It's almost predictable - I just expect it happen now.
Anyway... I then disconnect my USB cable from my PC, reboot the Nexus 7 bootloader... reconnect my USB cable TO A DIFFERENT USB PORT on the PC - and begin the flash procedure all over again... and then it works! System image goes over.
Quite why this happens, I've no idea... but I suspect it has something to do with the size of system image, 'cos everything else (recovery, etc) goes over quite happily, without problems. At some point the fastboot connection dies (times out?), and you have to re-establish it.
Rgrds,
Ged.
Click to expand...
Click to collapse
Ok im actually trying it now. i have a different USB cable that I will use.

teraonic 318
No luck. because my debugger is not on I can t do anything. ADB and fastboot wont even recognize the device. probably just call up Asus.

Ksealy03 said:
No luck. because my debugger is not on I can t do anything. ADB and fastboot wont even recognize the device. probably just call up Asus.
Click to expand...
Click to collapse
I had a similar issue that I was able to fix. Hopefully this will help you too.
I have a Nexus 7 that is rooted, stock ROM, unlocked bootloader. I have gotten many OTA updates since buying the device, and all previous OTA updates have completed without a hitch.
On the most recent OTA Kit Kat update, the device froze when trying to apply the update. It just displayed the boot animation in perpetuity.
I was able to use the Nexus Toolkit here on XDA (LINK) to load the stock Kit Kat ROM. Hope that helps.

Nexus 7 "Soft Bricked", in never-ending Boot Loop, need help in simple terms

Nexus 7 "Soft Bricked", in never-ending Boot Loop, need help in simple terms
I have a Un-Rooted Nexus 7 2012 32GB (bought new in Nov 2013) that suddenly and for no reason "soft-bricked", stuck in a never-ending
Boot Loop (swirling/spinning 4 color circles). I still had Android
4.4.4 running on it, except for the typical slacker stock Launcher
hangs and not responding, it was running pretty good.
I have tried a few time to do a "factory reset" from the Recovery Menu
(Pwr & Volumn Down procedure) and nothing, also tried before that the
Cashe Clearing. Nothing gets it to Factory Reset, just another Boot Loop.
I have never tried a Rooting of an Android device (though I've been in
Windows and IBM Network IT engineering for 25+ years.) Can someone
help me step by step in near layman's term to restore this Nexus 7?
I'd actually rather NOT Root it for a custom ROM, just get it back to KitKat 4.4.4 (Preferred) of if I have to LolliPop 5.1 which I have experienced is the dead end for the N7's (2012 and 2013's) since my older N7 2012 8GB refuses to update to 5.1.1.
Appreciate the step by step help. If you're recommending a PC program
I need to use, please supply the link to the exact version to
download.
Thanks

Hi,
U can unlock ur nexus 7 bootloader and then flash the stock ROM using the Nexus Root Toolkit. Use this to unlock bootloader. Then on the right side ull see a flash option. Under that select bootloop and then click on flash. It should get u out of bootloop. Then relock bootloader if u want. Before using it check whether u have the proper adb drivers installed.
NRT- http://www.wugfresh.com/nrt/
U can get the stock ROM images from(if needed) - https://developers.google.com/android/images
Hit the thanks button if it helped!

How can I use Wugfresh or any PC App to access the BootLooped N7 2012 when it never starts?? It never gets past the spinning 4-color dots.
I've been to the Wugfresh site and noted that it says it's only compatible with N7 2013 models and up.
Also, where can I download the OEM pure KitKat 4.4.4 ROM?

VintageGuitarz said:
How can I use Wugfresh or any PC App to access the BootLooped N7 2012 when it never starts?? It never gets past the spinning 4-color dots.
I've been to the Wugfresh site and noted that it says it's only compatible with N7 2013 models and up.
Also, where can I download the OEM pure KitKat 4.4.4 ROM?
Click to expand...
Click to collapse
Boot into the bootloader and connect it to the PC. If u have proper drivers it will recognise it. The link I have to the NRT supports N7 2012(see ss). U can download the stock rom from the 2 link I've given.
Select nakasi for N7 2012 WiFi or depending on ur model