Develop Bugs

[Q] EFS Folder Rebuild

I did the Root66 stock Rom with root flash. I had Super User Pro installed with the OTA survival mode block ticked- then did the OTA update back in the day for the multiwindow. I of course lost root but didn't worry about it. 2 months later- my phone reset a bunch of times and wiped my MEID, IMEI, Baseband Version- etc.
I never did an efs backup before this because i didn't know too. Anyway- I have a Note 2 here now that will not connect to the cell towers at all but is seemingly in great condition. I used root explorer to copy my efs folder to my computer and i need to know what files are missing and what values i need to change to get my phone back to working. I think this would be usefull information to everyone that encounters this issue.
reference threads:
http://forum.xda-developers.com/showthread.php?t=1997150&page=5
http://forum.xda-developers.com/showthread.php?t=2143130
threads that fix this for other phones not ours:
http://forum.xda-developers.com/showthread.php?t=1968360
http://forum.xda-developers.com/showthread.php?t=859914
http://forum.xda-developers.com/showthread.php?t=1089039
we should have a thread that lists what files are supposed to be in our efs folder and where our important details are stored in those files- i.e.- what string to use a hex editor on to restore our values back to the phone.
Thanks everyone for your help.

dd807 said:
I did the Root66 stock Rom with root flash. I had Super User Pro installed with the OTA survival mode block ticked- then did the OTA update back in the day for the multiwindow. I of course lost root but didn't worry about it. 2 months later- my phone reset a bunch of times and wiped my MEID, IMEI, Baseband Version- etc.
I never did an efs backup before this because i didn't know too. Anyway- I have a Note 2 here now that will not connect to the cell towers at all but is seemingly in great condition. I used root explorer to copy my efs folder to my computer and i need to know what files are missing and what values i need to change to get my phone back to working. I think this would be usefull information to everyone that encounters this issue.
reference threads:
http://forum.xda-developers.com/showthread.php?t=1997150&page=5
http://forum.xda-developers.com/showthread.php?t=2143130
threads that fix this for other phones not ours:
http://forum.xda-developers.com/showthread.php?t=1968360
http://forum.xda-developers.com/showthread.php?t=859914
http://forum.xda-developers.com/showthread.php?t=1089039
we should have a thread that lists what files are supposed to be in our efs folder and where our important details are stored in those files- i.e.- what string to use a hex editor on to restore our values back to the phone.
Thanks everyone for your help.
Click to expand...
Click to collapse
bump- can't believe no one wants to help wih this.

I'll pull some files off my phone and send you copies of you want me to. I'm not a developer and can't help with what you're doing but will send you copies of stuff if that's all you need.

ohh I have the same problem
AndroidStephen said:
I'll pull some files off my phone and send you copies of you want me to. I'm not a developer and can't help with what you're doing but will send you copies of stuff if that's all you need.
Click to expand...
Click to collapse
I have the same problem my phone create a new efs folder but of course dont have imei no baseband and 0 storage
I have the N7105 , I have on my screen info pop telling me some specs ... we need help with another efs files if you can put a zip file we will appreciate ...... thank you

I wouldn't be giving anyone your intact efs partition. That contains all of your device specific information such as IMEI, ESN, MEID basically everything someone needs to clone your phone. And its not as simple as editing the files in efs and pushing them back to the device. You would need something like CDMA WS or equivalent to actually reprogram the values into the device. Most likely your information isn't missing it's just become hidden due to a corrupt partition. You can try doing a full repartition and restore with the lj1 firmware and then once the device boots ##786# and master reset, when it reboots after the master reset all of the missing values should be back. The repartition will un hide them and the master reset will allow the device to re read the efs and load the values properly. Once yoi get the values back the device will need to be reactivated and reprovisioned with your user info such and phone #, MIN, username and password, etc.
I like to break stuff!

