Database Users

Nexus 7 Stuck on Google Logo

Good day everyone,
My friend was updating her Nexus 7 and suddenly the connection went off and the update was stopped. When she booted her Nexus 7, it is stuck on the Google Logo and stays there.
If I press the Volume Down, I can get the Recovery, Bootloader or Shutdown. I tried the Recovery mode but still stuck there.
What to do? Is there anyone that can give me the right steps to get back the Nexus 7?
Thank you a lot.

Flash the stock boot.img using ADB
type “fastboot reboot-bootloader”
type “fastboot flash bootloader bootloader-grouper-3.34.img”
type “fastboot reboot-bootloader”
type “fastboot flash boot boot.img”
Hope this helps

sorry for my ignorance but how to flash the stock boot.img using ADB ?
Sorry again and thank you for your help

Aleksee said:
sorry for my ignorance but how to flash the stock boot.img using ADB ?
Sorry again and thank you for your help
Click to expand...
Click to collapse
Like I just told you, their the actual commands mate.
Open CMD by using Run -> CMD -> (NAVIGATE TO YOUR FOLDER)
E.g. cd c://mydocuments/adb/
Im guessing you have ADB installed, as you've already rooted and flashed.
When in the ADB directory, use
adb devices
With your tablet plugged in and USB Debugging enabled!!!
If this lists your device, then you're all good to go with flashing the boot.img
Hope this helps.
If you get stuck, google Flashing Boot.img with ADB on Android
Or something
---------- Post added at 02:35 PM ---------- Previous post was at 02:34 PM ----------
Or use the GUIDE that is on the first page, just above your post.
http://forum.xda-developers.com/showthread.php?t=1907796
^.-

6p with OS X 10.11 - Recovery adb devices not detected

I am hoping someone can give me some pointers on what to look at... I have two Macs where I have encountered this problem. When in recovery, I type
Code:
adb devices
into the terminal and I get no devices found. When my Nexus 6p is booted into full OS mode I can see the device serial number reported, and I can even issue
Code:
adb reboot recovery
commands.
Any ideas what needs to happen to get the device to work properly in recovery mode with adb? I've gone through several of the tutorials and haven't found any smoking guns. I do NOT have adb in my path, but I do change to that folder and run ./adb to execute.
Some background
Both Macs run OS X 10.11, El Capitan
The Nexus 6p is on 6.0.1, MMB29Q, stock recovery and ROM, not rooted
ADB/Fastboot were installed via the Google Android SDK

Idk how different it is, but I use OSX 10.10.5. I type: ./adb or ./fastboot before commands. With the phone in the bootloader, do you have an issue when you run:
./fastboot devices
Sent from my Nexus 5X using Tapatalk

I used both on my Macbook Pro last night on 10.11.
When you plug the phone in, is it being recognized by the OS? (Or, if you have Android File Transfer installed, does it pop open immediately?)

Follow this tutorial, it will fix your ills.
http://forum.xda-developers.com/showthread.php?t=1917237

gewecht said:
I am hoping someone can give me some pointers on what to look at... I have two Macs where I have encountered this problem. When in recovery, I type
Code:
adb devices
into the terminal and I get no devices found. When my Nexus 6p is booted into full OS mode I can see the device serial number reported, and I can even issue
Code:
adb reboot recovery
commands.
Any ideas what needs to happen to get the device to work properly in recovery mode with adb? I've gone through several of the tutorials and haven't found any smoking guns. I do NOT have adb in my path, but I do change to that folder and run ./adb to execute.
Some background
Both Macs run OS X 10.11, El Capitan
The Nexus 6p is on 6.0.1, MMB29Q, stock recovery and ROM, not rooted
ADB/Fastboot were installed via the Google Android SDK
Click to expand...
Click to collapse
See here.
And here for issues with El Cap.

