Hi All,
I have LineageOS running on a GS5 (G900I) and while it runs beautifully, every 1-2 weeks I have a hang that I cannot recover from - Even after reboot the phone hangs immediately - I can swipe across screens in Trebuchet but no widgets will run and the phone will hang if I try to open any app.
The *only* way I have been able to recover is to perform a restore of my /data partition from a TWRP backup. I've tried wiping cache, dalvik-cache and restoring the /system partition, but this does not help. I've upgraded LineageOS a couple of times to the latest. Now I seem to have to make a backup of /data every day or two, as I never know when this problem will strike again.
My /data partition is encrypted. Filesystem is ext4.
So I have really 2 questions:
1. Can anyone suggest the cause? I can't find any mention of this as a common issue.
2. How can I troubleshoot this? I can use "adb" when booted into TWRP recovery but it seems I cannot use this when the phone is booted without enabling USB Debugging in settings first - but when the hang has happened I cannot launch Settings to enable USB Debugging, so there appears to be no way to see any logs.
Any help would be appreciated...!
Related
Hey guys, got a strange problem here. I'm running MIUI-XJ 2.3.30 A2SD.
Had 8 apps to update via Google Play and 31mb internal left (over 600mb on sd-ext, too). In the middle of updating the apps I've got a Google Play crash followed by few other fc's, phone said my internal memory is too low to operate and such - so I tried the most obvious fix, which is of course rebooting the phone.
That was a mistake, apparently. Phone will not boot anymore - goes through the bootscreen and gets stuck on the yellow MIUI splash. It's not a bootloop, the phone just freezes and the only thing I can do is battery removal. Tried booting it up with no sd card as well, nothing seems to help though.
Is there anything I can do except full wipe via recovery? I had some important sms and spent quite a bit of time customizing the desktop, I'm not to keen on doing that again.
Is it possible to delete some apps via adb or something like that? Or is there a point in trying to install the rom again on top of my system?
Thanks in advance, help really appreciated!
Try clearing dalvik cache and cache from recovery and then boot. Thereafter clear some space or change your a2sd scheme.
Thanks for the answer! Makes me feel silly I did not think of that myself lol, sounds like an obvious solution.
Problem is, it still does not seem to help though - wiped /cache and dalvik-cache on data, sd-ext and system - still nothing, same problem persists. Stuck at MIUI bootanimation.
Any other ideas? I'm really kind of desperate to recover the data.
- Take a nandroid backup first. So you can start over if need be.
Some things to try
- Only flash ROM and see if it helps.
- Wipe data. Flash ROM fresh. Install Titanium Backup. With TB locate nandroid on sdcard and try to extract your data. Maybe restoring the launcher and messaging will do the trick. Not sure . Try. You can always start over.
- Fix permissions in recovery
There's an app called AROMA Filemanager that can be started from recovery and allows you to modify all phone partitions, all you need is to mount them before starting the app. Here it is:
http://forum.xda-developers.com/showthread.php?p=25911276
Tried flashing the ROM again on top of my system - no effect whatsoever, still gets stuck at bootanimation. Also, tried the permission fix as well as the RMD recovery "apk uid mismatches" fix. Still nothing.
Going to give the AROMA a try, having some problems right now though - using RMD recovery, no touch support. Trying to flash 4ext touch from fastboot somehow!
Thank you. Will keep you updated.
UPDATE//
Managed to get the AROMA up and running, deleted few apps from /data/apps, nothing to delete from /system really. /cache is cleared, so are all 3 dalvik-cache folders.
System still does not want to start.
Any ideas what might have happened? Seems like I'm running out of options and will have to do a clear install, after all.
You probably damaged some important system files so tho phone can't load system. The best solution is to restore some nand backup if you have, or to do a full wipe and start from scratch.
Sent from my HTC Desire using Flashes and Thunders
If that was the case, reflashing the ROM on top of my current system should fix the problem, while it didn't - right? Also, I find it hard to believe that "important system files" could have been damaged during routine Google Play apps update...
Than a full wipe and fresh install is inevitable...
Sent from my HTC Desire using Flashes and Thunders
Hey fellas,
A while ago I installed Cyanogenmod over my stock Samsung ROM (Rogers) using the Cyanogenmod Installer.
Then a few weeks ago, through settings -> about (or information), I updated to CM11 with no issue.
Today, I was prompted to update again (not sure what version it was, but I believe I had the update check frequency to 1 week, and today was the first time I got this prompt in a while).
The phone seemed to update fine, but after reboot, it is stuck on the splash screen (black background, says Samsung Galaxy S III, and has the cyanogenmod guy/logo at the bottom). This is the splash screen that pops up (usually only for a second) before the boot screen with the rotating circle.
From the search I've done, I was only able to find people that are stuck on the boot screen (with the circle), rather than the splash screen. And for those people the only solutions I was able to find involved factory reset. Before I attempt any of that, I was wondering if there was anything else I could try (other than wiping cache). Idiot that I am, I haven't backed my phone up since I first installed CM, and I have a number of very important contacts and texts that I really can't lose.
Failing that, is there a way to back up such information before wiping user data? Perhaps after booting into recovery?
Thanks in advance for any help whatsoever.
With regards to backing up,
If I boot into recovery, can I back up user data like contacts and SMS through ClockworkMod Recovery? If so, will it work even though the phone doesn't seem to be able to boot?
Under Backup and Restore, I see various options, I think storage/sdcard1 is the external SD card.
If I choose backup to /storage/sdcard1, it starts backing up my data, but exactly what will be backed up? Also, I don't have a ton of space in my SD card, would it be possible to select what to back up and what to skip?
Finally, under Mounts and Storage, there is a mount USB storage option. I assumed going into it will allow my computer (connected by USB) to detect my SD Card, and I can delete stuff off of it, but my computer can't detect the phone/sdcard either as media device or storage. Am I doing something wrong, or is this not what this function is supposed to do?
Hey all together,
I have an issue with the phone encryption of my GT-I9195.
I have a CWM Recovery v6.0.5.0 installed.
I downloaded the nightly 20150408 to upgrade vom CM11 to CM12.
My approach:
- I formatted the sd1 (external-card)
- I factory reset my phone
- I downloaded with the phone the nightly and moved it to sd1
- I downloaded gapps-ip-20141212 and moved it to sd1
- I deleted all folders on sd1 (android folder etc.)
In CWM Recovery
- I wiped the data / factory reset
- I wiped the cache partition
- under "mounts and storage" I formated all folders incl. the /data AND /data/media folders
- I wiped the dalvig cache
- installed the nightly zip
- installed the gapps zip (doesnt matter if I install the gapps or not, behavior of encryption is the same)
After booting into CM12, I configure some basics like Screen-lock, etc. and tried to enable the phone encryption.
After two screens, the message shows up, that the phone will reboot a couple times during encryption and it may take a couple hours.
If I confirm all screens, the green android robot shows up, and nothing happens. Not after a few seconds, not after an hour. The telephon shoutdown menu still works if I press the power button.
I wiped all caches in CMW a couple times, I reinstalled CM12 without gapps,.. everytime the same situation.
I couldnt find some information if the encryption should work or not by design. So I decided to go back to CM11 to encrpyt the phone and use it for business purposes.
I downloaded the cm11 20141112-snapshot and proceed the same way I did before with the CM12 clean install.
When I try to enable the encryption in CM11, it shows the same behavior like in CH12.
I know that I had some troubles to enable encryption when I installed CH11 the first time last year, but I dont know anymore what I did to make it works.
Do you have any advices for me how its possible to use the phone encryption?
Beside the fact, that its not possible to use business mails on a decrypted phone (exchange policy), I dont feel comfortable to have it not encrypted.
Thanks for you answers in advance.
Best regards,
Semo
Try with cwm 6.0.5.1
http://forum.xda-developers.com/showthread.php?t=2364980
Hi everyone,
I've got a Galaxy Nexus in use since approx. 2 years and update it to the latest CM from time to time. I also flashed Ziyan's beta build (08/06),
but honestly, I dont't think that’s the crux of the matter.
Let me begin with the error pattern:
One day, my Nexus was not in use and only lay on the table, it crashed an rebooted. That happened occasionally, so it seemed like nothing to worry.
Unfortunately the system kept on crashing on every attempt to boot after this or crashed shortly after finishing boot.
This repeated over several hours.
Once in a while, the system managed to stay alive for a few minutes and I was able to browse the settings for example. Doing so, I noticed that it responded normally for about 5 seconds and then froze for 5 seconds alternatingly.
I then tried to flash a backup or rather the latest rom again.
Then it became awkward:
In the beginning I was unable to aquire writing permissions (rw) and only had reading permissions (ro) on my /sdcard. Even adb remount didn't change this.
An attempt to fix permissions in TWRP recovery broke with an error.
I couldn't even access the sideload due to missing write permissions.
Surprisingly, I was able to adb push the rom to /cache partition since I still had rw permissions on /cache and /system and therefore successfully flashed the rom subsequently.
When I checked my permissions again, I regained rw permissions on all partitions.
Trying to reboot my system, it kept on crashing like before, which led me to format the internal memory completely.
According to TWRP the whole memory was deleted completely and I adb pushed an older rom (CM 11) and flashed it.
To my astonishment, I found my phone boot the old rom again, all data was restored and it still crashed like nothing happened to the memory.
I then tried to delete all files manually and flashed the stock rom, even unrooted, all with the same outcome.
After every attempt to change something, Ziyans rom remained on the phone, also the /sdcard data was still there.
What I found noteworthy was the recovery telling me, all the operations completed succesfully everytime and until I restarted the phone, it indeed showed no files remaining after formatting (though, I couldn't change the filesystem).
To put it all in a nutshell:
Memory delete, format or overwrite doesn't work any longer
I am totally out of options and would appreciate suggestions =)
Greetings,
Kosmo$
Yes it is. A way to verify this is to lock the bootloader. If it is unlocked upon rebooting your EMMC is corrupt..
After heavy reading and trying to sort things out by myself and before giving up on the device, just to give it a chance:
after upgrading to the latest build of Lineage OS for MicroG (lineage-14.1-20190215-microG-suzuran) i encrypted the phone, simple-hearted.
result:
starts into TWRP 3.1.1 but can't decrypt data
No more cell service, which i couldn't solve
After repeated wipe - advanced wipe - Format data followed by reinstallation each i can boot into Lineage, with adb and cell service working but the install is unstable:
-larger uploads like my TWRP backup (~2GB) result in ads connection loss, 'system read only' which can be solved by restarting into recovery, but backup upload is not possible although more than 20GB free space seem to be available (can it be that memory space encrypted before is still not usable, despite formatting all partitions?).
-Trebuchet app crashes
-Phone won't reboot, hangs with startup animation
Last two issues can be solved by wiping the phone and reinstallation, until reoccurring.
Do i have to trash the device or is there something else i could try?
Update:
SOLVED: TWRP Wipe - Advanced Wipe - select Data - Repair Or Change File System - Repair File System (Mount Point /data) (Many thanks: https://android.stackexchange.com/a/176124)
As far as i understand (as stated here https://forum.xda-developers.com/z5-compact/development/twrp-twrp-3-2-1-z5-compact-t3748952) i need a different kernel and a different TWRP build for Encryption and OTA Updates working on the same system, but which ones and how to install is a different thread.