Develop Bugs

[Q] N00b updating Custom ROM

I have installed MildWild CM-2.7 on my Desire but there is now MildWild CM-2.8 and I can't find a guide how to install/update my Desire.
I have got S-OFF and recovery by Revolutionary The guide I followed to S-OFF and ROOT
This is the ROM I using. MildWild CM ROM

Just flash it via recovery like you did with the previous version

Will flashing the new version cause me to loose everything on my current version I.e apps and data etc??
Thanks for the reply though

do back up first, wipe davik+cache and flash it... it should work if not do full wipe and restore back up
just post any result we will move from there

What should I use to hackup TIbackup? Or is there a better one that you reccomend?
Wh000sher

Titanium and recovery. All basic stuff. Have a,read of my rooting faq in my signature. Tells you everything you need to know
Sent from my HTC Desire using Tapatalk

rootSU said:
Titanium and recovery. All basic stuff. Have a,read of my rooting faq in my signature. Tells you everything you need to know
Sent from my HTC Desire using Tapatalk
Click to expand...
Click to collapse
Do I only restore the Titanium I am guessing, as restoring recovery would revert back to my current ROM? and I have thanks

Yes indeed. With titanium, only restore "missing apps with data".
Theres a guide Angusc wrote here:
http://forum.xda-developers.com/showthread.php?t=1480343

ROM Manager can make updating so much easier - well worth the investment.

JohnHarrisNZ said:
ROM Manager can make updating so much easier - well worth the investment.
Click to expand...
Click to collapse
I can't speak for other devices but for Desire, nope it's not worth the time and money.

kotag82 said:
do back up first, wipe davik+cache and flash it.
Click to expand...
Click to collapse
So I'm only wiping the davik cahce correct?
Not anything else or have I missed something?

Wh000sher said:
So I'm only wiping the davik cahce correct?
Not anything else or have I missed something?
Click to expand...
Click to collapse
Things I've learned with all this flashing that may be helpful for you.
1. Before flashing, always backup your current system up. nandbackup via recovery, titanium for your apps, sd card if really needed for that you need to do.
2. If flashing an updated version of same rom, wipe cache and dalvik only on your recovery (unless explicitly specified by dev to make a full wipe.)
3. If you are having weird issues after upgrading the same rom, do a full wipe and start fresh. If issue is not resolved, report the issue to the Dev's thread.
4. Do a Full Wipe on recovery (System/factory, cache, dalvik if coming from a different rom).

stankyou said:
Things I've learned with all this flashing that may be helpful for you.
1. Before flashing, always backup your current system up. nandbackup via recovery, titanium for your apps, sd card if really needed for that you need to do.
2. If flashing an updated version of same rom, wipe cache and dalvik only on your recovery (unless explicitly specified by dev to make a full wipe.)
3. If you are having weird issues after upgrading the same rom, do a full wipe and start fresh. If issue is not resolved, report the issue to the Dev's thread.
4. Do a Full Wipe on recovery (System/factory, cache, dalvik if coming from a different rom).
Click to expand...
Click to collapse
Thanks for the reply.
In response to 2. I am using ClockworkMod as my Recovery and I am guessing you mean I have to wipe 'cache partition' and 'wike dalvik cache' under advanced?
I am creating a guide to help fellow N00bs how to update a rom and change between ROM's
Wh000sher

Wh000sher said:
Thanks for the reply.
In response to 2. I am using ClockworkMod as my Recovery and I am guessing you mean I have to wipe 'cache partition' and 'wike dalvik cache' under advanced?
I am creating a guide to help fellow N00bs how to update a rom and change between ROM's
Wh000sher
Click to expand...
Click to collapse
Yes if I remember correctly there are the first three lines on that recovery is wipe system, cache partition (like you stated), and wipe dalvik. So if upgrading just wipe cache partition and dalvik cache.
System partition is where the "Android OS" resides. Wiping it is like formatting your computer. Most of the time, incremental updates of the same rom requires you to wipe just the cache partition and dalvik, otherwise if the rom update has a lot of changes, the dev might require you to wipe all three options on the recovery.

Having wiped my cache and dalvik cache. I am now wanting to install the new version. On the main screen I have 2 options which are tempting to click.
One is 'Apply update from SD card' and the other is 'Install zip from SD card'
I am unsure of which to choose but my gut instinct is to go with 'Install zip from SD card', is this correct or am i going to make a terrible mistake?
wh000sher

