Hello
I have a Samsung Galaxy S with SlimBean Installed, previously I had the stock 2.3.3 XEF version and CM9
When I rooted the device for first time the first thing I did ws backing up the EFS partition, I have made subsequent backups since then. However, the files don't seem to be equal and don't match the .MD5 signatures provided.
Do the files in this partition change over time? Does that mean they are getting corrupted? The most logical thing would be that the signatures matched the files but they don't..
Thank you.
Hello
Any ideas of why this happens and if it's normal?
Thank you.
And I've just checked my phone, the .bak files have dissapeared.
I've got an old backup tho, but why did they dissapeared?
Thanks.
Edit: The rest of the files are in the efs folder, they weren't displayed because Slim filemanager doesn't show hidden files by default.
So the only question remaining is: Do you know why the MD5 signatures don't match the files?
Thank you.
I think since IMEI is unchanged - thats ok. The most important file you have to keep is nv_data.bin (i think that one) it holds your IMEI. So as long as your phone works - no panic.
Sent from my GT-I9000 using xda app-developers app
Hello
Thanks. But why does the hash change and differs from it's MD5 signature?
Probably so.. dont worry about it and keep nv_data.bin just in case.
Sent from my GT-I9000 using xda app-developers app
When you flash back to Stock 2.3.6 with or without Root it will Fix EFS for you ..just to let you know
Related
Thanks to the good folks here i've just upgraded my Galaxy S to the leaked JPM firmware. So far so good - much faster than JPK I was on.
However - I'm having problems with the Appbrain Fast Web Installer and seem to have found out that it's due to the android device ID being the same because we're all using the same ROM (or something) (http://ip208-100-42-21.static.xda-developers.com/showthread.php?t=798644)
So.... How can I find out what my Device ID was/should be and how can I then change it to be "correct".
Any help much appreciated. Seems it might be a common issue....
Have you tried checking whether your IMEI changed after flashing? Type *#06# and if your IMEI starts with 0049... (I think...) then you need to do what almost everyone has been doing since JPC ... follow the instructions from here or some other threads from around here.
If your IMEI is fine, then I have no idea...
nonreviad said:
Have you tried checking whether your IMEI changed after flashing? Type *#06# and if your IMEI starts with 0049... (I think...) then you need to do what almost everyone has been doing since JPC ... follow the instructions from here or some other threads from around here.
If your IMEI is fine, then I have no idea...
Click to expand...
Click to collapse
Thanks for info - checked my IMEI and it seems to be fine - i.e. the one i registered with my insurance with (starts 3547)
I've read the thread you linked to trying to figure out what's what but I can't see anywhere how to find out what my product code is/was/should be or how I can change it. I've seen stuff about backing stuff up (nv_data?) but I'm not aware of having changed these.
All I've done to my phone - flashed JMX and now JPM and applied SuperOneClickv1.4-ShortFuse root. Will that have changed my product code?
I'm a bit lost with this one.
Use sgs toolbox to see the crc code.
Sometimes you got the right code in the backup file.
Just do a backup of all file on a safe place. The remove the 2 original file. Restart.
You need to be rooted for this.
Sent from my GT-I9000 using XDA App
DamianGto said:
Use sgs toolbox to see the crc code.
Sometimes you got the right code in the backup file.
Just do a backup of all file on a safe place. The remove the 2 original file. Restart.
You need to be rooted for this.
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
A bit of info that might help(?):
I loaded up SGS toolbox and pressed ""check product code" it says:
---------------------
Got root access
Copied nv_data files...
nv_data.bin could not be read!
No backup .nv_data.bak found!
-----------------------------------------
I'm guessing that's bad news?!
Under Firmware Info it says:
------------------------------
PDA: I9000XXJPM
PHONE: I9000XXJPM
CSC: I9000OXAJPM
Build Info: 2010. 10
--------------------------------------
When I tap CSC selection it says: "USSD code running" and then "UNKNOWN APPLICATION"
When you say to backup 2 original files - i'm guessing it looks like I don't have those. Is there another way I can check or is it definite from the above. If I don't have the original files am I stuck? Can I get them from anywhere else? Are they default to a phone by region or carrier (my phone is from O2 in the UK and is the 8gb version)
If you say delete the original files (which aren't there it seems) - am I right in thinking this will them make the phone auto-generate new ones? (I really have no idea what these files are for or what they do).
What's the next thing to try? Can I get hold of the missing files from somewhere? Do I even need them? And how do I restore the Product ID (if it's changed!)?
Thanks
Have you checked the path manually for them?
If they are not there you are in deep water.
Its you personal data for the phone and you can't use others file.
Search this forum for help about this.
I can only give you a advice what i would do if i had that problem.
I would flash a original firmware that is lower than its on kies.
Then i would upgrade thought kies.
Then i would check if the crc code is there and right.
If it still wrong then i guess i would make the phone look like it was out of the box and return it.
If the code is right i would make a backup(full) and on this files( to my external sdcard).
Then i would upgrade to jpm/jp6.
Sent from my GT-I9000 using XDA App
DamianGto said:
Have you checked the path manually for them?
If they are not there you are in deep water.
Its you personal data for the phone and you can't use others file.
Search this forum for help about this.
I can only give you a advice what i would do if i had that problem.
I would flash a original firmware that is lower than its on kies.
Then i would upgrade thought kies.
Then i would check if the crc code is there and right.
If it still wrong then i guess i would make the phone look like it was out of the box and return it.
If the code is right i would make a backup(full) and on this files( to my external sdcard).
Then i would upgrade to jpm/jp6.
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
Hi - thanks for reply
I've checked the /efs folder with Root Explorer and it seems i've got:
.android - folder
.nv2.bak
.nv2.bak.md5
.nv_data.bak
.nv_data.bak.md5
.nv_state
/imei - folder
nv_data.bin
nv_data.bin.md5
Now i'm guessing this is good? is it all in the right folder?
Just to clarify - I've never messed with this folder - I've only ever flashed with Kies and cleared the cache and restored factory settings with recovery. I've also formatted internal and external memory card.
So are these files my original files? How can I tell? Are these included with the Rom's I've flashed? (JPK and now JPM)
I've copied the entire efs folder to a safe place - is there anything else I should backup also incase I can't restore it?
SGS toolbox still says:
---------------------
Got root access
Copied nv_data files...
nv_data.bin could not be read!
No backup .nv_data.bak found!
-----------------------------------------
Why can't SGS toolbox read the files?
Many Thanks
Maybe I am not following this thread correctly, but your last post deals with IMEI and unlock data. Your first post said you needed to change your deviceID. You even link to the Captivate thread that discusses the problem AND in that captivate thread is a link to change Device ID - http://forum.xda-developers.com/showpost.php?p=8604909&postcount=3550
review that post as it tells you where your device ID is located (it is not in the nv_data.bin file). Also, in the captivate thread, one person said he just made one up and that worked for him.
If you mess up with nv_data.bin you will mess up your IMEI and any unlock the phone has - so I caution you be careful.
I made a thread with the solution
http://forum.xda-developers.com/showthread.php?t=815503
This should work.
alsheron said:
Hi - thanks for reply
I've checked the /efs folder with Root Explorer and it seems i've got:
.android - folder
.nv2.bak
.nv2.bak.md5
.nv_data.bak
.nv_data.bak.md5
.nv_state
/imei - folder
nv_data.bin
nv_data.bin.md5
Now i'm guessing this is good? is it all in the right folder?
Just to clarify - I've never messed with this folder - I've only ever flashed with Kies and cleared the cache and restored factory settings with recovery. I've also formatted internal and external memory card.
So are these files my original files? How can I tell? Are these included with the Rom's I've flashed? (JPK and now JPM)
I've copied the entire efs folder to a safe place - is there anything else I should backup also incase I can't restore it?
SGS toolbox still says:
---------------------
Got root access
Copied nv_data files...
nv_data.bin could not be read!
No backup .nv_data.bak found!
-----------------------------------------
Why can't SGS toolbox read the files?
Many Thanks
Click to expand...
Click to collapse
I had the same problem.
I installed Busybox from the App Market and it solved the problem.
abumuqaatil said:
I had the same problem.
I installed Busybox from the App Market and it solved the problem.
Click to expand...
Click to collapse
thanks...had same problem and that solved it
I have flashed darky's no wipe and was using Axura before
Axura never changed my product code or IMEI
However darky's has changed my product code but not the IMEI
I have a proper backup created with SGS Toolbox but how do I restore it? I have root explorer so should I use that to overwrite the folder with the backup?
I only have my phone at the moment so restoring the backup from SD with the phone is what I'm looking for.
Thanks,
Brian
Sent from my GT-I9000 using XDA App
B-Naughty said:
I have flashed darky's no wipe and was using Axura before
Axura never changed my product code or IMEI
However darky's has changed my product code but not the IMEI
I have a proper backup created with SGS Toolbox but how do I restore it? I have root explorer so should I use that to overwrite the folder with the backup?
I only have my phone at the moment so restoring the backup from SD with the phone is what I'm looking for.
Thanks,
Brian
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
Just replace the nv_data.bin and nv_data.bin.md5 back to your /efs folder. leave the .bak files alone if they are dated from august. those are the originals, these can be used to restore your .bin and .bin.md5 files.
if you have root explorer I would honestly copy that whole EFS folder to your SD card and maybe to a backup on the computer.
Nah no Aug files... Some nov files though... And i got this phone after the files' date so i suppose those may be it? Im guess having a proper product code and imei is all that matters correct?
Thanks and merry xmas
Sent from my GT-I9000 using XDA App
Ok.. So ive tried replacing the files with my backup and the product code stays the same... However when i tun a product check it says the backup has the correct product code... So i go to my earliest product code check folder and rename the files and paste them into the efs folder then reboot... Am i doing something wrong? I have the correct imei and things are working so should i just get a computer handy and follow the steps to restore everything?
Sent from my GT-I9000 using XDA App
useless
Sent from my SAMSUNG-SGH-I897 using XDA App
how can i fix a note without imei? tuts?
Restore an efs backup if had ever made one or contact cvxcvx.pl
nokiamodeln91 said:
Restore an efs backup if had ever made one or contact cvxcvx.pl
Click to expand...
Click to collapse
i don't have an efs backup...i most contact cvxcvx.pl?
is this a user?
yes user as well as http://www.cvxcvx.pl/?lang=en
he restores IMEI.. may be he can help you.
He can do this when you can show and prove that you have and own the original imei number. He can't "invent" one.
So you should check this first.
ThaiDai said:
He can do this when you can show and prove that you have and own the original imei number. He can't "invent" one.
So you should check this first.
Click to expand...
Click to collapse
Yup
he restores IMEI.. > doesnot mean generates
may be he can help you. > doesnot mean he will
ok i understand..but he want's money ) i'm from romania it's hard to pay , i don;t have credit card..
it isn't any free tut how to restore the imei.. ?! .. i will be greatefull!
Georgebucataru said:
ok i understand..but he want's money ) i'm from romania it's hard to pay , i don;t have credit card..
it isn't any free tut how to restore the imei.. ?! .. i will be greatefull!
Click to expand...
Click to collapse
No, because using hardware equipment is part of the repair process.
Until now I do not know a "software" restore mechanism (if you do not have a working backup of your old efs).
And I read and checked a lot of threads about this because I have a device where the IMEI is written in letters inside the device but not anymore in the efs - I have the so-called developer IMEI.
You should fist explore your note with root explorer. Depending on the rom you're using, you may have a backup of your efs partition (some rom do it automaticaly).
Watch your SD card if ther is a file called "efs.img"
You can also look inside the efs partition if there are files called .nv_data.bak and another one called .nv_data.bak.md5
If yes, you can fix it yourself.
I have a device where the IMEI is written in letters inside the device but not anymore in the efs - I have the so-called developer IMEI.
Click to expand...
Click to collapse
Oh!!Note? may be thats why you got the LSC update. Good
nokiamodeln91 said:
Oh!!Note? may be thats why you got the LSC update. Good
Click to expand...
Click to collapse
Pssst, do not tell anybody. But I guess that developer door is closed now, since November nothing (I check for OTA updates every day - I can do the install XXLSA/restore GB backup process while deep sleeping now).
i have found in the efs folder from internal memory the files! what now?
take a look!
Sent from my GT-N7000 using xda app-developers app
http://forum.xda-developers.com/showthread.php?t=1264021 i use that steps because i have foun an efs folder..but i didn't found ".nv_data " i copied a .nv_data.bak and rename it , that file with 2mg .. and i do the procedure..and i see a difeerence.. befor to do the procedore all was unknown ..now it's something else ..i'll post some screenshots!
now it'r rwiten that...the picture are after the procedure... sorry for my bad english
Sent from my GT-N7000 using xda app-developers app
Rename nv_data.bin to nv_data.bak
Rename nv_data.bin.md5 to nv_data.bin.md5.bak
Then:
Rename .nv_data.bak to nv_data.bin (remove the point at the begining)
Rename .nv_data.bak.md5 to nv_data.bin.md5 (remove the point as well)
Restart your phone and let us know.
ok ,i will copy those files from my backup efs folder in the interlan folder efs..rename it and i will process something in terminal?! or i will just reboot the phone?
Sent from my GT-N7000 using xda app-developers app
well you are stubborn, stubborness is annoying but can lead to great inventions and progress. However to save you time shiuld you fail, you will not without an efs backup be able to fix this. Imei gone is gone, no efs backup then need Samsung or cvxcvx.
Georgebucataru said:
ok ,i will copy those files from my backup efs folder in the interlan folder efs..rename it and i will process something in terminal?! or i will just reboot the phone?
Sent from my GT-N7000 using xda app-developers app
Click to expand...
Click to collapse
All can be done with root explorer. Just long press the file to rename and then chose "rename" and edit the name.
Files don't have to be moved, everithing needed is inside the efs folder.
After renaming those files, just reboot the phone.
so i delete the efs folder from internal memory and i did what you said to me and nothing take a look at the pictures
Sent from my GT-N7000 using xda app-developers app
Georgebucataru said:
so i delete the efs folder from internal memory and i did what you said to me and nothing take a look at the pictures
Sent from my GT-N7000 using xda app-developers app
Click to expand...
Click to collapse
where are the files from post # 12 ?
I never told you to delete anything but only to rename four files.
Know your stuck and only samsung repair center can help you sorry about that.
EDIT: By ECS i meant EFS (don't know how to edit the title)
Hey guys, first time posting in the galaxy tab forums.
Gonna try be as specific and brief as i can:
Sister has a P1000 with stock gingerbread.
I updated it to CM9 like this: rooted it -> installed CWM -> used root explorer to backup ecs folder -> downloaded CM9 from official CM page -> install as zip file.
First thing i noticed is that i have no IMEI and the radio is not working. I googled a bit, downloaded a radio, installed and now it works, i have network. However, i also have the infamous 004999XX IMEI which is giving me some problems in some apps.
I googled and tried lot's of things i found here on xda and some other forums.. Nothing worked.
First thing i did:
Deleted everything in ecs folder
Copied everything from the backup folder to ecs
Made sure nv_data.bin had radio as owner
Reboot
Didn't work
Next:
Deleted only the bin and md5 files
Copied .nv_data.bak from backup to ecs folder and rename ir properly
chown to radio
Reboot
Same thing
I also tried other variations, none worked.
Funny thing is that in the backup folder, the md5 hashes stored in the md5 files are not the same as the real hashes of the bin files, is this normal?
For example: in .nv_data.bak.md5 the hash stored is 2a3e2340b5f66adb17f2d1e9d95ceca5 but the real hash of the .nv_data.bak is f8638a35a8cd952ecff2a97f60b24b4d. Same goes for the nv_data.bin file
Other thing i noticed, if i upload the nv_data.bin file to ecs and reboot the device for it to create the md5 file, the system modifies it, it gets a different hash.. is this normal?
I am doing all this in ICS of course, i read it's preferred to do it in the stock rom, but i want it working with this one.. What am i missing?
Sometimes, what you want isn't going to work.
Just restock, it took 3 minutes to do ( download time is another)
Follow my signature, use overcome method. Read the from page 7 of the pdf.
Sent from my GT-N7100 using xda app-developers app
priyana said:
Sometimes, what you want isn't going to work.
Just restock, it took 3 minutes to do ( download time is another)
Follow my signature, use overcome method. Read the from page 7 of the pdf.
Sent from my GT-N7100 using xda app-developers app
Click to expand...
Click to collapse
Thank you.. my IMEI is back, even on ICS now..
I'm guessing it didn't work the first time because i went from stock gingerbread to ICS without any preparations.
Again, thank you so much.
Hi guys,
Yesterday I updated my cyanogenmod 11 with newest version doing a wipe cache first. After rebooting my phone seems to have an issue: the IMEI is null and I can't call or receive calls.
So I decided to flash the stock rom with odin, I thought that this could help, but nothing to do, the IMEI is still null and I can't use the phone
The first time I installed cyanogen I made a backup (using TWRP function), looking for that backup files, I discovered a file called efs.ext4.win, but if I try to open it with an unrar program, I see these files inside:
\.files
\bluetooth
\FactoryApp
\imei
\RFHAL
\RFHAL.DEF
\wifi
GUARDFIL
gyro_cal_data
pre_recovery.log
I don't see any "nv_data.bin" file or something like that. Is that normal?
Anyway, I think that EFS folder is corrupt or missing, i don't know. Is there a way to solve this issue? Thank you.
MaterialX said:
Hi guys,
Yesterday I updated my cyanogenmod 11 with newest version doing a wipe cache first. After rebooting my phone seems to have an issue: the IMEI is null and I can't call or receive calls.
So I decided to flash the stock rom with odin, I thought that this could help, but nothing to do, the IMEI is still null and I can't use the phone
The first time I installed cyanogen I made a backup (using TWRP function), looking for that backup files, I discovered a file called efs.ext4.win, but if I try to open it with an unrar program, I see these files inside:
\.files
\bluetooth
\FactoryApp
\imei
\RFHAL
\RFHAL.DEF
\wifi
GUARDFIL
gyro_cal_data
pre_recovery.log
I don't see any "nv_data.bin" file or something like that. Is that normal?
Anyway, I think that EFS folder is corrupt or missing, i don't know. Is there a way to solve this issue? Thank you.
Click to expand...
Click to collapse
S3 mini has no nv_data.bin file in EFS folder. You made already a backup of your efs, try to restore it with TWRP to get your IMEI back
Sent from my GT-I9301I using XDA Free mobile app
xXPR0T0TYPEXx said:
S3 mini has no nv_data.bin file in EFS folder. You made already a backup of your efs, try to restore it with TWRP to get your IMEI back
Sent from my GT-I9301I using XDA Free mobile app
Click to expand...
Click to collapse
Thanks for replying.
I tried to restore EFS folder using TWRP and my backup, but nothing changed, I still don't have Imei and baseband.
Do you think that flashing a PIT file could help me?
Thank you so much.