[How To] Preparing yourself for a wipe data/factory reset in Clockwork Recovery

Ha! My one claim to fame! Now back to the real world of relative Android newbie-ism.

Well, for examples of maintaining the ROM, the new TSM Parts under Settings in the new EF ROM stays, I think. (or did I flash that?) Baseband and Build number both still contain ED01 after restoring data from previous ROM over ED01. (I used the Anrynalyne method, not OTA ED01).

What else would be a good thing to check?

I kind of like Launcher, fromm Com Rom and EF, and now what I think is Launcher2, but this is where I began to wonder if my Nandroid Data backup might be overwriting some of the ROM launcher stuff. Because I don't know how to tell if I have Launcher2 or not.

I believe my evolution path has been:
Stock
Odin DB/DO tar
EC01 DB/D0 (zip i think, can't remember)
ED01 (Adrynalyne)
ComROM 1.0 zip
EF, all variants in sequence. zip

Oh, and I wipe like crazy, includiing data. Lately, triple wipes, but I think that is overkill. (did triple wipe originally mean wipe all 3 places? or 3 times each?)

Whenever I started flashing through CWR, shortly after (perhaps immediately) I started doing Nandroid Backups, and found Advanced Restore/ Restore data. Used it ever since. TB is pretty flexible, but also pretty convoluted. Based on your writeup, though, I am trying My Backup again as a more straight forward alternative. (I even wonder if it doesn't do many of the same things as Nandroid.)

I think I will try flashing the new MIUI Hybrid over at XDA, with a number of different backups, My Backup first, then Nandroid Data, and see what I get.

I think with Android (minus the Fascinate-ing tendency to write the file structure poorly, as I understand, and to create unusual dependencies) it should be possible to stucture the files such that a very clean batch User Data backup could be obtained. Making flashing so easy some of us junkie's won't know what to do betweeen flashes. (actually using our phones instead of tweaking them?) :p Here's hoping I am right.

PS: nothing thick about your head


Thanks for the info! Now, here we go..

I need to know where your nandroid backup was initially made from that you are restoring...was it from your "stock" ECLAIR or FROYO? Which ROM are you restoring from?

With that said..

TSM parts is actually an application and could have been backed up/restored with your "data" in nandroid....It is also a part of ComRom and EF..so that doesn't give me any information. it should show up in a EF and KB rom as its included in both roms...

We can't use TSMparts to tell..I can't tell if it saves the .apk and restores it or if it is restoring it with the Rom..

Baseband and build number won't change unless you change your modem(baseband) and you switch from stock ECLAIR (DL09, EA28 etc) to FROYO (EB01, ED01,EC10)..

If your initial advanced nandroid backup was made from an ECLAIR build, and you restored it over a FROYO ROM (which all the ones listed are) and the build number stays ED01..your on to something..

However if your restoring a adv nan bu from a ED01 build on to another ED01 build, you can't look at this. It's going to be ED01 no matter what..they're all ED01 builds. This doesn't mean it isn't restoring the Rom..


I don't know anything about Launcher 2, and the info you gave me is hit or miss, so we can't use that either to test this out.


Here's what to do if you want to know if it's replacing your Rom...or parts of it.

Follow whatever steps your taking to backup with nandroid with EVIL Fascination or another Custom ROM installed. It doesn't matter which one, just make sure its a ED01 build.

Wipe caches, and wipe data...

Flash this if your currently voodoo..
super_frankenclean_2_9_2v.zip

Let it boot all the way...take note of the build number should be (EB01 or EC10 or something)

Then reboot to recovery and do your advanced nandroid data restore..

Reboot to phone.. (if it boots at all :) )

See if the superclean stuck.. (there should be something in the pulldown that says SC2.9.2).

See if the build number is still EB01 or whatever it was before the restore...

Check to see if TSM parts is there..

Try this and let us know what you find!

If it doesn't boot at all..

Three button to boot to recovery and then just do a full nandroid restore and you should be back to where you were before you started the testing..

Good luck and please let me know what you find.
 
I guess you would have to say the backup is cumulative, ever since I have been working with CWM, which would have started after Froyo. I always create a new Nandroid backup before I flash.

Let's just do this thing! I will get back with the results. Downloading SC 292.
 
Oops, that ROM appears to need edify scripting. CWM aborted it. Other ROM suggestions? I will be looking for one to try.
Or look for a 2.51 CWM?

Oh, do I need to worry about my ED01 Modem?
 
Last edited:
OK! I am sitting pretty with same Build info before and after Nandroid Advanced Restore/Restore Data:
SC292 up at the top (but in my font now)
Build EB01
Kernel 2.6.32.9
Firmware 2.2.1

All the above did not change after Nandroid Data restore.

TSM must have been part of the ROM, it is no longer found in Settings.
Launcher 2 and associated widgets are no longer there as they were also part of the older ROM. I remember that I had to redo all the widgets especially for Launcher 2.
But my wallpaper is back.

This is a pretty cool ROM, I never actually tried any of the SC. My loss.

All my apps, contacts, data, as far as I can tell are all there.

I am ready to try MIUI now.
 
  • Like
Reactions: Lttlwing16
Thanks man!! I'll look into this some more.

This looks like a very good thing for everybody. Obviously it has worked for you..

Just to confirm...you did restore the data from your ED01 build, correct?
 
I've been sort of busy lately and have been trying to catch up on anything I've missed. Is there a latest version of CWM? I currently have 2.5.1. or CWM Red.
 
there is a newer version streebs..3.x ...it's edify only.

2.5.2 3-30 Gizmodroid fix all is what I roll. It will flash amend and edify.. not sure the benefits of only edify.

The link to the new cwm is in Jaekar's thread I believe if you want to try it out.
 
  • Like
Reactions: stilltipin87
Thanks man!! I'll look into this some more.

This looks like a very good thing for everybody. Obviously it has worked for you..

Just to confirm...you did restore the data from your ED01 build, correct?

Correct. I restored the data from my latest (earlier today) Nandroid backup, made while running full ED01 with the EF 3.5.1. On top of the SC 2.9.2.

Now I did wipe cache and Dalvik before making the backup, just in case.
 
  • Like
Reactions: Lttlwing16
there is a newer version streebs..3.x ...it's edify only.

2.5.2 3-30 Gizmodroid fix all is what I roll. It will flash amend and edify.. not sure the benefits of only edify.

The link to the new cwm is in Jaekar's thread I believe if you want to try it out.

Nice, thanks!
 
Lttlwing16,

Should I start another thread, rather than semi-hyjack this one? It is definitely related, but may get in the way.

Let me know.

Anyway, times_infinity had a comment over in XDA: "Wiping data and dalvik cache is kinda pointless because it gets overwritten and replaced by the restore anyway. Dalvik cache is located in the data partition, not the cache partition, ironically."

My thinking is that wiping before the backup means the caches will come back blank in the restore, and the new ROM will fill them in from scratch without any confusion from the old ROM. Possibly something similar could happen by bringing back the data and apps after the new ROM boots. I really have only a vague idea of how this all works, but it makes sense, and there does seem to be a reason why my flashes go so smoothly.
 
there is a newer version streebs..3.x ...it's edify only.

2.5.2 3-30 Gizmodroid fix all is what I roll. It will flash amend and edify.. not sure the benefits of only edify.

The link to the new cwm is in Jaekar's thread I believe if you want to try it out.

It seemed from what I was reading that there were some improvements in the later versions, avoiding problems under certain conditions, but I am glad I hung on to this version for amend compatibility. When I tried to install it via zip, though, it didn't seem to take. Thanks for the Odin direction, which did the trick.
 
It seemed from what I was reading that there were some improvements in the later versions, avoiding problems under certain conditions, but I am glad I hung on to this version for amend compatibility. When I tried to install it via zip, though, it didn't seem to take. Thanks for the Odin direction, which did the trick.

The older versions of CWM (pre 3-30) had a problem with mounting memory correctly and restoring backups was likely to lead to a force close loop.. some of us abandoned the 2.x versions.. I know that the new 3.x versions from times_infinity have an option to clear voltage settings if you have saved Voltage Control settings for boot and they are causing issues..

The newer versions only accept the edify scripting vs the older taking both.. Given you use the versions that Lanshark and Gizmodroid worked up you should be fine with backups and restores..

Be careful of older versions and the versions downloaded with ROM Manager have been know to cause problems.. (DON'T mess with Green CWM)..
 
@robtao

Feel free to start your own thread! I don't have the experience with this like you do.A dedicated thread will help with diagnosing etc, and bring more testing to the table.Trust me, there will be plenty of takers!

I plan on trying this out when the next version of KB comes out!

Strong work!
 
  • Like
Reactions: Robtao
Once you get some takers, testers, absolutely iron out a process, and can answer specific questions....i'll amend this thread with your process and a ink to yours...
 
I found a thread from another forum about restoring. I'm trying it now because I was getting some FCs for some reason. I thought I would start from scratch with the ComRom 1.3. Let me know what you think of the process outlined in the first message in the thread.

Please note that the ROM referred to in that thread is one that contains Titanium Backup Pro. Since the ComRom does not, you'll want to have it on your SD card before trying to restore. I did that by before installing the new ROM, used the TiBu option to create an "Update.zip" file. Create one that works with the recovery method on your phone (Amend or Edify). It will be stored in the root directory of your SD card. After clearing cache, data, installing the ROM, et.al., I ran the TiBu install (the zip file I created) so it would be installed on my phone without my having to attach to Google and download it from the Market. Then I followed the steps outlined in the other forum. I'm still in the process of restoring so I can't say if it works better or not than the method in this thread.
 
A lot of peope's have had problemo's restoring app data from TiBU, thusly why I suggets only restoring the app data that you really need.. i.e. notepad, etc.. stuff you would miss otherwise. According to Jaekar it has to do with the permissions. If you try fixing permissions in CWM it may help.

OR

If you try restoring the apps and data selectively you'll have better luck. Thusly why I like MyBUp vs TiBU..you can batch restore just the apk's and then go back and selectively restore data....can't do that with TiBU..
 
Re: [How To] Preparing yourself for a wipe data/factory reset in

How do I unfreeze my fascinate and continue to reset to factory settings.
 
Re: [How To] Preparing yourself for a wipe data/factory reset in

footnote:
It froze up after updating to gingerbread.