Related
Hey guys,
I've been noticing something unusual with my tablet. The stock hard-reset recovery(as well as CWM) only works with USB plugged in. When it is not plugged on the computer, it hangs on the black screen with the Google logo(when it is oem locked, there's a lock on the bottom). I am also a Galaxy S2 user so I know that I didn't need the USB plugged in, in order to enter the recovery mode.
Is this normal for the N7 tablet? or is there something wrong with it?
Thank you
kaywoo said:
Hey guys,
I've been noticing something unusual with my tablet. The stock hard-reset recovery(as well as CWM) only works with USB plugged in. When it is not plugged on the computer, it hangs on the black screen with the Google logo(when it is oem locked, there's a lock on the bottom). I am also a Galaxy S2 user so I know that I didn't need the USB plugged in, in order to enter the recovery mode.
Is this normal for the N7 tablet? or is there something wrong with it?
Thank you
Click to expand...
Click to collapse
I have the same issue, and I always thought it was just me. Going to try a different recovery when I'm back home.
cheami said:
I have the same issue, and I always thought it was just me. Going to try a different recovery when I'm back home.
Click to expand...
Click to collapse
Yeah it's weird. Even after coming back to stock, unrooted, the hard-reset via stock recovery doesn't work unless USB is plugged in. Maybe some files are missing
Wow, I'm glad I stumbled on this thread, I was going nuts trying to figure out why I couldn't boot back into CWM after going back to the stock image and applying the OTA .zips.
Confirmed, I can get it to boot into CWM from fastboot only if I have the USB cable plugged in. Otherwise it just hangs on the Google splash screen.
Weird.
I've been able to boot into recovery using the app "quickboot" which had an option to reboot into recovery. My usb cable isn't plugged in.
Sent from my Galaxy Nexus using Tapatalk 2
This sounds a bit like my Nexus S i9020. It will only go into bootloader without the usb, and only go into download mode with USB attached (although it doesn't have to be powering it). This is the same on both handsets I've used. Maybe not a 'flaw' and more a nod to using fast boot/adb?
Sent from my Nexus S using xda app-developers app
I am currently having the same problem. Did anybody come up with a fix for this?
I'm having the same issue with the nexus 7. I've found out that you can boot into recovery if you have ROM Manager installed and select reboot into recovery.
Does anyone know if this is an OS issue or recovery issue?
Interesting. Was wondering why I couldn't get into Recovery from the Bootloader.
Another bug for me is that if I boot into Bootloader with the USB connected, I cannot make any selection using the volume keys. Only works if I boot in first without USB connected, then connect once I'm booted.
Its a bug, guys learn to search in the Development threads, I'm sure its being worked on,personally I've been able to get into recovery without have to connect via USB, if all else fails you can enter recovery via USB and ADB, by issuing the command adb reboot recovery in terminal/cmd
I had the same issue last week. Not sure what changed but now I'm able to get into recovery using the reboot menu or good mngr/rom mgr. No need for usb. I'm on modaco rom and used both clockwork and twrp.
Sent from my PG86100 using xda app-developers app
I have one more problem...
When I connect USB, the keys don't work in bootloader so can't try recovery with USB cable on.
Any solution for this?
cheami said:
I have the same issue, and I always thought it was just me. Going to try a different recovery when I'm back home.
Click to expand...
Click to collapse
I have the same problem.
LTE Galaxy Nexus
Nexus 7 (16gb)
Miracle.vl63 said:
I have one more problem...
When I connect USB, the keys don't work in bootloader so can't try recovery with USB cable on.
Any solution for this?
Click to expand...
Click to collapse
There are two different versions of CWM- one uses the power and vol-up/down buttons for keys- the other used the tablets touchscreen for button press functions.
You may have installed the touch(screen) version of CWM- try using the touchscreen for controls.
Same issue here. I can get to recover either connected or via rom manager.
Sent from my MIUI Motorola Star Tac
omegajester said:
Same issue here. I can get to recover either connected or via rom manager.
Sent from my MIUI Motorola Star Tac
Click to expand...
Click to collapse
I too can get into recovery via ROM Manager. I read somewhere that pulling the battery might help. I know that's a bit of a pain on the Nexus 7, but I'm going to try that when I get home later to see if that helps.
LTE Galaxy Nexus
Nexus 7 (16gb)
Trikkenut said:
I too can get into recovery via ROM Manager. I read somewhere that pulling the battery might help. I know that's a bit of a pain on the Nexus 7, but I'm going to try that when I get home later to see if that helps.
LTE Galaxy Nexus
Nexus 7 (16gb)
Click to expand...
Click to collapse
Nope, disconnecting the battery didn't change anything. Wug Fresh (Nexus Root Toolkit developer) informed me on Google + that it's a Google issue and it should be fixed in a future update. For now i'll be either plugging in USB to computer or ROM Manager.
I can't even get into the boot loader with my usb plugged into a charger not a computer
askho said:
I can't even get into the boot loader with my usb plugged into a charger not a computer
Click to expand...
Click to collapse
Try Quick Boot
Free, easy to use, will boot to bootloader, recovery, reboot etc... requires root of course, you already have that.
i dont't have root because it was screwed up right fromt he get go
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!
When I turn my n7 on all I get is the android with the red triangle over it and underneath it says no command. I'm unable to do anything with it. When I press power & volume up all it does is dim the screen/undim it.
From what I've been reading, I think I need to load a recovery image, but when I try to load it, I'll either get a DLL error, or in command prompt it'll give me an error saying the image can't be loaded.
The DLL error is something like adbwin.dll & its frustrating because its in the sdk\tools folder, I can see it & I've tried setting environmental variables in control panel/system to the DLL path & I still can't get my system to see it. Any help would be appreciated.
I'm using windows 8 and the recovery image I tried was twrp 2.2.1. I'm missing a step somewhere I'm thinking.
No suggestions? Uggghhhh
Is there anyway to install drivers without enabling USB debugging?
Look up Wugfresh's Nexus Root Tool Kit.
Once you install all of the drivers it'll be a breeze....
danvee said:
Look up Wugfresh's Nexus Root Tool Kit.
Once you install all of the drivers it'll be a breeze....
Click to expand...
Click to collapse
Tried this already too just last night. I've tried using samsungs mobile phone drivers, asus', and the naked drivers. I can't get this thing to be recognized. its not even charging when plugged in to my PC. I've also tried it on a w8 PC & win 7 PC.
That's an entirely different issue then. Try a different cable?
danvee said:
That's an entirely different issue then. Try a different cable?
Click to expand...
Click to collapse
Tried a few. The original stock cable, a cable from my cell phone & a diffferent phone. I also tried different USB ports lol. I've tried everything I can think of. Thanks for the suggestions though. Open to more.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Have you tried to do something simple at the error screen with fastboot? For instance just do a fastboot devices? Does it return anything? Have you properly configured your PC to run adb and fastboot? Are you trying to run fastboot/adb from the directory all the files are stored in? I know this may be basic stuff to some, not sure of your level of skill, but even still professionals still can overlook something.
Here is the latest Android Composite ADB Interface Driver straight from SDK.
http://d-h.st/kDu
If you can get into bootloader then you can erase your existing partitons then flash all the images from the Nexus Factory Images package to restore your device to stock.
SlowCobra96 said:
Have you tried to do something simple at the error screen with fastboot? For instance just do a fastboot devices? Does it return anything? Have you properly configured your PC to run adb and fastboot? Are you trying to run fastboot/adb from the directory all the files are stored in? I know this may be basic stuff to some, not sure of your level of skill, but even still professionals still can overlook something.
Click to expand...
Click to collapse
I tried running cmd to check for fast boot devices but nothing came up. Tried root kit to detect & nothing is detected either. All my files are located in C:\ which is where I had fast boot pointed to.
I'd say I'm pretty noob at this. It was originally rooted & no orobs till this instant. I'm pretty positive adb/fast boot is installed correctly.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Username invalid said:
Here is the latest Android Composite ADB Interface Driver straight from SDK.
http://d-h.st/kDu
If you can get into bootloader then you can erase your existing partitons then flash all the images from the Nexus Factory Images package to restore your device to stock.
Click to expand...
Click to collapse
I think my problem is I can't get into anything on my tablet. I can't get into boot loader & I can't enable USB debugging. I'll try the drivers tho & see if it helps
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
thestrangebrew said:
I think my problem is I can't get into anything on my tablet. I can't get into boot loader & I can't enable USB debugging. I'll try the drivers tho & see if it helps
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
USB debugging is not needed to use Fastboot.
Have you tried power and down? That's how you get into recovery. I just reread the first post and you stated that you're pushing power and up volume.
Sent from my Nexus 7 using Tapatalk 4 Beta
I'm thinking along the lines of a hardware issue with the usb port...
yea I've tried power + down also. @ user name I'm unable to get into boot loader then. fast boot doesn't detect any fast boot devices
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
danvee said:
I'm thinking along the lines of a hardware issue with the usb port...
Click to expand...
Click to collapse
the device charges when plugged into the wall. not on the PC. so I'm sure its hardware. I'll try to post some screen shots later this evening.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Unplug the battery?
Sent from my Nexus 7 using Tapatalk 4 Beta
I was going to start dismantling it as a last resort, I'm thinking this wknd might be time to do it.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Hello,
This is my first time rooting anything. I have talked to several people and followed the instructions on here and it seemed pretty straightforward--Until I got stuck. I got the bootloader unlocked and the recovery is loaded correctly I think...but now my computer won't install the nexus 7 drivers that it already had installed, and therefore I can't load a rom onto it...I don't know what to do. I've tried installing the nexus 7 drivers multiple ways from multiple sites with no luck. This is a new device and I really hope it's still fixable. The attached picture is what I think is the recovery mode, which I can navigate in, I just can't communicate between my nexus and my computer. Windows 7 64-bit HP Elitebook laptop.
Thanks
You don't need the pc anymore.
Next step, reboot your tablet, and download the superuser binaries from http://download.chainfire.eu/365/SuperSU/UPDATE-SuperSU-v1.69.zip
Then reboot into recovery by holding down power and volume down together, install the superuser binaries, reboot your tablet, and you're done.
Sent from my Nexus 7 using Tapatalk 4
xdhall said:
You don't need the pc anymore.
Next step, reboot your tablet, and download the superuser binaries from http://download.chainfire.eu/365/SuperSU/UPDATE-SuperSU-v1.69.zip
Then reboot into recovery by holding down power and volume down together, install the superuser binaries, reboot your tablet, and you're done.
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
Or he can connect to his PC, use ADB and type "adb reboot recovery", just saying.
Sent from my GT-I9505G using Tapatalk
LoopDoGG79 said:
Or you can connect to your PC, use ADB and type "adb reboot recovery", just saying.
Sent from my GT-I9505G using Tapatalk
Click to expand...
Click to collapse
Unless, like the OP, you're missing the drivers (though how he got that far without them is a little hazy).
Sent from my Nexus 7 using Tapatalk 4
All of the correct drivers were there and it was completely recognized before the root. Now in device manager it shows Nexus 7 with a yellow exclamation point next to it and it won't show up in my connected devices. Because of this I can't connect from the pc. I don't know why the drivers worked and now don't. Also when I try to boot the Nexus 7 it stays on the Google 'X'
schneiderm3709 said:
All of the correct drivers were there and it was completely recognized before the root. Now in device manager it shows Nexus 7 with a yellow exclamation point next to it and it won't show up in my connected devices. Because of this I can't connect from the pc. I don't know why the drivers worked and now don't. Also when I try to boot the Nexus 7 it stays on the Google 'X'
Click to expand...
Click to collapse
You're stuck in a bootloop.
Power it down for five minutes and then try rebooting into recovery again. Use the recovery to wipe your cache and dalvik cache. Try rebooting the system again. If you're still stuck in a bootloop, go back to recovery again and wipe data/factory reset.
Sent from my Nexus 7 using Tapatalk 4
Thanks Guys! Bootloop fixed it!
So I wanted to refresh my phone from the start and in the process i did a format data wipe not knowing what it meant and now i'm stuck with no os and i cant adb sideload because any computer i go to says "driver descriptor failed" and i left usb debugging off and now i'm stuck in boot loop. Please Help !!
Nurfulous said:
So I wanted to refresh my phone from the start and in the process i did a format data wipe not knowing what it meant and now i'm stuck with no os and i cant adb sideload because any computer i go to says "driver descriptor failed" and i left usb debugging off and now i'm stuck in boot loop. Please Help !!
Click to expand...
Click to collapse
Stop and take a breath.
Right this happened to me execpt I had no idea how to use adb, download a toolkit, I used Wug Fresh but I am sure it can work in any. Then delete all the drivers for your nexus 4 and then download the universal drivers. Then perform the battery pull (push the power and volume up for 5 sec) and boot into fastboot (power + up buttons). Flash to boot with the status soft-bricked. It should boot up and good luck. :fingers-crossed:
Mubz_C said:
Stop and take a breath.
Right this happened to me execpt I had no idea how to use adb, download a toolkit, I used Wug Fresh but I am sure it can work in any. Then delete all the drivers for your nexus 4 and then download the universal drivers. Then perform the battery pull (push the power and volume up for 5 sec) and boot into fastboot (power + up buttons). Flash to boot with the status soft-bricked. It should boot up and good luck. :fingers-crossed:
Click to expand...
Click to collapse
I got passed the first step of wubfesh but i don't have usb debugging on
Nurfulous said:
I got passed the first step of wubfesh but i don't have usb debugging on
Click to expand...
Click to collapse
Stop worrying about the debugging already lol, when you boot in fastboot (volume down + power button) you do not need debugging because it is ON in fastboot
Mashed_Potatoes said:
Stop worrying about the debugging already lol, when you boot in fastboot (volume down + power button) you do not need debugging because it is ON in fastboot
Click to expand...
Click to collapse
But my wubfresh doesn't recognize m computer nor does my computer.
Nurfulous said:
But my wubfresh doesn't recognize m computer nor does my computer.
Click to expand...
Click to collapse
post some screenshots of PC
Mashed_Potatoes said:
post some screenshots of PC
Click to expand...
Click to collapse
Thanks Guys so much. I finally got it to connect and now my nexus is up and running.