Install zip from SD

[Guide] CWM Touch JB Backup/ Restore and Flash new ROM

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

Superwipe question?

Is it only necessary when coming from ICS to JB or is it necessary to do when coming from a JB ROM to another JB ROM? In my SGS2 days it was factory data wipe, wipe cache, wipe delvik cache, and maybe a kernel cleaning script for good measure, but never touched my SD user content( PDFs, music, etc.).
Super wipe will erase everything( as indicated by the warning in CWM), if you don't think it did cuz you still see the files, try and open them, its a shell only, no content (still lists correct file sizes though???)
I found this out by trying to flash some alternate ROM firmware or kernels I had but couldn't get them to work.

Don't use those stupid superwipe .zip's.
They're running the same scripts as your recovery runs...potentially multiple times for the "LULZOMGCLEAN" factor. [Uh...not needed]
Even installing a rom wipes /system...but %90 of people say "lul wipe /system/ /data/ /cache/ /dalvik/ and then flash superwipe..."
(Yes, I realize a script has to be run for the .zip to wipe system...and the Rom dev MAY leave it out. Personally, if the developer of my rom doesn't even make a "wipe system" script in the .zip I would not use that rom.)
NOT necessary.
If you don't trust your recovery to do it's job...wipe everything with one wipe...
Maybe you should get a new one.

Jubakuba is right but rather than assume the ROM zip wipes /system I find it easier to just wipe it. I never have the problems that others do when they flash ROMs and I always do a factory reset from recovery and wipe system. And if a ROM requires Gapps I always reflash the Gapps after a new ROM update. May not be needed but has saved me from problems before and only takes a couple seconds. Wipe zips are for chimps.

jesusice said:
Jubakuba is right but rather than assume the ROM zip wipes /system I find it easier to just wipe it. I never have the problems that others do when they flash ROMs and I always do a factory reset from recovery and wipe system. And if a ROM requires Gapps I always reflash the Gapps after a new ROM update. May not be needed but has saved me from problems before and only takes a couple seconds. Wipe zips are for chimps.
Click to expand...
Click to collapse
You have to flash Gapps after flashing a rom as they reside in /system/
FYI!

Jubakuba said:
You have to flash Gapps after flashing a rom as they reside in /system/
FYI!
Click to expand...
Click to collapse
Right. Many ROMs like CM are supposed to have a script to preserve Gapps and they say that you don't need to flash Gapps after, say, updating to a new nightly but I've learned the hard way not to depend on it.

Making an wipe script flashable zip

Hello there,
I was thinking to make a flashable CWM script that eliminates the necessary steps before changing a Rom. He script should have this content:
/format data
/format cache
/format system
/format Dalvik cache
Would it work? If yes has anyone such a similar script and share it please?
Thanks

First of all, wiping dalvik and system is redundant.
Wiping data wipes dalvik (/data/dalvik)
Also, when you flash a tom, it automatically wipes /system unless you're flashing an incremental update.
So why do you want this script when you have to push like 2 buttons anyway (factory reset/wipe data and cache)? The red be more trouble migrating to the flash able to wipe stuff than going to the wipe menu.
Sent from my Galaxy Nexus using Tapatalk 2

geoffcorey said:
Also, when you flash a tom, it automatically wipes /system unless you're flashing an incremental update.
Click to expand...
Click to collapse
no. the rom you're flashing has to have the script to wipe system (most do, but there are some that do not)

Zepius said:
no. the rom you're flashing has to have the script to wipe system (most do, but there are some that do not)
Click to expand...
Click to collapse
If it doesn't wipe system to install the rom, then I don't know what you think it would be installing....I would question that 'dev ' that does that.
Sent from my Nexus 7 using Tapatalk 2

Zepius said:
no. the rom you're flashing has to have the script to wipe system (most do, but there are some that do not)
Click to expand...
Click to collapse
If the ROM doesn't wipe /system, then most likely you're flashing an incremental upgrade, or the dev doesn't know what in the world he's doing and you should probably steer clear of said ROM.
Also, AFAIK, all the gnex ROMs here at xda, rootzwiki, and cyanogenmod wipe /system.
Sent from my Galaxy Nexus using Tapatalk 2

I understand the knowledge shared here but better be safe and follow all four steps then be not sure? Or not?
Can someone help by providing such script please?

Search for the Android Revolution ROM in the dev section. IIRC they have some kind of script in the OP

Anyone can pass Wipe Script Flashable ZIP me to flash (for Baked ROM)?
Thanks!!

There's no need to wipe until after you're done

Flashing a ROM (JellyTime)

I got a simple question about flashing a rom, at this point its JellyTime.
I'm not really familiar with the order that you need to flash and if you need to flash the kernel separately?
My order is now:
- clean/wipe
- Flash ROM
- Flash gapps
- fastboot flash boot.img (is this step required, or does this already happen when flashing the ROM?)
Then the follow-up question is, does it affect the ROM when you boot the first time with an older kernel?

Spluh said:
I got a simple question about flashing a rom, at this point its JellyTime.
I'm not really familiar with the order that you need to flash and if you need to flash the kernel separately?
My order is now:
- clean/wipe
- Flash ROM
- Flash gapps
- fastboot flash boot.img (is this step required, or does this already happen when flashing the ROM?)
Then the follow-up question is, does it affect the ROM when you boot the first time with an older kernel?
Click to expand...
Click to collapse
You can flash the kernel basically anytime. I usually dirty flash kernels with no problem.
Also, no need to fastboot the boot.img. The rest of your order looks fine.

My order :
- format all partitions (except sdcard)
- wipe cache/dalvik
- Flash ROM
- Flash gapps
- fixing permissions
- Reboot
But i think your steps should be fine as well.
Sent from my Desire HD using xda premium

How do you fix permissions ?
When I flashed gapps I saw that in the end its fixing permissions. Do I need to something manually ?

Kobibo said:
How do you fix permissions ?
When I flashed gapps I saw that in the end its fixing permissions. Do I need to something manually ?
Click to expand...
Click to collapse
You can fix permissions using recoveries like 4ext and stuff...remember to wipe cache and davlik if you are flashing just kernel.

Like he said use recovery 4ext there's an option at "tools".
[ Sent from my HTC Desire HD using XDA-Premium App ]

RayRayX91 said:
My order :
- format all partitions (except sdcard)
- wipe cache/dalvik
- Flash ROM
- Flash gapps
- fixing permissions
- Reboot
But i think your steps should be fine as well.
Sent from my Desire HD using xda premium
Click to expand...
Click to collapse
Wiping cache+dalvik cache is redundant after formatting all partitions. A lot of people have this habit and recommend it, but its unnecessary. Dalvik-cache is located in the data partition. It's nothing special, its a folder there like any other, and contains classes.dex files for all apps on the device. When you format all partitions, data is formatted, so the dalvik-cache is wiped along with it. And the cache partition is formatted anyway. So wiping cache+dalvik again after formatting all partitions is of no use and unnecessary.
ai6908 said:
You can fix permissions using recoveries like 4ext and stuff...remember to wipe cache and davlik if you are flashing just kernel.
Click to expand...
Click to collapse
You don't need to wipe cache and dalvik after flashing a kernel. I used to do it too, but many times the devs themselves have said it isn't required. Lord Clockan said many times that wiping cache+dalvik is unnecessary after flashing a new kernel. When you think about it, it makes sense. Dalvik cache just contains classes.dex files for all the apps on the device and nothing else. When the dalvik-cache is rebuilt after a wipe, it pulls the classes.dex from each apk and puts it in the dalvik-cache folder (please correct me if I'm wrong). This isn't in any way related to the kernel and what it does. Regardless of the kernel flashed, the dalvik cache will remain the same. So it shouldn't make sense to wipe it for every kernel flash.
Sent from my Desire HD using xda premium

RayRayX91 said:
My order :
- format all partitions (except sdcard)
- wipe cache/dalvik
- Flash ROM
- Flash gapps
- fixing permissions
- Reboot
But i think your steps should be fine as well.
Sent from my Desire HD using xda premium
Click to expand...
Click to collapse
Hello, I did all of the steps in this order and ROM is booting OK. But after that I have random freezes while doing different tasks (taking picture, going to settings, after unlock). Do you have any suggestions what can I do/change to fix this. This is happening on all Jelly Time releases - i tried R3, R4, R5.1 and also AOKP V6. When I flash IcoColdSandwich everything is running without problem.
I will appreciate your help. Thank you!

My order :
- wipe data/factory reset
- wipe cache
- wipe dalvik
- Flash ROM
- Flash gapps
- fixing permissions
- Reboot

Thanks, that makes it clear.
So its possible that you flash the kernel when you are flashing the ROM!