Related
Hi.
My Galaxy S3 is frequently getting into hotboot looping state for no apparent reason. The only way to get it out of this state is to wipe the phone or restore a backup of the "data" folder only.
After that, it might work for a week, but it might not work for a day (not work = start to hotboot loop).
It happens when after the phone screen is locked, it doesn't wake up anymore. It doesn't answers to any calls (like if it's off) or notifications. Just dies.
Forcing a reboot (by holding the power button) or removing the battery ables me to reboot it, but enter in hotboot looping state. I can make it go thru the whole booting state and I see the homescreen (And that's weird because I'm supposed to see the lockscreen first). Some widgets animation works but the device doesn't answer to touch (two softbuttons vibrates when touched, they do vibrate but don't render anything on Android) and then hotboots. Keeps doing this forever. Booting into safemode USED to work, but it doesn't work anymore, I don't know why.
After wiping the device or restoring the Data backup, device turns on as expected (restoring data takes it back to working state exactly like it was before the backup, even the same lockscreen pattern). I've tried to leave a terminal running logcat to catch the error, but it doesn't write in realtime, so when the bug breaks out, the logfile is empty.
I even thought it could be the S3 memory issue with firmware, but I'm using the "fixed" kernels. Also, it is recoverable, and not permanently dead.
I suspect of some rogue app, but I have too many apps to just go through installing one by one (and waiting even weeks to install the other one). Is there any way I can get a postmortem logfile or make logcat write in realtime?
Thanks
GTMoraes said:
Hi.
My Galaxy S3 is frequently getting into hotboot looping state for no apparent reason. The only way to get it out of this state is to wipe the phone or restore a backup of the "data" folder only.
After that, it might work for a week, but it might not work for a day (not work = start to hotboot loop).
It happens when after the phone screen is locked, it doesn't wake up anymore. It doesn't answers to any calls (like if it's off) or notifications. Just dies.
Forcing a reboot (by holding the power button) or removing the battery ables me to reboot it, but enter in hotboot looping state. I can make it go thru the whole booting state and I see the homescreen (And that's weird because I'm supposed to see the lockscreen first). Some widgets animation works but the device doesn't answer to touch (two softbuttons vibrates when touched, they do vibrate but don't render anything on Android) and then hotboots. Keeps doing this forever. Booting into safemode USED to work, but it doesn't work anymore, I don't know why.
After wiping the device or restoring the Data backup, device turns on as expected (restoring data takes it back to working state exactly like it was before the backup, even the same lockscreen pattern). I've tried to leave a terminal running logcat to catch the error, but it doesn't write in realtime, so when the bug breaks out, the logfile is empty.
I even thought it could be the S3 memory issue with firmware, but I'm using the "fixed" kernels. Also, it is recoverable, and not permanently dead.
I suspect of some rogue app, but I have too many apps to just go through installing one by one (and waiting even weeks to install the other one). Is there any way I can get a postmortem logfile or make logcat write in realtime?
Thanks
Click to expand...
Click to collapse
Try flashing another ROM for S3 and doing a full wipe.
TenKoX said:
Try flashing another ROM for S3 and doing a full wipe.
Click to expand...
Click to collapse
Thanks for the reply.
I already did. It started to happen out of nowhere while I used the Android Revolution HD ROM, then after a few wipes and reinstalls with the same problem, I gave a shot to WanamLite ROM. Exactly same problem. Both are based on the original 4.1.2 Android.
I'm pretty sure it is being caused by some rogue app, because the only thing in common between those ROMs is that I "batch-install" all my apps back from Google Play.
So far, I'm suspecting about Vine (it's the last install that I remember since it started to have this issue) and I have already uninstalled it, but it might have been caused by some app update that broke hell to my phone.
If there were some kind of "black box" that I could retrieve after a crash, it could be the solution
GTMoraes said:
Thanks for the reply.
I already did. It started to happen out of nowhere while I used the Android Revolution HD ROM, then after a few wipes and reinstalls with the same problem, I gave a shot to WanamLite ROM. Exactly same problem. Both are based on the original 4.1.2 Android.
I'm pretty sure it is being caused by some rogue app, because the only thing in common between those ROMs is that I "batch-install" all my apps back from Google Play.
So far, I'm suspecting about Vine (it's the last install that I remember since it started to have this issue) and I have already uninstalled it, but it might have been caused by some app update that broke hell to my phone.
If there were some kind of "black box" that I could retrieve after a crash, it could be the solution
Click to expand...
Click to collapse
If you wipe data, your apps disappear, so I think this is not the problem.
Do another full wipe and DON'T restore your data. Just download again from Google Play and see if the problem appear again.
TenKoX said:
If you wipe data, your apps disappear, so I think this is not the problem.
Do another full wipe and DON'T restore your data. Just download again from Google Play and see if the problem appear again.
Click to expand...
Click to collapse
Thanks for the reply.
I started doing this the first time, but it still crashes it. And as I was wasting too much time with this, the backup option came as a option to not have to click to download over 200 apps one by one. Also, it once happened during a long holiday, and I was in a friend's ranch with no decent internet connection for downloading. All my apps were gone and I was stuck with a default phone for five days.
The backup is exactly the point where I finish downloading all the apps and they're installed. There are no cracked programs or adapted (e.g. Nexus camera). Every single app is obtainable from Play Store, so it's pretty fresh
Funny (actually sad) thing is that it's a system-wide error that a wipe solves it. If I don't wipe data and reinstall the same ROM (which under normal condition is no big deal), it doesn't get past from boot screen.
The worst is it happens instantly. It's working now, but then it crashes. Bam, gone. Few hours ago I was texting my gf and I left the phone for a while, waiting for her answer. After some time I knew something was off, picked up the phone and it was pretty warm (first signal), with the LED blinking some Facebook notification. Tried to wake up but it is in coma. I force a restart and it hotboot loops like I described on first post
It -only- happens when screen is locked. I disabled the screen lock for now to see if it's a workaround, but I'm not holding my breath
It could be a hardware malfunction if it can carry through all the roms you flashed and even when you tried a fresh install without your apps it still happened.
WildfireDEV said:
It could be a hardware malfunction if it can carry through all the roms you flashed and even when you tried a fresh install without your apps it still happened.
Click to expand...
Click to collapse
That's pretty much discarded. Wiping data instantly solves it. It did indeed run for 5 days with no external app without a single problem.
But also it ran over one week with external apps without a problem. I've executed some memory integrity tests and they all reported a-OK.
I'm kinda ruling out the "rogue-app" issue. I thought that recovering "data" from NAND backup was the /sdcard/android/data. But it's deeper than that. Now I don't even have a lead.
Phone already crashed today, without Vine and lockscreen, so that's not the problem. I really need to get some logs out of him. Just need to know how. Only if it could write a realtime log, so I could pull through ADB.
My last resort will be a fresh-fresh android installation, default S3 i9300 ROM, with only essential apps. Already have it triggered for the next crash.
If it goes rogue even this way, I'm running triangleaway and returning it (will be a profit too, the silver border is stripping).
This time around, I'm trying running it without a external sdcard (several files were being corrupted in it, don't know if it's due to force restart by removing battery, or some real issue on the card)
It's a problem within the Facebook social app or Youtube.
I've managed to run the phone flawlessly for weeks without signing in on Facebook, suspecting it might be it.
Today I logged in on Youtube app accidentally, and had to login on Facebook app to retrieve some info. Three hours later, phone went mad again.
I don't know which app caused it, but I think there's some relation to Facebook due to a greater ~involvement~ (couldn't find a proper word.. forgot it) with Android.
I've changed ROMs, launchers, system versions.. but not Kernel. I'll try another kernel and report on Boeffla main thread to see if there's some known bug
So I have been using Omega v12 (23/09/2013) on my Galaxy S4 i9505 for a week or so absolutely no problems what so ever.
Then last night my phone just ran out of battery and safely shut down when I plugged it in and turned it on everything seemed fine until it got to the lock screen it was quite unresponsive and once i unlocked it the screen was black but showing the notification bar and it keeps bringing up a dialog box saying gmail has stopped working which once you press it it reboots. one time it said system UI has stopped working.
I can pull down the notification bar but i cannot do anything in there if you try to get to settings or for example turn bluetooth off it reboots. i was able to get the multitask menu up once where i could access google search and it allowed me to browse the web it even opened chrome but as soon as i closed it it rebooted again.
I really don't want to wipe data, keep that as my last option.
I have not seen anyone else with a similar problem i have seen a few people have 'system ui' crashes but they seem unrelated.
They were talking about installing something called '3Minit Framework'. I have no idea about this or what it does and i don't know how i would get it onto my phone, I have not tried to see if i can plug it into the computer and copy data i might try that when i get home from work...
On a different thread it was suggested to just reinstall from zip without wiping data. It didn't work.
I would like to maybe try flashing a different kernel but I don't know if right at this stage its safe to do so or even if it will make any difference?
If yes, what kernel would you guys suggest???
Any assistance would be much appreciated!
inthestarrysky said:
So I have been using Omega v12 (23/09/2013) on my Galaxy S4 i9505 for a week or so absolutely no problems what so ever.
Then last night my phone just ran out of battery and safely shut down when I plugged it in and turned it on everything seemed fine until it got to the lock screen it was quite unresponsive and once i unlocked it the screen was black but showing the notification bar and it keeps bringing up a dialog box saying gmail has stopped working which once you press it it reboots. one time it said system UI has stopped working.
I can pull down the notification bar but i cannot do anything in there if you try to get to settings or for example turn bluetooth off it reboots. i was able to get the multitask menu up once where i could access google search and it allowed me to browse the web it even opened chrome but as soon as i closed it it rebooted again.
I really don't want to wipe data, keep that as my last option.
I have not seen anyone else with a similar problem i have seen a few people have 'system ui' crashes but they seem unrelated.
They were talking about installing something called '3Minit Framework'. I have no idea about this or what it does and i don't know how i would get it onto my phone, I have not tried to see if i can plug it into the computer and copy data i might try that when i get home from work...
On a different thread it was suggested to just reinstall from zip without wiping data. It didn't work.
I would like to maybe try flashing a different kernel but I don't know if right at this stage its safe to do so or even if it will make any difference?
If yes, what kernel would you guys suggest???
Any assistance would be much appreciated!
Click to expand...
Click to collapse
try wiping dalvik cache and cache
for kernels you should try yourself
I posted this in the A500 forum as well, but it's probable that this is not a problem limited to my device, and it's also possible that there is a rom that might help me out.
I purchased my tablet on the day it came out, so it's long out of warranty. Everything has been fine with it until three nights ago.
I woke up in the morning to a crashed app alert. I don't get crashed apps often, but it does happen, so I hit ok. A few seconds later I was inundated with crashed app alerts. At that point, any app I opened would also crash immediately. Figuring a good reset would fix it, I turned it off...and it wouldn't turn back on.
I did finally get it to start by holding the volume up and power button.
But that didn't fix the problem. I've discovered that it is somewhat stable if I keep wifi off, but if wifi is on, within minutes everything starts to crash again.
I tried uninstalling some of the apps that crash, but when I restart, the apps are back. It doesn't matter what I uninstall, when I restart, it's back. Installed apps also disappear, the wallpaper resets...basically nothing I do sticks once I restart. I tried to factory reset using the button combination required for my device, and the screen gives the "erasing user data" message, but when it loads up, everything is just as I left it. I tried using the android os option to factory reset, but when I hit "erase everything", the button depresses, but nothing happens.
So obviously, I'm a bit perplexed.
I've never rooted it, and I ran an anti-virus scan a few hours before this all happened and it came up clean.
Anyone ever experienced this? Any advice? If no one has any ideas one how to fix it, is there a way to bypass the main os completely with a rom? I have absolutely no idea how those work, so it may be obvious that it won't, but I figured I'd check.
Thanks in advance! And thanks for reading this far, even if you have no advice!
So after messing with this phone for the last few day I decided to do a full reset and wipe everything clean. I did so and after going through the set up process I couldn't get to the home screen. I just kept getting the error that touchwiz stopped. Luckily the restore loaded nova so I could get to the home screen to try and figure this out.
I tried everything from clearing data from the apps menu to booting into recovery and clearing cache. I Googled the error and found nothing I hadn't tried. I then did another master reset and it still won't load to touchwiz home.
Not sure what to do other than exchange the phone. Anyone have any idea?
verks said:
So after messing with this phone for the last few day I decided to do a full reset and wipe everything clean. I did so and after going through the set up process I couldn't get to the home screen. I just kept getting the error that touchwiz stopped. Luckily the restore loaded nova so I could get to the home screen to try and figure this out.
I tried everything from clearing data from the apps menu to booting into recovery and clearing cache. I Googled the error and found nothing I hadn't tried. I then did another master reset and it still won't load to touchwiz home.
Not sure what to do other than exchange the phone. Anyone have any idea?
Click to expand...
Click to collapse
Hey there,
I'm having the exact same issue and am BEYOND frustrated because usually I can find an answer on Google but it seems like no one seems to know what causes this, but many people have the problem. Did you happen to find a solution?
Brand new S6 Edge. Out of the box.
I've got this issue too.
Here's the steps I took.
No mobile connection as waiting for carrier to transfer account to new sim.
Connected to wifi.
Touched my S4 to the back to transfer accounts. Entered Samsung account details, requested restore.
Restore completes.
Set up finger print password.
Touchwiz has stopped error. Click OK. It repeats. again, and again.....
Power off, power on. Still get the touchwiz error.
Great out of the box experience. This is not good at all.
I don't know about the warranty in your country.
My advice is just reinstall the stock rom. It will clean all the problems.
My compromise so far...
The only way I've been able to use my phone so far in the last 12 hours since taking it out of the box is to set it up in "Easy Mode", which for a seasoned android user is not fun, but makes the phone usable. If not for that, I'm having the exact same problem with the error message and not being able to even get to my home page. Since turning my phone on I haven't seen my pages in standard mode yet. Hopefully I'll be able to contact someone today about this since I got the phone set up pretty late last night before noticing the error.
Has anyone experience the second screen not working all of a sudden? Mine is just dark with the main screen both on and off. I tried toggling the second screen on and off from the setting, reboot, battery pull, and wiping cache and dalvik but so far none worked.
It's not a hardware issue, I think, because when I open the camera, the second screen comes on for the camera Settings. Also, when in twrp, the second screen is also on as a part of the whole display.
EDIT: I can actually see some light bleed from the second screen with the main screen off. It's just not displaying information it should for some reason.
Sent from my LG-H901 using Tapatalk
I just got mine, and something I did in the course of adding/changing/modding did the same - I lost my second screen when the phone was off, but when it was on I had my shortcuts. I wound up factory resetting and re-installing/re-configuring my apps... knock on wood, everything works just fine now. I think mine failed when I unfroze an app in Titanium that it marked for me.
About the only thing that I did before I lost the second screen is installing a game from the play store. I have uninstalled it, but still no luck. I most likely will factory reset and if that doesn't work, I'll flash stock rooted rom... And set my phone up yet again.
Sent from my LG-H901 using Tapatalk
Same symptoms
I am on stock, albeit rooted. I froze a few apps, but I have also rebooted multiple times before the second screen disappeared, so I am not sure how anything I have done this far could be the cause.
Because I saw I am not alone, I started to do some digging. It looks like the app is located in /data/data/com.lge.signboard, which actually has symlinked directories. Not sure if its a clear indicator of the issue, but most of the directories are empty. Definitely odd.
I'll load up SSHd later and see if I can investigate more.
Did the factory reset and now the second screen works. I'm sincerely hoping that this is not a regular occurrence. I haven't liked a phone so much since galaxy s2.
Sent from my LG-H901 using Tapatalk
I also had my second screen go funky. Haven't factory reset but I'm going to. It seemed to happen as I was also defrosting and refreezing some LG things, mainly services and such and not apps that you interact with per se. At right about the same time I noticed something else strange. When plugging the phone in, it takes several seconds for it to realize it whereas before it used to be instant. Also, the camera is very slow to load and change from the front to the back ones.
So I got a little bored
And fired up adb logcat to see if I could find anything. I don't yet know if it's related or not, but there is a message
Code:
I/[SystemUI]MiniStatusBar( 5541): signBoardWindowShow() requested but unavailable. Hide MiniActivity.
that shows in the log.
I to tried clearing cache and dalvik or art or whatever to try to get the second screen back no avail.
I'm having the same issue. Any update on this?
I too am interested in this, I had this issue occur too when I froze some applications (system apps) that I didn't think were necessary. Unfortunately once you freeze the component it blocks the screen and unfreezing everything back does not bring the screen back you have to factory reset it. Any ideas of what the service is that affects the second screen?
Second Screen symlink busybox
After reading all your comments on what you could have done to cause the second screen from working, it looks like the symlink is broken especially if you have updated your busy box. I too started to have the second screen go bad on me and I couldn't figure it out until I read this thread especially the log post. I am going to reset and ensure that smart install is set right in busy box.
Recently, the AT&T LG V10 (H900) just got root here: http://forum.xda-developers.com/att-lg-v10/general/root-lg-h900-real-tot-make-tungkick-t3336317
I then debloated the V10 on firmware H90010f with Debloater v3.90 here: http://forum.xda-developers.com/android/software/debloater-remove-carrier-bloat-t2998294
Before, I decided to have the second screen off for a while, so I disabled it in the system's menu. I then advanced towards debloating. Decided to turn on the second screen again. Notice that there were issues with it. So now I'm currently experiencing this issue: the second screen does not show date, time, weather, notifications, quick icons. Only shows quick toggles if I swiped from right to left, such as sound profile, WiFi, flashlight, and camera. I undo all of the debloating, rebooted the phone many times, still the same problem. Sigh. I'm trying to avoid doing factory reset because I'm not up to reloading everything again, especially the SMS/MMS.
So, anybody found out a better solution other than doing a reset?
Update 1: It seems like re-rooting with updating the ROM with the "upgrade" option for the AT&T LG V10 to not do a full clean install does not solve the problem. I didn't lose all my personal data, but I did not gain anything that it restored system apps to previous default settings. Sigh, it's just one step closer to just do a factory data reset.
Update 2: There appears that other things were broken from disabling/removing apps (during phone calls, cannot multitask, such as switch apps or use the notification area; SuperSU couldn't generate a log correctly), so I went ahead and did a factory reset since there was no alternative restoring method. The second screen works again and so does the said apps. Looks like I'll have to be careful which apps I'll be disabling/removing with Debloater.
Uninstalling an app restored my second screen.
I had this issue as well. Camera controls were in the second screen space, the swipe to end call would appear, but none of my other settings stayed long after restarting my phone, maybe 10 min. I uninstalled some of my most recent apps, the suspect one being "Zooper Widget Pro" and the issue stopped. No factory data reset etc. This app was a launcher-type app (I'm a geek but nowhere near the tech terms used elsewhere on this site) and I thought it might be the issue due to its ability to control the home screen. I doubt it was intended to work with this arrangement. So I would look at any launchers or apps which can control the home screen before doing a reset as this exact issue was easily solved for me.
I just got the phone and set it up. the only thing I disabled was ATT bloatware nothing else. 2nd screen is only on when main one is on. Using nova launcher. I tried uninstalling and that didn't help. Is there any more info on this, can I get it working without factory reset ? I get no indication of notification right now other than sound.
I did factory reset and that didn't help either.
I have a same problem with the second screen to. So anybody can help me!
Is there anyone can help me pls!!!
I solved this problem by checking PINs on mainboard for the second Flex Cable for LCD of LG V10, see the video, READ comments here https://www.youtube.com/watch?v=hpeVAqgU94s, so in my case one of three PINs was folded little, so one PIN contact didn't touch the second Flex Cable and this caused the problem...