-EViL-KoNCEPTz- said:
I wouldn't be giving anyone your intact efs partition. That contains all of your device specific information such as IMEI, ESN, MEID basically everything someone needs to clone your phone. And its not as simple as editing the files in efs and pushing them back to the device. You would need something like CDMA WS or equivalent to actually reprogram the values into the device. Most likely your information isn't missing it's just become hidden due to a corrupt partition. You can try doing a full repartition and restore with the lj1 firmware and then once the device boots ##786# and master reset, when it reboots after the master reset all of the missing values should be back. The repartition will un hide them and the master reset will allow the device to re read the efs and load the values properly. Once yoi get the values back the device will need to be reactivated and reprovisioned with your user info such and phone #, MIN, username and password, etc.
I like to break stuff!
Click to expand...
Click to collapse
Thanks for this reply- I already tried to flash back to stock with a Pit file and the and repartitioning checked in odin. didn't work. thats why i started this thread. ulitmately i think it was a hardware failure becuase it didn't happen when i was flashing the phone- is just happened when i was sitting on the couch watching tv. my phone reset a bunch of times in a row and then no signal. i finally got a new phone so i guess it doesn't matter.

Problem whit efs folder backup

I made a backup of efs folder with root explorer just cut and paste on your sd card. Now that I have corrupt files and generic imei and no network when I put the sd files from efs folder when i reboot the phone I find myself the same corrupted files. Is there a way to prevent the system to regenerate files inside the folder efs?

notedue9 said:
I made a backup of efs folder with root explorer just cut and paste on your sd card. Now that I have corrupt files and generic imei and no network when I put the sd files from efs folder when i reboot the phone I find myself the same corrupted files. Is there a way to prevent the system to regenerate files inside the folder efs?
Click to expand...
Click to collapse
No mate, if you've done a backup which isn't 100% then your knackered. You should always use a toolkit or efsbackup software

LBTaylor1984 said:
No mate, if you've done a backup which isn't 100% then your knackered. You should always use a toolkit or efsbackup software
Click to expand...
Click to collapse
what should I do? belonging to the assistance of course

notedue9 said:
what should I do? belonging to the assistance of course
Click to expand...
Click to collapse
As for as I know if your EFS data is lost or corrupt, and you cannot restore a backup version you are stuck. However something has come to mind, does the phone have a Modem listed in the menu where the IMEI is listed? I had a modem not flash right and gave the impression that the IMEI was lost, however upon reflashing the modem, the IMEI returned and the phone as 100% ok.

LBTaylor1984 said:
As for as I know if your EFS data is lost or corrupt, and you cannot restore a backup version you are stuck. However something has come to mind, does the phone have a Modem listed in the menu where the IMEI is listed? I had a modem not flash right and gave the impression that the IMEI was lost, however upon reflashing the modem, the IMEI returned and the phone as 100% ok.
Click to expand...
Click to collapse
I have generic imei 00049...

notedue9 said:
I have generic imei 00049...
Click to expand...
Click to collapse
Oh, tbh mate I know when I lost mine, I had to replace the EFS folder, then flash a ROM, factory reset, and it was ok, it's all i can suggest, someone more knowledgable then me might be able to help you a bit more.

notedue9 said:
I made a backup of efs folder with root explorer just cut and paste on your sd card. Now that I have corrupt files and generic imei and no network when I put the sd files from efs folder when i reboot the phone I find myself the same corrupted files. Is there a way to prevent the system to regenerate files inside the folder efs?
Click to expand...
Click to collapse
Flash stock Rom via odin, let's see if it's not that bad a problem
Sent from my Samsung Galaxy Note II GT-N7100 using Tapatalk HD

Elle233 said:
Flash stock Rom via odin, let's see if it's not that bad a problem
Sent from my Samsung Galaxy Note II GT-N7100 using Tapatalk HD
Click to expand...
Click to collapse
already done but no result

notedue9 said:
already done but no result
Click to expand...
Click to collapse
Send to Samsung service center
Sent from my Samsung Galaxy Note II GT-N7100 using Tapatalk HD

[Q] GT-N7105 network blocked , not available storage

