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
Related
Ok so i tried to root my N7 and im pretty sure i screwed up because now when i enter the boot loader with the usb connected, it crashes. On my computer it says the device is not running, i can get bootloader working if its not plugged into my computer.Help plz!
Does your computer recognize the fact that it's plugged in? And if so - do you have Android Debugging installed?
If you have both of these things working you can flash the stock image and basically start over. You can either go install the Nexus toolkit or do it manually through ADB - both of those are found over in the Development section and are pretty straight forward.
Try rooting/installing CWM through the Nexus Toolkit, it's essentially foolproof save unplugging your device.
brianjr1 said:
Does your computer recognize the fact that it's plugged in? And if so - do you have Android Debugging installed?
If you have both of these things working you can flash the stock image and basically start over. You can either go install the Nexus toolkit or do it manually through ADB - both of those are found over in the Development section and are pretty straight forward.
Try rooting/installing CWM through the Nexus Toolkit, it's essentially foolproof save unplugging your device.
Click to expand...
Click to collapse
Thanks for replying so quickly. I can boot up into jelly bean, but i can't boot into boot loader.
In both the bootloader and the actual rom my computer can detect it with ADB installed; however heres the problem, when in the bootloader it gets stuck, i can't use the volume buttons i can't click anything and on my computer (inside device manager) it tells me:
This device cannot start. (Code 10)
If i don't plug in the USB i can use the boot loader, and because I can't leave the usb in while in bootloader, i can't flash anything.
*edit also i can't go into recovery mode, it just gets stuck at the google logo
bump
Have you tried to boot into the boot loader through adb?
Also, I'm pretty sure its a known issue that you can't boot into recovery from the boot loader menu. I'd suggest flashing the stock nakasi file through adb and see if that fixes it for you.
Sent from my Nexus 7 using xda app-developers app
I also had trouble getting the bootloader to operate correctly with the USB connected.
Disconnect USB
Hold down vol+, vol- and pwr to get into the bootloader
Reconnect USB once you are in the bootloader
The problem is I can't unbrick and restore my nexus to stock rom.
I can't boot the device and I'm only able to boot to bootloader. However, my computer doesn't recognize the nexus. It keeps saying Window cannot recognize it whenever I plug my tablet to the computer in bootloader. I tried uninstall and reinstall driver several times, but none of them seems to work . ----> That means I can't even use adb to restore the phone simply because my tablet is not recognized in window.
Is there anyway to fix this problem? I really need your helps as soon as possible.
Thank you for reading !
Get to bootloader. Then use Wugs toolkit, open advanced options. On the very left is something like "temp boot to recovery". Once that boots it to recovery, ADB should work. It did for me. I was in some trouble last night and got out by this. If you know how to use adb/fastboot commands, you should be good. And I uninstalled my drivers and when I plugged it in the device automagically reloaded the drivers. But you have to do it a few times. Had to do it in bootloader, recovery, and another point. Anytime it asks to load drivers/etc do it.
I can't boot to recovery through Wug Tool Kit. It keeps saying Fastboot device was not found >"<
By the way, whenever I connnected my device to computer, the bootloader freezes :|
What were you doing before you go into this situation?
I was on Glazed Jelly Bean rom and wanted to go back to stock rom. I used nexus 7 toolkit to do all the work for me. However, there was something wrong like the toolkit didnt extract the stock img right or something like that, my tablet got bootloop, and what happened next was what i had been telling you guys.
Best bet is if somehow you could get into recovery or get adb working. Might want to uninstall drivers and install again and reboot computer. I would suggest using this thread and flash things manually back to stock. http://forum.xda-developers.com/showthread.php?t=1907796 but you would need adb working.
When you power off device and use volume and power can you get it to go into boot loader then plugged into computer try to get to recovery or adb.
Consider deleting the drivers from Windows after uninstalling them otherwise Windows may try to be "clever" and reinstall the bad driver when you plug the device in. The Nexus 7 drivers from Asus can be downloaded here and Google's USB drivers are here
Travisdroidx2 said:
Best bet is if somehow you could get into recovery or get adb working. Might want to uninstall drivers and install again and reboot computer. I would suggest using this thread and flash things manually back to stock. http://forum.xda-developers.com/showthread.php?t=1907796 but you would need adb working.
When you power off device and use volume and power can you get it to go into boot loader then plugged into computer try to get to recovery or adb.
Click to expand...
Click to collapse
What if I couldn't get adb working?
I tried everything and windows still doesn't recognize my device in fastboot
Have you tried Nexus Root Toolkit v .1.5.4?
kiddo94 said:
I tried everything and windows still doesn't recognize my device in fastboot
Click to expand...
Click to collapse
try connecting to the usb port at the back of your computer
Paranoid flashed with the bricked kernel did this to me once right after the move to 4.1.2. Even with a full wipe and all the usual safety precautions it just stuck on bootloop forever and wouldn't let me in. I chalked it up as that's what I get for being the guy that's never satisfied with stock. I was unable to get my nexus7 fixed. I sent you a suggestion on pm though.
Never mind everyone. Thank you so much for your help.
I tried install the nexus 7's driver on another computer and it recognized my device in bootloader mode, and restore everything back to stock now. Thank you so much!!!!
Mine did that to the first time I tried. After I got it to work, the permissions were all messed up and I could not get it to download anything off the web and I was getting a playstore error 90% of the time as well. I finally just wiped everything on my tablet, installed the stock rom via N7 toolkit, then reflashed smooth rom, and all is working now. It may have been a bug with the older version of N7 toolkit, as I updated it before I reran everything.
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
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!
I recently bought a refurbished 2012 Nexus 7 on 4.2. The only things that I have done on the phone are entering my Google account details and downloading a single app (papyrus). I then clicked to install the automatically downloaded software update (it downloaded 4.3), and after restarting the tablet was stuck on the Nexus X boot animation forever. Factory reset/cache wipes do not help.
I found drivers for the phone to be recognized while showing the X, and I found drivers for the phone to be recognized after selecting the a "apply update from ADB" option from stock recovery. However Windows does not recognize the phone at all in recovery mode before selecting that option. Nothing changes in the device manager when plugged/unplugged. Windows doesn't attempt to install anything. It's as if I unplugged the cord once it enters recovery from the bootloader. I assume USB debugging is off, because it would be at the default setting. I tried using the Flash Stock + Unroot option in the Nexus Root Toolkit with the Soft-Bricked/Bootloop setting in, but that fails in both normal recovery (with the device unnoticed) and sideload mode. I'm guessing that debugging needs to be on for this?
Does anyone have any suggestions for other things to try? I have no way of knowing what the original owner may or may not have done, and this was the first time that I restarted the device, so I have no way to know if the problem was caused by the OTA or not.
EDIT: It looks like I made the situation worse. I attempted running the Flash Stock + Unroot option from the bootloader. I am not sure what happened, but now the device starts at the Google page with green start in an arrow. I have the bootloader options, and start and recovery options give me a "booting failed" message in the top left and just stay on the google page. Restarting the bootloader gives me the normal bootloader android image and the options have the same effects.
For anyone who runs into this problem, I seem to have at least temporarily solved it.
I followed the advice here to manually flash the factory image. I am now back to where I was when I bought the phone, and I will immediately enable debugging and test it's ability to restart, connect in recovery mode, etc now.
EDIT: It can restart normally (with the unlocked logo), but it is still completely unrecognized in recovery unless I choose the sideload option like before. Should I return the tablet?
wioneo said:
For anyone who runs into this problem, I seem to have at least temporarily solved it.
I followed the advice here to manually flash the factory image. I am now back to where I was when I bought the phone, and I will immediately enable debugging and test it's ability to restart, connect in recovery mode, etc now.
EDIT: It can restart normally (with the unlocked logo), but it is still completely unrecognized in recovery unless I choose the sideload option like before. Should I return the tablet?
Click to expand...
Click to collapse
still have a problem?
Wrong drivers, try other USB ports. Had that happen with another tablet. Only recognized in adb side load with galaxy nexus driver loading, possibly from universal adb drivers... Switched to a port on the other side and correct drivers finally worked.
Sent from my Le Pan TC1020 using Tapatalk
norwoodesteel said:
still have a problem?
Click to expand...
Click to collapse
As far as I know, no. I was never able to get the device is to be detected by my computer while in stock recovery mode, however it was detected after I flashed ClockworkMod Recovery. So I still have no idea what was causing that problem, but it is no longer relevant.