[Q] Create ODIN backup with CWM? - Verizon Droid Charge

There is an option in CWM under Advanced to create an ODIN backup for personal use. I chose it and it created an ODIN package for me. But, I cannot find it. There is a file on the root of my sdcard called "101920111542.tar.md5" but it has a 0kb filesize. I do not see any odin packages under the clockworkmod folder.
Any tips/tricks/ideas?
Using CWM 4.0.0.8.

dhenryrmu said:
There is an option in CWM under Advanced to create an ODIN backup for personal use. I chose it and it created an ODIN package for me. But, I cannot find it. There is a file on the root of my sdcard called "101920111542.tar.md5" but it has a 0kb filesize. I do not see any odin packages under the clockworkmod folder.
Any tips/tricks/ideas?
Using CWM 4.0.0.8.
Click to expand...
Click to collapse
Two points here. First is that is not an Odin backup...it's a nandroid backup for use by CWM. Second, that function does not work properly in 4.0.0.8 and will cause a bootloop if you try to restore. Only the newest CWM, the orange CWM dated 8/17 with the banana in the background (version 4.0.1.4 I think) will work for backup and restore.

You are talking about the "Backup and Restore" function. But, if you go to Advanced, there is an option that says "Create ODIN backup". If you select that, you have to confirm on a line that says "Yes - take a dump". Then you see a black screen with white text, telling you that it is performing the backup and it is going to take several minutes.
Yes, the backup and restore option does cause a bootloop. However, this is not the option I am talking about.
Is CWM 4.0.1.4 the official release for the Droid Charge (any phone)? I use ROM Manager (they make CWM) to flash CWM and it says I have the most current version. Also, I don't see reference to it anywhere in the Droid Charge development forums. I THINK I use CWM 4.0.0.4 on my Galaxy Tab 10.1, and the backup/restore function performs properly.

dhenryrmu said:
You are talking about the "Backup and Restore" function. But, if you go to Advanced, there is an option that says "Create ODIN backup". If you select that, you have to confirm on a line that says "Yes - take a dump". Then you see a black screen with white text, telling you that it is performing the backup and it is going to take several minutes.
Yes, the backup and restore option does cause a bootloop. However, this is not the option I am talking about.
Is CWM 4.0.1.4 the official release for the Droid Charge (any phone)? I use ROM Manager (they make CWM) to flash CWM and it says I have the most current version. Also, I don't see reference to it anywhere in the Droid Charge development forums. I THINK I use CWM 4.0.0.4 on my Galaxy Tab 10.1, and the backup/restore function performs properly.
Click to expand...
Click to collapse
Hmmm...haven't used that option, and I don't think it's present in 4.0.1.4. As fare as an official ROM Manager CWM release, I don't think there has actually been one. There's been some reports that there is one that will install, but it's less functional than the ones imnuts put together.

I checked clockworkmod.com and the official version for Samsung Charge installs as 4.0.0.8. I know there are problems with Backup/Restore. I can create backups just fine, but it definitely doesn't restore correctly. I just wanted to explore the ODIN feature to see if it works, but maybe it doesn't. It would be nice to have a full personal ODIN file so if I dont like a ROM, I can restore to a previous mode.
I can see if the CWM team has any answers for this. 4.0.0.8 is a teal color (wish it was customizable). Are you sure it's a banana for the watermark? My tab has the orange one and it works flawlessly.
Thanks for your input though. I appreciate it.

Related

Rom Manager backups my ROM, but it is not listed after reboot