my galaxy note 2 (GT-N7105) is no service and not available storage :crying: how can i fix it pls anyone help me
PS: this videos phone exactly sama as mine phone

ibizadesert said:
my galaxy note 2 (GT-N7105) is no service and not available storage :crying: how can i fix it pls anyone help me
PS: this videos phone exactly sama as mine phone
Click to expand...
Click to collapse
What did you. Havent looked at the vid so far, but it woud be nice to have a few more facts.
Did you tried to install a custom rom (modified Android-Software) or you are on the original Andrid Software? Since when you having the Probems?
No Service sounds like an EFS Problem, if you did a SW Change and it doesnt worked out well. Having no storage (if you mean ext. SD-Card) could be also a sign of a non proberly installation.

Same here maybe efs as you have imei unknown
Sent from my GT-N7105 using xda app-developers app

thedadio said:
Same here maybe efs as you have imei unknown
Sent from my GT-N7105 using xda app-developers app
Click to expand...
Click to collapse
Agreed, looks like a fried efs partition. And that usually happenes after trying to flash an OLD ROM aftetr flashing a new one. As the new ROM does something to the EFS partition(i am not a dev so have not clue what) that makes it screwed when you try to flash old ROMS.
I would try to flash a new ROM again and see what happenes. And do search for invalid IMEI Note 2 and you will find ALOT of help.

If you did flash a new ROM and having these issues then, take your efs.img (which you should have backup after rooting your device on the official Android Software -> also called Stock Rom) copy it on a SD-Card, insert that card to your Note 2 and copy it to the SDCard0 folder (the internal storage), then do the following:
- Start in Recovery Mode
- wipe cache
- factory reset
- format /system (under adv. settings -> Storage...then you see it)
- flash the Rom again
- wipe cache
- wipe Dalvik Cache (under adv. settngs in Recovery)
- Reboot
Now check your IMMEI and your Service. IMMEI should be ok now and Service available and running. At least your SD-Card should be mounted now and available. I believe you tried to flash from a 4.1/4.2 System to a 4.3 System and you didn`t wiped the Dalvik-Cache, which is the System tree of Android, which got changed with Android 4.3. I think something went wrong in your installation, so this "tree" mght be corrupted. Be sure that you also install the right GAPPS (Google Services for Android 4.3, such as Google Play Store). You can flash it as .zip also over Recovery-Mode, after you flashed the ROM (Software).
If you didn`t save your EFS on any proberly running System before, you might get hard times recovering it.

SunShiner said:
What did you. Havent looked at the vid so far, but it woud be nice to have a few more facts.
Did you tried to install a custom rom (modified Android-Software) or you are on the original Andrid Software? Since when you having the Probems?
No Service sounds like an EFS Problem, if you did a SW Change and it doesnt worked out well. Having no storage (if you mean ext. SD-Card) could be also a sign of a non proberly installation.
Click to expand...
Click to collapse
thanks for trying helping me dude my IMEI / baseband version is UNKNOWN that is problem :crying: how can i repair my imei back ?

SunShiner said:
If you did flash a new ROM and having these issues then, take your efs.img (which you should have backup after rooting your device on the official Android Software -> also called Stock Rom) copy it on a SD-Card, insert that card to your Note 2 and copy it to the SDCard0 folder (the internal storage), then do the following:
- Start in Recovery Mode
- wipe cache
- factory reset
- format /system (under adv. settings -> Storage...then you see it)
- flash the Rom again
- wipe cache
- wipe Dalvik Cache (under adv. settngs in Recovery)
- Reboot
Now check your IMMEI and your Service. IMMEI should be ok now and Service available and running. At least your SD-Card should be mounted now and available. I believe you tried to flash from a 4.1/4.2 System to a 4.3 System and you didn`t wiped the Dalvik-Cache, which is the System tree of Android, which got changed with Android 4.3. I think something went wrong in your installation, so this "tree" mght be corrupted. Be sure that you also install the right GAPPS (Google Services for Android 4.3, such as Google Play Store). You can flash it as .zip also over Recovery-Mode, after you flashed the ROM (Software).
If you didn`t save your EFS on any proberly running System before, you might get hard times recovering it.
Click to expand...
Click to collapse
my internal storage is not available and i tried to copied stock rom to my Sd-card but when i do step by step (factory data reset , wipe cache , wipe dalvik cache , fix permission) rom will not be installed

