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
Ok. so i searched for the problem and nothing seemed to work or be related to my issue.
I have the EV0 4G.
Its been rooted, wiped the data/cache/dalvik, flashed the rom and gapps yet it still get stuck at the boot screen.
Trying to install the Savaged-Zen ROM
My buddy, nor I can figure out whats going on here.
anyone have this issues
Thanks
socalchef00 said:
Ok. so i searched for the problem and nothing seemed to work or be related to my issue.
I have the EV0 4G.
Its been rooted, wiped the data/cache/dalvik, flashed the rom and gapps yet it still get stuck at the boot screen.
Trying to install the Savaged-Zen ROM
My buddy, nor I can figure out whats going on here.
anyone have this issues
Thanks
Click to expand...
Click to collapse
What rom were you coming from? What recovery are you using to flash and wipe? I may suggest flashing a format all zip before flashing the ROM. That will wipe your system and boot partition as well. Where are you getting stuck at? The splash screen or boot animation?
Format All, Install You Rom, wait for it too boot, then power down and install G-Apps afterwards if it hangs clear dalvik and cache
k2buckley said:
What rom were you coming from? What recovery are you using to flash and wipe? I may suggest flashing a format all zip before flashing the ROM. That will wipe your system and boot partition as well. Where are you getting stuck at? The splash screen or boot animation?
Click to expand...
Click to collapse
I am coming from the stock evo.
Was using the clockwork recovery.
I'm trying to put on savaged zen ROM.
I'm getting stuck at the boot loop after everything was wiped and then flashed.
thanks
i tried different roms lately but everyone that i try my phone randomly reboots it self i was wondering could someone please HELP ME
Basic questions.
What ROM are you running now? What kernel?
How do you flash, in recovery or with ROM Manager?
What recovery do you have?
HipKat said:
Basic questions.
What ROM are you running now? What kernel?
How do you flash, in recovery or with ROM Manager?
What recovery do you have?
Click to expand...
Click to collapse
the rom i am currently using is mikG 2.55 and using Freedom0.9 aggressive for my kernel. and i flashed them both with Amon_RA v2.3
what was your method of flashing? did u flash rom, then reboot? Or did u flash both of them @ same time in recovery? give me a run down and i'll see what i can do to help
u prob know all this stuff but sometimes i forget something as simple as wiping diff stuff. Best option might be a fresh install and maybe flashing virus superwipe first.
I disagree with superwipes.
Just go to wipe in Amon RA and wipe every option there is, except SD Card: and Battery Stats, if you're not full ycharged. Wipe Cache and Dalvik-Cache twice, then flash the ROM, reboot, let it settle for a few minutes, reboot to recovery. Wipe Cache and Dalvik Cache again, flash the kernel.
Reboot, let it settle a few minutes and start doing your setup
I recently got a replacement Evo from Sprint and was able to root and have been running MikG for a while. I haven't been getting the battery life that I'd like to see (I'm a fairly heavy user) so I want to go back to using Deck (which I had great success with in the past). However, when I flash Deck 1.3 I get stuck in a white screen boot loop. I wipe Cache, D-Cache and Data via AmonRa, but no look. I can get back to recovery just fine and restore a nandroid backup just fine.
Any thoughts?
Make sure to wipe everything except your sdcard and battery stats.
Wipe data factory rest, data,system, boot, cache,dalvik cache, android secure and sdext if your partitioned then flash ROM and gapps and see if that works for you.
Sent from my PC36100 using xda premium
Just tried wiping all of those partitions and reflashing with the same result. I even powered off after flashing just to be safe and I let it go through the boot loop about 10 times as well. No luck.
Just out of curiosity, what partition is the kernel stored on? I didn't know if there was anything special that I needed to do to wipe the kernel or not. My guess would be system but I'm not positive what wipes the kernel.
Try a format all zip. Are you partitioned for a2sd? Wipe SD ext.
You can find the format all in the link below
Having trouble with AOSP? http://forum.xda-developers.com/showthread.php?t=1295702
Dont know if anyone else has experienced this but i have been using jellybean port for sprint the past few days and today i decided to revert back to cm9. Im using stock cwm recovery which means not touch recovery or twrp just plain stock cwm recovery. well i wiped data and wiped cache and flashed cm9 rom i had on my sd card and it boot3d fne but i got the jellybean setup wizzard and i couldnt get past it it force close as soon as i touch anything so i went back into recovery and tried again same thing. i have a nandroid backup so i restored that and of course that works because i dont have to go thru setup wizzard. i dont know if this is just my phone or what so im placing this thread here to find out if anyone else has experienced this or if this is happening to me only. if this is an issue with cwm then im sure the devs of cwm would want to know this because if cwm is not wiping correctly then we have a problem. anyways please if anyone can try this and post back results im sure the cwm recovery devs would appreaciate it very much. thanks!
The cm9 installer may not have wiped the system partition. It's usually a good idea to do that before flashing to something new just in case.
xHausx said:
The cm9 installer may not have wiped the system partition. It's usually a good idea to do that before flashing to something new just in case.
Click to expand...
Click to collapse
i did tht! wipe data, wipe cahce, go to mounts/system format system, flash rom and still the same **** man.
maddoggin said:
i did tht! wipe data, wipe cahce, go to mounts/system format system, flash rom and still the same **** man.
Click to expand...
Click to collapse
One thing you could try is "fix permissions" in CWM.