Rom Manager will do a backup of my current ROM (seems to go through it OK just like on my HTC Incredible, but it is not listed after reboot. I can browse out with Astro and see all the backup rom directories with the names I've given them and files in their directories, but Rom Manager does not list them when I select Manage and Restore Backups. Any ideas why?
(I'm currently on TnT Lite v4.2.2)
I just discovered that it is listing 1 old backup. So I found that that listed backup is being stored on under sdcard, where as all the ones that are NOT showing up are being stored under sdcard2. Where/how can I point Rom Manager to sdcard2?
Also, checking the recovery.log, I jusr saw and remembered an error it displays while making the backup. "E:Can't mount /dev/block/mmcblk2p1 (or /dev/block/mmcblk3p1)" but it continues on and 'appears' to finish normally.
Thanks for any help.
Dont use Rom Manager with the GTab right now. Only use bekit 0.8 and enter recovery with the power/vol+. Rom Manager does not play nice with our tabs and it will cause problems.
aldar5 said:
Rom Manager will do a backup of my current ROM (seems to go through it OK just like on my HTC Incredible, but it is not listed after reboot. I can browse out with Astro and see all the backup rom directories with the names I've given them and files in their directories, but Rom Manager does not list them when I select Manage and Restore Backups. Any ideas why?
(I'm currently on TnT Lite v4.2.2)
I just discovered that it is listing 1 old backup. So I found that that listed backup is being stored on under sdcard, where as all the ones that are NOT showing up are being stored under sdcard2. Where/how can I point Rom Manager to sdcard2?
Click to expand...
Click to collapse
I may be incorrect, but I don't think ROM Manager identifies CWM recovery files. You would have to use CWM to locate and restore a backup that was performed with CWM.
Correct me if I am wrong guys. I use CWM only for backup and restore purposes. I have never used ROM Manager.
Sent from my VEGAn-TAB-v1.0.0B5.1 using Tapatalk
Well it seems if I can just point Rom Manager to the sdcard2/clockworkmod location that would fix it. Any ideas how to do that? Maybe I could delete the sdcard/clockworkmod dir and make it a link to the sdcard2/clockworkmod dir?
Seriously....don't use Rom Manager
thebadfrog said:
Dont use Rom Manager with the GTab right now. Only use bekit 0.8 and enter recovery with the power/vol+. Rom Manager does not play nice with our tabs and it will cause problems.
Click to expand...
Click to collapse
Thank you so much for your comment...I was about to use it to back up my Rom. You saved me a lot of time and effort
USE MANUAL
Sent from my ADR6300 using XDA App
Koush Ditta needs to support this device...
thebadfrog said:
Dont use Rom Manager with the GTab right now. Only use bekit 0.8 and enter recovery with the power/vol+. Rom Manager does not play nice with our tabs and it will cause problems.
Click to expand...
Click to collapse
+1
ROM Manager won't work correctly with GTAB.
The install from SDCard feature, backup current rom feature, and restore backup feature will only reboot the device without doing anything
You can perform backups and restores via recovery and then rename the files via ROM Manager if you like. CWM will see the renamed file in recovery.
Also, if you update the flash recovery and decide you need to revert to a backup for some reason afterwords, it may send your device into bootloop after restore. You will need to flash to a previous version in order for the restore to work correctly.
status of rom manager for viewsonic gtab
If you google "my brain hurts rom manager"
you'll find an img file for Rom Manager posted for the vs gtab.
anyone tried this yet ?

Rom manager Backup of stock rom

I'm hoping someone can help me here. I have rooted my infuse, I used the one click root method. I installed Ti backup and performed a backup of all my apps. I then downloaded Rom Manager latest version off the market. I told it to flash the galaxy i9000 information as thats what i had read was required. Now when I go to make a backup of my rom as it is, it restarts boots into recovery, all the top lettering is blue and says android system recovery, then it shows the options of reboot, reinstall packages,delete all user data, delete cache data, and format internal sd card.
below all this in yellow it shows a bunch of checksum confirmation, then not need cheksum confirmation, Mov1_check executed, update media finished, #MANUAL MODE#, appling multi-csc, installing multi csc, then it shows install defaul apk-files, please wait, then install default apk-files, finished.
at this point the phone just sits there and never reboots or anything. so i choose reboot the system and it does. I can find any backup of the rom on the external or internal sd card. I have both. did i do something wrong somewhere? am i missing the file in the structure somehow? thanks for all the help.
You have to update the recovery in order to use Clockwork. Right now you are in the stock recovery. Once you do it right you will see many more options and the CWM recovery screen (red letters). I am just a noob, so maybe someone more experienced can chime in here too. Here is a thread.. http://forum.xda-developers.com/showthread.php?t=1107881
Ok so basically I need to download that file, replace the recovery, then reinstall the package twice. Dies that sound right? Lol
Also, I really don't have Amy plans to install a. Custom rom, so a Ti backup would probably be enough anyway right??
Sent from my SAMSUNG-SGH-I997 using Tapatalk
Yes you will know when you are in Red Clockwork recovery, it looks way different than the blue stock one. Install the update twice and you should see it.
I would just do a batch backup of your apps and data with Titanium. You don't need a Nandroid backup really unless you are flashing roms or kernels and something goes wrong.

[Q] Problems with Nandroid advanced restore

I actually have two questions here.
I'm trying to do an advance restore of the data from a previous backup using CWM. recovery 5.0.2.7 and having some problems.
In recovery, when I click on 'advanced restore' I am told there are no files. I then choose the regular 'restore' option and it shows the files to choose from.
I can then go back one screen and select 'advanced restore' again and it will now display the list of backups. When I select a backup and try to restore the data, I get a MD5 mismatch error. This happens when I try to do an advanced restore with any of my backups, not just a certain one. Also, I can do a normal restore without any problems.
I tried this:
http://www.geekdevs.com/2011/10/solved-md5-mismatch-error-on-clockworkmod/
Then this:
http://forum.xda-developers.com/showthread.php?t=1606047
I've read several threads but most of them seem to be solved after trying one of the above methods. I also haven't seen any that describe the backup list not displaying at first.
Secondly, I found this problem because I'm running Pyr'o'Ice ICS Desensed 1.1.3 and stupidly tried to tether with wifi and my phone got stuck in a reboot loop. I want to restore the userdata via Nandroid recovery, but will that also restore the tether setting that causes that bug?
My main issue is with the Nandroid recovery, but I thought someone reading this might also know the answer to that question also.
Any help is greatly appreciated.
Edit: (didn't read whole post)
1. Open your sdcard on pc (usb mounted)
2. ensure there is a folder in clockworkmod/backup (ex: 2011-08-10.02.40.28)
if your sure the nandroid isn't corrupted and you want to restore it anyway, you can modify the md5sum.
1. go get a md5sum checker
2.With your phone mounted on your pc...go into the clockworkmod/backups/(yourbackups folder)
3. md5 sum all the images in there (write it down somewhere)
4. open the nandroid.md5 with a text editor
5. replace the md5s with the ones you wrote down
6. Try restoring it again
This doesn't appear to do anything
xmc wildchild22 said:
Edit: (didn't read whole post)
1. Open your sdcard on pc (usb mounted)
2. ensure there is a folder in clockworkmod/backup (ex: 2011-08-10.02.40.28)
if your sure the nandroid isn't corrupted and you want to restore it anyway, you can modify the md5sum.
1. go get a md5sum checker
2.With your phone mounted on your pc...go into the clockworkmod/backups/(yourbackups folder)
3. md5 sum all the images in there (write it down somewhere)
4. open the nandroid.md5 with a text editor
5. replace the md5s with the ones you wrote down
6. Try restoring it again
Click to expand...
Click to collapse
I'm having exactly the same problem as the OP, and I'm not sure how this will help as all md5sum does is give the md5s listed in the nandroid.md5 file. Using this method, all one is doing is putting the exact same md5s over what is there in the nandroid.md5 file.
I really need a method to make the Nandroid Advance Restore work in order to get back my data after updating to 1.63.531.2.
Any other suggestions? --
--
KingCheetah
y do u guys need to advanced restore...just restore
xmc wildchild22 said:
y do u guys need to advanced restore...just restore
Click to expand...
Click to collapse
Heh, well, in my case, I'm trying not to have to restore my phone from scratch after updating to 1.63.531.2, as well as keep the update. A straight restore will just take me back to DS Mod 1.55.531.3. Advanced Restore would allow restoration of data without overwriting the boot.img, system, etc.
So, no further methods to try to address this error?
--
KingCheetah
then take the system.img from the 1.63 update and put in replace of the nandroids one....then redo the md5 checksum for the system.img like i had showed before
xmc wildchild22 said:
Edit: (didn't read whole post)
1. Open your sdcard on pc (usb mounted)
2. ensure there is a folder in clockworkmod/backup (ex: 2011-08-10.02.40.28)
if your sure the nandroid isn't corrupted and you want to restore it anyway, you can modify the md5sum.
1. go get a md5sum checker
2.With your phone mounted on your pc...go into the clockworkmod/backups/(yourbackups folder)
3. md5 sum all the images in there (write it down somewhere)
4. open the nandroid.md5 with a text editor
5. replace the md5s with the ones you wrote down
6. Try restoring it again
Click to expand...
Click to collapse
The md5s are already the same.
That also doesn't address the issue why I am told that there are no files found when I try the advanced restore option without first going to the regular restore and backing out.
Investigation ongoing, but an idea to help
paperskye said:
The md5s are already the same.
That also doesn't address the issue why I am told that there are no files found when I try the advanced restore option without first going to the regular restore and backing out.
Click to expand...
Click to collapse
This may have something to do with the way in which CWM 5.0.2.7 saves the majority of data to tar files instead of img files. This behavior of CWM is part of the discussion in this thread: http://forum.xda-developers.com/showthread.php?t=1624516
Yogi2010 made the suggestion of using the Modaco 4.0.0.9 recovery for backups that can be successfully used with Advanced Restore. I believe Modaco's AR works because it saves all data to img files.
I'm going to attempt an update to 1.63 using Modaco for backup and then AR of data afterward. If successful, we know that Modaco is the key for utilizing AR due to the file type it uses for data storage.
Why CWM 5.0.2.7 behaves as it does regarding AR remains an open question.
I'll report back to this thread with results after my update attempt --
--
KingCheetah
Modaco functional with Advanced Restore
I used the Modaco 4.0.0.9 recovery for my backup prior to updating to 1.63, then followed with an Advanced Restore of data afterward, which successfully restored my phone environment. So AR is functional with Modaco, but not CWM 5.0.2.7. I don't know for certain if the fact that CWM uses tar files has something to do with its inability to execute AR, but it certainly seems like this is a contributing factor.
I'm going to Google this and see if I can come up with any further info on CWM that might explain its behavior.
So far, it's Modaco FTW. Itz on my fone, reestoring my data --
--
KingCheetah
Did you use this to get Modaco? I noticed it says you must have s-off but in your thread you said you have s-on.
http://forum.xda-developers.com/showthread.php?t=1179125
My problem is that with the data I want to restore, my phone gets stuck in a boot loop. I am thinking that I might be able to install Modaco, restore the data where I can't start up my phone and then do a Modaco backup while still in recovery. Then restore a functioning backup (so my phone boots up) and finally do an advanced restore where I only restore the data I need from the bootloop backup.
paperskye said:
Did you use this to get Modaco? I noticed it says you must have s-off but in your thread you said you have s-on.
http://forum.xda-developers.com/showthread.php?t=1179125
Click to expand...
Click to collapse
That's the original thread Paul (Modaco's creator) posted. I downloaded my copy via Blue's invaluable Developers Reference: http://forum.xda-developers.com/showpost.php?p=17384145&postcount=7. Scroll down to the Recovery section, and under Clockworkmod 4.0.0.9 Recovery there's a download link; but it's the same file.
As to being s-off, I think that's how things used to be. Obviously, all you need now is the bootloader to be unlocked so you can fastboot flash the recovery img file. Otherwise, I couldn't have been doing all the monkeying I've been doing recently.
paperskye said:
My problem is that with the data I want to restore, my phone gets stuck in a boot loop. I am thinking that I might be able to install Modaco, restore the data where I can't start up my phone and then do a Modaco backup while still in recovery. Then restore a functioning backup (so my phone boots up) and finally do an advanced restore where I only restore the data I need from the bootloop backup.
Click to expand...
Click to collapse
My experience is limited, but from your description, I'm not sure if the Advanced Restore option will be the smoking gun for your problem. The way I understand it, ClockworkMod recovery--of which Modaco is an unofficial flavor--takes the equivalent of a disk image of your phone while the OS is inactive (like many disk imaging programs for the PC). If you've got some ratty data causing the boot looping, that data is going to be stored along with everything else in the snapshot during backup. It will also be restored using regular restore or Advanced. So, I'm not certain how using a different recovery module will accomplish your goal of stopping the boot loop. Also, remember that any backups made with CWM 5.0.2.7 will be incompatible with Modaco recovery since it uses only img files.
This definitely needs to go to someone more experienced in troubleshooting Android, I think. Maybe you could edit the title of this thread to reflect the boot looping problem. This will hopefully get someone like Blue involved to help out. Sorry not to have a definitive answer for this. I suppose you could flash Modaco (same as you flashed CWM 5.0.2.7) and see if it does what you're hoping it will do. Best advice I can give.
Apologies for not having a concrete solution, and best of luck --
--
KingCheetah
Same problem, with ANY restore
I'm running cwm 5.0.2.7 and can't restore any previous backups. When I run restore it restores a few things, but then it just stops and cwm recovery seems to abruptly reset. After that I get stuck on the splash screen after rebooting.I verified the md5s in the backup folder, also. All match.
I DID change the backup filename so I could find it easily in my backup folder, but it was doing the same thing even before I changed it.
Anyone else have the same issue?
Also, is there a way to restore the images through adb/fastboot, even though they were created by cwm recovery?
A small suggestion
IBtokin said:
I'm running cwm 5.0.2.7 and can't restore any previous backups. When I run restore it restores a few things, but then it just stops and cwm recovery seems to abruptly reset. After that I get stuck on the splash screen after rebooting.I verified the md5s in the backup folder, also. All match.
I DID change the backup filename so I could find it easily in my backup folder, but it was doing the same thing even before I changed it.
Click to expand...
Click to collapse
Check your backup filenames and make sure they don't have any spaces. If that isn't an issue, you might try reflashing CWM and see if that resolves its difficulties. CWM shouldn't be behaving as you describe if it has been installed properly. Only other thing I can think of is looking into any item installed on your phone that could possible not play nice with CWM. I don't know of any myself, but it's a possibility.
IBtokin said:
Also, is there a way to restore the images through adb/fastboot, even though they were created by cwm recovery?
Click to expand...
Click to collapse
Not that I know of; hopefully someone with more CWM knowledge will chime in on this thread.
Purrs --
--
KingCheetah
Hmm...I'll have to check to see if the old fastboot method can still be used.
---------------------------------------------------------------------------
Nope. Nandroid used to save the files in .img format instead of the current one. This means no fastboot restore.
Sent from Spaceball One.

Loading First ROM

Hey guys,
I'm very new to Android and I have a few questions. I used to install custom OS's on my blackberry and I jailbroke my iphones so I'm some what used to this stuff but every operating system is obviously different. So I've had my S3 for about 6 weeks and I finally rooted a couple days ago. To root I followed this thread: http://forum.xda-developers.com/showthread.php?t=1875914. I rooted, unlocked the bootloader, and installed clockworkmod recovery. Now I have been wanting to load a jelly bean ROM. I kind of wanted to load the Synergy ROM found here: http://forum.xda-developers.com/showthread.php?t=1792499. So am I ok to just download from that thread and drag and drop to my phone on my PC and just follow the directions? I don't have an external SD Card is just fine to use internal storage? Like I said all I have done is rooted from that first link. I just kinda wanted some verification before I go and brick my phone, thanks for your help.
Piece of cake. If you scroll down to the second post of the Synergy thread, you'll see the very first question in the FAQ:
Q: How do I install this ROM?
A: Download the ROM from the "Download Links" section above, place the file on your phone's external SD card, and then flash via your recovery. First boot after flash takes a wee bit longer than usual.
Click to expand...
Click to collapse
So, download the ROM (using either your phone (take note of where it saves it) or computer). If using your computer, connect your phone and drop that sucker somewhere on the SD card (external or internal -I use internal). (I create a folder in the root of my internal SD card called Files to Flash, in which I keep everything I flash, so it doesn't get scattered about, but do what you want )
Use Titanium Backup to back up all your apps and data to restore later (when you do restore, since you're going from ICS to JB, don't restore any System Data as it will cause many issues (apps and app data is fine)).
Reboot into recovery using Rom Manager, as mentioned in the rooting tutorial you followed.
Use your volume keys to navigate to "backup and restore" and select it using either the home or power button.
Select "backup" and wait for your nandroid backup to complete.
Next, navigate back to the original menu and select the "wipe cache/factory data reset" option.
Once that's done, select the "wipe cache partition" option.
(side note: Instead of doing those two things, I like to go into the "mounts and storage" option and select "format /system" "/data" and "/cache". Both ways work - BE VERY CAREFUL NOT TO FORMAT SDCARD AND EXTERNALSD IF YOU USE MY METHOD...bad joo joo).
Select the "advanced" option from the initial menu and "wipe dalvic cache".
Now you're ready to install.
In the first menu, the second option is "install zip from sdcard." Select it.
Select "choose zip from sdcard" and navigate to where you saved the ROM and select it.
Scroll either up or down, passed all the "no"s and select "yes" and let it do it's thing.
Once it's done, navigate back to the menu you first started at by selecting the "Go Back" option, then reboot and profit.
letinsh posted pretty much the most concise instructions to follow. In addition, I'll suggest to backup your IMEI prior to flashing anything.
Info here:
http://forum.xda-developers.com/showthread.php?t=1852255
So I can just go to this website from my phone and go to the download link and download directly to my phone? Is that easier/faster? Thanks for responding
Good call, Snoop.
I totally forgot about it because I did it once and have flashed dozens of times since
Naganalf - as far as downloading via fone or computer, it's really 6 of one, half dozen of the other. Whichever makes you more comfortable. Keep in mind that it is HIGHLY recommended that you check the md5 sum of your download before flashing, to ensure you have a good download. I have an md5 sum checker on both my computer and fone, so I can do either fairly easily.
This is the one I used on my computer
and I use MD5 Checker by Fabien Thalgott (play store) on my phone.
Having just looked at the Synergy thread, they don't post md5's for their nightly's, so don't worry about that step for them, although, it typically is good practice to check (I hardbricked my S3 the third day I had it by pushing a corrupt file using Odin that would have been caught if I had checked the md5). (Got it JTAG'd back to life, so no worries - everything is recoverable from except physical damage )
Thanks for your help snoop and letish, after this first flash I will be much more comfortable. I am downloading now so when it gets done I will give it a whirl and let you know how it goes.
Naganalf said:
Thanks for your help snoop and letish, after this first flash I will be much more comfortable. I am downloading now so when it gets done I will give it a whirl and let you know how it goes.
Click to expand...
Click to collapse
No worries, dude. I agonized for days before I rooted and flashed my first ROM on my OG Droid back in the day - had one of the founders of DroidForums (synik4l) on G-chat while I did the deed...I was so chicken
Good times, though. Just do your research, understand what it is you're doing, mitigate any risks (by doing your research...) and go to town! Most of the bugs in the process have been ironed out by jokers like me testing and hard-bricking along the way . At this point, the processes are very user friendly and reliable:fingers-crossed:
Enjoy!
How'd it go?
Sent from my SCH-I535 using xda app-developers app
Getting ready to try it now, I will let you know.
when i "Reboot into Recovery" from Rom Manager i don't have a "backup and restore" option. it only has "reboot system now", "apply update from external storage", "wipe data/factory reset", "wipe cache partition", and "apply update from cache"
am I missing something?
Naganalf said:
when i "Reboot into Recovery" from Rom Manager i don't have a "backup and restore" option. it only has "reboot system now", "apply update from external storage", "wipe data/factory reset", "wipe cache partition", and "apply update from cache"
am I missing something?
Click to expand...
Click to collapse
If you haven't selected any options yet then just go back into your rom. You need to download EZ Recovery from the Play Store so that you can flash a custom recovery (ClockworkMod or TWRP) through that app.
Sent from my SCH-I535 using xda app-developers app
I'm sorry but I'm a little confused. Why is it only giving me those options when I reboot into recovery from ROM Manager? The first time after I rooted I'm pretty sure there was an option to "Backup and Restore". Also, why can't I just go into ROM Manager and select "Install ROM From SD Card" and select my ROM that way? sorry but I do appreciate your help.
Naganalf said:
I'm sorry but I'm a little confused. Why is it only giving me those options when I reboot into recovery from ROM Manager? The first time after I rooted I'm pretty sure there was an option to "Backup and Restore". Also, why can't I just go into ROM Manager and select "Install ROM From SD Card" and select my ROM that way? sorry but I do appreciate your help.
Click to expand...
Click to collapse
Good questions. The recovery you rebooted into is the Stock recovery that comes with the phone. Your OP in this thread says that you installed CWM recovery. It looks like it didn't stick. Two options - Use the program Snoop suggested, or open up Rom Manager and hit the "Flash Clockwork Mod Recovery" option.
From there you can continue as previously explained.
EDIT - I've never used the ROM Manager's install ROM from SD card option, so I can't speak to it. I know I like having the control (or perceived control ) of doing everything by hand in recovery.
ok I have loaded android version 4.1.1 build number SynergyROM Nightly JB(r111) so I guess i did everything correctly. now i'd like to get my phone kinda back to how i had it lol. if I run titanium backup will my home screens all be restored the way I had them? and when i run titanium backup i ONLY want to run "restore missing apps with data" right? not "restore missing apps + all system data" just want to make sure. thanks
Naganalf said:
ok I have loaded android version 4.1.1 build number SynergyROM Nightly JB(r111) so I guess i did everything correctly. now i'd like to get my phone kinda back to how i had it lol. if I run titanium backup will my home screens all be restored the way I had them? and when i run titanium backup i ONLY want to run "restore missing apps with data" right? not "restore missing apps + all system data" just want to make sure. thanks
Click to expand...
Click to collapse
Correct, don't restore the system data. Now, if you want your txt messages back, you'll see a yellow Messages backup (with a TiBu logo). If you restore that (the only option available is Data, I think), you'll get your txts back.
Remember that you'll prolly need to reboot after the restore, then use ROM Manager to Fix Permissions, then restart again. You'll be off to the races!
As far as getting your home screens back, I don't know if that'll be possible, although they're both TouchWiz launchers....might be alright, then
I run Nova launcher regardless of ROM, so all I have to do is restore the Nova app, then used the built in Nova backup/restore to get my home screens back. Let me know how the Titanium restore works! As a side note, if I have any doubt about whether I'll be able to get my launcher set back up (or I'm switching launchers to try them out), I'll take quick screenshots of all my screens and use that as a reference to set them back up
well i think im all set, thanks again for your help guys. I went ahead and installed nova launcher so i can back up my home screens like you said. so if I want to try a different ROM do i need to flash back to stock first? or just do it like i did this time?
Naganalf said:
well i think im all set, thanks again for your help guys. I went ahead and installed nova launcher so i can back up my home screens like you said. so if I want to try a different ROM do i need to flash back to stock first? or just do it like i did this time?
Click to expand...
Click to collapse
Nahh, just as simple as putting the ROM you want on your ex SD card or internal one which ever you prefer, wiping system/data , and wiping your cache, and then flash your new ROM . You can also "dirty flash" if say you are just moving from r111 of synergy to a newer one. Typically on the forum you will see if anyone had any problems dirty flashing. I always go with a clean flash just to avoid any problems to begin with.
Naganalf said:
well i think im all set, thanks again for your help guys. I went ahead and installed nova launcher so i can back up my home screens like you said. so if I want to try a different ROM do i need to flash back to stock first? or just do it like i did this time?
Click to expand...
Click to collapse
HoudiniJr said:
Nahh, just as simple as putting the ROM you want on your ex SD card or internal one which ever you prefer, wiping system/data , and wiping your cache, and then flash your new ROM . You can also "dirty flash" if say you are just moving from r111 of synergy to a newer one. Typically on the forum you will see if anyone had any problems dirty flashing. I always go with a clean flash just to avoid any problems to begin with.
Click to expand...
Click to collapse
What he ^ said. You can go from ROM to ROM. I, also, like Houdini said, like to flash clean each time. Try it both ways and see if you have problems
I just threw out Nova as an example - there are several good launchers out there...Nova, Apex, Go Launcher (I'll probably catch flack for mentioning it), Trebuchet (from CM). Most if not all have the ability to backup your settings. Try 'em each and figure out which one works best for you :good:
Glad it worked, buddy. Welcome to the flashing addiction :highfive:!
letinsh said:
What he ^ said. You can go from ROM to ROM. I, also, like Houdini said, like to flash clean each time. Try it both ways and see if you have problems
I just threw out Nova as an example - there are several good launchers out there...Nova, Apex, Go Launcher (I'll probably catch flack for mentioning it), Trebuchet (from CM). Most if not all have the ability to backup your settings. Try 'em each and figure out which one works best for you :good:
Glad it worked, buddy. Welcome to the flashing addiction :highfive:!
Click to expand...
Click to collapse
+1 for Nova Apex is also pretty good. Like lentinsh said, most if not all have the ability to back up your settings, making flashing from ROM to ROM that much easier :good: Cant go wrong with Nova though :laugh:
App Restore
Hey peeps,
I have been able to flash a few new ROMs but can't quite get my Apps Restored. I have/had Titanium Back up installed and backed up. With each ROM I install I don't quite get how to restore the Apps I had installed, Titanium Back up gets dropped when I flash to a new ROM.
I'm going to search the Forum for App Backup 101...
OK so I found a link to App Backup and Restore in GPS, on a different thread looks like it is what I need
thanks for any tips...

[Q] Newer CWM, md5 mismatch won't allow recovery.

I don't know if it has to do with having installed a newer version of ClockworkMod Recovery (6.0.3.1), but when I go to restore a previous backup, I get "md5 mismatch!" and no recovery is done.
Things that my non-developer brain can think of that might be relevant:
I may have changed the name of the folder for the recovery (I didn't think this mattered)
I am trying to go from CyanogenMod M5 to a recovery of an M2 (don't think this should matter).
The recovery was made using a previous version of ClockworkMod Recovery (an earlier, but 2013, version)
The recovery folder was stored on my computer and I put it on my phone using USB on-the-go (I have tried this twice to make sure one wasn't corrupted or whatever).
Thanks for any pointers. Do have have to install an older version of ClockworkMod Recovery or is there something simpler I could do? Thanks! :good:
LudicrousPeed said:
I don't know if it has to do with having installed a newer version of ClockworkMod Recovery (6.0.3.1), but when I go to restore a previous backup, I get "md5 mismatch!" and no recovery is done.
Things that my non-developer brain can think of that might be relevant:
I may have changed the name of the folder for the recovery (I didn't think this mattered)
I am trying to go from CyanogenMod M5 to a recovery of an M2 (don't think this should matter).
The recovery was made using a previous version of ClockworkMod Recovery (an earlier, but 2013, version)
The recovery folder was stored on my computer and I put it on my phone using USB on-the-go (I have tried this twice to make sure one wasn't corrupted or whatever).
Thanks for any pointers. Do have have to install an older version of ClockworkMod Recovery or is there something simpler I could do? Thanks! :good:
Click to expand...
Click to collapse
Changing the name for CWM backups will cause md5 mismatches. If you did this, you should switch and use TWRP which allows native nandroid renaming. Delete your CWM backups and stick to TWRP. It could also be an issue between CWM backups over different CWM versions however if you renamed your backups and each of those renamed backups failed except the ones you left alone then you found your issue.
SlimSnoopOS said:
Changing the name for CWM backups will cause md5 mismatches. If you did this, you should switch and use TWRP which allows native nandroid renaming. Delete your CWM backups and stick to TWRP. It could also be an issue between CWM backups over different CWM versions however if you renamed your backups and each of those renamed backups failed except the ones you left alone then you found your issue.
Click to expand...
Click to collapse
Thanks for the insight. Seems like I should just be able to change the folder name back to what it was named by default, if I can make sure it is correct. Do you think that's worth trying or is it deeper than that? I'll use TWRP from now on since it seems to be more robust (CWM was just the recommended recovery from Cyanogenmod)
LudicrousPeed said:
Thanks for the insight. Seems like I should just be able to change the folder name back to what it was named by default, if I can make sure it is correct. Do you think that's worth trying or is it deeper than that? I'll use TWRP from now on since it seems to be more robust (CWM was just the recommended recovery from Cyanogenmod)
Click to expand...
Click to collapse
Depends on how much you value those nandroids. I only keep two on my phone so it's no thing for me to delete my backups entirely. You can rename them to their original names and your issue should go away.
Sent from my SCH-I535 using Tapatalk 4 Beta
Make sure the name of the backup folder doesn't have any spaces. When I renamed backups and had a space in the name I would get that same "md5 mismatch!" error.
Thanks! So renaming the backup to what it was originally allowed the backup to attempt to restore, but data could not be restored. Attempting to boot it resulted in nor getting past the boot animation. I wonder if it was because I didn't have enough space left on my phone or of it had to so with the newer firmware I installed. Or something else.
Slightly of topic at this point but not really. Any ideas why data could not be restored?
Sent from my SCH-I535 using Tapatalk 2
LudicrousPeed said:
Thanks! So renaming the backup to what it was originally allowed the backup to attempt to restore, but data could not be restored. Attempting to boot it resulted in nor getting past the boot animation. I wonder if it was because I didn't have enough space left on my phone or of it had to so with the newer firmware I installed. Or something else.
Slightly of topic at this point but not really. Any ideas why data could not be restored?
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
I had a similar issue about a year ago. I resolved it by generating a new md5, but I don't recall what method I used. Do a search for that.

Categories

Resources