I have a head unit with an MCU version of MTCD_GS_V1.78_1.
Every couple of days, it hangs at boot and eventually says "Optimising Apps, 1 of 1". It then does what seems like a hard reset and when it finishes booting, it's back to factory settings having forgotten all of the configuration I've done. I think it does this after something has been installed or updated, but I can't work out exactly what is causing it at present.
Any ideas what would trigger this would be much appreciated.
Related
i searched and could not find anything about this issue.
i'm stuck at the startup screen where it shows the radio, rom versions in the lower right corner.
soft reset returns it to the same place, and holding down the power does nothing. removing the battery does nothing. and i'm physically unable to do a hard reset. http://forum.xda-developers.com/showthread.php?t=413976
what can i do? i have hardspl 1.40, new radio and flashed one of the roms here. it was working for a while, then i installed a bunch of cabs, and unsuccessfully tried to hard reset about 25 times (i had 2 internal storage folders for some reason and i wanted to clean it up), gave up on hard reset, did a a memory cleanup by settings-clean memory-1234 way, soft reset several times while reinstalling cabs again and now it gets stuck at the screen...
fixed by going into bootloader manually and flashing the same rom again. it works now. but i'm going with another rom.
all was fine, then i installed the touch diamond 2 keyboard and didn't like the one with the arrows so i uninstalled and this same problem came up again. the last i suspected that was the cause too so this is just so it's documented that uninstalling the TD 2 keyboards causes this problem.
hard reset and putting all my settings again, oh joy....
So I've had some weird stuff happening the last couple days, which is to be expected since i've been experimenting with JPH, OCLF 2, and Rooting.
Now, last night I decided to flash back to JG8, re-partitioned, then factory reset. Then I flashed JPH and factory reset. Now after I got all my apps setup again, I thought I was good, but decided to reboot once more. Upon reboot, everything looked like a normal boot, but i was greeted by a phone in a semi factory reset state. By that I mean, everything looked factory, but if I went into manage applications I could see the com.blah.packagnames of some of my apk's i had installed, but none had icons, and they all showed 0 size.
The only possible reason I can think of for this to happen is that I rebooted while my phone was plugged into my pc, and while odin was open (although it was not doing anything at the time).
I'm kind of afraid now of having my phone randomly go back to basically, factory defaults on its own. Has anyone experienced this? Is there a good explanation? If I can reproduce it, I'm happy to avoid it, it's the lack of predictability right now that worries me.
Thanks
This is one of the weirdest problems I've had. I'll try to be very specific. I'm running Android 6.0 on a Moto G 2014. I was just using my phone, on YouTube, when it decides to randomly reboot. Ok, just an error. Then I noticed that my phone's lockscreen never shows up anymore, and I can't pull down the quick settings. I thought it was just an error from the unexpected reboot it had, so I do a full reboot. No change. Okay, maybe clearing cache and dalvik will solve this. Cleared, reboot, Android is Upgrading, and no change. Okay, now I'm worried. So I restore a system backup from a month ago, reboot, and no change. I also tried uninstalling xposed framework, and no change. Now I don't know what else there is to do before factory resetting, because I really don't want to do that. By the way, here's all of the problems I've noticed since that reboot:
Can't pull down notifications.
Lockscreen will not show up at all.
Home button does not work at all, pressing it does nothing. I have to press back if I want to get to the homescreen.
"Developer options are not available for this user" error screen, even though I'm the only user
adb won't respond (probably for the reason above)
I get no notifications at all
I can't receive calls
Any tips or steps I should take to find this problem? Any help is appreciated.
Solved
Restoring System, Data, and Boot from early June took the problem away. But it bothers me that I'll never know what the problem was.
Boy am I upset about this. So I get the update and I even liked it looking around at the new freed up internal storage. Well, I clean my history, run ccleaner, etc. like I normally do to restart and when I restart it will not pass the fire screen whatsoever. Now this tablet is not and has never been rooted or tampered with in any malicious way. Launcher hijack and things from this forum are the only tweeks used. It will not work.
I have tried factory reset dozens of times, restart, anything I can do from the hardboot blackscreen (I guess it is called). Somehow managed to make it run the initial setup once, ran through hours of fixing it back the way it was. Restarted it again, bricked again. I can never manage to factory reset it like normal again and I mean I've tried 30 times by now. Only "Fire" loading screen. Has anyone seen this? This is not fair.
CaptainPatterson said:
Boy am I upset about this. So I get the update and I even liked it looking around at the new freed up internal storage. Well, I clean my history, run ccleaner, etc. like I normally do to restart and when I restart it will not pass the fire screen whatsoever. Now this tablet is not and has never been rooted or tampered with in any malicious way. Launcher hijack and things from this forum are the only tweeks used. It will not work.
I have tried factory reset dozens of times, restart, anything I can do from the hardboot blackscreen (I guess it is called). Somehow managed to make it run the initial setup once, ran through hours of fixing it back the way it was. Restarted it again, bricked again. I can never manage to factory reset it like normal again and I mean I've tried 30 times by now. Only "Fire" loading screen. Has anyone seen this? This is not fair.
Click to expand...
Click to collapse
Yes - I have (indirectly) seen this on numerous unrooted Amazon Fire devices from several generations following a major OTA update. In most cases the device is NOT recoverable unless the bootloader is unlocked (not possible on 5th-7th gen devices). Boils down to a borked update which is not totally unexpected given the manner in which they are engineered and administered by Amazon. Clearly a very high percentage work without issue. Still sucks if you're a member of the substantial minority...regardless of size. You can try giving Amazon support a call...they might throw you a coupon that can be used against a future purchase (including deeply discounted Amazon/Fire devices during "Black Friday" week).
Just an update on this...
After a few days of not being able to use it I powered it on for the umpteenth time and it properly went through factory reset mode. I was able to manually download the 5.6 update again and it is finally back to normal. Funny thing is I now have even less internal storage than before but at least it is working now. That was a huge inconvenience and I still have no clue what happened.
My Mi A2 was behaving weirdly. Uninstalling apps was making the system to freeze and reboot itself. There were also other small nagging issues. So, decided to do a factory reset.
I did the factory reset from withing setting menu. After confirming to go ahead with the factory resetting, the phone rebooted to a black screen displaying "Erasing" and then it powered off. I waited few minutes thinking that it might have been doing something in the background. But the phone didn't boot itself. I pressed and held the power button and then it booted just fine and I continues with the setup procedure. I have owned several android phones previously, but each one of them rebooted itself after factory reset.
Is this something new/normal to Android One devices? Or did I unknowingly interrupted the resetting procedure? Does anyone have any experience/insight on this issue?
P.S.: I removed my google account and screen-lock before resetting.
P.S.: I did a reset again and this time it behaved as expected and rebooted itself as normally it should.
it might be hardware issue
MIN313 said:
it might be hardware issue
Click to expand...
Click to collapse
Did the factory reset again and this time it behaved as expected and rebooted itself. Anyway, Thanks for the comment