thedadio said:
Same here maybe efs as you have imei unknown
Sent from my GT-N7105 using xda app-developers app
Click to expand...
Click to collapse
my imei is unknown too. any ideas ? did you know fix that ?

Did you a backup of your EFS?..... that's what your IMMEI needs.
If not, try to download Stock ROM from a Source you know and maybe the immei will be rebuild. I don't know much about how to rebuild immei without EFS. Only thing I know is that there are not much ways. It's pretty difficult.
---------- Post added at 09:39 PM ---------- Previous post was at 09:32 PM ----------
Which ROM and Kernel you flashed?
BTW try to copy the files to thr phone without SDCard available thru a USB Cable to your PC. The phone should appear in the explorer list then.

SunShiner said:
Did you a backup of your EFS?..... that's what your IMMEI needs.
If not, try to download Stock ROM from a Source you know and maybe the immei will be rebuild. I don't know much about how to rebuild immei without EFS. Only thing I know is that there are not much ways. It's pretty difficult.
---------- Post added at 09:39 PM ---------- Previous post was at 09:32 PM ----------
Which ROM and Kernel you flashed?
BTW try to copy the files to thr phone without SDCard available thru a USB Cable to your PC. The phone should appear in the explorer list then.
Click to expand...
Click to collapse
i've flashed an old firmware and gone my imei. and now not available storage if i connect to PC storage is hidden.

ibizadesert said:
i've flashed an old firmware and gone my imei. and now not available storage if i connect to PC storage is hidden.
Click to expand...
Click to collapse
What you mean by old firmware? Like official firmware or modified (custom ROM)?

Maybe you have flashed an n7100 rom? I know the n7105 stored nv data in a different way to the n7100 so a standard efs backup using cwm or twrp will not suffice
Sent from my GT-N7105 using xda app-developers app

The 7105 posts in this forum are mixed with the posts for problems with the 7100 hence the title "Samsung Galaxy Note II GT-N7100 , N7105 " above
but the 7105 does have a different and way of storing data responsible for the correct operation of the IMEI and baseband along with other items
The backup programs provided by other members of the forums backup the efs partitions of the file system.... this is VITAL and allows user of the 7100 to restore their lost baseband and IMEI more easily than the on the 7105 Model.
It is possible to damage items in the NVram of the 7105 which can result in Baseband Unknown , IMEI unknown , lost of GPS functionality and also the loss of the internal storage file system making it appear as 0 bytes available which crashes applications as Android thinks there is no space on the emulated file system which presents its self as /storage/sdcard0 and other linked directories.
As a result of flashing the N7105 may users risk NVRAM corruption and may think they have a backup ... but they have no way of backing up the NVRAM only the EFS , as a result luck is the only thing between a phone with working IMEI , Baseband , GPS and internal storage becoming a tablet with WIFI only !!!!!
Their are some programs out on the net which claim to read and write the NVRAM such as QPST and NV-Reader Writer but Samsung use a modification to the
Qualcom message set which means that not all loacations are read and also writing the data back when a phone does have a corrupt NVRAM is a hit or miss affair.
the worst button on ODIN is the ERASE NVRAM button ..... if you have a 7105 model make sure you do NOT have this box ticked as it may not make you day a happy one !!!!
I would ask the Mods to separate the GT-N7105 posts into a separate forum as the 7100 and the 7105 share are lot but are different enough to make a big issue when people read posts on how to recover from
My BaseBand is UNKNOWN
My IMEI is UNKNOWN
My internal storage is 0Kb or doesnt mount properly as /Storage/sdcard0 ..../emulated/legacy etc
My GPS has stopped working
all of the above on the N7105 can point to a corruption of some data stored on the EMMC chip which we can call NVRAM within the device.
The 7100 is different as you have data in the /efs partition which MAY fix the problem
THE 7105 does NOT
As a result the 7105 at present has a good chance of taking a trip back to Samsung if you are unlucky enough to get a NVRAM problem...
Comments Please :