Thanks for the pointer... However, the problem persists.
I ran the installer after disabling System Integrity Protection (done in Recovery) and rebooted into OS X
I was able to detect the Nexus when the Android OS was running, but not in recovery (same behavior).
I rebooted to recovery and re-enabled System Integrity Protection. Rebooted again. No change in behavior.
So I'm really not what else I could or should be looking at.
BTW, it looks like the only benefit of disabling SIP is allowing the installation of the files into /usr/local/bin. Once it is installed I'm thinking you can re-enable SIP.
Any other thoughts?
uicnren said:
See here.
And here for issues with El Cap.
Click to expand...
Click to collapse

gewecht said:
Thanks for the pointer... However, the problem persists.
I ran the installer after disabling System Integrity Protection (done in Recovery) and rebooted into OS X
I was able to detect the Nexus when the Android OS was running, but not in recovery (same behavior).
I rebooted to recovery and re-enabled System Integrity Protection. Rebooted again. No change in behavior.
So I'm really not what else I could or should be looking at.
BTW, it looks like the only benefit of disabling SIP is allowing the installation of the files into /usr/local/bin. Once it is installed I'm thinking you can re-enable SIP.
Any other thoughts?
Click to expand...
Click to collapse
I did some further digging... When the Nexus is booted into Android I can see the device (identified as "Nexus 6p") in the USB chain in OS X's "System Information" tool. In the bootloader screen, OS X shows "Android" and fastboot does detect the device.
However, when I've rebooted into recovery I cannot see anything connected - not a device in recovery, not a Nexus 6p. Nothing!

gewecht said:
I did some further digging... When the Nexus is booted into Android I can see the device (identified as "Nexus 6p") in the USB chain in OS X's "System Information" tool. In the bootloader screen, OS X shows "Android" and fastboot does detect the device.
However, when I've rebooted into recovery I cannot see anything connected - not a device in recovery, not a Nexus 6p. Nothing!
Click to expand...
Click to collapse
Mind if I ask, what are you trying to do in recovery?

have you tried unplugging and replugging the usb type c while you were on adb/recovery screen? i had the same problem but unplug and replug worked for me.

bluwavemarshall said:
have you tried unplugging and replugging the usb type c while you were on adb/recovery screen? i had the same problem but unplug and replug worked for me.
Click to expand...
Click to collapse
I finally figured out what was going on.
When in Recovery mode, I could never see the Nexus 6p attached to the OS X machine. However, on a hunch, I enabled the sideload ZIP with ADB option (this is stock recovery), and suddenly I was able to see the 6p in OS X System Information, and detect it via "adb devices".
Not sure if this is expected behavior or not, but it seems that there is a portion of the USB interface in stock recovery that only loads on this device once you have enabled the sideload feature in recovery.
Thanks to everyone for the suggestions.

gewecht said:
I finally figured out what was going on.
When in Recovery mode, I could never see the Nexus 6p attached to the OS X machine. However, on a hunch, I enabled the sideload ZIP with ADB option (this is stock recovery), and suddenly I was able to see the 6p in OS X System Information, and detect it via "adb devices".
Not sure if this is expected behavior or not, but it seems that there is a portion of the USB interface in stock recovery that only loads on this device once you have enabled the sideload feature in recovery.
Thanks to everyone for the suggestions.
Click to expand...
Click to collapse
ADB works in OS mode, while USB debugging is enabled. Where stock recovery is concerned, only sideload mode will be available, since it doesn't require ADB access for anything else.
EDIT: And yes. It is expected behaviour of the stock recovery.

Glad you figured it out! Cool

I had the same problem, how did you "enable the sideload ZIP with ADB option "?

I'm having the same issue on my Pixel. How did you "enabled the sideload ZIP with ADB option (this is stock recovery)"??
---------- Post added at 11:54 PM ---------- Previous post was at 11:50 PM ----------
How do I "enabled the sideload ZIP with ADB option"?
gewecht said:
I finally figured out what was going on.
When in Recovery mode, I could never see the Nexus 6p attached to the OS X machine. However, on a hunch, I enabled the sideload ZIP with ADB option (this is stock recovery), and suddenly I was able to see the 6p in OS X System Information, and detect it via "adb devices".
Not sure if this is expected behavior or not, but it seems that there is a portion of the USB interface in stock recovery that only loads on this device once you have enabled the sideload feature in recovery.
Thanks to everyone for the suggestions.
Click to expand...
Click to collapse

