Can someone provide me with "nv_data.bin" file? - T-Mobile Samsung Galaxy S 4

I'm not a tech. So if i wrote something wrong, care to correct.
I lost me IMEI of S4(T-Mobile)- It just shows "/06" after dialing *#06#.
So i was just wondering (after checking the "NAND erase" in odin and accidentally deleting my efs folder) if any how i can get the "nv_data.bin" file.
I know most people might be thinking, "Why to give away my own IMEI data to some random stranger.".
Just for a fix, and wandering here and there. I thought i just need the framework of the file.
Found this link
hitechpreneur . wordpress.com/2013/07/09/imei-restoration-techniques-for-a-rooted-samsung-galaxy-s/ .(omit space)
Maybe if someone be kind enough to edit their Backed up "nv_data.bin" and replace their original IMEI with any random numbers from the file using the above method and post it.:angel: I might be able to get my phone to work again.
Link to Hex Editor
bpsoft .com/bbl/download/download.html?dlfile=hw_v673.exe (omit space)
And if possible please someone share the screenshot of the backed up content of EFS folder.
Please Help. It might be able to help a lot of people.
ThankYou!

Try a clean flash of a stock rom. I have not tested on the SG4 but it has worked on different models. It may rebuild it for you.
http://forum.xda-developers.com/showthread.php?p=64431358

Related

Advanced Backup/Restore tactics...