Am I right in thinking normal efs backups dont work with n7105?
Sent from my GT-N7105 using xda app-developers app

The normal EFS backups do contain what is in the EFS directory which is mounted BUT
BUT the 7105 carries addition data in the NVRAM and this is NOT repeat NOT backed up by
the backup programs or utilities in the forums.
As a result if you loose the IMEI and the Baseband you may be lucky and just damaged the efs directory and have a backup
BUT their is a good chance you may not get back to a working phone from and EFS backup as damaged NVRAM will not be fixed
by restoring an EFS backup
so if you have a GT-N7105 and you have 0kb of internal storage
or /and Baseband Unknown
or /and IMEI Unknown
or /and GPS not working
then you may be in a suitation which nobody on the forums has really got into that is full restore of N7105 NVRAM
from scratch.
As this contains the IMEI then nobody is going to post their own backup for you to use
and the NV reader Writer or QPST or the Pro Qualcom reader tools are old and have read errors in them
If anyone has performed a full backup of N7105 NVRAM then erased it ,,,, then restored from backup
please let us know as nobody appears to have proved to have tested a NVram backup and restore cycle.

[Q] About i9195 backup and restoring EFS

Hi all, I'm a new I9195GT owner (for a week already) and have been researching and having some satisfaction rooting and restoring all my apps with Titanium from my previous smartphone.
The phone works fine and I'm quite happy with it. I've already done a full backup with CWM recovery for any trouble I might come across in future but I don't know if a full backup from recovery contains all important and sensible data like EFS and NV data. Those two things are totally new for me as I'm coming from a HTC Desire which didn't require attention to those sensible points.
So I would be very grateful if anybody clears some doubts I have relating EFS and NV data:
- Does a full backup from recovery contain EFS and NV data, so in case that flashing a custom ROM results in corrupted EFS data, I would fix it just by restoring the full backup from recovery?
- What is the best and safest way for backup EFS and NV?
I've seen this post from arco68 which states a command I guess should be executed from Terminal directly in the smartphone, but I don't know how should that .img file restored to the phone in case it becomes corrupted.
I've also seen this post about the EFS Professional tool from lyriquidperfection but in the whole post I havent found anybody confirming it works in the S4 Mini i9195.... so it sounds good but I don't want to brick my new device being the first one to run the tool with the i9195
Thank you very much

As far as I know CWM does not back up EFS.
The good idea is to use TWRP recovery instead of CWM. TWRP does backup EFS.
You can get TWRP for 9195 here
http://forum.xda-developers.com/showthread.php?t=2449107

Thanks for the idea. I'm ready to install TWRP recovery but, before installing it and replacing CWM,
Is it possible to launch TWRP recovery from CWM recovery, as temporary? And when rebooting CWM is back.
I remember doing something like this in my previous device: from 4EXT recovery launching a CWM recovery for some particular reason I don't remember
Sent from my GT-I9195 using xda app-developers app

batareikin51 said:
As far as I know CWM does not back up EFS.
The good idea is to use TWRP recovery instead of CWM. TWRP does backup EFS.
You can get TWRP for 9195 here
http://forum.xda-developers.com/showthread.php?t=2449107
Click to expand...
Click to collapse
TWRP Recovery does not backup full EFS. IMEI is not included at least. Even though it lists a possibility of EFS backup, all it does is backups /efs partition. which does not contain IMEI in it. This concerns specifically I9195, which I own too and am researching this issue and also lost IMEI issue.

