Database Users

My N7 ran out of power and now loops the Google Screen over and over...

My N7 ran out of power and shut off. I immediately put it on the charger and it turned on for a minute (without me turning it on) and then powered off again. After that it booted to the White "Google" screen and continues to reboot into this screen.
I can get into fastboot (holding power and the volume down) where I have options to Power off, restart bootloader, recovery mode (which shows me the red triangle and says "no command"), or start.
I am not rooted and the bootloader is still locked.
I'm good at following directions and have tried what I thought were solutions but nothing seems to be working... or perhaps I am just retarded (no offense to people who are actually retarded) I think I have installed the correct drivers but I still can't get the cmd prompt screen to show my device when I type adb devices
How do I fix this? I don't want to send it back and deal with that hassle!
Thanks in advance and I apologize up front for what is probably a simple fix but I couldn't find any other posts with a solution that has worked for me.

Wot-75 said:
My N7 ran out of power and shut off. I immediately put it on the charger and it turned on for a minute (without me turning it on) and then powered off again. After that it booted to the White "Google" screen and continues to reboot into this screen.
I can get into fastboot (holding power and the volume down) where I have options to Power off, restart bootloader, recovery mode (which shows me the red triangle and says "no command"), or start.
I am not rooted and the bootloader is still locked.
I'm good at following directions and have tried what I thought were solutions but nothing seems to be working... or perhaps I am just retarded (no offense to people who are actually retarded) I think I have installed the correct drivers but I still can't get the cmd prompt screen to show my device when I type adb devices
How do I fix this? I don't want to send it back and deal with that hassle!
Thanks in advance and I apologize up front for what is probably a simple fix but I couldn't find any other posts with a solution that has worked for me.
Click to expand...
Click to collapse
In boot loader you use fast boot commands. Type "fastboot devices". If listed type "fastboot reboot". If its still stuck in loop try and taking back cover off and disconnecting battery for a few seconds, reassemble and power on.
Sent from my Nexus 7 using xda premium

Gizmoe said:
In boot loader you use fast boot commands. Type "fastboot devices". If listed type "fastboot reboot". If its still stuck in loop try and taking back cover off and disconnecting battery for a few seconds, reassemble and power on.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Thanks. The battery pull didn't work however your tip on typing fastboot instead of adb worked and it recognized my device. Consequently I was able to flash the stock image and start over with setup and etc.. which sucks but it's better than sending it back in and all that mess.
Thanks!

Nexus 10 stuck in bootloop "X"

hello
after i try to unlock the bootloader my nexus stuck in "X" (with toolkit 2.0)
and the recovery mod is not work (Attachments)

I had the same problem when unlocking mine, reboot into fast boot and use the volume buttons to change the select option to recover and hit power, you should get a picture of an android with a red triangle that's normal , then try a couple times to hit the power and both volume buttons to boot into the stock recovery and then do a full wipe and factory reset (wipe both cache and dalvik cache just yo be safe) you may have to do this more then once, I did but it fixed the problem
Sent from my Infected HTC Rezound using xda premium

Just get back into recovery and factory reset. This is a common issue when unlocking bootloader.