Error updating via OTA

Hi everyone,
I was trying to update via OTA to the latest version, but after downloading the update the tablet started updating itself and returned the Android dead droid error. It is important to highlight that I was rooted with KingRoot and removed it to apply OTA update. Any help would be appreciated

regular_ said:
Hi everyone,
I was trying to update via OTA to the latest version, but after downloading the update the tablet started updating itself and returned the Android dead droid error. It is important to highlight that I was rooted with KingRoot and removed it to apply OTA update. Any help would be appreciated
Click to expand...
Click to collapse
Am in the same situation. Waiting to hear back from Cameron Yan.

Looks like you might need to flash the 1.5 version via fastboot and go through each update iteration.

Yeah u might have to flash 1.5
Your Jide Ambassador is here!!!
---------- Post added at 12:45 PM ---------- Previous post was at 12:35 PM ----------
U can't just remove the rooting and think the update will be applied. Each updated is like a layered cake placed on its foundation. When you rooted you messed with pliers of stability for future layered updates and the updates check where they are suppose to be place. If something is missing or out of place you are going to get an error.
Your Jide Ambassador is here!!!

regular_ said:
Hi everyone,
I was trying to update via OTA to the latest version, but after downloading the update the tablet started updating itself and returned the Android dead droid error. It is important to highlight that I was rooted with KingRoot and removed it to apply OTA update. Any help would be appreciated
Click to expand...
Click to collapse
I had the same experience and ended up flashing 1.5 and then going through the automatic updates. Took a little while, but the update installed and I am back to stock for the time being.

regular_ said:
Hi everyone,
I was trying to update via OTA to the latest version, but after downloading the update the tablet started updating itself and returned the Android dead droid error. It is important to highlight that I was rooted with KingRoot and removed it to apply OTA update. Any help would be appreciated
Click to expand...
Click to collapse
Same issue for me I am scared about the root by King root : not the cleaner tool ...

iceheart3131 said:
Same issue for me I am scared about the root by King root : not the cleaner tool ...
Click to expand...
Click to collapse
If you have rooted, the only way to get OTA that I have found is to reflash version 1.5 and then have the normal updates be applied.
I have done this and then rerooted after I have applied the current update.

tomlogan1 said:
If you have rooted, the only way to get OTA that I have found is to reflash version 1.5 and then have the normal updates be applied.
I have done this and then rerooted after I have applied the current update.
Click to expand...
Click to collapse
Ok , but where can I found this 1.5 version please ? there is no Download section on Jide webpage ...
Ok 1.5 version and toutos available on JIDE webpage

I have an issue with fastboot : adb devices found the tablet but fastboot devices found nothing ... My fastboot is functionnal with my edge 7, nexus 5x and android TV ... So it must be something specific to do on Utra Tablet ... But I don't know what

iceheart3131 said:
I have an issue with fastboot : adb devices found the tablet but fastboot devices found nothing ... My fastboot is functionnal with my edge 7, nexus 5x and android TV ... So it must be something specific to do on Utra Tablet ... But I don't know what
Click to expand...
Click to collapse
Probably obvious, but to you have USB debugging enabled?

tomlogan1 said:
Probably obvious, but to you have USB debugging enabled?
Click to expand...
Click to collapse
Yes i have... I have try to connecter other Devices to be sure but the issue is only with Ultra Tablet

iceheart3131 said:
Yes i have... I have try to connecter other Devices to be sure but the issue is only with Ultra Tablet
Click to expand...
Click to collapse
Try connecting via USB and then run a command like adb devices and then unplug the tablet and plug it back in. I remember a security (RSA?) prompt that you have to accept in order for this to work. Worth a try.

tomlogan1 said:
Probably obvious, but to you have USB debugging enabled?
Click to expand...
Click to collapse
Sorry for the long delay (Holydays !!)... Yes USB debug is enabled .
---------- Post added at 05:15 PM ---------- Previous post was at 05:02 PM ----------
tomlogan1 said:
Try connecting via USB and then run a command like adb devices and then unplug the tablet and plug it back in. I remember a security (RSA?) prompt that you have to accept in
Still not available with fastboot
Click to expand...
Click to collapse

