About a year ago, my Nexus 7 (2012 wifi) started occasionally locking up, then (after a couple of minutes) rebooting and getting stuck on the boot animation. This would happen once every month or two. The only fix was to disconnect the battery, then reboot to recovery and do a restore. Sometimes I only needed to restore /system; sometimes I had to restore /data too. This continued after I moved from Kitkat to Lollipop.
The other night it happened again, and this time things are worse. I boot into TWRP and try to restore, but it only finds /system. It can't see /data or /cache.
I'd love to solve the underlying problem, but for now, any ideas on how to resurrect /data?
Related
Hello,
Firstly I want to apologies for creating new thread for a thing on which there already number of threads here. However when I was in this big trouble (at least it was for me) on Saturday evening I searched everything and couldn't find a working solution.
And I would like to request moderator or someone who has better knowledge of what did happen and how it got fixed can make it guide with his thoughts if there is a need to .
Let's start with my story. I unlocked bootloader first time and flashed CWM. While restarting I tried to wiped data as told in one of the tutorial and then I restarted. As long as I remember it said you would not be able to boot in CWM again and I said Yes. That's the time when it got stuck to X logo. I flashed CWM again and then tried to restart still nothing happened. I got further and flashed CM 10.1.2.
Then it got stuck to CM logo. I wiped cache, data, dalvik cache before and after; nothing helped. Then I managed to Power off phone and planned to go for sleep. I thought I have ruined my phone
This is how I fixed it:
At the last moment I thought to give it a last try before sleeping. I could not have went to sleep with that I thought Then I rebooted my Nexus 4 in CWM and went to 'Mount and Storage'. Mounted everything which were in unmount state. Formatted data. Went back a step then wiped data. And restarted. And there it got rebooted in CM 10.1.2 :highfive:
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
Hey, I'm in a very strange situation. The thing is I left my phone to charge overnight just like usual (made it reboot before doing so), when I woke up today I've noticed that it was bootlooping like crazy along with being very hot to the touch, like it was about to go off :x. Rebooting resulted in nothing, phone still bootloops. After entering TWRP and trying to look for my backup I also noticed that it shows "Internal storage (0mb)", what is totally weird considering that I've been doing absolutely no software modifications lately (I'm on Lineage). I also cannot mount data in "Mount" section, backing it up is also not an option.
I havent't tried yet to restore my full back up I've made around a month ago, is there any way I can revive the data partition?
Ok, since my backup is missing I've decided to reinstall the rom. But I can't format the Data partition at all . TWRP just goes "Failed to mount '/data' (Invalid argument), Unable to wipe /data). What should I do? Is the phone internal memory dead or what?
OK SOLVED. I entered erecovery and formatted my data. Now I reinstalled Lineage and everything works again... apart from photos of my doggy lost . Damn, I have completely no idea what caused that Data partition failure
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.