Hi guys,
for the last 3 days my Galaxy Nexus has been going into bootloop every night. I believe it is when it gets charged fully - I put the phone on the charger, wake up, the phone is off and when I try to turn it on it goes through a bootloop.
I am running stock recovery/4.1.1
The only way I can get to my homescreen is to format System then reflash the stock images via the tool kit. Any ideas on what's happening here? Could this be a hardware issue?
I've had my Nexus for a year now - no issues
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.
The issue
Nexus 7 2013 has a problem where the tablet wont boot, it is stuck on the Google boot logo.
At that point i had tried the recovery mode, yet this flips back into the boot loop.
I had tried the charger option also... no luck there either.
The fix
I left the tablet for 1.5 hours then switched it on as normal.. the tablet decided to come back alive.
Its not the first time this has happened, the last time i done a factory recovery and that kind of solved it for a couple of days.
------------
It seems that this nexus 7 tablet is a lemon and needs to go back unless someone knows the answer >?
I don't know if you've unlocked the bootloader, rooted or flashed a custom recovery/ROM. If you have, I'd suggest completely returning to stock and seeing if that helps. If you haven't done those things or returning to stock doesn't help, send it back.
That's how mine started too, it will get worse until it fails completely. Mine just came back from ASUS on Monday and by Wednesday night it was already boot looping again.
My Galaxy S3 keeps shutting off during boot. I encountered this problem while running Cmod 11. Was using poweramp playing music off my 64gb exFat microsd card, and suddenly Poweramp encounters "Error too many files" and promptly shuts the phone down. (Poweramp has been giving me strange problems before this, like that error just mentioned, and scanning for changes when there are none, but this is the first time the error caused the phone to shut down).
After rebooting it, The S3 gets to the boot screen and upon opening an app, promptly shuts down again. Further attempts result in the phone shutting off during the boot animation, and finally now the phone simply shuts down right before the boot animation. (note: it doesn't reboot. It turns itself off).
I thought it might be a problem with Cmod, so I wiped everything and using CWM, installed slimkat. Same problem. so I went and installed stock android using Odin, and now I'm back to stock. STILL same problem.
When I have the phone plugged into a computer, it seems to get further than the boot animation before shutting down (sometimes it gets to the lockscreen before shutting down again).
Any idea what's causing this problem? I have no problems with erratic shutdowns during recovery and download mode.
How old is your battery? Might be time to replace it.
This is the same battery the phone came with since a couple years ago. Assuming it is a problem with the battery, why does recovery and download mode still work fine?
cheezyphil said:
This is the same battery the phone came with since a couple years ago. Assuming it is a problem with the battery, why does recovery and download mode still work fine?
Click to expand...
Click to collapse
They're not as heavy to load.
Was any modification done to your phone (software) about when that started happening?
The s3's been on and off custom roms for a year now
cheezyphil said:
The s3's been on and off custom roms for a year now
Click to expand...
Click to collapse
I mean before it started happening. Or were you on the same ROM/version of that ROM for a while when it happened.
Been on cmod for a year before it happened. Reverted to stock rom about a month ago to unlock it, and then straight back to cmod. A couple days after coming back to cmod, this happens.
cheezyphil said:
Been on cmod for a year before it happened. Reverted to stock rom about a month ago to unlock it, and then straight back to cmod. A couple days after coming back to cmod, this happens.
Click to expand...
Click to collapse
Well if you can get in recovery, I would suggest doing a clean flash. But chances are that it's your battery giving out.
If you want to test, borrow a battery from another S3. I know with T-Mobile you can go to a store and they usually have a device on hand that you can borrow one from to test it out before spending money on it. I imagine you can do this at AT&T stores as well.
had the same problem with my atnt galaxy s3
i have the same problem,,i am using cm12 ryt now,,i tried to put every single rom and same thing happens,,i also brought it back to its stock firmware,,and still the problem occurs... did u find any solution for it,already?
:crying:
Hello,
I've bought a Hong Kong D855 from ebay when I was visiting US (I'm from Brazil) and for some months it worked flawlessly. SOme 2 months ago it started rebooting and I had to factory reset it. It happened twice a month and every time I had to factory reset, for it would boot normaly and reboot after a few seconds.
So I got to avoid updating apps and avoided installing new ones, because I couldn't find a definite solution on the web.
It was stable for a month but yesterday it happened again, but this time, after a few reboots into the OS, it froze in the LG logo screen.
And this time I can't even hard reset it - it just freezes on the same screen. I tried everything I found on the net - removing the battery, trying download mode (it goes directly to the same LG logo screen) and even just charging is weird (it shows an image of an empty battery with a frozen loading "animation").
I never rooted or did anything besides updating the firmware OTA. I'm on vacation on the beach, so I don't have with me the original charger (I'm using a samsung note 10.1 2014 one) and I don't know what else I could do.
As I've bought it overseas, LG won't cover it with a warranty, so have it officially repaired would be my last resort.
Does anyone have an idea what I could try? Or is it game over for me?
Thanks for any help, folks...
Several days ago I was watching a livestream when my phone froze & suddenly went into bootloop. At this point I've tried all that I know to - I've flashed several different OS versions using the Nexus Root Toolkit, I've manually flashed 6.0.1 & 7.0 (not sure if 7.0 was a good idea to flash tho just because of what's been happening), and at this point I'm not even able to go to the recovery to manually do anything. At one point the phone did work, but it would constantly go back into bootloop for a few minutes before coming back out, but now it is simply stuck in bootloop. I was using Android 6.0.1, stock. The phone was rooted for awhile, but I eventually unrooted and went back to stock. I don't understand what happened, and everything I find on the internet about Nexus 5x bootloop is in relation to the 7.0 update, which I did not bother downloading (luckily lol). Is my phone gone forever? :/
I got my phone replaced some time ago as it also went into a bootloop mid usage. Flashing anything didn't help. My finding was, that the phone worked as long as it was cold. Leaving it off to cool down and putting it on a cooling pad helped for about 10 minutes. From what I understand, it may be a hardware issue.
Gesendet von meinem Nexus 5X mit Tapatalk
See the other threads on here that showed up within the last 1-2 Weeks regarding bootloop, bricked or QHSUSB. Chances are, it might very well be a hardware problem (bad soldering).
My nexus5x suddenly died 5 days ago (with no prior symptoms). Unlocked, no root, stock 7.0 november update.
I was able to turn it on once for ~3hrs after walking outside for 20 minutes, right after it first froze down/bootlooped.
Then it showed up as "QHSUSB_BULK" (8009?) when connected to a pc, but would not even start fastboot anymore.
I tried putting it in the freezer in a plastic bag for ~10 minutes. Fastboot worked, booting freezed inbetween; twrp would not let me enter security pattern.
So I let it rest for two days. Then decided to give it one more try by putting it on my radiator for 20 minutes (just warm, not hot! - please don't panic and make the situation even worse!)
Got it to boot up regularly and keep it on for ~20 minutes. So was able to do one last backup of msgs, imgs, etc. (while still on the radiator). Booted up successfully two more times, but with every decreasing on-time.
RMAing now through Google.