farewellartist said:
TWRP Recovery does not backup full EFS. IMEI is not included at least. Even though it lists a possibility of EFS backup, all it does is backups /efs partition. which does not contain IMEI in it.
Click to expand...
Click to collapse
I already had installed TWRP and made backups and nandroids....
So how can we safely backup IMEI in a way we can restore it in case it gets corrupted?

sergiosch said:
I already had installed TWRP and made backups and nandroids....
So how can we safely backup IMEI in a way we can restore it in case it gets corrupted?
Click to expand...
Click to collapse
Good question, I've been looking for answer for weeks.

sergiosch said:
I already had installed TWRP and made backups and nandroids....
So how can we safely backup IMEI in a way we can restore it in case it gets corrupted?
Click to expand...
Click to collapse
Guys!
The most simple method to backup our IMEI (efs folder) is:
1.Install rootexplorer
2.open it with superuser permission
3. Copy efs folder from root main folder to your sd card.
4.Upload from sd card to clouds to be sure you have a backup a different places.
5. Push thx for me

radicspeter said:
Guys!
The most simple method to backup our IMEI (efs folder) is:
1.Install rootexplorer
2.open it with superuser permission
3. Copy efs folder from root main folder to your sd card.
4.Upload from sd card to clouds to be sure you have a backup a different places.
5. Push thx for me
Click to expand...
Click to collapse
I did already that too, not with rootexplorer but TotalCommander which also has root access to any partition, I guess it performs the same backup just copying everything.
But then I don't know why it is valid to do "raw" directory/file copy with root explorer but it is not valid an EFS partition backup with TWRP recovery. I'm a newbie with this but, it seems the same to me....
Can anyone tell exactly in which file is stored imei? Isn't the same structure/process valid for other Galaxy brand smartphones so we can follow them?

