First of all i apologise if this has already been asked and solved, i have searched and each time i have drawn up a blank. I have been given the mission of reloading android back on a asus nexus 7 (2012) wifi tablet. So far i have been unsuccessful in reloading it. I have attached the details given to me by "fastboot gervar all" if it helps. all i know is it is not version 3.41 and when i attempt to flash any bootloader img i get errors. the tablet will load into fastboot mode no problem, i also get the white google image with an unlocked padlock. the unit charges showing the white charge symbol. I guess the main question is can i reload the tablet into working order, or with the errors and info provided do i give up and accept defeat?:crying:
Related
Dear XDA Geniuses,
I have a 16gb Nexus 7 WI-Fi. I was using Nexus 7 toolkit 2.0.0 to try and flash my nexus 7 back to the the stock google rom (option 9 in the toolkit.) It seems as if it wiped out cyanogen mod 10, which i had been using, as well as clockwork recovery. My nexus 7 now boot up with the google logo and the unlocked padlock on the bootom. using the volume rocker i can select the bootloader option and get an android figure with his chest open.
this is the only option i can select. my attempts have been:
1)connect it to computer. Windows 7 and Windows 8 will not recognize it, nor let me access it from the command line.
2. Use nexus 7 toolkit, which DOES recognize it in fastboot mode, to flash a new recovery on there. it says that a command failed, and won't let it write to it.
3) install adb and android sdk tools. my tablet won't show up under devices, and I am not sure if it is still in usb debugging mode. command line will not recognize it as an adb device and will not control tablet.
when i looked at this thread it was dealing with a locked bootloader, while mine is unlocked. it also wanted command line operations from the computer, which does not seem to work for me.
i was attempting to do something like this (laptop mag blog how to hard reset a bricked nexus 7) but without my nexus 7 showing up under devices I am not sure what my options are.
TLDR: Nexus 7 16gb WIFI only boots into boot recovery. Using nexus 7 toolkit to recognize as fastboot. otherwise will not show up on computer. no recovery, no boot image.
Thank you for reading.
I went back and reread the thread on flashing and restoring nexus 7 to stock in this forum, but every command I try returns " command write failed invalid argument ". Using android sdk manager i can get it to recognize the device in fastboot mode. my drivers there seem to be working.
edit: I got all the way to flashing the bootloader, but it returned "no such device or address. "
JerryMc88 said:
I went back and reread the thread on flashing and restoring nexus 7 to stock in this forum, but every command I try returns " command write failed invalid argument ". Using android sdk manager i can get it to recognize the device in fastboot mode. my drivers there seem to be working.
edit: I got all the way to flashing the bootloader, but it returned "no such device or address. "
Click to expand...
Click to collapse
latest progress can be found at imgur slash TAikq
now it is say data transfer failure - too many links. 146.84 seconds.
it was my cable. the cable mounted it in fastboot mode, but would not allow writing. switched out the cable, and we are up and running again. thanks!
Um.... Glad we could help?
Sent from my Nexus 7 using xda app-developers app
Sticky?
Man, I would love to see this sticky posted, or at least a list of errors and fixes stickied. I have been looking for an answer to the same issue for two days. Finding out it was just a lousy cable really really really pissed me off... I'm glad someone figured it out and actually posted their solution, most of these wind up with nothing.
OMG, I've tried to flash my N7 with a new lollipop 5.1 today and got the same issue as described here http://forum.xda-developers.com/showthread.php?t=2724273 then, after 5 or 6 hours of thinking what is going on, I finally found this very old thread and guess what? Changing this sh***ty cable I was using solved the problem.
Use USB ports on the back of your computer, not the front.
*** 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:
Don't know how but I broke my Nexus 7 (2013 LTE) using wugfresh toolkit. I had it rooted and unlocked using the toolkit then decided I wanted to go back to stock. So I used the flash stock + unroot (device on) and oem lock.
Now my Nexus when powered on comes to the bootloader (fastboot mode) screen that has START at the top in green. If I press power to select start it shows Google in white with nothing else on the screen. It will stay like that forever (at least a few hours that I've verified). I also just noticed while it is on the "Google" screen I can press the up/down volume buttons and it gives me the option to start, power off, etc. just like it's still in the bootloader. I'm not really sure what all that means... just trying to give as much information as possible.
I've had no luck finding a solution already on this forum. I haven't even found someone who describes this exact same problem with this particular model Nexus.
In addition to trying to use the Wug toolkit to fix my Nexus I also came across this thread: http://forum.xda-developers.com/showthread.php?t=2381582
I tried following the instructions exactly and the output seemed to report fixing my Nexus but it did not. I'm referring to the output you get when you run the dead nexus bat file. The only bad output it gave me was several messages "FAILED (remote: Bootloader is locked)" However, at the bottom of the output it said my "Nexus has been restored!"
So in summary these two solutions I've tried (wug toolkit and the thread mentioned above) seem to report fixing my Nexus but didn't actually do anything. Also noticed now with the WUG toolkit the driver test fails. I followed all the steps and removed all drivers and did a fresh install. It mentions needing USB debugging enabled but how can I do that since I can't get past the bootloader/google screen?
Any help appreciated!
One other thing I forgot to mention. When it was working after I had rooted/unlocked I installed that multirom app from the app store. I don't see how that could have broken anything.
One last thing I recall. The last thing I did was do a factory reset under settings when everything was working.
I've been trying all these various toolkits and following videos but nothing seems to fix it. One thing about all these help guides out there they all tell you to make sure you're in usb debugging mode... but that isn't possible for me since I can't get past the Google loader. I haven't had much luck finding out what to do in my case.
and I think I just fixed it! I will post what I did if this works...
So all I had to do was unlock my bootloader then do the factory/stock restore. When I tried following every single recovery guide out there none of them mentioned unlocking before doing the 1 click restore/fix. Strange I had to do it this way I guess, but every tool would error out saying the Nexus was locked.
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!
Hello Everyone,
So I've got a friend's Nexus 7 (2012) that gets stuck at the google logo when booting up now.. I'm gonna go out on a limb and assume it's probably dead but I'm trying some things to see if I can get it to do anything.
The state of the Nexus:
Will Not Boot (Stuck on google logo)
USB debugging is //NOT// enabled
Bootloader is locked
OEM unlock is not enabled
Can get into bootloader and recovery options
Clearing /cache and /data just get stuck
Running KTU84P
My current line has been to try and update the OS through the recovery options adb sideload update with an OTA update from google, I've been using images from here https://forum.xda-developers.com/showthread.php?t=1745781 for KTU84P but when I run all of them they all just get stuck at
Code:
Verifying current system...
There are no error codes, no error messages and it stays there indefinitely.
I've looked around a bit and can't see anyone else having this issue (usually they at least get an error to help them along) if anyone has seen this issue happen before or has any ideas on anything I can do to try and get the nexus to be more than an expensive paperweight that'd be great. I have a feeling there's something wrong with the storage somewhere along the line but... No real idea.
Edit: Been running for about 6 hours now, still no change
Thanks,
P110