After using Ubuntu Touch for a little while, I decided to revert back to Android. I wiped the cache and dalvik cache, then began restoring (according to this guide). While doing that, TWRP hanged in the middle of restoring the system partition.
Any idea what to do?
Related
Been running CM10 and CWM 6.0.1.9 for ages with no issues and loving it. Yesterday morning (while on vacation) picked up the tab from charging and it was boot looping. Tried formatting cache and Dalvik cache as 1st attempt to fix and it reboots when trying to format Dalvik cache, regular Cache deletes just fine. Next reflashed CM10, but still boot loops. Started manually formatting partitions and when I get to Data it reboots.
So this sounds like Brick Bug, but shouldn't be since I'm on CM10/CWM6.0.1.9 and wasn't wiping when it occurred.
So questions for the braintrust...
1) Is there anything I can do to fix this while on vacation when the only PC I can access is Windows RT? Basically it needs to be something I can flash with CMW.
2) Assuming #1 isn't possible, my next step was to try flashing a stock rom when I get back home. Make sense or other thoughts?
Thanks,
Todd
try removing your ext sd card and boot it up. See if that helps. If not, I'd Odin the stock ROM
I have experienced this too. My fix was to delete data after reflashing CM10. I tried just clearing cache and dalvik like you did but it continued to boot loop. So I flashed CM10 because I was at school and it was all I have but it was still stuck and so I cleared data at CWM(Didn't flash CM10 again anymore). And yeah, it pretty much deleted everything, but I had a backup at home. It was fixed.
Graffiti Exploit said:
I have experienced this too. My fix was to delete data after reflashing CM10. I tried just clearing cache and dalvik like you did but it continued to boot loop. So I flashed CM10 because I was at school and it was all I have but it was still stuck and so I cleared data at CWM(Didn't flash CM10 again anymore). And yeah, it pretty much deleted everything, but I had a backup at home. It was fixed.
Click to expand...
Click to collapse
Thanks. Formatting data causes a reboot, so I think I'm stuck until I get back home and can use Odin.
Sent from my SCH-I535 using Tapatalk 2
[SOLVED] [Q] [P6210]Boot Looping and Corrupt Data Partition
For the sake of the archives...reflashing stock Honeycome fixed the partition problem and allowed me to re-install CM10.
I made a backup of my system using CWM recovery (v.5.5.0.4). It worked well. I restored my system several times using this backup I made.
But when I tried to increase the internal memory of my device using a method published by another XDA member, the backup I made didn't work..
the error was as follows:
checking md5 sums...
removing boot.img..
restoring boot.img..
restoring system...
error while restoring system....
I tried everything wiping my data/factory reset, wipe delvik cache, formatting system...
But the system just didn't restore..
I even tried the unbrick method of my device.. (i.e by restoring default ROM)
but the error remains the same..
I NEED HELP... ANY SUGGESTIONS..
Hey,
I've been running several Lollipop ROMs on my Nexus 5 in the past few months.
Today my Nova Launcher suddenly stopped working and froze instantly on restart, so I rebooted the phone.
It got stuck shortly before ending the boot, after several seconds of those colored dots whizzing around the screen they froze.
This issue was reproducible, so I first cleared the Cache and Dalvik Cache and rebooted, same problem. I then tried to Fix Permissions to no avail.
I then erased System, Data, Cache and Dalvik Cache and reflashed my current L-ROM of choice, OptiPop.
The device still doesn't boot, same problem.
Now TWRP is showing an error in red font whenever I try to wipe or flash.
The error I'm getting is:
Code:
unable to stat '/data/data/com.google.android.feedback/cache/com.android.opengl.shaders_cache'
Does anyone have an idea on how to fix this?
Try reflashing TWRP and then wiping. If it still doesn't work flash the factory images from fastboot using either the script or ( optimally ) by hand one by one.
Your filesystem might have gotten corrupted well enough for TWRP not to make heads or tails of it.
If that still doesn't work search the forum for how to format the needed partitions - and triple check what you are formatting.
I have a galaxy pro 12.2 rooted with CM12.1.
I tried to install a nightly but I couldnt wipe the cache. The console always says "can't mount cache"
I tried it 300 times and rebooted 300 times and it wouldn't mount.
After googling for a little bit, a majority of the pages I found said TWRP isnt stable with partitions and I was supposed to choose rm -f instead of formatting the partition or it corrupts the partition.
I'm assuming this is what happened to me because I just wiped the cache instead.
I wiped the cache and dalvik and system and did a factory reset and then I installed the nightly. It would boot but then it got stuck on the boot screen. So I tried to clear the cache again but I got the same error.
Then I reset my phone and wiped /system and data but not cache because I couldnt mount cache. And then I installed a stock rom. This rom also gets stuck on the boot screen. So now I have a tablet with a stock rom installed and what I'm assuming is a corrupt cache partition.
Also, I did back up before I installed the nightly. I have a working backup on my phone. It worked fine when I used it and it gave no errors when I backed it up and I got no errors when I restored it other than cant mount cache.
So I tried to boot into my working backup too. Still didnt work.
How do I fix this?
Hello everyone,
I'm trying to wipe the phone to do a clean installation.
So i reboot into twrp, choose wipe and i select dalvik cache, data, cache and system, i swipe to start the wipe and the progress shows that is wiping, but a few seconds after the phone reboots and goes back into the system.
What can i do?
Tried to flash a new rom without wiping data, got stuck in a bootloop and unable to go back into twrp.
Flashed again twrp, wiped everything and its working again.
Repair the data filesystem by going into Repair option. Fixed it for me
Hello, I will be assisting you in fixing this issue. first of all can I get tghe model version, twrp version and bootloader version?