First I'd like to say hello to all. I've been looking for the most comprehensive android discussion forum, and I think I hit the jackpot here. Anyway to the point. As it is known by the pros here, The S3 comes from your telecom company loaded with your personal connection info. From what I've read recently, the carriers either don't know how, or simply wont backup the nv and efs data to the onboard chips to preserve it in case of software failure, or mod failure. I did find an article with google explaining that a couple of devs discovered the fix for this inside the bootloader that we can use to force that backup to happen like it should, and it works. I've flashed several times since that backup and not lost the data from the phone. When I install cyanogen mod 11, it does not read those 2 particular memory blocks on booting, thus cyanogenmod does not recover the imei data from the onboard backup, even after a factory reset. I really would like to see if there is a workaround for that because unfortunately for me, any other method for backup is illegal where I live. If I flash back to stock rom, It reads the data back out of the chip, and restores my connection data for the carrier to the efs partition as well as the other 3 displayed in EFS Backup Pro. But I really like cyanogenmod, and since one of it's developers worked at Samsung, I'm really hoping my question finds an answer here.
So my question is is anyone familiar enough with the Cricket version of the S3 and cyanogenmod to tell me of a workaround for that problem if it exists. Thanks in advance for the community's responses.
Did You used the "cricket" Version of cyanogenmod?
Sent from my loved HTC One S using buggy Tapatalk 0.o
LS.xD said:
Did You used the "cricket" Version of cyanogenmod?
Sent from my loved HTC One S using buggy Tapatalk 0.o
Click to expand...
Click to collapse
I used the cyanogenmod installer to install. From what I've read, the universal installer detects my phone and installs the correct version. Also I think that all s3 builds are now unified, so that's not an issue. Tried 10.2 after that, and caused my self more problems than I needed to fix, so I flashed back to stock. But I am going to attempt the mod again after backing up efs and nv if I have to. I can only run 4.3 or 4.4 android, which means I can only run 10.2 or 11 on my phone, or it will nuke the bootloader and hard brick my phone.
Corny007 said:
I used the cyanogenmod installer to install. From what I've read, the universal installer detects my phone and installs the correct version. Also I think that all s3 builds are now unified, so that's not an issue. Tried 10.2 after that, and caused my self more problems than I needed to fix, so I flashed back to stock. But I am going to attempt the mod again after backing up efs and nv if I have to. I can only run 4.3 or 4.4 android, which means I can only run 10.2 or 11 on my phone, or it will nuke the bootloader and hard brick my phone.
Click to expand...
Click to collapse
http://download.cyanogenmod.org/?device=d2cri
Sent from my loved HTC One S using buggy Tapatalk 0.o
---------- Post added at 05:51 AM ---------- Previous post was at 05:50 AM ----------
This is the cricket Version
Sent from my loved HTC One S using buggy Tapatalk 0.o
Versions are correct. Its not a version problem, it's an implementation problem where cm10.2 or 11 does not read the memory blocks that store the eps and nv data. Stock rom from cricket will read them and restore nv data from the chips. (I am not referring to the efs folder that can be seen as root. Im referring to the data stored in the 2 chips that Samsung and Cricket don't tell you about. Normally a corrupted efs folder is backed up from there because no one backs it up first. Google "Samsung derp" and you will find the article I found that explains this. People lose their efs because they don't know this about the knox system, and that it's not backed up properly. When you do not do " su nvbackup" then you lose your number. You do he nv backup procedure correctly and it backs up your current efs, then it's automatically restored whenever you flash a rom that reads those blocks. Cyanogenmod does NOT read those blocks to rebuild the efs/nv data. If it did, then when I do the factory reset after flashing, my phone would work right after the reset, but it does not. Neither version 10.2 nor 11.x reads those blocks.on reboot.
Corny007 said:
Versions are correct. Its not a version problem, it's an implementation problem where cm10.2 or 11 does not read the memory blocks that store the eps and nv data. Stock rom from cricket will read them and restore nv data from the chips. (I am not referring to the efs folder that can be seen as root. Im referring to the data stored in the 2 chips that Samsung and Cricket don't tell you about. Normally a corrupted efs folder is backed up from there because no one backs it up first. Google "Samsung derp" and you will find the article I found that explains this. People lose their efs because they don't know this about the knox system, and that it's not backed up properly. When you do not do " su nvbackup" then you lose your number. You do he nv backup procedure correctly and it backs up your current efs, then it's automatically restored whenever you flash a rom that reads those blocks. Cyanogenmod does NOT read those blocks to rebuild the efs/nv data. If it did, then when I do the factory reset after flashing, my phone would work right after the reset, but it does not. Neither version 10.2 nor 11.x reads those blocks.on reboot.
Click to expand...
Click to collapse
Looked at this already? --> Backup + Restore EFS SIII
I'm not sure how, but I'm up and dialing.
LS.xD said:
Looked at this already? --> Backup + Restore EFS SIII
Click to expand...
Click to collapse
Sorry I didn't get back here. I have an update. Corny007 1, Samsung Galaxy S3 0. I won :highfive: The first time I installed cyanogen I did it with the installer, and like I said, the blocks weren't read. Not sure how or why yet as I'm just starting out, but I did about 2 or 3 days research, kept hitting dead ends, so I decided just to go back and use the installer again. For some reason, and I still have no idea why, as I mentioned my IMEI data would not restore. This time, it did, no backing up required. I do have them just in case, except I never went through the trouble to get them onto my Ext/SD, and I couldn't figure out how to work around version mismatches after Philz was overwritten. I could have installed the SDK, and took a couple more days probably to get it that way, but for some reason, that I still don't know, maybe it was a bugfix between last time and this, not sure. Bottom line is I am modded, and calling. Thanks for the suggestions, I'll hit the thanks button too. By the way, I never answered your question. I did look where you recommended. It just seemed like I was the one exeption to everything I found. EFS Pro for example couldn't make the .tar file, just little headaches like that. Thanks again.
Hello,
I started with Galaxy Note 2- i317M (rogers, canada), rooted with DN3 V4 beta installed. But I wanted to try DN4, so I created a back-up using TWRP and tried installing DN4. However, I later realized that it is not for the LTE versions yet and phone did not recognize SIM anymore. So I wiped the data and tried installing dn3 v5.5, but the phone still did not connect.
Losing all hope I installed DNv4 again, but it still did not work. So i finally just tried restoring from the back-up I made using TWRP. Everything in the phone is same except no network.
Finally I tried restoring from back-up after doing a complete wipe of internal storage and everything except the external card. But still the error does not go away. I researched more about the error and the fact that my imei shows up as null/null. I used the instructions of using EFS professional, but it did not work. The model number in my phone now shows up as SM-G900F and baseband shows as unknown, and it shows DN3V5 Rom despite the clean-up and restoring from DN3V4.
Any guidance available on this please...I need specific steps because after 12 hour search and try-outs I am lost now.....
UPDATE:
Solved it! Here is the solution for anyone in this problem
http://forum.xda-developers.com/showpost.php?p=46231268&postcount=4
worked like a charm.. No reason to throw this and get a new phone
I have had this problem. It didn't happen whilst flashing though. My imei number is now a generic one and I had no efs backup. After 5 days of trying everything I can find I'm giving up. My note 2 is dead as far as I'm concerned. As far as I'm aware to get my imei back I'll have to send it for repair so I'll buy another phone and not a Samsung
I don`t think your phones are dead. I didn`t try it personally, but I`m sure you can restore your EFS back. Just you need to do some research, maybe you could start here:
https://www.google.ro/?gws_rd=ssl#safe=off&q=how+to+recover+efs+folder
Do not give up, read on end you will eventually do it! And, by the way, next time maybe you don`t forget to back up before doing anything to your phone!
nmugurel2003 said:
I don`t think your phones are dead. I didn`t try it personally, but I`m sure you can restore your EFS back. Just you need to do some research, maybe you could start here:
https://www.google.ro/?gws_rd=ssl#safe=off&q=how+to+recover+efs+folder
Do not give up, read on end you will eventually do it! And, by the way, next time maybe you don`t forget to back up before doing anything to your phone!
Click to expand...
Click to collapse
I did back up. with both titanium backup and twrp but it is not working. And I dont think I will give up. I will format is all together and start over if i have to.
Do you think it will work if I format it entirely and start over?
dexterousyash said:
I did back up. with both titanium backup and twrp but it is not working. And I dont think I will give up. I will format is all together and start over if i have to.
Do you think it will work if I format it entirely and start over?
Click to expand...
Click to collapse
Glad to see you solved it!
So I made a backup and promptly flashed a new rom as soon as I got my OPO it hasn't even been activated yet. When I went to activate it I realized my imei number was null. I looked for my backup but I must have deleted the backup somewhere along the way. Is there some way to restore this. Like if I flashed the stock image would it fix this? I saw another thread for fixing a corrupted EFS but is that the same thing. I'm sorry I don't really understand much of this stuff.
Thread concerning corrupted efs is where you need to be.
Hey guys,
It's briefin here. So yeah long story short, I recently restored a TWRP backup file of the EFS partition from another OnePlus 7 Pro. Now everything else seems fine but unfortunately my whole IMEI is just messed up (It's showing 0(zero). And that's why phone 's network signals isn't working anymore. Also I don't have any backup of my original EFS Partition. So is there any way, that I can rewrite my IMEI to my device?
Briefin said:
Hey guys,
It's briefin here. So yeah long story short, I recently restored a TWRP backup file of the EFS partition from another OnePlus 7 Pro. Now everything else seems fine but unfortunately my whole IMEI is just messed up (It's showing 0(zero). And that's why phone 's network signals isn't working anymore. Also I don't have any backup of my original EFS Partition. So is there any way, that I can rewrite my IMEI to my device?
Click to expand...
Click to collapse
Buddy I'm kind of in the same boat. I tried a sim unlock I was directed to and lss my backup became corrupted and gone forever. It's been a nightmare. And so far not looking any better or at least for me. But if theirs a way I'll find it
https://www.gizmoadvices.com/repair-imei-snapdragon/
matze19999 said:
https://www.gizmoadvices.com/repair-imei-snapdragon/
Click to expand...
Click to collapse
Thanks. Mine wasn't a imei issue. I actually fixed mine found a 2nd copy of my efs backup I drunkenly made
Hi,
I hope someone can answer this question:
I dropped my Oneplus 7pro and the screen cracked. Its still useable but i bought the same model again and want to use the backup of the old phone. I took a full backup from the old phone and now i am not sure if should use the whole backup or f.e. only the system and data image?
Anyone didi this before?
Thx in advance
Edit: Twrp on the new phone didnt even recognize the Backup file from the old one, so I am doing it with Oneplus switch app.
System and data may work. But nothing else. You'll end up with a messed up efs if you do