Database Users

stock nexus 7 stuck in boot loop

i read that it can be fixed by unlocking and rooting. problem is it is a friends and he doesn't know what version of android is on it. also can't put it in usb debugging.

Install this using Fastboot which does not require USB debugging. Simply download the factory images package then extract into the ADB folder. Typing "flash-all.bat" will flash all stock images including the boot, recovery, system and data.

thank you that worked

waiting for device
Username invalid said:
using Fastboot which does not require USB debugging. Simply download the factory images package then extract into the ADB folder. Typing "flash-all.bat" will flash all stock images including the boot, recovery, system and data.
Click to expand...
Click to collapse
I tried doing this and looked pretty promising because I have the same exact problem, but the terminal just says that it is waiting for device and does not budge. I have tried rebooting both computer and device. Neither work. Any other suggestions?
I tried again and now it says erasing 'boot'... and hangs there..
Is there any way to enable USB debugging or ADB through the command line fastboot?

curioux said:
I tried doing this and looked pretty promising because I have the same exact problem, but the terminal just says that it is waiting for device and does not budge. I have tried rebooting both computer and device. Neither work. Any other suggestions?
I tried again and now it says erasing 'boot'... and hangs there..
Is there any way to enable USB debugging or ADB through the command line fastboot?
Click to expand...
Click to collapse
Is your bootloader unlocked? If not boot into fastboot mode and type the command fastboot OEM unlock follow the prompt on the tablet and it will reboot now try the flashall.bat again. There is no way to enable USB debugging without selecting it from the menu that's a question that has been asked many times before
Sent from my C5303 using xda app-developers app

No. Sorry I forgot to mention that. My bootloader is not unlocked. And when I tried to do the fastboot OEM unlock, that is the only time the screen changes and gives me the option to unlock. When I scroll to yes and push the power button, the terminal says erasing user data and then it just gets stuck there.
I suspect that there is some kind of reading or writing problem.
Sent from my SGH-T889 using Tapatalk

curioux said:
No. Sorry I forgot to mention that. My bootloader is not unlocked. And when I tried to do the fastboot OEM unlock, that is the only time the screen changes and gives me the option to unlock. When I scroll to yes and push the power button, the terminal says erasing user data and then it just gets stuck there.
I suspect that there is some kind of reading or writing problem.
Sent from my SGH-T889 using Tapatalk
Click to expand...
Click to collapse
OK if the bootloader won't unlock that sounds like a corrupted nand partition which would mean the internal memory is unwritable. One more suggestion try downloading wugfresh NRT use the unroot back to stock option tick soft bricked and force write. I'm not sure it will work with a locked bootloader.
Sent from my C5303 using xda app-developers app

Captain Sweatpants said:
OK if the bootloader won't unlock that sounds like a corrupted nand partition which would mean the internal memory is unwritable. One more suggestion try downloading wugfresh NRT use the unroot back to stock option tick soft bricked and force write. I'm not sure it will work with a locked bootloader.
Sent from my C5303 using xda app-developers app
Click to expand...
Click to collapse
I have attached a screen shot of what I got when I tried the NRT unroot. It appears as though you were right, and that it is not going to work with a locked bootloader.

curioux said:
I have attached a screen shot of what I got when I tried the NRT unroot. It appears as though you were right, and that it is not going to work with a locked bootloader.
Click to expand...
Click to collapse
OK well it looks like you are at the new motherboard stage then. Fastboot OEM unlock failing is a pretty sure sign that the internal memory of your nexus has become corrupted and it is no longer possible to read from or write to the tablet. If you have warranty now would be a good time to use it. If not eBay is a relatively cheap place to get a replacement motherboard. Sorry I can't be of more help than that
Sent from my C5303 using xda app-developers app

[Q] Bricked and gone?

