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
I was running an August MIUIAndroid ROM release, with no other modifications.
Downloaded the latest 12/10 release and placed it on my Internal SD. Rebooted to recovery, wiped cache, wiped dalvik cache and flashed the release.
Rebooted tablet, wherein it passed the Google logo and then just stayed blank.
Pressed volume up/down and power for a few seconds, went into fastboot. Tried to go into recovery by selecting that option in fastboot menu, tablet restarts and stays at the Google logo.
Went back into fastboot, connected the tablet to my PC with a view to using mskip's toolkit. PC doesn't recognise the tablet despite drivers being present, and the tablet becomes unresponsive in fastboot mode (can't move between menu options with volume buttons and even on disconnecting USB, have to long press power to restart).
Any help would be appreciated as I'm unsure whether ASUS will honour the warranty...
You said you can still go to bootloader, then try do manual boot(fastboot boot nameofcustomrecovery.img) and restore your backup(that is if you have any).
Tapatalked from my Ace 2
Easy
Connect it to the PC (better use the one you used in the past, with all the drivers... also use the cable that came with it)
turn it on spamming the vol until you get in the screen with start, shut down and recovery.
Go to recovery and boom, you are back to recovery
dont do nothing on the pc, just the fact that its connect will enable it:good:
Thank you for both of your replies.
This is what I did:
Connected my Galaxy Nexus to PC
Switched on USB Debugging, ADB drivers got auto-installed
Rebooted Galaxy Nexus into Bootloader, appropriate driver got installed
Switched on Nexus 7 in Bootloader mode, started praying
Swapped the Galaxy Nexus with the Nexus 7 - this time it didn't hang
Used mskip's toolkit to flash bootloader, stock recovery and stock ROM
Reason the tablet wasn't being recognised in Bootloader mode earlier was because while I had connected it to the PC many times, I'd never had USB debugging enabled (tablet was unlocked and rooted on my laptop) and had never been in Bootloader while tablet was connected to PC. So the PC didn't know what was connected to it, and presumably due to the issues with the tablet, the PC wasn't able to recognise it and download the drivers...
*huge sigh of relief* Thanks again guys!
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!
Hello Everyone,
I have an issue with my nexus 6p screen all of a sudden being unresponsive to touch. The big error on my part was not setting up my videos and images to automatically backup. So now what i'm trying to do is unlock the phone using ADB and a usb cable but haven't had any luck. I've gotten as far as listing my devices, which show up an unauthorized and seem I can only authorize it from my phone. Q1. is this true? Could there be any other way to authorize my phone, or am I out of luck and my data is kaput? I've also tried an OTG cable but it doesn't load since i'm guessing the OS has to fully load for the cable work.
Do I have any choice on saving my data with a USB cable and command line or can someone suggest a tool that would help me out of this situation?
Put it into fastboot/download mode and flash the latest TWRP recovery.
Use TWRP's file manager or ADB Pull commands to pull your data off. Use ADB push to push a new ROM image and flash over everything except userdata (back it up just in case).
Hi, my 6p will not show up on my PC. Have tried installing drivers, different PC, different cable but nothing works.
I recently upgraded to android O. I extracted the files from system image and flashed boot image, vendor image, and system. But now when I try to go into recovery it says no command and I lost root access but my bootloader is unlocked. I never flashed the recovery thinking TWRP would stay intact but I guess I was wrong. Normally I would just use ADB and fix it but hence my problem. Is there any way to root without PC or any way I can fix my situation?
Having the same exact issue here, hope someone has a way to fix it.
sonysingh1983 said:
Hi, my 6p will not show up on my PC. Have tried installing drivers, different PC, different cable but nothing works.
I recently upgraded to android O. I extracted the files from system image and flashed boot image, vendor image, and system. But now when I try to go into recovery it says no command and I lost root access but my bootloader is unlocked. I never flashed the recovery thinking TWRP would stay intact but I guess I was wrong. Normally I would just use ADB and fix it but hence my problem. Is there any way to root without PC or any way I can fix my situation?
Click to expand...
Click to collapse
So your phone will boot into the OS, or not? If so, make sure USB debugging is set to "on" in Developer Settings. Can you put your device in fastboot mode by holding down the volume down button before hitting the power button? The "no command" means you are in (stock) recovery. You then have to hold the power button down while using the volume buttons to navigate. Power button is confirm. Get your phone into bootloader mode and use ADB to flash TWRP again. @meoshe
v12xke said:
So your phone will boot into the OS, or not? If so, make sure USB debugging is set to "on" in Developer Settings. Can you put your device in fastboot mode by holding down the volume down button before hitting the power button? The "no command" means you are in (stock) recovery. You then have to hold the power button down while using the volume buttons to navigate. Power button is confirm. Get your phone into bootloader mode and use ADB to flash TWRP again. @meoshe
Click to expand...
Click to collapse
Yes phone is working fine. Debugging is on. Can't use ADB phone does not get recognized by PC, only charges. Dint even get the pull down notification once I connect usb. Tried changing connection to mtp in developer options also. Nada. Nothing works to fix it. I'm thinking my charging port might have something wrong with it I don't know. I'm stuck not having root atm.
sonysingh1983 said:
Yes phone is working fine. Debugging is on. Can't use ADB phone does not get recognized by PC, only charges. Dint even get the pull down notification once I connect usb. Tried changing connection to mtp in developer options also. Nada. Nothing works to fix it. I'm thinking my charging port might have something wrong with it I don't know. I'm stuck not having root atm.
Click to expand...
Click to collapse
Gotcha. What about the other points? Entering bootloader mode from a powered off state, and that you are in Recovery mode (no command), and navigating thru it with the power+volume buttons?
v12xke said:
Gotcha. What about the other points? Entering bootloader mode from a powered off state, and that you are in Recovery mode (no command), and navigating thru it with the power+volume buttons?
Click to expand...
Click to collapse
Yes that works. Thank you. But still can't root phone and can't flash TWRP. Was looking at a root APK but not sure if they will work with O. If I could root then I could install TWRP thru it's app but I need root for that.
You can't root the phone until you have a working custom recovery. Focus on either fastboot flashing or fastboot booting TWRP.img
v12xke said:
You can't root the phone until you have a working custom recovery. Focus on either fastboot flashing or fastboot booting TWRP.img
Click to expand...
Click to collapse
How do I go about fastboot booting TWRP image?
I can get into bootloader from phone but I can't use a PC.
I did read your OP, but this sounds like a driver issue. There are two drivers that need to be installed first the USB and then fastboot. Since you can boot the device and use it, maybe you should try NRT by Wugfresh to install, test and confirm the drivers are properly installed. Booting or flashing TWRP is just a different command. Instead of fastboot flash recovery twrp.img, you use fastboot boot recovery recovery.img. The NRT toolkit can also either boot or flash a recovery image.
EDIT: Also try "Revoking ADB debugging" and re-enabling @sonysingh1983
sonysingh1983 said:
Yes phone is working fine. Debugging is on. Can't use ADB phone does not get recognized by PC, only charges. Dint even get the pull down notification once I connect usb. Tried changing connection to mtp in developer options also. Nada. Nothing works to fix it. I'm thinking my charging port might have something wrong with it I don't know. I'm stuck not having root atm.
Click to expand...
Click to collapse
Hi, just tried the mtp setting in developer options. Didn't get it the first time but now am able to access internal storage. I have plug sound app from play installed and I get a notification sound when plugging and unplugging. First try there was no sound when changing from charging to mtp. Ok after repeating it. Hope that helps.
Just as a follow up I got my win10 pc to recognize my O flashed nexus. I booted into bootloader after I had updated my sdk and drivers through android studio. It recognized the phone but nothing was happening. I rebooted into the os and the access allow prompt popped up on the phone and adb was able to see it under listed devices.