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 :/
Related
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
Hey Everyone,
I had Starburst with Data2SD flashed on my Desire with some things cooked in from the UOT. I found the MIUI ROM and I figured I wanted to try it. I made a Recovery backup so that if I didn't like it, I could get right back to where I left off. I flashed the CDMA MIUI ROM which was a mistake because my Desire is GSM (Doh) But I went in to recovery and selected the backup I made before I flashed MIUI and restored it, it restored successfully but when I reboot it just sits at the white screen that says htc and it doesn't go anywhere after that. I can reflash the Starburst ROM and reinstall the Data2SD and it will boot and everything and then I go back in to recovery and restore just the data from the back up and it doesn't boot after that. Can anyone help me figure out where I'm going wrong? I don't really want to start from scratch. Any help is appreciated. If you think you can help but don't understand what I'm asking, either post here or PM me. Thanks. I would really like my Desire to work so I can stop using my dreaded Iphone.
Did you do a full wipe before you restored your backup? Make sure you do a factory reset/data wipe, cache wipe and dalvik wipe (from advanced menu)
If it still does not work, try wipe just the cache and dalvik cache after restoring the backup and see if it will boot then.
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
Hi all,
Would really appreciate your help! I'm a nOOb and may have bricked my phone. I rooted and installed a LeeDroid Froyo Rom last year, updated this recently to LeeDrOiD V3.0.2 GB. I got brave today and attempted to change this to RCMix S v1.3 (Sense 2.1+3.0mix) but now my phone is stuck on the HTC Bootscreen.
The process I followed was the same as when installing LeeDroids ROMs:
I backed up my apps
Re-partioned my SD card - 512md using ROM Manager
Used ROM Manager to boot to recovery
Factory re-set
Re-installed ROM Manager
Copied the new ROM zip file to the SD Card
Used ROM Manager to boot to recovery
Installed the new ROM which installed correctly ("Congrats, successful installation, re-boot and enjoy ..." or similar word to that effect)
Re-booted
But now it's frozen on a permanent HTC logo bootscreen.
I would greatly appreciate any help you can offer, or a link to the solution if there is one that may have been requested and solved before, I've spent an age searching the forums but can not find a solution.
Thanks in advance,
Karl
sounds like you didnt wipe the dalvik cache.
I would drop the battery out, replace and boot into recover, wipe data factory reset, wipe dalvik and go for another install.
Can you confirm if you did the above?
edit: oh and i dont know if its made a differance but when i install a new rom, i transfer to the SD card then, wipedata, wipe cache and then install as opposed to booting the phone after wiping data
Before flashing you always have to do a full wipe.
Your systemdata and apps can backed up by Titanium Backup. The backup don't get deleted by the wipe. After flashing the new rom (and eventually re-downloading/re-installing Titanium Backup you can restore all systemdata and apps by "Menu>Batch>Restore missing systemdata and apps".
First tip for the future: Always make a complete nandroid before every flash. If there are problems with your new system, you a running system anyway.
Second: When go from sense-rom to a non-sense-rom (or reversed), you must not restore system data, only the apps. Otherwise there can be heavy problems with your system.
vis-tec said:
sounds like you didnt wipe the dalvik cache.
I would drop the battery out, replace and boot into recover, wipe data factory reset, wipe dalvik and go for another install.
Can you confirm if you did the above?
edit: oh and i dont know if its made a differance but when i install a new rom, i transfer to the SD card then, wipedata, wipe cache and then install as opposed to booting the phone after wiping data
Click to expand...
Click to collapse
Cheers Vis-tec,
Yeah, it was the dalvik cache, I did exactly what you suggested and it worked perfectly. Never heard of dalvik cache before but wiping it did the job.
Thanks again,
Karl
MatDrOiD said:
Before flashing you always have to do a full wipe.
Your systemdata and apps can backed up by Titanium Backup. The backup don't get deleted by the wipe. After flashing the new rom (and eventually re-downloading/re-installing Titanium Backup you can restore all systemdata and apps by "Menu>Batch>Restore missing systemdata and apps".
First tip for the future: Always make a complete nandroid before every flash. If there are problems with your new system, you a running system anyway.
Second: When go from sense-rom to a non-sense-rom (or reversed), you must not restore system data, only the apps. Otherwise there can be heavy problems with your system.
Click to expand...
Click to collapse
Thanks MatDroid,
Good tip about the system data when moving between sense and non-sense roms - I would have found that out the hard way for sure!
I know nothing about nandroid so I'll start reading up on it!
Thanks again,
Karl
Yekrallum said:
Thanks MatDroid,
Good tip about the system data when moving between sense and non-sense roms - I would have found that out the hard way for sure!
I know nothing about nandroid so I'll start reading up on it!
Thanks again,
Karl
Click to expand...
Click to collapse
This thread might help to understand the technical definitions:
http://forum.xda-developers.com/showthread.php?t=805247
MatDrOiD said:
Before flashing you always have to do a full wipe.
Your systemdata and apps can backed up by Titanium Backup. The backup don't get deleted by the wipe.
Click to expand...
Click to collapse
Another good tip, I assumed that the wipe would delete the back-up, or to be more precise, I was unsure where it backed up the data/apps to. So I uploaded to Dropbox using the Dropbox feature in Titanium Backup ... this takes an age so it's good to know that the backup doesn't get deleted by the wipe for future rom changes!
Thanks again,
Karl
Try using RaRecovery http://forum.xda-developers.com/showthread.php?t=839621
It's the recommended recovery for RCMix S. I got stuck in splash because of CWM.
Yesterday I tried installing Danvh's 4.4.2 Google Edition ROM and I guess it must have went wrong. I backed up my current ROM and data before the installation. I did a full wipe (davick / data / cache etc.) and I also did a format of internal SD. I installed Danvh's ROM fine but when I rebooted after the installation it will not get past Galaxy S4 screen. So I figured there was something wrong with the ROM so I flashed back to my back up but when I restart my phone it will still be stuck at the S4 screen so I have to keep flashing back to the backup file. I used TWRP 2.6.1.0 for recovery and I also fixed the permissions with TWRP. Any ideas? What should I do? If my phone ever crashes I will have to restore to my only back up.
re: stuck
ragingazn628 said:
Yesterday I tried installing Danvh's 4.4.2 Google Edition ROM and I guess it must have went wrong. I backed up my current ROM and data before the installation. I did a full wipe (davick / data / cache etc.) and I also did a format of internal SD. I installed Danvh's ROM fine but when I rebooted after the installation it will not get past Galaxy S4 screen. So I figured there was something wrong with the ROM so I flashed back to my back up but when I restart my phone it will still be stuck at the S4 screen so I have to keep flashing back to the backup file. I used TWRP 2.6.1.0 for recovery and I also fixed the permissions with TWRP. Any ideas? What should I do? If my phone ever crashes I will have to restore to my only back up.
Click to expand...
Click to collapse
You forgot to do a "factory reset" in twrp before restoring your Nandroid backup.
Most likely after doing that the phone will fully boot.
Be sure to wipe data, system, cache, dalvik cache and
do a factory reset before restoring your backup.
Good luck!
Good luck!
Nope I did do factory reset as well...