Develop Bugs

Bricked nexus 7 won't even charge

So I tried using the wugfresh toolkit last nigh to root since from what I've read all the nexus devices use the same method to unlock the bootloader and such. This was likely a mistake. After figuring out I had to change the device to PtP I managed to get to the unlock bootloader screen on the device, at which point it became unresponsive. I turned it off completely, and at that point it wouldn't boot at all, it would just sit on the nexus logo forever. I also couldn't fastboot, holding down the power, volume up and volume down buttons seemed to do nothing. So I let it run down last night in hopes of starting on a fresh charge. Now the device doesn't seem to want to charge at all. I plugged it into both my computer and wall charger through the usual usb cable, and the screen isn't showing any indication of charging. All I saw was the notification light blinking in short bursts after initially plugging it in, and now not even that is happening.
Ideas?

Reboot to recovery and wipe dalvik, cache and system and reboot
Sent from my Nexus 7 using xda premium

Simer03 said:
Reboot to recovery and wipe dalvik, cache and system and reboot
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
If you wipe system, what exactly are you expecting to reboot into???

je
Simer03 said:
Reboot to recovery and wipe dalvik, cache and system and reboot
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Exactly....I can't reboot into recovery because I can't fastboot into anything. I'm not sure how this helps.

destructobob said:
Exactly....I can't reboot into recovery because I can't fastboot into anything. I'm not sure how this helps.
Click to expand...
Click to collapse
A few points.
First, this is why I highly discourage 'toolkits', especially on Nexus devices. There simply is no reason to use them and many reasons not. It is much wiser to learn how to do things manually, as it makes troubleshooting problems much easier and is less likely to cause a problem. For example, to unlock the bootloader, you could have issued a single command to accomplish it.
Second, as I don't use toolkits, I can't say exactly how the one you used works, but it most likely automates that 'fastboot oem unlock' command, which IS the same for both N7 versions. If so, it shouldn't have caused you any issues.
Third, assuming all you did was attempt to unlock the bootloader - and not flash any custom stuff, root the device, etc. - you should not be running into this issue. If you did try something else, that could certainly explain some of the problems you have. There is certainly a possibility that your device is defective. It it truly won't charge or function at all, I would highly recommend you return it for a new one. If it's dead, there should be no reason why they won't take it back.
Next time, I would recommend doing things the old fashioned way .

phonic said:
A few points.
First, this is why I highly discourage 'toolkits', especially on Nexus devices. There simply is no reason to use them and many reasons not. It is much wiser to learn how to do things manually, as it makes troubleshooting problems much easier and is less likely to cause a problem. For example, to unlock the bootloader, you could have issued a single command to accomplish it.
Second, as I don't use toolkits, I can't say exactly how the one you used works, but it most likely automates that 'fastboot oem unlock' command, which IS the same for both N7 versions. If so, it shouldn't have caused you any issues.
Third, assuming all you did was attempt to unlock the bootloader - and not flash any custom stuff, root the device, etc. - you should not be running into this issue. If you did try something else, that could certainly explain some of the problems you have. There is certainly a possibility that your device is defective. It it truly won't charge or function at all, I would highly recommend you return it for a new one. If it's dead, there should be no reason why they won't take it back.
Next time, I would recommend doing things the old fashioned way .
Click to expand...
Click to collapse
It turns on, it's on at the moment actually. It's been sitting at the nexus logo for about ten minutes. And I still can't load into fastboot, holding down those three buttons does nothing. I'm not even sure why the device froze at the unlock screen. I'm trying to start up the old fashioned way right now, following this link http://forum.xda-developers.com/showthread.php?t=2379618
I've managed to make my way to the platform tools folder in a command line, but running the reboot bootloader command there does nothing. It simply says device not found. I don't think my computer is even seeing the n7 properly so it can't reboot it. I don't think its defective, but I don't know where to begin to fix this using the old fashioned way either....

phonic said:
A few points.
First, this is why I highly discourage 'toolkits', especially on Nexus devices. There simply is no reason to use them and many reasons not. It is much wiser to learn how to do things manually, as it makes troubleshooting problems much easier and is less likely to cause a problem. For example, to unlock the bootloader, you could have issued a single command to accomplish it.
Second, as I don't use toolkits, I can't say exactly how the one you used works, but it most likely automates that 'fastboot oem unlock' command, which IS the same for both N7 versions. If so, it shouldn't have caused you any issues.
Third, assuming all you did was attempt to unlock the bootloader - and not flash any custom stuff, root the device, etc. - you should not be running into this issue. If you did try something else, that could certainly explain some of the problems you have. There is certainly a possibility that your device is defective. It it truly won't charge or function at all, I would highly recommend you return it for a new one. If it's dead, there should be no reason why they won't take it back.
Next time, I would recommend doing things the old fashioned way .
Click to expand...
Click to collapse
I second all that's been said here. While toolkits can seem attractive, it's really quite simple, and much safer to do it manually once your take an hour to learn your way around the Android-SDK (way easier than it sounds, I promise).

I like toolkits, seriously, but they hardly ever work. I usually have to drop to a shell prompt and run the commands manually anyway.
Sent from Nexus 7 XHD using XDA Premium HD

