Okay, so I have looked into the other posts about people not having anything in their /efs folder. So I bought an i957r from Rogers. Rooted it and have su and busybox installed. Astro shows that my /efs folder is empty. My IMEI is perfectly fine, all of my data services work, and I am sure root is installed. When I run the adb shell to pull my nv_data.bin, it tells me the file doesn't exist, and when I pull it from the sdcard, it is an empty file. Any ideas as to why that folder would be empty?
Also on a side note, if I was to factory reset it, with root installed, would it damage my device? The only reason I want to reset it is to get the /efs folder. Any help that can be given would be greatly appreciated. Thanks so much!!
Astro is lying to you. Astro also shows /efs to be empty on my ATT device, but if i get a root shell, it is NOT empty.
This is due to the default permissions on the /efs folder:
Code:
# ls -l | grep -i efs
drwxrwx--x system radio 2012-06-15 10:04 efs
Note the lack of read permissions for other users (not user system or member of group radio). If you change the permissions on the folder, say via:
Code:
# chmod 775 /efs
# ls -l | grep -i efs
drwxrwxr-x system radio 2012-06-15 10:04 efs
Astro would then should you the files in that folder. But that's probably not the best way to handle it... Just deal with the efs files from a root shell, not a user-level file browser like Astro.
Interestingly enough, my Tab 8.9, which has been through a hackathon and a half, doesn't have nv_data.bin file.. anywhere. I do have a /efs/redata.bin file, though.
I wonder if the lack of nv_data.bin is related to why my tab started displaying "Search Network Manually" when I turn LTE on, and sometimes randomly whines about an invalid SIM even though it then immediately connects and works like normal... I've been trying to root cause that change for a while, although it seems to have no negative effects. Probably leaving some whacky log entries on the carrier side of things, though... FWTW.
Do you all actually have an nv_data.bin in /efs?
Also, before someone else flames you... this thread does not belong in this forum... Use the main forum for non-development issues
Well thank you for not making me feel completely stupid, I wasn't really sure where to put it. Can you tell me how to move it? So I'm not "that guy"?
But as far as what I have, in the /efs folder, I have redata.bin, but no nv_data.bin and a couple of other files and folders.
I downloaded Root Explorer and it was able to show me what was in that folder. I also searched using that for nv_data... didn't find anything
But while I am already in the wrong forum, can you tell me if doing a factory reset will hurt my device? Also, if I don't have an nv_data.bin file, I can't unlock it, can I? Just hoping you could help. Thanks so much!
I could be wrong, but I believe only mods can move threads. Never tried, and don't see anything obvious.. Ah well, no big deal.
I wonder if these devices use something different than nv_data.bin? I mean, we both seem to get working LTE service without it, right? Other various posts found via gooogle show several folks that claim their corruption and/or lack of nv_data.bin results in no service.
I highly doubt a factory reset will do any damage, "factory reset" basically means wiping data and cache, which is quite safe. Factory reset doesn't touch /system, /boot, etc. The assumption is that the user never had access to modify /system, so wiping the cache and user data partitions results in a "factory fresh" condition.
No so much after you've haxxored up all sorts of stuff.
If you are looking to get back to as close to stock as possible, you are probably best off starting with the factory ODIN tarball, which I believe is still available on sammobile. It contains the boot, system, recovery, cache and two modem partitions (although it doesn't appear to contain an EFS image).
It would be interesting to see if a virgin device actually has this file. My suspicious is we are both missing this file because it never existed on the i957 in the first place. I believe another vector would be used to unlock the device, instead of the nv_data hack.
Futhermore, I believe the nv in nv_data means nvidia, who makes the Tegra chipset and associated radio modems which are used in devices based on Tegra. The i957 is based on the MSM8660 SOC, a Qualcomm part, which is an entirely different beast than the Tegra solution. Pretty much everything I can find online about hacking up nv_data.bin covers devices that are NOT based on Qualcomm SOCs, which in recent times is most devices not destined for LTE on AT&T or other similar carriers (Rogers/Bell/Telus).
The captivate had the nv data file and it was on a hummingbird chip which was the precursor to exynos
Sent from my SAMSUNG-SGH-I727 using xda premium
Related
After flashing Haykuro's H build to my girlfriend's phone without a wipe everything went a little screwy. So I moved all of her data to the ext2 partition of her sd card, flashed JF RC33 back to her phone and then tried symlinking the data directory. This brought back alot of the same issues (she was getting an inconsistent system ID error).
So I went back to the default data directory as it stood after flashing rc33 and started copying over the /data/data/[app package] folders from the sd card for only the apps that she really needed the data for and even though I can read them in the terminal, for some reason whenever I try to start any apps that I copied the folders over for, they force close immediately. My only thought is that maybe they're owned by the wrong group or something. I tried chmoding them all 777 to see if that helped, but it didn't. I know I have to do a chown to change the owner of the files, but what should I chown it to? 0?
/data/data/* is 755, and the content is owned by the various sandboxed users (Except a handful of androids own services, which is owned by 1000 and 1001).
Symlinking the data directory itself should work just fine, i had the whole data partition symlinked out, until i just decided to mount my ext2 partition as /data.
Well, symlinking the data directory isn't fine. As I said in the original post there's something wrong with her data directory and whenever I boot up with the entire thing symlinked it says it needs a factory reset as there are inconsistent system IDs. So I'm trying to just add them back one by one. Is there any way to determine which user/group ID an app is running as so I can chown the data folder for that app to be the same? My thought is it has to come down to an ownership issue.
I'm far from a guru, but you may want to consider a couple of things.
I finally moved my data off of my sd. I had tons of quirks and force closes as long as data was on the ext2 partition. You may consider just moving apps and dalvik-cache.
If it's your GID that is incorrect, you should be able to go into the sd/data and "ls -l" to see what the ownership for each file looks like. Then verify that is carrying over when you copy it back to internal flash. If it's changing the group you can do a chgrp and change it back to what ever it was in the sd/data directory. Same goes for ownership also... ls-l will tell you who owns it and what group. Like you said, you can chown to change that.
I reall don't think this is going to solve your problems, but give it a shot. Ultimately, i think you're going to have to wipe data. If you did a nandroid before it went south, you might be alright.
Beyond that, i got nuthin... Good luck.
If it was my phone, I would've just wiped it and not thought twice about it. But my g/f is a fanatic about her shopping lists, todo lists, etc.
What I'm thinking about doing when I get home is running a ls -l on the app directory to see if I can see what group ID each of the apps are running at because I'm fairly certain that's what the problem is. The apps are running as one user id after the wipe, but the data is owned by another user id that was being used before the wipe.
Run it, and quickly check the UID with ps ("busybox ash", then "ps", or jut "busybox ps"
, the first one starts a shell, so you only have to write "ps"), then compare to the UID/GID of the files (ls -l, again with busybox).
If they don't match, you should change them with "chown uid:gid /data/data/directory".
If the UID's GID's are correct, you should just copy the contents of the directories out, wipe, run the apps once, and copy the content back in (Then you'll know the correct UID).
You can always take a nandroid backup if you don't trust me
Thanks Joushou, that's actually what I was looking for. I couldn't remember the command to see what the apps are running as. Now, considering they force close immediately, would I be able to run ps before I click force close and still see the IDs?
So in this format, which numbers are the user/group ids? I'm guessing the username is the first column.
USER.....PID PPID...VSIZE RSS..WCHAN PC............NAME
app_24 174 33 89264 13412 ffffffff afe0c824 S com.android.calendar
app_28 186 33 86828 11076 ffffffff afe0c824 S com.android.alarmclock
app_36 217 33 88892 11828 ffffffff afe0c824 S edu.mit.locale
Nevermind, that was from a regular ps. Did busybox ps and it turned up the number I was looking for, thanks Joushou!
LPChris said:
Nevermind, that was from a regular ps. Did busybox ps and it turned up the number I was looking for, thanks Joushou!
Click to expand...
Click to collapse
So were you able to get it working again?
So. my IMEI is jacked up. I made a copy of /efs when I got the phone but instead of making an archive I did a straight copy, Seems like the fat filesystem owned the permissions.
I am trying to restore from that backup but I am not having luck. People say you can just drop those files into place but it seems that they are replaced after every reboot. What do the permissions need to be? I see that ownership needs to be 1001:1001. Also, can I do this on JH7 with any success?
If your flashed back to stock OTA JH7? Shouldn't need to have to restore them.
Only need to input that (if Android ID doesn't work) - you should be able to copy it using ADB shell and SU.
cp /dir/foo /dir/newfoo
I used the CWM flashable zip to get back to JH7, didn't use odin (im not at home yet, and this was eating away at me at work, heh).
Ill flash back with odin and then see where that gets me. For my own sanitys sake, could you tell me what the permissions are on your files in /efs?
i have a fix that worked for me posted in the dev section
bames said:
i have a fix that worked for me posted in the dev section
Click to expand...
Click to collapse
Hmm..my product id is correct (...AATT). Maybe my current files are only half borked. Ill try restoring to jf6 with odin and see where I get. Thanks for the reply
z28james said:
Hmm..my product id is correct (...AATT). Maybe my current files are only half borked. Ill try restoring to jf6 with odin and see where I get. Thanks for the reply
Click to expand...
Click to collapse
once in jf6 if your imei isn't corrected then delete everything but the nv_data.bin and .nv_data.bak.md5.
use android terminal emulator to execute following (must have busybox installed)
su
busybox chown 1001:1001 /efs/nv_data.bin
reboot
avgjoegeek said:
If your flashed back to stock OTA JH7? Shouldn't need to have to restore them.
Only need to input that (if Android ID doesn't work) - you should be able to copy it using ADB shell and SU.
cp /dir/foo /dir/newfoo
Click to expand...
Click to collapse
fyi android id is different than the device id. Device ID = IMEI.
I see my problem, the efs directory I have is from my OLD captivate. Arrrg....I have no backup of my current /efs. The random nv_data.bin it creates has the correct product code already.
There must be something in the phone that knows the imei as this is why it was not accepting my dropped in files (the files from my old phone).
Ah well...ill use it till ATT blocks the test IMEI "lose" mine and go get a refurb as I have insurance.
FYI, the stock original firmware does not create those .bak files from what I could see. I bet your files had jacked product IDs but perhaps the part that went with your IMEI was still intact. This would be why my phone wont accept my old phones nv_data.bin?
once your in stock
run the terminal emu commands you should have baks once your system reboots.
I can delete my baks
run the term commands reboot and they will generate again.
if you have both bin.md5 and bak.md5 delete the bin and run terminal commands.
bames said:
once your in stock
run the terminal emu commands you should have baks once your system reboots.
I can delete my baks
run the term commands reboot and they will generate again.
if you have both bin.md5 and bak.md5 delete the bin and run terminal commands.
Click to expand...
Click to collapse
None of those files get generated for me or exist. If I remove everything, a generic nv_data.bin and .imei get created. Thats it. If I copy over the files from my old captivate, I believe they do get created but since the IMEI in that file does not match whatever is being checked in the phone, new files are created anyways.
I suppose nobody as of now knows how to generate the string that is in the nv_data.bin based on an IMEI so it seems that I am out of luck.
Perhaps some shady place in town can help me repair the IMEI or something
I ended up calling Samsung today. I described the problem (damaged IMEI) and they sent me a pre-paid shipping label to send it off to Plano TX to have them take a look (i'm in Austin).
I will let you guys know how this turns out.
My phone is on its way back to me. They ended up swapping the mainboard under warranty.
I suppose if you have a damaged IMEI and can deal with using an old phone for a week, consider sending it over to samsung.
did you have to pay for new mainboard? cause i got the same problem but i am not the orginal owner for the phone.
Jeez, that's wild. What is the correct way to go about backing up the necessary information while the phone is still stock? Planning on rooting (but not unlocking) my gf's Captivate and want to make sure I leave a proper trail of breadcrumbs.
Phateless said:
Jeez, that's wild. What is the correct way to go about backing up the necessary information while the phone is still stock? Planning on rooting (but not unlocking) my gf's Captivate and want to make sure I leave a proper trail of breadcrumbs.
Click to expand...
Click to collapse
It was no cost. They could see based on the IMEI that it was still in warranty. My mistake is I forgot to make a backup of /efs. If you make a backup before doing the OTA update, the unlock code in in clear text
z28james said:
It was no cost. They could see based on the IMEI that it was still in warranty. My mistake is I forgot to make a backup of /efs. If you make a backup before doing the OTA update, the unlock code in in clear text
Click to expand...
Click to collapse
So just back up that efs folder and that's it? Anything else?
This phone was purchased used on Craigslist so I don't there's any warranty remaining. It's a 1007 so it's older...
Phateless said:
So just back up that efs folder and that's it? Anything else?
This phone was purchased used on Craigslist so I don't there's any warranty remaining. It's a 1007 so it's older...
Click to expand...
Click to collapse
Well, the warranty period is a year and so since its been less than a year since the captivates release, you should be good. It would seem the only way it would be out of warranty would be if samsung for some reason deemed it to be at some point. Im sure you could call samsung with the IMEI and verify.
In my case, my product ID had become damaged. My problem is although I had a backup of /efs, it was for my first captivate, not my current. I deleted /efs and moved the backup into place. Seeing that it was the nv_data.bin for some other phone with another IMEI (the IMEI is encrypted inside that file) it instead replaced the files with a generic set of files and the dreaded test IMEI.
Since nobody had a good way to write the IMEI to that file as it expects, I was SOL.
If I could do it again, I would make a .99 cent jig (I did this using a wonderful thread here labeled something like "make a jig without cutting up USB cable) which gets you into download mode if odin or something soft bricks your phone, root, make a backup of /efs and then take a nandroid backup. I THINK I remember reading that sgstools can backup /efs for you but in the sticky there is a method on how to make a .tar of /efs (good as this will retain permissions/ownership as if you straight copy them to the sd card with fat32, the filesystem does not understand linux permissions and blows them away).
Master-Clear did the trick 4 me
OP I had the same exact same problem here. I spent many hours looking for a fix, N/G, nothing I tried would work. Didn't want to go to AT&T so I took a big chance and went into the efs folder and started deleting files one at a time. When I was through the efs was empty, did this with Root Explorer. When I did a reboot I wound up with a different IMEI, had NO data connection, NO APN, but wifi worked fine. I then did a factory reset from CW which did nothing, still no data connection. More time down so I loaded up ODIN3 One-Click and did a Master Clear. This was the last thing I was going to try before a trip to your friendly AT&T store. Well low and behold after the Master Clear and a reboot everything is back to normal! My IMEI is correct, APN is back, 3G working, wifi working. TITS! What a rush!
TommyZee said:
OP I had the same exact same problem here. I spent many hours looking for a fix, N/G, nothing I tried would work. Didn't want to go to AT&T so I took a big chance and went into the efs folder and started deleting files one at a time. When I was through the efs was empty, did this with Root Explorer. When I did a reboot I wound up with a different IMEI, had NO data connection, NO APN, but wifi worked fine. I then did a factory reset from CW which did nothing, still no data connection. More time down so I loaded up ODIN3 One-Click and did a Master Clear. This was the last thing I was going to try before a trip to your friendly AT&T store. Well low and behold after the Master Clear and a reboot everything is back to normal! My IMEI is correct, APN is back, 3G working, wifi working. TITS! What a rush!
Click to expand...
Click to collapse
Do you know where I can find this ODIN3 one-click and how to do a master clear?
Hey folks. I'm having a hell of a time here - I noticed that after the (fresh) installation of cm7 and updating to the latest nightly, my imei changed to 004999010640000.
Now, I have two backups, and went ahead and copied nv_data.bin, from when I originally got the phone, to /efs and changed the permissions to 1001:1001. After a reboot, imei is still 004999010640000.
I went ahead and flashed back to JL2, at which point my iemi was showing correctly, so I flashed speedmod, flashed cm7-kernel, rebooted, installed the cm7 update, and now my iemi is back to 004999010640000.
It doesn't seem to have any negative effects, my phone works as it usually does, but it is driving me nuts why my iemi is buggered up under cm7, and why restoring the original doesn't fix it. Is this a cm7 issue?
TIA
CM7 copies the efs folder and reads it from somewhere else. That's why restoring it to original place didn't do anything. Don't know why it changed it.
Yeah I started poking around the initial flash zip and noticed that all efsbackup.sh does it copy the contents of /efs to /sdcard/backup/efs.
I figured that they were keeping /efs because of
Code:
/dev/block/mtdblock4 on /efs type yaffs2 (rw,relatime)
showing up when viewing mounts...
Still having the problem... im hoping someone here can offer up some suggestions.
Sent from my GT-I9000 using XDA App
EFS backup post somewhere on the forum its a topic thats been well covered.
Due to flashing wiping efs .
One post is .
http://forum.xda-developers.com/showthread.php?t=881162
jje
JJEgan said:
EFS backup post somewhere on the forum its a topic thats been well covered.
Due to flashing wiping efs .
One post is .
http://forum.xda-developers.com/showthread.php?t=881162
jje
Click to expand...
Click to collapse
Thanks for the link, but it doesn't relate to my problem. The edits to nv_data.bin in that thread relate to changing the product code back to a proper AT&T product code on the captivate. I have a BMC i9000m, and an original (and proper) nv_data.bin from my stock phone when purchased.
The issue is when I copy my proper nv_data.bin to /efs, set proper permissions and reboot, it reverts back to a buggered IEMI according to settings -> status in CM7. I'm looking to find how how exactly CM7 handles /efs, and if it is CM7 specifically that is overwriting my nv_data.bin or if something else is at work.
Ah, finally figured it out. After seeing what nv.log was saying and thanks to zacharias over on the cm forums for tipping me off that just restoring nv_data might not work without everything else in /efs. I transferred my efs backup from windows to my ubuntu vm, set the permissions and made a tarball. Transferred that to my device, extracted the tarball, rebooted and poof, it worked. As this was a complete /efs backup and not just nv_data.bin, I'm guessing there was another file that the phone needed, despite what some of the guides say.
I still wish I knew what caused the phone to reject the nv_data.bin (as per nv.log)... I did delete the nv_data.bin.md5 because I read elsewhere that the phone would simply rebuild a new hash on boot, but it obviously didn't work. I wonder if it had something to do with that.
Oh well, it works now... thanks everyone!
Hi All,
like many of the users I have a problem with missing /efs folder. Although I can't find it I have my IMEI and my phone (S5830) works fine. I can make and receive calls.
But let's start from the beginning. I had Android in 2.3.3 version.
Using this post http://forum.xda-developers.com/showthread.php?t=1034145 I have upgraded it to 2.3.6.
I have also rooted it using universal_gb_root_v25.zip.
Now I wanted to play with it a little more so I though of doing backup. Previously I made one using CWM but I read that it doesn't backup /efs folder that stores IMEI and other important data. So I started searching through the forum for a solution. I've downloaded EFS Professional but for some reason it gives me error "An error occured while getting partition list!" when I select my phone from the drop-down list on the backup tab. I cannot do backup because the "Device Partitions" window is empty.
I did not give up and searched the forum a little more. So I've downloaded two apps: ES File Explorer and Root Explorer. Unfortunately both could not locate /efs folder. All the Linux folders were there except /efs. There's dev and next is etc. No efs.
So I though that maybe the folder was hidden but the I checked the options of Root Explorer to show hidden files.
Lastly I checked the method with adb shell and busybox like below:
adb shell
su
tar zcvf /sdcard/efs-backup.tar.gz /efs
but as I though I got the message that /efs folder could not be found.
Has anyone have an idea how to get to /efs folder in my case? Where does my phone keep IMEI? How to backup (and restore) my phone in this scenario? Is there any other way to backup the most important files?
I know there are lot of questions but I'd appreciate helping me with it. Thanks in advance.
habit81 said:
Hi All,
like many of the users I have a problem with missing /efs folder. Although I can't find it I have my IMEI and my phone (S5830) works fine. I can make and receive calls.
But let's start from the beginning. I had Android in 2.3.3 version.
Using this post http://forum.xda-developers.com/showthread.php?t=1034145 I have upgraded it to 2.3.6.
I have also rooted it using universal_gb_root_v25.zip.
Now I wanted to play with it a little more so I though of doing backup. Previously I made one using CWM but I read that it doesn't backup /efs folder that stores IMEI and other important data. So I started searching through the forum for a solution. I've downloaded EFS Professional but for some reason it gives me error "An error occured while getting partition list!" when I select my phone from the drop-down list on the backup tab. I cannot do backup because the "Device Partitions" window is empty.
I did not give up and searched the forum a little more. So I've downloaded two apps: ES File Explorer and Root Explorer. Unfortunately both could not locate /efs folder. All the Linux folders were there except /efs. There's dev and next is etc. No efs.
So I though that maybe the folder was hidden but the I checked the options of Root Explorer to show hidden files.
Lastly I checked the method with adb shell and busybox like below:
adb shell
su
tar zcvf /sdcard/efs-backup.tar.gz /efs
but as I though I got the message that /efs folder could not be found.
Has anyone have an idea how to get to /efs folder in my case? Where does my phone keep IMEI? How to backup (and restore) my phone in this scenario? Is there any other way to backup the most important files?
I know there are lot of questions but I'd appreciate helping me with it. Thanks in advance.
Click to expand...
Click to collapse
its difficult to find the efs folder bt u can check ur IMEI number by this code *#06#.
you can backup efs files by efs professional tool.
a CWM backup is also safe as it includes most of important files.
hit thanx if helped.
its difficult to find the efs folder bt u can check ur IMEI number by this code *#06#.
Click to expand...
Click to collapse
I was clever enough to write down my IMEI before but this is not an issue. The phone works fine.
you can backup efs files by efs professional tool.
Click to expand...
Click to collapse
I already wrote that I'm getting an error "An error occured while getting partition list!" using EFS Pro
Anyone has other ideas?
habit81 said:
I was clever enough to write down my IMEI before but this is not an issue. The phone works fine.
I already wrote that I'm getting an error "An error occured while getting partition list!" using EFS Pro
Anyone has other ideas?
Click to expand...
Click to collapse
forum.xda-developers.com/showthread.php?t=1637249 may this thread help u
forum.xda-developers.com/showthread.php?t=1637249 may this thread help u
Click to expand...
Click to collapse
Thanks for the one above. From this post I read that SGA does not have /efs (folder/partition) or it is not mounted by default so I can't see it. Which one is the right answer? It does not exists or it is not mounted?
If doesn't exists then where should I look for IMEI data and all other critical stuff?
If it exists I could issue:
mount -r -t ext4 /dev/block/mmcblk0p3 /efs
-r not to make any changes. I would have to create /efs folder first using: adb shell mkdir /efs
Am I following the right path?
I'd have already tried that but don't want to screw up my phone. Thanks in advance for any suggestions.
habit81 said:
Thanks for the one above. From this post I read that SGA does not have /efs (folder/partition) or it is not mounted by default so I can't see it. Which one is the right answer? It does not exists or it is not mounted?
If doesn't exists then where should I look for IMEI data and all other critical stuff?
If it exists I could issue:
mount -r -t ext4 /dev/block/mmcblk0p3 /efs
-r not to make any changes. I would have to create /efs folder first using: adb shell mkdir /efs
Am I following the right path?
I'd have already tried that but don't want to screw up my phone. Thanks in advance for any suggestions.
Click to expand...
Click to collapse
I can suggest you
DON'T TOUCH/MOUNT ESF FOLDER AND DON'T TRY TO BACK UP IT EITHER,DOING IT = BRICK!!
I can suggest you
DON'T TOUCH/MOUNT ESF FOLDER AND DON'T TRY TO BACK UP IT EITHER,DOING IT = BRICK!!
Click to expand...
Click to collapse
Thanks for the suggestion however this doesn't bring any useful information to this topic. I already know to be very careful with EFS data.
I would like to get some answers about configuration of this data on SGA. I would like to know whether there is a way to back it up That's all
habit81 said:
Thanks for the suggestion however this doesn't bring any useful information to this topic. I already know to be very careful with EFS data.
I would like to get some answers about configuration of this data on SGA. I would like to know whether there is a way to back it up That's all
Click to expand...
Click to collapse
I think it's useful...anyway It's really simple, FORGET TO BACKUP YOUR EFS FOLDER OR YOU'LL BRICK YOUR PHONE!!
First... the question is why would you wanna backup your IMEI ? You needn't even write it down as a backup if you have the bill of your phone. And in case if you ever lost the IMEI, there is a guide to restore it & you can restore your older IMEI. So why worry to backup ?
Sent from my GT-S5830 using xda premium
I wrote the IMEI down just as a precaution. I didn't know it was on the bill as to be honest the phone used to belong to my wife. I know there are several threads about restoring IMEI and other necessary data. I have already viewed them.
The reason I put this thread was that I was unable to locate the famous efs folder. I'm new in this stuff but I'm also a quick learner. After going through several threads and articles I was curious why I could not locate efs folder on my SGA. Answers such as "don't look for it or you will damage your phone" are just simply not what I was looking for. Anyway if someone please explain me the technical details of this phone and the reason why I can't make a backup using several tools and methods I would be very grateful.
Your quest for the efs folder is unending. I appreciate your effort in learning new things but what's the point of finding something that's of no practical use ? Yeah, you can't find the efs folder & no one else has ever worried about it coz everyone knows how to get their phone back online when they lose their IMEI. So either backing it up or looking for it is not worth a penny . All that counts is that the phone works & that the IMEI is secured, be it without that folder of your interest. If you clearly state your intentions with what you have to do by backing it up, someone might be able to help.
Sent from my GT-S5830 using xda premium
Hi I am have just joined the forum searching for a help. It was my first time flashing custom roms and had been at fault in technically missing some of the instruction. I have failed to backup any bin, img or efs folder which could help me fix IMEI. using MTK droid tool (for MT6589), I am receiving an error of missing pttycmd1 and even searching the root of my phone, I can't find any nv_ram or efs. Is there any other way to fix my device?
Baseband: Unknown
No IMEI
cannot use AT+egmr command
thanks for the reply.
efs ?
efs is a partition for sim unlock right ?
i do hope so, because I just read from other threads about exploring and backup of efs can fix baseband & imei.
I can't find my efs either. The issue I'm having is to get rid of Factory Mode. Have seen tutorials on how to do it, but the efs file is missing and so I can't actually do it. Any suggestions on how to fix these issues? Thanks
I recently unlocked my bootloader using sunshine and installed TWRP. After rebooting into recovery, I immediately made a backup of my phone. When I plug my phone in, I can see the TWRP folder, but it shows as empty. None of my file explorers can see anything, either. TWRP, however, is able to see it when I go into the file manager. I can't get ADB to see the device when hooked up to my computer while in TWRP. MTP also doesn't work. Chmod 755 and 777 doesn't do anything. I was able to initially copy the TWRP folder into the downloads folder in the TWRP file manager, but now it just hangs there if I try to move it again.
How do I get access to my backup?
evanft said:
I recently unlocked my bootloader using sunshine and installed TWRP. After rebooting into recovery, I immediately made a backup of my phone. When I plug my phone in, I can see the TWRP folder, but it shows as empty. None of my file explorers can see anything, either. TWRP, however, is able to see it when I go into the file manager. I can't get ADB to see the device when hooked up to my computer while in TWRP. MTP also doesn't work.
How do I get access to my backup?
Click to expand...
Click to collapse
http://forum.xda-developers.com/droid-turbo/help/twrp-backup-file-location-t3259060
6Binford said:
http://forum.xda-developers.com/droid-turbo/help/twrp-backup-file-location-t3259060
Click to expand...
Click to collapse
Unfortunately, there aren't any solutions in that thread.
evanft said:
Unfortunately, there aren't any solutions in that thread.
Click to expand...
Click to collapse
There are two solutions in the first 4 posts:
ruledrbrt1 suggests http://forum.xda-developers.com/showpost.php?p=64048593&postcount=2
And GeoFX has the great : http://forum.xda-developers.com/showpost.php?p=64049328&postcount=5
Both work on my phone so they should work on yours too.
Have you given file explorer root privileges?
josephpalozzi said:
There are two solutions in the first 4 posts:
ruledrbrt1 suggests http://forum.xda-developers.com/showpost.php?p=64048593&postcount=2
And GeoFX has the great : http://forum.xda-developers.com/showpost.php?p=64049328&postcount=5
Both work on my phone so they should work on yours too.
Have you given file explorer root privileges?
Click to expand...
Click to collapse
I didn't even see GeoFX's post for some reason. That looks like it worked. Thanks!
TWRP and NAND Backups
I had the same question, and found the previous thread too. So what's the difference between these 2 locations?
/data/media/0/TWRP
and
/sdcard/TWRP
From my point of view, they are duplicates - same data in both folders, just duplicated into separate partitions. If this is true, then my 7.5 GB NAND backup, is really taking up 15GB of memory. Can that be true? I'm doubting it, but you never know.
I started to dive into this, because I was also wondering if NAND backups made copies of my media or not (photos, music, etc). After digging into it a bit, it looks like it does NOT make a backup of anything in the root folder "/data/media" in order to prevent it from non-stop backing up in a loop (you can't back up the location your backing up to, at the same time). This is also noted on github: https://github.com/TeamWin/Team-Win-Recovery-Project/issues/276 Logically, this would make sense since I currently have 25 GB of data in my /sdcard/ location. That's one helluva compression if you were able to get this down to 7.5GB! So I'm guessing this isn't included, which is also why I'm guessing that these are really the same. /sdcard/ must be a shortcut to the /data/media/0/ location, that's my best understanding.
So my original question still stands. What's the reason for these 2 locations, and is there a difference?
This also brings up the next question, what's the best way to make an all-encompassing backup? NAND + Titanium Backup + copy all the contents of your /sdcard/ over to your computer (or OTG drive)?
Florestan2 said:
I had the same question, and found the previous thread too. So what's the difference between these 2 locations?
/data/media/0/TWRP
and
/sdcard/TWRP
From my point of view, they are duplicates - same data in both folders, just duplicated into separate partitions. If this is true, then my 7.5 GB NAND backup, is really taking up 15GB of memory. Can that be true? I'm doubting it, but you never know.
I started to dive into this, because I was also wondering if NAND backups made copies of my media or not (photos, music, etc). After digging into it a bit, it looks like it does NOT make a backup of anything in the root folder "/data/media" in order to prevent it from non-stop backing up in a loop (you can't back up the location your backing up to, at the same time). This is also noted on github: https://github.com/TeamWin/Team-Win-Recovery-Project/issues/276 Logically, this would make sense since I currently have 25 GB of data in my /sdcard/ location. That's one helluva compression if you were able to get this down to 7.5GB! So I'm guessing this isn't included, which is also why I'm guessing that these are really the same. /sdcard/ must be a shortcut to the /data/media/0/ location, that's my best understanding.
So my original question still stands. What's the reason for these 2 locations, and is there a difference?
This also brings up the next question, what's the best way to make an all-encompassing backup? NAND + Titanium Backup + copy all the contents of your /sdcard/ over to your computer (or OTG drive)?
Click to expand...
Click to collapse
The way I understand it, and I might be wrong, is that before Android 4.0 (or maybe 5.0), the partition containing user data was called /sdcard and apps were stored in a separate partition. The partition where apps went was significantly smaller, which could result in people running out of space for apps while still having a ton of free user data. To remedy this, the newer version of android places apps and user data in the same partition (called media). The /sdcard that you see is a symlink (shortcut) to this new partition, and is included so that older apps that were designed to expect the /sdcard partition to be there will still work.