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.
Related
I do not know the reason for the following Situation.
I once had Fresh 3.2 installed, for no reason the phone one day stayed at the boot screen after a restart.
I tried Installing CYANOGEn but never could o I installed NONSENSE, this is all usong RA recovery.
I tried installing the latest Fresh and Myns and no luck, I decided to go Closckwork, I was finally able to istall the new FRESH. YAY SO HAPPY... NOT I cant install anythig from the market or any apks. it reboots to bootscreen saying FRESHHHHH. AHHHHH, so I tryed reinstallyng, nothing then tried Myns, wont install in closckwork.
AHHH
then I go and reinstall RAs recovery, Im able to install Myn Ota supersonic, the rom runs perfectly I can install apps on the market, it wont reboot. so Now I install Myns warm twopointtwo. and yess it installs YAY, lets go install an app.. NOOOOOOO it restarts phone to boot screen.
WHY?????????????????
is there a problem witth my phone?
Did you wipe before flashing? If you dont, it might cause the problem you are describing.
i heard psoting in the right forum helps fixs problems too (see Q&A)
You're not wiping. If you are, you're doing it wrong. If you wipe wrong, it leaves sh*t behind. Same rule applies to the men's room.
Sent cuz I like boobies
Not sure if you are doing complete wipes and disregard my answer if you are, but I used Amon RA and wipe EVERYTHING twice whenever I install a new ROM or do a nandroid restore. I wipe data, cache, dalvik cache, ext, battery, and rotation twice. I have never had a problem flashing ROMs. It might be overkill, but it works.
I have done everything
I have Wiped EVERYTHING even changed the SD card,
now Im able to Flash Fresh and Warms rom but
now I cant install any apps from the market or SD
everytime I try to install something it reboots.
Edit: Still not fixed. Any help would be appreciated.
Hi all. I'm currently using MIUI and want to swith to CM7 for 2.3 and 4G. I've been on the Cyanogen forums but to no avail. I have so far tried the following...
1. Flash from MIUI to CM7 #8 through rommanager with wipe.
2. Flash from MIUI to CM7 nightly 8, 12, 17 through Clockwork with full data and cache wipe.
3. Flash from MIUI to CM6 to CM7 through clockwork w/ full wipe.
4. Flash Amons recovery in rommanager and flash from MIUI to CM7 nightly 17 w/ full wipe.
I am currently at a loss. Please throw any suggestions my way.
- Nick
What exactly are you wiping when you say full wipe?
Try flashing calkulin's format_all.zip, then cyanogenmod, then gapps, all within one recovery session (no rebooting/restarting between flashing each one)
Sent from my hand with XDA Premium installed
Try a full wipe, cache, dalvik, and data. Then reflash the rom.
By full wipe I mean data/factory reset, then wipe cache, then dalvik.
Trying Calkulin now. On Cyanogen forum someone suggested a different kernel. I've never flashed only just a kernel. Would I use the same method as flashing other zips?
That's correct, just wipe dalvik and cache before doing so.
So, I did the calculkin format all however I also did something different this time. I started to notice that it would only boot loop after I did a Titanium batch restore. I would normally restore all apps and system data. This time I only restored apps instead of system data and I can reboot just fine... for now.
Would this cause a problem? Restoring system data from a backup inside MIUI and restoring it in CM?
Edit: Now it's stuck at the white screen. Doing a nandroid backup and going to try some other fun stuff. Yay...
I use amon RA recovery and when I was stuck in a boot loop I would wipe data/factory reset, cache, dalvik cache, as well as wipe the system. That did the trick for me. Best of luck!
PS. Not sure of you can wipe system via clockwork mod, I used it briefly before I got aggravated and flashed a better recovery img IMO.
hTC Evo CM7-n17
You can do a full wipe in clockwork:
factory/data reset, and wipe cache from the main screen, then navigate to advanced and then wipe dalvik cache.
The reason I've been using clockwork is because I like using Rom Manager, but I'm not against Amon if it's the answer. Though, I've now tried it, and it doesn't seem to be.
I've been doing the wipes you're suggesting since the beginning. Those aren't doing it. I have a few ideas that I didn't try last night. Gave up after about hour 7 of trying different things.
My next experiment is to switch kernels. But I'm also thinking there could be a problem w/ my Titanium backup. I don't remember specifically, because I didn't notice it at first, but it does seem to only have a problem after I do a restore. Any thoughts on that one??
deaconzero said:
The reason I've been using clockwork is because I like using Rom Manager, but I'm not against Amon if it's the answer. Though, I've now tried it, and it doesn't seem to be.
I've been doing the wipes you're suggesting since the beginning. Those aren't doing it. I have a few ideas that I didn't try last night. Gave up after about hour 7 of trying different things.
My next experiment is to switch kernels. But I'm also thinking there could be a problem w/ my Titanium backup. I don't remember specifically, because I didn't notice it at first, but it does seem to only have a problem after I do a restore. Any thoughts on that one??
Click to expand...
Click to collapse
Well amon_ra isn't the answer. I've used clockwork and had ZERO problems, and still use it. But if you think titanium is your issue, go into it, and click problems, and it'll download the busybox and correct itself. And if you think the kernel may be the problem, it could be, so go for it. Just make sure to use an aosp kernel on an aosp rom, and the same for sense; don't mix them.
Thanks for the advice. Any suggestions on which kernel I could try? On MIUI my kernel is brandon-ThinkPad-T510 #5.
deaconzero said:
Thanks for the advice. Any suggestions on which kernel I could try? On MIUI my kernel is brandon-ThinkPad-T510 #5.
Click to expand...
Click to collapse
Well I would try the a froyo savaged zen kernel. They all play nice from what I hear.
No fix yet even after switching kernels. I found this link when I was looking up more info http://www.shahz.net/android/what-is-dalvik-cache.html and this section interested me.
"This dalvik cache can grow immensely huge as more applications are installed on your phone. It is safe to wipe dalvik-cache. It will be rebuilt again when the phone boots. This also explains why your phone takes ages to start up for the first time. As for my Nexus One, having about 145 applications installed, it takes about 13 minutes to build the cache"
Could this be what's going on? Is the dalvik cache being rebuilt and I'm not actually getting a bootloop? Do I need to let the blue arrow circle around the skating android for 15 minutes?
Still not working. Tried the kernel switch and the above idea of letting the boot screen run for over 20 minutes. Nothing.
Anyone w/ any thoughts?? Thanks.
Are you flashing the new kernel the same time you flash the rom. What you should do is wipe everything, factory/data, cahe, dalvik cache, then flash the rom. Give it a couple of minutes to boot up. After it eventually boots up, back it up, then flash the new kernel, just wipe the cache and dalvik before you do so.
deaconzero said:
So, I did the calculkin format all however I also did something different this time. I started to notice that it would only boot loop after I did a Titanium batch restore. I would normally restore all apps and system data. This time I only restored apps instead of system data and I can reboot just fine... for now.
Would this cause a problem? Restoring system data from a backup inside MIUI and restoring it in CM?
Edit: Now it's stuck at the white screen. Doing a nandroid backup and going to try some other fun stuff. Yay...
Click to expand...
Click to collapse
Restoring system data through Titanium Backup is almost a certain recipe for disaster - especially when switching between different ROMs. Use TB only to restore user apps, and the data associated with only those apps.
The other thing you may want to try is to repartition/format your SD card. Make sure you back it up to your computer first, then use whatever recovery (I know Amon Ra will do it, think CWM will too) to partition and format the SD card. This helped me out when I was getting bootloops...
Good luck!
BigJohn
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?
This is the weirdest thing, I can't figure it out. I flashed cm7 ran it for a while. I wanted to go back to sense, so I flashed the pbimg for cwm 2.5 through hboot. Data reset, wiped cashe, wiped dalvik. Flashed inc rom 1.5 and after boot downloaded root explorer to remove my bloatware. I noticed I stll had the gb apk's. Obviously, didn't wipe right so booted recovery wiped everything ,flashed again. Still there. after several wipes and re-flashes, they would keep popping back up after reflash. So I went back to cwm 3 wiped and reflashed same issue. So after several times I decided since it wasn't affecting the rom I deleted the apk's I attempted to just keep it. Ran it for a while. Then I came across lcd density changer on app brain so installed it. It looked nice. Until I seen my widgets were all screwed up. So I went back to the default 240. They were still screwed up. so wipe and re-flash, still the same. I got tired of the headache and decided to just restore to stock. So, I restore to stock through hboot. Ran unrevoked . Got into recovery downloaded a fresh copy of inc rom wiped, flashed, got root explorer got root explorer. Guess what, the gingebread system files still mixed in with the inc rom files and widgets are still messed up. Now I'm just scratching my head. Anyone got a clue whats going on?
Try with CWM 3.0.0.7
New ROM's om CWM 2 and CWM 3.0.0.8 do not wipe correctly
The 3.0.0.7 did wipe it. Thanks man. I got it wiped, but I'm still trying to figure out how the hell the cm files stuck around after I restored back to stock .
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