Related
Hey guys! After flashing to xxkpe, the phone and csc both showed "unknown". After repeated flashes the csc problem was fixed but even after flashing 5 times the phone still showed unknown and it wont recognize the sim card. any suggestions???
what did you flash? more details please...
Oh sorry i forgot to add i flashed XXKPE!!!
Is your IMEI visible
No IT IS NOT. I flashed back to xxkp9 and same problem!
Open phone and dial *#06#
If it doesn't show the imei number and you don't have the back up, your only option is samsung service center
Sent from my GT-I9003 using XDA App
1. Try flashing XXKPE twice. Use the latona file before the first flash only. Then factory reset after flashing the firmware for the first time. You probably placed the files wrong.
2. You can always try to use someone's nandroid backup of CWM and restore on your phone and test and check.
3. Service center.
how to make the back up of IMEI
tarunagg said:
how to make the back up of IMEI
Click to expand...
Click to collapse
Backup IMEI
Basically the method is almost alike. Just flashing it is an issue that I don't know how.
I think you post in wrong forum
I just used Root Explorer and copied my "/efs" folder to my external SD card (i.e copy "/efs" folder as a whole to "/mnt/sdcard/external_sd/backup").
But it sounds like you hadn't done this backup before you flashed. I think the only option is to go to the service centre and have them recover it for you. Before you go, take a Nandroid backup using CWM and a backup using TitaniumBackup. Make sure all the backups from Titanium go to the external SD card.
Also it is probably best to flash back to your original firmware (or something close from here) before giving it to them, and try to act innocent (---> "What's a firmware!?! I flashed who?!?!")
BTW @ Misledz: Here is the original post. Also contains a compressed efs attachment. Do you think it would be too complex to modify that and flash it (find the IMEI from the box and manually input)?
Cherio!
Can anyone please upload a copy of the efs folder?
I'm on Valhalla-Final with it's stock Kernel. I had a Bad flash which resulted in my IMEI becoming 0000000000000.
My phone is working fine right now (I can't download Swype Beta. I get can't install Android Emulator Notific) on Valhalla-Final AND I have my (Pre flash) efs folder backed up on my external sdcard and my laptop.
My back up is different than my current efs folder. It has my IMEI #, ect, in it. It is Good.
I have researched and read this thread:
http://forum.xda-developers.com/showthread.php?p=12807550
But a fix for me isn't in it.
What do I do??.. I could delete my Null efs folder and paste my back up then reboot??..
I DON"T WANT TO MESS THIS UP. To me the only thing worse than this problem is a Hard Brick.
Any Advise will be Appreciated.
I ALWAYS Give Thanks!
First take out the battery for 10mins and see if the IMEI is restored after you power it back on.
Sent from my SGH-T959V using XDA App
I've tried that twice already and I'm doing it again right now at your suggestion..
right before the battery pull I copy, pasted and rebooted my backed up efs folder to the efs folder WITHOUT deleting my current and 000000000 efs folder. That did not work.
FIXED!!!
I deleted my 00000000000 IMEI efs folder and copy and pasted my pre-flash efs back up using Root Explorer (Paid version) Then Powered down and Powered up.
My IMEI AND Wi-Fi MAC address are both restored!!..
I guess I knew what to do but wanted confirmation.. I don't have a contract and paid $500 for my phone so Mod with Caution..
If I have Your/THE answer for you I will ALWAYS give it even if I think you should know it or find it on your own.. Probably because I can only help on a few things so I'm proud to and not burnt out helping Members LOL...
Thank God I came here when there was no CWM or ROMS and it was so Dead People were EAGER to Help me. Because I knew NOTHING.. This is my first time Rooting and hacking Andriod. My first Forum..
I Love this Phone, It's Devs, Themers, Modders and Members!!
THANK YOU ALL!
Now that my IMEI is restored I just downloaded and installed Swype Beta...
If you get a " Can't Install Android Emulator" Notification check that your IMEI is not 00000000000..
Menu> Settings> About Phone> Status> IMEI.. check Wi-Fi MAC address TO
What is it? Because I want to download the mokeeOS, but the installation is confusing me, so I wanna know if the efs matters
Sent from my SGH-T959V using XDA
1. Yes efs matters a lot
2. I don't know a whole lot but it holds the network info, imei number, and alot of other really important things
Sent from my SGH-T959V using xda premium
Although there is a way to make sure you have a backup, flash this file in cwm
sourceforge.net/projects/teamacid/files/fb/cwm/cm7-efs-backup.zip/download
And there will be two files in the root of your sd card
Efs-backup.tar and efs-backup.tar.md5 ( I suggest save it to your computer, it saved my ass )
And you can restore this backup at anytime by flashing this
sourceforge.net/projects/teamacid/files/fb/cwm/cm7-efs-restore.zip/download
Good luck
Sent from my SGH-T959V using xda premium
Efs is the files system that holds the unique identifiers for your device. Without it, your phone is basically useless. You won't be able to connect to any network properly do things like phone calls, internet, texting, are all degraded, if they even work at all... Make sure you know what you are doing before messing with it. Fb created a vet good guide on the wiki. Follow it to a T!
Sent from my SGH-T959V using XDA
I would suggest using a root browser to copy the EFS folder to somewhere safe on your PC and copy a 2nd back-up to your SD card. I lost IMEI going from CM7 to moKeeOS but was able to easliy restore it with a back-up and a root browser.
The flashable EFS back-up/restore from FB should still be used, but with EFS/IMEI I don't think you can be too careful and backing it up manually as previously stated is a good idea.
Yeah, I keep multiple copies of it on my PC. The reason being is that I copy it whenever I do a backup before a flash. So I have a directory with the date with 3 folders: efs, nandroid, and sdcard. I used adb to copy them:
Code:
cd efs
adb pull /efs/
Probably overkill, but better to be safe than sorry, eh?
Ok, but once you lose IMEI and don't have a backup (I received this phone for repair), then what can I do?
serialteg said:
Ok, but once you lose IMEI and don't have a backup (I received this phone for repair), then what can I do?
Click to expand...
Click to collapse
It's pretty much screwed without the OEM Samsung/Tmo software. You would have to send it to Samsung for repair, or you might get lucky and get an engineer to hook you up, but that is unlikely...
thomas.raines said:
It's pretty much screwed without the OEM Samsung/Tmo software. You would have to send it to Samsung for repair, or you might get lucky and get an engineer to hook you up, but that is unlikely...
Click to expand...
Click to collapse
thanks for the answer. that OEM software isn't available in the forums or anywhere else for us? because I swear I flashed something OEM'ish without root with heimdall.
also, the imei is on the battery part of the phone, can't i fix it?
i read somewhere that you could use a phone just fine without imei on the about phone.
you can use the phone without imei, but it doesn't function as well as it would with it. Also, i was using titanium backup and it said my device's id was changed, and it showed my actual imei. If i were to restore it, would that fix the imei?
EFS help on the SGH-T959V
Basically, I've had a hell of a time with some EFS drama this weekend, made a total noob mistake, but in a stroke of luck I was able to "recover" so to speak my EFS even after it was supposedly "wiped."
After some thorough research and READING and bit of thought, I realized that the PIT mapping layouts between BML and MTD are indeed different, and that in theory if one remaps to BML (in layman's terms a stock partition map) then the EFS data originally on the phone gets correctly remapped (at least in my case it did).
To reiterate:
1. I did a nandroid backup. Basic ****. I hope to god you at least did this step too.
2. I used the cm7-efs-backup.zip script to backup my EFS. This was my first mistake. In my case, I don't know why I'm still researching, this script failed to make a backup .tar on my sdcard or anywhere else for that matter. It didn't throw any error messages either on the screen in the process. Not trying to attack the authors of that script, I'm just saying it didn't work for me this time.
3. I pushed the TWRP boot.img with Heimdall
4. I used the cm7-efs-restore.zip script which also "succeeded" but did nothing to restore any sort of EFS obviously because there was no backup to begin with.
5. I flashed R11 unofficial cm7 and booted up. Everything was fine but the IMEI was corrupted and I confirmed that the new MTD EFS partition was empty. On T-Mobile I could place no calls and only got sporadic and intermittent data access.
It was at this point I was sure I had ruined my phone.
After some more careful reading I realized that the original EFS was still present on the firmware, however the new MTD layout I flashed (wisely) stores its EFS partition in a different physical location. In theory, I thought if I reverted to BML and a stock ROM then I would recover the original EFS. In my case, this was successful.
1. I accessed the most recent "boot.img" file from my most recent nandroid and pushed that back to the device with Heimdall
2. At this point you have to flip your USB drivers back to USB Composite Device.
3. I then used a Heimdall one click to return to a rooted stock KJ6 "Gremlin Remover"
4. Upon restart, everything was fine (sigh of relief)
At this point, I'm still trying to determine why my EFS cannot be backed up with a few automatic tools. I made a backup of the file structure, but even lyriquidperfection's EFS Pro 1.4.7 can't make a backup of the EFS. It can access the ADB Server, but the backup 'fails'.
I'll check back in after I figure out why.
Hopefully this info will help anyone else who has switched to MTD and has a missing EFS.
nick.tansy said:
At this point, I'm still trying to determine why my EFS cannot be backed up with a few automatic tools. I made a backup of the file structure, but even lyriquidperfection's EFS Pro 1.4.7 can't make a backup of the EFS. It can access the ADB Server, but the backup 'fails'.
I'll check back in after I figure out why.
Hopefully this info will help anyone else who has switched to MTD and has a missing EFS.
Click to expand...
Click to collapse
I had similar issues yesterday. If your trying to install the twrp and then downgrade to the version with wifi dont flash the boot.img with heimdall. Follow the instructions for installing via cwm.
Just install the zip that has twrp in it. But follow the directions for normal cwm installation.
Also when trying to make a backup of your efs, make sure system is mounted. I initially did not have any problem but I was on antonx's kernel and when you flash with that recovery it would mount properly. What is happening is system isnt getting mounted. So its making a null backup.
The most important thing to do is when you are trying to make a backup of your efs is mount system!
Hi have you tried the updated EFS Pro v1.7.13? It can now automatically detect the mount point of the '/efs' folder for back up and restore. Also many many bug fixes and new code to communicate with adb.exe alot more quickly and efficiently.
Head over to the forum and check it out.
I already solved this problem, but this would seem useful other people with the same problem. But what forums are you exactly referring to?
Sent from my SGH-T959V using XDA
mierkat09 said:
I already solved this problem, but this would seem useful other people with the same problem. But what forums are you exactly referring to?
Sent from my SGH-T959V using XDA
Click to expand...
Click to collapse
This one.
http://forum.xda-developers.com/showthread.php?p=18524176
So i broke the glass on my n5 but it's working ok, recently i manged to buy a cheap new white one, and basically have 2 working phones.
I want to transfer all my stuff from the old > new, i'm wondering, apart from the usual Titanium path, is there any google service or other method that will make a copy of my old phone on the new one?
What would be the best approach here, if Titanium, are there any shortcomings?
ty
Why not backup in TWRP (make sure NOT to backup EFS) and then restore (once again, WITHOUT EFS) on the other phone? Everything will be exactly the same.
Also make sure they're both on the same bootloader/baseband.
You forget the content of your /sdcard. Use adb pull/push to transfer your favorite folders/files to your new device.
Tnx gents! I was thinking of nandroid, but wasn't sure it can work between phones.
They have the same baseband, by the same bootloader you mean the same version/build number?
Of course i will transfer sdcard by other means.
btw. it's strange google doesn't offer simple backup/restore to new phone
invisibles said:
Tnx gents! I was thinking of nandroid, but wasn't sure it can work between phones.
They have the same baseband, by the same bootloader you mean the same version/build number?
Of course i will transfer sdcard by other means.
btw. it's strange google doesn't offer simple backup/restore to new phone
Click to expand...
Click to collapse
I did that,since I asked Google to replace my phone due to abattery charging problem. I installed same bootloader same radio same twrp version on both phones,backup all the "SD card" with a PC,and then made a nandroid backup. Now if you export the whole nandroid folder on the new phone ,you will not be able to install it because the folder name is related to the phone serial (if you look at the nandroid folder is named with many random charters). To solve this I created a nandroid backup on the new nexus 5 ,and renamed the backup of the old one with the name of the new one. This worked for me . I don t know if now you have to do the rename stuff no with last versions, but was like this 8 months ago (don't remember twrp version).
Don t backup efs partition and restore on the new one,it contains the imei and other stuff,and don't try to flash a 32gb nandroid backup on a 16gb model, I don't know if it will work
It worked, i also found out you can migrate stuff from the old nexus using google tap&go through nfc, don't know how much that restores..
Ty all for the help
Hi,
I have a note 3 neo, 7505 and i updated the firmware. It was all working good for a week then i was listening to soundcloud to sleep and the phone restarted, since then the phone doesn't have an imei and says to insert sim card, and of course unknown modem..
Anyway, i created a backup of the efs using twrp, i have tried gazillion ways to restore the backup and gazillion manual ways too. Going to stock recovery... trying to copy manually the nvdata and all but it doesnt resolve. The files are placed there, i can see it in the shell but the thing just wont work!
i don't know how to proceed to this, i don't know if its a hardware fault, had it been that, shouldnt have i gotten the efs corrupted or some issue? could it be that the hardware itself is damaged all of a sudden? i dont think so, i pretty much think its the efs and yet i cant restore it?
should i attach my efs folder if someone can look through hex editor or logs to suggest a possible solution?
Thanks a lot and also i have search through and proceeded with many solutions and after that created a thread. hope someone can help.
P.S. I just noticed the serial number can be seen in phone status, so apparently its reading NVdata? or is it getting it from elsewhere? how to test if its a hardware fault?
penandweb said:
Hi,
I have a note 3 neo, 7505 and i updated the firmware. It was all working good for a week then i was listening to soundcloud to sleep and the phone restarted, since then the phone doesn't have an imei and says to insert sim card, and of course unknown modem..
Anyway, i created a backup of the efs using twrp, i have tried gazillion ways to restore the backup and gazillion manual ways too. Going to stock recovery... trying to copy manually the nvdata and all but it doesnt resolve. The files are placed there, i can see it in the shell but the thing just wont work!
i don't know how to proceed to this, i don't know if its a hardware fault, had it been that, shouldnt have i gotten the efs corrupted or some issue? could it be that the hardware itself is damaged all of a sudden? i dont think so, i pretty much think its the efs and yet i cant restore it?
should i attach my efs folder if someone can look through hex editor or logs to suggest a possible solution?
Thanks a lot and also i have search through and proceeded with many solutions and after that created a thread. hope someone can help.
P.S. I just noticed the serial number can be seen in phone status, so apparently its reading NVdata? or is it getting it from elsewhere? how to test if its a hardware fault?
Click to expand...
Click to collapse
The point is that TWRP creates faulty EFS backups on many devices which can't be restored properly.
There are different backup solutions (e.g. EFS Pro) confirmed working which may help you prevent future issues. I prefer the manual backup using adb shell or terminal emulator:
dd if=/dev/block/mmcblk0pXX of=/storage/SdCard/efs.img bs=4096
(XX needs to be replaced with the model specific partition number as they use different partition tables)
Restore:
dd if=/storage/SdCard/efs.img of=/dev/block/mmcblk0pXX bs=4096
thanks LS.xd, but i guess i have a pretty solid backup as i did create backup various ways, some were corrupt, but one that i working with has nvdata and every other file along with imei pretty intact....
i can open it up with winrar, and open the nvdata with hexeditor, i was wondering if i could confirm some way that the back up is actually 100% solid?
wondering if the partition's aren't aligned. I don't know for sure if EFS folder in the root directory is the same as being pointed by /mmcblkp03/platform/by-name/EFS ?
i mean they should be the same thing, its just a redirection right?
what should i be doing now? the baseband is unknown and the imei wont just work, waste the phone? or it could be done via some boxes or some other process?
there must be a starting point? isn't there some way i could use a generic imei and just any modem? then i could replace nvdata may be? right now, i'm installing various versions of stock firmware and repeatedly placing old efs data in various ways and i kind of turning hopeless. first i lost a nexus then i bought a g4 last month, gave me a bootloop just a week after, gone dead. then i bought the n3n and now this..... i mean 3 phones in a row..... i really hope this could work..
penandweb said:
there must be a starting point? isn't there some way i could use a generic imei and just any modem? then i could replace nvdata may be? right now, i'm installing various versions of stock firmware and repeatedly placing old efs data in various ways and i kind of turning hopeless. first i lost a nexus then i bought a g4 last month, gave me a bootloop just a week after, gone dead. then i bought the n3n and now this..... i mean 3 phones in a row..... i really hope this could work..
Click to expand...
Click to collapse
So you got some non TWRP made EFS backup, too? You can list your partitions using shell:
[email protected]:/ # cat /proc/emmc
You can use the dd command once you know the layout. Backups not generated manually may only be restored with the specific app/version and are probably not compatible using other restore methods. For my OnePlus 3 EFS backup can generated fine using TWRP but restoring it screws up the partition. Manually created image works fine. As I don't have a Note 3 Neo I don't know how it behaves for your device.
any idea how would i go on about inspecting the nvdata.bin? i'm in hex editor trying to see something resembling imei but its just so much garbage except a few lines.
i can't be sure whether its corrupt or not...
in efs -> imei -> a file called mps_code.dat i open it up in hex editor, and it has only 3 characters.....
is it possible i could initially use a generic imei and modem and later on populate it with actual somehow or just keep using generic one for now until i find a better solution, using hex editor or something...?
there are some tutorials on qualcom.. none for exynos but it should happen the same way, somewhere in nvdata, you place the imei ... and it would be generic method for most exynos devices...
i wish someone could guide me to that...
also can it be restored via "boxes"?
penandweb said:
any idea how would i go on about inspecting the nvdata.bin? i'm in hex editor trying to see something resembling imei but its just so much garbage except a few lines.
i can't be sure whether its corrupt or not...
in efs -> imei -> a file called mps_code.dat i open it up in hex editor, and it has only 3 characters.....
is it possible i could initially use a generic imei and modem and later on populate it with actual somehow or just keep using generic one for now until i find a better solution, using hex editor or something...?
there are some tutorials on qualcom.. none for exynos but it should happen the same way, somewhere in nvdata, you place the imei ... and it would be generic method for most exynos devices...
i wish someone could guide me to that...
also can it be restored via "boxes"?
Click to expand...
Click to collapse
After 3 years I had to retire my HTC One S. I flashed roms and firmwares up to 3-4 times a week without having any issues. One sunny day some update bricked then nvdata. I spent a bunch of hours trying to restore it in different ways, extracted data from stock firmware as well as using dumps from other user's phones, as some users reported this error fixed doing so. Even when the files was identical it just did not work for me. Changing the mainboard was the only possible solution so I decided to get a new device.
All I want to say is try to restore a valid backup in a way confirmed working. If you don't have a usable backup ask in your device's forum for somebody may upload it. Or spend 100 hours messing around with hex editors until you reach then point where you realize its cheaper to switch the device as wasting a year's holidays browsing the internet for some solution.