Hello there,
Recently I was on one of the custom ROMS and I wanted to go back to stock. The stock firmware I downloaded was for G965F Indian region but somehow it still erased my IMEI.(all zeros) I tried few documentations and guides here on XDA and messed up my EFS as well. KG STATE in boot-loader mode has gone to 'prenormal' so I can't install twrp and phone is also not booting anymore as EFS partition is corrupted. I tried flashing many stock firmware's but none of them got flashed.
Does anyone has idea how to fix my phone. All your help will be much appreciated. I know combination file could fix this but right now I'm on android 10 and there's no combination file for that released yet. Can anyone give me EFS backup? or does anyone have any solution? Please help !
fyi: "SM-G9965F_G965FXXSBETH2_Q(Android10)_INS_Factory ROM(5 File)_20200915" is the only firmware that is getting flashed with odin. I got it from Samfirm. But phone doesn't boot because EFS partition is corrupted.
Thanks,
Andromuks
Combination files are out ?
andromuks said:
Hello there,
Recently I was on one of the custom ROMS and I wanted to go back to stock. The stock firmware I downloaded was for G965F Indian region but somehow it still erased my IMEI.(all zeros) I tried few documentations and guides here on XDA and messed up my EFS as well. KG STATE in boot-loader mode has gone to 'prenormal' so I can't install twrp and phone is also not booting anymore as EFS partition is corrupted. I tried flashing many stock firmware's but none of them got flashed.
Thanks,
Andromuks
Click to expand...
Click to collapse
Hey guys, I'm recently seeing these files floating 'https://support.halabtech.com/index.php?a=downloads&b=file&id=332402' . Could this help for those memebers who have recently updated to Android 10 and has broken their IMEI?
Related
Hi all,
So now after being a passive but reading 'member' for a long while now, i finally managed to dig myself a hole deep enough not to be able to climb out on my own. So that's me registered now, and typing my first post asking for your help.
I have a GT-i9300 bought in Germany, brand free.
- It was still stock FW, and recently received the stability update released for 4.1.2
- I flashed it to "Android Revolution HD 32.0 (Android 4.2.1) using the infamous "mod manager" and "CF-Auto-Root-m0-m0xx-gti9300"
- This corrupted my or changed the format of my EFS folder in the process
- The EFS backup made during this process is not being accepted and phone is stuck in the factory mode
- I tried flashing the emergency.zip modem found on this forum to no avail
- I tried flashing back to the original stock, however i forgot to write down my starting point and thus not sure what to put in. (dailing *#1234# only gives you what is currently flashed)
- I had high hopes flashing I9300XXDLIH_I9300DBTDLI2_DBT (tried also others) but again no luck, even after trying to restore my backup EFS with Ktool.
- also tried: I9300XXEMG4_I9300DBTEMG3_I9300XXEMG4_HOME
So in my understanding there are only a few options available to bring my device back to fully function:
1 - Bring it to a repairshop that had a z3x box to put the EMEI back in.
2 - Reset the flashcounter, stock FW and try claim warranty (though i doubt Samsung will fall for it), and what FW to put in ?
3 - Somehow inject the IMEI to the phone with some of the available tools like "NV-items_reader_writer" or "qpst"
So before i manage to brick my device, i would appriciate any help from the specialist called YOU what of the above methods left to try should i go with, or is there another method i'm overlooking ?
Flashing the MG4 rom wasn't a good idea. You already had EFS issues. Your problem wasn't MG4 related in the first place so also not related to the solution. Same reason the "emergency zip" didn't do anything.
You could try manually putting the EFS backup in place using root explorer (etc)
rootSU said:
Flashing the MG4 rom wasn't a good idea. You already had EFS issues. Your problem wasn't MG4 related in the first place so also not related to the solution. Same reason the "emergency zip" didn't do anything.
You could try manually putting the EFS backup in place using root explorer (etc)
Click to expand...
Click to collapse
Thanks for the reply,
Yes after reading further into the problem i started to realize that too, but by then it was already to late.
Last time trying to copy\paste the files from my backup to the EFS folder using root explorer gave me a 'read only error'. Will however give it another go right now.
kamaradski said:
Thanks for the reply,
Yes after reading further into the problem i started to realize that too, but by then it was already to late.
Last time trying to copy\paste the files from my backup to the EFS folder using root explorer gave me a 'read only error'. Will however give it another go right now.
Click to expand...
Click to collapse
Yeah, you need to make sure you have permissions to write to the folder.
Getting closer, but not yet there...
- Used another root browser
- managed to delete the EFS, but was not able to write anything in it.. :S
- Used Ktool to recover backup
- However did see that this recovery created another efs sub-folder...
- Re-packed the content from my efs backup file, in a new tar.gz with 7zip this time making sure no subfolder was present.
- restored with Ktool and after reboot atleast i'm out of the 'factory safemode'!!!
However still invalid EMEI
As i have XXDLID, i guess i have to get another modem in ?
EDIT:
Now the phone is out of the safemode, Kies was able to update the device to PDA: MG4 + CSC: MG3 (DBT)
After reboot, IMEI was recognized again and phone is working normally !! Thank you all.
Next step, see if i can still upgrade to 'Android Revolution 32.0', without touching the modem.
Thanks again all, sending me on the right track !!
kamaradski said:
Getting closer, but not yet there...
- Used another root browser
- managed to delete the EFS, but was not able to write anything in it.. :S
- Used Ktool to recover backup
- However did see that this recovery created another efs sub-folder...
- Re-packed the content from my efs backup file, in a new tar.gz with 7zip this time making sure no subfolder was present.
- restored with Ktool and after reboot atleast i'm out of the 'factory safemode'!!!
However still invalid EMEI
As i have XXDLID, i guess i have to get another modem in ?
EDIT:
Now the phone is out of the safemode, Kies was able to update the device to PDA: MG4 + CSC: MG3 (DBT)
After reboot, IMEI was recognized again and phone is working normally !! Thank you all.
Next step, see if i can still upgrade to 'Android Revolution 32.0', without touching the modem.
Thanks again all, sending me on the right track !!
Click to expand...
Click to collapse
Hey - I think I just spent the last 24 hours doing exactly what you did.. I got out of factory mode. But your last statement "Kies was able to update the device to PDA: MG4 + CSC: MG3 (DBT)" - what did you do exactly? oddly I have a UK phone (BTU) but it is registered in Germany so connects to Vodafone (if only the EMEI were not empty!). I came from flashing Ultimarom v14.0.1 and since then it will not do anything with the modem. So I have a phone that cannot phone...
Any pointers on what you did in the last sentence would be good!! I am getting desperate
biffaxda said:
Hey - I think I just spent the last 24 hours doing exactly what you did.. I got out of factory mode. But your last statement "Kies was able to update the device to PDA: MG4 + CSC: MG3 (DBT)" - what did you do exactly? oddly I have a UK phone (BTU) but it is registered in Germany so connects to Vodafone (if only the EMEI were not empty!). I came from flashing Ultimarom v14.0.1 and since then it will not do anything with the modem. So I have a phone that cannot phone...
Any pointers on what you did in the last sentence would be good!! I am getting desperate
Click to expand...
Click to collapse
Any news I am in the exact same boat. ((
Imei 004999901...
danihassanein said:
Any news I am in the exact same boat. ((
Click to expand...
Click to collapse
Nope. In fact i found an old laptop with an EFS backup on it (galaxy toolkit skipsoft) so i thought i was saved. I restored /efs or /factory and also efs partition but no matter what i do (even root explorer cut n paste the whole /efs folder from backup, or the 9 steps someone else logged) it always reboots with the dummy IMEI number. i have no clue how to progress. wondering if a samsung service repair is more expensive than a UART cable and box...
i think it comes back to the original comment by kamradski:
So in my understanding there are only a few options available to bring my device back to fully function:
1 - Bring it to a repairshop that had a z3x box to put the EMEI back in.
2 - Reset the flashcounter, stock FW and try claim warranty (though i doubt Samsung will fall for it), and what FW to put in ?
3 - Somehow inject the IMEI to the phone with some of the available tools like "NV-items_reader_writer" or "qpst"
[
i think it comes back to the original comment by kamradski:
So in my understanding there are only a few options available to bring my device back to fully function:
1 - Bring it to a repairshop that had a z3x box to put the EMEI back in.
An IMEI repair is relatively cheap .
Hey guys,
Sorry in advance for what is no doubt something that's came up a few times in the past (as is clearly evident by the posts). I've spent a long time trying to get around the issues with this thing so hopefully I can explain what I've done so far which might help.
So, basically -
My brother had an S3. The screen broke (glass only) and he asked me to repair it. This was a few months ago. Inbetween he moved to using a Windows phone and had the S3 sitting around until he eventually decided to hand me it to repair a couple of days ago.
Now, the phone was working flawlessly prior to him turning it off and switching over to the Windows phone. The S3 sat dormant for a few months, battery out.
When I went to turn it on to test the screen and buttons to ensure that's the only fault, it wouldn't get past the boot screen.
No huge deal there.
Upon checking in recovery it was unable to mount the EFS partition. I managed to get round that.
It still wouldn't boot, so I flashed a new ROM and it booted up fine however was in "Factory mode" with IMEI starting 0049.
I've done a fair amount of searching and came to a few conclusions but essentially :
How I don't know but his EFS folder was competely corrupt and essentially contained few files, none of which were IMEI related. I have no clue how this has happened but it has.
I've managed to get the phone working ALMOST flawlessly by restoring a stock EFS backup IMG using kTool, I HAVE the phone's IMEI and serial which are printed on the phone itself. Only issue now is that the phone can't connect to any networks - because the IMEI is a default.
So, I've dug around in the stock EFS backup IMG that I was able to find (which has got the phone working great, minus mobile networks) and found that the IMEI folder contained a file "mps_code.dat". Upon opening this file it's basically empty. I assume this is because it's a stock EFS I located.
Does anyone have any clue how I can input the IMEI into this file? I tried to decompile the IMG, type it into the file and save, then recompile the IMG however kTool doesn't recognise the newly created IMG file and crashes, then restores the phone. Is there a specific tool I should be using to make the IMG and can someone root into their "mpd_code.dat" and tell me the format that it needs to be in? (I don't need or want any IMEI numbers, just the format that the file is. Just open it in a text editor through Root Explorer (root\efs\imei) and star out the IMEI if you can).
Just to clarify before anyone jumps on it - I'm NOT looking for the file(s) OR the IMEI numbers on anyones phone with that request. Simply the format in which it should be in. I'm simply trying to put the IMEI for the phone ONTO the phone so it'll recognise networks and work as it should. Everything else is absolutely fine now.
So just to clarify the options I've boiled down to :
Recompile the efs.img with the correct IMEI within - if someone can tell me how that'd be great - then restore it on kTool.
OR
Edit the on-phone mps_code.dat with the correct IMEI but I need the format (if someone could peek at theirs that'd be great).
Thank you in advance all and sorry for the story! If I manage to get this to work I'll upload a tutorial with all the relevent files required which I know will help a lot of people.
Cheers
Mine mps_code.dat have 3 letters in it i-e 'TNL' which is csc i think. And imei is in efs1 and efs2 partition you can see in pit analysis thread google it if you don't know anout this thread.
Only thing which you can do is give phone to repair shop they have boxes and tools which can write imei. Or take backup of efs1 efs2 and efs of other phone and restore it in your phone.you do backup/restore using partition backup app in playstore by wanam.
Thanks for your reply. I will try to locate someone else I know with an S3 and pull their EFS - hopefully something will happen that's of benefit.
In the meantime, I'll focus on this as hard as I can to get it sorted. I've managed to go from having the IMEI reading as a random 0049 one, to "Null/Null" which means it HAS been written to (or does in my mind), just with nothing rather than the correct number.
If I get anywhere I'll update this thread, and if im successful in the repair I'll create a How-To based on what I did.
Cheers
I can repair your device. Had the same problem with my mothers phone.
The problem is that samsung changed the style of the efs format years ago and the S3 was falling in this time.
So if you need help, i can help.
konsolen said:
I can repair your device. Had the same problem with my mothers phone.
The problem is that samsung changed the style of the efs format years ago and the S3 was falling in this time.
So if you need help, i can help.
Click to expand...
Click to collapse
Hey mate,
Want me to PM you?
Thanks
I had the same problem days ago and I couldn't connect to sim network.
What I did was flash stock rom using odin and then a custom modem and a custom kernel I found in the internet. At the end it gave me a normal imei number (not the [email protected]%) but it wasn't my original imei... nevertheless it can connect now without any issues .
jairolas said:
I had the same problem days ago and I couldn't connect to sim network.
What I did was flash stock rom using odin and then a custom modem and a custom kernel I found in the internet. At the end it gave me a normal imei number (not the [email protected]%) but it wasn't my original imei... nevertheless it can connect now without any issues .
Click to expand...
Click to collapse
Hey bro,
Do you remember specifically what ROM, kernel and modem you flashed? Ive tried this with no luck so interested in trying your combination.
Cheers
Ok guys this is exactly what I did:
1- backup all your data.
2- download a stock 4.3 jellybean rom from sammobile (I used the Trinidad and Tobago version because I live in Mexico but that shouldn't matter), autoroot cf for i9300 4.3 from their website and twrp 2.8 recovery, again from their website.
3- download this especial kernel and this modem:
https://www.dropbox.com/s/4cawyqzg8zo1vot/Patched_XXUGMK6_kernel.zip.zip?dl=0
https://www.dropbox.com/s/tky93zds14kt1hz/Patched_XXUGMK6_modem.zip.zip?dl=0
4- Proceed to flash stock 4.3 rom using odin 3.07.
5- After stock rom is installed flash the root cf file and recovery tar using odin.
6- Now that you have a rooted stock rom with custom recovery proceed to flash both the especial kernel zip and the modem zip using twrp recovery.
7- You should now be able to connect network.
Good luck.
jairolas said:
Ok guys this is exactly what I did:
1- backup all your data.
2- download a stock 4.3 jellybean rom from sammobile (I used the Trinidad and Tobago version because I live in Mexico but that shouldn't matter), autoroot cf for i9300 4.3 from their website and twrp 2.8 recovery, again from their website.
3- download this especial kernel and this modem:
https://www.dropbox.com/s/4cawyqzg8zo1vot/Patched_XXUGMK6_kernel.zip.zip?dl=0
https://www.dropbox.com/s/tky93zds14kt1hz/Patched_XXUGMK6_modem.zip.zip?dl=0
4- Proceed to flash stock 4.3 rom using odin 3.07.
5- After stock rom is installed flash the root cf file and recovery tar using odin.
6- Now that you have a rooted stock rom with custom recovery proceed to flash both the especial kernel zip and the modem zip using twrp recovery.
7- You should now be able to connect network.
Good luck.
Click to expand...
Click to collapse
Thanks bro, will try that in the morning!
Hey mate,
I started the process of this today, using a stock samsung FW that I updated to using Kies.
Unfortunately the end result is the same, 0049 IMEI number.
What I'll do is I'll download the T&T 4.3 from Sammobile and see if that makes any difference.
Thanks again,
jairolas said:
Ok guys this is exactly what I did:
1- backup all your data.
2- download a stock 4.3 jellybean rom from sammobile (I used the Trinidad and Tobago version because I live in Mexico but that shouldn't matter), autoroot cf for i9300 4.3 from their website and twrp 2.8 recovery, again from their website.
3- download this especial kernel and this modem:
https://www.dropbox.com/s/4cawyqzg8zo1vot/Patched_XXUGMK6_kernel.zip.zip?dl=0
https://www.dropbox.com/s/tky93zds14kt1hz/Patched_XXUGMK6_modem.zip.zip?dl=0
4- Proceed to flash stock 4.3 rom using odin 3.07.
5- After stock rom is installed flash the root cf file and recovery tar using odin.
6- Now that you have a rooted stock rom with custom recovery proceed to flash both the especial kernel zip and the modem zip using twrp recovery.
7- You should now be able to connect network.
Good luck.
Click to expand...
Click to collapse
yetep said:
Hey mate,
I started the process of this today, using a stock samsung FW that I updated to using Kies.
Unfortunately the end result is the same, 0049 IMEI number.
What I'll do is I'll download the T&T 4.3 from Sammobile and see if that makes any difference.
Thanks again,
Click to expand...
Click to collapse
Hey hey,
Right unfortunately all of the above doesnt solve any issues im having with the IMEI.
What I'm ultimately trying to do is find out a way to fix this, without having to use third-party hardware or a samsung service station.
The real reason is that I don't think the average user should have to go that extent to fix this - it's ultimately Samsung's fault.
Android is designed to be customisable allowing users to go up/down versions as they please (provided it's compatible with the hardware of their phone).
Just a thought -
is there any possible way to "bake" the old style EFS into a newer rom?
yetep said:
Hey mate,
I started the process of this today, using a stock samsung FW that I updated to using Kies.
Unfortunately the end result is the same, 0049 IMEI number.
What I'll do is I'll download the T&T 4.3 from Sammobile and see if that makes any difference.
Thanks again,
Click to expand...
Click to collapse
Hey All (that are viewing this).
The above procedure didn't work. I have managed to get the IMEI to change from 0049 to NULL/NULL and back again at will using a blank EFS restore file that I've got, however can't figure out what and how to change the files WITHIN the EFS restore to the correct IMEI etc.
I'll continue my search and if I come across anything, I'll let you all know on here and create a How-To.
Cheers
Hey all - just a quick question on this.
Does anyone know how to modify the server to which a program points to check for user credits etc? There's clear reason I'm asking for this, however for obvious reasons I won't elaborate further right now.
Cheers
Hello there! Is the problem fixed? Couple of days ago i fixed someones i9300 whos having this kind of error. Pm me ill help
lyxtian said:
Hello there! Is the problem fixed? Couple of days ago i fixed someones i9300 whos having this kind of error. Pm me ill help
Click to expand...
Click to collapse
I have sent you a pm.
konsolen said:
I can repair your device. Had the same problem with my mothers phone.
The problem is that samsung changed the style of the efs format years ago and the S3 was falling in this time.
So if you need help, i can help.
Click to expand...
Click to collapse
I have a samsung galaxy s7 sm-G930F which is bricked. no imei anymore and no efs backup. can u help me fix it?
Phones specs:
MODEL: [GT-I9100GSMH]
S/N: [RF1C27N3LQA]
ORIGIN COUNTRY: [MADE IN VIETNAM]
Rooted.
STOCK recovery.
Firmware before soft brick: unknown, probably latest stock.
Situation shortly:
My IMEI got wrecked somehow(only 1 digit away from the original) and I was searching for methods on how to get it back to the original one. I rooted the phone and removed EFS folder through root explorer using some kind of a guide(10th in a row) and it resulted in a freeze ----> permanent boot for me. Before removing the EFS I just made an archive out of it and sent to my gmail so it seems that I have kind of a backup. I was trying to just flash STOCK but I searched for hours(maybe I am that bad at searching) but I didn't find one where it would say it is exactly for my GT-I9100GSMH. Also I am not sure how do I restore EFS on a phone that won't go farther that boot if that is the solution too. I also have adb installed if it is needed as well as odin, kies, drivers and everything else.
I would really appreciate any help or suggestions in this thread as I don't know what to do, I've tried myself for long enough and didn't succeed sadly.
Thanks in advance!
DedToto said:
Phones specs:
MODEL: [GT-I9100GSMH]
S/N: [RF1C27N3LQA]
ORIGIN COUNTRY: [MADE IN VIETNAM]
Rooted.
STOCK recovery.
Firmware before soft brick: unknown, probably latest stock.
Situation shortly:
My IMEI got wrecked somehow(only 1 digit away from the original) and I was searching for methods on how to get it back to the original one. I rooted the phone and removed EFS folder through root explorer using some kind of a guide(10th in a row) and it resulted in a freeze ----> permanent boot for me. Before removing the EFS I just made an archive out of it and sent to my gmail so it seems that I have kind of a backup. I was trying to just flash STOCK but I searched for hours(maybe I am that bad at searching) but I didn't find one where it would say it is exactly for my GT-I9100GSMH. Also I am not sure how do I restore EFS on a phone that won't go farther that boot if that is the solution too. I also have adb installed if it is needed as well as odin, kies, drivers and everything else.
I would really appreciate any help or suggestions in this thread as I don't know what to do, I've tried myself for long enough and didn't succeed sadly.
Thanks in advance!
Click to expand...
Click to collapse
Try this comprehensive guide for IMEI/EFS backup/restore
forum.xda-developers.com/showthread.php?t=1852255
Sent from my SCH-I535 using Tapatalk
hi guys,
recently i had a problem with nvram partition on my henessy and i had lost my imei also,so what can i do is only flashing custom rom from twrp,root it,and restore my imei (otherwise i will always lose my signal on sim 1 so i only be able to use sim 2) but couple of these days i feel unsatisfaction of any other custom rom so i desperately need backup of stock rom in twrp.i really felt grateful if someone would help me with this problem. because if i flash directly from fastboot or spflash i will revert back with locked bootloader and stock recoveries,which means i cant flash Super User inorder to get my device rooted and get back my imei.
Thanks mod and xda
galuh said:
hi guys,
recently i had a problem with nvram partition on my henessy and i had lost my imei also,so what can i do is only flashing custom rom from twrp,root it,and restore my imei (otherwise i will always lose my signal on sim 1 so i only be able to use sim 2) but couple of these days i feel unsatisfaction of any other custom rom so i desperately need backup of stock rom in twrp.i really felt grateful if someone would help me with this problem. because if i flash directly from fastboot or spflash i will revert back with locked bootloader and stock recoveries,which means i cant flash Super User inorder to get my device rooted and get back my imei.
Thanks mod and xda
Click to expand...
Click to collapse
http://en.miui.com/forum.php?mod=viewthread&tid=299779&highlight=IMEI+restore
not working
Capt. John Yossarian said:
http://en.miui.com/forum.php?mod=viewthread&tid=299779&highlight=IMEI+restore
Click to expand...
Click to collapse
my device is redmi note 3 mediatek so it is not possible to repair it using qspt which is for quallcom only,but thanks anyway
Kindly i need a help for this, i have a KII-L21 phone model, i flashed a custom rom then wanted to go back to the stock rom, i followed a guide here that mentioned to restore from TWRP, i did so but the simm didn't want to work and i wasn't able to flash TWRP again or unlock the bootloader as the serial no. of the phone changed so it didn't match with the IMEI also the update from the settings didn't install, can some one help please to solve that issue
No one here to reply!!!! where are the huawei developers or experts kindly help
hazemnada said:
Kindly i need a help for this, i have a KII-L21 phone model, i flashed a custom rom then wanted to go back to the stock rom, i followed a guide here that mentioned to restore from TWRP, i did so but the simm didn't want to work and i wasn't able to flash TWRP again or unlock the bootloader as the serial no. of the phone changed so it didn't match with the IMEI also the update from the settings didn't install, can some one help please to solve that issue
Click to expand...
Click to collapse
R u on stock recovery...
Yes i'm on stock recover.
Let me tell u exactly what happened i restored a backup that was here for my phone and i checked that the backup is for my region, when i restored it asked me for the puk code i entered it but it didn't want to accept, then i checked again the version from about the phone it was correct and it informed me from the updater that there is an update i downloaded but it told me installation failed i then tried to factory reset from both the phone and the recover it did but also everything was the same, so i tried to flash TWRP denied even tried the dload method installation failed also, at the i discovered that the bootloader is locked so i had the lock key and it told me incorect then i discovered that when connecting with ADB it gives a serial number different than mine although when i check through the phone the serial number is my old one. Now i'm stuck and don't know what to do
why no one here replies where r the experts here
hazemnada said:
Yes i'm on stock recover.
Let me tell u exactly what happened i restored a backup that was here for my phone and i checked that the backup is for my region, when i restored it asked me for the puk code i entered it but it didn't want to accept, then i checked again the version from about the phone it was correct and it informed me from the updater that there is an update i downloaded but it told me installation failed i then tried to factory reset from both the phone and the recover it did but also everything was the same, so i tried to flash TWRP denied even tried the dload method installation failed also, at the i discovered that the bootloader is locked so i had the lock key and it told me incorect then i discovered that when connecting with ADB it gives a serial number different than mine although when i check through the phone the serial number is my old one. Now i'm stuck and don't know what to do
Click to expand...
Click to collapse
Which firmware number you tried via dload??
hassanjavaid8181 said:
Which firmware number you tried via dload??
Click to expand...
Click to collapse
first i restored the backup in the Repository that mentioned my phone model
GR5 KII-L21
GR5+TWRP+backup_KII-L21C185B130.rar Thanks to Under World
and it changed everything then