I keep getting cwm cache errors on my rooted rogers (att) sns, any ideas?
Related
Everytime i try to rrstore data after flashing a new rom or after a new nightly i always get hung up on the boot logo. I just went from baked to the new synergy 125 wiped data factory reset wiped cache and dalvik flashed rom rpm and modem and rebooted. All was fine as far as installing the rom. Went back to recovery wiped cache and dalvik again advance rrstore data and get hung. What am i doing wrong? Really annoying to have to redo everything everytime....and im a crack flasher
jessbowring said:
Everytime i try to rrstore data after flashing a new rom or after a new nightly i always get hung up on the boot logo. I just went from baked to the new synergy 125 wiped data factory reset wiped cache and dalvik flashed rom rpm and modem and rebooted. All was fine as far as installing the rom. Went back to recovery wiped cache and dalvik again advance rrstore data and get hung. What am i doing wrong? Really annoying to have to redo everything everytime....and im a crack flasher
Click to expand...
Click to collapse
You can't just restore the data that's the same thing as not factory resetting because all you're really doing is wrong the data and then putting it right back on.
You need to use something like titanium backup
Sent from my SCH-I535
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 flashed from stock w/root to cm10 and im stuck i have recovery still. clockwork mod to be exact. but everytime i flash any rom all it does is bootloop. i have tried six different roms to still be stuck in a bootloop. i wipe everything before flashing wait for it to get stuck in a bootloop pluck the battery then try to power it on and still loops, i have also tried wiping just cache, just delvik cache, and just data reset individually and even all at the same time. im in a perma loop on any rom even a stock debloated rom...... where did i go wrong. i have the latest cwm the latest and oldest roms
i've tried to wipe data/factory reset, wipe cache partition, wipe dalvik cahe, and mounts/format cache and data... but when i rebooted, its still boot looping... Help me!!:crying: tell me if there is another way to fix my Samsung galaxy tab 2 10.1... i've rooted this device.. do i have to unroot it? please help. thanks
oh yes, i've tried to format sd card, and it didnt working.. still boot looping
wiping data, cache, dalvik cache or sdcard won't help fix a bootloop!
You need to flash a custom/stock rom using recovery or odin mode in your tab.
samsungrockz said:
wiping data, cache, dalvik cache or sdcard won't help fix a bootloop!
You need to flash a custom/stock rom using recovery or odin mode in your tab.
Click to expand...
Click to collapse
thanks for the reply.. but can you give me the instructions? or the link?
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?