radicspeter said:
Guys!
The most simple method to backup our IMEI (efs folder) is:
1.Install rootexplorer
2.open it with superuser permission
3. Copy efs folder from root main folder to your sd card.
4.Upload from sd card to clouds to be sure you have a backup a different places.
5. Push thx for me
Click to expand...
Click to collapse
I repeat, EFS FOLDER / PARTITION even on a raw byte level DOESN'T CONTAIN phones IMEI. This concerns specifically Samsung Galaxy S4 Mini LTE (I9195).
---------- Post added at 03:45 PM ---------- Previous post was at 03:31 PM ----------
sergiosch said:
I did already that too, not with rootexplorer but TotalCommander which also has root access to any partition, I guess it performs the same backup just copying everything.
But then I don't know why it is valid to do "raw" directory/file copy with root explorer but it is not valid an EFS partition backup with TWRP recovery. I'm a newbie with this but, it seems the same to me....
Can anyone tell exactly in which file is stored imei? Isn't the same structure/process valid for other Galaxy brand smartphones so we can follow them?
Click to expand...
Click to collapse
Normally, phones IMEI in previous galaxy devices (don't know about current S4, I own S4 Mini LTE), was stored in nv_data.bin file which was located in /efs folder on root. (which is a mount point for mmcblk0p10 partition in S4 Mini LTE). But, in this device, there is no nv_data bin file and IMEI is not stored nowhere close to efs partition. Not too many people own S4 Mini's and almost everybody whom I asked an information based their knowdledge on another devices and were feeding me false information I heard over and over again.
To clarify something, I know, that EFS partition doesn't contain IMEI, because:
No file in efs mount point contains IMEI.
No IMEI found checking EFS Professional backup (tar) on HEX level using various search methods. Even through-looked it, file is not that big.
No IMEI found through-looking .raw backup made using cygwin (which contains every single byte of partition, even though it is not a part of a file), which is 95+% warrant, that IMEI is not in EFS partition.

farewellartist said:
I repeat, EFS FOLDER / PARTITION even on a raw byte level DOESN'T CONTAIN phones IMEI. This concerns specifically Samsung Galaxy S4 Mini LTE (I9195).
---------- Post added at 03:45 PM ---------- Previous post was at 03:31 PM ----------
Normally, phones IMEI in previous galaxy devices (don't know about current S4, I own S4 Mini LTE), was stored in nv_data.bin file which was located in /efs folder on root. (which is a mount point for mmcblk0p10 partition in S4 Mini LTE). But, in this device, there is no nv_data bin file and IMEI is not stored nowhere close to efs partition. Not too many people own S4 Mini's and almost everybody whom I asked an information based their knowdledge on another devices and were feeding me false information I heard over and over again.
To clarify something, I know, that EFS partition doesn't contain IMEI, because:
No file in efs mount point contains IMEI.
No IMEI found checking EFS Professional backup (tar) on HEX level using various search methods. Even through-looked it, file is not that big.
No IMEI found through-looking .raw backup made using cygwin (which contains every single byte of partition, even though it is not a part of a file), which is 95+% warrant, that IMEI is not in EFS partition.
Click to expand...
Click to collapse
Thanks mate. Pretty clear :good:
I was also not confident about some tutorials I read in other forums claiming that just doing a copy of file structure from /EFS folder would backup our IMEI. Your explanation is appreciated.
Hope to find some way to effectively backup sensitive data as IMEI is....

sergiosch said:
Thanks mate. Pretty clear :good:
I was also not confident about some tutorials I read in other forums claiming that just doing a copy of file structure from /EFS folder would backup our IMEI. Your explanation is appreciated.
Hope to find some way to effectively backup sensitive data as IMEI is....
Click to expand...
Click to collapse
Found it! Making guide right now. Basically IMEI is contained in both mmcblk0p11 and mmcblk0p12 partitions. Samsung apparently has developed a new error-safe phone nv data preservation system, I'll explain in details in tutorial.

farewellartist said:
Found it! Making guide right now. Basically IMEI is contained in both mmcblk0p11 and mmcblk0p12 partitions. Samsung apparently has developed a new error-safe phone nv data preservation system, I'll explain in details in tutorial.
Click to expand...
Click to collapse
Great news! looking forward to read that guide :good::good:

sergiosch said:
Great news! looking forward to read that guide :good::good:
Click to expand...
Click to collapse
How do you mount those partitions? I've tried with no success. All I get is "mount: No such device".

deliog said:
How do you mount those partitions? I've tried with no success. All I get is "mount: No such device".
Click to expand...
Click to collapse
Don't mount, just backup.
Through terminal emulator, enter commands
su
dd if=/dev/block/mmcblk0p11 of=/dev/block/mmcblk0p12

And how to restore later if IMEI gets corrupted/null?
Sent from my GT-I9195 using xda app-developers app

sergiosch said:
And how to restore later if IMEI gets corrupted/null?
Sent from my GT-I9195 using xda app-developers app
Click to expand...
Click to collapse
See this: http://forum.xda-developers.com/showthread.php?t=2569532

sergiosch said:
Great news! looking forward to read that guide :good::good:
Click to expand...
Click to collapse
Could you (or someone) PLEASE post or send PM with backups of partition mmcblk0p11 and mmcblk0p12? While researching this issue, I trashed 2 OF MY PHONES and nulled my IMEIs because of delusion caused by memory of having a backup, which I didn't. It's a pity to give away such a fortune for spares. I need NV blocks to hex compare them with blocks I got from another healthy I9195. Since IMEI numbers of different phone blocks will be different, difference will show on hex level too, which will help me determine exact address of IMEI location, after which I could modify my trashed NV blocks at determined memory address with my original IMEI, which could save me from watching at useless brick. And also would help me at development of I9195 IMEI Restore tool.
Disclaimer: I am not modifying my IMEI nor doing any actions which end-target is modification of original IMEI and differing it from original one. I am modifying nulled (trashed, unoriginal) IMEI to its ORIGINAL state which ultimately couldn't be called nothing else but RESTORING. I won't use IMEI from gathered NV blocks. I just need a another healthy block to fix my issue and help develop tools so others could be able to sleep at nights without issue that causes me sleepless nights.

farewellartist said:
Could you (or someone) PLEASE post or send PM with backups of partition mmcblk0p11 and mmcblk0p12? While researching this issue, I trashed 2 OF MY PHONES and nulled my IMEIs because of delusion caused by memory of having a backup, which I didn't. It's a pity to give away such a fortune for spares. I need NV blocks to hex compare them with blocks I got from another healthy I9195. Since IMEI numbers of different phone blocks will be different, difference will show on hex level too, which will help me determine exact address of IMEI location, after which I could modify my trashed NV blocks at determined memory address with my original IMEI, which could save me from watching at useless brick. And also would help me at development of I9195 IMEI Restore tool.
Disclaimer: I am not modifying my IMEI nor doing any actions which end-target is modification of original IMEI and differing it from original one. I am modifying nulled (trashed, unoriginal) IMEI to its ORIGINAL state which ultimately couldn't be called nothing else but RESTORING. I won't use IMEI from gathered NV blocks. I just need a another healthy block to fix my issue and help develop tools so others could be able to sleep at nights without issue that causes me sleepless nights.
Click to expand...
Click to collapse
I haven't done yet any of the backup processes you explain, so I don't even have the files you're asking for, but with all the gratitude and admiration I feel for the developers I wouldn't feel any confortable sending sensible data from part of a nandroid backup.... speaking just for myself of course, if I could choose how to help a developer I would preferr doing a donation to help him recover the hardware he has broken to help others. Some months ago I heard a friend telling that he had been scammed with a phone he bought in some cash converter and only worked for one day, then it became with null IMEI, and he suspected someone had "stolen" or "shutdown" his IMEI for unknown reasons...
sorry to say that, maybe I'm an ignorant but I just don't feel confortable with what you are asking directly to me

[Q] Default IMEI after Kies software upgrade

So I found myself wondering how can I make life difficult for myself... I did a software upgrade in Kies on my T805 and now I have a default IMEI...
I was on cm11 before doing the upgrade to 5.0.2
Has this happened to anyone or does anyone have any idea how to fix it?
Many thanks for any reply.

That shouldnt have happened but youre not the first person to state that cm has messed with the partitions. Id stick with stock based roms in future.
Download EFS professional then under the samsung tools tab select other tools then 'Repair NV data from internal file backup'
If youre lucky it will be restored.
Now some friendly advice, ALWAYS make a full backup via recovery before messing with anything custom on your device, especially make sure the EFS partition is backed up.

ashyx said:
That shouldnt have happened but youre not the first person to state that cm has messed with the partitions. Id stick with stock based roms in future.
Download EFS professional then under the samsung tools tab select other tools then 'Repair NV data from internal file backup'
If youre lucky it will be restored.
Now some friendly advice, ALWAYS make a full backup via recovery before messing with anything custom on your device, especially make sure the EFS partition is backed up.
Click to expand...
Click to collapse
Thanks for the reply, sadly it restore a different default IMEI ending in /01 instead of /17.
I was 100% sure I had backed-up my efs, turns out I did but on my phone x(.
Any other suggestions?

Try this. Make a backup in recovery of the efs partition.
Boot into android then using a root file explorer open the efs folder then delete nv_data.bin and nv_data.bin.md5 then reboot.
See if this replaces the deleted files with the backup.

ashyx said:
Try this. Make a backup in recovery of the efs partition.
Boot into android then using a root file explorer open the efs folder then delete nv_data.bin and nv_data.bin.md5 then reboot.
See if this replaces the deleted files with the backup.
Click to expand...
Click to collapse
It does but not with the correct imei. Thanks for the reply!

What IMEI does it give?

ashyx said:
What IMEI does it give?
Click to expand...
Click to collapse
A default imei ending in / 17 instead of / 01

DieZz said:
A default imei ending in / 17 instead of / 01
Click to expand...
Click to collapse
You may as well post it as its not a valid imei, it's a generic imei.
Is it 004999010640000?