destructobob said:
It turns on, it's on at the moment actually. It's been sitting at the nexus logo for about ten minutes. And I still can't load into fastboot, holding down those three buttons does nothing. I'm not even sure why the device froze at the unlock screen. I'm trying to start up the old fashioned way right now, following this link http://forum.xda-developers.com/showthread.php?t=2379618
I've managed to make my way to the platform tools folder in a command line, but running the reboot bootloader command there does nothing. It simply says device not found. I don't think my computer is even seeing the n7 properly so it can't reboot it. I don't think its defective, but I don't know where to begin to fix this using the old fashioned way either....
Click to expand...
Click to collapse
To get into bootloader mode, you hold down POWER+VOLDOWN - not all three buttons. Make sure you turn off your device first (hold down power until it shuts off), then hold down those two buttons.
If it gets to the nexus logo, that means your bootloader should be OK, which means you can probably recover.
The 'adb reboot bootloader' command will not work until the device is booted up, your turned on developer mode and USB debugging, and you allowed your computer to connect.
Assuming you can get into bootloader, look to see if you did successfully unlock it or not. If you didn't, try the 'fastboot oem unlock' command.
If you continue to be unable to boot normally, you will likely need to flash the system image. There is one floating around here (system.img). You can do this in the bootloader as well (fastboot flash system system.img).

hadisious said:
I second all that's been said here. While toolkits can seem attractive, it's really quite simple, and much safer to do it manually once your take an hour to learn your way around the Android-SDK (way easier than it sounds, I promise).
Click to expand...
Click to collapse
I understand that and have absolutely learned my lesson. What's confusing me at the moment is installing the drivers listed in the link I posted. All that's there is a zip file, no exe or anything which is what I'm used to for installers. I was able to reboot my nexus 7 into bootloader before with the toolkit, so I know I had the drivers installed properly at some point. The toolkit installed a universal ADB set which I'm thinking should work. I don't know what to do to get the device into bootloader to follow the instructions.

phonic said:
To get into bootloader mode, you hold down POWER+VOLDOWN - not all three buttons. Make sure you turn off your device first (hold down power until it shuts off), then hold down those two buttons.
If it gets to the nexus logo, that means your bootloader should be OK, which means you can probably recover.
The 'adb reboot bootloader' command will not work until the device is booted up, your turned on developer mode and USB debugging, and you allowed your computer to connect.
Assuming you can get into bootloader, look to see if you did successfully unlock it or not. If you didn't, try the 'fastboot oem unlock' command.
If you continue to be unable to boot normally, you will likely need to flash the system image. There is one floating around here (system.img). You can do this in the bootloader as well (fastboot flash system system.img).
Click to expand...
Click to collapse
So I'm able to get into the bootloader, but its not responding to the command line entries. My computer brings a popup anytime the nexus tries to do a regular boot, where it just sits at the logo. The popup explains that the device is unrecognized. I've uninstalled any devices that resemble the nexus in device manager, and have tried repeatedly to update the driver manually by pointing it to the usb driver folder within the sdk. Doing that simply says windows is unable to locate the correct driver. So I think my device is where it needs to be, I just can't connect to it from the command line at the moment.

First of all, what made you try the toolkit(effective as it is) on the new Nexus...? Couldn't you just sit down for a day or two enjoying stock experience(abominative as it is)...?

alicarbovader said:
First of all, what made you try the toolkit(effective as it is) on the new Nexus...? Couldn't you just sit down for a day or two enjoying stock experience(abominative as it is)...?
Click to expand...
Click to collapse
Unlocking the bootloader will always result in your device getting wiped.
So it makes sense that you do this first, this way you don't need to setup your device twice.
It also has nothing to do with stock vs custom. I have an unlocked bootloader, custom recovery and am rooted. But my device is still completely stock as far as the OS goes. The only thing I might change in the future is a custom kernel, as I am usually fine with things 'stock' from a user perspective on Nexus.

phonic said:
Unlocking the bootloader will always result in your device getting wiped.
So it makes sense that you do this first, this way you don't need to setup your device twice.
It also has nothing to do with stock vs custom. I have an unlocked bootloader, custom recovery and am rooted. But my device is still completely stock as far as the OS goes. The only thing I might change in the future is a custom kernel, as I am usually fine with things 'stock' from a user perspective on Nexus.
Click to expand...
Click to collapse
Honestly I had completely forgot that the initial unlocking does the factory reset. I got caught up in booting up the device and installing a few apps to try it out, to the point that I completely blanked on the reset haha.
I tried a bunch of different roms and verions on my gnexus and old N7, jumping between CM and PA mostly, and I got used to just having a backup ready and not worrying about a data wipe. I've mostly stuck with PA because the pie controls are fantastic on both devices and I've come to get used to the added screen space. I'm perfectly fine with the stock experience outside of pie controls, but I do love customizing my device and the custom roms allow for so much freedom in that regard.

destructobob said:
I understand that and have absolutely learned my lesson. What's confusing me at the moment is installing the drivers listed in the link I posted. All that's there is a zip file, no exe or anything which is what I'm used to for installers. I was able to reboot my nexus 7 into bootloader before with the toolkit, so I know I had the drivers installed properly at some point. The toolkit installed a universal ADB set which I'm thinking should work. I don't know what to do to get the device into bootloader to follow the instructions.
Click to expand...
Click to collapse
Okay... so its a zip file.... go to device manager and it should show you some android driver or nexus 7 or something.... right-click on that and choose update drivers... choose manual method and select the folder hat you unzipped...
then use fastboot to flash factory image...
Q: is factory image for nexus 4 2013 available
??

shengovind said:
Okay... so its a zip file.... go to device manager and it should show you some android driver or nexus 7 or something.... right-click on that and choose update drivers... choose manual method and select the folder hat you unzipped...
then use fastboot to flash factory image...
Q: is factory image for nexus 4 2013 available
??
Click to expand...
Click to collapse
I actually got it successfully up and running, unlocked and rooted and everything. The screen and dual speakers alone justify the price for sure, and the speed difference is noticeable. Riptide 2 seems to run alot smoother on this than my old N7. I'm also aware that in general a clean install runs better than something that's been used for a while, so perhaps that's part of my percieved performance gains. In any case I'm more than happy with my purchase, and am looking forward to getting my chromecast tomorrow!

