I have been running CM7 RC1 for a few weeks now with no issues. I have no special apps or anything besides the basics (titanium backup, setcpu, and CWM).
I ran into this issue about a week ago when I tried to flash my stock rom when I was running Gingervillian 1.5. I was getting:
E: Can't open cache/recovery/command
when I tried to flash back from stock Froyo ROM to Gingervillian and I figured it was because I used CWM 3.x.x and not CWM 2.x.x to flash from a Gingerbread ROM to a Froyo ROM...
However, since then, I installed a clean CM 7 RC1 ROM and have been fine. Then all of a sudden today, the phone locked up and I had to pull the battery and then it ran fine for a few hours and did it again. So, when I got home, I flashed a recovery from 2 days ago that was running fine and I got the cache error and then bootloops again.
WTF is going on?
The ONLY thing that changed between my recovery image from Mar 11 to now was my wife downloaded Soduko from the market, and I made a SetCPU profile for when the phone is charging. Other than that, nothing changed.
I was able to get it working...I am not sure what I did that made it work but this is what I did.
Format /cache (originally gave me the cache error)
Format /data (originally gave me the cache error as well)
Format /davlik cache
Reboot recovery
Downloaded another CWM 3.0.0.5 .img file and copied it to sd card (was going to try to flash new CWM to see if it would help).
Then I tried to Format /data again and it worked, so I tried format /cache and it worked.
Then I tried my recovery and it worked as well. So, it is working, but I think I may flash CMW 2.x.x and go back to CM 6.1 since it is stable. I know everyone says CM 7 RC1 is pretty stable as well, and I reallllly don't want to go back to Froyo...I don't want to keep having problems like this.
happened again tonight. Phone froze after running completely fine. I pull battery and try to reboot and get stuck at HTC screen. Go into recovery and get the same cache errors.
I tried formating data, cache and davlik cache and nothing is working. Is there something I am doing wrong, or something I can do to keep this from happening?
You need Clockwork mod recovery app from market. 3.0.0.5 is official and goes between froyo n cm7 without problems. Try that
meXdroid Ghost Chilli
I have the latest CWM and I wasn't trying to flash a new ROM tonight, or last time either. The phone just froze and then started with the cache errors.
...anyone?
Related
My phone won't boot more than 3 seconds into the animation. I use CM6.0 stable. I had flashed the PS3Freedom zip in order to Jailbreak my PS3, restored to CM6 with no problem, and then when I did it again I couldn't boot into my RESTORED CM6 ROM. I restored few old nandroids that I didn't like till I got to my rooted Sense 2.2 one, then I deleted a few nandroids from when I was flashing nightlies to make room to download BakedSnacks 1.7 through ROM Manager. Everything was working fine, but then I tried to get CM6 running again and I am still not able to boot into it. What's going on here?
To the best of my knowledge I've been wiping the Data/Cache as often as necessary, even the Dalvik Cache a few separate times trying to get this to work.
blakerboy777 said:
My phone won't boot more than 3 seconds into the animation. I use CM6.0 stable. I had flashed the PS3Freedom zip in order to Jailbreak my PS3, restored to CM6 with no problem, and then when I did it again I couldn't boot into my RESTORED CM6 ROM. I restored few old nandroids that I didn't like till I got to my rooted Sense 2.2 one, then I deleted a few nandroids from when I was flashing nightlies to make room to download BakedSnacks 1.7 through ROM Manager. Everything was working fine, but then I tried to get CM6 running again and I am still not able to boot into it. What's going on here?
To the best of my knowledge I've been wiping the Data/Cache as often as necessary, even the Dalvik Cache a few separate times trying to get this to work.
Click to expand...
Click to collapse
what recovery are you using?
in clock work, try wiping to factory, wipe cache partition, wipe datavik then flash from zip to whatever rom.
in RA do the same but make sure your rom is on the root of your sd.
i had the same issue and did that and it worked fine.
Ok, I just finished formatting one of my memory cards and installed a new rom. It booted fine. I went back into recovery to wipe the cache and dalvik and when I go to reboot it stays stuck at the white HTC screen. This has happened with multiple roms. After that I went back into recovery to try to reflash the rom and this is when the errors from last night come back:
Gets all the way to formatting cache, then system, then copying files....
E:Failure at line 6:
Copy_dir Package: data DATA:
Installation aborted.
This is the problem I've been running into before I formatted the card. This is a brand new Evo, with the 2.02 boot, version 4.
If I wipe data
What does this sound like? Something go bad in the rooting process? Maybe something to do with Amon recovery? Maybe try clockwork or what?
I rebooted into recovery and wiped all 3 then went to install the rom on the card and it installed this time. I don't remember my last phone working anything like this at all... not sure what gives.
Jbroad572 said:
Ok, I just finished formatting one of my memory cards and installed a new rom. It booted fine. I went back into recovery to wipe the cache and dalvik and when I go to reboot it stays stuck at the white HTC screen. This has happened with multiple roms. After that I went back into recovery to try to reflash the rom and this is when the errors from last night come back:
Gets all the way to formatting cache, then system, then copying files....
E:Failure at line 6:
Copy_dir Package: data DATA:
Installation aborted.
This is the problem I've been running into before I formatted the card. This is a brand new Evo, with the 2.02 boot, version 4.
If I wipe data
What does this sound like? Something go bad in the rooting process? Maybe something to do with Amon recovery? Maybe try clockwork or what?
Click to expand...
Click to collapse
Ive seen this also with a new phone that has the older hBoot, just without the errors. Couldn't get it to take a custom ROM but you could flash kernels with no problem.
Have you tried running the RUU and then reflashing the recovery?
xHausx said:
Ive seen this also with a new phone that has the older hBoot, just without the errors. Couldn't get it to take a custom ROM but you could flash kernels with no problem.
Have you tried running the RUU and then reflashing the recovery?
Click to expand...
Click to collapse
I think it might be something with the recovery, because I tried to flash Clockwork via rom manager and it said it took, but Amon is still there. I'm going to flash the pc36 ruu that was originally used to see if it has any affect.
Solved.. thanks for the help
I am getting the exact same situtation going on. I hope I didnt break my phone. I really LOVE this damn thing. hahah Please help. What are the steps I need to do to get my phone working again.
Hey, for some reason I just started having huge problems with clockworkmod recovery within the last few hours. I've had my nexus for a month just about and have been unlocked, rooted , and flashing roms since day one ( I've been flashing my phones for about two years now, just so you know I'm not a noob) and before tonight haven't had one issue. I was running aokp build 13 , and decided to check out the progress on cm9 kang. So I flashed it with no problem , rebooted, set up the rom, and then I went to flash Lean kernel 1.3.0 ( which should work for all 4.0.3 roms) and I ended up getting stuck at the "Google" boot screen, so I booted back into recovery and figured I would just restore my backup of aokp 13.... so I wiped data, cache, and dalvik and proceeded with the restore. The restore got to restoring data , and I got an error saying "data cannot be restored" or something like that. So I figured it was a fluke of some kind , so I tried again... still the same thing. So I tried another one of my backups , still the same thing . I can't figure out why none of my backups will install. So I had to download the stock recovery image and run the bat file just to get the phone working again , and everything was fine . I was back on android 4.0.1 and unrooted. So I rooted again and flashed recovery all over. Made a backup of the stock rom, and proceeded to flash aokp again and the install went smooth, but now any ics gapps I use end up in market force closes, so I figured " I don't feel like dealing with this again lol" , so I booted into recovery and attempted to restore my backup of the stock rom..... again it failed.....
I am beyond confused now what is going on with my recovery, especially since I started fresh a couple hours ago. If anyone has any idea what is going on or if anyone has some input it would be much appreciated. I'm going crazy over here
Edit: I also forgot to add that it seems recovery isn't wiping everything fully. As in I'll wipe data, cache , and dalvik , then install the same rom I was using ( the actual update.zip) , and everything will still be the same when I reboot , meaning all my apps are still there and my docks are still set up the same way like it wasn't wiped at all. Very weird , I've never seen that happen before.
Sent from my Galaxy Nexus using XDA App
So, im having a problem now. I used boot manager then i installed a cm7 nightly, i restarted and went back to deck ics 5, then everything was fine so i rebooted. it was looping. so i wiped everything and i just decided to install deck ics 6 and it reboots and goes to the recovery, Im stuck and I need some help, after the flash and it goes to recovery, i checked the usb mode toggle and theres nothing there, so im guessing its not installing at all
Just do it the normal way. Wipe everything in recovery (With Amon Ra) as has been detailed a billion times on here, then flash the ROM you want
^ Yeah I agree with that person. I was using CWM until yesterday when it wasn't wiping the Dalvik cache properly. I now use the alternative that he said, use it lol
I have a T-Mobile SGH-T989 (Galaxy S2), and for a while I had an ICS darkside ROM on it with CWM 5.0.2.4. This evening, though, I decided to upgrade to an Android KitKat ROM (Beanstalk). I first upgraded CWM to the latest version, and then flashed the ROM. Everything seems to have flashed correctly, and I get the Beanstalk splashscreen, but it never seems to go any further than that. It's hung (for around 30mins) on the Beanstalk splash screen with the beanstalk and rain.
When I go into CWM, I can re-flash just fine, but when I try to do a full wipe or a cache wipe, it also gets hung (I eventually rebooted after about a 10 minute cache wipe attempt). It says that it can't open /cache/recovery/last_install, and that the cache file system is read-only. I also attempted to use the super wipe/cache wipe tools here: http://forum.xda-developers.com/showthread.php?t=2235141&nocache=1 but they also hung.
I'm wondering what the best course of action is at this point? I have a full backup, but since it was made with the previous version of CWM, it also appears to not be working.
Thanks,
~j
jwir3 said:
I have a T-Mobile SGH-T989 (Galaxy S2), and for a while I had an ICS darkside ROM on it with CWM 5.0.2.4. This evening, though, I decided to upgrade to an Android KitKat ROM (Beanstalk). I first upgraded CWM to the latest version, and then flashed the ROM. Everything seems to have flashed correctly, and I get the Beanstalk splashscreen, but it never seems to go any further than that. It's hung (for around 30mins) on the Beanstalk splash screen with the beanstalk and rain.
When I go into CWM, I can re-flash just fine, but when I try to do a full wipe or a cache wipe, it also gets hung (I eventually rebooted after about a 10 minute cache wipe attempt). It says that it can't open /cache/recovery/last_install, and that the cache file system is read-only. I also attempted to use the super wipe/cache wipe tools here: http://forum.xda-developers.com/showthread.php?t=2235141&nocache=1 but they also hung.
I'm wondering what the best course of action is at this point? I have a full backup, but since it was made with the previous version of CWM, it also appears to not be working.
Thanks,
~j
Click to expand...
Click to collapse
When all fails always use ODIN, if you know what you're doing. IDK which ROMs here are flashable via ODIN but use any you can find in the dev section in which somebody has uploaded a flashable .tar version (usually it will be rooted stock). If that doesn't save you, you have big trouble.
Also you should still be able to restore backups between different CWM versions, so yeah there is potentially something wrong with your phone.