Database Info

[Q] Can you rename Rom backup folders?

noob question i know however just a quick one,
can you rename nandroid backup folders with messing up md5sum ?
i load a ton of roms on the regular [a junkie i know] basis and get flustered when i have tons of backups but they are all dated

great question i also would like to know never had the balls to try cuz it says something about messing it up i know in rom manager u can under manage and restore (i think) also rom manager doesnt see ur cwm backups i usually go through ando zip but yea id def like to kno

Suprah said:
noob question i know however just a quick one,
can you rename nandroid backup folders with messing up md5sum ?
i load a ton of roms on the regular [a junkie i know] basis and get flustered when i have tons of backups but they are all dated
Click to expand...
Click to collapse
I don't know if you can rename the folders themselves, but you CAN rename the backup file itself. I use Root Explorer to do this. Just make sure you don't put any spaces in the new file name. You can use dashes and underscores to separate words and numbers, though.

Someone in the past said you can download mand5 to generate a new md5 sum, but I haven't tried it.

@visedmonk do u think andro zip will work it says it will let me rename then i click on that and it says change to file extension can make file unusable and i dont space any letters for instance il put cm for (cyanogenmod) rite next to the numbers havent had the balls to try it

sarni84 said:
@visedmonk do u think andro zip will work it says it will let me rename then i click on that and it says change to file extension can make file unusable and i dont space any letters for instance il put cm for (cyanogenmod) rite next to the numbers havent had the balls to try it
Click to expand...
Click to collapse
I dunno. I've never used andro zip. Only one way to find out...
But seriously, it should work. To be safe, though, make a copy of the file you want to rename and place the copy with the unaltered name on your computer or sd card or whatever. Then you can rename the file and see if it works. If it does, great. If it doesn't, you still have the backup you need.

Suprah said:
noob question i know however just a quick one,
can you rename nandroid backup folders with messing up md5sum ?
i load a ton of roms on the regular [a junkie i know] basis and get flustered when i have tons of backups but they are all dated
Click to expand...
Click to collapse
Don't know if you're using "nandroid" generically to refer to both the true nandroid as well as CWM but I rename CWM backup folders all the time and have never had trouble restoring them. I've done it from ROM Manager, via a file manager and also via ADB.

short/y said:
Don't know if you're using "nandroid" generically to refer to both the true nandroid as well as CWM but I rename CWM backup folders all the time and have never had trouble restoring them. I've done it from ROM Manager, via a file manager and also via ADB.
Click to expand...
Click to collapse
im talking about the folder not the actual files in the folder.
i just want to organize my roms so i can always jump between each

@suprah name it like this ex, 2011-06-16.05.57.13.....
you want...2011-06-16.05.57.13gingerbread ? rite well when i try that in andro zip it sayin it will make file unusable.... n i guess i will have to try and i always used to use rom manager and just go to manage and restore backups but its different with this phone especially cuz rom mana doesnt see cwm i guess?

Suprah said:
im talking about the folder not the actual files in the folder.
i just want to organize my roms so i can always jump between each
Click to expand...
Click to collapse
Yup, that's exactly what I'm talking about. I rename the folders all the time and have no problems restoring.

short/y said:
Yup, that's exactly what I'm talking about. I rename the folders all the time and have no problems restoring.
Click to expand...
Click to collapse
alright welp as long as you rename the folder without any spaces, then there would be no problem with restoring nandroid backups

nice nice will try soon cuz yea i have like 6 backups on here n was writing the date down with a name lmao

I renamed the folder once and couldn't restore. It was making a reference to the md5 file.
What I did to fix the backup is rename the folder again but this time without spaces and then it let me restore without any problems.
Now my Nandrioids are all organized
Hope that helped
Sent from my Bionix 2 - A TeamWhiskey Production using XDA App

the stock rooted nandroid restore that's posted in the dev section is renamed to LG-P999-V10f. it's not the typical date format. and alot of people have used it. so the answer is ....yes.

crazythunder said:
the stock rooted nandroid restore that's posted in the dev section is renamed to LG-P999-V10f. it's not the typical date format. and alot of people have used it. so the answer is ....yes.
Click to expand...
Click to collapse
jus making sure, im not a dev so i assumed that was possible with some code editing

