So I'm running PnP and wanna run cyanogenmod 6 that got ported. If i make a backup and decide i don't like cyanogen (which i doubt) then i can just do a restore and everything will be there? In the thread about cyanogen it says wipe data.. so i just wanna make sure that i can get everthing back if i dont like it. And is there a way to just wipe data other than wipe data/ factory reset?
Yes, everything will still be there when you restore a backup. Just make sure to reflash whatever kernel you had been using on PnP if you restore your backup.
No, wipe data and factory reset from recovery are one in the same and can't be done separately.
So reflash the kernel before I do the restore?
Sent from my SCH-I500
Correct sir.
Alright thanks.
Sent from my SCH-I500
I'm currently running ics bata10 and was wounding when I Restore one of my back up should I wipe everything then restore or don't need to wipe just restore
Sent from my Nexus S using xda premium
smok3thekid said:
I'm currently running ics bata10 and was wounding when I Restore one of my back up should I wipe everything then restore or don't need to wipe just restore
Sent from my Nexus S using xda premium
Click to expand...
Click to collapse
Technically you don't have to wipe because the nand restore process actually does a full wipe for you... but me personally, I always wipe at least cache and dalvik before restoring a nand, just to make sure there's nothing left over from the previous ROM.
I've been thinking. I wonder if it's best to wipe everything (system, cache, dalvik, factory reset) before you do a nandroid restore. I thought I remember reading in a thread once that someone thought some things carry over from the rom you were on even though you restored your previous backup. Does anyone wipe before they restore a backup? I usually don't but this last time I did. I don't think I'm going the notice any difference tho but maybe that's why some people have problems. If they're on a rom that has a bunch of bugs some of them could carry over without doing a wipe before restoring a backup.
If you look at the nandroid procedure it wipes system and data. I never thought of the caches. Hmmm.
gunnyman said:
If you look at the nandroid procedure it wipes system and data. I never thought of the caches. Hmmm.
Click to expand...
Click to collapse
Yea I did notice that after I posted this lol.
Sent from my One X using xda app-developers app
I have what seems like a very basic question on backing up using TWRP, and yet I havent been able to find this anywhere in the help threads.
When I am creating a backup it asks for what I want to backup: System, Data, Boot, Recovery, Cache, .android_secure.
Which of these do I want to make sure are checked? The first backup I did I left the default (which was only System and Data) and now I am unable to restore to that backup (I just get a blank, dark screen). Looking through the forums it seems I may need to flash boot.img in order to restore?
So does that mean in the future I should make sure to also check the Book option when I create backups? Any others?
Thanks.
system, data, boot
leave the other 3 unchecked
vincom said:
system, data, boot
leave the other 3 unchecked
Click to expand...
Click to collapse
Thanks again for all of your help over the last few days!
Would the failure to check Boot on my first backup be the reason I am getting that blank screen when I try to restore? And is this fixable by flashing "boot.img" if I can find it somewhere?
Would the failure to check Boot on my first backup be the reason I am getting that blank screen when I try to restore? > yes
And is this fixable by flashing "boot.img" if I can find it somewhere? > yes from another backup from siimar rom through the backup utility from twrp, but just flashing a rom would be easier
vincom said:
And is this fixable by flashing "boot.img" if I can find it somewhere? > yes from another backup from siimar rom through the backup utility from twrp, but just flashing a rom would be easier
Click to expand...
Click to collapse
You could probably just flash the same ROM you made the backup from and then just restore the data from that backup through TWRP. Then you'd be back to the same setup you tried to backup originally, right?
Sent from my SAMSUNG-SGH-I897 using xda app-developers app
If you want your backup to work after you do it - don't touch the default selection.
And this is also the reason you don't see any threads about it. All those who don't understand what each partition does just don't touch anything, and all those that understand don't write about it.
Read more to see why the first suggestion you got (system, data, boot) might fail you.
Backing up recovery in recovery is useless, though.
Jack_R1 said:
If you want your backup to work after you do it - don't touch the default selection.
And this is also the reason you don't see any threads about it. All those who don't understand what each partition does just don't touch anything, and all those that understand don't write about it.
Read more to see why the first suggestion you got (system, data, boot) might fail you.
Backing up recovery in recovery is useless, though.
Click to expand...
Click to collapse
My initial backup was made just with the default - first two boxes ticked. Unfortunately I now cannot get that backup to recover and boot, which is why I am asking. What else might be the cause or how would you suggest I try to solve?
Also, apologies but I dont understand what you mean when you say "Backing up recovery in recovery is useless, though." Do you mean this isnt the best way to make a backup/nandroid to recover to?
Alright, here's a short explanation to get you started:
/boot - your kernel partition. Without it the ROM won't boot.
/system - your ROM.
/data - user data, all the apps and app settings that user has.
/.android_secure - all the apps that are on SD (or USB storage).
/cache - temporary place for storing downloads, exchanging data with recovery and such.
/recovery - where your recovery resides.
From this you should be able to understand why it's useless to backup recovery partition - you won't be able to restore it if you don't have custom recovery in place, and if you have custom recovery in place - you don't need to restore this partition, it's already populated.
This should also tell you why you need .android_secure. Some apps are still installed by default to SD card, and these will be lost if you don't back it up.
Jack_R1 said:
Alright, here's a short explanation to get you started:
/boot - your kernel partition. Without it the ROM won't boot.
/system - your ROM.
/data - user data, all the apps and app settings that user has.
/.android_secure - all the apps that are on SD (or USB storage).
/cache - temporary place for storing downloads, exchanging data with recovery and such.
/recovery - where your recovery resides.
From this you should be able to understand why it's useless to backup recovery partition - you won't be able to restore it if you don't have custom recovery in place, and if you have custom recovery in place - you don't need to restore this partition, it's already populated.
This should also tell you why you need .android_secure. Some apps are still installed by default to SD card, and these will be lost if you don't back it up.
Click to expand...
Click to collapse
Thanks. I think I misunderstood your initial post. When you said "system, data, boot" advice might fail me, I thought you meant NOT to backup boot. But I think you meant to ALSO backup .android_secure, not to avoid backing up boot.
When doing a recover, is it generally advised to do full cache, davlik wipe and factory reset, like when flashing a new ROM?
lirong said:
When doing a recover, is it generally advised to do full cache, davlik wipe and factory reset, like when flashing a new ROM?
Click to expand...
Click to collapse
I never do any of the wipes and never have had a problem when restoring a nandroid.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
jd1639 said:
I never do any of the wipes and never have had a problem when restoring a nandroid.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Click to expand...
Click to collapse
and you're totally wrong...the only "cleaning" the restore function is doing is erasing boot before restoring (to at least protect from statements like yours) , imagine you restore a windows image over another windows installation ...
mahanddeem said:
and you're totally wrong...the only "cleaning" the restore function is doing is erasing boot before restoring (to at least protect from statements like yours) , imagine you restore a windows image over another windows installation ...
Click to expand...
Click to collapse
Only erasing boot? So the only thing that remotely connects to what you're saying would be boot.IMG which is the kernel in which case you would be incorrect. Please if you plan on correcting someone at least be concise so people understand the point you are trying to convey.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
mtdew said:
Only erasing boot? So the only thing that remotely connects to what you're saying would be boot.IMG which is the kernel in which case you would be incorrect. Please if you plan on correcting someone at least be concise so people understand the point you are trying to convey.
Click to expand...
Click to collapse
LOL. Can't we all just get along.
Since I'm not one to speak for others I'll only guess that what he was trying to get at is restoring only erases the boot.img. It then restores boot.img, system, data, android.secure, and cache. So in theory it doesn't actually erase any of the remaining partitions. It just writes over them. Whether or not this leaves any residual parts of any of the partitions has been a source of debate for quite some time. If it does format the partitions before restore there is no indication textually that I have seen.
Carry on.
EDIT: I might as well point this out before some one else does. The restores I stated above where done from CWM not TWRP. I forget what the thread was originally about. For that I apologize. The logic behind the post stands for either recovery though.
mahanddeem said:
and you're totally wrong...the only "cleaning" the restore function is doing is erasing boot before restoring (to at least protect from statements like yours) , imagine you restore a windows image over another windows installation ...
Click to expand...
Click to collapse
Maybe. But a couple of points. First, I've never had any issues. Second, have you watched what happens when you restore?
Wiping system.....
Formatting system....
Restoring system....
Wiping data....
Formatting data....
Restoring data....
Restoring boot...
This is on twrp 2.3.3.0 and 2.4.0.0. So technically it does the wipes for you.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
So TWRP restore system, data, cache before boot ? Big fail...
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
mahanddeem said:
So TWRP restore system, data, cache before boot ? Big fail...
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
Is this even English because I can't understand the point of this sentence. Was it meant to be an insult? It honestly makes no sense.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
mtdew said:
Is this even English because I can't understand the point of this sentence. Was it meant to be an insult? It honestly makes no sense.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
It's Japanese
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
mahanddeem said:
It's Japanese
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
So basically you have no idea what you're saying. I guess I'll go back to my being concise point
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
mahanddeem said:
So TWRP restore system, data, cache before boot ? Big fail...
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
You're obviously a CWM guy. I'm a TWRP guy. Both are good recoveries and used by many. So use what you're comfortable with and you know works.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
I am currently on CWM touch recovery v14.4.6. If I want to a restore a nandroid backup, do I perform the following steps before I hit the restore button?
1. wipe data/factory reset
2. wipe cache partition
Any guidance is greatly appreciated.
Sure why not
Sent from my SGH-I727 using Tapatalk 2
If you're restoring a nandroid it doesn't make any real difference what you do. As long as you don't wipe the the nandroid
God promised men that he'd put beautiful women in all corners of the world. Then he laughed and laughed and made the world round
For a full restore I wipe system/data/cache. I've never had a single issue restoring.
hechoen said:
For a full restore I wipe system/data/cache. I've never had a single issue restoring.
Click to expand...
Click to collapse
Thanks for the response. I don't see the wipe system in CWM touch, only factory data and cache.
Skyrocket2 said:
Thanks for the response. I don't see the wipe system in CWM touch, only factory data and cache.
Click to expand...
Click to collapse
It would be format system in cwm if I remember right. Haven't used cwm since twrp came out.
Sent from my SGH-I727 using Tapatalk 2
xcrazydx said:
It would be format system in cwm if I remember right. Haven't used cwm since twrp came out.
Sent from my SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
Thanks Xcrazydx! So, is doing a format/system the same as wiping system?
Skyrocket2 said:
Thanks Xcrazydx! So, is doing a format/system the same as wiping system?
Click to expand...
Click to collapse
Yeah it's the same. So I should have said I format system/data/cache. Do those and you'll be fine.
Just remember that you have to flash the radio separate if you need to change radios. Nandroids to not contain the radio / modem. If you want to keep the same radio / modem, then you won't have to do anything except flash the nandroid.
I have problems restoring lately. I use sk8ers cwm latest and when restoring I get system could not be restored. I did backup pre load. I use the externel SD card to backup. Md5 sum checks out fine or appears to check out fine.
Normally I wipe just as if I was installing a fresh rom before restore. I have restored backups without wiping and they work fine. Just gives me piece of mind especially if I encounter any issues.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Jnewell05 said:
I have problems restoring lately. I use sk8ers cwm latest and when restoring I get system could not be restored. I did backup pre load. I use the externel SD card to backup. Md5 sum checks out fine or appears to check out fine.
Normally I wipe just as if I was installing a fresh rom before restore. I have restored backups without wiping and they work fine. Just gives me piece of mind especially if I encounter any issues.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
Have you resolved the issues? I got error messages when I tried to do a nandroid backup with preload option checked. So, I decided to do a normal nandroid leaving out the preload and got no errors. I haven't tried to do a restore yet afraid that I might have the same issues as you.
I do believe that my backups got corrupted maybe from just not unmounting from pc properly as I just un plug it most the time. I lost the backups but still got titanium so no big loss. I change roms like I do underwear.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Jnewell05 said:
I have problems restoring lately. I use sk8ers cwm latest and when restoring I get system could not be restored. I did backup pre load. I use the externel SD card to backup. Md5 sum checks out fine or appears to check out fine.
Normally I wipe just as if I was installing a fresh rom before restore. I have restored backups without wiping and they work fine. Just gives me piece of mind especially if I encounter any issues.
I've always had problems backing up/restoring from external SD. Try moving your backup to internal SD, should work fine.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
curiouscrackers said:
Jnewell05 said:
I have problems restoring lately. I use sk8ers cwm latest and when restoring I get system could not be restored. I did backup pre load. I use the externel SD card to backup. Md5 sum checks out fine or appears to check out fine.
Normally I wipe just as if I was installing a fresh rom before restore. I have restored backups without wiping and they work fine. Just gives me piece of mind especially if I encounter any issues.
I've always had problems backing up/restoring from external SD. Try moving your backup to internal SD, should work fine.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
I would never backup to internal sd where it can get wiped. Also keep backups on you're pc
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse