[Q] Is this thing completely bricked? Need some help! - Nexus 7 Q&A, Help & Troubleshooting

Ok, I've got no idea what happened, but here it goes: I think I royally screwed things up when I tried to go from 4.2 back down to PA 2.54. The install froze in twrp, so I made the mistake of holding down the power.vol buttons. Now will boot into the bootloader screen, but won't get past the Google screen on reboot, and when I try to get to recovery it stalls as well.
adb and fastboot can't find the device, although my pc does "see" it when I plug in the usb.
Here's the info on the bootloader screen:
Product Name - Grouper
Variant - Grouper
HW Version - ER3
Bootloader Version - 4.13
Baseband Version - n/a
Signing - not defined yet
lock State - unlocked
I tried using the toolkit to reload and unroot, but it can't see it.
Is this thing toast? Or is there a way to get it rolling again?
Any help MUCH appreciated!!

Strangely when the device is stuck on the teamwin screen, I can get my pc to recognize it via adb devices, It returns: --015d21d9100bec0d recovery--
I've never seen it mention recovery before, but I'm far from an expert.
Being that the bootloader still loads and the pc at least somewhat recognizes it, there's got to be some kind of solution??

Related

I could use some help with my nexus 7

I've tried to flash custom ROMs on my nexus 7, 3 times now, each time has the same result. I flash the ROM, then the Gapps and wipe data/cache. What happens afterwards is an endless boot cycle and a frozen bootloader (after rebooting into bootloader pressing up and down do nothing, neither does power button.) So i pull the battery and reboot into bootloader, now it works. This time it is a little different. Usually I can go into CMD and re flash stock, fallowing the instructions on this forum. This time when I try the command "adb reboot bootloader" I get "Failed to find device",even tho my computer recognizes it as an "Android ADB Interface." So I decided to try and re install my ADB drivers and I get "Failed to handshake device' or something along those lines.
My bootloader also reads a little differently than usual so I'll list the information below, it might be helpful.
"Product name - grouper
Variant - not defined yet
HW version - ER3
Baseband version - N/A
Signed - not defined yet
Lock state - unlocked'"
So I'm stuck with a nexus 7 in bootloader and my computer is not able to connect to it. Any help would be nice. I've already tried fallowing the returning to stock guide 3 times so please don't give me a bunch of **** about that.
Help would be nice, information/instructions would be amazing. Please help.
CptHoovsen said:
Help would be nice, information/instructions would be amazing. Please help.
Click to expand...
Click to collapse
After you boot into the boot loader, Windows sees the device name as Grouper - and there is no Windows driver for Grouper.
Try to find a Linux system to connect with. Linux is much less picky about device names.

