So I have been having issues with random hangs during boot and subsequent filesystem corruption. I say filesystem corruption because TWRP prompts me for a password because it thinks the drive is encrypted and certain partitions/directories fail to be restored to with the dalvik cache failing to be wiped seeming to be a consistent.
So in a nutshell rebooting my phone without first going into TWRP and performing a cache/dalvik wipe inevitably causes filesystem corruption. I discovered this pattern last night when flashing a zip, booting the phone and setting things up, rebooting directly into recovery and making a backup and doing nothing else, rebooting, noticing the phone hang after a few minutes of the "Samsung Galaxy S4" splash screen, then rebooting in recovery being prompted for a password, then formatting data, then restoring the backup I had just made, and having the phone bootup successfully after that. Since then a bit of trial and error has only demonstrated to me that without wiping the cache/dalvik some filesystem gets corrupted rendering the phone unable to boot.
So I am curious if anybody has any idea what might cause this except maybe a bad internal SD card. I am pretty tech savvy but I do not have nearly as much experience troubleshooting these phones as many of you guys.
I have tried everything short of restoring to stock which I am going to attempt later if nobody is able to shed some light on this issue.
Thank you.
Try re-loading recovery via Odin.
Check out this thread close to your issue
I am attempting this now. I did not realize that you meant stock recovery when I first wrote this post.
czahrien said:
So I have been having issues with random hangs during boot and subsequent filesystem corruption. I say filesystem corruption because TWRP prompts me for a password because it thinks the drive is encrypted and certain partitions/directories fail to be restored to with the dalvik cache failing to be wiped seeming to be a consistent.
So in a nutshell rebooting my phone without first going into TWRP and performing a cache/dalvik wipe inevitably causes filesystem corruption. I discovered this pattern last night when flashing a zip, booting the phone and setting things up, rebooting directly into recovery and making a backup and doing nothing else, rebooting, noticing the phone hang after a few minutes of the "Samsung Galaxy S4" splash screen, then rebooting in recovery being prompted for a password, then formatting data, then restoring the backup I had just made, and having the phone bootup successfully after that. Since then a bit of trial and error has only demonstrated to me that without wiping the cache/dalvik some filesystem gets corrupted rendering the phone unable to boot.
So I am curious if anybody has any idea what might cause this except maybe a bad internal SD card. I am pretty tech savvy but I do not have nearly as much experience troubleshooting these phones as many of you guys.
I have tried everything short of restoring to stock which I am going to attempt later if nobody is able to shed some light on this issue.
Thank you.
Click to expand...
Click to collapse
I'm having this same issue on my gf's Kindle Fire I w/CM10.2, but without the prompt for password. So annoying! Did you ever fix it? - http://forum.xda-developers.com/showthread.php?t=2563695
Related
The title says it: My TPT is bootlooping and when I try to wipe the cahce/Dalvik-cache in recovery, it just won't finish.
I'm running ICS (OTA3), but the same thing has happened to me before with Honeycomb.
I don't want to wipe data! Any ideas?
You qualify for a new motherboard if you want it.
But that would not preserve my data
My understanding, and I could be wrong, is that once you start boot looping you need to have made great backups prior to the issue because all you can do is send it in for repair. Hopefully you have such backups if you have root.
Not good news so I hope I'm wrong. Wishing you luck.
I pulled some of the data via adb and then did a factory reset (in recovery). Now it boots again.
I just hope it won't happen again. This was the second time already: Once it started bootlooping in Honeycomb and now ICS. It just came out of nowhere (it booted up fine many times before).
Excellent news. Didn't think you could pull anything with adb while bootlooping. Should have tried that straight away.
I still could enter the recovery mode. Strangely, wiping cahe/dalvik cache alone didn't work (it wouldn't wipe), but wiping everything (which also includes dalvik cache) worked...
I still lost some important data, but at least my tablet works again. I just hope it won't start bootlooping again... but I'll definitely make sure to have an automatic backup solution set up just in case.
Good show. At least you're not bootlooping. Too bad about the data.
So recently I formatted my internal storage mainly to start fresh and clear out all the crapi didn't want, but since then whenever I reboot three phone gets stuck at the splash screen and will not function again until I pull the battery, reboot recovery, format data/media again, and flash something clean. When this happens and I reboot into recovery it prompts me to enter a password as if the data is encrypted. When I open the command line to see what it says it reads E: unable to decrypt storage... Or something to that effect. In on the most updated tarp and I've tried several Roms to see if there was something going wrong there but no. I would hardly consider myself a noob, and I have exhausted all other options with the exception of back to 100% stock and start from scratch unless anyone has any input... I can't even reboot without wiping my internal storage, please help!
janob09 said:
So recently I formatted my internal storage mainly to start fresh and clear out all the crapi didn't want, but since then whenever I reboot three phone gets stuck at the splash screen and will not function again until I pull the battery, reboot recovery, format data/media again, and flash something clean. When this happens and I reboot into recovery it prompts me to enter a password as if the data is encrypted. When I open the command line to see what it says it reads E: unable to decrypt storage... Or something to that effect. In on the most updated tarp and I've tried several Roms to see if there was something going wrong there but no. I would hardly consider myself a noob, and I have exhausted all other options with the exception of back to 100% stock and start from scratch unless anyone has any input... I can't even reboot without wiping my internal storage, please help!
Click to expand...
Click to collapse
i had this problem as well, and only thing i found to fix it was to completly odin back to stock, since then ive had no problems.
That's what I figured I might have to do.
Much appreciated
Hi, thanks for looking at this.
I have a Galaxy S 4 Google Edition phone. I rooted it, and I have TWRP 2.5.0.2 running on it. I have backed up my system a few times.
I tried flashing a rom of cyanogenmod for the first time today, cm-10.1-20130801-NIGHTLY-jfltexx.zip (http://get.cm/get/jenkins/36550/cm-10.1-20130801-NIGHTLY-jfltexx.zip)
I wasn't having any luck with the boot, so I turned to this thread, http://forum.xda-developers.com/showthread.php?t=2370101, which utilized a modified updater-script. That still was giving me no dice, so I tried editing the updater-script myself. Cyanogenmod boot-up appears! . . . and then it just keeps spinning. I turn off phone, boot into custom recovery, factory reset phone, try again. Same deal, try it again. Factory reset again, then I try restoring my device so that I can try again with different parameters. TWRP says that the restore is successful. This turns out to be not true, however, as when I reboot, the Google logo shows up, vanishes, and then nothing happens.
This is where I'm stuck. I can boot into TWRP, but that's it. Everytime I try to wipe dalvik or data, it fails. Restores supposedly work, but they don't, no matter if I'm restoring just system, or system data and cache. I have tried mounting my sd card so that I might load another rom, but even though TWRP says "USB Storage Mounted", nothing happens.
I'm completely at a loss here. I simply can't afford to brick a $700 phone. This is crazy.
PLEASE HELP
Vivisec said:
Hi, thanks for looking at this.
I have a Galaxy S 4 Google Edition phone. I rooted it, and I have TWRP 2.5.0.2 running on it. I have backed up my system a few times.
I tried flashing a rom of cyanogenmod for the first time today, cm-10.1-20130801-NIGHTLY-jfltexx.zip (http://get.cm/get/jenkins/36550/cm-10.1-20130801-NIGHTLY-jfltexx.zip)
I wasn't having any luck with the boot, so I turned to this thread, http://forum.xda-developers.com/showthread.php?t=2370101, which utilized a modified updater-script. That still was giving me no dice, so I tried editing the updater-script myself. Cyanogenmod boot-up appears! . . . and then it just keeps spinning. I turn off phone, boot into custom recovery, factory reset phone, try again. Same deal, try it again. Factory reset again, then I try restoring my device so that I can try again with different parameters. TWRP says that the restore is successful. This turns out to be not true, however, as when I reboot, the Google logo shows up, vanishes, and then nothing happens.
This is where I'm stuck. I can boot into TWRP, but that's it. Everytime I try to wipe dalvik or data, it fails. Restores supposedly work, but they don't, no matter if I'm restoring just system, or system data and cache. I have tried mounting my sd card so that I might load another rom, but even though TWRP says "USB Storage Mounted", nothing happens.
I'm completely at a loss here. I simply can't afford to brick a $700 phone. This is crazy.
PLEASE HELP
Click to expand...
Click to collapse
UPDATE: THANK YOU TO THIS THREAD: http://forum.xda-developers.com/showthread.php?t=2388504
PROBLEM FIXED!
Good morning.
After almost 3 years with no problems with a XT907, I have again an issue with it (this time, my father's one). Again, I come to you requesting help.
It all started with all apps crashing over and over. With an old XT907 I have for emergencies, the common fix method is flashing VZW_XT907_4.4.2-KDA20.62-15.1_1FF.xml.zip with RSD Lite v6.1.5 and all solved.
I tried that method with my father unit, and when it started again, all process were still crashing. I thought it was still nothing (just a harder issue), and tried flashing VZW_XT907_4.4.2-KDA20.62-15.1_CFC_1FF_SVC.xml.zip, just deleting all his data, to fix it.
When the process ended, it turned on and it had still the same problem. In this point, I got worried the /system and /data partitions got locked
I re-started, went to stock Recovery, and wiped system and cache. Then, went to Fastboot a third time and tried again flashing VZW_XT907_4.4.2-KDA20.62-15.1_CFC_1FF_SVC.xml.zip. Guess what? Still the same problem
The phone turns on, but ALL apps keep crashing over and over. I can't even take an screenshot, as it immediately reboots.
Someone know what happened with it? And... how to fix this issue?
To make things worse
Fastbook Locked
No Root
Last 4.4.2 stock ROM
by twrp try make Wipe Data Or Repair File System, if not done mybe your internal memory Currpted
I had LineageOS 17.1 + TWRP running fine on my Galaxy S5 klte, then the glue on the top part of the screen came away and disconnected the screen while the phone was on. After that it would only boot to part way through the Lineage animation, dimming to low brightness in the middle of it and rebooting into recovery.
Wiping the cache in recovery did nothing, but wiping the data partition fixed it, so I guess the data partition became corrupted. Restoring the data partition from an old TWRP backup of the same install works too. The hardware and ROM seem fine.
I made a full backup of the bad install, so is there anything I could do to try to get that working again or diagnosing what happens at boot? Any cache/settings files I could try deleting from the image if that's possible? I did find stuff about getting the last kmsg output but that doesn't seem to work with this phone/Android build. I wish I'd though about running fsck on the partition before I wiped it. No idea if the screen thing is a red herring or not.