Okidoki.
With help of WinComm and little bit luck I found this...
See Screenshot.
This Backup Restore thingie is maybe same mechanism like Kies use...
These folders are removed after finish... I have NO idea what happens with these files... or where stored...
WinComm only show me this:
Code:
+[055]=> [641.314]Packaging Start[/Media/_SamsungBnR_/DRM.bk]
+[056]=> [641.560]Packaging Finish[/Media/_SamsungBnR_/DRM.bk]:[Success]
+[057]=> [641.618]Packaging Start[/Media/_SamsungBnR_/Configuration.bk]
+[058]=> [642.016]Packaging Finish[/Media/_SamsungBnR_/Configuration.bk]:[Success]
+[059]=> [642.072]Packaging Start[/Media/_SamsungBnR_/Message.bk]
+[060]=> [642.095]Packaging Finish[/Media/_SamsungBnR_/Message.bk]:[Success]
+[061]=> [642.152]Packaging Start[/Media/_SamsungBnR_/MusicSetting.bk]
+[062]=> [642.176]Packaging Finish[/Media/_SamsungBnR_/MusicSetting.bk]:[Success]
+[063]=> [642.231]Packaging Start[/Media/_SamsungBnR_/PhotoSetting.bk]
+[064]=> [642.251]Packaging Finish[/Media/_SamsungBnR_/PhotoSetting.bk]:[Success]
.
.
.
But I can't find *.bk files...
http://forum.xda-developers.com/showpost.php?p=19756666&postcount=10
You need Internal Menu...
Maybe someone could help to understand how it work...
Thanx.
Best Regards
hmmmmmm
This backup function done from the internal menu makes the files only while real backup is done by Kies
What i mean is if you clicked backup in Kies it sends a command to backup these files just like from internal menu then copy them to the *.sbu file
You can see that Kies is making a temp folder during backup that has all the files then deletes it after completing...I catched one of those temp folders before just before its delete but it don't has *.bk files at all ....It contains real data
Best Regards
If I'm fast enough, then I can catch few files...
Attached is filelist...
Hmmm.
But I don't understand where result is stored...
My testdevice is nearly empty... Maybe on full device better to see something.
Best Regards
Searching for String _SamsungBnR_ leads to this:
WsSyncml.so
in ShpApp.app
And in FFS I see this:
Contents.xml
...
Best Regards
Edit 1.
With help of this:
http://forum.xda-developers.com/showpost.php?p=21142664&postcount=186
Thanx again.
I have made ELF file... it is attached.
But my brain is too small.
Maybe someone can see, what where how is stored.
Thanx.
Best Regards
I am wondering why we never used alternate ways for faster Restore in "new" Firmware...
1. Multiloader "advanced" stuff
All user used Kies update in bada 1.x know.
That it is possible to update WITHOUT dataloss.
1.1
Users can read... in Multiloader
Differences only.
Why I never seen Tutorial to make own PFS + ShpApp_HD.app.
1.2
It seems most now only MINOR changes in apps_compressed... ever same size...
I have also few tests, where I have only flashed apps_compressed.bin...
Why we ever flash FULL and erase all our stuff...
I ever thought. Lemmings is an only nice Game....
2.
FOTA update is without dataloss...
Okidoki. But other problems as only few users are able to enter...
3.
Now 1 of the advanced thingie...
Why not investigate some time and energy to BACKUP database... in main it is:
DB2 and Registry folder...
Its long time ago...
I was able to make clones...
1:1 copy on 2 handsets...
Last tested Version was XXJL2.
Warning! During security it is not risk free to play with database.
Bootcycle etc...
But hey...
We not know how long Samsung need to rollout bada 2.0 ...
and make PFS + ShpApp_HD.app for S8500/S8530
I think it is NOT magic or impossible... Only little bit time and brain needed.
Best Regards
small pfs i used to work with
b.kubica
Thanx again.
It takes long time before I have realized how usefull SHP_CSC_FEATURES.zip is.
http://forum.xda-developers.com/showpost.php?p=21697568&postcount=13
After short look into your attached PFS I must smile little bit...
SHP_CSC_FEATURE_RECORD_VOICE=1
Thank you very much for all your findings.
Best Regards
sorry i haven't seen your thread when i opend my new thread
but these are all i've found from sbu files
that might help you
http://forum.xda-developers.com/showthread.php?t=1469175
---------- Post added at 03:35 PM ---------- Previous post was at 03:30 PM ----------
another thing that i understood right now!!
when you extract a .sbu file via 7zip you see a file "_mainfest.xml" which includes a "device id" that is static for all backups of a device
so maybe replacing this device id with our device id (which can be found with making a small backup) might help installing a device's backup on another
@Adfree
About PFS updating
I made an update for my own custom with my own hands ....No need for Kies anymore
http://www.sammobile.com/forum/showthread.php?t=3417
How i did it
I used WinMerge to compare every file from XXKL6 & XXLA1
Made PFS file from differences
Added some tweaks to make CSC & Registry updates
PFS is really a nice idea to update registry if what you are updating doesn't need master reset
Best Regards
Little progress...
*.bk files are simple ZIP.
I have catch them during Kies Backup...
My handset was new flashed... nothing installed...
Now several ideas...
Best Regards
a dummy question!!!
what do you want to do by knowing the mechanism of backups?
i myself like to restore a backup of a handset on another !
Totally forgotten...
But it seems now with DisableBadaIntegrity you can backup and restore DB2 folder... :good:
Via Multiloader...
This means f. Database...
Not tested yet by me... maybe "sooon"...
On bada 1.x it was possible to make 1:1 Backups...
Thank you b.kubica
Best Regards
BackupInfo.dcf
These files are created in every Info folder... if Internal Menu Backup is used...
http://forum.xda-developers.com/showpost.php?p=19756666&postcount=10
If you open these files... you can see:
Content-Vendor:htpp://samsungindia.com
http://forum.xda-developers.com/showpost.php?p=33260382&postcount=47
...
Best Regards

Whatsapp doesnt restore Backups