moshe22 said:
I renamed the folder once and couldn't restore. It was making a reference to the md5 file.
What I did to fix the backup is rename the folder again but this time without spaces and then it let me restore without any problems.
Now my Nandrioids are all organized
Hope that helped
Sent from my Bionix 2 - A TeamWhiskey Production using XDA App
Click to expand...
Click to collapse
Could be there's a coding error in the recovery code and stops parsing the directory name when it hits a space. The md5 file only references the individual files not the directory.
In general it's better to stay away from spaces in file and directory names. Back in the early days of *nix spaces were verboten and there are still some vestigial issues lurking either in the code or in the coding habits of some people. It's rare but it does happen. Hyphens, underscores, periods are all OK though.
Sent from my Xoom using Tapatalk

If after you rename the folder you get an md5 error. This http://forum.xda-developers.com/showthread.php?t=714114 can help you fix it.
BE SURE AND READ THAT POST COMPLETELY
It's imperative that one not generate an md5 sum for a nandroid that is actually corrupted. That will wreak all kinds of havoc on your system.
ONLY PERFORM THE ABOVE IF YOU KNOW ITS NOT RESTORING DUE TO A NAME CHANGE
EDIT: For the record, the above commands can be performed from terminal emulator if you know what bits to leave out. Saved me a few steps.

I rename all of my nandroid backups. They are easy to get confused otherwise. The only thing I change is the year in the date, and leave the month/day alone.
Sent from my LG-P999 using XDA Premium App

Yea I downloaded the Stock Nandroid and loaded it. I renamed the folder and got a MD5 error. Now I'm not sure it if was because of the rename or because it was a bad download to begin with.
I think I still have the file on my pc and possibly find the MD5 checksum before copying it over this time.

player911 said:
Yea I downloaded the Stock Nandroid and loaded it. I renamed the folder and got a MD5 error. Now I'm not sure it if was because of the rename or because it was a bad download to begin with.
I think I still have the file on my pc and possibly find the MD5 checksum before copying it over this time.
Click to expand...
Click to collapse
Most likely because you renamed it
Sent from my LG-P999 using XDA App

[Q] Change Nandroid Backup Name

I finally rooted TF and flashed Revolution HD. I understand that ROM Manager does not work with the TF. I want to be able to change backup names w/o messing up md5. Is there method or app for this?

go into file manager and change the name of the .zip

What zip? I have the CWM backup folder with sub folders for each backup and the 4 nandroid files in each.

mrevankyle said:
go into file manager and change the name of the .zip
Click to expand...
Click to collapse
Actually it looks like I can change the folder name for the Nan back without problem.

I thought that changing the names of the Nandroid backups would cause a restore to fail....unless the name was reverted back to it's original name.

HuskerWebhead said:
I thought that changing the names of the Nandroid backups would cause a restore to fail....unless the name was reverted back to it's original name.
Click to expand...
Click to collapse
That's what I feared. Evidently it's OK to change the directory name that contains the files. I tried a restore after and it went fine. Makes sense that the file md5 sum is not affected by chance nging folder name.

Hi, I changed the name of the folder and BAM!!.. the restore failed! I had two backups of two different ROM's and could not restore either of them after name changing! I managed to put back the old names and now both work. But I still need a way to identify so was wondering if there was any way to change the name and yet keep the md5 sum intact!!

MysticPhantom said:
Hi, I changed the name of the folder and BAM!!.. the restore failed! I had two backups of two different ROM's and could not restore either of them after name changing! I managed to put back the old names and now both work. But I still need a way to identify so was wondering if there was any way to change the name and yet keep the md5 sum intact!!
Click to expand...
Click to collapse
Usually a simple name change should still work. If you use symbols and stuffs in the name it might not work.
The latest version of TWRP let you name you nandroid backup.

