Hi,
I. Have gotten myself into quit a frustrating situation. My nexus 7 was unlocked, rooted and had several different custom roms installed at various times and had never had a problem. But then one time in particular, when trying to flash a rom (which I can't even remember which one it was,) after the rom had "successfully" been flashed, it rebooted to the splash screen, which it stayed at for a very long time; before just turning into a series of flashing vertical lines that never end. I can use the power+vol- method to get to fastboot, but not recovery; it would appear that my recovery has been wiped as I get the same google splash screen loop as when I try to boot. My problem is that nothing I do allows me to successfully connect the device to my pc (w7, 32bit.)
I have uninstalled any conflicting drivers, un/re-installed the proper drivers from like 7 different guides, I have also tried two different nexus root toolkits. I even tried to use a Linux machine to no avail. I have switched USB cables, everything I have tried has not worked. This is by no means my first foray into android devices, I even freshly installed my android SDK and still my computer just fails to recognize the nexus 7 in fastboot mode.
Any tips or advice would be a godsend. Thanks.
This sounds like a issue a few people have been having.. As far as i know as of a week ago there is no solution . You need to flash the boot-loader it sounds like. There is a thread about this. Search for NV FLASH .. OR APX MODE. Sorry for being lazy and not looking for the thread for you..
They may have some things in that thread that you have not tried.
Turn your Nexus off and plug it into your computer. Does your Nexus start charging? A completely bricked Nexus wouldn't charge. If it starts charging, then try turning it on into Fastboot mode.
Sorry, I'm no dev. Just a random thought to try. But if your Nexus can charge you shouldn't be fully bricked, hopefully. At least this is what I think.
When you say your computer fails to recognise the device...
If you open your device manager in Windows and then plug in the nexus 7 in fastboot mode, what happens? Does it show up in the device manager in any category? Even with a yellow exclamation mark or as unknown device?
Sent from my Nexus 7 using Tapatalk 2
My bro bricked his N7
He was rooted and unlocked, flashed a rom now it bootloops on the logo. Now when doing adb devices, it doesnt detect the device when in bootloader, went to device manager and shows problem with driver. Tried other drivers but says its up to date. Thing is I just upgared his friends N7 with the same drivers so I know thats not a problem.
It wont go into recovery either. Now when it is bootlooping, the decive is recognised when doing adb devices. So can I flash a factory image when it is bootlooping or does it have to be in fastboot?
TRY THIS
from powered down,
hold VOL- and POWER for ten seconds,. then let go of POWER and still hold down VOL-
dramdrum said:
When you say your computer fails to recognise the device...
If you open your device manager in Windows and then plug in the nexus 7 in fastboot mode, what happens? Does it show up in the device manager in any category? Even with a yellow exclamation mark or as unknown device?
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
it doesn't even acknowledge that I plugged anything in to the computer at all.
chismay said:
TRY THIS
from powered down,
hold VOL- and POWER for ten seconds,. then let go of POWER and still hold down VOL-
Click to expand...
Click to collapse
Just goes to bootloader?
Edit seems to be working now even though when doing adb devices in fastboot it doesnt list the device id
In fatboot mode you don't have adb access - down load a recovery image and name recovery.img
Hold shift and right click in the folder recovery.img is in
Choose open command here, in cmd type
fastboot devices
If you see your serial number proceed
fastboot flash recovery recovery.img
When finished reboot to recovery and flash rom of choice
ps, you have had to either change your path in enviromental variables to include platform-tools from the sdk or have both fastboot.exe and recovery.img in the same folder that cmd is pointed to
Sent from my HTC Vision using xda premium
Related
Hi guys, after restoring from a backup I made in CWM - which apparently was corrupted - I can't boot past the "X" boot animation, and because of the glitch in the bootloader, I cannot boot to recovery, which would at least allow me to flash a clean ROM. At any rate, I tried to boot to recovery from my computer, but I keep getting "error: device not found" errors from ADB and the Nexus 7 ToolKit (which uses ADB anyway). I have tried all possible scenarios with drivers, but to no avail. I can only assume that debugging is disabled. Is this a reasonable assumption, and if it is true, am I completely screwed out of $250, or is there something I can do?
SpaceToast7 said:
Hi guys, after restoring from a backup I made in CWM - which apparently was corrupted - I can't boot past the "X" boot animation, and because of the glitch in the bootloader, I cannot boot to recovery, which would at least allow me to flash a clean ROM. At any rate, I tried to boot to recovery from my computer, but I keep getting "error: device not found" errors from ADB and the Nexus 7 ToolKit (which uses ADB anyway). I have tried all possible scenarios with drivers, but to no avail. I can only assume that debugging is disabled. Is this a reasonable assumption, and if it is true, am I completely screwed out of $250, or is there something I can do?
Click to expand...
Click to collapse
Can you get to fastboot if you have the USB plugged in? If so you can use it to restore stock with the factory images from Google.
I managed to use the fastboot method to solve the problem. Everything went nicely for about a day, and just an hour ago my soft navigation buttons stopped responding to touch. A factory reset from the device did not resolve the problem. I'm going to try some work in ADB once I get access to a proper windows computer, but that may not be for a while, is there anything that might work that doesn't require a computer in the meantime? (I'm clueless when it comes to Linux. I tried installing Java and the Android SDK using a LiveCD of Ubuntu, but my efforts were met with frustration.)
You can just put windows on through a disk rather than buying a PC
Sent from my Nexus 7 using xda app-developers app
Nah, I have a fully functional custom rig, but windows killed itself and my cracked disk image of the install disk is on the same hard drive on the same partition. I'm waiting for my SSD to come in, so I can install Mint on it and burn the iso on my hard drive from there, then install Windows on my SSD.
At any rate, I used my friend's computer to flash to stock from fastboot and it didn't fix anything. Now, every time i try to touch the screen it just pulls the notification bar down to that point on the screen. I'm ready to re-lock my bootloader and bring it back to the store if nobody has a more convenient solution.
UPDATE: I rebooted from there and I'm back where I was in the last post. My navigation buttons at the bottom don't work, and sometimes touches don't register on the rest of the screen. The lock screen also doesn't respond to touch either.
ADB commands only work when its on. Fastboot boot commands when in bootloader.
Or just plug the N7 into the PC, hold down all the buttons to boot into fastboot, then select recovery. It has to be plugged in to the PC to get into ClockworkMod.
Sent from my Nexus 7 using xda premium
player911 said:
ADB commands only work when its on. Fastboot boot commands when in bootloader.
Or just plug the N7 into the PC, hold down all the buttons to boot into fastboot, then select recovery. It has to be plugged in to the PC to get into ClockworkMod.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
But I'm not attempting to do anything in ADB, unless there is some way I can use ADB to fix my nav bar and lockscreen.
UPDATE: It seems the lockscreen is working. Also, my navigation bar sometimes feels like activating buttons without me touching them.
UPDATE 2: And just like that my lockscreen isn't responding to touch again.
Bump?
can we launch fast boot while in recovery cause mine n7 always boot into clockwork recovery, i can not boot into my rom
Plugged in device. Drivers loaded. Turned off tablet. Restarted into bootloader (both volume buttons held, hold power until vibrate)
In cmd prompt, navigate to folder with fastboot.
typed "fastboot devices" (without quotes) and it returned nothing. Shouldn't it return the device ID or something?
All I want is to unlock my bootloader and root the device!
No search has helped me. Hopefully someone hear can!
Are you sure the ADB driver was installed for the device? Try reading through this:
http://trevorsullivan.net/2012/07/03/forcibly-installing-the-android-usb-driver-in-windows-7/
couple things to try
As silly as it sounds with modern computers, but make sure you are plugging into the back of your PC rather than a a usb port on the front.
Also, even if fastboot devices comes back blank, try typing the fastboot oem unlock anyways. 9/10 times my computer comes up empty when I query for the device but then am able to flash recovery, unlock etc with no prob
Blueback22 said:
Plugged in device. Drivers loaded. Turned off tablet. Restarted into bootloader (both volume buttons held, hold power until vibrate)
In cmd prompt, navigate to folder with fastboot.
typed "fastboot devices" (without quotes) and it returned nothing. Shouldn't it return the device ID or something?
All I want is to unlock my bootloader and root the device!
No search has helped me. Hopefully someone hear can!
Click to expand...
Click to collapse
Blueback22 said:
Plugged in device. Drivers loaded. Turned off tablet. Restarted into bootloader (both volume buttons held, hold power until vibrate)
In cmd prompt, navigate to folder with fastboot.
typed "fastboot devices" (without quotes) and it returned nothing. Shouldn't it return the device ID or something?
All I want is to unlock my bootloader and root the device!
No search has helped me. Hopefully someone hear can!
Click to expand...
Click to collapse
As mentioned in the above post... I've had a handful of devices that won't return a fastboot id, however they except commands just fine.
dannymac77 said:
As silly as it sounds with modern computers, but make sure you are plugging into the back of your PC rather than a a usb port on the front.
Also, even if fastboot devices comes back blank, try typing the fastboot oem unlock anyways. 9/10 times my computer comes up empty when I query for the device but then am able to flash recovery, unlock etc with no prob
Click to expand...
Click to collapse
Thank you to everyone for your help.
First thing I did was force the driver. It was showing up under mobile devices as Nexus 10, but I pushed the Google USB drivers anyway
This didnt help show the device ID when using fastboot devices, but I followed the above instructions anyway and it unlocked.
It's now at the X boot screen and taking a while. I hope I'm not in a boot loop. I dont know why I would be as all I did was unlock the bootloader and going to give it another minute before I reboot.
OK. It did boot loop. To fix this, follow this video to do a factory reset:
http://youtu.be/T1Se7Hr9Cww
I had the same issue as you with my Galaxy Nexus recently, and force installing the USB drivers does the trick every time. I think it has to do with Windows seeing the device as a media device (external MP3 player, or similar), rather than as an ADB interface. That's why you have to tell it to forcefully install the ADB driver, so it can talk ADB, rather than treating it as a media device.
Glad you got it working. Cheers
OKay I cannot for the life of me get this to work at all. I have never had a problem unlocking an HTC device, but anytime it comes to a samsung it doesn't work. I've tried the steps listed here, I've watched a video guide on unlocking from another post, I have the SDK updated, it sees the device as Android Bootloader Interface in Device Manager, I've rebooted straight to bootloader on the tablet, I've tried two different USB ports in the rear, fastboot will not read this device or give it commands at all. No reboot, no unlock, nothing. I'm seriously starting to freak out here. Been at this for 2 and a half hours now.
Varekai said:
OKay I cannot for the life of me get this to work at all. I have never had a problem unlocking an HTC device, but anytime it comes to a samsung it doesn't work. I've tried the steps listed here, I've watched a video guide on unlocking from another post, I have the SDK updated, it sees the device as Android Bootloader Interface in Device Manager, I've rebooted straight to bootloader on the tablet, I've tried two different USB ports in the rear, fastboot will not read this device or give it commands at all. No reboot, no unlock, nothing. I'm seriously starting to freak out here. Been at this for 2 and a half hours now.
Click to expand...
Click to collapse
I'm sure you did this right, but let's walk through the steps again anyway...
1) turn on tab and plug into USB do windows can install drivers
2) force ADB drivers according to link at the beginning of this thread
( it wouldn't hurt to reboot windows between steps 2 and 3)
3) shutdown tab and lead into boot loader
- do this by holding down all buttons while tab is off. When it vibrates, let go of power button until boot loader comes up
4) make sure USB is connected to back of PC and to tab
5) open terminal by going into start menu and typing CMD
6) change directory to location of fastboot
7)type fastboot devices
8) if ID comes up, you're home free. If nothing comes up, try step 9 anyway
9) type fastboot OEM unlock
10) follow instructions on tab screen
Let us know if any step failed.
Sent from my Galaxy Nexus using Tapatalk 2
pcgeek86 said:
I had the same issue as you with my Galaxy Nexus recently, and force installing the USB drivers does the trick every time. I think it has to do with Windows seeing the device as a media device (external MP3 player, or similar), rather than as an ADB interface. That's why you have to tell it to forcefully install the ADB driver, so it can talk ADB, rather than treating it as a media device.
Glad you got it working. Cheers
Click to expand...
Click to collapse
I had to do this with the Nexus 10, as well, after messing with it for a while.
Sent from my Galaxy Nexus using Tapatalk 2
Blueback22 said:
I'm sure you did this right, but let's walk through the steps again anyway...
1) turn on tab and plug into USB do windows can install drivers
2) force ADB drivers according to link at the beginning of this thread
( it wouldn't hurt to reboot windows between steps 2 and 3)
3) shutdown tab and lead into boot loader
- do this by holding down all buttons while tab is off. When it vibrates, let go of power button until boot loader comes up
4) make sure USB is connected to back of PC and to tab
5) open terminal by going into start menu and typing CMD
6) change directory to location of fastboot
7)type fastboot devices
8) if ID comes up, you're home free. If nothing comes up, try step 9 anyway
9) type fastboot OEM unlock
10) follow instructions on tab screen
Let us know if any step failed.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I've done every one of those steps to the T. Rebooted multiple times, tried different USB cables, tried every port in the back, plus both up front just for extra measure. USB port works on the tab because I'm transferring media files to it right now, it recognizes as an ADB device, drivers were also force installed from SDK Toolkit, but it won't take commands, not reboot, not ID, and certainly not unlock. The only other thing I can try is using my fiance's laptop and see if for some reason it's just an issue with my PC, because if not then it's an issue with the tablet, for whatever reason, and not being able to root this is not an option for me.
Varekai said:
I've done every one of those steps to the T. Rebooted multiple times, tried different USB cables, tried every port in the back, plus both up front just for extra measure. USB port works on the tab because I'm transferring media files to it right now, it recognizes as an ADB device, drivers were also force installed from SDK Toolkit, but it won't take commands, not reboot, not ID, and certainly not unlock. The only other thing I can try is using my fiance's laptop and see if for some reason it's just an issue with my PC, because if not then it's an issue with the tablet, for whatever reason, and not being able to root this is not an option for me.
Click to expand...
Click to collapse
If you'd like, I can remote into your computer and walk through it with you to see if I can help in anyway. Let me know.
I will PM you my phone number so you can text me if you want to try this.
I am presently having the EXACT same problem. I have a Mac mini (mountain lion) and Windows 8 (vmware). Under osx I follow all the steps and similarly I can't get fastboot to give me the ID or recognize the unlock command. In Windows it recognizes the tablet when it's booted up normally. But with fastboot in the cmd prompt I get the exact same results as in osx.
P.s. I also had the same issue with my Samsung galaxy 3. Wound up having to root it at a friend's house.
Sent from my SPH-L710 using xda premium
Blueback was able to solve all my woes, thanks!
verusevo said:
I am presently having the EXACT same problem. I have a Mac mini (mountain lion) and Windows 8 (vmware). Under osx I follow all the steps and similarly I can't get fastboot to give me the ID or recognize the unlock command. In Windows it recognizes the tablet when it's booted up normally. But with fastboot in the cmd prompt I get the exact same results as in osx.
P.s. I also had the same issue with my Samsung galaxy 3. Wound up having to root it at a friend's house.
Sent from my SPH-L710 using xda premium
Click to expand...
Click to collapse
I just fixed this for the other guy. What is the file path of your fastboot.exe file?
Its in user/downloads/root. on both my osx/windows drives.
Sent from my SPH-L710 using xda premium
verusevo said:
Its in user/downloads/root. on both my osx/windows drives.
Sent from my SPH-L710 using xda premium
Click to expand...
Click to collapse
In your windows VM, is it inside of the Android SDK/Platform-Tools/ folder?
Sent from my Galaxy Nexus using Tapatalk 2
No its on the virtual C: drive in the downloads/root folder. Root being the folder I created to extract all relevant unlocking rooting files to
Sent from my Nexus 10 using XDA Premium HD app
verusevo said:
No its on the virtual C: drive in the downloads/root folder. Root being the folder I created to extract all relevant unlocking rooting files to
Sent from my Nexus 10 using XDA Premium HD app
Click to expand...
Click to collapse
Download and install the Android SDK. Use the fastboot tool that is inside of the Android SDK/platform-tools/ folder. I can almost guarantee success.
My win 7 didn't recognize my n10 fastboot too, so I went into device manager and updated the android 1.0 or something by selecting the main SDK folder in the android SDK as an update source
Same for adb
Sent from my Nexus 10 using XDA Premium HD app
Hi Guys/girls
I received my nexus 7 today (its lovely!) and then proceeded to attempt to root it so I can change the dpi etc.
I unlocked the bootloader using the Nexus 7 toolkit and that worked fine.
I then went to do the one click to root/flash etc and then got stuck on downloading boot.img.
After leaving it for a few hours I gave up and the nexus booted straight back into the os.
My next attempt was to root using the su binarys via fastboot. This again failed on sending the file. I also noticed that my device is locked at fastboot mode when the usb cable is plugged in, e.g the up/down doesn't work unless I unplug the cable. I have tried different cables and a different PC!
My next step was then to use the toolkit to reset back to factory incase I had screwed something up, so this deleted the bootloader etc as it should and then froze on sending the .img across.
I now have a un responsive fastboot when usb is plugged in and no recovery or bootable tablet, any hints/solutions?
Thanks
herghost said:
Hi Guys/girls
I received my nexus 7 today (its lovely!) and then proceeded to attempt to root it so I can change the dpi etc.
I unlocked the bootloader using the Nexus 7 toolkit and that worked fine.
I then went to do the one click to root/flash etc and then got stuck on downloading boot.img.
After leaving it for a few hours I gave up and the nexus booted straight back into the os.
My next attempt was to root using the su binarys via fastboot. This again failed on sending the file. I also noticed that my device is locked at fastboot mode when the usb cable is plugged in, e.g the up/down doesn't work unless I unplug the cable. I have tried different cables and a different PC!
My next step was then to use the toolkit to reset back to factory incase I had screwed something up, so this deleted the bootloader etc as it should and then froze on sending the .img across.
I now have a un responsive fastboot when usb is plugged in and no recovery or bootable tablet, any hints/solutions?
Thanks
Click to expand...
Click to collapse
yes, actually : D
download this
http://forum.xda-developers.com/showthread.php?t=1809195
if you dont have that one.
pick your device from the list.
install the drivers for your device with device unplugged
make sure the device is fully off
plug in into the computer and hold down the power and volume buttons
windows should pop up saying nexus 7 bootloader driver successfully installed and then you can use the whole fastboot menu thing without a problem and reboot to recovery or whatever.
my suggestion is to install twrp recovery project 2.x.x.x
oh yeah, its a bug with the bootloader that it freezes when you plug the usb cable into the wall or a computer without the proper drivers
jombo2323 said:
yes, actually : D
download this
http://forum.xda-developers.com/showthread.php?t=1809195
if you dont have that one.
pick your device from the list.
install the drivers for your device with device unplugged
make sure the device is fully off
plug in into the computer and hold down the power and volume buttons
windows should pop up saying nexus 7 bootloader driver successfully installed and then you can use the whole fastboot menu thing without a problem and reboot to recovery or whatever.
my suggestion is to install twrp recovery project 2.x.x.x
oh yeah, its a bug with the bootloader that it freezes when you plug the usb cable into the wall or a computer without the proper drivers
Click to expand...
Click to collapse
Thanks for your reply, thats what I did in the first place! Removed and tried again but same issue
herghost said:
Thanks for your reply, thats what I did in the first place! Removed and tried again but same issue
Click to expand...
Click to collapse
you are 100% positive you did EXACTLY what i said?
I have no idea what went wrong
That's the problem with toolkits though. People don't know what they're doing and when something goes wrong you don't know how to fix it!! I understand where toolkits come from, but they are only useful if you know what happens in the background when you click on a button.
Thread Moved
Thread belongs in Q&A. Not the Dev Forum
Post moved.
MD
I mess with several android and other devices on my notebook..
Doing so i install drivers for them and often have the exact same issue as you are having..
Do a search for a program called usbdview.. Install to your pc..
With the nexus unplugged run the program..Delete everything in the list that you do NOT HAVE plugged into your computer..Especially anything that says ADB.. OR ANDROID..
Plug in the nexus 7 refresh the list.. and delete the entries created for it..
Unplug the nexus .. reboot the pc.. Then download or use the tool kit to install the latest Adb drivers for nexus 7 ..
reboot the pc.. then plug in the nexus ..
After doing the above see if you can now use fastboot/ adb...
The above will insure its not a driver issue.Often computers get usb devices confused and causes them to hang ..
Good Luck
erica_renee said:
I mess with several android and other devices on my notebook..
Doing so i install drivers for them and often have the exact same issue as you are having..
Do a search for a program called usbdview.. Install to your pc..
With the nexus unplugged run the program..Delete everything in the list that you do NOT HAVE plugged into your computer..Especially anything that says ADB.. OR ANDROID..
Plug in the nexus 7 refresh the list.. and delete the entries created for it..
Unplug the nexus .. reboot the pc.. Then download or use the tool kit to install the latest Adb drivers for nexus 7 ..
reboot the pc.. then plug in the nexus ..
After doing the above see if you can now use fastboot/ adb...
The above will insure its not a driver issue.Often computers get usb devices confused and causes them to hang ..
Good Luck
Click to expand...
Click to collapse
You Star
Put me on the right track, my PC was basically assuming that it was my S3, in the end I removed everything with samsung in it from the registry, uninstalled all the drivers then tried again, correctly showing as a nexus and not a samsung
So I managed to bricked Nexus last night trying to flash the factory images. It wouldn't flash correctly through the Nexus Root Toolkit, due to the outdated bootloader. I tried to install the 4.2 boot loader through recovery, (as it was flashable). It it didn't work, and I can't boot into recovery as it gets stuck on the splash screen. And of course I can do anything in fastboot because the tablet freezes when I plug in USB. Anything else I can try?
Here's some quick info.
Recovery- TWRP 2.3.3.x
Bootloader- 3.3.4
ROM- CM10.1
Sent from my Rooted Nexus 4
JiG Brick USB
JiG Brick USB might help, but i don't know for sure.
AW: Soft Bricked Nexus, fastboot/bootloader non-responsive
Are you able to boot into boot loader? If yes, you are not bricked. You can flash the factory image and you can flash a new recovery.
Sent from my Nexus 7 using xda app-developers app
So I got back from school today and tried to turn it back on again, and it decided to boot up normally.
This is happening to me. I can boot the Nexus into Fastboot, but as soon as you plug in a USB it freezes and any commands sent from the PC receive only "awaiting device" in response. I can't boot into recovery, it just stays on the Google splash screen and unfortunately the ROM I was trying to install didn't work. Any advice?
Ethicistabdiel said:
This is happening to me. I can boot the Nexus into Fastboot, but as soon as you plug in a USB it freezes and any commands sent from the PC receive only "awaiting device" in response. I can't boot into recovery, it just stays on the Google splash screen and unfortunately the ROM I was trying to install didn't work. Any advice?
Click to expand...
Click to collapse
Could you please describe a bit in more details what you are doing nd what is freezing?
If you are in bootloader mode, you can send only fastboot commands to your device, nothing else, so I am wondering what is freezing ...
AndDiSa said:
Could you please describe a bit in more details what you are doing nd what is freezing?
If you are in bootloader mode, you can send only fastboot commands to your device, nothing else, so I am wondering what is freezing ...
Click to expand...
Click to collapse
What I mean is that as soon as the USB is plugged in, the bootloader on the Nexus becomes completely unresponsive, I can no longer use the volume buttons to navigate the options or the power button to progress. It appears for all intents and purposes frozen and remains so after the USB is unplugged. Commands sent from ADB while the Nexus is in the bootloader just say "awaiting device" and nothing happens and I can't see the Nexus with ADB Devices.
I may not be using the best terms, I'm assuming the bootloader is the screen where you are given the options of recovery, restart the bootloader, start and so on. That screen becomes completely frozen when the usb cable is plugged in. If I select for it to go to recovery and do not plug in the USB cable, it goes to the google splash screen and the recovery never loads. I've had this Nexus fully rommed before, it has Clockwork Mod Recovery Manager on it and I've had no trouble getting it to load previously.
I'm doing all this because I tried to install a new rom (Paranoid Android Nightlies, latest version) and it did not install properly, upon start it says gapps has stopped and the setup wizard has stopped working - the OS will not load but will just keep repeating these error messages. Thus, I'm trying to either get into recovery or send ADB commands to the tablet to fix it.
AW: Soft Bricked Nexus, fastboot/bootloader non-responsive
1.) When you are in boot loader, adb will not be able to connect to your device, you need to use fastboot instead. This command is part of the SDK and can be called from the command line. Eventually you need to add the directory containing the fastboot executable to your path.
2.) That the buttons do not respond any longer after plugging to USB is very strange.
- What bootloader version is installed on your device?
- What does fastboot devices print on the screen?
- Did you try already with a different USB-port / cable?
Sent from my Nexus 7 using xda app-developers app
AndDiSa said:
1.) When you are in boot loader, adb will not be able to connect to your device, you need to use fastboot instead. This command is part of the SDK and can be called from the command line. Eventually you need to add the directory containing the fastboot executable to your path.
2.) That the buttons do not respond any longer after plugging to USB is very strange.
- What bootloader version is installed on your device?
- What does fastboot devices print on the screen?
- Did you try already with a different USB-port / cable?
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
All fixed now. It was actually the computer, an issue with the USB, did it on my laptop and was able to fix it pretty quickly. It was you differentiating Fastboot from ADB that got me there though, I tried that on my PC and when it didn't work I then did it on the laptop. Most likely wouldn't have gotten there without you, at least not so quickly. Thank you very much!
Hi all!
First of all I would like to give small heads up - I've been searching XDA and web for two days and ended with no working solution.
Situation:
Suddenly my Nexus 7 (2012) just died. No charging signs, nothing. So i tried Google described and random hardware resets using buttons with no luck.
I ended with situation:
device is not turning on - no screen flickering, not even small amount of pixel light visible,
ADB - no devices found,
fastboot - no diveces found,
nvflash - only my GeForce PC card found
when I connect device to PC I have to hold power button for ~10sec and there I hear "boing" (USB dev. disconnected), "boing" (USB device connected) sounds.
device is visible as APX device with "!" mark
I've tried:
hardware reset by pressing: power button, power+volume's buttons for different amount of time,
taking back and disconnecting battery,
using different software to discover device,
editing driver .inf file to recognize my device as ADB device. It did but still no visibility via ADB or fastboot (URL: http://blog.dantup.com/2012/10/fixing-adb-device-not-found-with-nexus-7-in-recovery-mode/),
read and tried to use things from: http://forum.xda-developers.com/nexus-7-2013/general/rd-thread-trying-to-solve-ota-brick-t3117495.
No result at all...
One more - when I unplug and then plug in battery while having back taken I can hear sound that something is "running".
Please help!
@kepisty89 You can check here. Install the driver and check your device is detecting or not, actually you've a fried bootloader.
Tahnk you @DutchMan_1990, I tried this and now ended with my device recognized as "Asus Transformer Prime APX Interface". Nothing else happened.
Any ideas?
kepisty89 said:
Tahnk you @DutchMan_1990, I tried this and now ended with my device recognized as "Asus Transformer Prime APX Interface". Nothing else happened.
Any ideas?
Click to expand...
Click to collapse
Hi, kepisty89...
Unfortunately, APX mode is generally never good news .
It usually indicates that the Nexus 7's bootloader has either become corrupted or has been erased, and effectively hardbricking the device.
-----
See here, for a post I wrote for another XDA member with similar issues to yours, back in December 2014, where I elaborate further on this problem.
-----
I suspect your Nexus 7 will require a motherboard replacement .
Rgrds,
Ged.
I have similar issue, but mine I can get to bootloader but that's it, if I try to power it on all I get is the Google and unlock padlock, can't get to recovery, but my device is seen via fastboot ADB Wugfresh NRT, but as soon as I try to write to it ie flash files or try to restore device, ADB locks up, and when it says rebooting device my nexus tries to reboot but I get a black screen and Wugfresh says waiting for device, I have to force reboot bootloader hold power button vol down for NRT to see it again in fastboot. I can also boot tempery recovery via NRT but when I select mount it pops up on PC but I can't copy anything to it, also it says I have no OS installed.
Sent from my Nexus 6 using Tapatalk