Pretty sure I know the answer to this, but before I finally through in the towel or rather my Nexus 4 against the wall... I will defer to the resident experts. So, I attempt to install Liquid Smooth 4.0 and after going into TWRP I did a wipe and installed it. I was running the previous official build of Liquid Smooth. I also install gapps for Lollipop. Everything began to boot and then the phone said something to the like apps are starting and it stayed on that screen for a full 8 hours. I went back into recovery and tried to restore from my previous Liquid Smooth. Exact same thing happened. After several attempts I did the unmentionable. I did a full wipe. I know it was a dumb*ss move now. My phone does NOT connect to ANY PC. Every time the PC says device not recognized. Now I have now OS. Only TWRP. I tried sideload, but computer does not recognize device. I bought usb-otg adapter, but found out that usb-otg does not work with Nexus 4. So.... should I throw in the towel? My phone now a fancy paperweight?
Many thanks!

kjtay said:
Pretty sure I know the answer to this, but before I finally through in the towel or rather my Nexus 4 against the wall... I will defer to the resident experts. So, I attempt to install Liquid Smooth 4.0 and after going into TWRP I did a wipe and installed it. I was running the previous official build of Liquid Smooth. I also install gapps for Lollipop. Everything began to boot and then the phone said something to the like apps are starting and it stayed on that screen for a full 8 hours. I went back into recovery and tried to restore from my previous Liquid Smooth. Exact same thing happened. After several attempts I did the unmentionable. I did a full wipe. I know it was a dumb*ss move now. My phone does NOT connect to ANY PC. Every time the PC says device not recognized. Now I have now OS. Only TWRP. I tried sideload, but computer does not recognize device. I bought usb-otg adapter, but found out that usb-otg does not work with Nexus 4. So.... should I throw in the towel? My phone now a fancy paperweight?
Many thanks!
Click to expand...
Click to collapse
Under device manager, what is listed as your phone?

Ajxx16 said:
Under device manager, what is listed as your phone?
Click to expand...
Click to collapse
Unknown Device... It is worth noting that I have used Wugs Toolkit and followed every set of directions to a T. This includes a PC that that has never had my phone in it before. Followed all the steps before I even tried to connect. Also, both PC machine indicate that I have installed the most update driver.

I have zero experience with that toolkit, but have you tired every usb port on your computer and possibly another computer? Your phone is far from gone, this just sounds like a driver issue to me. Is your phone recognizable in bootloader?
I don't actually have this phone but my wife does, as well as my brother. Just the other night my wife's was showing up unrecognized, all I had to do was swap usb ports on the computer.

Ajxx16 said:
I have zero experience with that toolkit, but have you tired every usb port on your computer and possibly another computer? Your phone is far from gone, this just sounds like a driver issue to me. Is your phone recognizable in bootloader?
I don't actually have this phone but my wife does, as well as my brother. Just the other night my wife's was showing up unrecognized, all I had to do was swap usb ports on the computer.
Click to expand...
Click to collapse
I have tried all usb ports and a different usb cord. My OS is gone, so I was hoping to find some way to install a rom or stock. I am at a loss!

How about the bootloader? If you have that feature you can flash stock image
---------- Post added at 07:44 PM ---------- Previous post was at 07:43 PM ----------
Volume down + power incase you didn't know.

Ajxx16 said:
How about the bootloader? If you have that feature you can flash stock image
---------- Post added at 07:44 PM ---------- Previous post was at 07:43 PM ----------
Volume down + power incase you didn't know.
Click to expand...
Click to collapse
I do if I understand the term correctly. I am at the android "start" screen and underneath the android it says
Fastboot Mode
Product_Name - mako
lock state - unlocked
Now what?

Connect it to your computer, and I assume you have fastboot and adb set up correctly. In command prompt type fastboot devices and see if your phone is listed, should give the serial and say fastboot next to that

Not sure if I know how to set up adb correctly... as far as fastboot goes.. I assume that is set up correctly. Would adb work if the PC doesn't recognize my phone?

Well adb is of no use here so I wouldn't worry about it. Is fastboot recognized?

