Out of the blue my Nexus 7 2013 got stuck at booting up. At first it would get to the spinning coloured circles animation forever, now it doesn't advance beyond the Google logo. I don't think I had enabled USB debugging. What are my options now? I want to save the data on it if possible.
It was running 4.4.4 when this happened, unrelated to Lollipop.
Related
I'm running stock ICS, no roms, no root, just the regular version of Android that game on my Verizon Wireless Galaxy Nexus. Last night the battery drained and I recharged it while I slept using the charger that came with the phone. When I woke up I turned my phone on. The Google logo came up, it vibrated, and then the colors boot animation started. After a few seconds, the animation froze and then the Google logo came back up, it vibrated, and the colors boot animation started again, then froze. It keeps doing this over and over.
I can enter recovery mode and download mode. I made a video of my problem and posted it on YouTube:
Bah! new users can't post outside links >:-(
watch?v=OrrGNMtU8Lc
Is there anyway I can get my phone bootable without wiping the memory? Is there anyway I can access the contents of the phone on my computer while it is in this non-bootable state?
If not, then what is the best way for me to get my phone back to a bootable state? I have never messed around with rooting or roms for Android so I would need to know the best place to start. I have messed with custom roms for my old Treo and some game consoles, so I have some experience following tutorials.
Hello all,
I poked around and saw some similar issues, but nothing quite like what I am facing and was hoping you all could help me.
I woke up this morning to find my nexus 7 2013 32 gig wifi only on the "Google" logo loading screen. The tablet will not boot up into android.
I read up a little bit and found that I can factory reset using adb and fastboot...but here is my problem...USB Debugging is not enabled on my tablet, and I cannot access android to turn it on. Therefore, adb is not recognizing my device. If I try to enter recovery from the bootloader screen I get the same "Google" logo.
My bootloader is locked.
Really hoping someone who knows more than I about how these things work can help.
Thanks in advance for any assistance you can provide.
help! my Galaxy nexus is stuck in a boot loop the X animation... with the glowing blue, red, yellow, green.. it was rooted and i believe it was on JB.. but it may have been Kit Kat.. i tried to just pop out the batt and let is set for a big.. did no good... still boot loop... i have tired to get to recovery by Power on Vol- did no good... still boot loop.. at this point i dont care if the phone is wiped clean.. i have it all backed up... but its just a cool paper weight now.... so with the phone in infinite boot loop... what is my next step.... if just want to flash a new rom or something... its un rooted but stock... kinda lots here... help?
edit:
i can get into odin mode.. home + DN
but
when i try home +up all i get is boot loop... even after doing the remove battery thing...
have tried the nexus root toolkit.. will not see the device says i need to enable ADB on the galaxy nexus.... which i cannot do because i am in a boot loop... this is looking bad and worse!
edit: sorted... back to ICS.. so now its time to find a stable version of KitKat or Lollipop... any ideas?
I'm curious to find out if I can get the N7 boot splash logo (not the boot animation) to landscape orientation like the Nexus 10? For an in dash hardwired install. Any Ideas out here would be greatly appreciated
The logo is within secure boot process and can not be modified.
k23m said:
The logo is within secure boot process and can not be modified.
Click to expand...
Click to collapse
I knew it. Sigh
Not my first rodeo on this.. running latest beta on my Essential Phone.
I just got a Pixel 2 XL tonight (refurb, was on May 8.1 when I booted it) and I was able to get into Android and toggle OEM unlocked. Did both normal and critical unlocks fine. Flashed latest P beta and after reboot I got a red text screen saying the device was corrupt (not the regular orange text bootloader warning message). Device booted to white Google logo screen with lock (in locked position). It rebooted on its own and same error messages, then got to Google white logo screen with the same lock and sat there for at least 15 minutes before I power cycled it. Same happened again. Went into recovery and factory reset. Same thing, stuck at white screen. Flashed back to 8.1 July update. Same 2 error messages on boot. Did the first short boot to white screen again and reboot again. Stuck at the white logo screen again on 8.1. Started the process over flashing latest P beta again. Same results.\
I should note that my Essential Phone never saw that red message even with leaving the bootloader unlocked, only the orange one. That phone is still working fine on latest beta. That also means I know my USB ports and USB cables are sound.
I'm totally stuck at white screen on boot no matter what I do after flashing. I can't even get 8.1 booting anymore. Flashing all seems to work for both P and 8.1, no errors. Tried a different USB cable and also different USB port. No luck. What's going on? Why can't I get this thing to boot at all past the logo now? Help!
elkay said:
Not my first rodeo on this.. running latest beta on my Essential Phone.
I just got a Pixel 2 XL tonight (refurb, was on May 8.1 when I booted it) and I was able to get into Android and toggle OEM unlocked. Did both normal and critical unlocks fine. Flashed latest P beta and after reboot I got a red text screen saying the device was corrupt (not the regular orange text bootloader warning message). Device booted to white Google logo screen with lock (in locked position). It rebooted on its own and same error messages, then got to Google white logo screen with the same lock and sat there for at least 15 minutes before I power cycled it. Same happened again. Went into recovery and factory reset. Same thing, stuck at white screen. Flashed back to 8.1 July update. Same 2 error messages on boot. Did the first short boot to white screen again and reboot again. Stuck at the white logo screen again on 8.1. Started the process over flashing latest P beta again. Same results.\
I should note that my Essential Phone never saw that red message even with leaving the bootloader unlocked, only the orange one. That phone is still working fine on latest beta. That also means I know my USB ports and USB cables are sound.
I'm totally stuck at white screen on boot no matter what I do after flashing. I can't even get 8.1 booting anymore. Flashing all seems to work for both P and 8.1, no errors. Tried a different USB cable and also different USB port. No luck. What's going on? Why can't I get this thing to boot at all past the logo now? Help!
Click to expand...
Click to collapse
Most likley an issue with the boot.img if your doing flashall.bat make sure you have the newset adb/fastboot files
Does essential have a and b partition?
I know the pixels do and is part of the reason these roms are trickier.
Sent from my Pixel 2 XL using Tapatalk
Fixed it. Caused my own pain (sort of). Path to my platform-tools was changed to an old version (not sure what changed my path grrrrr).
Lucky of 2 things: 1) That I didn't blow out my bootloader and 2) Nothing else caused permanent partition issues.
Anyway, I would recommend anyone else that runs into this issue to be absolutely sure you're running the current version of the platform tools (*all* of them, not just fastboot.exe). Now my device just booted up and with only the usual orange message. Red message is gone.