Database Users

Nexus 7 unresponsive in bootloader

I've been searching while at work trying to find someone with a similiar issue and have not met any luck.
I've tried the 2 different 1 touch root programs to no avail. I am able to unlock my device fine, but once it tries to push the img for CWM the Nexus 7 becomes unresponsive. It will lock up. The only way to get out is to hold the power button until it powers off.
After a few attempts with both 1 click tools I gave up and just decided to use ADB and do it myself.
What I can do:
lock/unlock the device.
reboot to and from the boot loader.
install apk's while in the Android OS
What I cannot do:
Push any file to the Nexus 7 while in the boot loader.
Once I try to push the img for CWM the device locks up, becomes unresponsive, and the fastboot devices command does not show any devices connected anymore.
Currently using Windows 7 Ultimate x64 and OTA 4.1.1. I've tried numerous known working USB cords and the OEM cord. I've used both sets of drivers included in the 1 click root tools, the "naked" drivers, and the set of drivers that work for numerous devices.
I'm a complete newb with ADB and don't know much about it. is it possible to copy the CWM img to my internal storage and install it from the internal storage rather than pushing it over USB?
I'm currently at work, and do not have admin on this PC or I would try again and see if I have the same problem on a different system. Tonight when I get home I will try my girlfriends PC, and I do have a dual boot of linux I can try from as well. But if her PC and linux both fail I'm probably going to have to return it claiming I have display issues and get a new one.

Intentionally deleted.

Using root tool kit make sure you have stock ROM selected before you select root. Once you have stock ROM selected you should be able to root.

mcdermott1 said:
Using root tool kit make sure you have stock ROM selected before you select root. Once you have stock ROM selected you should be able to root.
Click to expand...
Click to collapse
When using either root tool, as soon as the tool starts pushing the custom recovery over the Nexus becomes completely unresponsive. The device itself locks up. At this point it does not show up as a connected ADB device anymore on my PC. I need to hard power it off and reboot for my PC to see it again.
Both tools boot it into the bootloader fine, and both tools can unlock the bootloader fine. I can do it with ADB manually as well. But as soon as any of them start actually pushing the CWM img file over that's when the Nexus locks up. Volume up/down do nothing, power does nothing, my pc doesnt recognize the device anymore either. All I can do is hard power it off by holding the power button.
At this point I'm convinced it's either some strange issue on my PC, or the nexus itself. I'll know for sure once I try it again on my girlfriends computer tonight.

roblol said:
When using either root tool, as soon as the tool starts pushing the custom recovery over the Nexus becomes completely unresponsive. The device itself locks up. At this point it does not show up as a connected ADB device anymore on my PC. I need to hard power it off and reboot for my PC to see it again.
Both tools boot it into the bootloader fine, and both tools can unlock the bootloader fine. I can do it with ADB manually as well. But as soon as any of them start actually pushing the CWM img file over that's when the Nexus locks up. Volume up/down do nothing, power does nothing, my pc doesnt recognize the device anymore either. All I can do is hard power it off by holding the power button.
At this point I'm convinced it's either some strange issue on my PC, or the nexus itself. I'll know for sure once I try it again on my girlfriends computer tonight.
Click to expand...
Click to collapse
If what your describing is when you go to push custom recovery screen locks up should be black screen with Google on it then your computer says can't find device something like that. Mine did the same thing, in the tool kit upper left corner it ask for model type, make sure you have correct Android selected. I selected custom rom by mistake and it just hung there on the black screen. It should list custom ROM, Android 4.1, or Android 4.1.1 Select what you have and it should work....hopefully.

mcdermott1 said:
If what your describing is when you go to push custom recovery screen locks up should be black screen with Google on it then your computer says can't find device something like that. Mine did the same thing, in the tool kit upper left corner it ask for model type, make sure you have correct Android selected. I selected custom rom by mistake and it just hung there on the black screen. It should list custom ROM, Android 4.1, or Android 4.1.1 Select what you have and it should work....hopefully.
Click to expand...
Click to collapse
Unfortunately not. I have selected the right options. It freezes on the bootloader screen. It never even makes it to the boot stage. I've tried to flash a recovery permanently and temporarily boot from a recovery as well. It freezes either way.
Additionally if I boot to the boot loader, and select recovery it will not boot into the stock recovery at all... It just sits at the google splash screen with the unlocked padlock.