Ajxx16 said:
Well adb is of no use here so I wouldn't worry about it. Is fastboot recognized?
Click to expand...
Click to collapse
Don't mean to sound like an idiot (may be too late for that), but do you mean fastboot recognized on my PC when I plug in my phone? Or does is say fastboot on my phone? PC does not recognize my phone, but it does say fastboot enabled on my phone.

Alright so follow these instructions.
http://forum.xda-developers.com/showthread.php?t=2317790
Get that set up and in the mean time download either the 4.4.4 or 5.0 image here.
https://developers.google.com/android/nexus/images
Once you finish the adb fastboot setup, while your phone is in the boot loader screen you should be able to type into a command prompt "fastboot devices" and your device should be listed.

Ajxx16 said:
Alright so follow these instructions.
http://forum.xda-developers.com/showthread.php?t=2317790
Get that set up and in the mean time download either the 4.4.4 or 5.0 image here.
https://developers.google.com/android/nexus/images
Once you finish the adb fastboot setup, while your phone is in the boot loader screen you should be able to type into a command prompt "fastboot devices" and your device should be listed.
Click to expand...
Click to collapse
I can't get the PC to recognize the phone. The phone is in fastboot mode. It is looking mighty grim!

I'm fairly certain this is just a simple fix on the drivers on your computer, you have access to recovery and boot loader, your phone is far from gone. I'm out atm so I'll check in with ya a little later.

Ajxx16 said:
I'm fairly certain this is just a simple fix on the drivers on your computer, you have access to recovery and boot loader, your phone is far from gone. I'm out atm so I'll check in with ya a little later.
Click to expand...
Click to collapse
An easy fix, do you have a nandroid backup? Just restore it in twrp. As mentioned, you're far from bricked and sol. If you can get into the bootloader it's recoverable.
Sent from my Nexus 9 using XDA Free mobile app

jd1639 said:
An easy fix, do you have a nandroid backup? Just restore it in twrp. As mentioned, you're far from bricked and sol. If you can get into the bootloader it's recoverable.
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
Would you happen to have a link for an ADB driver he could install? Not sure of the n4 requires something specific.

Ajxx16 said:
Would you happen to have a link for an ADB driver he could install? Not sure of the n4 requires something specific.
Click to expand...
Click to collapse
I'd Google 15 second adb install xda. That'll set yo adb and fastboot on the pc and includes drivers
Sent from my Nexus 9 using XDA Free mobile app

jd1639 said:
I'd Google 15 second adb install xda. That'll set yo adb and fastboot on the pc and includes drivers
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
Installed 15 second adb and still nothing recognized on my PC. Still have "fastboot mode" in red on my phone???

kjtay said:
Installed 15 second adb and still nothing recognized on my PC. Still have "fastboot mode" in red on my phone???
Click to expand...
Click to collapse
Open up device manager, look for the phone, right click and hit update driver, then hit let !e choose driver, then select from list, you shpuld see something along the lines of ADB interface. Select that and install and try fastboot devices in command prompt again.

Ajxx16 said:
Open up device manager, look for the phone, right click and hit update driver, then hit let !e choose driver, then select from list, you shpuld see something along the lines of ADB interface. Select that and install and try fastboot devices in command prompt again.
Click to expand...
Click to collapse
I am pretty certain I have the proper drivers installed on 3 computers. Not a single one recognizes the device. I suppose it is possible that it is a hardware issue? If I can figure a way to the computer to recognize the phone I am certain I can save it. Right NOTHING has worked.

[Q] Nexus 7 doesn't boot

Hello all! I'm having a problem with a Nexus 7.
This is my brother's tablet that he hasn't used in a few months. It hasn't been unlocked or rooted.
I can get to the boot screen with the android lying on it's back and the options with the volume buttons. The other info on that screen which might be pertinent:
Fastboot mode
Product name: grouper
variant - grouper
hw version - er3
bootloader version - n/a
serial number -
signing - not defined yet
lock stated - locked
When I go to recovery mode and push the power button, it says "booting failed" in the upper left. It still says Google in the middle, and has the options with the volume in the upper right, but the android is gone as is the text in the lower left.
I have adb and fastboot installed, but I can't seem to do much since the tablet is locked. I tried unlocking a few times, and it's always failed. Usually it doesn't give a reason, but one time I got this: "Failed (status read failed (Too many links))"
I've tried googling this and can't find someone with the same problem.
Anything I can try?
Thanks!