destructobob said:
I actually got it successfully up and running, unlocked and rooted and everything. The screen and dual speakers alone justify the price for sure, and the speed difference is noticeable. Riptide 2 seems to run alot smoother on this than my old N7. I'm also aware that in general a clean install runs better than something that's been used for a while, so perhaps that's part of my percieved performance gains. In any case I'm more than happy with my purchase, and am looking forward to getting my chromecast tomorrow!
Click to expand...
Click to collapse
:good::good::good:

phonic said:
Unlocking the bootloader will always result in your device getting wiped.
So it makes sense that you do this first, this way you don't need to setup your device twice.
It also has nothing to do with stock vs custom. I have an unlocked bootloader, custom recovery and am rooted. But my device is still completely stock as far as the OS goes. The only thing I might change in the future is a custom kernel, as I am usually fine with things 'stock' from a user perspective on Nexus.
Click to expand...
Click to collapse
Yes but you should've waited for a suitable toolkit.

alicarbovader said:
Yes but you should've waited for a suitable toolkit.
Click to expand...
Click to collapse
Why would I wait for a toolkit?
This is a Nexus device. You don't need a toolkit. All you need is two brain cells and a willingness to learn. You can unlock, flash custom recovery and root in a matter of minutes with nothing other than the Android SDK. Toolkits cause more problems than they solve.

phonic said:
Why would I wait for a toolkit?
This is a Nexus device. You don't need a toolkit. All you need is two brain cells and a willingness to learn. You can unlock, flash custom recovery and root in a matter of minutes with nothing other than the Android SDK. Toolkits cause more problems than they solve.
Click to expand...
Click to collapse
ok, not a toolkit.. I give you that, but was the stock experience too intimidating...?
personally, i'd nuked htc sense when i got thoroughly bored with its great buttery ui. i like the aosp experience, rooted or not.
and i didn't know that we don:t need toolkits fpr nexus devices, cuz i've never happened to own one.

[Q] Nexus 7 (2013) 4.4 KRT16S Touch Screen Dead

Hello
Today Morning I got an Adroid 4.4 OTA 253.1 MB update for my Nexus 7(2013) WIFI version. My current Build was JWR66N.
The updation was succesful and Tablet was running Properly without any issues..... Then Suddenly after 4-5 Hours all the problems started
1)Screen Partially Unresponsive
2)Not Recognizing the swipe and touch
3)Icons not getting Selected
..AND NOW
4)The Screen is completely UNRESPONSIVE !!!
The tab is working fine... i mean its showing notifications etc... But The screen is unresposive and i cannot even use the Lock Sreen
Please Help !!!!!!!

red_ferrari007 said:
Hello
Today Morning I got an Adroid 4.4 OTA 253.1 MB update for my Nexus 7(2013) WIFI version. My current Build was JWR66N.
The updation was succesful and Tablet was running Properly without any issues..... Then Suddenly after 4-5 Hours all the problems started
1)Screen Partially Unresponsive
2)Not Recognizing the swipe and touch
3)Icons not getting Selected
..AND NOW
4)The Screen is completely UNRESPONSIVE !!!
The tab is working fine... i mean its showing notifications etc... But The screen is unresposive and i cannot even use the Lock Sreen
Please Help !!!!!!!
Click to expand...
Click to collapse
Was your tablet rooted to begin with? If so were you running stock or a custom rom?
If it wasn't, you might wanna try unlocking the bootloader and flashing the stock image from Google using adb and fastboot. The relocking your boot loader.
Let me know if you Dont know how to do that. Hope that helps.
Sent from my Nexus 5 using Tapatalk

Help
frarredo said:
Was your tablet rooted to begin with? If so were you running stock or a custom rom?
If it wasn't, you might wanna try unlocking the bootloader and flashing the stock image from Google using adb and fastboot. The relocking your boot loader.
Let me know if you Dont know how to do that. Hope that helps.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
It was a Stock ROM 4.3 JWR66N... I had not done any modification or rooting whatsoever
I dont even now how to flash or unlock bootloader....
It was untouched in terms of modifications since the day I bought...
I got an normal OTA update as i mentioned... First 3-4 hrs awesome ... Then all went south... touch screen partially unresponsive and now completely Un responsive.. The tablet is working Fine

red_ferrari007 said:
It was a Stock ROM 4.3 JWR66N... I had not done any modification or rooting whatsoever
I dont even now how to flash or unlock bootloader....
It was untouched in terms of modifications since the day I bought...
I got an normal OTA update as i mentioned... First 3-4 hrs awesome ... Then all went south... touch screen partially unresponsive and now completely Un responsive.. The tablet is working Fine
Click to expand...
Click to collapse
Before I go on I'm assuming you didn't drop it or got it wet or anything like that.
Now, if you have warranty. I would do a factory data reset. And if your issues are still persisting then call Google support and request a new one.
If you DONT have warranty left, then
I think you should just unlock 5he boot loader, and flash the 4.4 kk stock image, then look for the ota update again, install it and see if your issues disappears. If they do then you can either go for root =] or relock the boot loader and stay bone stock.
The are tons of greats guides for rooting/flashing stock images online and in these forums. Just pick one and follow it.
If you have a Mac I could write one up for you once I ge5 back from work/school around 1p (pacific). Just lmk
Good luck!
Sent from my Nexus 5 using Tapatalk

