Related
i have three nandroid backups and have never had a problem what so ever with them....seems like eversince i renamed them to keep track of them i tried to use them and they give me and error saying run via adb...does anyone one have any insight?
im an iddiot mods delete this
aauussttiinn88 said:
i have three nandroid backups and have never had a problem what so ever with them....seems like eversince i renamed them to keep track of them i tried to use them and they give me and error saying run via adb...does anyone one have any insight?
Click to expand...
Click to collapse
Actually the last time I tried to restore I had the same issue. Not sure what the remedy is, but I had to just re-flash the Modaco ROM I was running prior to trying out the 2.1 Rom. Wish I knew what was going on.
just figured it out...let me ask you this did you rename your nandroid backups?
aauussttiinn88 said:
just figured it out...let me ask you this did you rename your nandroid backups?
Click to expand...
Click to collapse
No, I just have a ton of them in my nandroid folder but never changed any names.
It names the backup based on the source device serial number and the time the backup was made. This, I think, is how it knows which one is the latest. I had this problem once before and the trick was to create the following folder structure in the root directory of your sd card:
nandroid\[insert device serial number]\BCDMRS-20100205-2102\
Note the BCDMRS-20100205-2102 is just a folder name I took from my nandroid folder. If you created the nandroid folder as I describe and have just one backup you can use the same folder name I did and put your backup in it.
An alternative method would be to do a nandroid backup to recreate the paths on your sdcard and overwrite the contents of your equivalent of BCDMRS-20100205-2102 with your older backup.
I didn't get much sleep so sorry if this doesn't make sense.
aabbccddeeffgghh said:
It names the backup based on the source device serial number and the time the backup was made. This, I think, is how it knows which one is the latest. I had this problem once before and the trick was to create the following folder structure in the root directory of your sd card:
nandroid\[insert device serial number]\BCDMRS-20100205-2102\
Note the BCDMRS-20100205-2102 is just a folder name i took from my nandroid folder. If you created the nandroid folder as i describe and have just one backup you can use the same folder name I did and put your backup in it.
Click to expand...
Click to collapse
Cool i will try that and see if it works. Actually im not all that pressed to backup any of my nandroids, so if this doesn't work I am going to delete all of mine and make just one backup to what im running now and hopefully that one will work if I ever need to restore. But thanks for the info.
You posted as I was editing my post. The alternate method might work better.
yea i just renamed my nandroid backups to the date in which i created them ie. 20100303 and that worked...weird i think but it works like a charm
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...
In the need to recover a deleted SMS thread, I have recently found out that the SQLite database file mmssms.db retains deleted data, which means that I could, in theory, recover the conversation thread which had vital information that I need back. The problem is that this file is located somewhere in an area inaccessible without rooting the phone, and doing so seemingly will erase the file, making this whole process pointless.
I have done some research and realized most backups only save the com.android.providers.telephony.json and .ab files, which only have data from non-deleted texts. Also, please correct me if I am wrong, but it seems I am only capable of backing up files from the "sdcard" folder and nothing from other folders such as "root" and "data" (which on my unrooted phone appear empty), the two possible locations for the mmssms.db file. I would like to know if there is any possible way of accessing this file without having to root the phone or if I am safe to root the device without the risk of wiping mmssms.db.
Thanks in advance. Recovering those messages would greatly help my cause.
henriliveira said:
In the need to recover a deleted SMS thread, I have recently found out that the SQLite database file mmssms.db retains deleted data, which means that I could, in theory, recover the conversation thread which had vital information that I need back. The problem is that this file is located somewhere in an area inaccessible without rooting the phone, and doing so seemingly will erase the file, making this whole process pointless.
I have done some research and realized most backups only save the com.android.providers.telephony.json and .ab files, which only have data from non-deleted texts. Also, please correct me if I am wrong, but it seems I am only capable of backing up files from the "sdcard" folder and nothing from other folders such as "root" and "data" (which on my unrooted phone appear empty), the two possible locations for the mmssms.db file. I would like to know if there is any possible way of accessing this file without having to root the phone or if I am safe to root the device without the risk of wiping mmssms.db.
Thanks in advance. Recovering those messages would greatly help my cause.
Click to expand...
Click to collapse
You can recover ur sms before the rooting because after rooting ur phone would left with 0 sms's.
D_RiDeRs said:
You can recover ur sms before the rooting because after rooting ur phone would left with 0 sms's.
Click to expand...
Click to collapse
How would I go about recovering deleted text messages without having root access?
henriliveira said:
How would I go about recovering deleted text messages without having root access?
Click to expand...
Click to collapse
While googling for more than half an hour I got the solution to ur problem. Here:-
1.
2.
You can try the first one first because it has trial version available.
Best of Luck!! :good:
Thanks for the help, but I have already tried both, the former does not support MTP phones and the latter needs root access.
henriliveira said:
Thanks for the help, but I have already tried both, the former does not support MTP phones and the latter needs root access.
Click to expand...
Click to collapse
Good to know. MTP is a blessing and a curse.
is possible to root without wiping data, this is a security issue, but for you it's fine:
http://forum.xda-developers.com/showthread.php?t=2266928
having a custom recovery will make you able to install the necessary files to root your phone.
EDIT: Reading the previous thread, there was a comment with another way of rooting the phone, without wiping data, try the one that is easier for you.
http://forum.xda-developers.com/showthread.php?t=2300480
moxtrom said:
is possible to root without wiping data, this is a security issue, but for you it's fine:
http://forum.xda-developers.com/showthread.php?t=2266928
having a custom recovery will make you able to install the necessary files to root your phone.
EDIT: Reading the previous thread, there was a comment with another way of rooting the phone, without wiping data, try the one that is easier for you.
http://forum.xda-developers.com/showthread.php?t=2300480
Click to expand...
Click to collapse
Thanks a lot man, I tried the second one and it worked perfectly.
Also. You can adb pull the file without root as long as you know it's location.
Adb pull /data/data/com.android.providers.telephony/databases/mmssms.db
You would need root to modify and replace it though.
And when you put it back you also have to chmod and chown it
Sent from my Nexus 4 using xda app-developers app
You can also download go sms from play store, it has a backup feature, so you can backup before wiping, it will create a backup file on your "sd card", then wipe, install go sms again after wiping, restore, and eventually delete go sms if you don't want it that's what I do, and it works
Sent from my Nexus 4 using xda app-developers app
gallardo5 said:
You can also download go sms from play store, it has a backup feature, so you can backup before wiping, it will create a backup file on your "sd card", then wipe, install go sms again after wiping, restore, and eventually delete go sms if you don't want it that's what I do, and it works
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
It backs up deleted text messages?
Guessing you didn't read the OP.
Sent from my iPad 4
I've been lucky not to lose my EFS data so far. But now I really need to back that up.
I've been reading about problems with TWRP, and I allready have CWM, which I really like.
Is there an easy "noobproof" way to make EFS backup?
For Samsung, there is EFS Professional but I don't know if it works with LG G2.
Another way I found is from another Samsung thread: Backup your EFS IMMEDIATELY, but same thing, I don't know if that'll work with G2
Any help, anyone?
Hi,
Take a look here: EFS Partition Backup and More [All G2 Variants] *Fixed*.
EDIT: I misread, you want to keep CWM...
viking37 said:
Hi,
Take a look here: EFS Partition Backup and More [All G2 Variants] *Fixed*.
EDIT: I misread, you want to keep CWM...
Click to expand...
Click to collapse
I was thinking, I'd install TWRP through goomanager, make EFS backup and go back to CWM.
But if something happens, I should have TWRP installed to restore EFS?
terhiha said:
I was thinking, I'd install TWRP through goomanager, make EFS backup and go back to CWM.
But if something happens, I should have TWRP installed to restore EFS?
Click to expand...
Click to collapse
CWM backs them up. The problem is, they only seem accessible/viewable in CWM. I can not get to the folder in a file explorerexplorer, yet can see them in CWM.....?
Steamer86 said:
CWM backs them up. The problem is, they only seem accessible/viewable in CWM. I can not get to the folder in a file explorerexplorer, yet can see them in CWM.....?
Click to expand...
Click to collapse
What I've been reading, CWM doesn't backup EFS.
Where did you read it does?
terhiha said:
What I've been reading, CWM doesn't backup EFS.
Where did you read it does?
Click to expand...
Click to collapse
I used the zips, and did it in CWM. The folders are present and viewable in recovery, not upon boot. They are created before emulation/0 in CWM. I'm gonna go check if I can somehow move them in CWM... and check files. I'll be back.
Edit: Use the one that makes the zip. CWM shows it created and there, but I can not access it past this to verify it and or it it works and is correct. I am not going to flash it and take that risk.
Steamer86 said:
I used the zips, and did it in CWM. The folders are present and viewable in recovery, not upon boot. They are created before emulation/0 in CWM. I'm gonna go check if I can somehow move them in CWM... and check files. I'll be back.
Click to expand...
Click to collapse
I used the efsbackup zips in CWM.
I initially encountered the same problem with not being able to find the files. From memory I was able to get to the by using a file browser with root capabilities (in my case solid explorer) go back to the root directory then Data\Media. In there I found my efs backup files as well as my CWM nandroid backup.
drc13 said:
I used the efsbackup zips in CWM.
I initially encountered the same problem with not being able to find the files. From memory I was able to get to the by using a file browser with root capabilities (in my case solid explorer) go back to the root directory then Data\Media. In there I found my efs backup files as well as my CWM nandroid backup.
Click to expand...
Click to collapse
The zip and individual files are there in their respective folders, as well other backup data. You sir, are my hero of the day.
The zip method is extremely smaller than individual files...
Steamer86 said:
The zip and individual files are there in their respective folders, as well other backup data. You sir, are my hero of the day.
The zip method is extremely smaller than individual files...
Click to expand...
Click to collapse
That's great news, glad I could help!
I've been wanting to post it in the development thread as a few people had asked something similar but unfortunately I don't meet the post count requirements to help them out!
I quoted your post over there.
I'm not able to move "EFS_backup" anywhere. I try, but moved folder stays empty. It shows "efsbackupflashable.zip", "efs1.img" and "efs2.img"
But they all are 0kb.
I found EFS_backup from data/media, all 3mb large.
Whit root explorer, I copied Efs_backup folder, to another folder in my sdcard, with root explorer I can see it there, but I cant copy it or to my computer.
How do I get it to safe place???
The other zip works too for individual files. I used ZArchiver to zip them up. Sent a copy to my PC with ES File Explorer over lan and uploaded another copy to Google Drive. You should be able to grab anything from SD to PC when plugged in USB. I replaced su with SuperSU a while ago. Actually get prompt permissions now. The OG SU on this phone with root method didn't play well. Also, make sure you show hidden files, PC and Phone explorer.
Steamer86 said:
The other zip works too for individual files. I used ZArchiver to zip them up. Sent a copy to my PC with ES File Explorer over lan and uploaded another copy to Google Drive. You should be able to grab anything from SD to PC when plugged in USB. I replaced su with SuperSU a while ago. Actually get prompt permissions now. The OG SU on this phone with root method didn't play well. Also, make sure you show hidden files, PC and Phone explorer.
Click to expand...
Click to collapse
Thanks!! Via Root Explorer I emailed this for me and uploaded to Google drive. Size looks fine.
Now i have my EFS backup and I can continue my search for best ROM for me!
sorry for being dumb but do i use the zip from EFS Partition Backup and More [All G2 Variants] *Fixed* link and just flash it in cwm for the efs backup
Yes
And what if I just root my g2, download ES-Explorer then go to the root of the internal and just copy and paste the efs folder?
Shouldn't that work too?
Kalaidos said:
And what if I just root my g2, download ES-Explorer then go to the root of the internal and just copy and paste the efs folder?
Shouldn't that work too?
Click to expand...
Click to collapse
stick to proven methods......
Sent from my LG-D802
Ok thank :crying:
Not sure whether or not this is actually a EFS backup. It just showed up in my External SD card and it's named 'efs.tar.gz' and it's only about 5kB. What does the EFS folder contain? I have folders such as bluetooth, WiFi, IMEI, carrier, etc.
Is it necessary to do a EFS backup nowadays?
How would I do an EFS backup?
emckai said:
Not sure whether or not this is actually a EFS backup. It just showed up in my External SD card and it's named 'efs.tar.gz' and it's only about 5kB. What does the EFS folder contain? I have folders such as bluetooth, WiFi, IMEI, carrier, etc. Is it necessary to do a EFS backup nowadays? How would I do an EFS backup?
Click to expand...
Click to collapse
Yes, DO make a backup of your EFS folder. Find the folder on your phone (I am away from my phone right now, but I believe it is a folder off of the root directory). You can easily find this folder (on a rooted phone) by using a file manager app-- then copy the entire folder and keep one copy of it on your SD card and keep ANOTHER copy of the EFS folder on your desktop computer or off-phone on a disk.
There are several threads here by folks who have lost their EFS folders or some setting on their phones, which can only be re-aligned by the data stored in the EFS folder. I believe at least some of the data is unique to your own phone, so it can't just be copied from another phone without some effects.
EFS folder seems like a small thing until it is gone. Then it really is a major pain in the neck to recover. MAKE YOUR OWN BACKUP COPIES of it now. Please search some threads --usingthe term EFS! -- and you will see more details about the effects of corrupt or missing EFS files.
Good luck!
markbc01 said:
Yes, DO make a backup of your EFS folder. Find the folder on your phone (I am away from my phone right now, but I believe it is a folder off of the root directory). You can easily find this folder (on a rooted phone) by using a file manager app-- then copy the entire folder and keep one copy of it on your SD card and keep ANOTHER copy of the EFS folder on your desktop computer or off-phone on a disk.
There are several threads here by folks who have lost their EFS folders or some setting on their phones, which can only be re-aligned by the data stored in the EFS folder. I believe at least some of the data is unique to your own phone, so it can't just be copied from another phone without some effects.
EFS folder seems like a small thing until it is gone. Then it really is a major pain in the neck to recover. MAKE YOUR OWN BACKUP COPIES of it now. Please search some threads --usingthe term EFS! -- and you will see more details about the effects of corrupt or missing EFS files.
Good luck!
Click to expand...
Click to collapse
Good advice, but I think more than just the EFS folder itself needs to be backed up in order to be able to restore EFS information to the phone if needed. Backing up or making a copy of the actual EFS "folder" is only part of the equation. TWRP variants usually offer an option to properly back up EFS and I have also seen several apps on the market, but I have not personally tried any of them. If anyone has any experience in methods to back up and restoring the EFS information to the phone please post your experience.
So basically all I have to do is copy the efs folder located in the /~ directory and memorize the permissions. And if anything happens I can just restore that folder and the set the permissions back?
emckai said:
So basically all I have to do is copy the esf folder located in the /~ directory and memorize the permissions. And if anything happens I can just restore that folder and the set the permissions back?
Click to expand...
Click to collapse
yikes. . . not so sure (anymore) that a copy/paste and a chmod will be enough. . . A quick search for recover ESF provides numerous results inside XDA.
It seems that there are several methods to doing an effective backup of ESF data (and by effective, it means more than our copy folders!). The below thread by @tamirda offers several techniques for the I9500 model of the S4! This ESF process does seem to be "kind of" phone-specific, but perhaps some processes are fungible among all models.
http://forum.xda-developers.com/showthread.php?t=2392632
From my quick (as yet unfinished) reading of some of the threads, it seems good to also know your IMEI #, independent of the ESF folder. Also --as @scott14719 stated--- there *is* more to it than just replacing the folder contents
@emckai, before you question, I was sanguine just having the folder backed up -now I am not. So thank you for asking this question! The answer is more than I thought!
Already I hit Play and downloaded/tried one of the programs. It loaded and "backed up" my ESF folder -then hot booted. However, I have not trashed my ESF data to test it so I will have to wait and see. (Some of the comments made it sound not so promising.)
But it also seems Odin can backup the ESF/IMEI data and restore it as well! I was going to see if Mobile Odin could do this too but I am running a 4.3 rom and Mobile Odin does not work so well on 4.3 yet..
Thanks. . .I have some more reading to do to protect my ESF :victory:
Edit: not sure, but perhaps that tar file for your ESF might be left there from an original Odin Flash of a kernel or rom. . .
Yeah I did some reading also around the XDA forums and some information found on Google but the information I found wasn't that useful; mostly because it was device specific.
After looking inside the EFS folder, each file had it's own permission which would cause a headache at the end.
Doesn't TWRP recovery have the option to backup the EFS folder? But it would be the same thing? Because apparently there are 2 blocks on the device where the IMEI information is stored and whenever something happens to the EFS folder or one of the blocks, it'll trigger on the Samsung boot screen and restore whatever is contained inside those blocks.
There is a lot of misinformation going around stating about EFS so I'm just left confused.