Nexus Tool Kit

rbeavers said:
Nexus Tool Kit
Click to expand...
Click to collapse
OK, I have that now, but I can't get very far. I think I need to enable debugging on the device first? How can I do that in that state it's in now?

swirv81 said:
OK, I have that now, but I can't get very far. I think I need to enable debugging on the device first? How can I do that in that state it's in now?
Click to expand...
Click to collapse
Anything else I can try? Not sure if I'm missing something with the tool kit, but I nothing I tried seemed to help.

swirv81 said:
Anything else I can try? Not sure if I'm missing something with the tool kit, but I nothing I tried seemed to help.
Click to expand...
Click to collapse
If you can get into the Bootloader, just run the below via ADB
Code:
fastboot oem unlock
Once you unlock the Bootloader you can use the "Soft Brick" Mode in the NRT to Re-flash back to stock and see if that will allow you to boot. You do not need debugging enabled to use the Nexus Root Toolkit if you use the Soft Brick mode, but you must have an unlocked bootloader.

ariesgodofwar said:
If you can get into the Bootloader, just run the below via ADB
Code:
fastboot oem unlock
Once you unlock the Bootloader you can use the "Soft Brick" Mode in the NRT to Re-flash back to stock and see if that will allow you to boot. You do not need debugging enabled to use the Nexus Root Toolkit if you use the Soft Brick mode, but you must have an unlocked bootloader.
Click to expand...
Click to collapse
I've tried unlocking a few times, but after a few minutes of it saying "unlocking" it fails.

swirv81 said:
I've tried unlocking a few times, but after a few minutes of it saying "unlocking" it fails.
Click to expand...
Click to collapse
What says "unlocking" (computer or tablet) and are you trying to do it through the Toolkit, or via command prompt ADB? I would first make sure your computer is seeing your tablet (ie. that the drivers and Fastboot are installed correctly). Do you know that they are?

ariesgodofwar said:
What says "unlocking" (computer or tablet) and are you trying to do it through the Toolkit, or via command prompt ADB? I would first make sure your computer is seeing your tablet (ie. that the drivers and Fastboot are installed correctly). Do you know that they are?
Click to expand...
Click to collapse
I was trying this with the command prompt. I could get fastboot to list the device when using that command. And the tablet and command prompt both say "unlocking" when doing that. I would assume that means the computer is seeing the tablet and everything is set up correctly?
I think I tried to unlock with the Toolkit, but I believe it told me that device needs to be in debugging mode.

Hey there, I'm having a similar problem.
My info is the same except my bootloader version is 4.18 and my lock state says it's unlocked. I tried to use the root kit but I'm having trouble with the fastboot device being detected. Driver solutions attempted were the google ones, and the pdanet ones. I can't really do the manual thing since that involves the device being recognized when plugged in, and since I can't enable usb debugging... anyways the automated drivers windows says were installed successfully so I don't really know what else to do.
Note: I do know the usb port on the tablet and computer work since when plugged in, it will show that its charging with the white battery icon.