frarredo said:
Before I go on I'm assuming you didn't drop it or got it wet or anything like that.
Now, if you have warranty. I would do a factory data reset. And if your issues are still persisting then call Google support and request a new one.
If you DONT have warranty left, then
I think you should just unlock 5he boot loader, and flash the 4.4 kk stock image, then look for the ota update again, install it and see if your issues disappears. If they do then you can either go for root =] or relock the boot loader and stay bone stock.
The are tons of greats guides for rooting/flashing stock images online and in these forums. Just pick one and follow it.
If you have a Mac I could write one up for you once I ge5 back from work/school around 1p (pacific). Just lmk
Good luck!
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Let me clear out some points
1) I did not drop
2) i Did not make it wet
3) Till today morning it worked perfectly fine.... then update came.... update successful.... again worked fine for 5 hrs... then all went south... touch screen unresposive...
4) I cannot get past even the lock screen
QUESTIONS
1) To flash stock rom i would require to Enable USB Debugging rite ?
How can i do that... I have no access to tablet
2) Can i flash i mean use the menus required for flashing when my entire screen is unresponsive
3) Should i flash Factory 4.4 Or stable version of 4.3 ie. JSS15R ???
I have a Windows PC

red_ferrari007 said:
Let me clear out some points
1) I did not drop
2) i Did not make it wet
3) Till today morning it worked perfectly fine.... then update came.... update successful.... again worked fine for 5 hrs... then all went south... touch screen unresposive...
4) I cannot get past even the lock screen
QUESTIONS
1) To flash stock rom i would require to Enable USB Debugging rite ?
How can i do that... I have no access to tablet
2) Can i flash i mean use the menus required for flashing when my entire screen is unresponsive
3) Should i flash Factory 4.4 Or stable version of 4.3 ie. JSS15R ???
I have a Windows PC
Click to expand...
Click to collapse
Okay let's do this step by step:
Do you have warranty on your tablet? If yes, then I would call Google support and explain to them the issue.
Question Answers:
1) you are right to use adb you would need to enable USB debugging as far as I know. What I would try is boot into fasstboot by powering it off. Then hold the power button and vol down key for about 12 secs. Then use fastboot to unlock the bootloader that should "basically" do a factory data reset since It will wipe all your user data.
2) if you install a custom recovery like twrp, that's not the touch on, I want to say yes. Because you can use the hardware keys to navagate through it.
3) I would flash factory 4.4 because its stock from Google it is stable. But you can do either or see if it makes a difference.
Now, I've seen around on these forums other people complain about getting defective tablets that have touch screen issue, although I Dont think I have heard of one as severe as yours yet. It could be that you have a defective unit, which is why I strongly suggest to use your warranty if you still have it. Google is pretty good about replacing devices, and there devices are know for having defects. I had a new nexus 5 with a defective screen called Google and got a new one within a week. They even let me use the defective one meanwhile until I got the new unit!
Sent from my Nexus 5 using Tapatalk

Flashing Help
frarredo said:
Okay let's do this step by step:
Do you have warranty on your tablet? If yes, then I would call Google support and explain to them the issue.
Question Answers:
1) you are right to use adb you would need to enable USB debugging as far as I know. What I would try is boot into fasstboot by powering it off. Then hold the power button and vol down key for about 12 secs. Then use fastboot to unlock the bootloader that should "basically" do a factory data reset since It will wipe all your user data.
2) if you install a custom recovery like twrp, that's not the touch on, I want to say yes. Because you can use the hardware keys to navagate through it.
3) I would flash factory 4.4 because its stock from Google it is stable. But you can do either or see if it makes a difference.
Now, I've seen around on these forums other people complain about getting defective tablets that have touch screen issue, although I Dont think I have heard of one as severe as yours yet. It could be that you have a defective unit, which is why I strongly suggest to use your warranty if you still have it. Google is pretty good about replacing devices, and there devices are know for having defects. I had a new nexus 5 with a defective screen called Google and got a new one within a week. They even let me use the defective one meanwhile until I got the new unit!
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Ok i am getting what you are saying...
See....
1) My tablet has been working perfectly for for about 2 months now when it was running Android 4.3 JWR66N.
So i dont think its an hardware issue because i certainly would have faced some problem in whole 60 days !!!
2) The fact that it has started showing some issues... only since past 2 hours and that too immediately after the 4.4 OTA makes me believe that its an software issue...
3) Warranty thing is out of question... Dont ask Why
SO now can you provide a way for me to solve my problem.... will unlocking bootloader as u said erase all data and solve the problem ???
Also to flash stock rom...I will revert back to 4.3... JSS15R
But the question is how can i enable USB Debugging ??? as my touchscreen is completely dead i Mean i can see the wall paper but its unresponsive
Thanks

