Related
Hi
Tried to flash a new kernel and all seemed ok (flashed phones and nexus 7 few times now) when I came out of flashing I hit a bootloop, I though nothing of it and tried to restart....same issue, so next I tried to go into cw recovery, no joy, it will not show again.
I can power/vol keys to android fastboot screen with start power restart boot and so on but if I choose recovery nothing happens, I am stuck with either a bootloop or stuck on android fastboot screen and not able to move from either.
I have tried the toolkit and most other things but the problem is it cannot see my nexus 7, even after installing drivers and so on the toolkit (top right) does not list my nexus as found, because of this I cannot reflash any stock firmware/recover/reflash cwr.
Not sure how I can get around this if my pc cannot see the nexus 7.
Thanks for any help
voodoochild2008 said:
Hi
Tried to flash a new kernel and all seemed ok (flashed phones and nexus 7 few times now) when I came out of flashing I hit a bootloop, I though nothing of it and tried to restart....same issue, so next I tried to go into cw recovery, no joy, it will not show again.
I can power/vol keys to android fastboot screen with start power restart boot and so on but if I choose recovery nothing happens, I am stuck with either a bootloop or stuck on android fastboot screen and not able to move from either.
I have tried the toolkit and most other things but the problem is it cannot see my nexus 7, even after installing drivers and so on the toolkit (top right) does not list my nexus as found, because of this I cannot reflash any stock firmware/recover/reflash cwr.
Not sure how I can get around this if my pc cannot see the nexus 7.
Thanks for any help
Click to expand...
Click to collapse
try to flash recovery again via fastboot...or doesnt pc recognize divice at all?
S.R
shivasrage said:
try to flash recovery again via fastboot...
S.R
Click to expand...
Click to collapse
Hi
I cannot flash anything. On the fastboot screen I can scroll up and down powr off/start/recovery....if I choose any (apart from power off) nothing happens.
When I hook it up to my pc it cannot see it, nexus 7 toolkit also cannot see it, it does not list it as found so I cannot flash anything on to it, if I try it just says waiting for device, tried other things and same thing either waiting for device or asks if fastboot installed.
voodoochild2008 said:
Hi
I cannot flash anything. On the fastboot screen I can scroll up and down powr off/start/recovery....if I choose any (apart from power off) nothing happens.
When I hook it up to my pc it cannot see it, nexus 7 toolkit also cannot see it, it does not list it as found so I cannot flash anything on to it, if I try it just says waiting for device, tried other things and same thing either waiting for device or asks if fastboot installed.
Click to expand...
Click to collapse
f****
have you tried flashing factory image from google site.with flash all-sh?
shivasrage said:
f****
have you tried flashing factory image from google site.with flash all-sh?
Click to expand...
Click to collapse
I have a image ready but not able to flash....but what is flash all-sh? trying to search for it, is it a tool to force flash?
voodoochild2008 said:
I have a image ready but not able to flash....but what is flash all-sh? trying to search for it, is it a tool to force flash?
Click to expand...
Click to collapse
no its included in the factory image to flash all i one so it looks like for the nexus 4:
flash-all .....its a windows batch image with all included.... try this
S:R.
shivasrage said:
no its included in the factory image to flash all i one so it looks like for the nexus 4:
flash-all .....its a windows batch image with all included.... try this
S:R.
Click to expand...
Click to collapse
Thanks....but still get waiting for device, thats the problem, nothing seems to see it so I cannot flash anything to it.
You are already at the bootloader screen. Use your computer to fastboot flash a new kernel. Being able to get into recovery has nothing to do with it. You screwed it up flashing a kernel. Its likely thats all you need to fix it. Flash a new one with fastboot.
You are already at the bootloader screen. Use your computer to fastboot flash a new kernel. Being able to get into recovery has nothing to do with it. You screwed it up flashing a kernel. Its likely thats all you need to fix it. Flash a new one with fastboot.
i thought the same as you but fastboot isn recognizig N7 anymore....always wating for device....
Hemidroids said:
You are already at the bootloader screen. Use your computer to fastboot flash a new kernel. Being able to get into recovery has nothing to do with it. You screwed it up flashing a kernel. Its likely thats all you need to fix it. Flash a new one with fastboot.
Click to expand...
Click to collapse
Downloaded the fastboot exe but unsure what it needs to work as when I click on it a run box opens for like half a second and then closes, dont get a chance to read what it says, think I will have to read up on it.
[/COLOR]
voodoochild2008 said:
Downloaded the fastboot exe but unsure what it needs to work as when I click on it a run box opens for like half a second and then closes, dont get a chance to read what it says, think I will have to read up on it.
Click to expand...
Click to collapse
read this... i hope you can follwow that easily like me...
greets S.R.
http://dottech.org/21534/how-to-ins...ows-computer-for-use-with-your-android-phone/
voodoochild2008 said:
Downloaded the fastboot exe but unsure what it needs to work as when I click on it a run box opens for like half a second and then closes, dont get a chance to read what it says, think I will have to read up on it.
Click to expand...
Click to collapse
EXE? doh.......Windows.......sorry cant help.
shivasrage said:
[/COLOR]
read this... i hope you can follwow that easily like me...
greets S.R.
http://dottech.org/21534/how-to-ins...ows-computer-for-use-with-your-android-phone/
Click to expand...
Click to collapse
Tried some of that already but will try again tomorrow.
Thanks for help with this and will post tomorrow if I can sort it. cheers
I hope this instructions can help you a little bit...but if it fails don´t be angry its all I can think of ...at this time ....merry christmas
S.R.
http://forum.xda-developers.com/showthread.php?p=31931117:D
Sent from my Nexus 7 using xda premium
Well after using bits of jrom flasher and nexus toolkit I got it working again, main issue was making the tablet seen, abd and fastboot would not show device.
All up and running again THANKS TO ALL WHO HELPED
voodoochild2008 said:
Well after using bits of jrom flasher and nexus toolkit I got it working again, main issue was making the tablet seen, abd and fastboot would not show device.
All up and running again THANKS TO ALL WHO HELPED
Click to expand...
Click to collapse
How did you get it to work? I have problem getting my device to be recognized. Stuck on boot loop too..
Hey man, how did you get your computer to recognize your device? Would be great to finally fix mine as this is the same exact problem -- computer doesn't recognize it even though in fastboot.
Quacker245 said:
Hey man, how did you get your computer to recognize your device? Would be great to finally fix mine as this is the same exact problem -- computer doesn't recognize it even though in fastboot.
Click to expand...
Click to collapse
I don't understand exactly what you are trying to do, sorry: you said the pc does not see the nexus, "even thought in fastboot".. If you say even thought, it seems to me that you are able to access Android itself or maybe recovery? In that case I can't see the issue.. Sorry my fault, non english mother tongue
But, if have the device soft bricked and you are able to enter ONLY the bootloader (that is what we call often fastboot), then you should start to remove the not working fastboot drivers installed into your PC: launch the nexus in fastboot mode, go to Device Manager into your PC and search for a driver with an yellow exclamation point. This issue is very common so I hope that you have it, too.. So, uninstall that driver, then unlink the nexus from your PC; after a few seconds attach it to another USB port and see if Windows install a driver (it should). If this new driver doesn't work, too, or if Windows does no install any, try this one: http://forum.xda-developers.com/showthread.php?t=1426502
Hope it helps, let us know, see you!
EDIT: also, if you still have no luck, you should find a Linux or Mac PC/laptop and download the adb/fastboot binary files for that OS; this will definitively solve your driver issue ( @#ò#@!"@# Winzozz )
brainvision said:
I don't understand exactly what you are trying to do, sorry: you said the pc does not see the nexus, "even thought in fastboot".. If you say even thought, it seems to me that you are able to access Android itself or maybe recovery? In that case I can't see the issue.. Sorry my fault, non english mother tongue
But, if have the device soft bricked and you are able to enter ONLY the bootloader (that is what we call often fastboot), then you should start to remove the not working fastboot drivers installed into your PC: launch the nexus in fastboot mode, go to Device Manager into your PC and search for a driver with an yellow exclamation point. This issue is very common so I hope that you have it, too.. So, uninstall that driver, then unlink the nexus from your PC; after a few seconds attach it to another USB port and see if Windows install a driver (it should). If this new driver doesn't work, too, or if Windows does no install any, try this one: http://forum.xda-developers.com/showthread.php?t=1426502
Hope it helps, let us know, see you!
EDIT: also, if you still have no luck, you should find a Linux or Mac PC/laptop and download the adb/fastboot binary files for that OS; this will definitively solve your driver issue ( @#ò#@!"@# Winzozz )
Click to expand...
Click to collapse
Hi sorry for not being clear. Basically I am only allowed to access the bootloader and my device is soft-bricked. I'm pretty sure I tried uninstalling and reinstalling the drivers about a year ago when I originally did it, but I'll try again and let you know. Thanks!
Hi folks,
My wife dropped her 2-week old Nexus 4 which caused part of the front glass to crack and portions of the touchscreen to be dead, so we had to send it into LG for repairs (at quite a price tag). Fine.
So we get it back, I turn it on, and it's in something called "FTM Mode" (file transfer mode, I think)? I can't seem to get it out of it.
Things I've tried:
Rebooting (have to hold the power button down for 5-10 sec).
Factory data reset (the settings are available through the notification menu in FTM Mode).
In recovery mode:
[*]Start (goes right back to FTM Mode)
[*]Power off (duh)
[*]Restart bootloader (gets me right back to the same screen)
[*]Recovery mode (gives me a little android with its stomach open, a red exclamation point, and says "No command.")
I attempted LG support, but they asked me to do a few of these (after asking me to hit the "home" button...), then told me to mail it back to them because they probably have to flash it.
So, the obvious question: how the hell can I get out of FTM Mode?
Secondary question: if none of the above worked and I do have to flash the OS, can I flash it myself to default Jellybean? Any idiot-friendly step-by-step guides out there?
Here you are! (I was the one talking to you on Reddit)
Since you can get to fastboot you can just flash the stock image files and you should be fine! The toolkit is in the original dev section but you cannot download the images from it anymore. A few people here have the images though so hopefully someone will pop up with them shortly
Sent from my Nexus 4 using Tapatalk 2
joshnichols189 said:
Here you are! (I was the one talking to you on Reddit)
Since you can get to fastboot you can just flash the stock image files and you should be fine! The toolkit is in the original dev section but you cannot download the images from it anymore. A few people here have the images though so hopefully someone will pop up with them shortly
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
Haha!
I have located an image... just need to figure out the fastboot stuff. I'm not a terribly adventurous user, you see.
Depressio said:
Haha!
I have located an image... just need to figure out the fastboot stuff. I'm not a terribly adventurous user, you see.
Click to expand...
Click to collapse
No worries! You can use the toolkit without knowing fastboot, I just recommended learning it in case you ever need to flash without it. I believe after you download the toolkit there will be a folder you can place the stock image into then you can use the toolkit to flash the image from that folder. I'm not 100% what folder that is though but I believe the name makes it fairly obvious if you look for it
Sent from my Nexus 4 using Tapatalk 2
joshnichols189 said:
No worries! You can use the toolkit without knowing fastboot, I just recommended learning it in case you ever need to flash without it. I believe after you download the toolkit there will be a folder you can place the stock image into then you can use the toolkit to flash the image from that folder. I'm not 100% what folder that is though but I believe the name makes it fairly obvious if you look for it
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
Unfortunately, I haven't even been able to install the bloody USB driver, so fastboot/adb can't even see the device. I've described by problem here. I think the source issue is what LG did during repairs... the device is named "Full JellyBean on Mako" instead of something like "Nexus 4", so the drivers in that post aren't being recognized by Windows as valid for the device. At least that's my guess.
OK, got it all fixed.
This post was incredibly useful. Once I got the USB drivers installed and fastboot recognizing the device (oddly, adb wasn't able to), it was extremely smooth unlocking the bootloader and flashing the image.
Thanks!
Depressio said:
OK, got it all fixed.
This post was incredibly useful. Once I got the USB drivers installed and fastboot recognizing the device (oddly, adb wasn't able to), it was extremely smooth unlocking the bootloader and flashing the image.
Thanks!
Click to expand...
Click to collapse
For future reference ADB only works in recovery and when booted into android, never in boot loader. Bit glad you got it working
Sent from my Nexus 4 using Tapatalk 2
drives
Depressio said:
OK, got it all fixed.
This post was incredibly useful. Once I got the USB drivers installed and fastboot recognizing the device (oddly, adb wasn't able to), it was extremely smooth unlocking the bootloader and flashing the image.
Thanks!
Click to expand...
Click to collapse
how did you can install the adb drivers,have same problem
ramonrecio said:
how did you can install the adb drivers,have same problem
Click to expand...
Click to collapse
plug your phone into your computer, then restart it in bootloader mode. the drivers will automatically install
same
hi,thank you,ok i can go to fastboot mode and select restart bootloader but when i hit power ,they turn off for a second and go back to fastboot mode initial page ,the pc do the sound when disconnect and connect back to usb pc,but that's it,no drivers installation ,what can i do!! this make me crazy,please help
Hi all,
Totally new to android and just recieved my new n10 yesterday.
I tried to root it and have got stuck at the google writing at the start. The computer is no longer regonising my device so i cant adb or odin to it, im pretty much stuck now and need your expert help
thanks,
steve
https://developers.google.com/android/nexus/images#instructions
Download factory image, extract the folder. Copy fastboot.exe and AdbWinApi.dll to the extracted folder. Connect your Nexus 10 and boot it into fastboot by holding down all buttons at the same time for a few seconds. Then double click the "flash-all.bat script.
Just tried that and just get <waiting for device>
I dont seem to have any connection with the pc anymore;/
Steve
technocra said:
Just tried that and just get <waiting for device>
I dont seem to have any connection with the pc anymore;/
Steve
Click to expand...
Click to collapse
If the N10 can go into fastboot, it's fixable
You probably just have to reinstall the ADB drivers. If you've used a toolkit... I would get rid of it and get the latest USB drivers from Android SDK (version 7). You'll also likely have to uninstall any driver relating to ADB from Device Manager.
technocra said:
Just tried that and just get <waiting for device>
I dont seem to have any connection with the pc anymore;/
Steve
Click to expand...
Click to collapse
I have a Android 1.0 in device manager
espionage724 said:
If the N10 can go into fastboot, it's fixable
You probably just have to reinstall the ADB drivers. If you've used a toolkit... I would get rid of it and get the latest USB drivers from Android SDK (version 7). You'll also likely have to uninstall any driver relating to ADB from Device Manager.
Click to expand...
Click to collapse
Ok android 1.0 has now become android bootloader interface but it still will not fastboot from recovery it just says waiting for device;/
Cheers,
Steve
technocra said:
Ok android 1.0 has now become android bootloader interface but it still will not fastboot from recovery it just says waiting for device;/
Cheers,
Steve
Click to expand...
Click to collapse
Make sure you're actually in the right bootloader.. BOTH volume buttons have to be held down while powering on. You know you're in the right one if you can hit volume up and down and switch between "Start/Recovery/Bootloader".. If your only option is "start" and nothing else you didn't do it right.
styckx said:
Make sure you're actually in the right bootloader.. BOTH volume buttons have to be held down while powering on. You know you're in the right one if you can hit volume up and down and switch between "Start/Recovery/Bootloader".. If your only option is "start" and nothing else you didn't do it right.
Click to expand...
Click to collapse
Yes
I managed to finally restore with a toolkit with the option of if it was soft bricked
I wanna thank all you guys for your help, I dont think I will root now until i get to grasps more with the deeper concepts of Android
Cheers
Steve
Hey everyone!
Just a few days after ordering a different phone which should get here tomorrow, I managed to drop my N4 and shatter the screen. The screen 'works' but the digitizer's broken below the crack so I can't get past the lock screen. I'm running Cyanogen mod and I honestly just want to get a few files off and update a few things onto drive so I can move to my new phone.
I was really hoping USB OTG would work, but I tried an external mouse with the right cable and the cursor wasn't showing up.
I don't think I have debugging mode enabled unless it carries forward if you update cyanogen. I do have CWM recovery 6.0.5.1. I tried mounting the drives through this, but it sadly didn't show up.
Is there any way I can enable USB OTG or get the files off without replacing the screen assembly? I tried using ADK Studio but I couldn't even get the command prompt open... If anyone has a link to a good walkthrough for this or suggestions for what I can do I'd be really grateful. Is there any way to force the USB OTG driver onto the phone? If I can use a USB keyboard/mouse combo to get everything off that would be the simplest way I think. Or if there's some way to get into the phone and have the display show up through my monitor, then that'd be great too.
Thanks a lot. I really appreciate any help.
You could try flashing twrp in place of cwm to mount the data partition.
audit13 said:
You could try flashing twrp in place of cwm to mount the data partition.
Click to expand...
Click to collapse
I can hit mount and unmount through CWM but nothing seems to happen. Nexus shows up as an empty device.
How would i flash TWRP at this point? Is there a way to push a zip into the phone if I can't get into it?
ridethecliche247 said:
I can hit mount and unmount through CWM but nothing seems to happen. Nexus shows up as an empty device.
How would i flash TWRP at this point? Is there a way to push a zip into the phone if I can't get into it?
Click to expand...
Click to collapse
If your physical buttons work then simply boot into fastboot by holding volume down and power and flash a TWRP recovery via fastboot. I've never had luck with CWM when it comes to reading files. TWRP opens up Android File Transfer right away on my Macbook when I connect it (Should do the same for Windows, not sure what OS you use)
fireball0093 said:
If your physical buttons work then simply boot into fastboot by holding volume down and power and flash a TWRP recovery via fastboot. I've never had luck with CWM when it comes to reading files. TWRP opens up Android File Transfer right away on my Macbook when I connect it (Should do the same for Windows, not sure what OS you use)
Click to expand...
Click to collapse
This seems promising, but how would I get it in via fastboot? Sorry I've never used fastboot before, but use the power+vol down command pretty often.
Would that also allow me to flash in the zip for USB otg once I'm in?
ridethecliche247 said:
This seems promising, but how would I get it in via fastboot? Sorry I've never used fastboot before, but use the power+vol down command pretty often.
Would that also allow me to flash in the zip for USB otg once I'm in?
Click to expand...
Click to collapse
Ok, you will want to be on your computer to do this. Download the latest TWRP recovery, which is here, you'll want to download the twrp-3.0.0-0-mako.img at the top of the list. You'll then have to open up fastboot in terminal/command prompt, and when you boot into your bootloader by holding volume down+power, connect your N4 and first I would type fastboot devices to make sure that your computer is recognizing that it's attached. Next type fastboot flash recovery twrp-3.0.0-0-mako.img and afterwards use the volume buttons to navigate and reboot to recovery. From there see if it connects to your computer and you can view files and if not, move forward with the USB otg. I have no experience with USB otg so I can't help you there, but hopefully this helps out at the very least!
fireball0093 said:
Ok, you will want to be on your computer to do this. Download the latest TWRP recovery, which is here, you'll want to download the twrp-3.0.0-0-mako.img at the top of the list. You'll then have to open up fastboot in terminal/command prompt, and when you boot into your bootloader by holding volume down+power, connect your N4 and first I would type fastboot devices to make sure that your computer is recognizing that it's attached. Next type fastboot flash recovery twrp-3.0.0-0-mako.img and afterwards use the volume buttons to navigate and reboot to recovery. From there see if it connects to your computer and you can view files and if not, move forward with the USB otg. I have no experience with USB otg so I can't help you there, but hopefully this helps out at the very least!
Click to expand...
Click to collapse
Ive had issues in the past trying to get the terminal to open. Do you have a link that could help?
Thanks so much!
ridethecliche247 said:
Ive had issues in the past trying to get the terminal to open. Do you have a link that could help?
Thanks so much!
Click to expand...
Click to collapse
Do you use Windows, Linux, or OS X?
fireball0093 said:
Do you use Windows, Linux, or OS X?
Click to expand...
Click to collapse
Windows.
ridethecliche247 said:
Windows.
Click to expand...
Click to collapse
Take a watch through this entire video, it's the most in depth one I can find that actually gives examples on things dealing with ADB and of course Fastboot. Make sure that the recovery .img is in the same directory that the fastboot prompts are in. If I didn't use OS X I'd walk you through it myself but I apologize there because I know the setup and way you enter commands is slightly different on Windows xD
Thank you! I'll give it a try!
ridethecliche247 said:
Thank you! I'll give it a try!
Click to expand...
Click to collapse
Just quick popping in to see how the progress is on it. Any luck at all?
fireball0093 said:
Just quick popping in to see how the progress is on it. Any luck at all?
Click to expand...
Click to collapse
I have finals next week so I was going to give it a try afterwards or if I get a study break. I'll definitely keep you posted on this thread though.
Thanks again!
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