Database Users

S5 IMEI null and Service mode blank

Hello,
I have this problem with my phone and i don't know how to fix it, the IMEI is Null and when i enter "*#0011#" the ServiceMode is Blank !!
I tried to use GS5_EFS_Backup but it doesn't work ! Also the phoe get hot a lot, and when i put it in charge the battery level of charge is stuck in 10% always.
My phone is rooted.
Help me Please.
Thank you

Sounds like you wiped your EFS partition without backing it up first
Phone is dead if that is the case
Some people have had success backing up another S5 EFS, then restoring it to the dead phone
Otherwise, take it to a repair shop, next time backup before messing about

*Detection* said:
Sounds like you wiped your EFS partition without backing it up first
Phone is dead if that is the case
Some people have had success backing up another S5 EFS, then restoring it to the dead phone
Otherwise, take it to a repair shop, next time backup before messing about
Click to expand...
Click to collapse
Thank you Detection for your answer. So where can i find another S5 EFS, and how can i restore it.
Help me Please because i tried already to take it to a repair shop but they don't know how to fix it, that's why I wanna try to repair it myself, and i think its one of the repair shops who wiped the EFS partition without making a backup (because i give to 3 repair shops and they don't know how to fix it).

You'll need another S5, no-one here will give you their EFS backup as it is specific to their S5
A trusting friend / family member or an old 2nd hand S5 if you can find one, is your only choice

*Detection* said:
You'll need another S5, no-one here will give you their EFS backup as it is specific to their S5
A trusting friend / family member or an old 2nd hand S5 if you can find one, is your only choice
Click to expand...
Click to collapse
There is no other solution like flashing the PIT file using Odin and reinstate the stock rom or any other solution !

Nope, not if you've deleted the EFS partition - that contains the IMEI and Radios

Ok thank you, ill try to contact samsung after sales service.

Hi everybody,
I have same issue:
I needed to update SU-binaries and tapped accidentally on CWM/TWRP-Mode instead of normal. After this IMEI is null, Service Mode blank, sudden reboots and unable to install any Apps (always saying no free memory). uninstalling App causes reboot.
I have efs backup made with (PhilZ Touch) CWM, but I'm not able to fix the problem with it.
What I tried:
flashing Stock ROM + updating Bootloader in Odin
this Guide (except Samsung Tool and Terminal Emulator steps, as I can't install any App)
CWM script
I really don't know what else I can do. Does anybody have some other ideas?
Also backing up is not possible, now. EFS Professional says specified PIT file does not exist, even when I choose all partitions.

FIXED. Possible solution.
Fixed. Went to a shop to repair IMEI/EFS.
It seems there is something called "IMEI NV Generator", this should also do the magic and would have saved me some money.

samsung S5 Imei Proplem
zicozack said:
There is no other solution like flashing the PIT file using Odin and reinstate the stock rom or any other solution !
Click to expand...
Click to collapse
I have the same problem after trying to change the original IMEI>>> any help please

Please take a look here and here.

Galaxy s5 Backup puts me on bootloop [NEED FILES INSIDE]

Hello so I flashed a rom and it decided to put me in a bootloop after trying everything couldnt fix it and i really didnt want to lose a chance of getting my pictures back etc so i made a backup even though i had a bootloop so i then restored and flashed rom again and was fresh again, Then tried restoring to the backup and went to a bootloop again which i expected is there any way to get my files back really need the pictures sentimental value..
Im sorry if whatever i said or did is not smart I checked everywhere but couldnt find a direct solution so wanted to try here. Thanks in advance!

if you changed bootloader & Modem then try stock bootloader & Modem.

Verizon note 4 efs folder inaccessible

Hi all, as the title says, my efs folder is inaccessible. Firstly let me explain. I bought a phone, it had the Paul pizz rom in it and I didn't like it. So I flashed the resurrection remix rom. It didn't have all the bells n whistles I wanted, so I tried the official res remix rom. Somehow I ended up with an efs problem. I ended up with an efs invalid argument error and from what I read, I did the whole adb efs fix. The error was gone. I ended up flashing a repair firmware back to bog5 and started from scratch. I worked my way back up to installing the modest rom and it works 99% flawlessly and I am happy enough to keep it. Here is the catch, I used kingo root and have ended up with a bad keyboard lag that's driving me nuts. It is unknown to me if the kingoroot caused the efs corruption or if it was just a bad flash going from one rom to another. I have tried several root browsers, made sure they all had root privileges, and no matter what, I can NOT get access to what's hidden in my efs folder. They always say it's empty. Now, here is the kicker, I got another note 4 for my son. Downgraded from 6.01 to 5.01 bog5, then up to 5.11 and flashed the modest rom on his. Instantly his phone has access to the efs folder. My note 4 works, can make calls, text etc. Imei is shown in settings, all info shows in settings as normal except one thing, on my phone it says configuration version not available whereas on my sons phone it gives a configuration version. I just can't figure out how to gain access to the efs folder to try to fix this extremely annoying lag. I DID make a complete backup of my system from when it had the Paul pizz rom, so the efs partitions should be intact there but I don't know if that would help or even where to start. Can someone please help?

Well, I just fixed my phone and thought I would share what happened. It seems that the guy that loaded the paulpizz rom on the phone before I bought it used a different version of twrp. He used a version for n910f, whereas when I began my rom search, I used one for a n910v because thats what the phone is. I was having a hard time with it so I reverted to stock, rooted, installed verizon twrp, and bam! No efs access. The difference in recovery programs is what screwed me up in the first place. I figured it out when I tried to restore his rom backup I made. The efs files were not working when it restored. I remembered what version of rom it was, and tried a twrp for 910f, and voila! So, now I have all functions working as blazing speeds, can actually access the efs folder, and no more damned lag! Big thumbs up button to me!

Corrupted EFS / IMEI is Null / Unknown Bassband

Hey!
I attempted to root my phone for the first time yesterday and after a lot of trial and error, managed to flash magisk and start the phone without anything breaking. But I was really, really dumb and forgot to actually move the backup I took off TWRP and onto my PC before I ****ed up the first time and had to reset everything. And now I don't have a functioning IMEI / Wifi / Bassband etc. I know the correct IMEI of my phone but can't find a way to flash it or any of the other things onto my phone.
Anyone been through something similar? Or am I **** out of luck?

This thread will give you the answers although it's for Moto g5 plus...
https://forum.xda-developers.com/g5-plus/how-to/fix-persist-resolve-imei0-explanation-t3825147

Korrac said:
Hey!
I attempted to root my phone for the first time yesterday and after a lot of trial and error, managed to flash magisk and start the phone without anything breaking. But I was really, really dumb and forgot to actually move the backup I took off TWRP and onto my PC before I ****ed up the first time and had to reset everything. And now I don't have a functioning IMEI / Wifi / Bassband etc. I know the correct IMEI of my phone but can't find a way to flash it or any of the other things onto my phone.
Anyone been through something similar? Or am I **** out of luck?
Click to expand...
Click to collapse
Flash stock using the guide here in xda

The data roaming problem on Zenfone 3

Hey there folks,
here I am now too on the forum, trying to find a solution for an old sticky problem.
So far a some people here on the forum a while ago have had the problem that when they flashed a custom OS on their Zenfone 3 while data roaming was turned off in the stock rom, they could never get it working unless reverting back to the stock OS and switching it on there before reinstalling the custom OS. Until then only normal calls and SMS work.
I'm having the same problem now and trying to avoid going back to stock, so I wonder if somebody has found another solution by now? Any help would be really appreciated, and I think a lot of other EU people who will run into this problem in the future will be grateful too if this could be solved easier somehow :fingers-crossed:

Update: I took a look at the firmware partition and there is a folder image/modem_pr which seems to include the configuration how the phone connects to mobile networks. I don't claim to have any special knowledge about it but i would expect this is where the stock rom most probably makes its change about data roaming.
So maybe, as long as what the firmware partition contains is generic firmware, could somebody who has data roaming working on their Zenfone3 send a copy of their /firmware/image folder so I can compare the two and hopefully find the missing puzzle piece to get data roaming working?
I would of course post the solution here for everyone in case I figure it out! Would be great if we can solve it

I have the same problem. Please help.

So, here's an update:
After going crazy searching for a possible fix I gave up yesterday and re-installed the stock rom in order to turn on data roaming (since my TWRP backup won't boot that is something I had been trying to avoid, because the only way I found to do this was to either install a recovery from somewhere on the internet that is claimed to be the original Asus recovery but has no way to be integrity-checked for possibly including malware, or to install software designed to bypass Google's SafetyNet and other system integrity checks. Nah.)
Today I took a look at comparing a TWRP backup of the modem partition (contents identical to the one that mounts as "firmware"), and the persist partition. I wrote a script that would calculate the md5 checksum for each file and then compare for any changes.
On the modem partition, only binary files named Widevine changed, for whatever reason :silly:
And here is a list of the files that were changed on the persist partition:
persist/coresight/qdss.functions.sh
persist/coresight/qdss.log
persist/coresight/qdss.log.old
persist/data/gxflag
persist/data/gxfp/0_0/105885283
persist/data/gxfp/0_0/105885284
persist/data/gxfp/0_0/gxfeature_table
persist/data/gxfp/0_0/gxfeature_table
persist/data/gxfp/0_0/gxflag
persist/data/gxfp/1_0/gxfeature_table
persist/data/gxfp/1_0/gxflag
persist/data/gxfp/calibration_data
persist/data/gxfp/calibration_data
persist/data/gxfp/gxflag
persist/data/gxfp/mptest/gxflag
persist/data/gxfp/raw/0_0/gxflag
persist/data/gxfp/raw/0_0/tpl_index_table
persist/data/gxfp/raw/1_0/gxflag
persist/data/gxfp/raw/1_0/tpl_index_table
persist/data/ifaa_fplist
persist/data/ifaa_fplist
persist/data/widevine/UZT8uT7lR1wsAoECBZWk4+aPFLDG92yRsy5vX3eX
persist/data/widevine/UZT8uT7++lR1wsAoECBZWk4+aPFLDG92yRsy5vX3eX.bak
persist/data/widevine/widevine
persist/dmclient/dm_client_info
persist/dmclient/dm_client_token
persist/dmclient/hash_sn
persist/rfs/msm/mpss/server_check.txt
persist/rfs/shared/server_info.txt
persist/sensors/error_log
persist/sensors/sensors_settings
persist/sensors/sns.reg
persist/time/ats_1
persist/time/ats_12
persist/time/ats_13
persist/time/ats_15
persist/time/ats_16
persist/time/ats_2
persist/.twrps
persist/sensors/sns.reg
persist/time/ats_1
persist/time/ats_12
persist/time/ats_13
persist/time/ats_15
persist/time/ats_16
persist/time/ats_2
Unfortunately, mostly binary files making it impossible for me to dig deeper into the changes. But maybe somebody spots something odd that could lead to the solution.
My next step will be to go abroad again in early March and see if the data roaming now works. If it does, I will restore a TWRP backup of all partitions I could back up before returning to stock. If it still works then, then the stock rom made its change somewhere on one of the partitions TWRP does not back up. If it stops working, then the answer lies hidden somewhere on the TWRP-backuped partitions.
Either way, I'm sure there must be a manual solution, what happens on the stock rom cannot be black magic
Will keep you updated.

Alright, it's the 1st of March and I'm back abroad! I finally have data roaming working and got a little further in my investigation: Restoring partitions one by one, i figured out that the change by the stock concerning the data roaming is made somewhere on the efs partition (which one of the two I can't say yet, as TWRP only lets me restore them both together). Now I haven't succeeded yet how to mount the efs.emmc TWRP backup or otherwise dump the contents of the efs partition, but if someone here knows I'll go dig deeper and track down the specific entry that is changed

Can you tell how to restore the original partition without flashing the asus rom? Thanks

If you ever had data roaming working and created a Nandroid (TWRP) backup at the time, you can simply restore the efs partitions from back then. Just be sure to use the latest TWRP version and make a fresh backup before you go, as there used to be a version some time ago that corrupted efs partition backups.
If you don't, well, as long as I can't read out my efs I can't tell you what to modify in there and how Maybe somebody

I think my only option is to flash the original Asus rom. It is waste time if only to turn on the data roaming.