red_ferrari007 said:
Ok i am getting what you are saying...
See....
1) My tablet has been working perfectly for for about 2 months now when it was running Android 4.3 JWR66N.
So i dont think its an hardware issue because i certainly would have faced some problem in whole 60 days !!!
2) The fact that it has started showing some issues... only since past 2 hours and that too immediately after the 4.4 OTA makes me believe that its an software issue...
3) Warranty thing is out of question... Dont ask Why
SO now can you provide a way for me to solve my problem.... will unlocking bootloader as u said erase all data and solve the problem ???
Also to flash stock rom...I will revert back to 4.3... JSS15R
But the question is how can i enable USB Debugging ??? as my touchscreen is completely dead i Mean i can see the wall paper but its unresponsive
Thanks
Click to expand...
Click to collapse
I can't say for sure that unlocking the bootloader will solve your issue but it will for sure wipe your device. I would recommend creating a back up, but since you can't enable USB debugging to create a backup using adb, you are most likely going to need to be okay with losing all your data first.
As far as I know, I Dont know of any way to enable USB debugging without going into settings first. =\
Check the forums?
I'm at work right now, and I'm also not familiar with the process on a PC. I know how to do it on a mac, since that's what I use and am familiar with. I know that for windows its a very similar process but there are some device specific drivers that you must download and install on your machine before hand.
Without a computer in front of me right now ( I'm at work ) I can't tell you exactly what to do for a PC
Look online there are tons of guides also check you tube.
I should be free later around 2 or 3pm ( pacific ) and if you can't figure it out and would still like to my help. Id be happy to help you then.
Sent from my Nexus 5 using Tapatalk

red_ferrari007 said:
Hello
Today Morning I got an Adroid 4.4 OTA 253.1 MB update for my Nexus 7(2013) WIFI version. My current Build was JWR66N.
The updation was succesful and Tablet was running Properly without any issues..... Then Suddenly after 4-5 Hours all the problems started
1)Screen Partially Unresponsive
2)Not Recognizing the swipe and touch
3)Icons not getting Selected
..AND NOW
4)The Screen is completely UNRESPONSIVE !!!
The tab is working fine... i mean its showing notifications etc... But The screen is unresposive and i cannot even use the Lock Sreen
Please Help !!!!!!!
Click to expand...
Click to collapse
Since rebooting doesn't work (from your PM) I'd suggest flashing JSS15R.
Reading the above posts, it seems your bootloader is not unlocked.
I'm concerned in your current state of mind it isn't good to do things like unlocking the bootloader or flashing stock images as you might make things worse.
First take a few hours off and think about whether you want to try and fix this yourself or just RMA the unit.
It is possible you might be able to fix this yourself but it is also possible you might mess things up even more.
Is there any data on the unit you really need?

i am ready !!!
sfhub said:
Since rebooting doesn't work (from your PM) I'd suggest flashing JSS15R.
Reading the above posts, it seems your bootloader is not unlocked.
I'm concerned in your current state of mind it isn't good to do things like unlocking the bootloader or flashing stock images as you might make things worse.
First take a few hours off and think about whether you want to try and fix this yourself or just RMA the unit.
It is possible you might be able to fix this yourself but it is also possible you might mess things up even more.
Is there any data on the unit you really need?
Click to expand...
Click to collapse
No problems...
I have calmed myself... Bring It On !! i am ready to do whatever you say... warranty and rma is not an option
Start telling me what to do I am Ready !!!

red_ferrari007 said:
No problems...
I have calmed myself... Bring It On !! i am ready to do whatever you say... warranty and rma is not an option
Start telling me what to do I am Ready !!!
Click to expand...
Click to collapse
First step, do you have the USB drivers from google installed? If not download/install from here:
http://developer.android.com/sdk/win-usb.html
Then boot into bootloader (Press/Hold Power+VolDown until bootloader menu comes up)
Then download and unzip this file on your PC
http://forum.xda-developers.com/attachment.php?attachmentid=2405103&d=1384987176
Connect your tablet to the PC via USB cable.
Open up command prompt
Go into the razors-krt16s directory from the unzipping of above file.
type in command line
fastboot oem unlock
follow the directions on the screen. You need to use volup to select yes, and Power to accept.
it will proceed to wipe your user data.
post back when you are done.

i am ready !!!
i am ready...
please guide me with in built steps
I have android SDK ready
I have downloaded Stock Image of JSS15R
Installed USB drivers
DID a Hard Reset

red_ferrari007 said:
i am ready...
please guide me with in built steps
I have android SDK ready
I have downloaded Stock Image of JSS15R
Installed USB drivers
DID a Hard Reset
Click to expand...
Click to collapse
Have you unlocked the bootloader?
---------- Post added at 10:27 AM ---------- Previous post was at 10:22 AM ----------
If you have unlocked the bootloader, follow the directions in this post to flash JSS15J
http://forum.xda-developers.com/showthread.php?p=44888268#post44888268
I am suggesting JSS15J instead of JSS15R because it is the closest factory image to JWR66N that you can get.

DONE !!!
i think its done
the LOCK STATE: UNLOCKED is shown

which u recommend ?
Should I proceed with JSS15J ???

red_ferrari007 said:
Should I proceed with JSS15J ???
Click to expand...
Click to collapse
yes.
Instructions in above post.

ok the file is downloading 10 mins left..
Just had a doubt... To unlock bootloader there is separate files for each version ???

red_ferrari007 said:
ok the file is downloading 10 mins left..
Just had a doubt... To unlock bootloader there is separate files for each version ???
Click to expand...
Click to collapse
No, unlocking the bootloader is the same for all versions. I just pointed you to that addon file because it happened to have the fastboot executable and I had the link handy. The only files that change between the addon files I'm pointing you to is the script (.bat file) that flashes the factory images because the filenames from google are different for every version.
The fastboot executable is the same for all of them.

Last doubt
sfhub said:
No, unlocking the bootloader is the same for all versions. I just pointed you to that addon file because it happened to have the fastboot executable and I had the link handy. The only files that change between the addon files I'm pointing you to is the script (.bat file) that flashes the factory images because the filenames from google are different for every version.
The fastboot executable is the same for all of them.
Click to expand...
Click to collapse
Just one doubt before proceeding
From ur link i downloaded JSS15J stock image
ur guide also mentions to download an addon zip file correct ? but its name is JSS1Q addon,zip
So is it correct ???

I need to extract that addon file to that extracted ? STOCK image file rite ?

[Q] Nexuz 7 stuck at the google logo