Same issue here
I was in the process of upgrading manually from android 5.0 to 5.0.2 owing to the serious lag that came with lollipop. The OTA was taking longer and testing my patience as most apps were crashing due to lag.
Therefore decided to go for manual flashing of the image. I have never done this before. I was able to make the computer see my device by disabling mtp via storage under setting in the device. This is one thin I noticed to make the device visible to the computer.
After installing the device drivers my nexus was visible within the device manager but it couldn't be seen as an external storage until I played with the MTP. I had even unlocked the boot loader before all this.
So everything was going well and while I started to think all is well, I ran into this issue. From adb I tried to run 'flash-all.bat' from the new device image. Something went wrong somewhere - don't know what it is, but from then on, I am stuck in the fastboot screen or into recovery mode but when i try to boot the device bu hitting the power button - I get this message 'Booting failed'.
I am also trying to use NRToolkit but no use. When I connect my device it is seen in the device manager in my pc but cannot see it as a storage. Therefore when I now try to run the 'adb devices' command it cannot see my device. From what I saw initially, until I enable/disable mtp mode adb was not able to see my device to communicate.
Now when I tried NRT and installed the drivers once again, it is being detected in the device manager but when I run the driver test within NRT - I get a ADB device not found error. Within NRT all that it says is go into device setting>storage to enable it which I know but at the current status of my device in boot screen/recovery mode how can I go in to enable this. This is not helpful.
Somebody please suggest a workaround for this issue. I know I am close to the solution but not sure how to enable the MTP or at least made the NRToolkit to say 'ADB device found'.
My fastboot screen shows these details:
Fastboot mode
Product name grouper
Variant = grouper
HW Version – ER3
Bootloader version – 4.23
Baseband version – N/A
Serial number – 015d21d910141c0a
Signing – not defined yet
Lock State - unlocked
Please help.

Soft Bricked Nexus 6P with locked bootloader

I have a Nexus 6P running stock android, with a locked bootloader and I've only ever installed OTA updates. After installing an OTA update to NRD09U from my phone, I got the "Your Device is Corrupt. It can't be trusted and may not work properly," message. Attempting to press the power button to continue simply reboots the phone starting the process again. Obviously, because I can't even boot into android proper, I'm unable to enable developer mode or the other necessary settings in order to unlock my bootloader, so I'm stuck in a loop. I've tried sideloading a rescue OTA but I'm unable to flash an image because my phone isn't being recognized as an ADB device, even though the Android Bootloader entry shows up in my device manager as it's supposed. Even more puzzling is the fact that my phone shows up correctly as a fastboot device; typing "adb devices" returns an empty list, while typing "fastboot devices" lists the serial number of my phone as expected. I've tried a number of troubleshooting methods to fix this, including uninstalling the drivers from the device manager, and reinstalling them manually from a .zip obtained directly from google, but I still can't get my phone to be recognized as an ADB device so I'm still stuck.. I've tried contacting Google directly to get them to service my phone, but because the device is corrupted, they're telling me that my phone was rooted and that it wouldn't be covered under warranty, so they wanted to charge me almost $400 to fix it. I've read on some posts here and elsewhere that using the "fastboot format ***" works for some users with locked bootloaders, but it fails due to my bootloader being locked when I tried it myself.
So the way I see it in order to fix my phone I either need to find a method to unlock the bootloader manually using ADB/Fastboot/some other method that doesn't require OEM unlock or USB debugging, or I need to find away to get my device to be recognized as an ADB device so I can sideload the image. Anyone have any ideas how I can do this? Or some alternate solutions?
When I enter recovery mode, my system version is as follows: angler/angler/7.0/NRD09U
Thanks in advance.

Make sure you are using Android SDK tools and is up to date
Sent from my Nexus 6P using Tapatalk
---------- Post added at 09:29 PM ---------- Previous post was at 09:26 PM ----------
Have you tried factory reset?
Sent from my Nexus 6P using Tapatalk

Enter stock recovery with the lying down Android. Use to side buttons to enter the menu. That's when ADB will work only.

gjkrisa said:
Make sure you are using Android SDK tools and is up to date
Click to expand...
Click to collapse
Everything should be up to date. I installed the SDK today, and I installed USB drivers from both the SDK manager and manually.
Factory reset fails, taking me back to the corrupted screen, which in turn brings me back to a bootloop.
Gazontop said:
Enter stock recovery with the lying down Android. Use to side buttons to enter the menu. That's when ADB will work only.
Click to expand...
Click to collapse
As soon as I enter recovery mode, my computer completely stops recognizing that the 6P is plugged in. It makes a sound like the device has been disconnected and there is nothing in the device manager.

If you're u don't OEM Unlocking or Bootloader unlocked then your at a lose...sell it for parts
Sent from my Pixel XL using Tapatalk

