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
I want to flash the deodexed LJC stock rom to do the multi window mod hack. The problem is that I don't want to have to re-do everything on my device. Is it possible to just flash the deodexed stock rom over my current root stock rom? I don't think I've ever had to do this on any of my Androids and I have never asked. Any help or answers are definitely appreciated. :good::good::good:
Shouldn't be a problem as current system would be wiped beforehand. Data however wouldn't be touched. I would wipe cache&dalvik-cache before the flash just to be cautious.
billard412 said:
Shouldn't be a problem as current system would be wiped beforehand. Data however wouldn't be touched. I would wipe cache&dalvik-cache before the flash just to be cautious.
Click to expand...
Click to collapse
I prefer to wipe before and after flashes especially with twrp since it sticks the option right there for u. Somethings I only wipe after flashing tho like system mods and kernels. Going from ljc to ljc deodexed id flash the rom wipe caches and if u were using a custom kernel with stock flash it then wipe caches then fix permissions and reboot. If no kernel skip that step and continue on
So in summary:
1. Flash deodexed ljc
2. Wipe cache and dalvik
*3. Flash kernel
*4. Wipe cache and dalvik
5. Fix permissions
6. Reboot
7. Profit!!
* indicates optional steps
Sent from my SPH-L900 using Xparent ICS Tapatalk 2
Howdy y'all!
I'm currently running a 4.1.1 ROM, and would like to get on to MMuzzy's 4.2, but there are a ton of things I think I need to flash and want to make sure I get the order right. Your help will be much appreciated!
I am already using the latest version of TWRP.
I would like to flash the latest JB bootloader, and latest JB radios, but have never flashed either. Should I do these before flashing the ROM, or after? Should I do these before formatting cache? Should I format system or factory reset before flashing these, too?
I am planning to do factory reset, format cache and dalvik before flashing ROM, gapps and kernel. Do I need to do anything else to prep for flashing the ROM? Also, is it okay to flash all three at once, or should I do rom and gapps, let everything boot and restore from market, and only then flash kernel?
My main concern is the differences in file system between 4.1 and 4.2. I'm aware of the /0 subdirectory thing already, but I'd there anything else?
Thanks much!
Jamie
I wouldn't bother with the bootloader, but if you insist then you can flash the bootloader and the radios before or after. Doesn't matter.. Other than that, you do them ROM, gapps, kernel and I've done all three at once. Mmuzzy's is a good ROM. Enjoy.
First make a backup in TWRP
Factory reset
Wipe both caches
Install ROM, gapps, then kernel and reboot. (All at the sometime in that order)
I have heard its better to flash the kernel with the new ROM so just do it all in one flash.
Set everything up and let your phone sit for 15 minutes untouched and go for it.
Sent from my Galaxy Nexus using xda app-developers app
jrbedford said:
My main concern is the differences in file system tree between 4.1 and 4.2. I'm aware of the /0 subdirectory thing already, but I'd there anything else?
Thanks much!
Jamie
Click to expand...
Click to collapse
Just a small correction; file system change would mean switching from ext4 to f2fs, for example. That's not the case.
MartianCeo said:
First make a backup in TWRP
Factory reset
Wipe both caches
Install ROM, gapps, then kernel and reboot. (All at the sometime in that order)
I have heard its better to flash the kernel with the new ROM so just do it all in one flash.
Set everything up and let your phone sit for 15 minutes untouched and go for it.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Watch out with restoring backups. Don't restore app/system data. OP is switching major versions.
sent from my Google Galaxy Nexus
Hi all, I had flashed successfully before but wanted to flash to a JB rom. I wiped and flashed, but then it just keeps looping the Samsung load screen, then I see the loading bar... and it reboots and goes back to the loading bar... Did I mess something up? Or is it suppose to do this the first time?
Sometimes it gets as far as the t-mobile 4G screen and the loops back again...
Thanks
What did you wipe?
Sent from my SGH-T989 using xda app-developers app
And what did you wipe with?
If you used an older clockwork mod recovery, you probably need to update your recovery or get one of the updated wipe scripts on this forum.
Sent from my Nexus 7 using Tapatalk 4 Beta
Have some question for you:
1/ What JB rom you flash?
2/ What recovery mod u used? (TWRP or CWM?)
3/ Did u wipe data / wipe cache / wipe devil ???
nguyenduytan said:
Have some question for you:
1/ What JB rom you flash?
2/ What recovery mod u used? (TWRP or CWM?)
3/ Did u wipe data / wipe cache / wipe devil ???
Click to expand...
Click to collapse
I tried to flash Infamous S2 as well as Jedi Mind Trick. After more reading, I also flashed the "wipe" zip file that was linked. After I flashed that clean wipe, all is well. For some reason when I did the usual wipe wipe (with CWM), stuff probably didn't get over written.
All is well and working smoothly now with Jedi Mind Trick
sky322 said:
I tried to flash Infamous S2 as well as Jedi Mind Trick. After more reading, I also flashed the "wipe" zip file that was linked. After I flashed that clean wipe, all is well. For some reason when I did the usual wipe wipe (with CWM), stuff probably didn't get over written.
All is well and working smoothly now with Jedi Mind Trick
Click to expand...
Click to collapse
it's a combination of how partition gets accessed vs custom recovery(in this case type of wipe) that cause that bootloop.
Provided you didnt have a bad download(.zip bein flashed) If it's a custom ROM suffice to say u need Darkside super wipe.
Unless its a stock (modded) ROM then Infamous super wipe is the way to go.
Hit thanks if/when it helped.
Hi,
I got the rooted, deodexed, and debloated version of the latest stock rom.
After I flashed it, I keep getting the error messages "unfotunately the process ... has stopped unexpectedly". I used CWM to flash this rom multiple times. I also wiped data/factory, cache, and dalvik cache. I saw some others are reporting the same error.
I was wondering if there is a solution for this out there.
Thanks
Did you try infamous superwipe and cache wipe? Check the sticky in the development thread.
gc84245 said:
Did you try infamous superwipe and cache wipe? Check the sticky in the development thread.
Click to expand...
Click to collapse
No I didn't try the infamous superwipe. I will do it. What is cache wipe, is it same as the option in CWM recovery mode?
I don't know much about how they work, but it's the only way I could get the stock rom to work, so it might work for you too. Just flash them both instead of wiping the normal way. I think one wipes data and one wipes cache, more info in the thread.
gc84245 said:
I don't know much about how they work, but it's the only way I could get the stock rom to work, so it might work for you too. Just flash them both instead of wiping the normal way. I think one wipes data and one wipes cache, more info in the thread.
Click to expand...
Click to collapse
Ok, BTW, I moved from Juggernaut 5.0 to JB Stock using ODIN and it worked fine. It's the rooted version of the JB Stock that gives me these errors. In fact, the main reason that I tried rooted version is because it supposedly doesn't have bloadware either.
Well using odin removes more than flashing a zip, for example it replaces your recovery. I'm not an expert and don't know much about the details, but that's probably why it worked using odin.