Hello I need a but of help my Nexus 7 is showing my nothing but the google logo and at the store earlier it showed the android with his chest up and a red triangle. it doesnt even show the moving colors after i turn it on it just sits and says google like a paper weight. i can turn it off and on but nothing more. the geek squad at best buy told me to ask for help here at Xda. last thing i was doing with it was opening deer hunter 2013 and next i go to see if it opened and it stuck on the google logo. can anyone help me fix my tablet? its not under store warranty only manufactures.

Well, sucks to be you.....just kidding...but that does suck. Now, on to more serious matters...
Do you have access to your bootloader? (hold the power button + the vol up button at the same time) If you do, you might want to look into rooting the tablet. Based on the content of your post, I am assuming that you haven't. There is plenty information about rooting the Nexus 7.2 tablet (and just about every other Android device). Simply Google "root Nexus 7 2013" and you will quickly find your answer.
Also, how much do you know about rooting and the sort? I want to know before I waste my time giving details about info that you are aware of.

aarsyl said:
Well, sucks to be you.....just kidding...but that does suck. Now, on to more serious matters...
Do you have access to your bootloader? (hold the power button + the vol up button at the same time) If you do, you might want to look into rooting the tablet. Based on the content of your post, I am assuming that you haven't. There is plenty information about rooting the Nexus 7.2 tablet (and just about every other Android device). Simply Google "root Nexus 7 2013" and you will quickly find your answer.
Also, how much do you know about rooting and the sort? I want to know before I waste my time giving details about info that you are aware of.
Click to expand...
Click to collapse
i dont know anything about rooting. i dont have access to the boot loader. i did a few days ago now it wont even show up, the guy and best buy tried to bring it up and its like it was showing a dead android or something chest open with a red triangle above it. he said someting about maybe have to flash a new or or something like that on to it, it wont show me anything just stays off or shows the google logo when its on

Sigh...that is the bootloader. Maybe...he could have booted into the stock recovery, which shows this or something similar for most devices. Please remember, they are reps...they may know about the software, but usually they speak from their experience or their perspective. I'm glad that he sent you here for a second opinion.
Hold the volume down button and power button to get into the bootloader. You should see some options at the top of the screen saying Start, Restart bootloader, Recovery Mode, Power Off. Not sure if those are the exact options, but it's pretty close.
Also, you need to look into rooting your device. You need to download some files first. You'll need adb, fastboot, and drivers for your Nexus.
And one last thing....what Computer OS do you use? The rooting process is slightly different for each one (Windows 7, 8/8.1, Mac OS, & Linux). If you are into computers, and you have Linux installed on a device, good for you. That is my preference when rooting, as Android is built from Linux, and naturally supported without the need for drivers.

I had similar problems when I first bought it. Going into recovery and resetting the tablet cured it. You will lost all your data BTW.

He's facing the loss of his entire tablet, so I'm sure that data loss isn't the biggest thing to worry about.
But yes, just about every solution involves a clean wipe of data.
_______________________________________
Phone: HTC EVO 4G LTE
Sense 5, S-Off
Tablet: ASUS Nexus 7.2
Rooted, Custom Rom & Kernel
_______________________________________

I'm stuck on the google logo too. I had my tablet plugged in over night and when I opened the cover this morning it woke up, but as soon I tried to access anything it rebooted and stuck.
I'm unlocked and have tried various thing. NRT doesn't recognize it as an ADB device so I don't think that will work. Fastboot works, but I keep getting "FAILED (remote: flash write failure)" when I try to use the factory flash all, or the instructions found here: http://forum.xda-developers.com/showthread.php?t=2381582
I can use fastboot to query the device and get it to return "flo" but it seems like the flash storage has failed.
if it's truly horked, can I use "fastboot oem lock" to relock it and attempt a warranty replacement?

sean67854 said:
I'm stuck on the google logo too. I had my tablet plugged in over night and when I opened the cover this morning it woke up, but as soon I tried to access anything it rebooted and stuck.
I'm unlocked and have tried various thing. NRT doesn't recognize it as an ADB device so I don't think that will work. Fastboot works, but I keep getting "FAILED (remote: flash write failure)" when I try to use the factory flash all, or the instructions found here: http://forum.xda-developers.com/showthread.php?t=2381582
I can use fastboot to query the device and get it to return "flo" but it seems like the flash storage has failed.
if it's truly horked, can I use "fastboot oem lock" to relock it and attempt a warranty replacement?
Click to expand...
Click to collapse
You can try Method 2 from this post: http://forum.xda-developers.com/showthread.php?t=2513701
I know it's for the N5, but I used this one for both my Galaxy Nexus, N5 and N7. Since they are all Nexuses (Nexi?), the same general procedures apply. I always prefer to do it all manually, step-by-step, which is why I went with Method 2 in the OP of that thread. Obviously, since this is the N7, just skip the radio flashing command. Everything else is the pretty much exactly the same. If this doesn't work in fastboot, then it's probably a hardware failure.

[Q] Nexus 7 Bricked due to 4.4.3 Update?

