Can anyone help me?
I am running SkyRaider 3.1 with the Hydra SSUV kernel.
I ran ClockworkMod through Rom Manager, selected wipe cache, then wiped dalvik cache and the phone is now stuck in the boot sequence at the Droid eye screen. It's now been about 20 minutes, so I assume it has had enough time to rebuild itself.
Any ideas? I have a nandroid backup from a few days ago, but I would like to avoid doing that.
joehero said:
Can anyone help me?
I am running SkyRaider 3.1 with the Hydra SSUV kernel.
I ran ClockworkMod through Rom Manager, selected wipe cache, then wiped dalvik cache and the phone is now stuck in the boot sequence at the Droid eye screen. It's now been about 20 minutes, so I assume it has had enough time to rebuild itself.
Any ideas? I have a nandroid backup from a few days ago, but I would like to avoid doing that.
Click to expand...
Click to collapse
It should have completed by now, I hate to say pull the battery.... but if you are really stuck.
go back to recovery wipe Dalvik and Cache Partition, try booting again, it will take quite a bit of time to reboot this time.
If that does not work use your nandroid backup.
BTW always nandroid before making any changes to your phone that way you lose nothing, even if you think they are quick, easy or minor. Hardware has a way of keeping us humble.
Thanks for the recommendation. I had pulled the battery and figured I would try booting to recovery and wiping the cache again to see what happened. Did that and booted in a minute.
Currently doing a new Nandroid backup...
Related
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 downloaded the supersonic zip to help with my battery life on my evo. it ended up downloading and i went to reboot it but it wont get past the first htc evo screen when you turn it on. Any suggestions?
Thanks.
Try booting into recovery and wiping the cache and dalvik cache, then reboot
i wiped the cache. whats the dalvik cache?
ineedhtcevohelp1 said:
i wiped the cache. whats the dalvik cache?
Click to expand...
Click to collapse
never mind i wiped that too. now it just goes back to clockworkmod.
You might need to restore from a backup, then you can try again. I'm not sure what this zip is that you're talking about.
You did make a backup before flashing, I hope?
yes, i backed up and restored every thing im just having trouble leaving the clockworkmod recovery now. ill try backing it up and restoring it again though
H'okay. So. I had Myn's 2.2 and I wanted to try out something different so I decided on CM7 RC2.
I do a nandroid backup (ofcourse) and then proceed to wipe my cache/factory reset. I then flash CM7 and then do a partial restore of my data for my apps/contacts.
I then proceed to the boot screen and it just loops, over and over again. Without loading my data, CM7 boots just fine... so what in my data is preventing me from being able to boot into CM7?
Thanks in advance!
Boot into recovery, wipe dalvik cache, reboot system.
Try not restoring the data part of the applications. I've heard sometimes issues can arise from that.
r916 said:
Boot into recovery, wipe dalvik cache, reboot system.
Click to expand...
Click to collapse
I have tried this.
totalanonymity said:
Try not restoring the data part of the applications. I've heard sometimes issues can arise from that.
Click to expand...
Click to collapse
What am I supposed to restore to get apps/contacts back then? :3
What you should do is backup your apps with titanium, backup your rom, then wipe factory/data, cache, dalvik cache, flash the rom. on the first boot, it may take an extra couple of minutes. After you sign in, blah blah, open titanium backup, then restore apps with data, NOT system settings.
What you have to do is flash Calkulin's Format All zip. This will delete everything except for the SD card. While still in recovery reflash CM7 and then while STILL in recovery flash the proper Gaaps. You follow these tlstwps I guarantee it will work without a problem. FYI, in terms of restoring your apps with data more than likely it wont work. I have always had trouble restoring AP data when going from Sense to AOSP (CM) Hope this helped.
I flashed SNS Gingerbread v1.7,OTA 4.53 Sense to my EVO and the ROM won't start. The phone has been sitting for 2 hours. I only see the black screen with android then somtimes the white htc screen will pop up but the ROM won't start. How long should it take.
Help is appreciated.
rford78 said:
I flashed SNS Gingerbread v1.7,OTA 4.53 Sense to my EVO and the ROM won't start. The phone has been sitting for 2 hours. I only see the black screen with android then somtimes the white htc screen will pop up but the ROM won't start. How long should it take.
Help is appreciated.
Click to expand...
Click to collapse
have you tried clearing cache in recovery?
if that doesn't work, i would do a wipe and reflash the rom.
I run that ROM with no problems. Try wiping everything (cache data dalvik), and then reflashing the ROM. It's always going to take a little longer to start up the first time, like 5 minutes, but should be faster from there.
Im a little new so thank you for the patience, here is a quick order of how i was taught to flash
wipe data/factory reset twice
wipe cache partition twice
go to advance
wipe dalvik cache twice
wipe battery stats twice
install zip from sd card
choose zip from sd card
then select the rom,
after that the screen has the black background and android then flashs the white background htc,
any corrections you advise are appreciated
Are you using Clockwork or Amon Ra?
If Amon Ra, which I suggest you use, Wipe everything, except SDCard: (And Battery Stats if not fully charged). Everything else gets wiped.
Then flash the ROM and reboot.
Im useing Clockwork, will give it a third try
This time the evo loaded Kings Alliance (which i pulled from backup, previously today)
AKWARD??
Where did you get the ROM from? Possibly a bad zip file. Check the Dev section and download it from there. Then reflash and see how that works.
It probaly was a bad file i flashed a new one so now im working on overclocking thanks everyone
just tried flashing xplod, after the boot animation just got a black screen.
flashed blazer 3.7, doesnt go past the sgs2 screen, waited like 10-15 minutes twice.
restored miui backup, no problems...
i feel like im probably forgetting something stupid, wiped everything a couple times and all that.
badname said:
just tried flashing xplod, after the boot animation just got a black screen.
flashed blazer 3.7, doesnt go past the sgs2 screen, waited like 10-15 minutes twice.
restored miui backup, no problems...
i feel like im probably forgetting something stupid, wiped everything a couple times and all that.
Click to expand...
Click to collapse
Did you go to advanced in clockwork and clear the dalvik cache?
sure did
this is how it all went down exactly
from miui rebooted into recovery
used calks wipe all 2 times
flashed xplod .05 or whatever it is with a 5
after boot animation black screen, but the screen is on
hold power, reboot, hold vol up and power
booted into rogue recovery, so rogue flashed
wiped everything from the wipe menu: factory restore, cache, dalvik, calks wipe all again just in case
reboot, same deal with black screen after boot animation
reboot into recovery wipe everything flash blazer
stuck at sgs2 screen
reboot into recovery, restore backup
MIUI is back up and running
Make sure you format the system and data before you flash touchwiz or aosp. I usually go to the mounts and storage, and format system, data, and cache. Also, are the roms your trying to install modified in any way?