iceheart3131 said:
Sorry for the long delay (Holydays !!)... Yes USB debug is enabled .
---------- Post added at 05:15 PM ---------- Previous post was at 05:02 PM ----------
tomlogan1 said:
Try connecting via USB and then run a command like adb devices and then unplug the tablet and plug it back in. I remember a security (RSA?) prompt that you have to accept in
Still not available with fastboot
Click to expand...
Click to collapse
When I use adb I get the device SN. When I use fastboot devices I get nothing. If I then adb reboot bootloader I get the attached response.
Click to expand...
Click to collapse

I follow this tuto (How to flash Remix OS 1.5 from Jide) :
To flash the ROM, please download the file from the following link and follow the below instructions.
https://drive.google.com/open?id=0B...1FVVR3RkRya29sakQ3SEdVbXU5cUg0YTIzUnNfUTRWMTA
Installing image files using fastboot
1. Make sure your Remix has working fastboot (http://wiki.cyanogenmod.org/w/Fastboot) and adb (http://wiki.cyanogenmod.org/w/Adb).
2. Download images
The information of the image zip file:
Images Zip File Name: SK1WG.zip
md5: f993e49ff5f0bfac169dcb62b2e820e8
sha1: 6f9b364f46680ff1294ff2eb9e3fe9aba6592d5a
3. Unzip the downloaded zip file ( SK1WG.zip ) and go to the folder
4. Connect the Remix to the computer via USB.
5. Make sure the fastboot binary is in your PATH (http://wiki.cyanogenmod.org/w/Doc:_paths) or that you place the recovery image in the same directory as fastboot.
6. Open a terminal on your PC and reboot the device into fastboot mode by typing adb reboot bootloader or by using the hardware key combination for your device while it is powered off.
7. Once the device is in fastboot mode, verify your PC sees the device by typing fastboot devices
-If you don't see your device serial number, and instead see "", fastboot is not configured properly on your machine. See fastboot (http://wiki.cyanogenmod.org/w/Doc:_fastboot_intro) documentation for more info.
-If you see "no permissions fastboot", make sure your UDEV (http://wiki.cyanogenmod.org/w/UDEV) rules are setup correctly.
8. Clean the existing data by entering the following command: fastboot -w
9. Flash images onto your device by entering the following three commands:
-fastboot flash system system.img
-fastboot flash recovery recovery.img
-fastboot flash boot boot.img
10. Once the flash completes successfully, run the following command to reboot the device into recovery to verify the installation.
-fastboot reboot
Click to expand...
Click to collapse
I can reboot with adb command
Code:
adb reboot bootloader
my tablet reboot and this menu is available :
but fasboot command seems still without effect , i have try to launch fastboot protocol in the menu : no effect . fastboot devices doens't return any ID . I have try to install complete suite android studio to have ALL tools ( and fastboot ) but it seems the same isssue .

iceheart3131 said:
I follow this tuto (How to flash Remix OS 1.5 from Jide) :
I can reboot with adb command
Code:
adb reboot bootloader
my tablet reboot and this menu is available :
but fasboot command seems still without effect , i have try to launch fastboot protocol in the menu : no effect . fastboot devices doens't return any ID . I have try to install complete suite android studio to have ALL tools ( and fastboot ) but it seems the same isssue .
Click to expand...
Click to collapse
Maybe a driver from previous devices? I'm using the Android naked drivers and they work with the tablet as well as my Android phone.

Victory !!!! until now i have tried with Windows 10 and it doesn't works . With a friend we have follow the sme process on Ubuntu and it works perfectly ! Thanks tomlogan1 for your patience and your support , I appreciate

iceheart3131 said:
Victory !!!! until now i have tried with Windows 10 and it doesn't works . With a friend we have follow the sme process on Ubuntu and it works perfectly ! Thanks tomlogan1 for your patience and your support , I appreciate
Click to expand...
Click to collapse
Congratulations! Now you can be ready when custom ROMs become available. Your presistance paid off.

Driver issue: ADB working fine but Fastboot isn't

I have a Zuk Z1, I wanted to unlock the bootloader and then root the device.
However, the device doesn't get recognized or listed after the command "fastboot devices".
Any help will be appreciated.
Thanks in advance.

I'm having the same problem as well.
I installed adb + Fastboot,
I'm able to issue the command adb reboot bootloader
But once the device is in bootloader, fastboot and adb are not detecting it anymore.
I tried installing the ADB android drivers in the device manager, but still same problem, device not getting detected while in bootloader
I wonder if anyone had the same problem, and was able to solve it?

I am also not able to use fastboot because of driver, but able to use adb.

Try latest version 1.17 from here:
http://leshcatlabs.net/downloads_usb_unifl/

did it work?

It's not working for me either. I've installed all the drivers and "adb reboot bootloader" reboots the phone into "CYANOGEN FASTBOOT MODE" but "fastboot devices" returns nothing. What am I doing wrong?

swarimk said:
I have a Zuk Z1, I wanted to unlock the bootloader and then root the device.
However, the device doesn't get recognized or listed after the command "fastboot devices".
Any help will be appreciated.
Thanks in advance.
Click to expand...
Click to collapse
I managed to finally get it to work with Win 10 using the drivers from here http://forum.xda-developers.com/zuk-z1/help/files-zuk-z1-drivers-qpst-roms-twrp-t3221629 I'm not sure if was just these drivers that solved it because I had an absolute bear of a day trying to get it to work and some odd stuff happened. But I just know it worked shortly after installing them. Now I'm very pleased with NuleaRom installed

edulus91 said:
did it work?
Click to expand...
Click to collapse
I Have the same problem.
But, although i can't send fastboot devices, i can send revovery.img
And now i can unloack bootloader

Hey guys.
Did anyone else hit this issue?
I am trying to prepare my Zuk Z1 for CM13 install.
Tried both "Minimal ADB and Fastboot" and the official Android SDK for tools and drivers.
I am stuck in the same place: "adb reboot bootloader" puts the device into fastboot mode, but I lose connectivity after that so cannot progress.
Any help would be gratefully received.
Thanks
Uri
---------- Post added at 05:47 PM ---------- Previous post was at 05:29 PM ----------
So to help anyone else, here is how I worked around this.
Keep device manager open when running the "adb reboot bootloader" command.
There, the Zuk Z1 will disappear and pop back up as no driver installed.
Go in and manually install the correct driver (android_usb.inf).

someoneelse999 said:
Hey guys.
Did anyone else hit this issue?
I am trying to prepare my Zuk Z1 for CM13 install.
Tried both "Minimal ADB and Fastboot" and the official Android SDK for tools and drivers.
I am stuck in the same place: "adb reboot bootloader" puts the device into fastboot mode, but I lose connectivity after that so cannot progress.
Any help would be gratefully received.
Thanks
Uri
---------- Post added at 05:47 PM ---------- Previous post was at 05:29 PM ----------
So to help anyone else, here is how I worked around this.
Keep device manager open when running the "adb reboot bootloader" command.
There, the Zuk Z1 will disappear and pop back up as no driver installed.
Go in and manually install the correct driver (android_usb.inf).
Click to expand...
Click to collapse
This morning I had the same problem, I installed All in one tool and reinstalled all with the tool. Zuk's driver didn't work but i tried in fastboot mode and it worked.... I don't know how but it worked.

Hi,
I have the same problem. ADB commands work but Fastboot ones don't and even a "fastboot reboot" returns with a "waiting for device". I have tried updating the drivers manually but the response is always that the best drivers are already installed. Today, I got the Zuk Z1 in fastboot mode and then installed the recommended drivers as in this link given by the user XQ55 using the executable file in the link. I don't know whether it was because of this driver update or the fact that I had connected the Z1 for the first time after a major Windows 10 update (the phone was set up as a new device), now, in the Fastboot mode, I can see the device shown as "Shenqi Composite ADB Interface" in the Device Manager as against just "Android" earlier. Also, now when in ADB mode, the phone shows as "MTP USB Device" as against "Z1" earlier in the Device Manager.
However the fastboot commands don't work. Can someone help with this; the stock ROM isn't good at all and want to unlock bootloader, root and then install a new ROM
someoneelse999 said:
Hey guys.
Did anyone else hit this issue?
I am trying to prepare my Zuk Z1 for CM13 install.
Tried both "Minimal ADB and Fastboot" and the official Android SDK for tools and drivers.
I am stuck in the same place: "adb reboot bootloader" puts the device into fastboot mode, but I lose connectivity after that so cannot progress.
Any help would be gratefully received.
Thanks
Uri
---------- Post added at 05:47 PM ---------- Previous post was at 05:29 PM ----------
So to help anyone else, here is how I worked around this.
Keep device manager open when running the "adb reboot bootloader" command.
There, the Zuk Z1 will disappear and pop back up as no driver installed.
Go in and manually install the correct driver (android_usb.inf).
Click to expand...
Click to collapse

swarimk said:
I have a Zuk Z1, I wanted to unlock the bootloader and then root the device.
However, the device doesn't get recognized or listed after the command "fastboot devices".
Any help will be appreciated.
Thanks in advance.
Click to expand...
Click to collapse
uninstall zuk usb driver from your pc and then reinstall it in your pc it may solve your problem.if problem still persists then try using all in one tool to install the drivers again it will definetly solve.

need help

Hello guys, i m facing very serious issue with my device. My volume up button not working at all and when i take my phone to service centre they said they dont have cheap( i didnt know what they said) and they refuse to repair to my phone. Now problem is i m also custom rom lover and try many roms time to time but if i accidenlty mess with my phone and it get brick than how i can go into recovery mode at that situation ?? Please help me if any one know how to go into recovery mode pc using commands. Thank u

I do not understand clearly. Do you have now a working custom ROM? Or now you are on brick/bootloop?
If you have working system:
If ADB -like minimal ADB and fastboot- (and all windowsdriver) is installed on your PC. And USB debugging enabled. And you have a working TWRP.img on your computer for example to minimal ad and fastboot folder. Then.
Connect your phone to PC with USB
Open a command prompt or run "minimal ADB and fastboot" prompt on your PC.
Type on PC prompt: adb devices (+enter)
If every driver installed correctly, then your PC will display the ID ot your Phone.
If displays then type: adb reboot bootloader (+enter)
The your phone will reboot in fastboot mode.
If you have fastboot mode:
Type on PC prompt: fastboot devices (+enter)
If every driver installed correctly, then your PC will display the ID ot your Phone.
If displays then type: fastboot boot TWRP.img (if your img file is not TWRP.img then rename it before) (+enter)
If everything is all right, your phone will reboot to recovery.
小米MIX标准版4GB128GB银色MIUI10中国开发者8.5.31.
---------- Post added at 06:57 PM ---------- Previous post was at 06:31 PM ----------
My developer friend said: you need to go a private service, and ask him to full button replace. He think, it will be solve your problem.
I found a description http://en.miui.com/thread-84580-1-1.html
bit I am not sure, that is yours.
Maybe...
小米MIX标准版4GB128GB银色MIUI10中国开发者8.5.31.

Thanks for reply ....by the way i have already installed twrp recovery...and the method u said using command is work when my phone in bootloader mode ? Because i cant go into recovery mode at that situation because my volume up button not work

Yes.
Install to your PC minimal adb and fastboot.
https://www.mediafire.com/file/rz87kfzmljiwne4/minimal_adb_fastboot_v1.4.2.exe/file
As I said, if you have fastboot (bootloader) [little green droid with fastboot word] mode:
Type on PC prompt: fastboot devices (+enter)
If every driver installed correctly, then your PC will display the ID ot your Phone.
If displays then type: fastboot boot TWRP.img (if your img file is not TWRP.img then rename it before) (+enter)
If everything is all right, your phone will reboot to recovery.
小米MIX标准版4GB128GB银色MIUI10中国开发者8.5.31.

Volume strip available online

Thank u so much

Please note - this is a general section post. Not android development section post.