My tablet recently began entering a locked blue screen state devoid of text or icon. It holds there for one to three seconds and then reboots.
Prior to the start of this rebooting sequence trend I downloaded and installed the stock ROM listed on my signature, hoping that it would alleviate some issues with delay in screen tap response, some occasional heating during gaming along with what I perceived to be a little bit of driver related lag.
I haven't figured out when, why, or how it decides to reboot. But as far as I can tell it seems to be related to [behind the scenes machinery of] Google Play (GP). I suspect this because it has happened when I've launched GP or GP tried to do some updates or software installation.
Incidentally, though possibly unrelated, when I try to add an account via settings, at the sign in page, the device returns unable to sign-in message citing connectivity issues. I am in China, so I suspect this could all be related. To get around this issue, I log into a VPN service. This allows me to sign in and add the account to the device. However, in order to play any games, I must log off the VPN. But once the account has been added to the device, it more-or-less is able to access some of the Google services (at least the ones not outright blocked -such as drive and YouTube).
In my troubleshooting attempts, I have thus far done a cache wipe and factory reset from the boot menu. All to no avail.
At this point I need to live in constant fear of a sudden reboot, for I know not when it will strike next.
I would appreciate some suggestions on either what the issue might be, how to determine the cause, or how to solve it.
Thanks
Funny story...
So Kitkat has been released, for the TGY country code.. Yay!
P605ZSUCNE3_P605OZSCNE3_P605ZSUCNE1_HOME.tar
Is the md5 file to be put into the AP slot of Odin 3.09, for my tablet.
I was excited thinking this would address the issue.
Prior to flashing the ROM I factory reset from within the settings, then I went into the recovery boot menu and there I wiped the cache and did a factory reset once more.
Then I proceeded to setup and sign into my Google account, after flashing the ROM.
Naturally the tablet went ahead and started downloading and installing apps and updates from Google Play.
I was happy to see that it was progressing along swimmingly.
The screen dimmed down and then shutdown after period of inactivity (while downloading and installing apps in the background).
Occasionally, I'd click the home button to see tat everything was going as it ought.
I then noticed the screen turned black somewhat suddenly, without dimming first.
I thought little of it.But I went to check by pressing the home button... I figured maybe there's a little lag or the tablet is too busy installing, so I clicked the power button. Nothing; no response.
The tablet is deader than dead.
Now I don't know what to do.
After waiting a while, under the advisement of another user who apparently has also been having issues with his note 10.1 2014, I decided to try to long press the power button. The tablet came back on, and resumed downloading and updating from Google.
But now the tablet is going into this sudden blank blue screen and most of the time rebooting on its own (occasionally it needs a little help, by the pressing and holding of the power button to induce the reboot) ever so randomly. I have found absolutely nor rhyme nor reason for when or how it decides it's going to reboot itself. It tends to happen often if/when I launch some apps that require logging into Google services; but at times it happens without provocation -at all.
Recently it's been boot-looping -without the launching of any app... just from turning on, sitting idle, and then rebooting. But I'm no closer to figuring out how to consistently induce the reboot, either.
My tablet has never been rooted (and for obvious reasons, never will be), no custom ROM, no ROM from another region. Nothing that would give Samsung the excuse to void my warranty (not that it's worth much, here in China).
And yet, it still reboots at random intervals for no immediately apparent reason.
In any event, if anyone has any ideas on how to proceed, any suggestions on what to do with this POS, I'm open to suggestions.
I'm interested in general ideas such as take it to the Samsung shop (something I'm loathe to do because Samsung has terrible service -especially in China- and at best I'm looking at a month or something like that before I get it back), so some ideas on how to discover when/why/how this rebooting sequence is being triggered -and maybe troubleshoot it is slightly preferable.
Related
This is probably nothing but today I got a bigger flash drive so I cloned it and put it on aftv. I installed some cloud games (purpose of getting more space) then moved them to USB. I reboot because I find the availability size of the drives don't change unless you do. When the aftv booted normally I ever so briefly saw "installing new software" message appear. This only happens to me when installing a new ROM or when wiping data/clear cache etc.
The message was on screen like 3 seconds. I would've missed it if I weren't looking then everything was fine. Its not possible I had updates enabled because I'm meticulous about disabling them EVERYTIME I do anything, especially if I boot to recovery (which I didn't this time) needless to say I disabled them again to be safe.
Any theories on why this happened? I'm not nearly as concerned as I am curious. I mess around with this a lot but this is the first time I've seen the updating notification without there being a reason I could identify...thanks.
Happened again. I wasn't even trying to reproduce the above, just needed a reboot. This aftv is identical to my other in every way except this is wired and I use a powered hub.
KLit75 said:
Happened again. I wasn't even trying to reproduce the above, just needed a reboot. This aftv is identical to my other in every way except this is wired and I use a powered hub.
Click to expand...
Click to collapse
You could ignore it or you could try doing a factory reset.
rbox said:
You could ignore it or you could try doing a factory reset.
Click to expand...
Click to collapse
If you think its not a concern, I'm comfortable with it. I factory reset every couple of months anyway so I'll get to it eventually. Thanks.
I am not rooted and it has happened to me twice in the past two hours. Within minutes of opening SPMC both time, a message appears telling me I have software updates the first time I hit the home button and it went away so I went to check for updates and it said I had none. The second time I clicked to install, but nothing happened. I have rebooted and still nothing. Not sure whats causing it, but its clear that there is not really an update. am guessin its a bug. Gonna open SPMC and see it it happens again.
Hi all, read many threads here and finally posting.
I have an xperia M (C1905 I think)
Short story:
As soon as I turn on this device within a few seconds I get the "Unfortunately, xxxx has stopped". I hit okay and within a second something else is stopped. This is repeated constantly for as long as I could tolerate waiting for. The odd occasion I have managed to get maybe 5 seconds between app crashing to navigate into the settings to try something out or check the album.
I am asking for help on what to do in order to access the files on the device. I really really want to save the images. I since has moved on to a Z and now a Z3 but at this moment I want to get the images. (Factory reset is thus out of the question). I rather leave the phone intact for years to pass until some technology makes it possible to retrieve the files.
Longer story:
I think this issue started occurring after an android update - which leads me to my conspiracy at the end of the post. Basically after an update I started noticing random apps being stopped/crashing without warning. Apps that weren't even being used. This happened maybe once a week, then a couple times a week. Seemed pretty random at first. Thus why I never took a moment to see the exponential trend and act fast to back up data. Over the course of a month probably, this just got worse to the point where an app of some sort is constantly crashing. It could be facebook, then gmail, then google, then a service, then homescreen blah blah anything and everything is crashing just so it can fill the screen. Multiple at a time. I hit ok and another appears or 5 more appear. Then I might get a glorious 4/5 seconds to browse the contents of the phone then boom another batch of crashes. The phone is completely useless right now, no way to navigate. Also, even with the phone turned on in safe mode or not, I cannot access the files whilst connected to my computer. The charging indicator shows up, computer recognises the device but on the odd occasion it does show up in "my computer" the folder does not open and the file explorer/documents just crashes. Xperia companion doesn't work either.
There was also an issue with charging/transferring media with the charge port. Bad connections but it was made better using the Sony original cable I have now. It charges alright now (instead of needing "the right" angle). Still, as far as I can remember data was hard to trasnfer, maybe I got 10 songs copied over before it stopped responding and had to cancel. All the files on the SD card I saved of course but the ones on internal storage are still there. I browsed the album for a few seconds and I just want to get them on my pc. I tried to copy to SD card but I can't perform that with the constant bombarding of crashing app error notifications that fill the screen. Also it seems like once the phone is on, I can navigate around (with the bombardment of crashing) but once the screen is allowed to time out it doesn't wake back with the power button. To mess with it again I have to pull the battery and put it back in. I have booted in safe mode to no avail, apps still keep crashing.
Please please help. I have USB debugging enabled if that helps? I just want to drag and drop my images and then the phone can sit in a draw. I am sure a factory reset would have it working back to normal but I can't lose the files.
Btw I think SONY is purposefully killing off these older devices. The phone worked flawlessly, yes it's older and not as fast but there was not a single issue (besides maybe the charge port wear). This issue with crashing is completely software related after an android update.
The phone is not rooted and no random software was installed (just social media and the like).
THANK you for any help!
Brad
Hey which rom are you using? do you have unlock your bootloader? if you are using stock rom and not unlock your phone bootloader then it can be resolve by using a software repair using sony pc companion.
Hello,
This is what have happened:
I was browsing via Chrome, when phone froze. Well, no big deal. It went black, and I couldn't power it back on. I was on rehersal, so I left it on the table for an hour.
Came back to it, tried to power it on, and after 20sec or so of holding Power button, Google appeared. And it disapeared again.
And that is it.
I can access bootloader, and recovery.
From there I tried to flash fresh img, but my device is locked. Went the other way. I downloaded latest OTA and went to adb sideload, and it downloaded it all to phone, but same thing with booting. It stops.
Sometimes it even goes to those circle animations on booting, but than it freezes again, and turns off.
Any hope for my 2 years friend now
Thanks.
@Nuuq: by searching for 'brick' 'bootloop' you find for example this thread Hope, it helps.
Exact same thing happened to me this morning. I was playing Clash Royale, and it froze. Rebooted, and it just went to Google screen and nothing else. I let it sit for an hour, and it started to boot, but froze mid-boot-animation. I can get into bootloader and recovery, so I'm going to flash the Bootloop fix this afternoon and see if it fixes it.
Odd......
I thought this was a CPU bootloop issue, so I flashed the 4-core TWRP, wiped everything, and installed the stock OPR4.170623.006 system, vendor, and thne 4-core boot.img I found in the bootloop thread. I got a little farther, say 5 minutes instead of 5 seconds, but it was still crashing and bootlooping! I couldn't activate the phone, cuz it was rebooting while waiting for my 2-factor authentication text, and when I tried wiping it again, it was rebooting while in TWRP while re-flashing the system. The more I try to fix it, the worse it gets...
I may just give up on the phone, and contact Project Fi support to see if they'll give me a new one.
Same here guys...put inside the the fridge for about an hour and it started, just in time to save my photos on Google photo...but as soon as I start to use it, it freeze, turn off, no reboot. If I reboot, it freezes on circles Google animation...i can enter in bootloader and recovery too...any suggestion?
Same problem - merrily browsing -> crashed and now bootlooping - can get to the bootloader menu but can't get into recovery mode
Running Oreo 8.0
I flashed the 4-core TWRP, and it was crashing even in that. Last night, it sat for 3 hours on the activation page, and never froze, but anytime I try to use it, it freezes. It sometimes turns on, but most of the time it just crashes while booting.
I already use Google Photos, and my texts are synced through Fi hangouts, so I'm not worried about losing anything. I've wiped my phone and started over maybe a dozen times over the past year. Different ROMs, kernels, etc. I just want a working device.
I called Google, and they said nope. They want me to call LG, but my brother has had 2 bootlooping 5x, and LG didn't help with either of his. I doubt LG will help me here, cuz I bought it from the Google Store. I think I have 3 options:
1) pay to gave the CPU reflowed. If I went this route, I would want to upgrade to 3GB or 4GB of RAM at the same time. If I do this, I still have to deal with my battery only holding a 70% of it's charge, and not wanting to spend $50 on a 2 year old OEM batter.
2) Upgrade to a used Pixel. I'm sure with the Pixel 2 coming out, lots of people are going to be upgrading, and I'm sure there will be a bunch of used Pixels showing up. But, you're still buying a used phone that's been out for a year now...
3) Upgrade to the Android One Moto X4. The word "upgrade' is used loosely, as it's VERY similar to our 5Xs. Similar benchmarks, similar screens, similar primary cameras, almost the exact same dimensions, etc. It would be an upgrade with 3GB RAM, bigger storage, SD card slot, 2nd rear camera, better GPS, bigger battery, new (not used), and a few other minor tweaks. Con is that it's so new, there are no ROM/kernels for it yet
I think I just talked myself into a X4 while writing this. We'll see what the wife says.
it happen for me but me i can boot to bootloder but the phone become very slow i just escape from bootloop i turn it on and after 2 week he bootloop again now only fastboot no recovery and no system how i do
squelch41 said:
Same problem - merrily browsing -> crashed and now bootlooping - can get to the bootloader menu but can't get into recovery mode
Running Oreo 8.0
Click to expand...
Click to collapse
Hmm, putting it in the freezer gets it to boot but rapidly crashes again - looks like it is the hardware rather than software
I've been having an issue since at least January. I was hoping either the Feb or March update would fix it, but it hasn't. My Pixel 2 XL has been acting strangely, but only when driving. When I drive, the device will either soft boot (states that PIN is required after restart, but opening terminal and checking uptime shows it hasn't physically booted) or soft lock (black screen that won't come on until hard booted). When it happens, my music will stop and my car's screen will go black. After a period of time, it'll ask me to reconnect the phone, either due to the device being encrypted until the PIN is entered after the soft boot or because it's simple no longer responding in the case of a soft lock. I've tried:
Removing the bluetooth connection for the car
Removing all known cars from Android Auto
Clearing cache
Uninstalling a few driving-specific apps
I was hoping maybe someone had an idea of anything to try besides a factory reset. I really hate reconfiguring my device from scratch (or even from TiBu backups).
I ended up trying multiple different kernels (Elixir and Evira) with the same results, so I broke down and did a factory reset. I reloaded apps and data from Titanium Backup. I'm no longer having the soft boot issue, but a different one instead. Now, randomly, my phone seems to disconnect from Bluetooth, audio it was playing plays through the phone speaker, and my car's display blanks out. I noticed my watch also shows that it has been disconnected from my phone. After a few moments, Android Auto returns to my car's display, but upon selecting anything (for instance, the music I had been listening to), it shows that the device is not compatible.
If I check the phone at this point, every app that had been running has been stopped. My notification bar is empty, and it usually has a few permanent notifications. The phone hasn't hard or soft booted, as it doesn't request the "PIN after restart". It just killed literally everything that was running. I have set both Android Auto and my music apps to not be battery optimized, as I assumed that might have been a problem, but with no better results. If I unplug and plug back in the USB cable, the phone operates normally. I haven't had any especially long trips to see if the issue occurs a second time. I'm lucky enough that my trips to work take 8-10 minutes.
Has anyone seen this or have any suggestions on things to try?
Well, your first post sounds a little similar to this thread: https://forum.xda-developers.com/pixel-2-xl/help/alert-using-adguard-private-dns-causes-t3896243 , Having tried dns.adguard.com private dns on my phone, that setting also survivied a factory reset. No idea about the second post. Shot in the dark.
cliff6056 said:
Well, your first post sounds a little similar to this thread: https://forum.xda-developers.com/pixel-2-xl/help/alert-using-adguard-private-dns-causes-t3896243 , Having tried dns.adguard.com private dns on my phone, that setting also survivied a factory reset. No idea about the second post. Shot in the dark.
Click to expand...
Click to collapse
It was similar, but I wasn't using Adguard. I had been using 1.1.1.1 for DNS, but when I stumbled on that post, I removed custom DNS settings without success. Thanks for the thought, though!
In all my years with Android, I haven't had such an infuriating issue. It's almost enough to make someone go to *gasp* iPhone! ... Not really.
For what it's worth, while you mention bluetooth audio and your watch disconnecting, of which I don't use either, I did have somewhat similar issues with Android Auto which it sounds like you also used as you mentioned plugging in. Sometimes AA was disconnecting, sometimes the phone not being recognised when plugged in. It's been a year so can't remember all the symptoms, but at the end of the day, it was the charging port that was malfunctioning, and which Google nicely replaced for me. This also caused adb and fastboot to be intermittent, and not see "devices" which also confirmed the charging/data port. Again, just another shot in the dark for you to consider.
Well, I went on vacation a few hundred miles away last week. On the way up, the phone freaked out repeatedly. I had my wife try to disable WiFi. Same issue. I had her try to disable Bluetooth. Same issue. Both disabled. Same issue. While at our resort, the phone freaked out a few times on the drive to breakfast (literally a 2 minute drive).
On the way back, I decided to disable Location services and revoke all Location permissions. I drove 50 miles with no problems. I had my wife enable Location and drove 30 miles. No problem. I had her tick on apps that I felt needed Location permission, one by one, every 10 miles. No problems at all. I ended up with all of the apps that I feel need Location turned on and haven't had a problem since. So something was choking on Location data, but unfortunately, I have no idea what app it was. I think it might have been Action Services, but I can't be sure. I'm just glad it's fixed, frankly.
I know this is an older post, but I wanted to get my "fix" posted, just in case someone else runs across a similar issue. At least they'd have something to try.
I've been running the latest update on the d2q Note 10 welcome it's a n975u1, and I've been running ice box as my device owner as well as revenant and also use a box to keep my apps under control, very conscientiously I must add.
Ever since the last update was ready to be installed I was trying to put it off because I was hoping to get off on one of those new routing techniques that keep telling me that I can't update my system Os or I won't be able to get it done, so I kept putting it off, but with each day my system kept getting more and more strained and suddenly just begin going into a straight boot loop going from the startup screen with the Android name printed across the screen and then saying it was booted and has been reset and then immediately going straight back to that Opening screen with the Android logo on it and repeatedly doing it until I catch it at the right time to Power It Off. My question is is there any way that I am going to be able to get around having to do a factory reset on this device or does anybody have any other suggestions that may circumvent this tedious measure at this point? I've been routinely wiping system cache, make sure I got all my backups ready to go during the periods of time that it doesn't go into bootloop,(which seems to be usually once a day for a few hours it will operate just perfectly until just suddenly shuts off with no warning signs). I was also able to get onto the Verizon update app via ADB download mode and they ran a scan on it and determined that they could fix my device if I were to leave it plugged in and allow them to do it. Theresa in the process of the repair that they said needs to be done. They didn't say what this repair would consist of, so I have no idea what is the real issue here. I've been trying to get as many system debugging reports as I can pick up along the way from various apps that record crashes and such but not sure really how to process that information to be able to determine what exactly the issue is. I'm at my wit's end and just about to point to just go for it the factory reset as much as I hate to do that! I think that I have Extreme Complex post-traumatic factory reset disorder and would do just about anything to avoid having to go through this again! If anybody has any advice I would very much appreciate it and I hope I'm posting in the right for him because all these Note 10 forms get kind of confusing when you got all the various processors and countries and all the other factors that you have to where to figure out where you're supposed to be asking a question here! LOL sorry, thanks!
Power management apps and launchers can boot loop you fast... so I learned
I get good run times with no power management on my stock N10+, but it's heavily optimized and I am using a package disabler.
To fix it you'll need to edit the offending apk(s) out of the boot sequence. I haven't a clue how to do that. The power management app is the most likely suspect though.