First off sorry if this is answered in another post, lease kindly direct me to the post if it is =)
I just tried to install a second ROM from ROM Manager. I was running DCU and created a back-up in ClockworkMod before I started then installed the new Fresh ROM successfully. When I tried to go back to my first ROM via the restore point I set up it gets stuck in a boot loop. The 2nd restore point from the Fresh ROM loads up just fine.
Is there anyway to fix the older restore point and get back to DCU or should I just wipe everything and reinstall DCU...
Thanks in advanced!
do a data wipe, clear cache and dalvick
Then restore your backup. Clockwork does not seem to like certain roms.
Bielinsk said:
do a data wipe, clear cache and dalvick
Then restore your backup. Clockwork does not seem to like certain roms.
Click to expand...
Click to collapse
thanks, i was able to wipe everything from the original android recovery mode and upload an old nandroid back up but from Clockwork it didnt seem to clear the dalvik cache, when i clicked clear it just went back to the last menu it never said anything in the log and when i loaded up the Clockwork backup it still didnt work :/
So i installed a custom rom and everything went to hell so basically i tried to download the newest update for the evo 2.2 when after i put the update on the root of the phone and o the whole boot thin i install from .zip then an error comes up and i fixed that then another and over and over again...all i want now is to have the phone back to like i had it when i bought it
KR3UZL3R said:
So i installed a custom rom and everything went to hell so basically i tried to download the newest update for the evo 2.2 when after i put the update on the root of the phone and o the whole boot thin i install from .zip then an error comes up and i fixed that then another and over and over again...all i want now is to have the phone back to like i had it when i bought it
Click to expand...
Click to collapse
need more info. how did you go about trying to do this? what steps did you? More info on what you did can help someone figure out where you went wrong. Did you create a nandroid backup before you flashed the ROM? what recovery are you using? Did you wipe data (factory reset), cache, and davlik cache prior to flashing the ROM? If you did make a back up, and can get to Recovery (volume down and power button, then select recovery) I would wipe all data, cache and davlik cache, then flash a nandroid backup. If you didn't make a nandroid backup, I would try wiping everything again, and try flashing the ROM a second time.
http://shipped-roms.com/index.php?category=android&model=Supersonic
THAT SHOULD GET U BACK TO STOCK
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'm sorry if this has been asked before but I tried searching multiple times and couldn't find anything about this. I just recently flashed my phone following the directions from the developer and the only major issue that I know of is the camera flash will not work when taking a picture in low light. I also tried the "flashlight" app and that also won't turn on the light either. Before I try re-flashing the ROM, is there anything I can try before? Thanks for the help...
I can assure you that it is NOT the rom, unless, of course, you have a corrupt download. My camera flashes like it is suppose to and my flashlight turns on and i am currently using the Synergy RC-1 rom. You can try rebooting into recovery, wipe cache & dalvik and then re-flash Synergy atop your current install.
posting & replying via my EVO 4G
Thanks for your help. I hate to re-flash after configuring the layout the way I like but if that's what it takes then I'll do that.
mexag05 said:
Thanks for your help. I hate to re-flash after configuring the layout the way I like but if that's what it takes then I'll do that.
Click to expand...
Click to collapse
If you're going to reflash the same Synergy rom then go into recovery, wipe cache & dalvik and then make a nandroid backup of only your data as well as android.secure & sdext partitions. (If you do not have any apps saved on the android.secure [usually paid apps] and/or the sdext partition then disregard including them in the backup). Afterwards, flash the Synergy rom, boot to your homescreen, and then clear all of the default widgets from your homescreens. When you're finished, reboot into recovery, wipe cache & dalvik then restore the backup that you made of your data, android.secure & sdext, if applicable. Whe the restore it complete, boot to your homescreen. You will find them as they were in the previous installation of the rom.
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.