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
So I got Cm7 running using rom manager, used titanium backup to restore apps + system data, then fixed permissions. For the last 10 minutes it's been stuck in the CM7 screen....
What should I do? Can I pull the battery without harm? Does it take that long to boot after fixing permissions?
Edit: pulled the batter and am trying to boot into recovery...going to wipe the dalvik/cache again.
Edit2: same thing for the last 6 minutes....dang. I guess I'll just nandroid in 5 minutes if it doesn't' get out of it.
Edit3: going to nandroid back. I might try it again later flashing from a Zip instead of using rom manager. I probably won't restore system data either next time. If anyone has any suggestions though please post them.
Edit4: not good...phone is bootlooping cyangen screen after nandroid.
Edit5: Cleared factordata, cache, and when I go to clear dalvik I'm getting
e unknown volume for path sd-ext
Any ideas here?
Edit6: I'm reflashing 6.1.2....okay...got through the boot and now I'm setting up the phone.
You may need to wipe everything now and reinstall fresh. Do a search for Calkulin's tools here and download the format all zip and put it on the root of your sdcard. Flash it just like you would a rom from recovery. It will wipe boot, data, cache and system. Then try flashing cm7 from recovery. Usually boot loops happen because of there not being enough space on one of your partitions like system or boot etc.
housry23 said:
You may need to wipe everything now and reinstall fresh. Do a search for Calkulin's tools here and download the format all zip and put it on the root of your sdcard. Flash it just like you would a rom from recovery. It will wipe boot, data, cache and system. Then try flashing cm7 from recovery. Usually boot loops happen because of there not being enough space on one of your partitions like system or boot etc.
Click to expand...
Click to collapse
Will do....I know I had been installing apps to the SD card using CM6 and when I first got CM7 up it said my phone memory was low. I thought it would say on the SD card.
I'll probably try tomorrow again if I get the courage and I most definitely will DL Calkun's tools.
Thanks!
I'm going to guess the nandroid didn't work either because of the phone memory low issue?
I would reccomend re-doing what you did originally, except when restoring with titanium, do NOT restore system settings, only apps and data. That's probably the cause.
teh roxxorz said:
I would reccomend re-doing what you did originally, except when restoring with titanium, do NOT restore system settings, only apps and data. That's probably the cause.
Click to expand...
Click to collapse
Wiped manually, installed from zip, and didn't restore system data. CM7 has been running for about an hour now.
Thanks everyone!
Glad that you got it working man.
Is ANY system data safe to restore from Titanium?
Had the exact same problem myself... I'm restoring my Myn nandroid as we speak, and I'll mess with it more tomorrow.
Does anyone know what (if any) system data is safe to restore from Titanium? I just want my contacts and text messages basically... I don't know exactly what caused the problem from Titanium since I made sure not to check any of the Sense-related items.
For about 20 min after I pulled the battery I couldn't get the phone to do anything except vibrate three times when I tried to get into recovery. Eventually coaxed it into the bootloader where I selected to boot into recovery to nandroid back. Almost had a heart attack!
phsteve said:
Had the exact same problem myself... I'm restoring my Myn nandroid as we speak, and I'll mess with it more tomorrow.
Does anyone know what (if any) system data is safe to restore from Titanium? I just want my contacts and text messages basically... I don't know exactly what caused the problem from Titanium since I made sure not to check any of the Sense-related items.
For about 20 min after I pulled the battery I couldn't get the phone to do anything except vibrate three times when I tried to get into recovery. Eventually coaxed it into the bootloader where I selected to boot into recovery to nandroid back. Almost had a heart attack!
Click to expand...
Click to collapse
You should never restore system settings.
For contacts, open accounts and sync, tap your google account, then sync contacts, and that'll be done.
For texts, people highly recommend sms backup or my backup. Then backup apps and data, then restore only apps and data, and you'll be set.
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.
I had flashed Warm TwoPointThree. Didn't really like it so I restored to my nandroid back up. Now the phone randomly crashes for no apparent reason. It is sitting next to me on my desk and just now it crashed, wasn't even touching it. Secondary to the crashes is that after it happen and I try to report the phone is registering no charge and then immediately shuts down till I put it on a charger, regardless of actual battery charge.
Edit
More info. It has never crashed while on the charger. Don't know if that is relevant.
Did you wipe properly prior to restoring your nandroid? Also, what recovery are you using? If it's not Amon-ra, you need to get it! Make sure when doing a nandroid restore you have the appropriate items checked for restore (Assuming you did this when making the nandroid to begin with). Usually Boot, System, Data, and SD ext if partitioned.
Im using Amon-ra and I have an unpartitioned SD card. What do you mean by wipe? I'm a new to the entire rooting thing.
You need to wipe all data factory reset, boot, system, and dalvik cache in recovery three times each. Then restore your nandroid. You can also use a superwipe script but I feel manually wiping them is best.
Sent from my PC36100 using XDA
dieselford said:
You need to wipe all data factory reset, boot, system, and dalvik cache in recovery three times each. Then restore your nandroid. You can also use a superwipe script but I feel manually wiping them is best.
Sent from my PC36100 using XDA
Click to expand...
Click to collapse
Can I use the wipe feature in Amon-ra to do this?
Yes. That is the way to do it.
Sent from my PC36100 using xda premium
Try fix permissions, I think RA has it under other, or if u have Rom manager there is an option to fix permissions
Sent from my Synergized Aggressive Lionfish Evo using the XDA app
I think I may have found a problem with the backup I was using. For some reason the backup file had 2 copies of every entry.
Under the other tad in RA recovery there was options to fix apk uid mismatches and move recovery.log to SD.
I selected the fix apk uid mismatches. Im hoping that is the fix permissions that the previous poster was talking about. If not then can I get some direction in doing it properly?
SabaBoBaba said:
I think I may have found a problem with the backup I was using. For some reason the backup file had 2 copies of every entry.
Under the other tad in RA recovery there was options to fix apk uid mismatches and move recovery.log to SD.
I selected the fix apk uid mismatches. Im hoping that is the fix permissions that the previous poster was talking about. If not then can I get some direction in doing it properly?
Click to expand...
Click to collapse
Yes that's it.
Well the crashes have started again. They seem to start slow, one crash then like 3 days later another and then just increase in frequency, today it crashed 5 times before noon. I'm at the point that I think perhaps I need to wipe and not attempt to do a restore. My concern is will I lose my root if I do that?
Will I lose root if I do wipe with out restoring afterward?
SabaBoBaba said:
Will I lose root if I do wipe with out restoring afterward?
Click to expand...
Click to collapse
If you wipe without restoring, you won't have a ROM on your device. You'll have to flash one, and as long as it's a custom or rooted stock ROM, you'll be fine.
Well I did a factory reset tonight so we'll see how that goes. Thanks to those people who contributed.
Well I did the factory reset and this morning it crashed again. I'm at a loss. All this started after I installed the Warm 2.3 ROM and then restored back to a backup to get the stock ROM back. Any thoughts on what to try now?
Any further help that anyone can offer on this. I'm at the end of what I can think of to do
SabaBoBaba said:
Any further help that anyone can offer on this. I'm at the end of what I can think of to do
Click to expand...
Click to collapse
Just stop restoring and flash a ROM from scratch. Do a full wipe (everything except SD card), and then flash the ROM (custom or stock) or your choice. It seems that the restore is at the root of your problem, so it may be time to give up on that.
Current ROM (BootManager Slot 5): ICS-Deck-PreBeta20 | Kernel: Mason v0.14 SBC (FSO)
Captain_Throwback said:
Just stop restoring and flash a ROM from scratch. Do a full wipe (everything except SD card), and then flash the ROM (custom or stock) or your choice. It seems that the restore is at the root of your problem, so it may be time to give up on that.
Current ROM (BootManager Slot 5): ICS-Deck-PreBeta20 | Kernel: Mason v0.14 SBC (FSO)
Click to expand...
Click to collapse
Well Im going to flash this http://forum.xda-developers.com/showthread.php?t=1455340&highlight=stock+rom and see if that works. Thanks for the assist.
After wiping last night and loading the rooted version of the latest stock ROM it crashed again today. Next idea?
Try wiping in recovery by flashing Edify_Format_ALL (found on xda). I manually wipe Dalvik, habit... Flash rom from scratch. I use Titanium Backup to back up apps and data just for these situations. Some caches are moved to SD card, maybe delete these folders and let system rebuild them. (ie android_secure).
Hope you get it sorted out.
Grizraz said:
Try wiping in recovery by flashing Edify_Format_ALL (found on xda). I manually wipe Dalvik, habit... Flash rom from scratch. I use Titanium Backup to back up apps and data just for these situations. Some caches are moved to SD card, maybe delete these folders and let system rebuild them. (ie android_secure).
Hope you get it sorted out.
Click to expand...
Click to collapse
Ill give that a shot. I hope I can fix what ever I did to foul this thing up.
Just from searching the forums I really dont understand this edify thing. Can you help be get some clarity on it?
Hello!
I have installed RootCloak and after the needed reboot of the phone, it is always stuck in Viper One logo boot screen.
When I wipe Dalvik, I get the actualization screen from Android and after checking the apps nothing else happens. Just "apps are getting started" and the spinning circle....
Any ideas how to recover my phone?
I can't perform a backup because CWM says it cannot mount the sd-card and there is not enough space on internal memory.....
Can you reflash the rom?
And why are you wanting to do a backup of a corrupt system?
KJ said:
Can you reflash the rom?
And why are you wanting to do a backup of a corrupt system?
Click to expand...
Click to collapse
I have already reflashed the ROM, but no effort.
All I want to save are SMS and photos. Can I secure them on any way?
Do you have a nandroid backup from your recovery that you can restore? And if not... Why? ? Everyone should do a backup before flashing anything.... Then you always can restore to your previous state.
That will not wipe your pics. But sms yes. Just about anything you do will wipe your sms's .
There may be a way to adb pull your texts and even pics... If you can get into adb mode in your recovery. But you'd have search on that, I've never done it.
Anyway, Another option is from recovery, wiping system, data, cache and dalvik and clean installing your rom. Whatever that app did will be wiped. Pics will be fine. But again, sms gone.
That's all the ideas I have. Aside from returning to stock.
KJ said:
Do you have a nandroid backup from your recovery that you can restore? And if not... Why? ? Everyone should do a backup before flashing anything.... Then you always can restore to your previous state.
That will not wipe your pics. But sms yes. Just about anything you do will wipe your sms's .
There may be a way to adb pull your texts and even pics... If you can get into adb mode in your recovery. But you'd have search on that, I've never done it.
Anyway, Another option is from recovery, wiping system, data, cache and dalvik and clean installing your rom. Whatever that app did will be wiped. Pics will be fine. But again, sms gone.
That's all the ideas I have. Aside from returning to stock.
Click to expand...
Click to collapse
I have a nandroid backup when I installed the ROM, sure...
But I did not make a new one while installing RootCloaker, because it is "just an app". so the backup is too old any many SMS will be gone.
Can I access the device via ADB when it is in recovery?
Schlicki said:
I have a nandroid backup when I installed the ROM, sure...
But I did not make a new one while installing RootCloaker, because it is "just an app". so the backup is too old any many SMS will be gone.
Can I access the device via ADB when it is in recovery?
Click to expand...
Click to collapse
If it has the option. In twrp it's in advanced menu I believe. Not sure about others.
Restoring your nandroid will likely get you running. In the future, backup texts with sms backup and restore or a similar app. Then you'll be good.
Or let go of the past like I do.... I start fresh with texts after every flash. But that's me. To each their own. ?
But at this point, you're missing out on your phones functionality over them. And whether you can pull the with adb , I'm not even sure.
Good luck though!