I'm hoping someone might be able to help me recover my Nexus 7 which appears to be bricked currently. It is the 2013 version, and it was never rooted initially and was running stock firmware. (By the way, I'm not the most proficient with messing with my Android devices or even with the terminology, so I apologize in advance if I might require clarification on some of the responses).
A few days ago, I woke up to discover that somehow my home screen had reverted back to the way it was upon initially getting the device. This wasn't a big deal since I didn't lose any data or apps, but I figured something might be wrong and even posted about it on Google's product forums. Then, last night, I attempted to update to 4.4.3 because it had been prompting me to do so for a week or two. It downloaded and attempted the update, but it failed. It then eventually restarted, but upon loading up Android I got an error message that stated:
System UID's Inconsistent
UIDs on the system are inconsistent, you need to wipe your data partition or your device will be unstable
with a button to click that says "I'm Feeling Lucky" - I clicked the button figuring I could at least get back in to back up my data, but after about 30 seconds the device just rebooted again (all I managed to do was accidentally click the Chrome icon) and now it is just stuck at the initial boot-up screen displaying the Google text logo.
I have tried to hold down the volume button and hit power, and I get to a screen with 4 options I can cycle through: Recovery mode (which will just put me back the Google text logo), Power off (which turns off the device), Start (which puts me back to the Google text logo), and Restart bootloader (which brings me right back to this menu options page). I'm attaching a screenshot of this page.
I spent about an hour on the phone with Google support, but they were basically useless. I then did some research and downloaded Skipsoft Unified Android Toolkit and was able to get the device to be recognized when it was in that 4-option mode by the Skipsoft Toolkit. However, all fastboot options I tried didn't seem to succeed because the Bootloader was locked. I figured I would try to unlock it, and it told me that in doing so it would wipe my device (so be it I figured since I had already pretty much kissed my data on there goodbye at this point). However, it seems to try and wipe it (even giving me a prompt on the actual Nexus 7), but then just sits and does nothing that I can see (see attached screenshots).
Anyone have any ideas/suggestions? Thanks so much!

To be safe, with a stock device that was not rooted... I would go ahead and use the Skipsoft program to flash the stock image back on the device. This should alleviate any future issues with the OS on your device.
I believe it to be Option #9 on Skipsoft.

xbi0s said:
To be safe, with a stock device that was not rooted... I would go ahead and use the Skipsoft program to flash the stock image back on the device. This should alleviate any future issues with the OS on your device.
I believe it to be Option #9 on Skipsoft.
Click to expand...
Click to collapse
Thanks for the reply - I attempted your suggestion, but it didn't work because the Bootloader is still locked; and attempting to unlock the Bootloader seems to stall on erasing userdata.
Any other thoughts? Thanks!

Anyone else have any suggestions/ideas? Thanks!

mbressman said:
Anyone else have any suggestions/ideas? Thanks!
Click to expand...
Click to collapse
Download ADB from my signature.
Put the device in bootloader mode (power+vol down), open fastboot.exe and type fastboot oem unlock.

Aerowinder said:
Download ADB from my signature.
Put the device in bootloader mode (power+vol down), open fastboot.exe and type fastboot oem unlock.
Click to expand...
Click to collapse
When I try that, I get:
Code:
C:\Users\User\Desktop\ADB & Fastboot API 19 (19.0.1)>fastboot oem unlock
...
(bootloader) Unlocking bootloader...
(bootloader) erasing userdata...
And it just hangs there....
The Nexus 7 did prompt me whether I want to unlock the bootloader and I selected yes (with the volume and power keys), but then it just hangs at that selection screen as well...
Any ideas??
Thanks!

mbressman said:
When I try that, I get:
Code:
C:\Users\User\Desktop\ADB & Fastboot API 19 (19.0.1)>fastboot oem unlock
...
(bootloader) Unlocking bootloader...
(bootloader) erasing userdata...
And it just hangs there....
The Nexus 7 did prompt me whether I want to unlock the bootloader and I selected yes (with the volume and power keys), but then it just hangs at that selection screen as well...
Any ideas??
Thanks!
Click to expand...
Click to collapse
I changed the wrong link in my signature. The ADB link correctly points to version 19.0.2 now. Try that one. Try a different cable if you have one, try a different USB port if you can.

Aerowinder said:
I changed the wrong link in my signature. The ADB link correctly points to version 19.0.2 now. Try that one. Try a different cable if you have one, try a different USB port if you can.
Click to expand...
Click to collapse
Tried two different cables on two different USB ports with the new 19.0.2 downloads you posted - still having the same thing happen. Could it be the computer I'm using, or the drivers I installed (I used the Skipsoft Unified Android Toolkit drivers)? Or is my device just totally bricked and unrecoverable?
Thanks!

mbressman said:
Tried two different cables on two different USB ports with the new 19.0.2 downloads you posted - still having the same thing happen. Could it be the computer I'm using, or the drivers I installed (I used the Skipsoft Unified Android Toolkit drivers)? Or is my device just totally bricked and unrecoverable?
Thanks!
Click to expand...
Click to collapse
You can try different drivers. Uninstall current ones, and install the ones from my signature.

Aerowinder said:
You can try different drivers. Uninstall current ones, and install the ones from my signature.
Click to expand...
Click to collapse
Ok, so I removed the Clockworkmod ADB drivers from add/remove programs (or uninstall programs - whatever it is called now on Win7), then I went into device manager and deleted the driver for Google Nexus BootLoader Interface, and then I rebooted. After the reboot, plugging the Nexus 7 in showed no driver detected, so I downloaded your Koush Universal ADB drivers, extracted them, and used them to install the Google Nexus Bootloader Interface drivers again (that's what it detected for my Android when I pointed the device listed in device manager to the extracted folder).
I then ran "fastboot oem unlock" but it's still getting stuck at the same place: (bootloader) erasing userdata...
Anything else I can try?
Thanks!

Hi,
I have the same issue since yesterday. When I pulled my nexus from my backpack (charged 12 hours earlier) its battery was drained. After charging it nexus stucked on google screen during normal or recovery boot. Oem unlock also hangs on erasing userdata. I'm looking forward for any solution to this.
Maybe some ****ty update? I've got the LTE version.

Anyone have anything else I can try?
I'm currently working on getting ASUS to replace the device under warranty - but they want me to send it in first, and I'm concerned that while I can't access any of my data on it, the data might still be there and potentially accessible to others (and I'd prefer to not have all of my confidential data that I stored on there accessible to anyone else). Unfortunately, ASUS won't replace/repair it unless I send it in, so I'm between a rock and a hard place...
Any help or advice is greatly appreciated!
Thanks.