[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:

[Q] Nexus 7 Cannot boot into recovery and cannot

Hey guys,
So I recently bought a nexus 7 32gb (first generation) and used it for about 30 minutes, then I applied what I presume was a faulty update and it has soft bricked my tablet.
Heres the scenerio,
-I cannot get my nexus 7 into usb debugging mode because it wont boot up into the actual interface and such
-Everytime I try to install the ADB drivers, the system installs it as "google nexus 7 bootloader interface"
-recovery mode will not load up, it ends up at the google screen with a text on the topright saying "booting failed"
-I'm pretty sure my bootloader is locked which could be another reason why I cant do any of the methods involving cmd, nrt, or that manual android sdk toolkit thing.
As far as I know right now (which is barely anything since I'm new to using this tablet), I can't do anything because I cannot get into usb debugging, nor can I get the tablet to read as the ADB interface / pass the full driver test in NRT.
Hopefully someone can help (Very descriptively please!) , thanks!
Sidenotes : my boot loader menus states the following...
FASTBOOT MODE
Product Name - Grouper
Variant - Grouper
HW version - ER3
Bootloader Version - 4.23
Baseband Version - N/A
Serial Number - idk if I should actually post this but im going to assume it's irrelevant for this subject
Signing - not defined yet
Lock state - Locked
Also, It was fresh out of the box, I think the tablet was updated to 4.1
bump...
anyone?!??!?!
I'm having a problem that is a little similar to yours. I have a nexus 7 2013 wifi. It won't boot up all the way it gets stuck on the X screen. Bootloader is locked and usb debugging is off. I've been trying to figure out if I can do a pull or backup over the adb sideloader.
Does your nexus have that capability?
I did come across a method that would unlock the bootloader. You need to install a nexus 7 toolkit.
I don't know if that will help you but let me dig up the link to the instructions.
If you would take the time to actually read the guides around here you would know that USB debugging is not a requirement in fast boot or recovery mode. USB debugging only applies to a booted os. Why don't you follow the guides and manually install your drivers? Use fast boot commands to flash a stock image. This isn't difficult to do. Stop messing with toolkits and learn something. You're here on XDA, utilize the resources we have.
happyfuntimes7 said:
Hey guys,
So I recently bought a nexus 7 32gb (first generation) and used it for about 30 minutes, then I applied what I presume was a faulty update and it has soft bricked my tablet.
Heres the scenerio,
-I cannot get my nexus 7 into usb debugging mode because it wont boot up into the actual interface and such
-Everytime I try to install the ADB drivers, the system installs it as "google nexus 7 bootloader interface"
-recovery mode will not load up, it ends up at the google screen with a text on the topright saying "booting failed"
-I'm pretty sure my bootloader is locked which could be another reason why I cant do any of the methods involving cmd, nrt, or that manual android sdk toolkit thing.
As far as I know right now (which is barely anything since I'm new to using this tablet), I can't do anything because I cannot get into usb debugging, nor can I get the tablet to read as the ADB interface / pass the full driver test in NRT.
Hopefully someone can help (Very descriptively please!) , thanks!
Sidenotes : my boot loader menus states the following...
FASTBOOT MODE
Product Name - Grouper
Variant - Grouper
HW version - ER3
Bootloader Version - 4.23
Baseband Version - N/A
Serial Number - idk if I should actually post this but im going to assume it's irrelevant for this subject
Signing - not defined yet
Lock state - Locked
Also, It was fresh out of the box, I think the tablet was updated to 4.1
Click to expand...
Click to collapse
Use Nexus root toolkit and folow Full driver instalation guide for correct driver instalation
After this use Flash stock to repair, then you can continue to unlock/root or anithing else.

[Q] Nexus 7 doesn't boot

Hello all! I'm having a problem with a Nexus 7.
This is my brother's tablet that he hasn't used in a few months. It hasn't been unlocked or rooted.
I can get to the boot screen with the android lying on it's back and the options with the volume buttons. The other info on that screen which might be pertinent:
Fastboot mode
Product name: grouper
variant - grouper
hw version - er3
bootloader version - n/a
serial number -
signing - not defined yet
lock stated - locked
When I go to recovery mode and push the power button, it says "booting failed" in the upper left. It still says Google in the middle, and has the options with the volume in the upper right, but the android is gone as is the text in the lower left.
I have adb and fastboot installed, but I can't seem to do much since the tablet is locked. I tried unlocking a few times, and it's always failed. Usually it doesn't give a reason, but one time I got this: "Failed (status read failed (Too many links))"
I've tried googling this and can't find someone with the same problem.
Anything I can try?
Thanks!
Nexus Tool Kit
rbeavers said:
Nexus Tool Kit
Click to expand...
Click to collapse
OK, I have that now, but I can't get very far. I think I need to enable debugging on the device first? How can I do that in that state it's in now?
swirv81 said:
OK, I have that now, but I can't get very far. I think I need to enable debugging on the device first? How can I do that in that state it's in now?
Click to expand...
Click to collapse
Anything else I can try? Not sure if I'm missing something with the tool kit, but I nothing I tried seemed to help.
swirv81 said:
Anything else I can try? Not sure if I'm missing something with the tool kit, but I nothing I tried seemed to help.
Click to expand...
Click to collapse
If you can get into the Bootloader, just run the below via ADB
Code:
fastboot oem unlock
Once you unlock the Bootloader you can use the "Soft Brick" Mode in the NRT to Re-flash back to stock and see if that will allow you to boot. You do not need debugging enabled to use the Nexus Root Toolkit if you use the Soft Brick mode, but you must have an unlocked bootloader.
ariesgodofwar said:
If you can get into the Bootloader, just run the below via ADB
Code:
fastboot oem unlock
Once you unlock the Bootloader you can use the "Soft Brick" Mode in the NRT to Re-flash back to stock and see if that will allow you to boot. You do not need debugging enabled to use the Nexus Root Toolkit if you use the Soft Brick mode, but you must have an unlocked bootloader.
Click to expand...
Click to collapse
I've tried unlocking a few times, but after a few minutes of it saying "unlocking" it fails.
swirv81 said:
I've tried unlocking a few times, but after a few minutes of it saying "unlocking" it fails.
Click to expand...
Click to collapse
What says "unlocking" (computer or tablet) and are you trying to do it through the Toolkit, or via command prompt ADB? I would first make sure your computer is seeing your tablet (ie. that the drivers and Fastboot are installed correctly). Do you know that they are?
ariesgodofwar said:
What says "unlocking" (computer or tablet) and are you trying to do it through the Toolkit, or via command prompt ADB? I would first make sure your computer is seeing your tablet (ie. that the drivers and Fastboot are installed correctly). Do you know that they are?
Click to expand...
Click to collapse
I was trying this with the command prompt. I could get fastboot to list the device when using that command. And the tablet and command prompt both say "unlocking" when doing that. I would assume that means the computer is seeing the tablet and everything is set up correctly?
I think I tried to unlock with the Toolkit, but I believe it told me that device needs to be in debugging mode.
Hey there, I'm having a similar problem.
My info is the same except my bootloader version is 4.18 and my lock state says it's unlocked. I tried to use the root kit but I'm having trouble with the fastboot device being detected. Driver solutions attempted were the google ones, and the pdanet ones. I can't really do the manual thing since that involves the device being recognized when plugged in, and since I can't enable usb debugging... anyways the automated drivers windows says were installed successfully so I don't really know what else to do.
Note: I do know the usb port on the tablet and computer work since when plugged in, it will show that its charging with the white battery icon.
Same issue here
I was in the process of upgrading manually from android 5.0 to 5.0.2 owing to the serious lag that came with lollipop. The OTA was taking longer and testing my patience as most apps were crashing due to lag.
Therefore decided to go for manual flashing of the image. I have never done this before. I was able to make the computer see my device by disabling mtp via storage under setting in the device. This is one thin I noticed to make the device visible to the computer.
After installing the device drivers my nexus was visible within the device manager but it couldn't be seen as an external storage until I played with the MTP. I had even unlocked the boot loader before all this.
So everything was going well and while I started to think all is well, I ran into this issue. From adb I tried to run 'flash-all.bat' from the new device image. Something went wrong somewhere - don't know what it is, but from then on, I am stuck in the fastboot screen or into recovery mode but when i try to boot the device bu hitting the power button - I get this message 'Booting failed'.
I am also trying to use NRToolkit but no use. When I connect my device it is seen in the device manager in my pc but cannot see it as a storage. Therefore when I now try to run the 'adb devices' command it cannot see my device. From what I saw initially, until I enable/disable mtp mode adb was not able to see my device to communicate.
Now when I tried NRT and installed the drivers once again, it is being detected in the device manager but when I run the driver test within NRT - I get a ADB device not found error. Within NRT all that it says is go into device setting>storage to enable it which I know but at the current status of my device in boot screen/recovery mode how can I go in to enable this. This is not helpful.
Somebody please suggest a workaround for this issue. I know I am close to the solution but not sure how to enable the MTP or at least made the NRToolkit to say 'ADB device found'.
My fastboot screen shows these details:
Fastboot mode
Product name grouper
Variant = grouper
HW Version – ER3
Bootloader version – 4.23
Baseband version – N/A
Serial number – 015d21d910141c0a
Signing – not defined yet
Lock State - unlocked
Please help.

[Q] Old Nexus 7, New Issues

Hey guys!
I've been scouring these forums for two days now making sure my specific issue hasn't been discussed and, from what I've seen, I've won some sort of "annoying issue" lottery.
I was handed a Nexus 7 (ME370T) a few days ago and told "if you can fix it, it's yours."
I can get to the bootloader no problem but not the actual OS. Here's the data from the bootloader:
Fastboot Mode
Product Name - grouper
Variant - grouper
HW Version - ER3
Bootloader Version - 4.23
Baseband Version - N/A
Serial Number - xxxxxxxxx
Signing - not defined yet
Lock State - Locked
Long story short, I've installed the Android SDK and when I plug the tablet into my PC, I can see it as "Google Nexus 7 Bootloader Interface"
When I use fastboot devices, it sees the tablet just fine.
When I use adb devices, it doesn't see the tablet.
I've tried fastboot oem unlock and I get a FAILED (remote: (Unknown error code)) error.
I can run the unlock feature through the Nexus Root Toolkit but it reboots to a black screen (my device manager sees it as "Asus Transformer Prime APX Interface")
When I finally get the thing rebooted to the bootloader (manually powering off and then back on), it's still locked.
I have no idea if USB Debugging was turned on or not. I keep reading that, to flash a partition to a new file, the bootloader doesn't need to be unlocked but every single time I try to fun fastboot, i get Failed, Bootloader is locked.
Am I nuts? I know I'm new to this but I'm fairly certain I've done everything right! You guys seem super knowledgeable and I hope you can help me out!
Thanks!

Categories

Resources