so i made a backup via CWM recovery and, to recognize the backup, i renamed the folder to the name of the ROM... when i tried restoring it, i got a size mismatch error... good thing i made a backup of all of my sdcard, including the original name of the folder, and the restore worked again
SO PLEASE! do *NOT* rename the backup folder!!
and this is news because....?
Sent from my HTC Vision using xda premium
androidcues said:
and this is news because....?
Sent from my HTC Vision using xda premium
Click to expand...
Click to collapse
because i didn't see someone doing it... so i think its new...
—————
|RIROZIZO|
—————
I agree thanks for the heads up. I'm sure there are those that don't know this. I found out the hard way monthes ago.
Sent from my Mikes HTC G2 with Google using xda premium
I didn't know this either. Surprising that this isn't more widely known. Learned this afew months ago by mistake. Never thought of making a post though.
Koodos!
Uh..duh
Sent from my HTC Vision using xda premium
Actually, here's the deal
You CAN rename backups. I do it all the time. What you CANNOT do is add spaces.
My_Rom <----works
My Rom <-----will fail
I usually use camel casing (camelCasing). I've seen people with this problem in a few other phone forums and just happened to stumble on this
OP, if you rename your backup to one that has no spaces, then you should be alright!
Hope I helped!
i didn't try without spaces, but could a space make the md5sum different? i thought just renaming the thing changes the md5sum
Riro Zizo said:
i didn't try without spaces, but could a space make the md5sum different? i thought just renaming the thing changes the md5sum
Click to expand...
Click to collapse
Nope, the md5sum is stored in a .txt file in the backup folder and doesn't ever change (even with the name). If you change the .txt file in any way it'll probably break the back up. I'm not sure the logistics behind it, but spaces break something that removing the space will fix.
A couple things.. The spaces are because of the file reader cannot register the new tokens, some programs (windows and most OSs) are completely fine with this, however some just don't have he exception to deal with it. As for changing the .txt file with the md5, that wont actually break the backup, but CWM will think that it is cause they don't matchup
Why not just use 4ext? They name the backup for you, very nice recovery.
Related
Just wondering if I can rename my nandroid backup files to make it easier to identify them -
Jacklad said:
Just wondering if I can rename my nandroid backup files to make it easier to identify them -
Click to expand...
Click to collapse
yup, just don't put any spaces in the name or the restore will fail
Or any ().. Actually anything that is not a number or letter is out..
PS underscores will work.
This has been asked before but to answer again...YES
You can use a file manager and rename them (astro, filemanager, ...)
A quick use of the search button and I found this
http://forum.xda-developers.com/showthread.php?t=654536&highlight=nandroid
Thank you, oh gross one - I will make sure to use our friend the search button in the future
Sent from my Eris using XDA App
You should use the Rom manager app its the easiest way
Sent from my FroyoEris using XDA App
Whitepaint said:
Or any ().. Actually anything that is not a number or letter is out..
PS underscores will work.
Click to expand...
Click to collapse
So will dashes and dots.
Heres what I do, and no problems yet (knocks on wood).
The top-level folders are named
BDS-YYYYMMDD-HHMM or
BDES-YYYYMMDD-HHMM
where a folder beginning with BDES is a NAND+ext backup.
So, I just stick something meaningful in between the BDS-/BDES- and the -timestamp string, e.g.: (actual backups)
BDS-ota21-postFR-20100607-2219
BDS-OTA21-Configured-20100708-0654
BDS-Sense_able_3.1_20100607-0010
BDES-+ext-AloysiusV12-20100620-0603
BDS-xtrROM3.0.1-20100704-0650
BDS-OTA21-Configured-20100704-0427
BDS-EvilEris_3.0-20100629-0300
BDES-CyanogenLB_2.5-20100619-2238
You do need to keep the strings in the middle a reasonable length - if you have multiple copies of the same ROM at different times, you don't want the timestamp string to roll off the screen to the right side when using Amon_RA. That could lead to unintended consequences.
bftb0
Awesome, now I won't mix up my roms ever again.
Can someone please tell me what folder clockworkmod stores the backup's in? I formatted my sdcard on accident with a rom that was not booting.
I have copied backup's stored on my computer but when i put in on the sdcard and go into restore, clockwork does not see it. I thought is was in a folder called "backup" on the sdcard, but that does not seem to work.
clockworkmod/backup/
Sent from my HERO200 using XDA App
Thank you
Sent from my HERO200 using XDA App
*edit* removed apparently I forgot my helmet
Kumetto said:
Also you want to make sure to use the correct recovery CWM 2.x or 3.x.
CWM2 ex. BCDMRS-date-...
CWM3 ex. Date-...
The times are in military/24 hour format.
My cousin ran in to issues mixing recov's & backup's. I suspect it was more than just that. However I haven't tried when its pretty painless to switch between the two.
Sent from my HTC Hero CDMA using XDA App
Click to expand...
Click to collapse
Not quite sure what your saying here. So you know, you can name the backups whatever you want, like "3/26gb.firerat.4_20" and you can restore backups between cwm2 and 3.
sent from a series of tubes.
il Duce said:
Not quite sure what your saying here. So you know, you can name the backups whatever you want, like "3/26gb.firerat.4_20" and you can restore backups between cwm2 and 3.
sent from a series of tubes.
Click to expand...
Click to collapse
Every time i rename them the backups always fail. I had to stop naming them. It would just say md5 sum failed or something like that. I got screwed over twice that way so if you do rename just be cautious.
herouser26 said:
Every time i rename them the backups always fail. I had to stop naming them. It would just say md5 sum failed or something like that. I got screwed over twice that way so if you do rename just be cautious.
Click to expand...
Click to collapse
FYI the key is not putting spaces in there. I have renamed EVERY backup I have ever made (using ANY recovery) so I could tell them apart. I never use anything but numbers, letters, periods, and underscores. I currently have 6 on my sd in /clockworkmod/backup/ named:
gb326.perfection.norat
gb326.perfection.rat
gb326.perfection.rat_ap5
gb421.perfection.rat
gb421.perfection.rat_ap5
nfx.prl01115.pri2.20
I have restored each one of these (I always restore them to make sure they work).
I've searched a dozen different ways to try to read up on this but can't find a thread, I don't want to make a custom rom just copy mine as setup to another epic. If this is easily found could someone just point out the correct search terms. I thought to put this in development but the question seemed to general.
kiab115 said:
I've searched a dozen different ways to try to read up on this but can't find a thread, I don't want to make a custom rom just copy mine as setup to another epic. If this is easily found could someone just point out the correct search terms. I thought to put this in development but the question seemed to general.
Click to expand...
Click to collapse
About the only way I could think of doing so would be to go into your clockworkmod folder and copy the backup you have there and move that to the same folder of the other phone and try restoring that. Not sure if it would work being the google accounts/contacts and whatever else.
Just make a nandroid backup. Take the sd card out of the original epic, root your new epic using one click 3.0.0.6, boot into clockwork And then click on backup and restore and restore the nandroid backup you made. Not sure if it'll work, but I would assume it would.
It should work, you may hit an MD5 mismatch and you'd have to copy the MD5 file from a backup on the new phone to the old backup but it will probably be fine.
And make sure you flash a kernel that is ext4 compatable!
Sent from my SPH-D700 using XDA App
Thanks for the reply's, I did try to take the backup folders (3 in all) and copy them to the new phone, but I did get an md5 mismatch. I need to do this for 30+ company phones so I'm looking for the easiest way to get all the apps and layouts we want to each phone.
Lol, I think you better start changing MD5 instead of posting. Thats a lot of phones!!
Do a nandroid backup and backup everything using my backup root and wipe then put sd in new epic flash cwm3 let it convert to ext4 if that's what you were on otherwise use cwm2.5 and restore the system from cwm only boot up into system go to market log in download my backup root and restore all with that. If it can't find ur backup it sometimes makes an "SD" folder on the sd card itself
Edit: if md5 is mismatched just use any rom zip like srf or bonsai as the system backup is basically just a rom the mybackuproot holds all the app data and phone data
Sent from my midnight rom 5.2 genocide 1.0 epic [email protected] using xda premium app
qbking77 said:
Just make a nandroid backup. Take the sd card out of the original epic, root your new epic using one click 3.0.0.6, boot into clockwork And then click on backup and restore and restore the nandroid backup you made. Not sure if it'll work, but I would assume it would.
Click to expand...
Click to collapse
This is how you do it. Yes and like mentioned, flash a EXT4 kenel
Make an odin tar... way easier not to mention quicker on a mass scale, and more reliable. I made a post detailing how.
Sent from my SPH-D700 using XDA App
chris41g said:
Make an odin tar... way easier not to mention quicker on a mass scale, and more reliable. I made a post detailing how.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
I read threw those post to see if anyone suggested this,atleast it didnt get to a couple pages...
+1 on the odin.tar,way easier.
Sent from my MyFrankenstein EC05OCE using XDAP App...
Mods please make this sticky.
Before anyone flashes any custom rom further, be sure to back up your
/efs folder somewhere on your PC.
The /efs folder is a hidden folder. You wont be able to see it using a usual file explorer e.g astro. You will need to be root to do so using root explorer for e.g.
This is something found sticky in the galaxy s forums and unfortunately for some of us it is coming too late.
The backup might come handy anytime if ever you mess up your own with custom rom flashing.
Thanks
Edit: just for you to understand the situation, by messing up i mean where product code and imei of the phone gets changed to a fail-safe one and even nandroid backups are of no help.
What exactly is in /efs that we need to back up?
I actually have already flashed one rom and after that I could not make or receive phone calls. I ended up calling Sprint and after about an hour of tinkering on their end they got it working. Would this be due to something missing in the /efs folder?
Everything concerning ur hardware info in short. Bluetooth, mac number, imei, ....
Many of us have got this tampeted with and unfortunately we had no clue it was something important( despite numerous threads in the i9000 forums warning users of this and nobody had backups) ,
there is no fix yet.
Check the nexussense forum for more details.
But do make a backup please.
After that whole incident I downloaded Samsung's Reflash tool and restored my phone back to stock.
Since then I have reflashed a custom kernel, but so far all is well. What exactly should be in the /efs folder as far as files.
My /efs folder has
Code:
imei>bt.txt
uart_path
bluetooth>bt_addr
nv.log
lost+found
Could you tell me if I am missing anything. I checked my MEID by typing *#06# and it matches what I have on the box.
EDIT: the bt.txt file int he imei folder does not have my MEID in it. Is it suppose to be in there?
I just copied and pasted a back up using root explorer to my sd card. I am on miui NS4G when doing this should I be on a stock rom?
Sent from my Nexus S 4G using XDA Premium App
seekis said:
After that whole incident I downloaded Samsung's Reflash tool and restored my phone back to stock.
Since then I have reflashed a custom kernel, but so far all is well. What exactly should be in the /efs folder as far as files.
My /efs folder has
Code:
imei>bt.txt
uart_path
bluetooth>bt_addr
nv.log
lost+found
Could you tell me if I am missing anything. I checked my MEID by typing *#06# and it matches what I have on the box.
EDIT: the bt.txt file int he imei folder does not have my MEID in it. Is it suppose to be in there?
Click to expand...
Click to collapse
Did you have a backup? Also where on samsung's site is and how to use it please? And is there one that will work on nexus s?
Sent from my Nexus S using Tapatalk
Isnt this something that only gets messed with if you use someone elses Nandroid?
A custom rom doesnt normally mess with that folder, i thought...
Anyway, i have a Nandroid of my phone from before i flashed anything to it, so i assume im covered with that.
Can the OP please post a method to do the back up before making it a sticky tab?
Pointless to make it sticky and we still had to find the way to back up ourself. LOL
window7 said:
Can the OP please post a method to do the back up before making it a sticky tab?
Pointless to make it sticky and we still had to find the way to back up ourself. LOL
Click to expand...
Click to collapse
Agree even though it is pretty easy with Root Explorer. Just go to the root of the phone and find the folder called "efs". Long press the folder and choose copy. Go to the "sdcard" and paste it. I also suggest connecting your phone to your computer and save the "efs" folder to your computer somewhere you'll be able to find it.
An alternative to root explorer, you can use IO file manager (I think it works)/
From this thread ADB is also very easy.
Open a terminal emulator or ADB on your computer and type
su
busybox cp -a /efs /sdcard/
back up the file on your computer and you're done
AshsToAshs said:
Isnt this something that only gets messed with if you use someone elses Nandroid?
A custom rom doesnt normally mess with that folder, i thought...
Anyway, i have a Nandroid of my phone from before i flashed anything to it, so i assume im covered with that.
Click to expand...
Click to collapse
Nandroid doesn't touch this folder, it seems. Best to make a backup on your own to be safe.
Zehlek said:
Did you have a backup? Also where on samsung's site is and how to use it please? And is there one that will work on nexus s?
Sent from my Nexus S using Tapatalk
Click to expand...
Click to collapse
I did not have a previous back up. I pulled mine from my phone with adb. I have no idea about your other questions.
window7 said:
Can the OP please post a method to do the back up before making it a sticky tab?
Pointless to make it sticky and we still had to find the way to back up ourself. LOL
Click to expand...
Click to collapse
If you already have adb, just do this:
Code:
adb pull /efs
seekis said:
I did not have a previous back up. I pulled mine from my phone with adb. I have no idea about your other questions.
Click to expand...
Click to collapse
You said you used Samsung reflash tool. I was wondering where I can download it and how to use it
Sent from my Nexus S using Tapatalk
seekis said:
If you already have adb, just do this:
Code:
adb pull /efs
Click to expand...
Click to collapse
I already flashed sense 0.3 and didn't backup
Sent from my Nexus S using Tapatalk
im still trying to figure out what exactly is getting messed with as the OP did not describe why we needed to back up this folder and or what could be messed up if we don't.
Any info would be great.
Zehlek said:
I already flashed sense 0.3 and didn't backup
Sent from my Nexus S using Tapatalk
Click to expand...
Click to collapse
well try it anyway and see what you get...i already flashed a different rom too, but the folder was still there
seekis said:
im still trying to figure out what exactly is getting messed with as the OP did not describe why we needed to back up this folder and or what could be messed up if we don't.
Any info would be great.
Click to expand...
Click to collapse
Look at this thread here. People are losing their IMEI number and is resulting in no service. If you back up the efs folder, it saves this information in case it happens to you.
I pulled it to my sdcard and computer. The imei folder is empty. I don't see a txt file and the bin files are all weird coding
Sent from my Nexus S using Tapatalk
Zehlek said:
I pulled it to my sdcard and computer. The imei folder is empty. I don't see a txt file and the bin files are all weird coding
Sent from my Nexus S using Tapatalk
Click to expand...
Click to collapse
Yeah, I just finally looked at my imei folder that I saved to my computer and it only has one bt.txt file...
Hey,
I was just wondering, is there a way to create a flashable ROM (.zip) from an existing backup??
I have used CWM Recovery to create a backup of a ROM that I'm using (BlackICE). It has been customized to an extreme point. Removed several system apps and pushed my own apps to the system. Now I want to save it as a flashable ROM so that others, specifically a few of my friends, could also use it.
Any help would be greatly appreciated.
Thanks!
You could download a ROM, then use the kitchen in the Chef Central section to add all if your stuff and remove the original developers stuff. That's the fastest way I know. I'm sure there is a better way.
Sent from my HTC Glacier using XDA App
Thanks. I know of that method, I was just wondering if it were possible to directly convert a backup to a ROM.
I'll keep searching. Thanks though =)
SH31KH said:
Thanks. I know of that method, I was just wondering if it were possible to directly convert a backup to a ROM.
I'll keep searching. Thanks though =)
Click to expand...
Click to collapse
I've never tried but you may be able to open the backup and get the data from it
Sent from my HTC Glacier using xda premium
Root explorer will allow u to zip the archive and make it flashable.. just go to ur back up location, long press it, then hit zip this file.. it'll be saved to the speed software folder
Sent from my HTC Glacier using xda premium
Kinda slow with my responses but I tried that and although it did create a zip, I was unable to flash it because the file wasn't signed.
Another question comes to mind..
If I give my backup to someone else, will they be able to restore from it? By placing my backup folder into their /sdcard/clockworkmod/backup/ ??
Just curious =)
Sent from my Htc Glacier using XDA App
SH31KH said:
Kinda slow with my responses but I tried that and although it did create a zip, I was unable to flash it because the file wasn't signed.
Another question comes to mind..
If I give my backup to someone else, will they be able to restore from it? By placing my backup folder into their /sdcard/clockworkmod/backup/ ??
Just curious =)
Sent from my Htc Glacier using XDA App
Click to expand...
Click to collapse
You could try toggling signature verification in CWM and then you should be able to flash..
SH31KH said:
Kinda slow with my responses but I tried that and although it did create a zip, I was unable to flash it because the file wasn't signed.
Another question comes to mind..
If I give my backup to someone else, will they be able to restore from it? By placing my backup folder into their /sdcard/clockworkmod/backup/ ??
Just curious =)
Sent from my Htc Glacier using XDA App
Click to expand...
Click to collapse
Yes, that should work, as long as you have the same phones (mytouch4g). although, any texts or personal contact info will also restore to your friends phone
Nicgraner said:
You could try toggling signature verification in CWM and then you should be able to flash..
Click to expand...
Click to collapse
Greetings,
I made image files with dd command (boot.img, recover.img, system.img, etc.).
I zipped them, but when I wanted to flash them (usin toggling the signature), it requests an update file, which is not available.
(the phone is a bit different, Alcatel 918D)
I have been looking for the solution for 3 days with google.
Could anybody suggest?
Thanks,
Cappa.