Related
So I moved some crap from system app (Bloatware) to my sdcard and rebooted and now I'm stuck at system checking.
Am I sol?
Did you do a backup first?
Nope of course not ROFL.
Okay I'm good it booted. What a scare!
"System Checking" means "you're screwed" in Korean. The phone will either reboot itself back to stock or you'll have to do a hard reset to revive it. It's happened to me three times.
yeah happened to me yesterday and ended up with a factory reset phone.
i wish someone would shed some light on this and the conditions by which it happens. This phone is full of mysteries from random reboots to factory resets.
I just wiped and installed EagleBlood, hoping it will do better (at least until CM7 is in good working order).
I thinks it's a corruption issue. Two times I was playing with settings (Bluetooth profiles, changing icons) and the phone started acting weird and I got "System Checking..." when I restarted it. The good news is that I can now completely load my apps and configurations in less than an hour.
happened to me yesterday, but I didn't let to finishing "checking". I pull the battery out and restarted the system. No factory reset or anything. the system booted nicely the second time. so next time you might want to do the same
Happened to me last week, and I wound up having to do a reset.
ikithme said:
So I moved some crap from system app (Bloatware) to my sdcard and rebooted and now I'm stuck at system checking.
Am I sol?
Click to expand...
Click to collapse
Glad to hear t booted.
What apps did you move?
this happened to me yesterday. not rooted. my phone did a random reboot earlier in the day and i noticed one of my alarms didnt go off so i powered down, turned back on and it gave me the system checking message. after like 3 mins it booted up fine.
uploder said:
this happened to me yesterday. not rooted. my phone did a random reboot earlier in the day and i noticed one of my alarms didnt go off so i powered down, turned back on and it gave me the system checking message. after like 3 mins it booted up fine.
Click to expand...
Click to collapse
I haven't seen this not to say it hasn't happened without me knowing but my guess is if the phone reboots or crashes and then at startup it notices a filesystem error or some corruption is when it throws that up. If it can fix it, it does (people who reboot fine) and when it can't you're hosed.
Think of it like if you have a desktop and you pull the cord. It will try to recover but depending on the state it was in it might not be able to.
ikithme said:
So I moved some crap from system app (Bloatware) to my sdcard and rebooted and now I'm stuck at system checking.
Am I sol?
Click to expand...
Click to collapse
my phone only did that after i did super one click and i figured it just verified new files or something. im still up and running great. i have 5 backups. can never be too careful
I notice mine does system checking if I forget to mount the /system filesystem back to read only before a reboot!
Happened to me last night, except i was not so lucky. the phone kept rebooting and never get to pass the LG start up screen. Tried the hard key reset and it showed a message of "S/W Upgrade, Please Wait"
Phone t-mobile, they're gonna send me a replacement phone, less the back cover. As soon as the new phone was on its way, I tried to hard key flash again and this time it worked.
But, I am still gonna return this POS and hope the new one can perform better.
Had this happen this morning. I had used the Quick Boot app to reboot my phone, and after it reset I had "system checking" for a few minutes, followed by an infinite bootloop!
Fortunately I had installed ClockworkMod Recovery yesterday and made a nandroid backup, so after restoring that I was back in business.
I will no longer use Quick Boot though. It seems to shutdown the phone unsafely.
Sent from my LG-P999 using XDA App
to stop Verizon from forcing update
Use Titanium to freeze com.smithmico
i lost root because vz forced the update so i reinstalled .5 oem then used revoluton to unlock boot in stall SU installed .9 radio seems to work well rebboted it pop saying .9 would start download in 26 secs i stoped it from installing
i remembered reading about smithmicro and OTA so i froze it so far n more pushed OTA ...
your mielage may vary
Or just delete it completely. Not needed and is in my top 10 list of things to remove via tb.
Could you tell me exactly how you reinstalled .5 after having .9 already on the phone?
http://www.multiupload.com/WES9PABEQF
rename it PG05IMG.zip copy to sd card reboot do power volume restart it should do it itself don't shutdown until it is completley finished.
I did that but it won't downgrade. It says I have the newest version installed so it won't flash the "older .5" version. Any suggestions?
Make you rename it pull battery two button restart and it will load .5 I had no issues
Sent from my ADR6400L using Tapatalk
davwman said:
Or just delete it completely. Not needed and is in my top 10 list of things to remove via tb.
Click to expand...
Click to collapse
Is that uninstall com.smithmicro.DM 1.0.0 ? Is this the right thing to uninstall for no OTA? Thanks
If so, I think I will uninstall this before I flash the new radio. What do ya think?
i don't see that file... on a side note, i updated the radio this morning and still no message to update so not sure if i'm in the clear or not
so what does com.smithmirco actually do? is it just an updater?
My phone seems to be stuck in the process. I can't locate a p50IMG on the SD card and before I can even open Titanium my phone starts to power down and tries to install the update, but fails. Any ideas?
---------- Post added at 01:51 AM ---------- Previous post was at 12:57 AM ----------
Finally think I figured it out for my situation. As soon as home screen loaded I opened up TasKiller, killed everything. Repeated that 4 times so that everything loading up with the phone was killed before it would reboot the phone. Went to app drawer and made a shortcut for Titanium right next to TasKiller. After this I went in and killed all apps again.
Now let's freeze some things via Titanium so it doesn't try to reboot to install an OTA. First I froze com.smithmicro, next I froze HTC DM. After these two I let the phone go while I messed around for a few minutes, after this I turned airplane back off. I checked TasKiller and noticed that an app MCC_OTA had opened, fearing this may be the cause I killed all apps again and went in to Titanium and froze this.
15 minutes later and I've had no issues with cell/data service. I can get into the market, update apps, receiving gmail/email, and Facebook working fine.
Pender1 said:
so what does com.smithmirco actually do? is it just an updater?
Click to expand...
Click to collapse
I am not trying to be an alarmist, but a description from Smithmicro's site sounds strangely similar to the description on the Carrier IQ site. I will let you be the judge.
"Device Management Suite™ (DM Suite) is a standards-based server solution for mobile device management, enabling mobile operators to remotely customize, provision, configure, and diagnose mobile device settings."
http://www.smithmicro.com/products/device-management-suite.aspx
Still running strong, no problems and no force OTA attempts.
Woke up at about 4:00 AM this morning and my phone was sitting at HTC screen. Pulled battery and phone rebooted, quickly showed OTA icon and rebooted.
It got to the android man screen and got stuck there. Again pulled the battery and rebooted in to recover. Wipe Davlik cache and regular cache, rebooted and phone appears to be back to normal.
Rooted running Team Gingerbreaton ROM. This is the second time in the last few months that the forced OTA has tried to run itself.
CenFlo said:
Woke up at about 4:00 AM this morning and my phone was sitting at HTC screen. Pulled battery and phone rebooted, quickly showed OTA icon and rebooted.
Click to expand...
Click to collapse
Happened to me this morning too. Good thing the phone sits next to my bed (use it as an alarm) and woke me up since I would have oversleep without it. Of course, I lost two hours of sleep because of it since I couldn't get it working in my half-sleep state and just stayed up because I didn't want to be late to work.
I need a real alarm clock.
CenFlo said:
Woke up at about 4:00 AM this morning and my phone was sitting at HTC screen. Pulled battery and phone rebooted, quickly showed OTA icon and rebooted.
.
Click to expand...
Click to collapse
Happened to me as well. Up at 4:30 roughly with nothing working. Cleared cache as suggested and phone is now powered up but no longer showing 3g or 4g, simply 1x so something is still wrong. Have to get ready for work at this point and will have to do some more digging.
CenFlo said:
Woke up at about 4:00 AM this morning and my phone was sitting at HTC screen. Pulled battery ... Wipe Davlik cache and regular cache, rebooted and phone appears to be back to normal.
Click to expand...
Click to collapse
Thanks for that. I was losing my mind this morning. Woke up, grabbed phone, and it had the sad Android screen with the Exclamation triangle. Felt like Anakin at the end of Ep. III for a bit. Did a search for "Block update" and came to this thread. Now to flash a non-Verizon ROM so I don't have to go through that again.
Just got another OTA notification this morning, was able to delay it... WTF? I'm rooted running a custom ROM and it's still trying to push this updated.
Just an FYI, if you get the update. Revolutionary root no longer works.
I woke up to my phone stuck on the black screen with the little Android man also. I pulled the battery, powered up and quickly restarted into recovery. Then I factory reset from recovery and after that I re-flashed my shift ROM and all is good so far. *knocks on wood* Anyone think its the new radio I flashed that prompted this or did they push everyone??
zx12dak said:
I woke up to my phone stuck on the black screen with the little Android man also. I pulled the battery, powered up and quickly restarted into recovery. Then I factory reset from recovery and after that I re-flashed my shift ROM and all is good so far. *knocks on wood* Anyone think its the new radio I flashed that prompted this or did they push everyone??
Click to expand...
Click to collapse
I had the same issue -- I received the update even though I had not accepted or checked for it. Took my phone out of my bag at work and saw I was at the Android man and exclamation point screen.
I wiped cache and wiped Dalvik cache, and the update stopped. I did flash the new radios though for the .9 update and have been sitting fine on 4G for the last two hours.
Hello Everybody
My name is Ilario from Lodi Italia, i have a problem with my nexus 4 16gb
the problem is:
starts will read ANDROID and goes into optimizing applications 104
then finished the optimization app appears starting with the circle of renovation that will continue to rotate endlessly
I have restored the factory, I installed both original ROM that cyanogen mod but the problem remains the same
Have a suggestions?
Many Thanks a lot
Ilario Orlandi
Same Issue
I second this. I am having the same issue. A couple of days ago my phone died. After plugging it in and letting it charge a bit, I tried to power it on but it stayed on the boot screen (rotating light balls) for hours. I rebooted it and then it stated "android is starting...optimizing app x of y." It then stayed on this screen for hours. My phone has never been rooted or even unlocked. It is completely stock, but won't go past the boot screen. I tried clearing the cache, and then did a full factory reset through recovery menu. Still same thing. Downloaded Nexus Root Toolkit and flashed the stock, still same thing. Any advice would be greatly appreciated. Thanks.
i_orlandi said:
Hello Everybody
My name is Ilario from Lodi Italia, i have a problem with my nexus 4 16gb
the problem is:
starts will read ANDROID and goes into optimizing applications 104
then finished the optimization app appears starting with the circle of renovation that will continue to rotate endlessly
I have restored the factory, I installed both original ROM that cyanogen mod but the problem remains the same
Have a suggestions?
Many Thanks a lot
Ilario Orlandi
Click to expand...
Click to collapse
Did this happen after any specific update.
I think you guys should start the device and leave it all over night. Plug the device in charger and leave it onn whole night.
Next day will bring same happiness for you.
Sent from my LG-X160 using XDA Free mobile app
My phone has been misbehaving since it upgraded the OS to Marshmallow. It was primarily occurring with the Google Now app and it would take over the phone and flash up and off the screen and whilst this was going on, the phone is busy vibrating, the screen became unresponsive and generally I couldn't do anything with it during these episodes. I stopped it sending to the screen and then it was the Google app that kept flashing up, starting with a round circle coming from the app drawer icon. It has got worse over the last few days to the point that it might take me ten minutes before I could get access to the caller to make a call and even trying to shut down the device was near impossible because the confirmation box never stayed on the screen long enough to answer the question and then it didn't come back. Yesterday, after many tries to restart, it finally restarted in safe mode. If it was related to an app that I downloaded, it should have stopped then but it didn't. When I was able to get into settings, I then went to apps and then disabled google app as this was the one starting up and flashing the screen non stop. I was then asked if I wanted to replace it with a factory version which I did but I also left it disabled. The problem has continued but not as ferociously with the screen becoming unresponsive at times while the buzzing from the vibrate still occurring. I have looked up various forums but haven't found any that have similar problems described. I checked the screen overlay settings and they are enabled and that seems to be the main problem with marshmallow. I'm looking for some advice but realise that this might be too basic for this forum? Vodafone Smart ultra 6, Android version 6.0.1 Kernel version 3.10.49
Stoksie said:
My phone has been misbehaving since it upgraded the OS to Marshmallow. It was primarily occurring with the Google Now app and it would take over the phone and flash up and off the screen and whilst this was going on, the phone is busy vibrating, the screen became unresponsive and generally I couldn't do anything with it during these episodes. I stopped it sending to the screen and then it was the Google app that kept flashing up, starting with a round circle coming from the app drawer icon. It has got worse over the last few days to the point that it might take me ten minutes before I could get access to the caller to make a call and even trying to shut down the device was near impossible because the confirmation box never stayed on the screen long enough to answer the question and then it didn't come back. Yesterday, after many tries to restart, it finally restarted in safe mode. If it was related to an app that I downloaded, it should have stopped then but it didn't. When I was able to get into settings, I then went to apps and then disabled google app as this was the one starting up and flashing the screen non stop. I was then asked if I wanted to replace it with a factory version which I did but I also left it disabled. The problem has continued but not as ferociously with the screen becoming unresponsive at times while the buzzing from the vibrate still occurring. I have looked up various forums but haven't found any that have similar problems described. I checked the screen overlay settings and they are enabled and that seems to be the main problem with marshmallow. I'm looking for some advice but realise that this might be to basic for this forum? Vodafone Smart ultra 6, Android version 6.0.1 Kernel version 3.10.49
Click to expand...
Click to collapse
When you updated to Nougat, what method did you use to update? Did you update via OTA? We're you rooted when you did it?
Have you tried booting to recovery and factory resetting and wiping cache then rebooting?
Sent from my SM-S903VL using Tapatalk
Droidriven said:
When you updated to Nougat, what method did you use to update? Did you update via OTA? We're you rooted when you did it?
Have you tried booting to recovery and factory resetting and wiping cache then rebooting?
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
It was an update that appeared on my notifications and I thought it was a small bug fix update and didn't realize that it would replace the entire OS. I just allowed the update and then realized what had happened. I think it is Marshmallow that it updated to but originally the app drawer was paginated and accessed by side swipes whereas the system now is a long page of apps moved up and down. I don't know if it was rooted and I assume that that means it wasn't.
I was trying to avoid a factory reset but I did wipe the cache and rebooting. When google apps is disabled, the interruptions are less often and not for as long but it still went into a complete meltdown of a screen appearing and disappearing at such a rate that nothing can be done with it. It won't show a video because of the interruptions.
Stoksie said:
It was an update that appeared on my notifications and I thought it was a small bug fix update and didn't realize that it would replace the entire OS. I just allowed the update and then realized what had happened. I think it is Marshmallow that it updated to but originally the app drawer was paginated and accessed by side swipes whereas the system now is a long page of apps moved up and down. I don't know if it was rooted and I assume that that means it wasn't.
I was trying to avoid a factory reset but I did wipe the cache and rebooting. When google apps is disabled, the interruptions are less often and not for as long but it still went into a complete meltdown of a screen appearing and disappearing at such a rate that nothing can be done with it. It won't show a video because of the interruptions.
Click to expand...
Click to collapse
Unfortunately, I think you're gonna have to factory reset in stock recovery because there's obviously a conflict with something you already had on the device and it isn't playing nice with something that was in the update.
Sent from my SM-S903VL using Tapatalk
Droidriven said:
Unfortunately, I think you're gonna have to factory reset in stock recovery because there's obviously a conflict with something you already had on the device and it isn't playing nice with something that was in the update.
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
Thanks for taking the time to respond. I have resigned myself to that although it does not seem to be anything that I downloaded to the phone as it occurred in safe mode too. I was just hoping that there was a fix out there but obviously it is not a widespread occurrence.
Stoksie said:
Thanks for taking the time to respond. I have resigned myself to that although it does not seem to be anything that I downloaded to the phone as it occurred in safe mode too. I was just hoping that there was a fix out there but obviously it is not a widespread occurrence.
Click to expand...
Click to collapse
It could have been something in system that got changed during the update but the data from before the change is still there and conflicting with whatever changes were made. Some kind of saved system data that can only be wiped by factory reset or reflashing.
Sent from my SM-S903VL using Tapatalk
I did a factory reset, lost a lot of photos that had started being saved on the phone and not the sdcard after the upgrade to Marshmallow. Have had to accept that but unfortunately the bizarre behavior did not stop and it continues on and off, sometimes so bad that I cannot dial a number on it and other times it happens but I can get in between the action and dial or send a text etc. I have gradually been stopping things like notifications from google apps and traffic reports from google maps (this may have had a good effect) and anything that might be doing constant checks. It seems to have quietened down over the last day or so and I even got to play a game on it but the next option is to send it away to an engineer. I just thought that I would let you know the outcome of the factory reset.
Hi. My device worked just perfect until 5 days ago. It slowly began to ignore some tasks like opening apps or doing calls.
2 days ago my google pixel with Android 8.0 started to ignore every input i made, like opening apps or trying to reboot. It behaving like this after taking some pictures with the rear cam. After some attepts in opening apps it started to reboot. But instead of a normal reboot it stuck in a booting screen (the one with the Google G and a gray animation bar underneath). It took a while and i waited until it seemed that the OS booted correctly. But after this my device started to reboot randomly after a few minutes. After a while i figured out, that i can hold the power button while the screen with the google G was up to reboot it normally. This worked so that the phone was at least half an hour or more working until it rebooted again out of nowhere.
So far i tried to get it in safe mode and delete some apps like whatts app etc. In safe mode i didnt notice any crashes so far.... but in normal one it does a lot so deleting apps wasnt helpful. Turning on flight mode was not helpful either.
What can I do? What could it be?
marf3 said:
Hi. My device worked just perfect until 5 days ago. It slowly began to ignore some tasks like opening apps or doing calls.
2 days ago my google pixel with Android 8.0 started to ignore every input i made, like opening apps or trying to reboot. It behaving like this after taking some pictures with the rear cam. After some attepts in opening apps it started to reboot. But instead of a normal reboot it stuck in a booting screen (the one with the Google G and a gray animation bar underneath). It took a while and i waited until it seemed that the OS booted correctly. But after this my device started to reboot randomly after a few minutes. After a while i figured out, that i can hold the power button while the screen with the google G was up to reboot it normally. This worked so that the phone was at least half an hour or more working until it rebooted again out of nowhere.
So far i tried to get it in safe mode and delete some apps like whatts app etc. In safe mode i didnt notice any crashes so far.... but in normal one it does a lot so deleting apps wasnt helpful. Turning on flight mode was not helpful either.
What can I do? What could it be?
Click to expand...
Click to collapse
Same thing happens with my Pixel, sometimes the phone is just get stuck on some random screen then I have to press and hold it for 15 seconds to let it reboot again. Lately I have started to see another problem, when it reboots bunch of google apps and services stops working and gives hell lot of notifications. All this started to happen after Android Oreo update
pradctgign said:
Same thing happens with my Pixel, sometimes the phone is just get stuck on some random screen then I have to press and hold it for 15 seconds to let it reboot again. Lately I have started to see another problem, when it reboots bunch of google apps and services stops working and gives hell lot of notifications. All this started to happen after Android Oreo update
Click to expand...
Click to collapse
I noticed problems with my ear speaker as well. And i cant make phone calls. The phone doent respond anymore when i try to.
Same problem after android 8.0 update
If you have installed the latest Google phone/dialer app, that is likely the problem, was for me.
Find the app in settings and uninstall,it will roll back to a previous version and hopefully fix your issues.
Sent from my Pixel using Tapatalk
My pixel does the same thing, ever since I updated to 8.0, have you tried doing a factory reset? I haven't done it yet, I have been uninstalling apps for the last couple of days, when it is in safe mode it works good, but when it's not, it freezes and restarts. I'm going to try uninstalling the latest version on google dialer to see if it helps.
I just want to update everyone in case you are having a problem with the random reboots.
I uninstalled the phone update and it was still randomly rebooting so I backed up the stuff that I needed and just did a factory reset. I have been a full day on my phone without any problems. I did a factory reset twice, just in case, for some crazy reason, the phone still had a problem, I wiped it twice! I think you'll be good with only wiping once.
Anyways to sum it all up, I did a factory reset, restored all of my backed up data from my pixel, I had about 120 apps and the phone has not had a problem since. I hope it helps someone else.
droid4lif3 said:
I just want to update everyone in case you are having a problem with the random reboots.
I uninstalled the phone update and it was still randomly rebooting so I backed up the stuff that I needed and just did a factory reset. I have been a full day on my phone without any problems. I did a factory reset twice, just in case, for some crazy reason, the phone still had a problem, I wiped it twice! I think you'll be good with only wiping once.
Anyways to sum it all up, I did a factory reset, restored all of my backed up data from my pixel, I had about 120 apps and the phone has not had a problem since. I hope it helps someone else.
Click to expand...
Click to collapse
Mate, please report if you're still getting the reboots. Mine disappear for two weeks after I do a factory reset and then come back. Same happens in Safe Mode. Bug report claims it's 'Sense Key : Hardware Error [current]' and Google rep says it's a hardware issue (Toshiba's memory or something). Buganiser thread is here.
wrong place sry
Had this on my pixel xl. I was on the 8.1 beta.
factory reset, rolled back to 8.0
8.1 ota official
haven't had a reboot in over a week now
Murrzeak said:
Mate, please report if you're still getting the reboots. Mine disappear for two weeks after I do a factory reset and then come back. Same happens in Safe Mode. Bug report claims it's 'Sense Key : Hardware Error [current]' and Google rep says it's a hardware issue (Toshiba's memory or something). Buganiser thread is here.
Click to expand...
Click to collapse
Yea, the issue is back, has been for about 2 weeks. This phone is really starting to be a pain in the ass, I can't believe that it happens so often. Did you do a warranty fix?
That's a pity. Yes, I did. Got the device roughly two and a half weeks ago. Flashed 8.0 and then sideloaded 8.1 right away. Knock on wood, all good. But there's still a report every other day in Buganiser of a phone even on 8.1 doing this.
Got mine at release. November 16. Google won't replace it either. I have a one pixel brick
I have the same problem. However, it is not frequent enough on Android P beta. But as soon as I go back to the stable build, it starts to do the same thing. Did you guys have any luck resolving this or should I send it back to the vendor I bought it from. They won't replace the device in Pakistan but may be will fix it in some manner.