roblol said:
Unfortunately not. I have selected the right options. It freezes on the bootloader screen. It never even makes it to the boot stage. I've tried to flash a recovery permanently and temporarily boot from a recovery as well. It freezes either way.
Additionally if I boot to the boot loader, and select recovery it will not boot into the stock recovery at all... It just sits at the google splash screen with the unlocked padlock.
Click to expand...
Click to collapse
I have the same problem on my nexus... it just freezes.

Roc1992 said:
I have the same problem on my nexus... it just freezes.
Click to expand...
Click to collapse
Did you get this fixed? I have the same issue

locked bootloader wont unlock

Hi everyone. Here is the deal im having with my nexus 7 (not the 2013 model) with jop40d.zip. The person I purchased from didnt tell me it was soft bricked. It seems as though he tried to root it but failed while at the same time relocked the bootloader. So I've tried almost everything in my mind to get it back to normal. It wont let me adb sideload the stock rom it says "installation aborted" or any other rom. Also when i boot up it goes directly to the bootloader which gives me the options start, restart bootloader, recovery mode, power off. start obviously does nothing. restart bootloader just for some reason turns the device off, recovery mode takes me the caution sign where i can adb sideload or factory restore. factory restore hangs and doesn't do anything then shuts off. adb sideload always fails when loading up the zip files. i factory restored the cache. I'm not sure what to do anymore. I spent a fair amount of money on this device but now it all seems like a mistake. Can anyone who has fixed this issue help me out? I would deeply and greatfully appreciate it.
-Cheers

truebattleaxe said:
Hi everyone. Here is the deal im having with my nexus 7 (not the 2013 model) with jop40d.zip. The person I purchased from didnt tell me it was soft bricked. It seems as though he tried to root it but failed while at the same time relocked the bootloader. So I've tried almost everything in my mind to get it back to normal. It wont let me adb sideload the stock rom it says "installation aborted" or any other rom. Also when i boot up it goes directly to the bootloader which gives me the options start, restart bootloader, recovery mode, power off. start obviously does nothing. restart bootloader just for some reason turns the device off, recovery mode takes me the caution sign where i can adb sideload or factory restore. factory restore hangs and doesn't do anything then shuts off. adb sideload always fails when loading up the zip files. i factory restored the cache. I'm not sure what to do anymore. I spent a fair amount of money on this device but now it all seems like a mistake. Can anyone who has fixed this issue help me out? I would deeply and greatfully appreciate it.
-Cheers
Click to expand...
Click to collapse
also I wanted to add. I have the android sdk installed and all drivers installed properly. as well as adb/fastboot.

Stop trying to use adb, follow the sticky at the top that says flashing a factory rom using fastboot/return to stock. If you can't type fastboot devices and get a serial number return then the drivers are not installed properly.
Sent from my Nexus 7(2012) that has zero issues.

SlowCobra96 said:
Stop trying to use adb, follow the sticky at the top that says flashing a factory rom using fastboot/return to stock. If you can't type fastboot devices and get a serial number return then the drivers are not installed properly.
Sent from my Nexus 7(2012) that has zero issues.
Click to expand...
Click to collapse
hey slow cobra. yes fastboot does recognize the device. however fastboot oem unlock doesn't do anything.

[Q] Rooted Nexus 10 Stuck in Bootloop, Please Help!

Hello all,
Any help with this would be seriously appreciated. I rooted my Nexus 10 a while back, maybe two years ago. I'm not very proficient with this stuff. Anyhow I decided to do the OTA upgrade to 5.0...I was concerned something would go wrong unless I went to stock first, but I read that the only thing that would happen is root would be removed.
Anyhow, the tablet appears stuck while booting. I see the Google screen first with the unlocked indicator on the bottom. A few seconds later is the Android logo on its back, a red triangle over it with an exclamation point and "no command" written below". It stays that way for a minute or so, tries to reboot and goes back to the no command screen. I can't even power off, when I try to do so it just powers back on by itself and ends up at the no command screen again.
I tried booting into recovery (power, volume up, volume down). My options from here are either Start, Restart Bootloader, Recovery Mode or Power Off. Every option I choose leads to the No Command Screen (except power off, which powers off). No idea what to do from here.
Any help at all would be appreciated. As you can probably tell I don't have much experience with this and just wanted to go back to unrooted stock. If you have advice, please be clear. I can follow directions well enough, just don't have much experience here. Thanks in advance.

