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.
Hello everyone,
I have had an issue with my nexus 7 2 days ago and couldn't figure out a way to fix it yet, so I need your help
So basically I have been flashing ROMs on my nexus 7 and everything was great no issues at all, til I accedintaly was in Recovery mode and fomatted sd and system (GOD that was stupid), so after doing so all my ROMs saved on my sd card were deleted so I am not able to flash ROMs anymore. The worest part is that even my preloaded PARANOID ANDROID Rom hasn't been able to boot up my device so it's stuck on Google boot logo.
Hence, I assume if there is a way to push ROMs while the tablet is in Recovery mode that would allow me to flash them again and the problem is sloved. However, I don't know if I am able to do that, I have tried nexus 7 toolkit and Android commander but they require USB debugging to be ON (which i am not sure if it was since last time I had this problem), and they both require the tablet to be tured on I belive in order for them to do thier magic ?? correct me if I am wrong...
Unfortuantely I didn't do Nanadroid backup
I am not able to take the tablet to Google obviousely cause i am rooted so you guys are my only hope
Thanks in advance and really appreiate it if i cab get a fast response.
Just flash the factory image from fastboot.
I use the Nexus 7 Toolkit v3.2.0 by mskip. It is amazing. It's in the development thread. You don't need adb to flash the original image. You only need to get into fastboot mode.--->
Turn off n7. Hold both volume up and down and the power button until you get into the bootloader. Then plug your n7 into USB and then launch the toolkit. Make sure your device is recognized at the top in fastboot mode. You are ready to restore the factory image.
Sent from my Paranoid Nexus 7 using XDA Premium
I had an unlocked and rooted Nexus 7 (2012) with Android 4.2. After on OTA-Update I have an unlocked but _rooted_ Nexus 7. I read a lot about "waiting for device", but can't get it work anymore to connect. The device is reset and contains a fresh install without any added data.
I tried to follow http://forum.xda-developers.com/showpost.php?p=44179882
Step 2: Reboot the Nexus 7 into fastboot mode using the combination of volume up, volume down and power buttons
Click to expand...
Click to collapse
I can't get into fastboot with 3 buttons, but with Power and Vol- I see:
Product-Name - tilapia
Variant - tilapia
HU Version - PR
Bootloader Version - 4.23
Baseband Version - 1231_0.18.0_0409
Serial Number - ....
Signing - not signed yet
Lock state - unlocked
Maybe I am doing something wrong then, when I try to flash.
I see start, when I press the power button the N7 starts
When I change to recovery mode, I see "waiting for device" (USB debugging is on, the cable worked to unlock it)
Since I have an unlocked device, I tried only from Ubuntu 12.04 as root:
Code:
~# fastboot-linux flash recovery CF-Auto-Root-tilapia-nakasig-nexus7.img
Before I followed http://forum.xda-developers.com/showpost.php?p=44179882 I flashed recovery-clockwork-6.0.0.6-grouper.img
I could also install SuperSU 1.51, but root doesn't work and I found no way to install an updated SuperSU 1.51
BTW, I didn't know, that the grouper.img is the wrong one for my 3G device, UMTS worked fine with 4.2
try using nexus root toolkit. I had rooted prior to 4.3. when I updated, i just had to press one button to reroot(if you didn't use nexus root toolkit to begin with then you may need to go thru the driver setup)
Xanthius Balaraw said:
try using nexus root toolkit. I had rooted prior to 4.3. when I updated, i just had to press one button to reroot(if you didn't use nexus root toolkit to begin with then you may need to go thru the driver setup)
Click to expand...
Click to collapse
I will try it, also I hoped to use Linux.
http://www.wugfresh.com/nrt/
Configure your drivers if you haven’t already using the driver guide (If you aren’t sure use Step 3 of the driver guide to test your drivers).
Click to expand...
Click to collapse
Where do I get the drivers? Couldn't find a link there.
Edit: Since I have to go to a Windows PC, I downloaded the windows-programm only on my linux pc, it looks like the drivers are included in Nexus Root Toolkit: http://www.youtube.com/watch?v=iQhyerPfGes
I tried a lot with Windows XP 32bit and Windows 7 bit, but always I got "adb device was not found", but I saw a popup on the windows desktop with the Nexus after I attached the USB-cable. With Win7 I tried drivers 1-3, with XP driver 1.
With Linux something works:
Code:
adb devices
List of devices attached
<serial no> device
Code:
fastboot devices
<serial no> fastboot
Code:
~# fastboot flash recovery cf-auto-root-tilapia-nakasig-nexus7_92bf3da522bbb6e86725fe3290f391cc.zip
sending 'recovery' (6900 KB)...
OKAY [ 0.802s]
writing 'recovery'...
OKAY [ 0.332s]
finished. total time: 1.134s
But how can I install supersu? I don't know how to get the menu, where I can install zip-files.
lg-optimus said:
Where do I get the drivers? Couldn't find a link there.
Click to expand...
Click to collapse
There is a button in nrt to download and install drivers also to test to make sure they are working.
This forum is for the new 2013 Nexus 7 named Flo. You stated you have the 2012 verson...might want to go to the 2012 Nexus 7 forum here for advice.
On the 2013 Nexus 7 I use the volume button in bootloader/fastboot mode to switch to recovery, then select it with the power button to boot into the recovery you just flashed to the device. From there you can install Supersu (if you have downloaded the Supersu zip file to your device before hand).
geckocavemen said:
This forum is for the new 2013 Nexus 7 named Flo. You stated you have the 2012 verson...might want to go to the 2012 Nexus 7 forum here for advice.
Click to expand...
Click to collapse
This Guy ^
Oh, I am sorry to be in the wrong forum. What I found out in the menatime, that the stock-recovery is flashed everytime after a reboot, so there is no menu to flash zip-files after a new start.
lg-optimus said:
Oh, I am sorry to be in the wrong forum. What I found out in the menatime, that the stock-recovery is flashed everytime after a reboot, so there is no menu to flash zip-files after a new start.
Click to expand...
Click to collapse
I know it was in the wrong forum and all, but found something odd. I had a lot of trouble due to the same thing, waiting for device when trying fastboot. Just in case anyone arrives here: When you see the screen with the Start on top and FASTBOOT MODE in small red letters with the product specs, you're exactly where you should, no need to choose any option.
In my case, the fastbood mode doesn't work from linux (Kubuntu 13.10). It's just not detected, it makes no usb plugged sound, no icon on the tray...nothing. After some headaches just decided to boot to windows and try again. Fastboot mode, exactly as described, plug it to USB, and there you go, the "bop-beep" sound of usb plugged. I knew then it was gonna work on Windows.
Wrong forum *and* necro posting. Fantastic.
Sent from my Nexus 7 (2013) running 4.4
limbonik said:
Wrong forum *and* necro posting. Fantastic.
Sent from my Nexus 7 (2013) running 4.4
Click to expand...
Click to collapse
Thanks for your contibutive post. However I got there through google searches, that kept directing me to this thread. I imagined more people would get there searching for answers not finding them. By the way, the thread is from august, not so old.
install PDAnet on your device .. follow procedure of installation carefully ( should be installed on both pc and phone ) and when it was installed .when u enter your bootloader your phone will be recognize by your pc and wait for device will gone .
the method tested by me and took me one month two years ago to find .. on my g nexus first try to unlock .
PDAnet isntall drivers and everything you need to use adB commands ... if it helped give me thanks and let me know by pm .
PDA links
http://junefabrics.com/android/downloadold.php
I believe I've hard-bricked my Nexus 7. I'm not stranger to flashing, etc., but something must have messed up this time. I was previously running stock Android 4.3 with TWRP recovery and my tablet took the OTA update. The update of course failed because of the root and recovery, but instead of going back to Android 4.3, it wouldn't boot past the fastboot screen (bootloader screen? with the green android).
So, planning to return to all stock, I downloaded the official Android 4.4 .tgz file and extracted it to my platform-tools folder for the Android SDK. I ran "flash-all.bat" as explained in this tutorial: http://www.androidpolice.com/2013/0...stock-using-a-full-factory-image-and-root-it/
Something must have went wrong because the screen went black and will not turn back on. When plugged into the PC, it is recognized as only an "APK" device. Sources online indicate that this is hard-bricked, as there is no "nvflash" openly available for the Nexus 7 to restore the bootloader.
1. What happened and how can others prevent this?
I think I should have flashed each partition individually (i.e. boot, recovery, system, etc) instead of "flash-all." Any idea what happened to the bootloader? Any other ideas on how to restore the bootloader?
2. What to do now?
EDIT: Apparently my device is out of warranty. Crap.
EDIT 2: Apparently I accidentally downloaded Android 4.4 (KRT16S) for the Nexus 7 Mobile (nakasig) and not for the Nexus 7 Wifi (nakasi)... Opps!
There are several Nexus 7s on ebay with cracked screens, etc. If I purchased one of these, what would I need to pull from them to fix this?
Thanks for your assistance in advance! This forum is great.
What about pressing and holding power button for more than 30 seconds?
Once it could boot and you could enter into fastboot mode, then I think you would get a chance to save it.
BTW, I did mess up when I was flashing KRT16O factory images, which was the earlier release for Kitkat.
At that time, I just used the flash-all.bat like you did. And in the second round, I still failed when following and typing the listed commands in flash-all.sh.
So I chose to use nexus toolkit after that.
Thanks for your reply.
I keep trying that, along with the various other combinations of power button and volume down and volume up. Nothing. The most that happens is when it's plugged into the PC, the PC makes the sound of something being connected and disconnected. I just tried unplugging the battery too. I'll let it charge over night and try again tomorrow.
When yours failed the first 2 times, you were still able to get into fastboot? You're right, if I can just get there then I'll be alright.
Thanks again.
I was just backtracking my steps and realized the mistake I made. I accidentally downloaded Android 4.4 (KRT16S) for the Nexus 7 Mobile (nakasig) and not for the Nexus 7 Wifi (nakasi). Major opps!!
1. Any way to recover from this brick? My gf also has a Nexus 7 (2012). Anything I can copy from that to restore mine? (if she even lets me touch it after she hears about this!)
2. There are several Nexus 7s on ebay with cracked screens, etc. If I purchased one of these, what would I need to pull from them to fix this?
No problem,bro. I think you can always get responses here at XDA though I didn't help you out.
And yes, I could still enter into Fastboot at that time.
However, I was not able to reboot my N7 using the aforementioned methods since it got stuck in Google logo.
Hence I removed the batterysilly, booted it and used the key combination to get into Fastboot. And you know the rest, used the toolkit....
My friend if u can enter fastboot then u can definately revive ur device, it is soft brick not hard brick (soft brick = software is dead) (hard brick = hardware is dead)
I do this all the time just for fun
Let me give u step by step instructions.
1. Download this tool kit
http://forum.xda-developers.com/showthread.php?t=1766475
2. Download the proper stock image for ur device (make sure u pay attention when u download the file, u definately dont want to download wrong file and then redownload the file again)
https://developers.google.com/android/nexus/images
3. Install toolkit, Select your device and don't worry about android version because u have non rit now and install the proper drivers for fastboot to work.
4. From toolkit main screen, select (softbrick/bootloop) and accept the warning.
5. Now select (Other/Browuse option) and then select (I Downlaoded a factory image myself) option then it will ask for the image that u downloaded from google website (Step 2).
6. If u have done exactly as i said then ur phone should be detected in Fastboot mode and the flashing would start and after some time phone should show loading screen (os is booting) wait for it to boot and enjoy ur stock android.
7. Enjoy.
FYI u should have enough battery (around 50%) and to enter fastboot mode u just have to boot to bootloader (restart/ power on the device while pressing volume down button) u should see the screen with bunch of numbers e.g bootloader version etc.
zamboniman87 said:
I was just backtracking my steps and realized the mistake I made. I accidentally downloaded Android 4.4 (KRT16S) for the Nexus 7 Mobile (nakasig) and not for the Nexus 7 Wifi (nakasi). Major opps!!
1. Any way to recover from this brick? My gf also has a Nexus 7 (2012). Anything I can copy from that to restore mine? (if she even lets me touch it after she hears about this!)
2. There are several Nexus 7s on ebay with cracked screens, etc. If I purchased one of these, what would I need to pull from them to fix this?
Click to expand...
Click to collapse
Hmm... there is a thread on making it unbrickable, but you have to do that ahead of time. If you were to buy a broken tablet, you'd probably need to replace the motherboard.
Sent from my Nexus 4 using XDA Premium 4 mobile app
xateeq said:
My friend if u can enter fastboot then u can definately revive ur device, it is soft brick not hard brick (soft brick = software is dead) (hard brick = hardware is dead)
Click to expand...
Click to collapse
Thanks for your help, but unfortunately I can't even enter fastboot. I can only enter APX mode, which apparently is pre-fastboot.
korockinout13 said:
Hmm... there is a thread on making it unbrickable, but you have to do that ahead of time. If you were to buy a broken tablet, you'd probably need to replace the motherboard.
Click to expand...
Click to collapse
Thanks. I saw that thread, but of course it was too late at that point. Perhaps I'll look into buying one with a cracked screen, or sell mine for parts on ebay.
Plz dont tell me u flashed wrong bootloader, plz plz plz.
zamboniman87 said:
I was just backtracking my steps and realized the mistake I made. I accidentally downloaded Android 4.4 (KRT16S) for the Nexus 7 Mobile (nakasig) and not for the Nexus 7 Wifi (nakasi). Major opps!!
Click to expand...
Click to collapse
Dammit, I just made this exact same mistake. Came here to XDA looking for help, and it seems that this may be one of those things that you simply can't recover from... sad day!
---------- Post added at 11:40 AM ---------- Previous post was at 11:09 AM ----------
SteveRiley said:
Dammit, I just made this exact same mistake. Came here to XDA looking for help, and it seems that this may be one of those things that you simply can't recover from... sad day!
Click to expand...
Click to collapse
Well, now isn't this weird... I unplugged the USB cable from my PC and then plugged it into the wall charger. After waiting a while, I was able to boot the Nexus into the "wrong" bootloader. I immediately flashed the correct one, and now am running the latest factory image.
@zamboniman87 -- I did find a thread on Android Central describing a situation in which someone erased their bootloader. The thread contains a tool that a couple folks claimed to help fix the problem. You might give that a try.
Lucky you! This gives me hope though. I'll check it out. Thanks!
xateeq said:
Plz dont tell me u flashed wrong bootloader, plz plz plz.
Click to expand...
Click to collapse
yep.... I feel dumb. haha.
xateeq said:
My friend if u can enter fastboot then u can definately revive ur device, it is soft brick not hard brick (soft brick = software is dead) (hard brick = hardware is dead)
I do this all the time just for fun
Let me give u step by step instructions.
1. Download this tool kit
http://forum.xda-developers.com/showthread.php?t=1766475
2. Download the proper stock image for ur device (make sure u pay attention when u download the file, u definately dont want to download wrong file and then redownload the file again)
https://developers.google.com/android/nexus/images
3. Install toolkit, Select your device and don't worry about android version because u have non rit now and install the proper drivers for fastboot to work.
4. From toolkit main screen, select (softbrick/bootloop) and accept the warning.
5. Now select (Other/Browuse option) and then select (I Downlaoded a factory image myself) option then it will ask for the image that u downloaded from google website (Step 2).
6. If u have done exactly as i said then ur phone should be detected in Fastboot mode and the flashing would start and after some time phone should show loading screen (os is booting) wait for it to boot and enjoy ur stock android.
7. Enjoy.
FYI u should have enough battery (around 50%) and to enter fastboot mode u just have to boot to bootloader (restart/ power on the device while pressing volume down button) u should see the screen with bunch of numbers e.g bootloader version etc.
Click to expand...
Click to collapse
I soft bricked my nexus 7 (2012), I was in Team Win Recovery and I selected Dalvik Cache, System, Cache, Data, Internal Storage and formated/deleted it , now I don't have system or recovery
img > https://www.dropbox.com/s/a7ojrr16lt8n27s/nexus bricked (3).JPG?dl=0
all I can load is fastboot mode
img> https://www.dropbox.com/s/jzmr7811w02r525/nexus bricked (2).JPG?dl=0
I will try to do all this steps that "xateeq" wroted and let you now how it went thanks!
psykg said:
I soft bricked my nexus 7 (2012), I was in Team Win Recovery and I selected Dalvik Cache, System, Cache, Data, Internal Storage and formated/deleted it , now I don't have system or recovery
img > https://www.dropbox.com/s/a7ojrr16lt8n27s/nexus bricked (3).JPG?dl=0
all I can load is fastboot mode
img> https://www.dropbox.com/s/jzmr7811w02r525/nexus bricked (2).JPG?dl=0
I will try to do all this steps that "xateeq" wroted and let you now how it went thanks!
Click to expand...
Click to collapse
hey it worked thanks!
at first there were problems with fastboot and drivers somehow usb 2.0 was a bit problematic but usb 1.0 was able to see device
after downloading many drivers (some from nexus tollkit some from web) , and after few restarts of device and bootloader, pc was able to recognize device and than I had to go 2 times with nexus tololkit >softbrick/bootloop
1st time failed
2nd time worked!
thank all!
Hello,
I wanted to install aosp_grouper on my Nexus /, but after wiping the connection becam elabile during dlahing. Now I cannot connect the Nexus anymore to my PC via the Nexus root toolkit. The device shows only the Google logo and an open lock. Hard reset does not result in anything different.
Is there a way to reconnect to my PC or do I have to throw away the device?
Many thanks for your help.
Phero100 said:
Hello,
I wanted to install aosp_grouper on my Nexus /, but after wiping the connection becam elabile during dlahing. Now I cannot connect the Nexus anymore to my PC via the Nexus root toolkit. The device shows only the Google logo and an open lock. Hard reset does not result in anything different.
Is there a way to reconnect to my PC or do I have to throw away the device?
Many thanks for your help.
Click to expand...
Click to collapse
Hi, Phero100...
Your device should be recoverable, because...
Phero100 said:
...The device shows only the Google logo and an open lock...
Click to expand...
Click to collapse
This indicates that the bootloader is still good, and the device is not hardbricked.
I've never used a toolkit myself, preferring to use fastboot commands instead, so I can't comment too much on the Nexus root toolkit you mention in your post. But it's possible you may get a response from the toolkit by booting your Nexus 7 into fastboot mode, as follows...
From a powered off state, press VOL-DOWN and then simultaneously press POWER-ON. Hold both buttons for 15 seconds or until the device boots into the bootloader.
If you don't get anywhere with the toolkit you're using, I suggest you just reflash the Nexus 7 back to Google factory stock using fastboot.
Take a look at my response to another XDA member, from a couple of days ago, where I elaborate on fastboot flashing in more detail...
https://forum.xda-developers.com/showpost.php?p=80387547&postcount=2
...and of course there are other detailed guides elsewhere on XDA.
Good luck
Rgrds,
Ged.
Dear Ged,
thanks, but it does work only partially. Although I got a new image on the Nexus, an opened android man with Start at the top (fastboot mode?), neither the toolkit nor Windows 10 makes any connection to my Nexus. Anyway, without connection I can't do anything.
How can I connect to the Nexus 7 now?
GedBlake said:
Hi, Phero100...
Your device should be recoverable, because...
This indicates that the bootloader is still good, and the device is not hardbricked.
I've never used a toolkit myself, preferring to use fastboot commands instead, so I can't comment too much on the Nexus root toolkit you mention in your post. But it's possible you may get a response from the toolkit by booting your Nexus 7 into fastboot mode, as follows...
From a powered off state, press VOL-DOWN and then simultaneously press POWER-ON. Hold both buttons for 15 seconds or until the device boots into the bootloader.
If you don't get anywhere with the toolkit you're using, I suggest you just reflash the Nexus 7 back to Google factory stock using fastboot.
Take a look at my response to another XDA member, from a couple of days ago, where I elaborate on fastboot flashing in more detail...
https://forum.xda-developers.com/showpost.php?p=80387547&postcount=2
...and of course there are other detailed guides elsewhere on XDA.
Good luck
Rgrds,
Ged.
Click to expand...
Click to collapse
Phero100 said:
Dear Ged,
thanks, but it does work only partially. Although I got a new image on the Nexus, an opened android man with Start at the top (fastboot mode?), neither the toolkit nor Windows 10 makes any connection to my Nexus. Anyway, without connection I can't do anything.
How can I connect to the Nexus 7 now?
Click to expand...
Click to collapse
Hi, Phero100...
It's possible your Nexus 7's USB port has failed/is failing, and I'm guessing you've already tried different USB cables/different USB ports on your PC.
But... I have some questions...
Phero100 said:
...but it does work only partially...
Click to expand...
Click to collapse
What do you mean 'partially'?
------------------------------------
Phero100 said:
...Although I got a new image on the Nexus...
Click to expand...
Click to collapse
Where did you get this image from, and why is it on your Nexus 7? It should be on your Windows 10 box - unzipped, with the contents in the same folder as the fastboot and ADB executables, and these are likely to be found in your toolkit folder.
------------------------------------
Phero100 said:
...an opened android man with Start at the top (fastboot mode?)...
Click to expand...
Click to collapse
Yes - that is fastboot mode.
------------------------------------
What happens when you run this command from your PC?
Code:
fastboot devices
Do you see your N7's unique serial number confirming you have a valid fastboot connection - eg., something like this...
019d2424b14050b fastboot
------------------------------------
Have you read this guide...
https://forum.xda-developers.com/showthread.php?t=1907796
It's a little out of date, perhaps - but the underlying principles are still good. There are also other guides available here on XDA, and if you take a look at my own posting history, you'll see I've written some fairly detailed responses to other XDA members regarding aspects of reflashing the Nexus 7, although you may have to go back to around 2012/2013/2014, since I no longer use my Nexus 7 and haven't done so for about five years.
------------------------------------
I could have written another detailed guide here, but it would feel like I'd be 'reinventing the wheel'. The Nexus 7 is now a little over seven years old, and everything that can be written about reflashing it, has been written about it...
...and writing yet another guide seems redundant and pointless, not to mention time consuming on my part.
I would advise you to read around the Nexus 7 forums/threads here on XDA and the 'stickies' - acquaint yourself with using fastboot and rely less on toolkits - I know that people use them, and I'm not wholly opposed to them, but they hide/mask the process of using things like fastboot and ADB, and the possible errors they occasionally throw. In short, using fastboot directly is a more transparent way of doing things, not to mention a more granular way of doing things - eg., such as flashing a specific partition - and you'll learn more about Android, and will likely have a better idea of what to do when things go wrong, as sooner or later, they inevitably will.
However, I digress...
Comimg back to your specific case. Your bootloader is still good, which is a good thing - it means your device is not hard-bricked. If you cannot, by any means whatsoever, achieve any kind of connection with your Windows 10 box, then, as I intimated at the beginning of this post, your Nexus 7's USB port may have failed/come-loose/become detached from the motherboard, or maybe there's a problem with the USB cable you're using.
Another possibility is, you may have a Windows driver problem, which is something I've never experienced myself, and is therefore something I wouldn't be able to immediately help you with, without me doing quite a bit of research first. But I've read that Windows driver problems are a notorious obstacle when it comes to things like fastboot and ADB, and by extension, with toolkits too - so called 'driver hell' (ie., possible Windows device driver conflicts), so I would suggest you Google around, and run some searches here on XDA pertaining to that particular problem.
I hope I've given you some useful pointers in the right direction, and I hope you get your Nexus 7 up and running again.
Good luck.
Rgrds,
Ged.
GedBlake said:
Another possibility is, you may have a Windows driver problem, which is something I've never experienced myself, and is therefore something I wouldn't be able to immediately help you with, without doing a bit of research myself. But I've read that Windows driver problems are a notorious obstacle when it comes to things like fastboot and ADB, and by extension, with toolkits too - so called 'driver hell' (ie., possible Windows device driver conflicts), so I would suggest you Google around, and run some searches here on XDA pertaining to that particular problem.
I hope I've given you some useful pointers in the right direction, and I hope you get your Nexus 7 up and running again.
Good luck.
Rgrds,
Ged.
Click to expand...
Click to collapse
If it does turn out to be a Windows driver problem, in my experience the Universal Naked Drivers work the best.
Hi Ged,
GedBlake said:
Hi, Phero100...
But... I have some questions...
Click to expand...
Click to collapse
What do you mean 'partially'?
That I do not get a connection ot Windows.
Where did you get this image from, and why is it on your Nexus 7? It should be on your Windows 10 box - unzipped, with the contents in the same folder as the fastboot and ADB executables, and these are likely to be found in your toolkit folder.
aosp_grouper-7.1.2-ota-20190823.eng.ds.zip
from: https://androidfilehost.com
Yes - that is fastboot mode.
------------------------------------
What happens when you run this command from your PC?
Code:
fastboot devices
Do you see your N7's unique serial number confirming you have a valid fastboot connection - eg., something like this...
019d2424b14050b fastboot
Yes
Have you read this guide...
https://forum.xda-developers.com/showthread.php?t=1907796
Not yet, but i will do.
On the other hand, if I try the toolkit again, to unlock boatloader it tries several times, but says that it is a connectivity issue. It seems to me that it cannot be the USB port/cable, because otherwise it would not be detected by windows. Furthermor, USB connection worked before until the decribed error occurred. Therefore, I assume that it might be a driver problem.
Phero100 said:
Hi Ged,
What do you mean 'partially'?
That I do not get a connection ot Windows.
Where did you get this image from, and why is it on your Nexus 7? It should be on your Windows 10 box - unzipped, with the contents in the same folder as the fastboot and ADB executables, and these are likely to be found in your toolkit folder.
aosp_grouper-7.1.2-ota-20190823.eng.ds.zip
from: https://androidfilehost.com
Yes - that is fastboot mode.
------------------------------------
What happens when you run this command from your PC?
Do you see your N7's unique serial number confirming you have a valid fastboot connection - eg., something like this...
019d2424b14050b fastboot
Yes
Have you read this guide...
https://forum.xda-developers.com/showthread.php?t=1907796
Not yet, but i will do.
On the other hand, if I try the toolkit again, to unlock boatloader it tries several times, but says that it is a connectivity issue. It seems to me that it cannot be the USB port/cable, because otherwise it would not be detected by windows. Furthermor, USB connection worked before until the decribed error occurred. Therefore, I assume that it might be a driver problem.
Click to expand...
Click to collapse
Ahh, my apologies ~ I thought you where referring to a Google Factory Image, not...
aosp_grouper-7.1.2-ota-20190823.eng.ds.zip
I have no familiarity with that image file, having never used it myself. If, as you say, it's on your Nexus 7's internal storage, you may be able to flash it using TWRP custom recovery, assuming you have TWRP flashed to the recovery partition. If not, then this brings us back to your problem, because TWRP needs to be flashed with fastboot...
You can find the download links (and instructions) for the Nexus 7 TWRP .img files at this link...
https://twrp.me/asus/asusnexus72012wifi.html
There are two download mirror links at this website, one for Europe and the other for America. Select the one that works best for you.
To flash TWRP, your Nexus 7 should be booted into fastboot mode, and from your laptop/PC, type this command in...
Code:
fastboot flash recovery [name-of-twrp.img file]
I usually rename the rather lengthy TWRP .img file to something short, like twrp.img, so the fastboot command is much easier to type, and would look like this...
Code:
fastboot flash recovery twrp.img
-------------------------------------------------
What is particularly puzzling about all of this, is the following...
Phero100 said:
What happens when you run this command from your PC?
Do you see your N7's unique serial number confirming you have a valid fastboot connection - eg., something like this...
019d2424b14050b fastboot
Yes
Click to expand...
Click to collapse
You answered 'Yes' to this question, and you do see your Nexus 7's unique serial number ~ this means you have a valid and usable fastboot connection to your Windows 10 PC. Logically then, your toolkit should work, and fastboot flash commands certainly should.
With regard to unlocking the bootloader, you might want to try this...
Code:
fastboot oem unlock
You should see a confirmation request screen on your Nexus 7, like the screenshot below.
Rgrds,
Ged.
Dear Ged,
I know manage to get everything running until flashing. The error occurs again, but hti time I red it correctly. It says zip file is corrupt. That is surprising to me given the source I downloaded the file from. I will now try a different custom ram.
GedBlake said:
Ahh, my apologies ~ I thought you where referring to a Google Factory Image, not...
aosp_grouper-7.1.2-ota-20190823.eng.ds.zip
I have no familiarity with that image file, having never used it myself. If, as you say, it's on your Nexus 7's internal storage, you may be able to flash it using TWRP custom recovery, assuming you have TWRP flashed to the recovery partition. If not, then this brings us back to your problem, because TWRP needs to be flashed with fastboot...
You can find the download links (and instructions) for the Nexus 7 TWRP .img files at this link...
https://twrp.me/asus/asusnexus72012wifi.html
There are two download mirror links at this website, one for Europe and the other for America. Select the one that works best for you.
To flash TWRP, your Nexus 7 should be booted into fastboot mode, and from your laptop/PC, type this command in...
Code:
fastboot flash recovery [name-of-twrp.img file]
I usually rename the rather lengthy TWRP .img file to something short, like twrp.img, so the fastboot command is much easier to type, and would look like this...
Code:
fastboot flash recovery twrp.img
-------------------------------------------------
What is particularly puzzling about all of this, is the following...
You answered 'Yes' to this question, and you do see your Nexus 7's unique serial number ~ this means you have a valid and usable fastboot connection to your Windows 10 PC. Logically then, your toolkit should work, and fastboot flash commands certainly should.
With regard to unlocking the bootloader, you might want to try this...
Code:
fastboot oem unlock
You should see a confirmation request screen on your Nexus 7, like the screenshot below.
Rgrds,
Ged.
Click to expand...
Click to collapse