atm im jumping between different roms while waiting for next cm release. i also use whatsapp. everywhere on the net its is said that WA is supposed to ask me to restore previously made backups. BUT IT NEVER DID!
does anyone know how to restore those backups? or better: whats the problem with ace/WA? i have tons of backups, but could never use them-.-
things i already did:
- install, then add backup
- put backup into sd, then install
- searched here and found a tool that was supposed to show the chats in browser (and it failed hard (XD), what doesnt matters, cuz it doesnt solve the problem)
these chatts dont contain highly important information, but it would be very nice to have them back
thanks in advance
hmm me use whatsapp too.. as long as i remember... i never make backups.. but after switching roms.. it always ask me to restore from backup or not.. dunno either..
there is a possibility to manually make backups of WA chats. i saved the folder, flashed, put the folder back, installed: nothing happened
CJCord said:
there is a possibility to manually make backups of WA chats. i saved the folder, flashed, put the folder back, installed: nothing happened
Click to expand...
Click to collapse
i switch roms often too. and whatsapp.. well it does ask me to restore from the backup..
u could try an alternative - use titanium backup to backup the application+data.
that way when u restore from titanium, u will have ur messages back.
i dont need titanium for that. the files it rstores the chats with are at /data/data/com.whatsapp
i had an old nandroid backup (stock rom), extracted those files, copied them in their place (see above) and it "worked". i dont get asked to restore, but the chats are "just there". and you cant tell me this is normal. this is only possible if you are rooted. afaik no stock rom is usually rooted
but even the official wa help states, that ONLY the folder on SD card has to be copied to new device/new rom and it should work. WhyTF it doesnt do it for me?
€: sry fogot that: the nand-BU is old as hell. the chats i want to restore are from a rom already deleted/overwritten so restoring via titanium would be a bit hard (cuz theres no backup of that rom. there was no reason for that)
Can someone where the backup works, can tell me if you have a ".crypt" file or not?
seems that "my" WA cant read its own encrypted DBs -.-
it worked when transforming the crypted DB into an unencrypted DB
Hi
I've just encountered this problem too, lost all my messages of over 2 years! I too have ".crypt" file but it doesn't ask me to restore it. Did you find a solution? Please say yes!!
thanks
CJCord said:
Can someone where the backup works, can tell me if you have a ".crypt" file or not?
seems that "my" WA cant read its own encrypted DBs -.-
it worked when transforming the crypted DB into an unencrypted DB
Click to expand...
Click to collapse
more or less....
WA still didnt accept its own files but try this: http://forum.xda-developers.com/showthread.php?t=1583021
worked well and i have all my conversations back.
hope i could help
Saw that, and yes it works well. Obviously better than nothing, but not the same as getting them back in the phone. I've opened a support issue with WhatsApp, maybe a future release can resolve this.
cheers!
if you encrypt them with the tool, WA will restore them and you will have youre stuff "back in the phone"
if you get a response from official wa, please share =)
CJCord said:
if you encrypt them with the tool, WA will restore them and you will have youre stuff "back in the phone"
if you get a response from official wa, please share =)
Click to expand...
Click to collapse
You mean, if you decrypt the database file with the tool Whatsapp Xtract. Yes, that should work.
[TOOL] Whatsapp Backup Messages Extractor
Decrypt, then copy the decrypted file (msgstore.db instead of msgstore.db.crypt) onto the folder /sdcard/WhatsApp/Databases, make sure it's the only database file inside that folder and then newly install WhatsApp. It should ask you to import the backup during the process of installation.
Thanks you ztedd, that makes more sense! Are you saying that only decrypted files get restored? That's not the impression the WhatsApp website gave me.
ztedd said:
You mean, if you decrypt the database file with the tool Whatsapp Xtract. Yes, that should work.
[TOOL] Whatsapp Backup Messages Extractor
Decrypt, then copy the decrypted file (msgstore.db instead of msgstore.db.crypt) onto the folder /sdcard/WhatsApp/Databases, make sure it's the only database file inside that folder and then newly install WhatsApp. It should ask you to import the backup during the process of installation.
Click to expand...
Click to collapse
Backup foun but..
FrikyBCN said:
Thanks you ztedd, that makes more sense! Are you saying that only decrypted files get restored? That's not the impression the WhatsApp website gave me.
Click to expand...
Click to collapse
Whatsapp now detects a Backup, but when i hit "yes" to restore it, not a single chat gets restored. :/ Any suggestions?
I copied the file msgstore.db.html from the tool to the database directory and the delete the ".html" ending.
*WORKS: Copy the msgstore.plain.db file an rename it to msgstore.db, then it works!
Thanks!
Hi
i too have experienced lots of problems restoring my old chat from my old phone. I followed your advice below and it worked.
However, I have now lost my new messages that were on my new phone. How do I restore them too?
Please help...I'm totally clueless....Thanks
[Decrypt, then copy the decrypted file (msgstore.db instead of msgstore.db.crypt) onto the folder /sdcard/WhatsApp/Databases, make sure it's the only database file inside that folder and then newly install WhatsApp. It should ask you to import the backup during the process of installation.[/QUOTE]
If you have questions, ask in the Q & A thread!
Sent from my rooted microwave
why opening new thread if old one still exists?
@topic: ztedd postet in his thread a solution to merge 2 databases. i havent tried it myself yet (was posted a few days ago. (well. earlierer, but it had some...problems)) but it looks promising
Apologises if I am incorrectly posting on this forum but as my username suggests I am totally clueless to how this process works.
I do not not how to ask a question in the thread Q&A as suggested and by replying did not realise that I had posted a new thread.
Please forgive me.
Please advice how to correctly use this forum and how do I merge databases on two samsung phones or generally, after having successfully restored my old chat history following your advice, how do I add/merge the new chat on my new phone to the old chat that now appears to have replaced my new chat history.
Thanking you in advance for your help.
ztedd said:
You mean, if you decrypt the database file with the tool Whatsapp Xtract. Yes, that should work.
[TOOL] Whatsapp Backup Messages Extractor
Decrypt, then copy the decrypted file (msgstore.db instead of msgstore.db.crypt) onto the folder /sdcard/WhatsApp/Databases, make sure it's the only database file inside that folder and then newly install WhatsApp. It should ask you to import the backup during the process of installation.
Click to expand...
Click to collapse
Totally clueless said:
Apologises if I am incorrectly posting on this forum but as my username suggests I am totally clueless to how this process works.
I do not not how to ask a question in the thread Q&A as suggested and by replying did not realise that I had posted a new thread.
Please forgive me.
Please advice how to correctly use this forum and how do I merge databases on two samsung phones or generally, after having successfully restored my old chat history following your advice, how do I add/merge the new chat on my new phone to the old chat that now appears to have replaced my new chat history.
Thanking you in advance for your help.
Click to expand...
Click to collapse
It's alright.
You'll soon get used to it.
And btw, welcome to xda!
Sent from my rooted microwave
Your welcome
/topic: the thread you already posted "[TOOL] Whatsapp Backup Messages Extractor" contains all neccesary information you need for your operation: Programs, knoledge, and a little how-to.
But you will have to read by yourself
and you should read most of it, as those information are a bit...fragmented and scattered around that thread^^
€: im in a helpy mood^^ there you go: http://forum.xda-developers.com/showpost.php?p=37292158&postcount=464
guys i need help please i have the db.crypt file from the SD and only the files from the SD i backed it up while ago on my pc and now i deleted all files in the database and uninstalled whatsapp and added the backed file in database and reinstalled but i didnt get the restore msg :/ is there any way possible to restore those msgs its really important :/ i didnt know i had to back the files in root/data tho i am not rooted and the whatsapp xtracter asks for wa.db otherwise it says the file doesnt contain chat_list table >.>
please if there is any way lead me to it

[Q] WLAN not working after Nandroid restore on another S3

Hi,
i tried to restore a Nandroid Backup into another Galaxy S3, ROM and Baseband Version is the same.
After Restore everything is fine except WLAN, i can see accesspoints and also can enter the psw but it will not propperly connect to the ap it tells me authentication failure but the psw is correct and it will also not connect to an open accesspoint, something must be messed up with the wlan.
Can anyone help? Else i will use my old way over Titanium Backup but this is more time intensive.
Greetz X23
Anyone? I have exactly the same problem after doing a nandroid restore on my replaced S3. How do I fix this without having to do a factory reset?
Fixed the "Authentication error occurred" problem
I finally solved the problem after trial and error. I found that it was a file called .cid.info in /data that I needed to delete. My WiFi now works again.
vpwrf said:
I finally solved the problem after trial and error. I found that it was a file called .cid.info in /data that I needed to delete. My WiFi now works again.
Click to expand...
Click to collapse
Hi. I just registered cause I am trying to resolve this exact issue.
My situation: Cracked my screen on my I9300 (still working and yes, not the t-mobile version but international) and got a brand new replacement phone (exact same model) so I can get my old one repaired.
Did a NANDROID restore and copied internal SD card content (external SD card was simply physically swapped). Everything seems fine, but WiFi is not connecting to any router (famous "authentication error occurred - incorrect password" message).
Flashing a newer version of my ROM (Android Revolution HD, currently on 20.0, flashing 29.0 on my new phone) works fine, WiFi working as it should. So it is not a hardware issue.
So my question really is (as I simply want to "clone" the software layer of my phone until Android Revolution HD for 4.3 is released):
What else did you modify/change/delete to get this to work? Simply deleting .cid.info after restoring from NANDROID did not resolve the issue.
Any hints are highly appreciated. Been playing around with it for a week now (on and off) but cannot resolve the WiFi issue. Checked several forums and googled like a lot, but without any success. What am I not getting?
I am fairly new to Android (6 months), sometimes missing some (to others) essential background information and vocabulary, but happy to learn and not completely retarded.
Thanks for your help!
Have you tried forgetting the networks then reconnecting? Otherwise try renaming the .rev file. Or you could try copying the .cid.info from a ROM where the WiFi works fine to the Nandroid restored data. That might fix it.
I tried forgetting the networks, without success. I do not know what you are referring to by .rev file, and I do not have another device to restore my NANDROID image to, to then copy the cid.info file. So I kept playing around and this is what worked for me:
I found a file called wpa_supplicant.conf in the following directory: etc/wifi
Opening that file revealed some (as I was assuming) device related information (such as device type, model name, serial number, etc).
I renamed that file to .bak and this resolved my issue. I even deleted that file later on.
After enabling WiFi again, the file was not recreated by the system, even after a system reboot. I am not sure what this file does and how it was created, but so far everything is working as it should.
I also found a second file with the exact same file name at a different location: /data/misc/wifi
The content of that file is different, but some of the information is identical. This file contains WiFi AP information (like AP that I connected to in the past). Deleting that file would break my WiFi and would prevent it from turning ON. So I strongly recommend not to delete that file!
Needless to say: Do not make any modifications to system files without a functional NANDROID backup!
So in the end it seems to have been what I suspected all along. Some system file that was related to my old device and that, if identical, would create issues on the new device. But all of this is pure speculation. I am not an Android/Linux expert and simply tried to apply some logic.
I hope that I will now face no more issues. In case I do, I will report back.
Thanks for your help!
So, after getting my S3 repaired and switching back to it (usual NANDROID restore process), I was facing the exact same issue.
The wpa_supplicant.conf file that I was talking about did not exist, so I tried renaming the cid.info and that worked.
skofox said:
I tried forgetting the networks, without success. I do not know what you are referring to by .rev file, and I do not have another device to restore my NANDROID image to, to then copy the cid.info file. So I kept playing around and this is what worked for me:
I found a file called wpa_supplicant.conf in the following directory: etc/wifi
Opening that file revealed some (as I was assuming) device related information (such as device type, model name, serial number, etc).
I renamed that file to .bak and this resolved my issue. I even deleted that file later on.
After enabling WiFi again, the file was not recreated by the system, even after a system reboot. I am not sure what this file does and how it was created, but so far everything is working as it should.
I also found a second file with the exact same file name at a different location: /data/misc/wifi
The content of that file is different, but some of the information is identical. This file contains WiFi AP information (like AP that I connected to in the past). Deleting that file would break my WiFi and would prevent it from turning ON. So I strongly recommend not to delete that file!
Needless to say: Do not make any modifications to system files without a functional NANDROID backup!
So in the end it seems to have been what I suspected all along. Some system file that was related to my old device and that, if identical, would create issues on the new device. But all of this is pure speculation. I am not an Android/Linux expert and simply tried to apply some logic.
I hope that I will now face no more issues. In case I do, I will report back.
Thanks for your help!
Click to expand...
Click to collapse
It did not work for me. Neither does deleting .cid.info works.
That sucks. It's so frustrating.
Try to play around with it, based on the info in this thread. Make sure you have a working NANDROID backup, to just state the obvious (no offense).
Can you elaborate a little further what you believe caused the issue?
Reflash ing the rom would probably fix this.
Sent from my SAMSUNG-SGH-I747 using Tapatalk

Mobile Network wont work after root

Hi,
I just rooted my Galaxy Note 2, build nzo54k.n7100xxdmc3.
I rooted using this guide: http://forum.xda-developers.com/show....php?t=2143479, method number 2. Now I cant use networking. There is a cross over where the network bars use to be. Everything else seem to be working fine. It rebooted a couple of times tho. Can anyone help me with this problem, how I can fix this. If I press "mobile networks" it tells me that I have to insert a simcard. I have the simcard in and tried to restart the phone several times.
I would appreciate any help that you guys can give me. Thank you!
mvattoy said:
Hi,
I just rooted my Galaxy Note 2, build nzo54k.n7100xxdmc3.
I rooted using this guide: http://forum.xda-developers.com/show....php?t=2143479, method number 2. Now I cant use networking. There is a cross over where the network bars use to be. Everything else seem to be working fine. It rebooted a couple of times tho. Can anyone help me with this problem, how I can fix this. If I press "mobile networks" it tells me that I have to insert a simcard. I have the simcard in and tried to restart the phone several times.
I would appreciate any help that you guys can give me. Thank you!
Click to expand...
Click to collapse
Link you've attached is broken ,
Strange , Could you check if your device shows IMIE number or it shows null ?
aukhan said:
Link you've attached is broken ,
Strange , Could you check if your device shows IMIE number or it shows null ?
Click to expand...
Click to collapse
It says IMEI: unkown. I can check under battery if you need me to? Can it have something to do with my service provider? Im from Norway
mvattoy said:
It says IMEI: unkown. I can check under battery if you need me to? Can it have something to do with my service provider? Im from Norway
Click to expand...
Click to collapse
It seems you've corrupted your EFS folder buddy, Have you rooted your phone ? After Root did you backup your phone EFS folder ??? Or any kind Of NAND backup
aukhan said:
It seems you've corrupted your EFS folder buddy, Have you rooted your phone ? After Root did you backup your phone EFS folder ??? Or any kind Of NAND backup
Click to expand...
Click to collapse
I don't know what a EFS folder is. I have rooted my phone using this guide, http://forum.xda-developers.com/showthread.php?t=2143479
I used method number two. I just rooted my phone so haven't done anything yet. I think I have rooted my phone, I got a "Superu" app but haven't tried doing anything yet.
mvattoy said:
I don't know what a EFS folder is. I have rooted my phone using this guide, http://forum.xda-developers.com/showthread.php?t=2143479
I used method number two. I just rooted my phone so haven't done anything yet. I think I have rooted my phone, I got a "Superu" app but haven't tried doing anything yet.
Click to expand...
Click to collapse
EFS file is where your Imei , Mac address and few more important files are stored as you phone doesnt have an IMIE it shows as unknown so that is the reason your unable to make calls or the Sim is not getting registered, What you could try is to Flash a Stock Firmware and check if the IMIE shows up or else will have to take it to Samsung Service Center and will have to Pay for the Service.
The Guide which you've Followed dont say that you will have to backup the EFS Folder i've informed to update it on OP any ways not your mistake .
Always remember 1step after Root is to backup EFS File
Getting to know your EFS folder on Samsung Devices
Common Files We Back up
I am sure you have heard of critical things you need to do when you mess with an Android device right? One of the things that always come up is to back up your devices.
Backing up data usually involves making sure those contacts, calendar entries, memos, messages and special media that you may have kept within the internal memory are kept safe. The general rule when flashing and rooting is that often times, you may have to end up wiping all your internal memory data.
Some people tend to take this further and back up the internal data of apps, which is only possible if you have root access on your device. This is especially useful for those who like to play games as well as flash custom ROMs.
There are those who would also recommend that you back up the entire image of your current ROM state by making a Nandroid backup so that you can get back that exact state of your ROM if you mess up with flashing a whole new one or if you didn’t like the new ROM you tried and wanted to get back.
For Samsung devices, there is one other thing you may want to secure in a back-up chest – your device’s EFS data.
What is an “EFS”?
EFS refer to a folder location called /EFS in Samsung’s Android devices. It is a very sensitive folder hidden within the deepest core of your smartphone’s internal file system and is very essential to the functions of our smartphones.
One of the very sensitive information you can find in this folder is the information regarding your phone’s unique IMEI number. As you may have guessed by now, it also contains other unique identifying numbers for your smartphone including the MAC address for your smartphone’s radios, as well as the MEID, ESN, as wells as the registered phone number for locked smartphones.
The Danger to EFS
Normally, the EFS folder is highly protected. Rooting and flashing ROMs normally do not touch this part of the device. Unfortunately, there is no such thing as a controlled environment where everything goes according to plan in the real world. Sometimes, a process hits the EFS folder, or ends up corrupting the data within.
The EFS is also likely to be corrupted by users who like to unlock smartphones since it usually involves editing the data within the EFS folder. Once the data is corrupted, the only way to get it back to working order is to restore the data as is.
The loss of the EFS folder may cause your phone to no longer be recognized by your carrier or some of your radios may no longer work. This breaks the device as a whole no matter how many times you reinstall a ROM.
Even if you are not planning to modify the EFS folder itself, you can still accidentally corrupt that data. That is why even if the process of rooting and flashing ROMs does not require you to do so, it would be prudent to back up the folder. This would be a classic case of being “better safe than sorry”.
Why Modify the EFS
Messing with the EFS is what you would call some “high level stuff”. People normally don’t mess with this folder due to the high risk of making the smartphone unusable. The most common use of editing the EFS folder is to unlock the smartphone so it can be used on other carriers.
Most users usually steer clear of this folder. If you really want to mess with it, look for us tomorrow as we show you how to back-up your EFS folder.
aukhan said:
EFS file is where your Imei , Mac address and few more important files are stored as you phone doesnt have an IMIE it shows as unknown so that is the reason your unable to make calls or the Sim is not getting registered, What you could try is to Flash a Stock Firmware and check if the IMIE shows up or else will have to take it to Samsung Service Center and will have to Pay for the Service.
The Guide which you've Followed dont say that you will have to backup the EFS Folder i've informed to update it on OP any ways not your mistake .
Always remember 1step after Root is to backup EFS File
Getting to know your EFS folder on Samsung Devices
Common Files We Back up
I am sure you have heard of critical things you need to do when you mess with an Android device right? One of the things that always come up is to back up your devices.
Backing up data usually involves making sure those contacts, calendar entries, memos, messages and special media that you may have kept within the internal memory are kept safe. The general rule when flashing and rooting is that often times, you may have to end up wiping all your internal memory data.
Some people tend to take this further and back up the internal data of apps, which is only possible if you have root access on your device. This is especially useful for those who like to play games as well as flash custom ROMs.
There are those who would also recommend that you back up the entire image of your current ROM state by making a Nandroid backup so that you can get back that exact state of your ROM if you mess up with flashing a whole new one or if you didn’t like the new ROM you tried and wanted to get back.
For Samsung devices, there is one other thing you may want to secure in a back-up chest – your device’s EFS data.
What is an “EFS”?
EFS refer to a folder location called /EFS in Samsung’s Android devices. It is a very sensitive folder hidden within the deepest core of your smartphone’s internal file system and is very essential to the functions of our smartphones.
One of the very sensitive information you can find in this folder is the information regarding your phone’s unique IMEI number. As you may have guessed by now, it also contains other unique identifying numbers for your smartphone including the MAC address for your smartphone’s radios, as well as the MEID, ESN, as wells as the registered phone number for locked smartphones.
The Danger to EFS
Normally, the EFS folder is highly protected. Rooting and flashing ROMs normally do not touch this part of the device. Unfortunately, there is no such thing as a controlled environment where everything goes according to plan in the real world. Sometimes, a process hits the EFS folder, or ends up corrupting the data within.
The EFS is also likely to be corrupted by users who like to unlock smartphones since it usually involves editing the data within the EFS folder. Once the data is corrupted, the only way to get it back to working order is to restore the data as is.
The loss of the EFS folder may cause your phone to no longer be recognized by your carrier or some of your radios may no longer work. This breaks the device as a whole no matter how many times you reinstall a ROM.
Even if you are not planning to modify the EFS folder itself, you can still accidentally corrupt that data. That is why even if the process of rooting and flashing ROMs does not require you to do so, it would be prudent to back up the folder. This would be a classic case of being “better safe than sorry”.
Why Modify the EFS
Messing with the EFS is what you would call some “high level stuff”. People normally don’t mess with this folder due to the high risk of making the smartphone unusable. The most common use of editing the EFS folder is to unlock the smartphone so it can be used on other carriers.
Most users usually steer clear of this folder. If you really want to mess with it, look for us tomorrow as we show you how to back-up your EFS folder.
Click to expand...
Click to collapse
Thanks for your help.
I knew I could lose everything on my internal memory but diden't bother me. Can you link me to how I flash with custom rom?
mvattoy said:
Thanks for your help.
I knew I could lose everything on my internal memory but diden't bother me. Can you link me to how I flash with custom rom?
Click to expand...
Click to collapse
first recommend you to flash stock and try see if you've got you IMIE .
mvattoy said:
Hi,
I just rooted my Galaxy Note 2, build nzo54k.n7100xxdmc3.
I rooted using this guide: http://forum.xda-developers.com/show....php?t=2143479, method number 2. Now I cant use networking. There is a cross over where the network bars use to be. Everything else seem to be working fine. It rebooted a couple of times tho. Can anyone help me with this problem, how I can fix this. If I press "mobile networks" it tells me that I have to insert a simcard. I have the simcard in and tried to restart the phone several times.
I would appreciate any help that you guys can give me. Thank you!
Click to expand...
Click to collapse
1st flash a stock rom and see whether u get imei and baseband back or not.. if it didnt get recovered then service centers can only help you as u didnt make a backup of efs..
There is a slim chance its not his efs,
I did pretty much the same as he to get root thru the toolkit, and had no network, I found I had no APN configured
Perhaps check this.
Settings... more settings .. mobile networks... acess point names.
Make sure you have something here.
if not you will need to search for the settings for whoever your provider is.
good luck
A|c

Need your help if you have a rooted HTC Desire HD

Hi All, we are working on unbricking HTC Desire HD and need the partition info and partition backup from a working DHD phone to move forward. If you have a working rooted DHD, you may help us on any of below. Thank you!
1. if you rooted your phone by using gfree, then as this page (http://forum.xda-developers.com/wiki/HTC_Vision) in section '6. Backup and cleanup' it mentions the gfree can backup part7backup-.bin, etc. If you have those backup files, can you please send them to us.
2. with your working phone, you may retrieve the partition info as this post (thanks E:V:A), can you post your partition info output, as well as your carrier name and ROM info. Other info like recovery type/version, HBOOT display (which shows S-ON/OFF, Radio version, etc) and CRC's are also helpful but optional.
3. If you phone's microSD has 2G or more free space, and you has some Linux and ADB knowledge, you can backup the whole internal memory of your phone to a file on SD, then pull the file over to your PC, and upload somewhere and share with us. See This post (thanks TrevE) for details. Please note this type of backup file has all your phone memory including the IMEI number and your user data, so please don't share it in public. You may use a HEX editor to search the backup file for your IMEI number and mask it (I don't know if it is encoded or encrypted somehow). If you can trust me, please upload your backup and PM me the download link.
4. If you are a developer (know python and has Linux or Windows with Python), you may try to run the attached script to pull the partition info and backup partition by partition as this post (thanks darkspr1te) . However, the post and script was not coded and tested for DHD so you may get error and need to edit the script to make it work with DHD.
Thanks for you help!
Anyone??
You wouldnt know when you would arrive in a QHSUSB_DLOAD situation.

Categories

Resources