Same here, bootloop.
Same thing here. A seemingly short download of Lollipop (even though I have 50Mbs internet). Installation, reboot, and now it loops endlessly. I can get to the bootloader or into Download mode, but that's all. Recovery mode just reboots. I was rooted and had TWRP installed. Other than that, I was running stock 4.4.4.
I've rooted all my devices, and installed various ROM's on several devices. I have the full ADB installation. I have the Nexus Root Toolkit installed. The problem is, the device will not show up under "Devices" on the computer itself. I've installed every USB driver there is (and uninstalled each one after it does not work, so no I do not have several USB drivers installed). Of course nothing shows up using "adb devices" either. Nexus Root Toolkit also cannot find any devices. I've read everything on this subject I can find, and there are no answers out there. Anyone have ANY ideas??
Thanks

Guys, if your device is connected in fastboot (try "fastboot devices") then you can flash roms or recovery (and then flash rom) from there. There are multiple threads with the same problems out there which were fixed. E.g: http://forum.xda-developers.com/nexus-10/help/bricked-t2948546
In my example, I flashed TWRP recovery from fastboot, then installed custom ROM from recovery (official ROM failed to install for some reason). Try this, it might help.

danweis said:
Same thing here. A seemingly short download of Lollipop (even though I have 50Mbs internet). Installation, reboot, and now it loops endlessly. I can get to the bootloader or into Download mode, but that's all. Recovery mode just reboots. I was rooted and had TWRP installed. Other than that, I was running stock 4.4.4.
I've rooted all my devices, and installed various ROM's on several devices. I have the full ADB installation. I have the Nexus Root Toolkit installed. The problem is, the device will not show up under "Devices" on the computer itself. I've installed every USB driver there is (and uninstalled each one after it does not work, so no I do not have several USB drivers installed). Of course nothing shows up using "adb devices" either. Nexus Root Toolkit also cannot find any devices. I've read everything on this subject I can find, and there are no answers out there. Anyone have ANY ideas??
Thanks
Click to expand...
Click to collapse
Go to Fastboot mode (pwr+both volumes), Than select recovery after a while an android with Exclamation mark appears which is a stock recovery screen. To access the stock recovery menu press and hold power than press one of the volume keys so the menu will appear. Than do a factory reset and clear caches. You can than reboot and wait for boot animation to finish (it wont take long this time) and you will boot.
If this doesnt work you can flash a stock factory image easily from fastboot again.

Aresmar said:
Go to Fastboot mode (pwr+both volumes), Than select recovery after a while an android with Exclamation mark appears which is a stock recovery screen. To access the stock recovery menu press and hold power than press one of the volume keys so the menu will appear. Than do a factory reset and clear caches. You can than reboot and wait for boot animation to finish (it wont take long this time) and you will boot.
If this doesnt work you can flash a stock factory image easily from fastboot again.
Click to expand...
Click to collapse
I also had the same problem... I followed these instructions and now my Nexus 10 can boot normally (it took a long time to boot).
Only problem is all my data was deleted.... stup*d f*cking sh*t!!!!!!!

Nexus 6P black screen will not boot into OS

Okay, so there is no screen protector or anything. Not rooted or unlocked or tampered in any way. I've had the phone for 26 hours and then the following happened:
EDIT: YouTube video added https://youtu.be/yAVmTz7MQbQ
I pulled the phone out of my pocket to unlock it. I see the lock screen and put in my pin (yes, I see the actual screen and stuff on it. Let me make that clear.) after I enter my pin successfully the screen locks itself. I contacted Google support and they said to factory reset it. I did the full factory data reset in the recovery mode (again, the screen works. I can see everything to do a FDR and I can see the boot animation) and it starts to boot up. Once I see the "welcome" screen it instantly locks itself. I can hear the audible "latch" locking sound that it makes when you press the power button. I know the buttons are not malfunctioning because they work perfectly fine in bootloader / recovery mode to scroll up and down and select things. I've tried multiple things but nothing seems to work. The problem here is that I want to try and do a factory image but my computer will NOT recognize my Nexus 6P when in recovery mode / bootloader mode. I have all the drivers installed but since I can't access the OS and enable OEM UNLOCKING there is no way to factory flash a factory image is there? Can someone maybe help point me in the right direction? Again, I can NOT access the OS at all whatsoever.

