Related
My phone won't boot more than 3 seconds into the animation. I use CM6.0 stable. I had flashed the PS3Freedom zip in order to Jailbreak my PS3, restored to CM6 with no problem, and then when I did it again I couldn't boot into my RESTORED CM6 ROM. I restored few old nandroids that I didn't like till I got to my rooted Sense 2.2 one, then I deleted a few nandroids from when I was flashing nightlies to make room to download BakedSnacks 1.7 through ROM Manager. Everything was working fine, but then I tried to get CM6 running again and I am still not able to boot into it. What's going on here?
To the best of my knowledge I've been wiping the Data/Cache as often as necessary, even the Dalvik Cache a few separate times trying to get this to work.
blakerboy777 said:
My phone won't boot more than 3 seconds into the animation. I use CM6.0 stable. I had flashed the PS3Freedom zip in order to Jailbreak my PS3, restored to CM6 with no problem, and then when I did it again I couldn't boot into my RESTORED CM6 ROM. I restored few old nandroids that I didn't like till I got to my rooted Sense 2.2 one, then I deleted a few nandroids from when I was flashing nightlies to make room to download BakedSnacks 1.7 through ROM Manager. Everything was working fine, but then I tried to get CM6 running again and I am still not able to boot into it. What's going on here?
To the best of my knowledge I've been wiping the Data/Cache as often as necessary, even the Dalvik Cache a few separate times trying to get this to work.
Click to expand...
Click to collapse
what recovery are you using?
in clock work, try wiping to factory, wipe cache partition, wipe datavik then flash from zip to whatever rom.
in RA do the same but make sure your rom is on the root of your sd.
i had the same issue and did that and it worked fine.
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 flashed CM7.1 and I'm stuck in a boot loop. I tried wipe cache partition, wipe date/factory reset, wiping dalvik cache and reflashing a different rom but still keep getting the boot loop. What else should I try doing to slove this ?
Could be kernel related, are you using an aosp and hopefully not a sense kernel? Need more info, what kernel, recovery are you using?
I'm using ClockworkMod recovery I'm not sure what kernel I using
Easy fix, recommend starting from new. wipe the entire phone in recovery at least 3 times, sd card also, backup sd card to computer if you need to via USb toggle, flash Cm 7.1, flash tiamat kernel, found in development section, reboot, good to go, nandroid once up and running, happy flashing
Thanks, okay I'm glad you said easy fix I'm not as worried now. I'm gonna follow your advice. Whats a roamer kernel ?
sorry swype acting weird, use tiamat kernel 4.1 something in development section
The FIRST Thing you should do is get rid of Clockwork Mod, and get Amon Ra, so you can wipe everything.
Just wiping Data/Cache/Dalvik when flashing a new ROM isn't enough.
Hey thanks again ! ! I followed your advice and got everything working again
Thanks to Hobby31 (http://forum.xda-developers.com/member.php?u=2360932) for figuring this out. I have taken his post, and rewritten for ease of reading. Tested and working on (at least) 2 phones so far.
How to restore a Nandroid or flash new ROM with CWM Touch
In CWM Touch Recovery
1. Go to mounts and storage and unmount cache.
2. Make a nandroid. (Going back to mounts and storage, you will see data is mounted and will not unmount.)
3. Go to "advanced" and select reboot recovery.
4. Once phone reboots into recovery, go back to mounts and storage and see that data is unmounted. You may now wipe data, system, and cache.
5. You may now restore a nandroid or flash a new rom.
Recommendation : As noted below, proper wiping matters when switching between roms, particularly from ICS to JB. Use superwipe from Mike (android revolution HD) when moving between roms. http://api.viglink.com/api/click?fo...="0" alt="">&jsonp=vglnk_jsonp_13416929577832
If this helped you, hit thanks. Also, thank hobby 31. Thread here. http://forum.xda-developers.com/showthread.php?t=1748049
EDIT 7-19-12 If you say "I've had no issues doing backups and restores with CWM," please ask yourself the following questions:
1. Are you using CWM Touch or non-touch? This is a Touch issue. If you are using the non-touch... you need not read further or report "I have no problems" because this is specifically related to Touch. (Please note I have not flashed the new 6.0 CWR Touch as some people are reporting problems with it also.)
2. Did you do multiple operations in the same recovery session? Meaning did you wipe data/factory reset, wipe cache, wipe delvik? Then did you try to flash a new ROM or restore a backup without restarting recovery? The reason this matters is because this issue of data not unmounting seems to happen in Touch CWM after a wipe is performed. You might be able to do one action per recovery session, but doing multiple actions that require data to be unmounted are what borks the operation and leaves some people hanging at the glowing X of "Oh crap I need to boot back into recovery."
Let me know if there are any problems, need for further clarification.
I flashed an older version of CWM (5.5.0.4) Non Touch version so I could flash JB but my SD card would not mount after I did a full wipe. Had to use the Toolkit to flash stock image. Do you know what would cause that to happen? People are saying to use the older version to flash JB and I want to try VanirBEAN ROM but don't want to run into the same SD mount issues.
I have not had any difficulty restoring cwm nandroid backups of other ROMs, or flashing other ROMs coming from V3. Have not had to resort to any of these steps. But I have seen a lot of threads about others having a lot of problems. Just curious if anyone has any theories about why this is?
Gallery69 said:
I flashed an older version of CWM (5.5.0.4) Non Touch version so I could flash JB but my SD card would not mount after I did a full wipe. Had to use the Toolkit to flash stock image. Do you know what would cause that to happen? People are saying to use the older version to flash JB and I want to try VanirBEAN ROM but don't want to run into the same SD mount issues.
Click to expand...
Click to collapse
I flashed the BAMF You Jelly Huh? ROM using the clockwork touch recovery and it worked flawlessly (I did wipe data though)
cam30era said:
I have not had any difficulty restoring cwm nandroid backups of other ROMs, or flashing other ROMs coming from V3. Have not had to resort to any of these steps. But I have seen a lot of threads about others having a lot of problems. Just curious if anyone has any theories about why this is?
Click to expand...
Click to collapse
After talking with others, I think my issue was after flashing the older CWM I did not reboot before moving forward with the wipe. Too chicken to try it again
I think it has to do with the coding in vicious and some of the initial releases of JB roms. Coupled with the data not unmounting at the proper time. A couple people also have mentioned that they didn't do as full of a wipe as is done with the super wipe script, hence why a lot of devs suggest using it to clean out old ics code.
Has nothing to do with Viscious. Same on JellyBelly 3.x Even when moving between JB roms, Data won't unmount when performing multiple operations.
I have flashed all three versions of Vicious' JB with CWM Touch and have not had a single problem. My process is as follows:
-Backup
-format /cache
-format /data
-format /system
-Wipe Dalvik cache
-Flash ROM
-Wipe Dalvik cache
-Reboot
-????????
-Profit
Team win recovery aka twrp. Everyone done says "use non touch recovery" it doesn't matter. Haven't had a single issue using twrp on this phone or any of my previous phones. It works great. Especially with super wipe scripts.
Sent from my Galaxy Nexus using Tapatalk 2
Omen87 said:
I have flashed all three versions of Vicious' JB with CWM Touch and have not had a single problem. My process is as follows:
-Backup
-format /cache
-format /data
-format /system
-Wipe Dalvik cache
-Flash ROM
-Wipe Dalvik cache
-Reboot
-????????
-Profit
Click to expand...
Click to collapse
Bingo. That's what superwipe does.
Added link to Mike's superwipe.
Sorry for the dumb question, but ive done a search and found conflicting answers. When you wipe data and cache do you want them to be mounted or unmounted?
Sent from my Transformer TF101 using Tapatalk 2
I have Touch CWM and I have no problems flashing back and forth between JB and ICS roms and nandroids.
You just have to flash a Super Wipe in between.
I just did this yesterday to test out my MHL adapter. Backed up my JB rom, super wiped, restored my ICS Liquid Rom, tested, super wiped, restored my JB rom.
I think super wipe is key in going between different rom builds. But I've had absolutely no problem using CWM at all. If Super wipe is the answer, then perhaps CWM's Factory Reset option isn't wiping as well as it should.
Flashing a SuperWipe is much easier then having to restart the phone a few times.
I think it may be related to Viscious old versions. Not Sure. Using Jelly Belly now. If you are not having problems, that's great. I used superwipe script. No problems. But, if people want the manual solution without getting errors, then at least we know the above method works. It might not be neccesary now with the newer releases, maybe data will unmount ok.
If anyone wants to test and see if they can restore old backups from ICS w/out doing the above steps (IE the rebooting) and report back, it'd be appreciated. I will be uber busy the next couple days or I'd take the time to backup to my computer before trying.
Would you mind sending me the super wipe script to flash? Or point me to the thread?
Sent from my Galaxy Nexus using xda premium
mikeacela said:
Would you mind sending me the super wipe script to flash? Or point me to the thread?
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Link on Page 1... Sorry, I'm on my phone or I'd paste it for you.
player911 said:
I have Touch CWM and I have no problems flashing back and forth between JB and ICS roms and nandroids.
You just have to flash a Super Wipe in between.
I just did this yesterday to test out my MHL adapter. Backed up my JB rom, super wiped, restored my ICS Liquid Rom, tested, super wiped, restored my JB rom.
I think super wipe is key in going between different rom builds. But I've had absolutely no problem using CWM at all. If Super wipe is the answer, then perhaps CWM's Factory Reset option isn't wiping as well as it should.
Flashing a SuperWipe is much easier then having to restart the phone a few times.
Click to expand...
Click to collapse
I'm running CWMR 5.8.0.2 and I've restored my ICS roms over several JB roms without issue and no use of any sort of superwipe script.
nhizzat said:
I'm running CWMR 5.8.0.2 and I've restored my ICS roms over several JB roms without issue and no use of any sort of superwipe script.
Click to expand...
Click to collapse
This. ^^^^^^
Sent from my Galaxy Nexus using xda app-developers app
nickles96 said:
This. ^^^^^^
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Are you using Touch Based CWMR? Or Standard.
I can confirm even with Jelly 3.6, that after I wipe data, cache, and delvik that the data will then remain mounted and not unmount unless I restart recovery.
This can/does cause problems and messes up operations when people are doing multiple actions in recovery at the same time. You might be able to do one action, such as making a backup just fine. But if you are using CWMR Touch, you might have issues with doing multiple operations in the same recovery session, like, backup, wiping, then restoring if the action you are doing requires data to unmount.
So, if you say "I have no problems..." please confirm that you are using touch recovery... not just standard.
CWM Touch was updated to 6.0.0.5 this week, is this issue still present? I haven't experienced any problems yet using CWM Touch, I'm just curious.
My steps are 1. Backup 2. Wipe data/factory reset 3. Wipe cache partition 4. Wipe Dalvik cache 5. Flash ROM 6. Flash GApps if needed 7. Reboot
Hi all, I'm pretty familiar with flashing custom ROMs as I previously had a Samsung Galaxy S Captivate.
I recently got a Telus T989D, and I'm having some frustrating problems trying to flash a custom ROM. I have ClockWorkMod Recovery installed, and have been trying to flash various Cyanogen CM9 ROMs onto the phone. They all install properly, but once it gets to the Cyanogen splash screen (with the Android man turning angry for CM9), it gets stuck here.
I thought perhaps I needed to flash my radio, since all these custom ROMs were for the T-Mobile T989 "hercules" model. So I flashed the SGH-T989_UVLE1_radio.zip hoping that would work. Same problem.
Kind of at a road block here - any suggestions would be very much appreciated. Thanks!
Rhombuss said:
Hi all, I'm pretty familiar with flashing custom ROMs as I previously had a Samsung Galaxy S Captivate.
I recently got a Telus T989D, and I'm having some frustrating problems trying to flash a custom ROM. I have ClockWorkMod Recovery installed, and have been trying to flash various Cyanogen CM9 ROMs onto the phone. They all install properly, but once it gets to the Cyanogen splash screen (with the Android man turning angry for CM9), it gets stuck here.
I thought perhaps I needed to flash my radio, since all these custom ROMs were for the T-Mobile T989 "hercules" model. So I flashed the SGH-T989_UVLE1_radio.zip hoping that would work. Same problem.
Kind of at a road block here - any suggestions would be very much appreciated. Thanks!
Click to expand...
Click to collapse
Oh, and to clarify in case anyone asks - I have been doing data/cache/Dalvik wipes in recovery before installing the ROM.
Rhombuss said:
Oh, and to clarify in case anyone asks - I have been doing data/cache/Dalvik wipes in recovery before installing the ROM.
Click to expand...
Click to collapse
If you are running CWM 5.0.2.7 non touch recovery, you have to use TDJs Superwipe script first to wipe data partition and system partition. Then you flash the ICS radio (if you haven't done so already) then the CM9 ROM, then ICS Gapps.
After this you need to flash TDJs Cache Wipe script. This will properly wipe cache, dalvik, and fix permissions. CWM 5.0.2.7 doesn't wipe and align the cache properly and gives problems. I never had any issues with CWM when running those scripts and it boots up everytime.
Alternatively, you may want to install TWRP 2.2.2 instead of CWM. It's a touch based recovery, but very simple to use and much better than CWM in my opinion. You also don't need to run the scripts since the data and system are wiped properly and cache and dalvik are also cleared properly as well.
If you go to the development section, under the TWRP thread, and search for flashable zip, there is a 2.2.2 flashable available that you can use in CWM. Then the next time you boot into recovery you will be in TWRP instead of CWM.
Chochiwpg said:
If you are running CWM 5.0.2.7 non touch recovery, you have to use TDJs Superwipe script first to wipe data partition and system partition. Then you flash the ICS radio (if you haven't done so already) then the CM9 ROM, then ICS Gapps.
After this you need to flash TDJs Cache Wipe script. This will properly wipe cache, dalvik, and fix permissions. CWM 5.0.2.7 doesn't wipe and align the cache properly and gives problems. I never had any issues with CWM when running those scripts and it boots up everytime.
Alternatively, you may want to install TWRP 2.2.2 instead of CWM. It's a touch based recovery, but very simple to use and much better than CWM in my opinion. You also don't need to run the scripts since the data and system are wiped properly and cache and dalvik are also cleared properly as well.
If you go to the development section, under the TWRP thread, and search for flashable zip, there is a 2.2.2 flashable available that you can use in CWM. Then the next time you boot into recovery you will be in TWRP instead of CWM.
Click to expand...
Click to collapse
I just installed TWRP and I'm still running into the same issue. The Cyanogen splash screen just runs indefinitely. Looks like that wasn't the problem? Does it matter if you're rooted or not, if you try to flash a ROM from recovery?
Rhombuss said:
I just installed TWRP and I'm still running into the same issue. The Cyanogen splash screen just runs indefinitely. Looks like that wasn't the problem? Does it matter if you're rooted or not, if you try to flash a ROM from recovery?
Click to expand...
Click to collapse
Use the Darkside Superwipe to recreate all your partitions correctly. Sometimes when they are not aligned properly (by TWRP) you get weird boot hangs.
Don't restore data! Instead back everything up with something like Titanium and restore user apps only after the ROM has booted and you are satisfied.
+1 for the last post. Should work 100%!
Sent from my SGH-T989 using xda premium
---------- Post added at 12:17 AM ---------- Previous post was at 12:09 AM ----------
http://forum.xda-developers.com/showthread.php?t=1477955
Sent from my SGH-T989 using xda premium