Last week my tablet froze at 5am (the screen was on and the clock stuck).
Since then, it randomly freezes (and sometimes reboots) -- hard lock.
I've tried wiping, new ROMs, etc. The freezes even occur in clockwork recovery.
Am I out of luck?
If it freezes both in normal mode and even in recovery, I would say you're out of luck.
requist said:
If it freezes both in normal mode and even in recovery, I would say you're out of luck.
Click to expand...
Click to collapse
I just logcat'd a few lockups, no clues whatsoever
Time to wipe and trash.
In recovery the tab is in a known state, freshly booted, no user programs, different states or options. If it is freezing in this mode it means either the loaded image is incorrect or the handling of this image is incorrect. The handling would mean a hardware error because other tabs with exact the same image and options work normally. An error of the image would be possible without hardware error but very unlikely since loading a different image (normal mode) gives the same problems.
I would guess a problem with either sd or normal ram. No clue what a repair would cost but is it already past guarantee? (Else I would try to recover to stock rom and bring it back to the store..)
Related
Couldn't find a similar thread so I thought i'd post my problem.
Beginning last night, after watching a video using Pulse I realized the sound wasn't working. I restarted the Nexus 7, had the sound working again, but the device froze during the video (in pulse), and then reset on its own.
Since then, the Nexus 7 will reboot, then once on, will freeze after 30 seconds - 2 minutes, reboot again, and just loop in that pattern. Sometimes when it turns out, I'm not even able to unlock it before it reboots again.
Even if I turn off the Nexus 7 when I get the chance, it will turn on itself and continue the freeze -> reboot loop.
Right now I've been letting the loop continue until the battery runs out to see if it fixes the problem. Until then, has anyone else faced this issue? Any solution?
Details: An unrooted Nexus 7, few apps, only thing off market was to enable flash, got the device 2 weeks ago
Bump to see if anyone has a solution.
Will post a video of what happens when I get home from work.
Haven't heard of this before.... what happens if you boot into bootloader? Perhaps you just need to do a full wipe and re-install.
It actually freezes on bootload.
When I do a force turn off (power and volume down), it will turn off, then turn on by itself and continue the bootloop
Will try to upload a video of what is happening soon.
I have the exact same issue.
Can't restore or reflash because it won't go into bootloader\recovery.
What it WILL do is reboot incessantly. SUffice it to say I'm pretty pissed. This just happened suddenly.
I had not rebooted in a few days so I rebooted, and now it won't stop.
The only change I have made is I disable the magazine app because I read that it's a battery hog and I just do not use it. I can;t imagine disabling the magazine app would result in a full on boot loop where even recovery fails...
-M
I would reflash recovery while in the boot loader through adb. That is what fixed my similar problem
kevlars9 said:
I would reflash recovery while in the boot loader through adb. That is what fixed my similar problem
Click to expand...
Click to collapse
I have the same kind of issue. Left to itself the device reboots until the 'Google' display every 1 minute or so. When trying to get into bootloader it freezes when the Android on its back shows up....
So it seems no flashing is possible. BTW this happened when I tried to uninstall an app, similar scenario to some others reporting this type of problem.
I guess the next stop is the Chocolate Factory helpline :/
I contacted the Googleplex helpline at 6 am Pacific time and Anthony kindly promised a replacement unit for next week... No tech explanation or other info was revealed. Purchase from Google Play in the UK.
Finally given a solution, though a very annoying one.
Basically, since you have about 30 seconds - 2 minutes everytime it loads up, I was just told to try and see if I can factory reset from settings within that time frame. Took a 3 attempts (sometimes it would reboot while loading), but eventually got the factory reset going. Luckily I've only had this thing for less than 2 weeks and didn't have much stuff needed to back up.
Right on, glad to hear you got it sorted - in my case. though, this solution would not have worked, as mine never booted all the way through but got stuck at the boot logo (just in case others are reading this with similar problems). So it sems there are at least 2, possibly more, problem scenarios of this type.
My replacement unit from Google Play just arrived - impressed by the speed of proceedings (inside 2 working days from reporting to receiving in Scottish Highlands). Let's see how this one pans out...
HEy problem plss help Boot loop on N7
Hey my nxus wint get out of a boot loop and i cant get in to recovery mode by bootloader this have ben going on for some time and it started when i flashed a new rom ( Paranoide android )on my Nexus 7:fingers-crossed:
Eternal 2013 Nexus 7 reboot loop
Last night my Nexus 7 2013 started going into a reboot loop and would not stop no matter what efforts I made to stop it.
It started when the Billguard application tried to apply an update. The update gets halfway and then forces the tablet to reboot every 30 seconds. I tried disabling the Wi-Fi to stop the update from happening. I even disabled automatic updates and the reboot still happens restoring the tablet to its previous state. I even tried uninstalling the application which appeared to be successful but then immediately rebooted the tablet to the previous state.
After calling Google tech support and only receiving minimal efforts to stop the tablet from rebooting. All efforts were unsuccessful. I even tried uninstalling the application which then instantly rebooted the Nexus seven and attempted the update agaian forcing it back into the reboot loop.
I then tried to do an android device manager erase which was not acknowledged or completed even when my Nexus 7 goes online.
Any help would be appreciated.
Thanks,
I have a very similar problem. However, it began from no changes to my system. I am on Legolas' All-F2FS Recovery and the SlimKat F2FS system. At first I got stuck in a boot loop, and could get into fastboot, but cannot boot back to the custom recovery. Now, I get past the bootloop but cannot get past the loading screen, and still cannot get into recovery. I've tried wiping cache, I've tried reloading the recovery via fastboot -- but since all I have is fastboot access, I don't know what else to do. All my partitions are F2FS, so I am afraid to try moving back to any standard ext4 recovery. I am very interested in this thread, as I feel our issues are related. Keep me updated, and I will do the same if I find anything useful.
Any help I suspect is appreciated by more than just myself.
BTW, removing back and leaving battery unplugged for a while (which had helped with other bootloop issues) did not fix this one, nor did the cold boot from fastboot with usb plugged in to boot recovery.
superdave132 said:
Last night my Nexus 7 2013 started going into a reboot loop and would not stop no matter what efforts I made to stop it.
It started when the Billguard application tried to apply an update. The update gets halfway and then forces the tablet to reboot every 30 seconds. I tried disabling the Wi-Fi to stop the update from happening. I even disabled automatic updates and the reboot still happens restoring the tablet to its previous state. I even tried uninstalling the application which appeared to be successful but then immediately rebooted the tablet to the previous state.
After calling Google tech support and only receiving minimal efforts to stop the tablet from rebooting. All efforts were unsuccessful. I even tried uninstalling the application which then instantly rebooted the Nexus seven and attempted the update agaian forcing it back into the reboot loop.
I then tried to do an android device manager erase which was not acknowledged or completed even when my Nexus 7 goes online.
Any help would be appreciated.
Thanks,
Click to expand...
Click to collapse
I found a fix that worked for me!
I have Minimal ADB & Fastboot installed on my computer. If you're comfortable with the idea of connecting to your Nexus when it is in bootloader download (Fastboot mode), you can try this.
First, I downloaded a full reset file from https://developers.google.com/android/nexus/images:
The ones you'll want are either:
this one for 4.4.2
this one for 4.4.4
I unzipped the appropriate one directly into my ADB directory, and then executed the "flash-all" script by literally typing in "flash all" into the prompt.
This installed all of the default bootloader, recovery and system back onto my Nexus 7 (btw two names for the nexus are "Grouper" and "nakasi"). Then, I was able to clean boot into a reset Nexus 7 system. It was still unlocked. From there, I was able to reinstall a custom recovery (I went with TMW), and even reinstalled a custom ROM (I always stick with SlimKat, personally).
Note: You should also wipe data from the custom recovery once you've installed it.
Second note: In order to be able to load this stuff, I believe you have to unlock your system
To unlock your system in fastboot: fastboot oem unlock
I sincerely hope this helps you (and anyone else stuck in a similar situation to where I found myself). I had completely set my system up with F2FS, and now I'm back to EXT4. BUT, I have a custom recovery, custom rom and root access. Can't complain.:highfive:
Nexus 7 (2012)
4.4.4 Stock
KTU84P
HW Version - ER3
Bootloader Version - 4.23
Locked Bootloader
Not Rooted
I have a Nexus 7 sitting in front of me that was dropped off by my aunt in hopes that I could repair it for her. It doesn't look too promising, but I thought I'd consult the mighty fine people here on XDA before I give her the bad news. Here's what she says happened. Yesterday, while preforming day to day activities on it (browsing internet, Skyping, Facebook, etc), the device completely froze. After holding down the Power Button and forcing it to shutdown, she booted it back up. Everything seemed to functioned properly for about 30s - 1min when, at that time, the device turned off and rebooted on its own. After booting back up, it started to repeat this cycle. Basically getting stuck in a bootloop. I personally have never witnessed a bootloop like this before, where the device successfully boots up completely into the OS before turning off and repeating. I'm more used to dealing with ones where it might go as far as the manufacturer logo and then repeats. So anway, as I stated, I only have a 30s - 1min window where I can make changes in order to troubleshoot. The first thing I figured I should do was to go into "About Device", turn Developer Mode on and get USB Debugging enabled. I was able to do this and used "adb devices" to confirm its connection to my computer before it looped again. After its next bootloop I headed back into settings because I wanted to take note of the Android version she was running. As I was navigating there, I noticed that the Developer Options were no longer active. Basically as if I hadn't enabled them yet. This made me start thinking that changes being made on the device weren't sticking. I decided to make a few visual changes to the home screen and see if they were still there after the next bootloop. I uninstalled an app, rearranged icon placement, and changed the wallpaper. Once it shutdown and booted back up again, everything was back to the way it was before the changes had been made. The app I had uninstalled was still there, the wallpaper reverted back, and the icons were back in their original location. At this point I decided to see if I could reboot into Safe Mode. Unfortunately, this doesn't work. I am able to get the reboot to Safe Mode confirmation box and tap "Ok" but it remains in Normal mode when it boots back up. I eventually tried to boot into recovery and preform a Factory Reset. I was able to get into recovery and reset the Nexus. Or so I thought. Instead of seeing a Device Setup screen after it wiped, like I assumed I would, it booted up and still had all the data on it. There were no errors during the wipe and it was confirmed with "Data wipe complete." afterwards.
I am absolutely lost. I've never dealt with such an unusual issue before. Especially with it not even reacting to a complete data wipe. So, just to recap . . . I only have 30s - 1min available to interact with the OS before it reboots itself, any changes made during that time don't stick, Device is successful booting into Stock Recovery, and I can successfully get a Fastboot connection when booting to the Bootloader.
Luckily she has come to terms that this might not get fixed and has decided to go a head an order a newer 2013 model. I'd still like to try any solutions that you all might have. Just in case there is a slight glimmer of hope.
Oh, and one last thing I should mention. I tried to see if I could get the bootloader unlocked but it didn't work. This is the first Nexus I've ever had in my possesion, so I'm not really familiar with the tools available for it. I found WugFresh's Root Toolkit and attempted to Unlock with it. The process seemed to go as it should and I didn't receive any errors on the tablet or in the software. However, in the end, it didn't make any changes to the bootloader.
same problem
I have the same problem as you.
Did you find a solution?
Can anybody help us?
Thanks.
I have a similar problem, but I think mine is related to the bootloader.
I'm stuck on 3.34 and that's where it fails ever time I try Wug's Nexus Tool Kit.
Have you tried Nexus Tool Kit yet?
eawooten said:
I have a similar problem, but I think mine is related to the bootloader.
I'm stuck on 3.34 and that's where it fails ever time I try Wug's Nexus Tool Kit.
Have you tried Nexus Tool Kit yet?
Click to expand...
Click to collapse
I have tried factory reset from recovery, no errors while wiping but when device restarts nothing has happened: I only have a 30s-1min of old system with all my data and apps or directly bootloop.
Also I have tried flash factory images with Nexus Tool Kit and directly from bootloader. No errors while flashing, apparently has flashed new image system. When device restarts nothing has happened: bootloop or my old system with data and apps for 30s before restart.
Myself and a few others are having the same problem... please keep us updated if you find anything out.
http://forum.xda-developers.com/showthread.php?t=2588911
Galaxy S4 I9505
Phone was second hand to me at the start of this year, though had been well looked after, always in a case etc
I flashed it with the newest stock ROM in January this year
I9505XXUHOJ2_I9505BTUHOJ1_I9505XXUHOJ2
& rooted with CF AutoRoot
It has worked fine until about 2 weeks ago, when it randomly shut down. After restarting, it kept bootlooping.
Left it off & charging overnight, & the next morning it booted ok. Managed to use spotify for a few hours.
Then it started bootlooping again, sometimes getting all the way but then crashing after a few minutes.
Managed to boot into recovery & do a 'wipe cache', that didnt fix it.
'Wipe data' didnt fix it
Have flashed the PIT file & ROM (via odin), no errors in odin, done it twice now
wiped cache & data
still wont boot past the white splash screen, only sometimes boots into recovery
(also, only the menu button lights up, not the back button.)
I've checked the power button (clicks & dosnt stick)
Dont think the batteries the issue (charges fine, dosnt get warm, isnt bulging)
What else could stop it booting?
Have you tried booting into safe mode?
Safe mode, from what I read, can be accessed by holding the menu button while the phone boots.
But you should also do some reading about it, in case I'm wrong.
The other idea would be to try a custom ROM.
GDReaper said:
Have you tried booting into safe mode?
Safe mode, from what I read, can be accessed by holding the menu button while the phone boots.
But you should also do some reading about it, in case I'm wrong.
The other idea would be to try a custom ROM.
Click to expand...
Click to collapse
Can't boot into safe mode
(& having read up on it, it would only not run apps that arn't already in the ROM)
Any suggestions for a custom ROM
& why would it work when the original official one won't?
Well, it's booted far enough to get into android & add a google account, then it bootloops again.
Then after leaving it off for a while, it will boot & let me look at settings etc, then bootloop
however
the menu soft key stays lit all the time after a boot
the top half of the phone, around the camera, gets very warm
Does that indicate it's a hardware issue?
Could it be the battery?
If it's the top half warming up without you doing anything, it's the motherboard.
Boot into recovery and and let it stand by, see if it reboots.
xedge said:
Well, it's booted far enough to get into android & add a google account, then it bootloops again.
Then after leaving it off for a while, it will boot & let me look at settings etc, then bootloop
however
the menu soft key stays lit all the time after a boot
the top half of the phone, around the camera, gets very warm
Does that indicate it's a hardware issue?
Could it be the battery?
Click to expand...
Click to collapse
The battery can't prevent the ROM from booting. It would have to turn off during the boot, which it doesn't. So, by my logic, it isn't the battery.
Try official CM.
GDReaper said:
The battery can't prevent the ROM from booting. It would have to turn off during the boot, which it doesn't. So, by my logic, it isn't the battery.
Try official CM.
Click to expand...
Click to collapse
Hello Reaper, I have exactly same problem. Please help. In my case leds are working fine, rest is exactly the same problem. And It all happened suddenly on its stock rom. I never rooted my phone before.
kingpin090 said:
Hello Reaper, I have exactly same problem. Please help. In my case leds are working fine, rest is exactly the same problem. And It all happened suddenly on its stock rom. I never rooted my phone before.
Click to expand...
Click to collapse
Try this.
GDReaper said:
Try this.
Click to expand...
Click to collapse
I am not able to go into recovery after firmware flash. The recovery bot appears and when the blue loading bar goes to half, the phone reboots and then again boot loop. I just noticed this always happened when i flashed a rom. I was never able to enter recovery on first boot.
kingpin090 said:
I am not able to go into recovery after firmware flash. The recovery bot appears and when the blue loading bar goes to half, the phone reboots and then again boot loop. I just noticed this always happened when i flashed a rom. I was never able to enter recovery on first boot.
Click to expand...
Click to collapse
Does phone go into download mode ?
gosha98_ said:
Does phone go into download mode ?
Click to expand...
Click to collapse
Yes it goes normally into download mode. Firmware always flashed without any error. But i noticed I can't enter recovery on first boot to do factory wipe.
Sent from my GT-I9300 using XDA-Developers mobile app
kingpin090 said:
Yes it goes normally into download mode. Firmware always flashed without any error. But i noticed I can't enter recovery on first boot to do factory wipe.
Click to expand...
Click to collapse
Why do you want to do factory wipe after one boot?
Its the only thing i didn't tried till now, my phone crashes and reboots everytime during boot.
Sent from my GT-I9300 using XDA-Developers mobile app
To start off, I have been running the pure nexus rom on marshmellow 6.0.1, and twrp 3.0.2-0 for months now, and loving my mxp. Today, my phone randomly froze (which happens often, due to me maxing out my ram with too many things running), no big deal right? We'll just hold the power button to hard reboot phone like normal Wrong. My phone now does not boot at all. I cannot get passed the "warning bootloader unlocked" screen. I cannot boot into twrp either, as it freezes at the teamwin start up screen (so unable to flash via recovery). None of my 3 computers recognize my phone as being plugged in (so unable to use adb/fastboot to flash), and fastboot flash mode is "Secure". Have I bricked my phone? I have not made any changes to it in months (aka I haven't flashed ANYTHING to my mxp in months, hence why I am so dumbfounded). I am willing to go back to stock (preferably keeping twrp) if need be. Any help is appreciated. Thanks
Have you tried a simple wipe? Open TWRP and go to Wipes, Advanced, and select caches and user data (NOT system or boot) and reboot... if not, you need to reflash your ROM.
And BTW, "Today, my phone randomly froze (which happens often, due to me maxing out my ram with too many things running), no big deal right?" Yes, actually that is a big deal... it is not normal and shouldn't be happening, you should have been troubleshooting that issue. Android usually doesn't just "max out RAM" and freeze up unless something is wrong.
A couple of days ago. I wanted to check my phone in the morning and it started boot looping when I pressed the power button. Then, after a couple of boots it went into the TWRP recovery. I wiped cache/dalvik in hopes of a quick fix but still boots into recovery.
I can also go into the bootloader but the bootloader is completely unresponsive. It just gets stuck on the "barcodes" option, the volume keys do nothing and adb doesn't see my device when it's in the bootloader. I also tried re-flashing the same ROM I'm using(within recovery) to no avail.
I still intended on using this thing for a couple more years (I have a couple of spare OEM batteries and a spare chasis). Really appreciate any help.
Recovery.log from TWRP
Any flash drive can become corrupted.
Boot loops are commonly caused by poorly coded apps like launchers and power management apps.
Rootkits are always suspect with abnormal boot ups and unstable operation when no other cause can be found.
On a stock Android a factory reset or in extreme cases a firmware reflash will resolve it unless it's a hardware failure which is rare*. Be careful what you flash, install and download... always.
*a drop, water exposure or a ESD event when repairing a phone can cause this... sometimes not immediately.
blackhawk said:
On a stock Android a factory reset or in extreme cases a firmware reflash will resolve it unless it's a hardware failure which is rare*. Be careful what you flash, install and download... always.
Click to expand...
Click to collapse
Can I reflash firmware without the download mode working properly?
Sorry, way beyond my skillset...