I think Google should fix this it's a defect in the memory most likely or a ****ty update
Sent from my Nexus 6P using Tapatalk

gjkrisa said:
I think Google should fix this it's a defect in the memory most likely or a ****ty update
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Is it still under warranty?

tech_head said:
Is it still under warranty?
Click to expand...
Click to collapse
It was supposed to have been, but Google basically accused me of having rooted my phone even though the bootloader is still locked, and OEM is still locked too and I've never touched any of these settings.

Can't find "fastboot" mode in bootloader

Hello, I've bought the HTC U Ultra for my birthday at a very good price (250€) and I'm very satisfied about this phone!
Only, it's been 3 months since I try to root without any success. I can not find the "fastboot" mode in the bootloader and I do not know how.
Yet I followed all the tutorials to the letter (French expression I do not know if you go to understand ... x)) but I have never reached that point. I have the ADBs and all the other files needed.
Also, I made all the updates at the first launch of the phone. Is that why it's blocked?
Thank you in advance.
PS: I also unlocked the bootloader in the development options.
PS n°2: I post here because the French forums are desperate desert for this phone.

Hold both volume down + power together for around 10 seconds. Your phone will vibrate after that. You will then enter download mode, which is actually fastboot.

bc Yume said:
Hold both volume down + power together for around 10 seconds. Your phone will vibrate after that. You will then enter download mode, which is actually fastboot.
Click to expand...
Click to collapse
Ok, but when I want to unlock the bootloader using htcdev, I have < waiting for device > when i enter fastboot oem get_identifier_token.

SofianeLasri said:
Ok, but when I want to unlock the bootloader using htcdev, I have < waiting for device > when i enter fastboot oem get_identifier_token.
Click to expand...
Click to collapse
The computer is unable to recognise your phone. Maybe another port.

bc Yume said:
The computer is unable to recognise your phone. Maybe another port.
Click to expand...
Click to collapse
my device is recognize when it's start, but when it reboot to bootloader, abd / fastboot lost the connection. :/
I've tried with all of my ports.

SofianeLasri said:
my device is recognize when it's start, but when it reboot to bootloader, abd / fastboot lost the connection. :/
I've tried with all of my ports.
Click to expand...
Click to collapse
Are you sure you have USB Debugging on and you are using ADB driver from Google, not the one comes from HTC Sync?

bc Yume said:
Are you sure you have USB Debugging on and you are using ADB driver from Google, not the one comes from HTC Sync?
Click to expand...
Click to collapse
I use minimal adb 1.4.2 and i don't installed htc sync.

I use adb command line directly from Android Developers and have absolutely no problem. Maybe uninstall minimal adb and try that one. I can't help you with something I am not familiar with.

bc Yume said:
I use adb command line directly from Android Developers and have absolutely no problem. Maybe uninstall minimal adb and try that one. I can't help you with something I am not familiar with.
Click to expand...
Click to collapse
Yes but I must to download a lot of GB to user these abd. :/
I've just install htc sync, I tell you more if it work.
UPDATE : Oh it work! x) I never thought it would work! I thought htc sync was a software like those samsull that block the phone.

cool but i've now s-on and a i can"t install twrp with this. x)

SofianeLasri said:
cool but i've now s-on and a i can"t install twrp with this. x)
Click to expand...
Click to collapse
You can install TWRP as long as your bootloader is unlocked, regardless of the status of S-ON or S-OFF

SofianeLasri said:
cool but i've now s-on and a i can"t install twrp with this. x)
Click to expand...
Click to collapse
double check "Allow USB debugging" for the computer. From Developers "Revoke USB debugging Auth" . Unplug & plug back USB cable should come up with dialog box for auth. You may (not sure) this from cmd: adb reboot fastboot which could come up with error msg: "error: device unauthorized. This adbd's $ADB_VENDOR_KEYS is not set; try 'adb kill-server' if that seems wrong. Otherwise check for a confirmation dialog on your device."

You cant find fastboot mode because it is now called download mode...