Related
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
Are there any special steps required flashing JB AOKP or CM10 from 2.3.6 Juggernaut 4.1v. With Synergy kernel.
Flashing new radios?
Kernels?
I'm looking for a DD. GB has served me well since I flashed back in Dec 11 but I would like to get with the times and Jelly Bean seems like a good fit.
I have searched the forums for a few days looking for similar posts but none seem to fit my circumstances.
Boot cwm, factory wipe, wipe partition cache, wipe dalvik, wipe system, flash rom, will reboot twice, mount system, flash again, flash gapps, I also backed up my efs
Sent from my dr0id running Liquid Smooth r0m
Any particular version of cwm. touch vs non touch. Ive read that a certain version of cwm had issues 6ish I believe.
Current ROM JellyTime - http://forum.xda-developers.com/showthread.php?t=1827590
Rom Manager v5.5.1.5.
Current Recovery ClockworkMod 5.0.2.0.
So I use Rom Manager to reboot into Recovery, where I wipe dalvik-cache, cache partition and data/factory reset. I then flash the zip, followed by gapps
Tried the following ROMS
http://forum.xda-developers.com/showthread.php?t=2003273
http://forum.xda-developers.com/showthread.php?t=2073992
GAPPS
http://goo.im/gapps - I used the top one CyanogenMod - 10.1.x - 4.2.1.
When booted, I get two messages, press OK and they both continue to appear
"unfortunately system ui has stopped"
"unfortunately, the process com.android.phone has stopped"
It appears as I have only just signed up, I cannot ask the Devs direct. I have searched through threads, and can see some others with same problem - no solution though. About to try a dirty flash from Jellytime.
Thanks
Dave
It must fullwipe before install...cause jelly time is 4.1.2 as and the 2 link above is 4.2
wiping
hdorius said:
It must fullwipe before install...cause jelly time is 4.1.2 as and the 2 link above is 4.2
Click to expand...
Click to collapse
I wipe dalvik-cache, cache partition and data/factory reset - is this not enough?
I forgot the menu of cwm recovery,I use 4ext... Is there any option like format all partitions except sdcard
hdorius said:
I forgot the menu of cwm recovery,I use 4ext... Is there any option like format all partitions except sdcard
Click to expand...
Click to collapse
Ok so, CWM "Wipe Menu" :
wipe dalvik-cache
wipe cache partition
wipe dalvik cache and cache partition
wipe battery stats
wipte data/factory reset
Try to
wipe data, cache and dalvik again
then manually (in the advanced menu if I recall correctly):
format boot
format system
<...> (everything except sdcard)
I've taken a look, and nothing relating to formatting is under Advanced.
Under Mounts and Storage Menu however, there is the following:
unmount /cache
mount /data
unmount /sdcard
mount /system
format /cache
format /data
format /sdcard
format /system
mount USB storage
Yep there.
format /cache
format /data
format /system
-SmOgER said:
Yep there.
format /cache
format /data
format /system
Click to expand...
Click to collapse
Rightyho, well I cleared dalvik & cache (from the Wipe menu)
Then into Mounts & Storage Menu and formatted the 3 above.
Then flashed the ROM followed by Gapps, but still system UI and com.android.phone stopping
davestar7 said:
Rightyho, well I cleared dalvik & cache (from the Wipe menu)
Then into Mounts & Storage Menu and formatted the 3 above.
Then flashed the ROM followed by Gapps, but still system UI and com.android.phone stopping
Click to expand...
Click to collapse
Seems like the gapps flashed is the wrong one.. I got the same problem as yours when i was flashing 4.2.1 rom with gapps for 4.1.2.. after that i realized and use the correct one and it boot up perfectly..
That's right. Download the correct gapps for your Android version. http://goo.im/gapps has a properly categorised list.
Jelly Time = CyanogenMod 10 (Android 4.1.2)
Sent from my Desire HD using xda premium
yumm91 said:
Seems like the gapps flashed is the wrong one.. I got the same problem as yours when i was flashing 4.2.1 rom with gapps for 4.1.2.. after that i realized and use the correct one and it boot up perfectly..
Click to expand...
Click to collapse
I flashed just the ROM by itself, and booted up with the same two errors
davestar7 said:
I flashed just the ROM by itself, and booted up with the same two errors
Click to expand...
Click to collapse
Thats weird.. if you have already format everything except sdcard, and flash the rom only, and still got the same problem, then the cause is either from the cwm,which is quite outdated, or the rom itself.. but i doubt the rom is the culprit... try use ext4 recovery or update the latest cwm.. or maybe wait for someone who have a better solution..
Sent from my Desire HD using xda app-developers app
sashank said:
That's right. Download the correct gapps for your Android version. http://goo.im/gapps has a properly categorised list.
Jelly Time = CyanogenMod 10 (Android 4.1.2)
Sent from my Desire HD using xda premium
Click to expand...
Click to collapse
Sorry but I am currently running Jellytime, but trying to flash TO 4.2.x AOSP codefirex - http://forum.xda-developers.com/showthread.php?t=2003273
Where do I update CWM from? I have the rom manager installed, should I use that?
Try to remove SD card. Just in case, as it all seems a bit mysterious.
davestar7 said:
Sorry but I am currently running Jellytime, but trying to flash TO 4.2.x AOSP codefirex - http://forum.xda-developers.com/showthread.php?t=2003273
Where do I update CWM from? I have the rom manager installed, should I use that?
Click to expand...
Click to collapse
Im not sure about updating cwm, because i changed it to ext4 recovery after cwm 5.0.70 that came with aahk cannot do backup correctly for me.. but if you would like to try ext4 recovery, you can find it in google play.. and it is very easy to install it..
Sent from my Desire HD using xda app-developers app
yumm91 said:
Im not sure about updating cwm, because i changed it to ext4 recovery after cwm 5.0.70 that came with aahk cannot do backup correctly for me.. but if you would like to try ext4 recovery, you can find it in google play.. and it is very easy to install it..
Sent from my Desire HD using xda app-developers app
Click to expand...
Click to collapse
Thanks for the replies, sorry I was busy over the weekend.
I tried booting 4.2.x with no SD, and same error occurs.
I am not interested in trying 4EXT, CWM is a widely used custom recovery I can't see why this could be at fault? I am running the latest version, though not the "touch" version!
Can't find anyone else with this issue!
BTW - I am S-ON?
Any further help or advice on this one?
Thank you.
I would try 4ext. CWM has had some problems on thus phone in the past. Also, if you are S-ON, are you fastboot flashing the boot.img? Check the Ace Think Tank thread in the General forum for a guide on how to do that. Though usually, not doing that results in a phone that hangs at the splash screen, not one with systemui stopping...
I am looking forward to flashing MIUI V5 on my AT&T Samsung Galaxy S3. It's a 4.1.2 ROM. I am currently using JellyBAM ROM V7.7.0 which is a 4.2.2 ROM. Can I flash MIUI V5 from JellyBAM? Will my phone end up toasted?
-Thanks for any help!
yes you can. when transitioning android versions you must do a full wipe including system and data before flashing. be sure you've made a backup and have all your personal data saved to your micro sd card, computer or both. from the guide:
In CWM:
Select Wipe data/factory reset
Select Wipe Cache
Select Advanced and Wipe Dalvik Cache
Select Mounts and Storage and format /system
If you are transitioning from 4.1 to 4.2 or 4.2 to 4.1, you must also format /data. You will lose all personal data so back it up first.
In TWRP:
Select Wipe
Select Factory Reset and wipe
Select System and wipe
If you are transitioning from 4.1 to 4.2 or 4.2 to 4.1, you must also select Data and wipe. You will lose all personal data so back it up first.
galaxys3world said:
I am looking forward to flashing MIUI V5 on my AT&T Samsung Galaxy S3. It's a 4.1.2 ROM. I am currently using JellyBAM ROM V7.7.0 which is a 4.2.2 ROM. Can I flash MIUI V5 from JellyBAM? Will my phone end up toasted?
-Thanks for any help!
Click to expand...
Click to collapse
If you flash the v5 in android development it's on 4.2.2
Sent from my Nexus 10 using xda premium
Guys,
Need your help. I am unable to install any Android 4.3 ROMs in my G Note II. I have tried PA 3.99, ProBam 4.4.1, etc. but all of them getting stuck right at the boot animation screen. Here is my status and what I've already tried:
CWM Touch Recovery v6.0.3.5 (latest one available with 4.3 support)
Tried Android Revolution HD Super Wipe Script
Tried Factory Reset + Wipe Cache Partition + Wipe Dalvik Cache
Tried formatting Internal Storage
Tried the method: Factory Reset + Install ROM + Clear Cache/Dalvik + Install GApps + Clear Cache/Dalvik
Tried multiple wipe cache + wipe dalvik cache combinations as suggested in forums
Still no dice. I am stuck at the boot animation screen. If I install any 4.2.2 or 4.1.2 ROMs, all goes perfectly fine.
I had installed a 4.3 ROM previously, then reverted back to 4.2.2 for stability. Now I want to try 4.3 ROMs since they are much more usable now.
Any help is much appreciated. Thanks in advance.
-Vikas
vikasvishnu said:
Guys,
Need your help. I am unable to install any Android 4.3 ROMs in my G Note II. I have tried PA 3.99, ProBam 4.4.1, etc. but all of them getting stuck right at the boot animation screen. Here is my status and what I've already tried:
CWM Touch Recovery v6.0.3.5 (latest one available with 4.3 support)
Tried Android Revolution HD Super Wipe Script
Tried Factory Reset + Wipe Cache Partition + Wipe Dalvik Cache
Tried formatting Internal Storage
Tried the method: Factory Reset + Install ROM + Clear Cache/Dalvik + Install GApps + Clear Cache/Dalvik
Tried multiple wipe cache + wipe dalvik cache combinations as suggested in forums
Still no dice. I am stuck at the boot animation screen. If I install any 4.2.2 or 4.1.2 ROMs, all goes perfectly fine.
I had installed a 4.3 ROM previously, then reverted back to 4.2.2 for stability. Now I want to try 4.3 ROMs since they are much more usable now.
Any help is much appreciated. Thanks in advance.
-Vikas
Click to expand...
Click to collapse
try with philz recovery 5.11.2 latest recovery its the best
4.3 install
vikasvishnu said:
Guys,
Need your help. I am unable to install any Android 4.3 ROMs in my G Note II. I have tried PA 3.99, ProBam 4.4.1, etc. but all of them getting stuck right at the boot animation screen. Here is my status and what I've already tried:
CWM Touch Recovery v6.0.3.5 (latest one available with 4.3 support)
Tried Android Revolution HD Super Wipe Script
Tried Factory Reset + Wipe Cache Partition + Wipe Dalvik Cache
Tried formatting Internal Storage
Tried the method: Factory Reset + Install ROM + Clear Cache/Dalvik + Install GApps + Clear Cache/Dalvik
Tried multiple wipe cache + wipe dalvik cache combinations as suggested in forums
Still no dice. I am stuck at the boot animation screen. If I install any 4.2.2 or 4.1.2 ROMs, all goes perfectly fine.
I had installed a 4.3 ROM previously, then reverted back to 4.2.2 for stability. Now I want to try 4.3 ROMs since they are much more usable now.
Any help is much appreciated. Thanks in advance.
-Vikas
Click to expand...
Click to collapse
It looks like you need to include a wipe of system partition when you perform the full wipe procedure, or as just recommended using philz recovery, use the wiped data/factory reset: Clean to install a new rom.
Blafer said:
It looks like you need to include a wipe of system partition when you perform the full wipe procedure, or as just recommended using philz recovery, use the wiped data/factory reset: Clean to install a new rom.
Click to expand...
Click to collapse
I got nandroid backups taken using CWM. I believe, if I move over to Philz, I might loose the ability to restore them, right?
No other method to do this using CWM? I can try formatting /system if required.
vikasvishnu said:
I got nandroid backups taken using CWM. I believe, if I move over to Philz, I might loose the ability to restore them, right?
No other method to do this using CWM? I can try formatting /system if required.
Click to expand...
Click to collapse
AFAIK PhilZ recovery can restore CWM backups. To be sure you can create a new Nandroid backup after installating PhilZ recovery.
(TWRP is the best for me )
Anyway do you flash a custom kernel or a mod/theme?
Primokorn said:
AFAIK PhilZ recovery can restore CWM backups. To be sure you can create a new Nandroid backup after installating PhilZ recovery.
(TWRP is the best for me )
Anyway do you flash a custom kernel or a mod/theme?
Click to expand...
Click to collapse
Nope, I never go for customer kernels or themes. Happy with default kernels.
I see.. Lemme try Philz recovery and wipe the system and retry installing PA 3.99.
vikasvishnu said:
Nope, I never go for customer kernels or themes. Happy with default kernels.
I see.. Lemme try Philz recovery and wipe the system and retry installing PA 3.99.
Click to expand...
Click to collapse
That worked! I installed Philz recovery and used the "Clean to install a new rom" option under "wipe data/factory reset".
Basically, I had to wipe the /system partition. I was under the impression that it was /sdcard. But now in love with Philz Recovery with all those options, along with the goodness of CWM Recovery.
Thanks a ton for all who helped!
Happy for you