IMEI Null, have nv_data.bak , not able to overwrite :(

So,
I tried the Galaxy S unlock software from the market, and now I am getting null/null as IMEI and I am not able to use it on any network..
Now, I saw in my sd card, there is a file nv_data.bak , that is around 20mb file...now I am trying to overwrite the one that exits in the efs folder, but its not letting me do it, saying I don't have enough space...
I am not even sure if the nv_data.bak is the actual file, I mean its like 20mb..is it supposed to be this big?
Would really appreciate if someone can tell me how to proceed from here...
I am currently on 2.2.1 Froyo.VUVKD1 kernel and 2.6.32.9 firmware.
Thanks

jackdowsan said:
So,
I tried the Galaxy S unlock software from the market, and now I am getting null/null as IMEI and I am not able to use it on any network..
Now, I saw in my sd card, there is a file nv_data.bak , that is around 20mb file...now I am trying to overwrite the one that exits in the efs folder, but its not letting me do it, saying I don't have enough space...
I am not even sure if the nv_data.bak is the actual file, I mean its like 20mb..is it supposed to be this big?
Would really appreciate if someone can tell me how to proceed from here...
I am currently on 2.2.1 Froyo.VUVKD1 kernel and 2.6.32.9 firmware.
Thanks
Click to expand...
Click to collapse
I've actually had that happen while flashing ROMs before... I crapped myself.
I fixed it by flashing to another ROM then to stock. Not promising a fix, but it worked for me, hell, its worth a shot eh?

Thanks...so should I try and flash back to Stock?

jackdowsan said:
Thanks...so should I try and flash back to Stock?
Click to expand...
Click to collapse
I would, yeah. When It happened to me I was flashing to a GB ROM, so I ended up flashing to another GB ROM and it was the same so I flashed back to 100% stock and it was back to normal. No clue on how or why it happened XD

flashed stock again...still NULL IMEI...I think I should flash one other rom before stock? Can you tell me which one you did?

jackdowsan said:
flashed stock again...still NULL IMEI...I think I should flash one other rom before stock? Can you tell me which one you did?
Click to expand...
Click to collapse
To be honest with you man I haven't the slightest clue. Mine may have fixed itself by random chance, or the reasons behind the problem are different. I just flashed a few times out of frustration and blind hope XD

Also, can you tell me what is the size of your original nv_data.bin?
I have a backup on sd card, that is like 20mb...and the one in efs folder is like 2 mb.... strange

jackdowsan said:
Also, can you tell me what is the size of your original nv_data.bin?
I have a backup on sd card, that is like 20mb...and the one in efs folder is like 2 mb.... strange
Click to expand...
Click to collapse
Im not finding a .bin titled nv_data. I've got an nv.log in my efs folder, thats the closest I see, its 400-some bytes.

It should be in efs\root\afs\settings
Would be great if you can look once and tell me...

jackdowsan said:
It should be in efs\root\afs\settings
Would be great if you can look once and tell me...
Click to expand...
Click to collapse
Herp derp im a tard! XD
Its 256kb

No problems..thanks mate, atleast now I know that 20mb is of no use...

jackdowsan said:
No problems..thanks mate, atleast now I know that 20mb is of no use...
Click to expand...
Click to collapse
Im thinking maybe that app you DLd was for the wrong phone or was just a crap app to begin with... there's gotta be a way to get it fixed but I can't speculate on it, I'll leave it to the smarter people here =X

do you have an nv_data.bin file in your /efs/ folder? Can you copy and email me the one in your /efs/root/afs/settings/ folder? I think IMEI NULL/NULL is different than the all 0's problem.

dagentooboy said:
do you have an nv_data.bin file in your /efs/ folder? Can you copy and email me the one in your /efs/root/afs/settings/ folder? I think IMEI NULL/NULL is different than the all 0's problem.
Click to expand...
Click to collapse
Thanks a lot for taking your time out to look into this, I have mailed you my nv_data.bin
Let me know how it goes, I am hopeful
Thanks
Jack

Anyone? I am still stuck here

Bump....anyone?

Rename nv_data.bak to nv_data.bin
I think you used a bad unlocking program.
Anyway, it created the backup, so rename and push.
But, delete a duplicate from efs if there is one.
also, try adb push, or repartition your phone if nothing works.

airfluip1 said:
Rename nv_data.bak to nv_data.bin
I think you used a bad unlocking program.
Anyway, it created the backup, so rename and push.
But, delete a duplicate from efs if there is one.
also, try adb push, or repartition your phone if nothing works.
Click to expand...
Click to collapse
re-partition would restore everything back? cause I think the backup is not working..

Try this
I had the same thing happen to me and this is how I solved it.
First check if you have any baseband version in phone settings -> about phone
If not your modem is not starting and this causes the null/null problem because of corrupt nv_data.bin.
1. rename your nv_data.bak to .bin
2. get root explorer and go to the efs/root/afs/settings folder
3. mount r/w if folder is r/o mounted
4. delete nv_data.bin and nv_data.bin.md5
5. copy your nv_data.bin from sdcard to this folder and reboot.
this fixed my screwed IMEI.
To get your unlock code just open the nv_data.bin file in a hex editor and look at adsress 1460 for something like 00 01 00 00 00 the text after this is your network lock code in PLAIN TEXT (if you use HxD free hex editor your code is in the ansi column in the right field) so just enter this to the phone and your phone is now unlocked.

brokencobba said:
I had the same thing happen to me and this is how I solved it.
First check if you have any baseband version in phone settings -> about phone
If not your modem is not starting and this causes the null/null problem because of corrupt nv_data.bin.
1. rename your nv_data.bak to .bin
2. get root explorer and go to the efs/root/afs/settings folder
3. mount r/w if folder is r/o mounted
4. delete nv_data.bin and nv_data.bin.md5
5. copy your nv_data.bin from sdcard to this folder and reboot.
this fixed my screwed IMEI.
To get your unlock code just open the nv_data.bin file in a hex editor and look at adsress 1460 for something like 00 01 00 00 00 the text after this is your network lock code in PLAIN TEXT (if you use HxD free hex editor your code is in the ansi column in the right field) so just enter this to the phone and your phone is now unlocked.
Click to expand...
Click to collapse
Does this still work ? ?

[Q] Can anybody explain what happened to my efs folder

Today I discovered that my Nexus S (9023) had no valid IMEI number. I suspect this happened while I was playing around with TWRP (I'm already back to CWM for the record).
Anyway, I saw no reason to panic, since I had backed up /efs back in june and I still had that backup.
At first, I tried to extract the tarball and copy it's contents to the /efs folder. This lead to my phone not even recognizing my sim card anymore. I tried several other methods of restoring my efs folder including this and this (edit: and this). I didn't succeed with any of these methods to get my sim recognized or have a valid IMEI number. In fact, I even ended up getting an efs folder inside the efs folder and another one inside that one (so ultimately leading to a /efs/efs/efs folder).
Then I wondered what would happen if I were to just delete the whole /efs folder. To be sure, I only renamed the thing to /efs_back. The result was amazing. Immediately, I had a valid IMEI number (the one that actually belongs to my phone). The efs_back folder was now gone however and /efs was back (with just the right content).
So what I can't help wondering is how my /efs folder was miraculously restored. Does the 9023 have some sort of self restoring feature, or did I do something right after all?

Today my IMEI was gone again, but I did not flash anything. I tried again renaming /efs to /efs_back and again, it was immediately replace by a /efs folder, but this time, I needed to reboot to get my IMEI back.
Can somebody please explain what's going on? I'm running CyberGR-MOD ver.8. Should I report my issues in the CyberGR-MOD thread?

Krekker said:
Today my IMEI was gone again, but I did not flash anything. I tried again renaming /efs to /efs_back and again, it was immediately replace by a /efs folder, but this time, I needed to reboot to get my IMEI back.
Can somebody please explain what's going on? I'm running CyberGR-MOD ver.8. Should I report my issues in the CyberGR-MOD thread?
Click to expand...
Click to collapse
Once you get it back, delete the bin files in the folder, then rename the bak files to bin files (ie: the bak files will become bin files after renaming!), reboot & see how you go from there! If all is well then it should stick on each reboot & you should then copy your efs folder to somewhere safe! Your bak files record the changes, so when you've deleted the bin files needed for connection & rename/change the bak files to bin files, the correct information that recorded the change should stick on each reboot!

CrackDaddy said:
Your bak files record the changes, so when you've deleted the bin files needed for connection & rename/change the bak files to bin files, the correct information that recorded the change should stick on each reboot!
Click to expand...
Click to collapse
I don't quite understand. Aren't the .bak files exact copies of the .bin files? And what do you mean by change? What change are you referring to?
Sent from my Nexus S using XDA App

..

Krekker said:
I don't quite understand. Aren't the .bak files exact copies of the .bin files? And what do you mean by change? What change are you referring to?
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
The bak file records any "changes" to the bin file (before you had a problem, ie: before your imei got corrupted!), meaning that if anything goes wrong with the bin file, the bak file will have the "correct" information stored on it before that "change" happened! Why not just try what I've said? because at this stage you have nothing to lose that you haven't already lost!
PS: if this fix doesn't correct your problem, try following this guide here: http://forum.xda-developers.com/showthread.php?t=881162 This works with the Nexus S also, good luck!

The problem is not how to fix my IMEI. I'm just very confused about why a simple renaming of the whole /efs folder fixes the problem and what caused my IMEI to get corrupted in the first place.
Sent from my Nexus S using XDA App

As the great member Election day taught me a great way of backing up the efs folder as .img by using the cat command in cwm recovery..as soon as you get a valid imei use that method.

Krekker said:
The problem is not how to fix my IMEI. I'm just very confused about why a simple renaming of the whole /efs folder fixes the problem and what caused my IMEI to get corrupted in the first place.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
Aside from user intervention, who knows why /efs managed to get corrupted - anything i say is just speculation.
As for the renaming, most likely some kind of factory-backup that was restored when you (effectively) deleted it. This is just fuel for figuring out whether these /efs backups mean anything when the phone can fix itself, but most of us are perfectly happy without the worry of sorting out our IMEI's

Help please! phone won't boot

So I think I made a stupid mistake.
I was trying to reset google wallet and It hung at 97% and wasn't able to reset. I used the google wallet installer to basically change my build prop to the nexus build prop. I figured it would just overwrite my original wallet app anyway, and once my build prop was changed to the nexus build prop I could simply reset the app from there.
Anyways, phone rebooted and it's stuck in a bootloop and isn't getting passed the boot animation screen. I can get into recovery mode and download mode just fine. I tried restoring a backup I had with CWM and it says "md5 mismatch error". I really have no idea what to do at this point, and would rather not go completely to stock since I know my data is still there. Also I'm concerned to even restore a backup because i'm pretty sure my build prop was changed. I'm also wondering if it would be possible to simply factory reset and flash a new rom on top of it.
Any help would be greatly appreciated.

which rom are you using?
extract its build.prop and flash manually (if you know how to create a flashable zip)
if you are using a cm based rom, just reflash the rom without deleting anything..
and avoid using space while renaming backups... it gives md5 mismatch error

Khizar Amin said:
which rom are you using?
extract its build.prop and flash manually (if you know how to create a flashable zip)
if you are using a cm based rom, just reflash the rom without deleting anything..
and avoid using space while renaming backups... it gives md5 mismatch error
Click to expand...
Click to collapse
No idea how to create the flashable zip. However I did notice a tutorial, I guess now would be a good time to learn.
I'm using darthstalker X1, it's a touchwiz based rom so I can't simply flash the rom again.
I saved all of my backups on my external SD card, can I just simply hook it up to my computer and change the backup names? And is my build.prop included in the backup I made?
Thank you for responding.

BadUsername said:
No idea how to create the flashable zip. However I did notice a tutorial, I guess now would be a good time to learn.
I'm using darthstalker X1, it's a touchwiz based rom so I can't simply flash the rom again.
I saved all of my backups on my external SD card, can I just simply hook it up to my computer and change the backup names? And is my build.prop included in the backup I made?
Thank you for responding.
Click to expand...
Click to collapse
renaming the backups again might not fix
i believe to have seen a script for sgy which fixes md5 mismatch error. but you need to give commands from terminal emulator.
if you have more than one backup of the rom, try to restore system only
if any one of them works your phone will boot up again
Edit: your backups contain the build.prop file in system.(partition type).tar
just extract this
and partition type may be rfs or ext4

Khizar Amin said:
renaming the backups again might not fix
i believe to have seen a script for sgy which fixes md5 mismatch error. but you need to give commands from terminal emulator.
if you have more than one backup of the rom, try to restore system only
if any one of them works your phone will boot up again
Edit: your backups contain the build.prop file in system.(partition type).tar
just extract this
and partition type may be rfs or ext4
Click to expand...
Click to collapse
No idea how that is even done. I think I need windows and ADB in order to extract the build.prop, I have a mac.
I found a restore that worked, I just forgot to rename it and it wasn't too old thankfully.
I really appreciate you helping. And now I know of this mismatch error so I can name my backups correctly.

BadUsername said:
No idea how that is even done. I think I need windows and ADB in order to extract the build.prop, I have a mac.
I found a restore that worked, I just forgot to rename it and it wasn't too old thankfully.
I really appreciate you helping. And now I know of this mismatch error so I can name my backups correctly.
Click to expand...
Click to collapse
to extract backups u need a tar extractor
if the backup format is something like .tar.a or .tar.md5 rename it to .tar first
and restoring the system only of your working backup would have booted your phone (in advance restore in recovery)
anyway this was an experience too for you.. so you would be carefull next time

Khizar Amin said:
to extract backups u need a tar extractor
if the backup format is something like .tar.a or .tar.md5 rename it to .tar first
and restoring the system only of your working backup would have booted your phone (in advance restore in recovery)
anyway this was an experience too for you.. so you would be carefull next time
Click to expand...
Click to collapse
Restoring my system partition only from advanced restore worked perfectly. All my apps stayed how they were and I didn't have to update all of my apps after I restored. Way better than doing a full restore in this case.
Thank you for this advice, this will be a very helpful method to me if I make any mistakes while messing with anything in my system folder. And yes, it was certainly an experience for me.
Sent from my SCH-I535 using Tapatalk 2