Summary:
So this morning (abiout six hours ago) my beloved S2 running CM12 crashed and could not reliable boot since then, it goes into some kind of weird bootloop.
The issue in detail:
Attempting to boot (long press on power button) will bring up the "Galaxy I9100" as sually and continues with the CM12 bootloader animation. After the typical time required to boot it vibrates slightly as usual, but afterwards the screen dims for about a second and the whole process is repeated.
What I did shortly before the issue:
Google Play wanted to update apps, but I was out of internal memory. So I went to /data/data and searched and deleted all files containing "cache". I've done this about 20-40 times over the last months (I didn't keep count) and never had any issue.
Things I've tried:
It is possible to access the recovery mode, but the options in CM12's recoverey are very limited (unlike TWRP for example). I cleared the cache but it had no effect.
After taking out the battery the "optimizing apps" windows pops up. When it's done, user input (enter sim, unlock pattern, homecreen) is possible, but only for a few seconds. The first time I missed the chance, the second and thired time I immediately restarted into safe mode.
Safe mode works surprisingly well, the first time I used it to let google continue the updates and disabled autostart of Applock and Greenify, the second time I uninstalled both Apps and cleared the dalvic cache (simply by deleting data/dalvic/). Neither attemped solved the issue.
What I'm currently doing:
After booting into safe mode for the 4th time I'm starting to back up all user data. Communication with a PC works only for some time, but reconnecting solves the issue (for now).
So what's next?:
Honestly I've no idea what I'm doing. I've installed CM on 3 devices in the past 4 years, but thats all experience I have. I'm hoping that I'm just missing an important detail and can get around all these problems with a simple fix. If not, I'd try a clean install, but I'd like to avoid that.
So, if you've got ANY IDEA what the issue might be or what to try, I'm open for all suggestions! Chances are that I haven't left the safe mode since posting, so you can also request sceenshots of anything you need. Thanks!
Screenshots or other related documents are in my sync.com folder: https [colum slash slash] cp [dot] sync [dot] com/dl/9b9bc5440#5b27p5ig-jfevicd7-kbnrzgcj-i2giy43b
Current screenshots: installed apps, phone info
I'll update this thread with all step that I take, so that a) you know where I am b) I remember everything and c) people with similar problems might benifit:
• The USB connection was kinda fragile, so I copied all data to the micro SD instead
• sdcard0 could be copied without problems
• phone crashed during coping of other files in root. Folder "sys" has been copied (at least partionally) before crash
• reboot normal, but always with message "Trebuchet was closed"
• seems to work fine now
• exit plane mode (I've enabled it before to charge quicker and reduce heat) and display turns black
• medium long press on power button brings up restart menu, nothing else can be done (checked: double click home button for camera, long click for recent apps)
• turn on airplane mode again and restart and its just fine again
• tried out a different sim card, same issue.
Based on all this, I'd say the issue is a third party app acting (badly) on the ppresence of a mobile connection. Weird. Will investigate the issue further tomorrow, or - more likely - flash the new lineageOS version. I'll report back when I know more.
After making a backup of ALL files I followed the pinned tutorial to install linageOS. Everything - including mobile connection - seems to work fine now! Thanks @djibe89 for such an amazing easy-to-follow tutorial
You can consider this thread closed
Related
Hi guys,
Wonder if anyone can shed a light why this happens. It's been going on for the last few months – Originally I thought I'd wait and see if the problem resolves by itself. But seems to get slightly worse over time now.
I am currently: Rooted & Unlocked
Problem: System hangs after reboot at home screen with message “Process System Not Responding” - with option to wait or terminate the process – Whatever option is chosen, ATP will reboot itself.
Frequency: Unpredictable – But once the message appears after switching it on, ATP will reboot itself 2 to 4 times before I can use it again.
I had done a lot of searches, but there doesn't appear to be any solution / or anyone knows why this is happening. One useful comment I found recently said this may be due to some processes starting before they are meant to during boot up sequence – but no details were given.
What I had tried (based on numerous suggestions after searching the net):
Wipe Dalvik Cache / Caches
Clear “Media Storage” and “Google Framework Services” data
Remove my accounts (currently I have two accounts registered in my ATP) and re-register the accounts.
Remove all the widgets from home screen
Hard reset / Factory Reset
Finally – Multiple different combinations of the above
Getting quite frustrated here.
Wonder if anyone can help please?
Thank you in advance.
[Q] "Process System Not Responding" researching and even downgrading to .15 --> .21, I think the problem is finally solved.
Allegedly "Process System is Not Responding" may be caused by process(es) that hangs or take too long to complete during the boot up sequence. So I uninstall blindly one program at a time - and it appears that Cachemate might have caused it.
Prior to this, every 3-4 normal boots, were followed by 2-3 "Process System is Not Responding" until a normal boot followed. I am now 48 hours problem free. Hopefully it will stay this way.
Edit (11/06) - Ok, spoke too soon. Got the message again after 24hours of use and after roughly 15 normal reboots (I switched ATP off/on these many times to make sure the problem was well and truly gone). The Cachemate could just be a red herring then. However there appear to be less in term of frequency. I noted that the message came on after I watched a video (3hours long video - 600mb in size) and rebooted ATP. Tried disabling media storage (no real logic here, I thought I just gave it a go) - but the problem is still there. So this evening, I reflashed the asus .21 rom --> downgrade to .15 --> reroot --> upgrade back to .21 (again to real logic here, thought I give it a go).
I can't think what else to do. I wonder if large hosts file (mine is 8mb) could cause the problem or the wallpaper I use that is stored under /sdcard - but again, the problem/message only comes up randomly.
Edit (13/06) - Finally managed to narrow down the problem. Everytime a large hosts file (mine is about 8mb) is created, the problem comes (faithfully everytime). And when the original smaller hosts file is restored - problem is gone entirely.
Any input on workaround is very much appreciated.
alright i fixed it on my phone. i did a full wipe. tell me if i need to explain how to do this. reflashed the ROM and gapps. when i went through the setup the first time there was an option to restore from google. it was checked by default. i left it checked. same problem... system process not responding... wiped and started over and reflashed ROM and gapps. unchecked restore google and it didnt come back. phone hasnt crashed since. the problem lies within the wifi passwords restore. the problem started when i was trying to start wifi. i dont know where to report the bug or i would. good luck and any questions? just quote this so i get an email and ill try to explain if this didnt make sense. hope it helped. if it did consider buying my buddy a beer who is a dev and needs a new computer. http://johntriger-development.yolasite.com/
Greetings.
Sorry for my grammar, I'm not a native english speaker, still learning.
I've got an unexplainable trouble, kind of frustraiting.
Phone: Galaxy Tab 10.1 P-5100 model.
Android: ver. 4.0.4
Stock ROM: official russian P5100XXLF2
The problem is, when I turn off and then turn on my device (or simply restart it) system is restored to some earlier state, this include:
1. Apps I've deleted are still installed.
2. Widgets or app shortcuts on 'home' pages are still on their old place though I've rearranged them.
3. Same with wallpapers.
4. Same with settings.
What I've tried:
1. Factory reset + cache clean. Even though it is supposed to be a full system wipe, it doesn't work.
2. Reinstalling Stock ROM via ODIN. Doesn't work either. Weird thing is, when I've done it before, it was done in about 5 minutes, but this time I've waited for about 1 hour.
Also there is a notice in android recovery, which states:
did not match sized '/system/csc/common/system/csc/feature.xml' (no data available)
Device wasn't rooted (whatever it is, at least I haven't done anything).
Yeah, I've used google search, It's a known issue but nothing useful was found.
Would appreciate any ideas how to fix it.
Added: also
1. I connect my device to pc via usb
2. I remove my music from device via PC OS
3. I disconnect the usb cord.
4. I reboot the device
5. Voila, music is still there.
did you fix this problem i have the same issue
Hello all! I registered real quick in hopes this community could help me out with something.
So quite a while ago I rooted my Lenovo Tab 2A 10-70 tablet with KingoRoot in order to generate a logcat file. That went fine and dandy, and then I disabled some misc. apps (like Kindle for Android). I can't remember exactly what I messed with, so please bear with me.
The issue is that a couple of days ago I tried taking an image with my tablet with the default Camera app, when suddenly it started giving me some errors with generating thumbnails. Worse yet, my computer could not open these and they were seemingly corrupted. The camera started acting up as well, and claimed that "Unfortunately, Gallery has stopped working." whenever I attemted to record. I tried clearing the cache based on some recommendations through others and force stopping the app, and this seemingly worked for one recording/picture, but then would stop again. I found deleting the DCIM folder entirely from my Android's Internal Storage helped, but it'd quickly corrupt again.
Frustrated, I asked a friend for help on what to do figuring he had more knowledge in Android devices then me. He suggested I tried another camera app, but I couldn't get Google Play to download anything to the internal storage or my SD card, despite clearly having enough space.
As a last resort, I tried updating through the official "Updates" app to see if that would help me, and it claimed there was a new ROM available. I tried that, but then suddenly it failed and now my tablet seems to bricked? I can now only get the "No command." screen to show up.
I've tried using the following options while on this screen:
- reboot system now - this takes me back to this menu after it shows a Lenovo screen twice, which makes me think it's having trouble booting into Android itself.
- Apply update from ADB/sdcard - Both did nothing for fairly good reason, but I checked these options out of curiosity.
- wipe data/factory reset - Tried these the very first time I got to this screen after a failed installation. It seemingly hasn't worked for me.
- wipe cache partition - Tried this a bit later, but got similar results.
- root integrity check - Scanned a bunch of .apk files, but then later threw up some errors after that was done and said the check failed.
So, in short, I'm stuck in this menu and I'm getting kind of frustrated/scared. Is there anything that I can do to save the tablet at this point? Is there something I did wrong that might have bricked it? I'm not terribly experienced with Android, so I'd love to hear some thoughts from others! I'll gladly take anyway to restore the tablet back to a point where it can actually boot into the OS, and I understand I'd lose some data doing any sort of clean install.
Thank you!
Cornholio309 said:
Hello all! I registered real quick in hopes this community could help me out with something.
So quite a while ago I rooted my Lenovo Tab 2A 10-70 tablet with KingoRoot in order to generate a logcat file. That went fine and dandy, and then I disabled some misc. apps (like Kindle for Android). I can't remember exactly what I messed with, so please bear with me.
The issue is that a couple of days ago I tried taking an image with my tablet with the default Camera app, when suddenly it started giving me some errors with generating thumbnails. Worse yet, my computer could not open these and they were seemingly corrupted. The camera started acting up as well, and claimed that "Unfortunately, Gallery has stopped working." whenever I attemted to record. I tried clearing the cache based on some recommendations through others and force stopping the app, and this seemingly worked for one recording/picture, but then would stop again. I found deleting the DCIM folder entirely from my Android's Internal Storage helped, but it'd quickly corrupt again.
Frustrated, I asked a friend for help on what to do figuring he had more knowledge in Android devices then me. He suggested I tried another camera app, but I couldn't get Google Play to download anything to the internal storage or my SD card, despite clearly having enough space.
As a last resort, I tried updating through the official "Updates" app to see if that would help me, and it claimed there was a new ROM available. I tried that, but then suddenly it failed and now my tablet seems to bricked? I can now only get the "No command." screen to show up.
I've tried using the following options while on this screen:
- reboot system now - this takes me back to this menu after it shows a Lenovo screen twice, which makes me think it's having trouble booting into Android itself.
- Apply update from ADB/sdcard - Both did nothing for fairly good reason, but I checked these options out of curiosity.
- wipe data/factory reset - Tried these the very first time I got to this screen after a failed installation. It seemingly hasn't worked for me.
- wipe cache partition - Tried this a bit later, but got similar results.
- root integrity check - Scanned a bunch of .apk files, but then later threw up some errors after that was done and said the check failed.
So, in short, I'm stuck in this menu and I'm getting kind of frustrated/scared. Is there anything that I can do to save the tablet at this point? Is there something I did wrong that might have bricked it? I'm not terribly experienced with Android, so I'd love to hear some thoughts from others! I'll gladly take anyway to restore the tablet back to a point where it can actually boot into the OS, and I understand I'd lose some data doing any sort of clean install.
Thank you!
Click to expand...
Click to collapse
Theirs a Guide here on how to re flash your tablet back to stock
http://forum.xda-developers.com/android/general/guide-lenovo-tab-2-a10-70-root-t3279322
Quite a late reply, but thank you! That ended up working quite nicely! I upgraded my tablet from Lollipop to Kitkat too, which seems to be working a bit better app performance wise for me.
So about 4 days ago my S3, on which i installed 4.4.4 kitkat last summer, started rebooting, then the home app crashes a couple of times, i see a lot of crash popups which are either for the home app or androind system, then it reboots again, and usually after some reboots it works normally until i go into an app, then if i press the home button the home app would crash again and it would beigin rebooting(though once every app was crashing left and right). Yesterday however it didn't even make it to the home app part, it was stuck in the screen with the CM logo loading(bootloop?).
My question is if it's possible to fix it while also recovering all the data such as photos, music and app data. I have Clockworkmod recovery 6.0.4.6. So far i've tried pulling everything from adb, which either didn't work or worked but pulled folders and files i don't really need(tried pulling /storage/, all i got was an almost empty sdcard1 folder). I also tried this method [i can't post the link, google How to Recover data Using ADB recovery on Android techglen] but when i get to this line
mkdir emmc
my console gives me
~ # mkdir emmc
mkdir: can't create directory 'emmc': File exists
Try flashing twrp and mounting the data partition from twrp.
Yes, thanks, that worked and i was able to get most of the data i wanted, though not all, and did a factory reset. I also did a backup on an USB but when i tried to recover the data from there the progress bar was stuck at 0%.
My phone managed to boot normally, started downloading apps and then i got the android system crash again, along with the home app(trebutchet). So far it hasn't restarted by itself. I can still go to the app store and launch some of the apps from there. I managed to get 3 of the android system crash logs on pastebin: (again i can't post links) pastebin dot com /axBsYXfV, /6e3AiEyB /nwHxym9Y; should i make a new thread about this altogether?
Edit:Another crash log from when i tried to enter Apps from settings: tRbUX5h1
So crashes happen with stock and custom ROMs?
Hi Folks,
Yesterday, out of the blue, when I tried to open the generic camera application to take a photo of my kids, the application never loaded. Instead, a black screen was presented for a brief 5 seconds, followed by a message "can not connect to the camera service".
I tried two different camera apps, same error message. Okay, the phone needs restart apparently, his uptime is over a month or so, so I did it - Same thing, the camera app won't load, and the flashlight is not functioning.
Okay, with the use of Google, I've tried several methods, incl. delete the cache partition, clear face recognition data etc. - none of them worked.
The last resort was to perfrom a full wipe/erase on the phone's internal memory and so I did - Didn't worked either. After a full reset/wipe and configurations (Google/Apps/Email/Whatever) Same thing happened again, like it was a hardware problem or something.
One last thing came to mind, as a programmer, I know that the wipe operation removes only the '/data' mount point, not the '/system' mount point and my guess was that something went corrupted with the camera service/binaries.
I went to the recovery menu (power off -> hold both power button & volume up for a 10 seconds) and I ended up downloading the latest firmware (.193) again from Huawei servers.
After that, everything is back to normal, and i've learned that the wipe stage was unneccessary. Hell, I could have saved all my data and configuration by doing the same without wipe my device.
So, for any of you that stumble on the same situation - Just go to recovery and d/l fresh copy of the latest firmware from Huawei, It will take ages (took me about 2hrs to download and i'm on a 500/100 broadband) but eventually it will solve your problem without loss of data.
Hope I helped someone.
Eviatar