Please help as I seem to have placed my Nexus 10 into a Bootloop state through Nexus Root Toolkit 1.6.8 by WugFresh. I have been attempting to enter into Recovery following the steps outlined here (http://forum.xda-developers.com/showthread.php?t=2239524). However, the tablet never seems to enter Recovery mode. At best I get a blank screen that eventually comes around to an unusable Bootloader. By unusable, I mean the volume buttons do not progress through the options. If select Recovery on a functional Bootloader and simply press the Power button. The tablet will cycle through to an Android with the red symbol.
Now the Toolkit no longer even see's my device even though Win 8 Device Manager shows the Android Bootloader Interface. There are no devices listed with the exclamation point warning symbol.
This is only my third attempt at Unlocking and Rooting a device. The first two times were successful on an HTC phone and a Samsung Tab 7". I do not know where to go from here and really need help fixing my Nexus 10.
Thank you in advance for any help you can offer.
Edit: I figured out how to access Recovery. I needed to use power + volume up once on the screen with the Android avatar and red symbol.

OvrTehBottm said:
Please help as I seem to have placed my Nexus 10 into a Bootloop state through Nexus Root Toolkit 1.6.8 by WugFresh. I have been attempting to enter into Recovery following the steps outlined here (http://forum.xda-developers.com/showthread.php?t=2239524). However, the tablet never seems to enter Recovery mode. At best I get a blank screen that eventually comes around to an unusable Bootloader. By unusable, I mean the volume buttons do not progress through the options. If select Recovery on a functional Bootloader and simply press the Power button. The tablet will cycle through to an Android with the red symbol.
Now the Toolkit no longer even see's my device even though Win 8 Device Manager shows the Android Bootloader Interface. There are no devices listed with the exclamation point warning symbol.
This is only my third attempt at Unlocking and Rooting a device. The first two times were successful on an HTC phone and a Samsung Tab 7". I do not know where to go from here and really need help fixing my Nexus 10.
Thank you in advance for any help you can offer.
Edit: I figured out how to access Recovery. I needed to use power + volume up once on the screen with the Android avatar and red symbol.
Click to expand...
Click to collapse
In stock recovery, wipe the data (it may be called system reset or something) u should be good to go.
Sent from my Nexus 10 using Tapatalk 4

OvrTehBottm said:
Please help as I seem to have placed my Nexus 10 into a Bootloop state through Nexus Root Toolkit 1.6.8 by WugFresh. I have been attempting to enter into Recovery following the steps outlined here (http://forum.xda-developers.com/showthread.php?t=2239524). However, the tablet never seems to enter Recovery mode. At best I get a blank screen that eventually comes around to an unusable Bootloader. By unusable, I mean the volume buttons do not progress through the options. If select Recovery on a functional Bootloader and simply press the Power button. The tablet will cycle through to an Android with the red symbol.
Now the Toolkit no longer even see's my device even though Win 8 Device Manager shows the Android Bootloader Interface. There are no devices listed with the exclamation point warning symbol.
This is only my third attempt at Unlocking and Rooting a device. The first two times were successful on an HTC phone and a Samsung Tab 7". I do not know where to go from here and really need help fixing my Nexus 10.
Thank you in advance for any help you can offer.
Edit: I figured out how to access Recovery. I needed to use power + volume up once on the screen with the Android avatar and red symbol.
Click to expand...
Click to collapse
If the suggestion of newell79 didn't work you can try to flash the Factory image..
Sent from my Galaxy Nexus using XDA Premium HD app

[Solved]
mrgnex said:
If the suggestion of newell79 didn't work you can try to flash the Factory image..
Sent from my Galaxy Nexus using XDA Premium HD app
Click to expand...
Click to collapse
Before discovering how to enter Recovery properly, I did end up flashing to stock. Unfortunately, I am unable to get ADB to recognize my Nexus 10 using Wug's scripts, even though the ADB installer see's the unit. I believe this is a Windows 8 issue, but I am not 100% positive. That said, I did further research and found another method using the Fastboot command line which did work. My Nexus 10 is now unlocked and rooted. I wish I had kept the thread's URL to the other method.
I wonder if my issue's come from not uninstalling the Samsung G3 through device manager as I did my Nexus 10. I did uninstall though the USB app found within Wug's, but that may not have been enough. That is certainly something I shall try in the future.

[Info] Guide to entering safe mode, bootloader, stock recovery

Yes, I know, everyone knows how to enter safe mode, bootloader, and recovery.
I found there are some inconsistencies to entering and using recovery depending on your which software you are running. In addition there are multiple ways of entering stock recovery.
Also I always see people asking this question because somehow the keypress order is not intuitive.
Entering Safe Mode
Tablet booted and running Android
Press/Hold Power button until power menu shows up
Tap/Hold Power off option
Choose OK to reboot in safe mode
Tablet powered down
Press/Hold Power button until Google screen shows up, RELEASE Power button
Press/Hold VolDn until Android has booted up
If successful, you will see Safe mode overlayed on bottom left of screen.
Entering Bootloader (ie fastboot mode)
Tablet booted and running Android
From adb
adb reboot bootloader
can also choose recovery from menu after bootloader comes up
From app
Use Quick Boot from Google Play
Tablet powered down
Power+VolDn while booting to enter bootloader
Release buttons after you see bootloader screen
Entering Stock Recovery
Tablet booted and running Android
From adb
adb reboot recovery
From app
Use Quick Boot from Google Play
Tablet powered down
Power+VolUp while booting to enter recovery
You can release buttons after you see Google on screen
When Stock Recovery starts you will see the Android fallen down screen
To bring up the Recovery menu
Power+VolUp to show recovery menu
Must be this sequence Press/Hold Power, THEN Press/Release VolUp, release Power
Within menu
VolUp to move up
VolDn to move down
Power to select
In addition, I found an inconsistency with JSS15J stock recovery that wasn't in the JWR66N recovery
While at the Android fallen down screen if you mistakenly press
VolUp
instead of
Power+VolUp
you will still get the Recovery menu.
However, VolUp will no longer function. It will instead become a toggle for switching between the Recovery menu and the Android fallen down screen
Android fallen down screen
VolUp to toggle recovery menu
Within menu
VolUp does not work since it toggles recovery menu
VolDn to move down
Power to select

sfhub said:
Entering Stock Recovery
Tablet booted and running Android
From adb
adb reboot recovey
Click to expand...
Click to collapse
Are you sure with this command. I think it must be => adb reboot recovery <= or am I wrong ???

pRo_lama said:
Are you sure with this command. I think it must be => adb reboot recovery <= or am I wrong ???
Click to expand...
Click to collapse
Sorry, typo, fixed.

i`m on completely stock JSS15Q and i cant get into stock recovery. When im trying i see "no command" and red exclamation mark on the laying robot. What should i do?

laska300 said:
i`m on completely stock JSS15Q and i cant get into stock recovery. When im trying i see "no command" and red exclamation mark on the laying robot. What should i do?
Click to expand...
Click to collapse
sfhub said:
Entering Stock Recovery
Tablet powered down
Power+VolUp while booting to enter recovery
You can release buttons after you see Google on screen
When Stock Recovery starts you will see the Android fallen down screen
To bring up the Recovery menu
Power+VolUp to show recovery menu
Must be this sequence Press/Hold Power, THEN Press/Release VolUp, release Power
Within menu
VolUp to move up
VolDn to move down
Power to select
Click to expand...
Click to collapse
Please see RED section

Does the presence or absence of the red exclamation triangle mean anything?

Wot does safe mode do?

Anderson2 said:
Does the presence or absence of the red exclamation triangle mean anything?
Click to expand...
Click to collapse
I don't remember if there are two images one with and one without the triangle. I think I've only seen the image with the red exclamation point.
I've never seen anything to indicate the red exclamation mark is something you need to pay attention to.
Now if you apply an update and there is an error, then that is something I would pay attention to.

LoVeRice said:
Wot does safe mode do?
Click to expand...
Click to collapse
It doesn't load the stuff you added.
It is similar to safe mode on a PC, used to diagnose whether the issue is in the stock ROM or is in something you introduced by installing some app.

I Have a probleme
since a bought TAB 3 10.1 and it's boot into safe mode i'v restart it and turrn it off the back on but it didn't go what should i do ?

This thread is about nexus 7.

sfhub said:
This thread is about nexus 7.
Click to expand...
Click to collapse
oh sorry i was panic so i searched in every thing

Bootloader
If none of that works, try the command with a dash "adb reboot-bootloader" Depends on your device sometimes, sometimes unplugging your device right after you enter this command will keep it from getting stuck at the boot logo screen. If that doesn't work, hold the power button to power device down and then boot it into recovery instead using the button combo. Then you can wipe cache & start all over again.

I'm not even able to get into Recovery. I can get to the bootloader, then I select "Recovery mode" and it shows the Google logo, but it never goes into recovery. I have let it sit at the Google logo for a couple of hours, and end up just holding down the power button to shut it down.
I have tried Skipsofts toolkit, as well as Wug's, to try to unlock the bootloader. This ends up with the device hanging at the "Unlock bootloader" screen after selecting "Yes". Again, I have left it in this state for well over an hour with no change.
Here's some info on my 2013 Nexus 7:
KitKat 4.4.4
Never rooted
Never unlocked bootloader
HW version rev-e
Bootloader version FLO-04.02
I suspect my Nexus knew I was supposed to go on travel next week and is faking sick.
Any help would be appreciated. Thanks.

Hi guys i have a google nexus 5 and it is locked state. It is getting booted again and again but it jiust reaches google logo and again restarts. Safe boot is also enabled so i cant enter in recovery mode also. Please help me ASAP.

Stuck in Boot Loop

Have searched the forum but came up empty.
Hoping someone can help.
Purchased the phone used back in December and have been using it as-is. Two OTA updates came through fine. The latest OTA update has it stuck in a boot loop.
- I can get to fastboot with power and volume down buttons but all of the options either turn it off or stick it back in the loop again (Essential logo with powered by Android, NO dot animation)
- Can't see it via "adb devices" since developer mode was likely not enabled
- "fastboot devices" can see the phone but can't change slots or do anything else
I saw two other people who've posted something similar but no solution. Is my phone garbage?
Any help is appreciated.

harpoon said:
Have searched the forum but came up empty.
Hoping someone can help.
Purchased the phone used back in December and have been using it as-is. Two OTA updates came through fine. The latest OTA update has it stuck in a boot loop.
- I can get to fastboot with power and volume down buttons but all of the options either turn it off or stick it back in the loop again (Essential logo with powered by Android, NO dot animation)
- Can't see it via "adb devices" since developer mode was likely not enabled
- "fastboot devices" can see the phone but can't change slots or do anything else
I saw two other people who've posted something similar but no solution. Is my phone garbage?
Any help is appreciated.
Click to expand...
Click to collapse
Damn, that's a bit unlucky, this March update said it would make recovery from a loop after OTA update easier to recover from, which might just have helped you. Sorry not sure how to help fix at present.

you can try flashing one of these https://forum.xda-developers.com/essential-phone/development/stock-7-1-1-nmj20d-t3701681
be sure to pick one with the fastboot images

harpoon said:
- Can't see it via "adb devices" since developer mode was likely not enabled
- "fastboot devices" can see the phone but can't change slots or do anything else
Click to expand...
Click to collapse
A couple of questions:
- Is your BL unlocked (or is OEM Unlocking enabled)?
What happens if you try executing "fastboot flashing unlock"? NOTE: this would WIPE your data if successful.
- Can you get to the Recovery mode? It's when you pick "Recovery" option from fastboot mode, see the lying android with an exclamation sign, then hold Power and press VolumeUp to get to the Recovery menu.

kt-Froggy said:
A couple of questions:
- Is your BL unlocked (or is OEM Unlocking enabled)?
What happens if you try executing "fastboot flashing unlock"? NOTE: this would WIPE your data if successful.
- Can you get to the Recovery mode? It's when you pick "Recovery" option from fastboot mode, see the lying android with an exclamation sign, then hold Power and press VolumeUp to get to the Recovery menu.
Click to expand...
Click to collapse
Thanks for your response.
- I dont belive OEM unlocking is enabled.
- I can get to the fastboot menu, but the recovery mode option just takes me back to the 'powered by android' logo, not the green dead robot.
- When I try fastboot flashing unlock, I get the below error:
=============
FAILED (remote: Flashing Unlock is not allowed
)
finished. total time: 0.013s
=============

yenkoPR said:
you can try flashing one of these https://forum.xda-developers.com/essential-phone/development/stock-7-1-1-nmj20d-t3701681
be sure to pick one with the fastboot images
Click to expand...
Click to collapse
Will this work even though I cannot see the device via adb? AND the device state is "locked".

harpoon said:
- I dont belive OEM unlocking is enabled.
- I can get to the fastboot menu, but the recovery mode option just takes me back to the 'powered by android' logo, not the green dead robot.
- When I try fastboot flashing unlock, I get the below error:
Click to expand...
Click to collapse
Dang... :\ Yeah, the last error means you don't have OEM unlock enabled. So, you can't flash the bts image via fastboot. One last thing I could think of is trying to get to recovery by the button combo. Although, if you are correct in saying you don't have USB debug enabled, it won't do much good, i.e. you won't be able to flash an OTA... :\
While device is OFF, press and hold Volume-Up button while pushing Power button to boot.
Your device will now be in Recovery mode. An Android logo with red exclamation mark should appear on screen. Hold the Power button, then press the Volume-Up button one time to see the recovery menu.

can you try this command on bootloader:
fastboot OEM unlock

harpoon said:
Have searched the forum but came up empty.
Hoping someone can help.
Purchased the phone used back in December and have been using it as-is. Two OTA updates came through fine. The latest OTA update has it stuck in a boot loop.
- I can get to fastboot with power and volume down buttons but all of the options either turn it off or stick it back in the loop again (Essential logo with powered by Android, NO dot animation)
- Can't see it via "adb devices" since developer mode was likely not enabled
- "fastboot devices" can see the phone but can't change slots or do anything else
I saw two other people who've posted something similar but no solution. Is my phone garbage?
Any help is appreciated.
Click to expand...
Click to collapse
Hi. A long time has passed and I want to know if you have solved your problem. I came across the same)

Rudter said:
Hi. A long time has passed and I want to know if you have solved your problem. I came across the same)
Click to expand...
Click to collapse
Nothing ! ..
my ph-1 still into the drawer ! .

N7 (tilapia) stuck at logo - no fastboot access ...

Hello everybody,
I hope somebody can help me to save my N7 (2012).
I installed TWRP without problems and after that I tried to flash a custom rom - which, for some reasons, didn't work.
After reboot my Nexus is stuck at Google logo with an opened lock at bottom...
I can't get to fastboot because when I power on while pushing VOL - button it just get stuck at the same logo screen.
If I keep power button pressed for about 10s, it shuts down but after a few seconds it boots again just to get stuck again at the logo screen...
The only way to shut it down completely is to keep VOL+ button pressed while pressing the power button.
My Windows 7 computer won't recognize the N7 at all anymore, but when I shut it down completely (Power & VOL+), windows says "Unknown device".
Is my Nexus still to be saved or I can throw it away?
Thank you in advance for each advice.
Conrad

Conrad-007 said:
Hello everybody,
I hope somebody can help me to save my N7 (2012).
I installed TWRP without problems and after that I tried to flash a custom rom - which, for some reasons, didn't work.
After reboot my Nexus is stuck at Google logo with an opened lock at bottom...
I can't get to fastboot because when I power on while pushing VOL - button it just get stuck at the same logo screen.
If I keep power button pressed for about 10s, it shuts down but after a few seconds it boots again just to get stuck again at the logo screen...
The only way to shut it down completely is to keep VOL+ button pressed while pressing the power button.
My Windows 7 computer won't recognize the N7 at all anymore, but when I shut it down completely (Power & VOL+), windows says "Unknown device".
Is my Nexus still to be saved or I can throw it away?
Thank you in advance for each advice.
Conrad
Click to expand...
Click to collapse
Hi, Conrad-007...
This is very strange - your Nexus 7 is clearly 'bootable' (sort of), with a functioning bootloader, ie., it's not hardbricked... or you wouldn't be seeing the Google logo.
In the distant past, back when I used to experiment with custom kernels on my Nexus 7, it sometimes required the POWER BUTTON+VOL DOWN buttons be pressed and held down for a good 30 seconds or more, to generate the necessary 'interrupt', and force the device into the bootloader.
My first instinct, is to suggest you may possibly have a problem with your VOL DOWN button, and maybe it's stuck somehow or not making contact.
It also occurred to me, that you might be able to access the bootloader with...
Code:
adb reboot bootloader
...or possibly...
Code:
adb reboot fastboot
...and even...
Code:
adb reboot recovery
But unfortunately, I'm pretty sure you need to be running fully booted Android or booted into a custom recovery (eg., TWRP) before you can issue ADB commands. I haven't tinkered around in this area of Android for a couple of years now, so my memory of the specifics is a little hazy.
Anyhow, here's a fairly comprehensive listing of Nexus 7 button presses/interrupts, which maybe of some use...
https://forum.xda-developers.com/showthread.php?p=37606945#post37606945
--------------------------------
Anyway, just some thoughts that might give you some clues/ideas, that may resolve your problem.
Good luck, and I hope you find something that works.
Rgrds,
Ged.

Thanks Ged for the detailed answer.
Unfortunately it seems that my Nexus is not booting complete (not finishing the booting sequence due to corrupted bootloader?) and so I cannot send to it any adb or fastboot command...
I read in the meantime that holding the VOL up button while powering up the Nexus, it will bring it in the APX mode (whatever this mean) and indeed, my computer recognize it as "APX" device.
I hope at least that this is a good sign and a first step to bring my Nexus back to life... but I have no idea what is the APX mode and what can I do in this mode to attempt to save my device...
Do you (or somebody else) have (has) an advice or tutorial for me concerning this?
Regards,
Conrad

Hi Conrad.
I'm in exactly the same situation (I've mistakenly posted a duplicate thread here https://forum.xda-developers.com/nexus-7/general/bricked-tilapia-t4005149). Let's continue here. So:
1. I spent 4 hours trying all possible button press combinations, including VERY long presses. I didn't notice any APX device or Uknown device connected to Windows. I might have missed it, you gave me hope. I will check again.
2. APX mode enables low level access to the chipset via nVidia tool nvflash. You probably came accross these threads here on xda:
https://forum.xda-developers.com/nexus-7/general/tutorial-how-to-unbrick-nexus-7-using-t3342364
https://forum.xda-developers.com/showthread.php?t=2564615
https://forum.xda-developers.com/showthread.php?t=2455927
https://forum.xda-developers.com/showthread.php?t=2340237
I haven't so far, as I was not aware of the visibilty of the tablet in Windows. I will check again.

Well, I must have been blind not to have seen all the posts here on xda and everywhere else. I went through the threads and now I know:
1. I can see the tablet in APX mode in Windows. Possibly I could correctly set up the driver.
2. This would be totally useless, since I hadn't backed up necessary blob.
I have a new paperweight