mbressman said:
Anyone have anything else I can try?
I'm currently working on getting ASUS to replace the device under warranty - but they want me to send it in first, and I'm concerned that while I can't access any of my data on it, the data might still be there and potentially accessible to others (and I'd prefer to not have all of my confidential data that I stored on there accessible to anyone else). Unfortunately, ASUS won't replace/repair it unless I send it in, so I'm between a rock and a hard place...
Any help or advice is greatly appreciated!
Thanks.
Click to expand...
Click to collapse
I've tried every single way to unbrick my nexus. After 2 days of searching send it for repair. Without any questions they replaced mainboard. Problem solved hard way.

Gawson said:
I've tried every single way to unbrick my nexus. After 2 days of searching send it for repair. Without any questions they replaced mainboard. Problem solved hard way.
Click to expand...
Click to collapse
Gawson - when you got it back did it still have your data on it, or was it wiped?

mbressman said:
Gawson - when you got it back did it still have your data on it, or was it wiped?
Click to expand...
Click to collapse
When I got it was wiped. Flash is on the mainboard so there was no way they could save my data. They do not migrate your personal stuff.
Now its working like new. In fact it has all new guts except battery and screen.
Only problem is that now auto brightness sensor is giving crap instead of useful data. I don't know if its hardware related or just 4.4.3 issue.

[q] hard bricked

OK,
So a friend of mine asked me to help him fix his Nexus 7 2013 FLO (WiFi only).
According to him he hasn't even unlocked the bootloader (and the info displayed while in fastboot mode confirms this). Apparently what happened, a few months ago, he downloaded an OFFICIAL KitKat OTA, clicked OK to upgrade, and since then, the tablet will not get past the screen that says Google. I can get it into fastboot mode but cannot flash anything, and when I attempted to use The Nexus Root Toolkit by WugFresh to unlock the bootloader at the very least, I can get it to display the screen that says "please use the arrow key to navigate Yes or No. Unlocking your bootloader allows you to load a custom OS, but may void your warranty, etc. etc. etc."
I tried using CMD to erase the cache and userdata and after giving it upwards of 20 minutes, during which the window (in CMD) simply said "erasing cache" and never actually made any progress whatsoever...
Any idea what (if anything) can be done?
Sound off in the comments!
Thanks a million!
Stephen Spigelman

I can't help... but am in the same boat as of last night with the 5.0 update.

Were you able to unlock the bootloader? You did say that you were able to get to the screen to unlock it. If not, i dont think much of anything can be done.

Bricked
Virgin N7 2013... No hacking... Bootloader locked... started acting weird and I attempted a system restore. It now gets stuck at the Google screen. Fastboot gets stuck at erasing userdata. I have tried multiple USB cables on Win7, OSX, and Ubuntu. Help!!!

im wondering how this happens?, I already unlocked my bootloader just cause of this.. maybe the chip just dies?

When my 2013 was stuck at the Google screen, I RMAed and they had to replace the motherboard. Unfortunately, I think this is a hardware issue.

ariesgodofwar said:
When my 2013 was stuck at the Google screen, I RMAed and they had to replace the motherboard. Unfortunately, I think this is a hardware issue.
Click to expand...
Click to collapse
Too many of us with the exact same problem after trying to to flash Lollipop. Cant believe we re all having hardware problems at the same time.

tigerdim said:
Too many of us with the exact same problem after trying to to flash Lollipop. Cant believe we re all having hardware problems at the same time.
Click to expand...
Click to collapse
Mine did not occur after flashing any firmware, but the symptom was the same in that I could get into the bootloader, attempt to flash new system images, appear as if all would be well, and then on reboot would stick at the Google screen. Not sure if folks are seeing the same thing here, but when I tried to get into Recovery from the Bootloader menu, it would reboot as if going there, but still never make it past the Google screen. It happened within 18 hours of unboxing a remanufactured N7 G2. Asus advised on the packing slip that is was a LED (Indicator) Error (whatever that is), and they they subsequently had to replace the board to fix it.
I hope it is a software issue, but not sure to tell you how to go about correcting it if you cannot flash new images via ADB or the bootloader and get it to boot successfully.

When i boot to recovery i get the TWRP startup screen but stays stuck.

Bump
bump.. any ideas?

i have the same :/

kobi_shalom said:
i have the same :/
Click to expand...
Click to collapse
Its driving me nuts.
I have found though that if I try a "Erase Boot" or similar and pull the cable after a second or so I do get a "OK" instead of being stuck with "Erasing boot..." Seems to work for Boot, Cache etc..
The problem is that when I try OEM Unlock it needs to perform 5 different erases, so pulling the cable wont work for this. I just stay stuck on "Erasing userdata...r..."

tigerdim said:
Its driving me nuts.
I have found though that if I try a "Erase Boot" or similar and pull the cable after a second or so I do get a "OK" instead of being stuck with "Erasing boot..." Seems to work for Boot, Cache etc..
The problem is that when I try OEM Unlock it needs to perform 5 different erases, so pulling the cable wont work for this. I just stay stuck on "Erasing userdata...r..."
Click to expand...
Click to collapse
So you success?

NO success because I cannot unlock the bootloader.