You just need the bootloader unlocked to flash a factory image, you can't enable that from settings o.0 so I guess your down to RMA now.
The command is now "fastboot flashing unlock"
Hey downloading a tool kit from this devices tools sections. Install the latest adb / fastboot binarys and try again
Good luck !

hutzdani said:
You just need the bootloader unlocked to flash a factory image, you can't enable that from settings o.0 so I guess your down to RMA now.
The command is now "fastboot flashing unlock"
Hey downloading a tool kit from this devices tools sections. Install the latest adb / fastboot binarys and try again
Good luck !
Click to expand...
Click to collapse
Hi Hutzdani, when I try to run the command it says "remote: oem unlock is not allowed". I have the RMA in progress but 3-5 days with no phone is going to become grueling unfortunately and I want to try everything I can. :S

xandr00 said:
Hi Hutzdani, when I try to run the command it says "remote: oem unlock is not allowed". I have the RMA in progress but 3-5 days with no phone is going to become grueling unfortunately and I want to try everything I can. :S
Click to expand...
Click to collapse
Can you run fastboot format cache and format user data? Then will anything happen ?
Sounds like you need to edit the partition that holds the data change for allow OEM unlock - there's a few threads about this on XDA for the N9 and N6 as far as I can remember.
It would seem the ability to flash a fresh system.img would solve this

Ticwatch c2 stuck in boot loop after factory reset.

Hey all, I recently flashed a new rom on my phone, which required me to factory reset my ticwatch I'm order to reconnect.
Upon doing to the first time, everything seems to have gone well, but had trouble connecting to the device. So I ran another factory reset. Since that one, I've been stuck in a boot loop.
I see the "device software can't be checked for corruption" screen for about 20 seconds, and then it vibrates, screen turns off, then I see the same screen again. And so on.
I tried letting the battery go to nothing and trying again, seems to be the same issue. I'm letting it charge and bootloop for now in case maybe I just don't have enough juice to make it through boot.
It is rooted, with custom ROM (followed a guide on this forum somewhere about half a year ago, was running great) and TWRP installed (at least it was, I've been unable to get to the recovery screen since the boot loop started). Cannot see it in adb ever in this process.
Anyone have any other suggestions? I remember the Samsung notes had a special USB tool that would bridge a couple pins to immediately go to recovery, is there a similar option here?

Can you get in usb mode,or fastboot or recovery maybe?There is solution..dont worry.I ghuess adb dont work,but you cant go to fastboot mode and boot twrp image and get in twrp recovery..in twrp recovery you need backup file..If you cant do that,we are going to another solution..

Yeah, I can't - via any combination of button holding - get into any booted mode. No recovery, no fastboot, nothing. If anything, some buttons seem to make it circle boot faster .

nieminen432 said:
Yeah, I can't - via any combination of button holding - get into any booted mode. No recovery, no fastboot, nothing. If anything, some buttons seem to make it circle boot faster .
Click to expand...
Click to collapse
,Yeah tough situation,and when you connect it to pc in that "broken mode" -boot loop and open adb shell on pc ,comand adb devices or fastboot devices,does it show device?When you screwed boot and you have twrp there must be option to get in twrp.One trick more go to manage devices in pc find your device if unknown you right klick on it,update drivers,manually,and then choose android,then android adb install device.

KristijanKG3 said:
,Yeah tough situation,and when you connect it to pc in that "broken mode" -boot loop and open adb shell on pc ,comand adb devices or fastboot devices,does it show device?When you screwed boot and you have twrp there must be option to get in twrp.One trick more go to manage devices in pc find your device if unknown you right klick on it,update drivers,manually,and then choose android,then android adb install device.
Click to expand...
Click to collapse
I tried adb devices, but not fastboot devices, thanks for the idea, I'll give it a go.

nieminen432 said:
I tried adb devices, but not fastboot devices, thanks for the idea, I'll give it a go.
Click to expand...
Click to collapse
Maybe it wont work,but if doesnt,we figure out something..Bootlop is not the end of your device..

No go on either command. Nothing shows up.
I'm half wondering if it's my battery at this point. I think I'm getting a new watch for Christmas anyway, so not a huge loss. But happy to keep trying if anyone else has any ideas.