ENGBOOT for SM-G930F (UNTESTED): Probably False (not Tested on a device) - Samsung Galaxy S7 Questions and Answers

Hello everybody!
I was surfing through the web when i found this file uploaded on 4shared claiming to be an Engboot for SM-G930F.
Naturally, I was sceptical about this file, as I am completely uneducated about the nuts and bolts of Android, I could neither confirm or deny that this is a valid file or not, so I decided to post the link to XDA , so much more knowledgeable people can take a look at it and see if it is a valid file or not. I don't want to flash this file on (bought yesterday) my S7 Edge, so here I am!
If anybody is feeling brave enough to try this on their phone, please go ahead and tell if this worked or not
Disclaimer: I am not responsible in any way for bricked devices, this file is completely untested.
Original Link: [url]https://www.4shared.com/get/X3a35HZTba/SM-G930F-ENGBOOT-bay_MrTpO.html[/URL]
Zippyshare (no registration) Link: [url]http://www80.zippyshare.com/v/axSXOCtR/file.html[/URL]
Edit: This is important because if this file works, you could thereotically flash anything you want WITHOUT tripping knox.
Also you can easily unbrick your phone by flashing the stock ROM if it comes to that.

Noob you can test self on your phone. We are not your tester here.

Schrotty35 said:
Noob you can test self on your phone. We are not your tester here.
Click to expand...
Click to collapse
I'm sorry that I apparently did not make it clear in the original post, but I have a S7 EDGE not a S7, so flashing this would probably brick my phone and yield no good result. I made this thread so the community may possibly benefit from this.

and what is SM-G930F-ENG(BOOT)_BST.bsp??

KPOCAB4EG said:
and what is SM-G930F-ENG(BOOT)_BST.bsp??
Click to expand...
Click to collapse
Engineering Bootloader.
Sent from my G930F using Tapatalk

KPOCAB4EG said:
and what is SM-G930F-ENG(BOOT)_BST.bsp??
Click to expand...
Click to collapse
You saw that too! I saw that through WinRar , after searching through the web I saw that it is a Binary Space Partitioning file, I am currently searching the web to see how to open it.
Sent from my Samsung SM-G935F using XDA Labs

The Game said:
Engineering Bootloader.
Click to expand...
Click to collapse
Does this work?:fingers-crossed:
Sent from my Samsung SM-G935F using XDA Labs

The Game said:
Engineering Bootloader.
Click to expand...
Click to collapse
lol lol lol i google'd what is:
Best Smart Tools (BST) – Supported Models & Features:
#SAMSUNG / Support Models & Features:
Samsung features:
- Reading full information via ADB or MTP interface
- Safe and fast flashing – supported tar, md5, smd, img, bin, rfs etc files format.
- Remove screen lock w/o usb debugging, w/o root, don’t lost userdata (support re-lock).
- OneKey Recovery (support 4.3/4.4.2 remove screenlock don’t lost userdata)
- Unlock/Read all unlock codes.
- Samsung Qualcomm Direct Unlock (no need root, no need wipe efs, no original imei loss)
- Repair damaged IMEI, backup/restore SuperIMEI.
- Repair baseband unknown.
- Read/write EFS,NVM,PIT,QCN,Cert files
- Repair SN, Cal Date, BT Addr, WiFi MAC, Product Code, HW Version etc
- Auto try to root when operation need rooted
- Repair Boot SDCard – brick phone repair
- App2SD
- Factory reset
Click to expand...
Click to collapse
this is no Engineer Boot
main function for this app - unlock mobile network

KPOCAB4EG said:
lol lol lol i google'd what is:
this is no Engineer Boot
Click to expand...
Click to collapse
I am not sure what you mean by that, that is BST not BSP
Sent from my Samsung SM-G935F using XDA Labs

Random04 said:
I am not sure what you mean by that, that is BST not BSP
Click to expand...
Click to collapse
http://gsmbest.com/en/ShowProduct.asp?Id=4 and Go To "Update logs"
* About Samsung "Reset FRP Lock" patch files(*.bsp):
Click to expand...
Click to collapse
this is no boot and no from samsung

KPOCAB4EG said:
http://gsmbest.com/en/ShowProduct.asp?Id=4 and Go To "Update logs"
this is no boot and no from samsung
Click to expand...
Click to collapse
Thanks KPOCAB4EG, I was unsure about this myself too. :good:
Sent from my Samsung SM-G935F using XDA Labs

Alright, I just stumbled upon this. I'm assuming no one has tested this. From what I've read in post 8, is it safe to say that this file is *supposed* to fix the IMEI issue coming up as 000000000?
This might be what I need because my phone is giving me the following error in recovery
"dm-verity verification failed...
Need to check DRK first..."
Also as I mentioned above my IMEI is all 0's, which I'm assuming is caused by a faulty EFS partition.
No matter how many times I try to flash stock firmware through ODIN, I always end up in the same spot.

m0d hipp¥ said:
Alright, I just stumbled upon this. I'm assuming no one has tested this. From what I've read in post 8, is it safe to say that this file is *supposed* to fix the IMEI issue coming up as 000000000?
This might be what I need because my phone is giving me the following error in recovery
"dm-verity verification failed...
Need to check DRK first..."
Also as I mentioned above my IMEI is all 0's, which I'm assuming is caused by a faulty EFS partition.
No matter how many times I try to flash stock firmware through ODIN, I always end up in the same spot.
Click to expand...
Click to collapse
Hi,
This file is probably going to make your situation worse, you should follow this guide: https://forum.xda-developers.com/s7-edge/how-to/guide-how-to-fix-check-drk-imei-issues-t3379516 or alternatively make a new thread so people can properly help you.
Best of luck!:good:
Sent from my Samsung SM-G935F using XDA Labs

Thanks for the response. I have came across that thread and tried those steps, but it didn't help unfortunately. I have also tried several other things such as hex editing the EFS partition and using 3rd party tools to try and change the IMEI, but nothing seems to be working. My last resort might have to be going through Samsung Service Center.
The odd thing is that I have a SM-G930T, however according to my IMEI on here: http://www.imei.info, it's showing as SM-G930F which is confusing. IMEI is 357752072430049

m0d hipp¥ said:
Thanks for the response. I have came across that thread and tried those steps, but it didn't help unfortunately. I have also tried several other things such as hex editing the EFS partition and using 3rd party tools to try and change the IMEI, but nothing seems to be working. My last resort might have to be going through Samsung Service Center.
The odd thing is that I have a SM-G930T, however according to my IMEI on here: http://www.imei.info, it's showing as SM-G930F which is confusing. IMEI is 357752072430049
Click to expand...
Click to collapse
That IMEI checker will tell you your model number and then your exact variant in the brackets.
By the way, which third party tools/other methods have you tried?
Sent from my Samsung SM-G935F using XDA Labs

Random04 said:
That IMEI checker will tell you your model number and then your exact variant in the brackets.
By the way, which third party tools/other methods have you tried?
Sent from my Samsung SM-G935F using XDA Labs
Click to expand...
Click to collapse
The thing that's confusing is that SM-G930F and SM-G930T are 2 different models.
My phone, is a tmobile version, which should be SM-930T (snapdragon chipset), according to the IMEI checked with my IMEI it shows that it's SM-G930F which is an exynos chipset. This is what's confusin to me...
I tried flashing twrp on there using herolte, heroqltechn and heroqlte and none of them worked. I tried it through ODIN, I tried it through flashfire, I tried it through adbshell using the DD command and none of those methods worked.
As far as what I have tried regarding the DRK and IMEI fixes...
I have tried flashing the SM-G930T PK1 and PIA stock firmware and nothing fixed it.
I have tried restoring full backups I made (prior to having these issues) with flashfire, and I got it to boot, but then I got a error with it being able to decrypt my storage so it forced me to go into the stock recovery and wipe data\factory restore and wipe cache, after I did that the DRK and IMEI issue came back.
From what I've read it seems I need a custom kernel (which apparently isn't an option right now) for me to bypass the IMEI and DRK issue.
The other option I read was to write the certificate back to my phone. I asked if I am able to pull the cert from an old backup that I made, but was told that it's not possible to pull it from a backup.
I also tried taking the EFS.img file from an old backup (prior to these issues) and tried restoring it, and this didn't fix anything.
I tried taking EFS and hex editing the value into it, still nadda.
When I was desperate, someone mentioned using the PIT file from a stock tmobile firmware and using that to re-partition the phone as well as doing a NAND erase on the phone as well as an EFS clear and bootloader update, so I tried that and still nothing.
If anyone can provide any assistance it would be greatly appreciated, but I'm not sure what else to try. Unfortunately my options are somewhat limited by a locked bootloader.

Related

*REWARD -Tablet lost Imei and network after attempting root

I'll give as much info as i can and will REWARD whoever can help me with this situation!
I have experience with different samsung phones rooting through odin and others never having much issues. This is first attempt with a tablet fyi.
Samsung tab 2 lte edition from at&t i497 5100
Attempted http://forum.xda-developers.com/showthread.php?t=1957165
root method through odin and everything was going alright until halfway through it said failed. I then rebooted into download and attempted this version http://forum.xda-developers.com/showthread.php?t=2101044
This method seemed to work as i was able to boot into recovery cwm and go through the options. I then ran the supersu zip and verified that the appdrawer had it in there. things looked ok i thought. so now i was ready to download a rom. Attempted the most current CM10 nightly through recovery.- it failed giving me the status 7 error. i then went to the only post about status 7 in the all things tab 2 thread and attempted to download mobile odin but when i loaded the app it said not compatible with my device.
I then attempted to download a stock rom and remove root from phone because sometime in this all i lost the ability to use wifi and my imei showed missing in the settings. no attempt at unrooting seems to work because of the cwm not allowing me to use roms. I attempted to recover the nandroid i made the minute i "rooted" and its giving me the md5 sum error as well.
Please help!!
circa_rider said:
I'll give as much info as i can and will REWARD whoever can help me with this situation!
I have experience with different samsung phones rooting through odin and others never having much issues. This is first attempt with a tablet fyi.
Samsung tab 2 lte edition from at&t 5100
Attempted http://forum.xda-developers.com/showthread.php?t=1957165
root method through odin and everything was going alright until halfway through it said failed. I then rebooted into download and attempted this version http://forum.xda-developers.com/showthread.php?t=2101044
This method seemed to work as i was able to boot into recovery cwm and go through the options. I then ran the supersu zip and verified that the appdrawer had it in there. things looked ok i thought. so now i was ready to download a rom. Attempted the most current CM10 nightly through recovery.- it failed giving me the status 7 error. i then went to the only post about status 7 in the all things tab 2 thread and attempted to download mobile odin but when i loaded the app it said not compatible with my device.
I then attempted to download a stock rom and remove root from phone because sometime in this all i lost the ability to use wifi and my imei showed missing in the settings. no attempt at unrooting seems to work because of the cwm not allowing me to use roms. I attempted to recover the nandroid i made the minute i "rooted" and its giving me the md5 sum error as well.
Please help!!
Click to expand...
Click to collapse
I'm worried for you, in that you have corrupted your efs folder - did you make an efs backup? as far as i'm aware, you can only recover your efs if you have backed it up. good luck.
If it helps I am an At&t store manager, and i do have access to a identical tab that is about to be sent back from a return. I am scared though of corrupting that one and then being in a worse situation. If i knew i could create a backup that could be moved to my personal one i would do it. is that possible? I'm not familiar with an efs backup but am researching it to check now.
squ89r97 said:
I'm worried for you, in that you have corrupted your efs folder - did you make an efs backup? as far as i'm aware, you can only recover your efs if you have backed it up. good luck.
Click to expand...
Click to collapse
circa_rider said:
If it helps I am an At&t store manager, and i do have access to a identical tab that is about to be sent back from a return. I am scared though of corrupting that one and then being in a worse situation. If i knew i could create a backup that could be moved to my personal one i would do it. is that possible? I'm not familiar with an efs backup but am researching it to check now.
Click to expand...
Click to collapse
I'm not sure it would, as a store manager you will know imei numbers are specific to each device!...you could swap the tabs over, but I don't condone that
Did you by chance rename the backup after making it? That has caused me problems in the past.
Sent from my SPH-L900 using Tapatalk 2
circa_rider said:
Samsung tab 2 lte edition from at&t 5100
Click to expand...
Click to collapse
Sorry I can't help, but is this the 7" tab? I have the 10.1" tab 2 and my model number is i497... LTE edition.
I totally understand what you mean now, i wasn't thinking a backup would switch over the imei i just thought it would contain whatever identifiers needed not realizing it would have the actual number in that.. I used total commander to look into the root file and there is a efs folder with all the separate folders "bluetooth, wifi, and other folders".
patrao_n said:
Did you by chance rename the backup after making it? That has caused me problems in the past.
Sent from my SPH-L900 using Tapatalk 2
Click to expand...
Click to collapse
I did rename it when i was going through a fix for the md5 sum issue, i was going through adb and couldn't navigate to the folder so i did rename it... i cant imagine that the recovery would have an issue just because of that? i wouldn't be sure what to name it back to.
I wonder if Samsung has any option for me to send it in and get them to reboot the thing. This sucks!
circa_rider said:
I totally understand what you mean now, i wasn't thinking a backup would switch over the imei i just thought it would contain whatever identifiers needed not realizing it would have the actual number in that.. I used total commander to look into the root file and there is a efs folder with all the separate folders "bluetooth, wifi, and other folders".
Click to expand...
Click to collapse
There will be, but unforunately they are corrupt now. :crying:
I wonder if Samsung has any option for me to send it in and get them to reboot the thing. This sucks!
i'm pretty sure samsung has an option for you to send it in, but depending on what firmware your running/whether the flash counter has increased in download mode - your warranty would be void - or you may have to pay some $$$$ - they may even refuse. i don't know for sure though.
squ89r97 said:
There will be, but unforunately they are corrupt now. :crying:
I wonder if Samsung has any option for me to send it in and get them to reboot the thing. This sucks!
i'm pretty sure samsung has an option for you to send it in, but depending on what firmware your running/whether the flash counter has increased in download mode - your warranty would be void - or you may have to pay some $$$$ - they may even refuse. i don't know for sure though.
Click to expand...
Click to collapse
I appreciate you talking me through the different things, even if it doesn't fix my issue. I am probably going to call samsung to see but my flash counter is reset from triangle away and the firmware looks like it did before i ever rooted. but it says modified when i go to download mode so im sure they would know in a second that its my fault
circa_rider said:
I appreciate you talking me through the different things, even if it doesn't fix my issue. I am probably going to call samsung to see but my flash counter is reset from triangle away and the firmware looks like it did before i ever rooted. but it says modified when i go to download mode so im sure they would know in a second that its my fault
Click to expand...
Click to collapse
if the counter is at 0 it sounds like you still have root access, do you?
you could try flashing a stock firmware through odin , which ever came with the tab - 4.0.4??? get the firmware from sammobile.com - that may :fingers-crossed: get rid of the modified status.
---------- Post added at 05:20 PM ---------- Previous post was at 04:40 PM ----------
never thought to ask either - whats the *REWARD?
Try flash this jamaican firmware it works on at&t
http://www.hotfile.com/dl/189517896/ee3001a/I497UMAMA1_I497JDIAMA1_JDI.zip.html
mihaidenis said:
Try flash this jamaican firmware it works on at&t
http://www.hotfile.com/dl/189517896/ee3001a/I497UMAMA1_I497JDIAMA1_JDI.zip.html
Click to expand...
Click to collapse
You're missing the point! He has a corrupt imei number. He can flash that but still won't be able to get signal.
I had a simaler issue with my S3 (d2tmo) as well as many others. Qpst I believe is what I used to get the imei back. I had the links all save on the laptop but it died 3 moths back. (10 year old dell). http://forum.xda-developers.com/showthread.php?t=1801997 try that out see if it will help. I have some of the other stuff saved that I will upload to you. Search the issue on S3 (us variants) it could help.
Samsung Rocks!
Great news! Samsung had me send it in and they repaired it in less than 2 days of having it. their ticket email says this
Problem found: ESN corrupted
Solution: Replaced PBA
-- not sure what a pba is but they didn't charge me for the repair! I'm taking this as a gracious sign from above that i should leave it well enough alone and enjoy it the way it was made! I'll just stick to rooting my s3 and doing what im comfortable with. I appreciate all your words of help and advice to try and narrow down a solution.
First of all, you flashed some things not meant for your device. the CF-Autoroot method is designed for the Pxxx models, NOT the SGH/SCH models. Flashing this on your device flashed partitions it shouldn't have.
Second, the PBA is the mainboard. I bricked my tab a few weeks ago (typo in my updater script) and they replaced the PBA also. Samsung warranty is pretty great. Glad you got it fixed.
Always, ALWAYS, be sure you flash a ROM/recovery/etc designed for your specific device. The pxxx tabs and sgh/sch tabs are 100% different in hardware AND partition layout. If you flash a ROM for the Pxxx tab on a SGH/SCH tab, it will overwrite imei. Moderators REALLY need to suck it up and create separate forums for the lte tabs.
MrHyde03 said:
If you flash a ROM for the Pxxx tab on a SGH/SCH tab, it will overwrite imei. Moderators REALLY need to suck it up and create separate forums for the lte tabs.
Click to expand...
Click to collapse
Don't think this will happen, too small community and even no CM.
I think the verizon Tab is the Xperia Pro in the Xperia Arc Forum
Dexxmor said:
Don't think this will happen, too small community and even no CM.
I think the verizon Tab is the Xperia Pro in the Xperia Arc Forum
Click to expand...
Click to collapse
I know... very unlikely which is why I'm currently setting up my own forums to alleviate the issue :good:
get my tab 2 imei back to normal
Dexxmor said:
Don't think this will happen, too small community and even no CM.
I think the verizon Tab is the Xperia Pro in the Xperia Arc Forum
Click to expand...
Click to collapse
How I can get my tab 2 10.1 original imei back ? I lost my orignal imei and network not registered after my tab is root...please tell me how I can get it back, hope to have a solutions soon...

[Q] Invalid IMEI after installing ROM

Hello guys,
I just installed 4.1.2 Android from 4.2.2 and now My phone can't read my SIM card. When I'm trying to unlock my phone with GalaxSim Unlock it says "Warning: invalid IMEI. Restoring an EFS backup before unlocking is advised." The IMEI code on *#06# and on my phone's box are different. I have no ideas what I can do because I have never had this problem before after ROM installing. How I can solve this problem?
did you backup you umei/efs before at ant time?
Cruzin' tha Galaxy SIII via Obsessed Rom / "INAPPROPRIATE" Kernel
bbolton_98 said:
did you backup you umei/efs before at ant time?
Cruzin' tha Galaxy SIII via Obsessed Rom / "INAPPROPRIATE" Kernel
Click to expand...
Click to collapse
No I did not. Is there an other way to solve it?
check out below thread. hope you'd get it back!
http://forum.xda-developers.com/showthread.php?t=1852255
thats the best way (link in above post) if you happen to of installed synergy rom at any time it would have asked about making one for you. also nandroid manager can backup it also so check and see if any of your nandroids have a efs partition saved. if not read post in link more than once before doing anything.
Cruzin' tha Galaxy SIII via Obsessed Rom / "INAPPROPRIATE" Kernel
Is terminal emulator download available in Google play store??
bbolton_98 said:
thats the best way (link in above post) if you happen to of installed synergy rom at any time it would have asked about making one for you. also nandroid manager can backup it also so check and see if any of your nandroids have a efs partition saved. if not read post in link more than once before doing anything.
Cruzin' tha Galaxy SIII via Obsessed Rom / "INAPPROPRIATE" Kernel
Click to expand...
Click to collapse
I followed all steps but there is some problem in Restore. My phone is rooted and I have Terminal Emulator. When I write "su reboot nvbackup' it works and my phone reboot. But when I write "adb reboot nv restore" it says "device not found". Could you help me? I cannot reply on that thread.
http: //i39.tinypic.com/x513yc.png
Delete the space in this link because I cannot post any links until I do not have 10 post.
Edvinas1602 said:
I followed all steps but there is some problem in Restore. My phone is rooted and I have Terminal Emulator. When I write "su reboot nvbackup' it works and my phone reboot. But when I write "adb reboot nv restore" it says "device not found". Could you help me? I cannot reply on that thread.
http: //i39.tinypic.com/x513yc.png
Delete the space in this link because I cannot post any links until I do not have 10 post.
Click to expand...
Click to collapse
You need to reread the directions in the Comprehensive IMEI thread. You'll see why it's failing. I will say this though, "adb" is primarily a computer command so it's unnecessary on mobile.
Sent from my SCH-I535 using Tapatalk 4
I still do not get this. It says that I do not need ADB if I have Terminal Emulator and my phone is rooted. I just need to restore it in a some way.
Edvinas1602 said:
I still do not get this. It says that I do not need ADB if I have Terminal Emulator and my phone is rooted. I just need to restore it in a some way.
Click to expand...
Click to collapse
I'll ask you this now before I explain to you the command, does your IMEI in Settings/About Phone match what's on your Verizon GSIII retail box? Cuz restoring your IMEI will not work right now if its the wrong one. What you just backed up could be the "broken" IMEI and restoring it will do you more harm than good.
twistedillutions said:
Is terminal emulator download available in Google play store??
Click to expand...
Click to collapse
For clarity purposes, yes. Although, I see you posted this question in the Comprehensive IMEI thread and received an answer there as well.
SlimSnoopOS said:
I'll ask you this now before I explain to you the command, does your IMEI in Settings/About Phone match what's on your Verizon GSIII retail box? Cuz restoring your IMEI will not work right now if its the wrong one. What you just backed up could be the "broken" IMEI and restoring it will do you more harm than good.
Click to expand...
Click to collapse
IMEI codes are different. Now the IMEI code is 004999010640000. On my box the IMEI code is very different that one.
Edvinas1602 said:
IMEI codes are different. Now the IMEI code is 004999010640000. On my box the IMEI code is very different that one.
Click to expand...
Click to collapse
Aight, second question. Are you absolutely sure that you have a Verizon Galaxy SIII (d2vzw aka SCH-i535)? If so, proceed to read.
if you just performed this IMEI backup with the improper IMEI then the restore command will only reinsert this same wrong IMEI. You want your "proper" IMEI which is on the box to be backed up before you ever attempt an IMEI restore. If you have a CWM or TWRP rom backup then you should try restoring that THEN check if your IMEI is correct or wrong.
Do not post your proper IMEI. If it returns if/when you restore your rom in CWM or TWRP then just say "my IMEI is correct" or something like that. If you don't have a CWM or TWRP backup or don't know what I'm talking about then you're going to need a Windows computer and you'll need to Odin flash stock VRALF1 or VRAGL1 firmware tar. Make sure to unzip the file before using Odin, Odin flashes "tar" and "tar.md5" files only. If your IMEI is not restored at that point, then you'll need to reprovision your LTE sim card with the following code. It will erase your phone's storage. The dialer code only works o ICS software (so you'll need absolutely need VRALF2 or VRALG1):
Open the dialer and enter *2767*3855#
I'm stepping out for an hour or so. If you have any questions, hopefully someone else can provide input. If someone else things what I wrote above is unnecessary, please say so.
Edit: For clarity as well, I do not know if the VRALF2 or VRALG1 tar files format your internal storage (let's reasonably assume they do wipe /sdcard), so backup whatever important data you have on the phone to your computer or external sdcard.
Actually I have got SGS3 i9300. When I created this thread I didn't see that here is a subforum for i9300. Thanks for the help I will try it and let you know.
SlimSnoopOS said:
I'll ask you this now before I explain to you the command, does your IMEI in Settings/About Phone match what's on your Verizon GSIII retail box? Cuz restoring your IMEI will not work right now if its the wrong one. What you just backed up could be the "broken" IMEI and restoring it will do you more harm than good.
For clarity purposes, yes. Although, I see you posted this question in the Comprehensive IMEI thread and received an answer there as well.
Click to expand...
Click to collapse
Yes i posted both places up late last night ill stay over there for answers thnz for the response
SlimSnoopOS said:
Aight, second question. Are you absolutely sure that you have a Verizon Galaxy SIII (d2vzw aka SCH-i535)? If so, proceed to read.
if you just performed this IMEI backup with the improper IMEI then the restore command will only reinsert this same wrong IMEI. You want your "proper" IMEI which is on the box to be backed up before you ever attempt an IMEI restore. If you have a CWM or TWRP rom backup then you should try restoring that THEN check if your IMEI is correct or wrong.
Do not post your proper IMEI. If it returns if/when you restore your rom in CWM or TWRP then just say "my IMEI is correct" or something like that. If you don't have a CWM or TWRP backup or don't know what I'm talking about then you're going to need a Windows computer and you'll need to Odin flash stock VRALF1 or VRAGL1 firmware tar. Make sure to unzip the file before using Odin, Odin flashes "tar" and "tar.md5" files only. If your IMEI is not restored at that point, then you'll need to reprovision your LTE sim card with the following code. It will erase your phone's storage. The dialer code only works o ICS software (so you'll need absolutely need VRALF2 or VRALG1):
Open the dialer and enter *2767*3855#
I'm stepping out for an hour or so. If you have any questions, hopefully someone else can provide input. If someone else things what I wrote above is unnecessary, please say so.
Edit: For clarity as well, I do not know if the VRALF2 or VRALG1 tar files format your internal storage (let's reasonably assume they do wipe /sdcard), so backup whatever important data you have on the phone to your computer or external sdcard.
Click to expand...
Click to collapse
I'm actually considering doing this today. I lost my IMEI/ERI and restored them with the forbidden software but the problem I'm having is on some roms my google play store won't connect and it's been kinda frustrating and I don't know what else do, I've cleared store cache and data, plus every other fix I could find online. Plus it might be good practice for me if I have to send my phone back in the future as I bought my S3 rooted and unlocked.
TheAfroSamurai said:
I'm actually considering doing this today. I lost my IMEI/ERI and restored them with the forbidden software but the problem I'm having is on some roms my google play store won't connect and it's been kinda frustrating and I don't know what else do, I've cleared store cache and data, plus every other fix I could find online. Plus it might be good practice for me if I have to send my phone back in the future as I bought my S3 rooted and unlocked.
Click to expand...
Click to collapse
Might as well give it a try, not much at risk you know?
SlimSnoopOS said:
Might as well give it a try, not much at risk you know?
Click to expand...
Click to collapse
The only thing I can chalk it up to is maybe there was something still wonky because I didn't Odin back and used the Repair Tool. I'm off today and not really interested in the football game tonight so I got time. I'll Odin back, reprovision and reroot, unlock and see what happens with play store after that, thanks for all your help. Learned alot from your posts dude...:good:
TheAfroSamurai said:
I'm actually considering doing this today. I lost my IMEI/ERI and restored them with the forbidden software but the problem I'm having is on some roms my google play store won't connect and it's been kinda frustrating and I don't know what else do, I've cleared store cache and data, plus every other fix I could find online. Plus it might be good practice for me if I have to send my phone back in the future as I bought my S3 rooted and unlocked.
Click to expand...
Click to collapse
How did you restore your IMEI? What software did you use?
Edvinas1602 said:
How did you restore your IMEI? What software did you use?
Click to expand...
Click to collapse
This was before I found the Samsung Repair Utility so you may not need QPST and you can just use the repair utility.
1) I restored my IMEI using this guide here: http://droidmodderx.com/galaxys3/?page_id=79
2) Please note that since I hadn't found the repair utility you may not need to do step one, the repair utility does both IMEI/ERI
3) Go here: http://forum.xda-developers.com/showpost.php?p=44871571&postcount=3
4) We don't want to get XDA in trouble so I can't link the repair utility or have a mirror for it. I can only put you on the block and you have to find the house....
5) Once everything is ok flash your modem back up to whatever current modem you were using.
6) Also it may be best to just Odin back as I'm having issues with Play Store on certain roms.
TheAfroSamurai said:
This was before I found the Samsung Repair Utility so you may not need QPST and you can just use the repair utility.
1) I restored my IMEI using this guide here: http://droidmodderx.com/galaxys3/?page_id=79
2) Please note that since I hadn't found the repair utility you may not need to do step one, the repair utility does both IMEI/ERI
3) Go here: http://forum.xda-developers.com/showpost.php?p=44871571&postcount=3
4) We don't want to get XDA in trouble so I can't link the repair utility or have a mirror for it. I can only put you on the block and you have to find the house....
5) Once everything is ok flash your modem back up to whatever current modem you were using.
6) Also it may be best to just Odin back as I'm having issues with Play Store on certain roms.
Click to expand...
Click to collapse
What is the version of your Android? When I write *#7284# I don't see something like "Qualcomm USB Settings"

IMEI=0 - how to enter working IMEI?

Hi everyone & thanks for reading this!
I bought 2 new, unused Nexus 5 as presents for my sisters for Christmas (not via playstore, but via a reseller. Still: new, sealed, unused.)
I unlocked, installed a custom recovery, rooted both devices without problems, then set up one in a smartphone-newbie-friendly way, which took quite some time. Then, to save me some time, I fear I made quite a big mistake: I made a nandroid-backup of the newly-setup device and restored/installed it on the second nexus (so I wouldn't have to change all the settings again, install apps, etc).
Unfortunately, this seems to have erased the IMEI on the second device (it shows as IMEI=0), so I can't connect to any cell service. Some googling leads me to believe that this might be due to a corrupt/missing EFS-folder, which, second mistake, I did NOT make a backup of beforehand. I know, it's my own fault - my thinking was: why backup, there's nothing backupworthy on the device *yet*.
FML. :crying:
I am not sure if the phone is still in warranty (and even if it was - I guess I voided that by unlocking/rooting?!). I want to re-iterate that I own both devices LEGALLY, I have the bill, I have the original sticker with the original IMEI - I just need a way to re-enter it. Any dialer-code for that? Any modify-able EFS-backups? Any other way?
Thanks in advance!
PS: tried so far & found useless: other simcard (not working) & simcard in other phone (working), so it's a device-issue; factory-reset;
Try fastboot flashing the cache.img from the factory image.
jd1639 said:
Try fastboot flashing the cache.img from the factory image.
Click to expand...
Click to collapse
thanks for the super-quick reply jd1639!
to make sure I understand you correctly:
I can use the factory image from
https://dl.google.com/dl/android/aosp/hammerhead-kot49h-factory-02006b99.tgz
(nexus 5, android 4.4.2), extract the cache.img from there & flash that via fastboot? (or would it have to be a factory image of this very device - which I do not have, unfortunately)
and, just for my understanding: how does that restore the imei? I mean, the factory image itself (or it's cache) can't really contain MY imei. does this just delete the invalid imei & force the phone to get it's original imei from some other, not yet overwritten source? e.g. hardware?
Yes fastboot flash the cache.img from the factory image is a known fix for this issue. Something has corrupt your cache causing the imei to not display properly
Sent from my Nexus 5 using Tapatalk
Thank you for clarifying, rootSU - that gives me hope.
I will try tomorrow & hopefully report success
Just tried this (twice) - unfortunately no success, IMEI is still 0
downloaded factory image, verified md5, extracted cache.img, flashed in fastboot; every step successful - final result is still IMEI=0. Tried again, this time erasing cache beforehand for good measure - still IMEI 0.
What else can I try?
PS: this seems to be the only issue - no hw-problems or similar. directly after boot, the device seems to connect to a mobile network for a second, then gets kicked out (due to missing/invalid IMEI, I suppose).
RogerG said:
Just tried this (twice) - unfortunately no success, IMEI is still 0
downloaded factory image, verified md5, extracted cache.img, flashed in fastboot; every step successful - final result is still IMEI=0. Tried again, this time erasing cache beforehand for good measure - still IMEI 0.
What else can I try?
PS: this seems to be the only issue - no hw-problems or similar. directly after boot, the device seems to connect to a mobile network for a second, then gets kicked out (due to missing/invalid IMEI, I suppose).
Click to expand...
Click to collapse
Did you use TWRP for the original nandroid backup that you restored on the new one? If so, you may have backed up, and consequently flashed the EFS from the original N5 to the new one. If so, I hate to say this, but I don't think there's any hope of getting the IMEI back on the new one...
RogerG said:
Just tried this (twice) - unfortunately no success, IMEI is still 0
downloaded factory image, verified md5, extracted cache.img, flashed in fastboot; every step successful - final result is still IMEI=0. Tried again, this time erasing cache beforehand for good measure - still IMEI 0.
What else can I try?
PS: this seems to be the only issue - no hw-problems or similar. directly after boot, the device seems to connect to a mobile network for a second, then gets kicked out (due to missing/invalid IMEI, I suppose).
Click to expand...
Click to collapse
I had a problem with my phone IMEI (Nexus 4) before. It would say unknown. The reason why was I flashed a bad radio and boot loader version. So what I did was find a thread on the N4 section for the right radio and bootloader. I'm not exactly sure if this will work on your part, but I don't think it'll hurt to try. Oh and maybe reflash the factory image.
Sent from a potato
---------- Post added at 12:47 AM ---------- Previous post was at 12:44 AM ----------
Sorry for double post. Check this link out and go to the second post talking about IMEI. Idk if this will help you out. Good luck
http://forum.xda-developers.com/showthread.php?t=2510966
Sent from a potato
charesa39 said:
Did you use TWRP for the original nandroid backup that you restored on the new one? If so, you may have backed up, and consequently flashed the EFS from the original N5 to the new one. If so, I hate to say this, but I don't think there's any hope of getting the IMEI back on the new one...
Click to expand...
Click to collapse
yes, that's precisely what I did.
That's why I had little hope of restoring the original IMEI and was instead asking in my original post for a way to enter it anew (since I KNOW what it should be).
CellPhish said:
I had a problem with my phone IMEI (Nexus 4) before. It would say unknown. The reason why was I flashed a bad radio and boot loader version. So what I did was find a thread on the N4 section for the right radio and bootloader. I'm not exactly sure if this will work on your part, but I don't think it'll hurt to try. Oh and maybe reflash the factory image.
Sent from a potato
---------- Post added at 12:47 AM ---------- Previous post was at 12:44 AM ----------
Sorry for double post. Check this link out and go to the second post talking about IMEI. Idk if this will help you out. Good luck
http://forum.xda-developers.com/showthread.php?t=2510966
Sent from a potato
Click to expand...
Click to collapse
thanks I will try this (even though I think my problem is not related to radio/bootloader and I am generally skeptical about my chances of "restoring" IMEI, as opposed to "manually entering/modifying it"). Still, willing to try anything, thanks for the idea!
RogerG said:
thanks I will try this (even though I think my problem is not related to radio/bootloader and I am generally skeptical about my chances of "restoring" IMEI, as opposed to "manually entering/modifying it"). Still, willing to try anything, thanks for the idea!
Click to expand...
Click to collapse
If all fails you can try to contact LG service and tell them your situation. Though its not good to lie, just tell them you got the IMEI=0 problem, they'll say its a hardware problem and will replace the motherboard(if your device is on warranty)
Sent from a potato
You'll probably have a hard time here finding anyone to help you manually entering or modifying the imei.
rootSU said:
Yes fastboot flash the cache.img from the factory image is a known fix for this issue. Something has corrupt your cache causing the imei to not display properly
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
The IMEI is stored in the EFS partition, not the cache partition.
RogerG said:
yes, that's precisely what I did.
That's why I had little hope of restoring the original IMEI and was instead asking in my original post for a way to enter it anew (since I KNOW what it should be).
Click to expand...
Click to collapse
Sounds like you turned the phone into a $400 paperweight. TWRP backs up and restores the EFS partition by default, and each device has a unique EFS partition, which contains the IMEI among other things. I don't know of a way of manually restoring the EFS data. This is unfortunately a $400 lesson for people who tinker without first doing their homework.
Hey guy. Let's not be so judgemental. There's always a risk of the imei being corrupted when you flash a ROM. As a matter of fact just before I even unlocked my nexus the imei got corrupted and I had to factory flash my phone to save it. Its scary but op, if you manage to get your phone working again make a backup and store it on your PC and or email yourself the backup.
BirchBarlow said:
The IMEI is stored in the EFS partition, not the cache partition.
Click to expand...
Click to collapse
Ha ha thanks! Can't believe you think I don't know that :/
Actually the "EFS partition" is 2 partitions..
/dev/block/platform/msm_sdcc.1/by-name/modemst1
And...
/dev/block/platform/msm_sdcc.1/by-name/modemst2
That doesn't change the fact that reflashing the cache.img is a known fix for missing IMEI. Corrupt cache can make the imei appear as 0 even when the EFS imei is in tact so reflashing the cache.img can resolve this.
Unfortunately though, I didn't read the OP fully. I just elaborated on an earlier response for the OP
jd1639 said:
You'll probably have a hard time here finding anyone to help you manually entering or modifying the imei.
Click to expand...
Click to collapse
Modification is illegal however many mobile repair shops have equipment that can rewrite the existing imei and are legally allowed to. In the UK, this costs about £20. That said, i'm not aware of anyone having it done on the nexus 5. The galaxy s3 with a single /EFS partition could be done easily by a professional
Sent from my Nexus 5 using Tapatalk
rootSU said:
Modification is illegal however many mobile repair shops have equipment that can rewrite the existing imei and are legally allowed to. In the UK, this costs about £20. That said, i'm not aware of anyone having it done on the nexus 5. The galaxy s3 with a single /EFS partition could be done easily by a professional
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Yes but all talks about how to change it in any way are not allowed here. Legally the only people that are allowed to do so is the OEM. You can look at international news reports of cellular dealers that are doing so are being closed down and arrested.
That is why it is well know to back up the efs before you do anything.
Bat cave One
My newly bought Nexus 5 shows IMEI 0 also
RogerG said:
thanks I will try this (even though I think my problem is not related to radio/bootloader and I am generally skeptical about my chances of "restoring" IMEI, as opposed to "manually entering/modifying it"). Still, willing to try anything, thanks for the idea!
Click to expand...
Click to collapse
i just update my newly bought nexus 5 from initial 4.4.2 to 4.4.4 which is appear at update section but then my IMEI appear =0 .. dont understand what to do..
if your problem solved, pls tell me the detail procedure to recover my IMEI no.
RogerG, did you ever get this working? I'm on 6.0 and having the same problem, flashing cache.img also does nothing.
Thanks.

urgent help no signal wrong kernel flashed

plz friends i by mistake flash wrong kernel for the device and now i try everything and iv got no signal nothing
i did again clean flash and not working what can i do? plz
bubu23 said:
plz friends i by mistake flash wrong kernel for the device and now i try everything and iv got no signal nothing
i did again clean flash and not working what can i do? plz
Click to expand...
Click to collapse
plz any help ??? i have no reciption i flash sprint kernel to g925f mobile
Kernel got nothing to do with signal.
Sent from my SM-G920T
ambervals6 said:
Kernel got nothing to do with signal.
Sent from my SM-G920T
Click to expand...
Click to collapse
plz people i can see my imei like 350000000000000000000 it looks not good so i have no reciption
it cant find the network register what can i do????
i did clean stock rom now waiting to solution
bubu23 said:
plz people i can see my imei like 350000000000000000000 it looks not good so i have no reciption
it cant find the network register what can i do????
i did clean stock rom now waiting to solution
Click to expand...
Click to collapse
Hello, I had sent you a message to try and help as much as I could but you opened a thread so I'll help you on here.
First. Double check all twrp folders using a file Explorer. Some roms when flashed through twrp automatically back up your efs partition.
Second. If the folders are blank then we'll proceed to try other methods of fixing your imei.
I assume since you went from having a blank imei to that weird number you tried one of the methods you found through Google.
There are ways to manually reenter your imei if the methods found on Google fail. Follow the instruction in the site below (I highly suggest using the terminal emulator method) and report back here. Your imei can be found on your Sim card or the bigger card your Sim came in.
Flash with stock 5.1.1 ROM via odin.
http://www.sammobile.com/firmwares/database/SM-G925F/
roydok said:
Flash with stock 5.1.1 ROM via odin.
http://www.sammobile.com/firmwares/database/SM-G925F/
Click to expand...
Click to collapse
i flashed all ready i was on 5.1.1
drock212 said:
Hello, I had sent you a message to try and help as much as I could but you opened a thread so I'll help you on here.
First. Double check all twrp folders using a file Explorer. Some roms when flashed through twrp automatically back up your efs partition.
Second. If the folders are blank then we'll proceed to try other methods of fixing your imei.
I assume since you went from having a blank imei to that weird number you tried one of the methods you found through Google.
There are ways to manually reenter your imei if the methods found on Google fail. Follow the instruction in the site below (I highly suggest using the terminal emulator method) and report back here. Your imei can be found on your Sim card or the bigger card your Sim came in.
Click to expand...
Click to collapse
there is no site below where?
Nothing is gonna work guys.your efs imei is damaged now.do you have an efs backup.if you have restore it
mariolcela said:
Nothing is gonna work guys.your efs imei is damaged now.do you have an efs backup.if you have restore it
Click to expand...
Click to collapse
i dont have backup efs
If it's illegal, then it doesn't belong here. End of story.
Get your phone to Samsung for repair, it'll cost but they might fix it
Anyway try to flash many stock fw like btu etc it should fix this issues & try latest modem too ok anyway my friend always after rooting device just backup efs ..
Sent from my SM-G925F using Tapatalk
You can try flashing this updated French stock 5.1.1 ROM via odin. The very latest.
http://www.sammobile.com/firmwares/download/51274/G920FXXU2BOG8_G920FOXA2BOG8_XEF/
thx my friend but i install my country latest and it still same can i try more and more and maybe it will be ok with one of them?
cause if 1 not good everything same no?
update: i have g925f
thereassaad said:
Anyway try to flash many stock fw like btu etc it should fix this issues & try latest modem too ok anyway my friend always after rooting device just backup efs ..
Sent from my SM-G925F using Tapatalk
Click to expand...
Click to collapse
you say like btu what is btu?
bubu23 said:
you say like btu what is btu?
Click to expand...
Click to collapse
Btu for united Kingdom its best stock rom just try it my friend
Sent from my SM-G925F using Tapatalk
mythos234 said:
If it's illegal, then it doesn't belong here. End of story.
Get your phone to Samsung for repair, it'll cost but they might fix it
Click to expand...
Click to collapse
This right here.
I have cleaned this thread, and I don't want to see any posts about IMEI modifying or anything illegal here.
You can try stock flashing, rebuilding an EFS partition somehow (probably impossible) or repair shop, but any talk of anything illegal and the moderators will take action on your account.
Thanks.
Have you tried searching for a Galaxy s6 efs repair script?
If nothing has worked you definitely need to go with a repair shop. Either a third party repair or try to warranty replace your phone through Samsung. If you go the Samsung route Odin flash 100% stock firmware then send it in to them and see what they say
yeh i boght new s6 edge lolllllll bbut i i learned to back up

[GUIDE] How to fix IMEI / DRK issues

This Guide works on both the S7 and S7 Edge.
This also works on other Samsung device including Snapdragon variants as long as you have the correct files for your device.
FIll out my form if you require assistance
S8 users go HERE
​This guide is for those of you with EFS issues. This can cause your IMEI and/or Baseband to show Unknown or a bunch of zeros. The guide can also be used to fix DRK errors, but if your Device Root Key (DRK) is corrupt or missing, this guide will fix your IMEI/Baseband but will not fix your DRK error.
The guide gives instructions on how to flash the combination firmware. This installs the factory binary which allows your phone to read your IMEI and DRK. This should then restore your IMEI and DRK and then when you flash stock, the phone will be working as normal. If the Device Root Key (DRK) is corrupt or missing, this guide will only fix the IMEI, the DRK errors will still remain.
I take no responsibility for any issues that arise from following this guide. Do so at your own risk. The smallest mistake can cause a much bigger issue so make sure you know what you are doing and follow every step word for word!​
Please note that this will not work for everyone
Some people will still face getting stuck at boot when flashing the combination firmware.
This means you have at some point flashed firmware that is later than the latest combination firmware and unfortunately, it is not possible to fix this by downgrading the firmware to an earlier version.​
Before you proceed, you're going to need the following:
A copy of your phones stock firmware saved to your computer. If you do not already have these available on your computer, you can go HERE or you can use this tool to download the latest firmware for your device. Alternatively, you can find your firmware on SamMobile but this can take forever to download with a free account.
[IMPORTANT!] Switch off Factory Reset Protection (FRP) by going into Developer options and turning on 'OEM Unlock'. If you do not see 'Developer Options' under settings, then go to Settings > About Device > Software Info and keep tapping 'Build Number' until it confirms "You are now a developer" then go back to the main Settings screen and you will see Developer options.
if you skip this step, you only have yourself to blame if something goes wrong.
Odin. If you do not have it, download it from here
The Combination Firmware (Factory Binary). Download the combination firmware relevant to your phone (links below) and extract the .rar archive somewhere you will remember.
S7 International [G930F/FD] - (Mirror) [UPDATED 03/11/2017]
S7 Edge International [G935F/FD] - (Mirror) [UPDATED 03/11/2017]
S7 Canada [G930W8] - (Mirror)
S7 Edge Canada [G935W8] - (Mirror)
S7 Edge AT&T [G935A] - (Mirror)
Files for other models available on request via my form
​
Now you have all the files you need, follow the guide below to repair your S7.
There are 2 methods.
The first method (Method 1) is quick and can solve most issues. Especially DRK errors.
The second method (Method 2) is to use if Method 1 does not work. This guide requires more work and therefore takes a little longer.
Method 1
Boot into recovery and wipe data.
Put your phone straight into Download Mode (do not reboot or boot up the system between wiping data and booting to download mode). To do this, you can use recovery to reboot to Download mode. Alternatively, switch off your phone and hold 'Power' + 'Volume Down' + 'Home' until it boots to download mode. Then connect the phone to your computer with your USB cable.
Open Odin, press the 'AP' button and select the Combination tar/md5 file you downloaded/extracted earlier. Then press the 'Start' button. (If you have any errors while flashing, first make sure you are using the correct firmware for your phone. If it is still throwing errors, remove the ".md5" from the end of the file name and try again).
When Odin has completed flashing the combination file, it should boot into the Factory Binary. You may get a message asking you to reboot. Click reboot (If you do not get prompted to reboot, do a reboot manually).
When it has booted back up. Press the 'IME' button at the bottom of the screen and type *#06#. You should now see your IMEI has restored.
Now restore the stock firmware using the firmware you downloaded earlier. (If you're not sure how, follow this guide)
You should now have a restored IMEI. If not, this means your efs is damaged. Therefore, you will need to follow Method 2 below.
Method 2
You will need to start on a rooted device. If you are not rooted, follow this guide to root your phone or flash CF Auto Root in Odin.
Before you continue, it is extremely important that you backup your EFS partition, even if it is corrupt. You can backup the EFS partition using THIS APP. If you skip this step, you only have yourself to blame if something goes wrong and you have no backup to restore.
Download Root Explorer (Paid) or Root Browser (Free). Open 'Root Explorer' or 'Root Browser' (whichever you installed) and browse to the /efs folder located in the root of the device.
Inside the /efs folder, delete everything EXCEPT the 'FactoryApp' and 'prov_data' folders.
Reboot. Make sure it does a full reboot. When the phone boots back up, you may some errors or unusual settings, this is normal and nothing to worry about.
Boot into recovery and wipe data.
Put your phone straight into Download Mode (do not reboot or boot up the system between wiping data and booting to download mode). To do this, you can use recovery to reboot to Download mode. Alternatively, switch off your phone and hold 'Power' + 'Volume Down' + 'Home' until it boots to download mode. Then connect the phone to your computer with your USB cable.
Open Odin, press the 'AP' button and select the Combination tar/md5 file you downloaded/extracted earlier. Then press the 'Start' button. (If you have any errors while flashing, first make sure you are using the correct firmware for your phone. If it is still throwing errors, remove the ".md5" from the end of the file name and try again).
When Odin has completed flashing the combination file, it should boot into the Factory Binary. You may get a message asking you to reboot. Click reboot (If you do not get prompted to reboot, do a reboot manually).
When it has booted back up. Press the 'IME' button at the bottom of the screen and type *#06#. You should now see your IMEI has restored.
Now restore the stock firmware using the firmware you downloaded earlier. (If you're not sure how, follow this guide)
You should now have a restored IMEI.
​
Still Getting a DRK error?
If you are still getting a DRK error then you probably have a corrupt or missing Device Root Key (DRK). Unfortunately, this cannot be fixed without a JTag box (which aren't cheap). However, you can continue to use the phone as normal by flashing the no-verity zip in TWRP. You can then go ahead and use your phone as normal. Unfortunately, you will no longer be able to receive OTA updates. All updates will need to be made through ODIN and the no verity zip will need to be flashed every time a new firmware is flashed. However, you can still use custom roms as normal. Other than OTA updates, the DRK issue will have no effect on the use of the phone. You can still update via Smart Switch but will need to install TWRP and flash the no verity zip after every update.
If you would like any assistance in fixing your issue such as Method 1 & 2 do not work for you or if you have a different model than what is listed in this guide, please complete THIS FORM and I will try to get back to you ASAP (unfortunately I cannot always respond)
Many thanks to everyone that has donated!!
If you would like to donate, you can do so by clicking here
As you can imagine, finding fixes and assisting people takes a lot of my time so it's always great to receive a donation. Thank you.
​
Goooooooooooooooood,tnx
Very well detailed and clear guide bro. Thanks for posting this.
Tapped on my Echoe'd out G935F
Very good guide. Cubz helped me get my IMEI back so he knows his stuff. Thanks again.
Sent from my SM-G935F using XDA-Developers mobile app
ecera said:
Very good guide. Cubz helped me get my IMEI back so he knows his stuff. Thanks again.
Sent from my SM-G935F using XDA-Developers mobile app
Click to expand...
Click to collapse
No problem. Was happy to help
What else can this factory binary do? Can it restore the original CSC? I had an AFG CSC phone and after playing around with different roms, when I go back to the original firmware (although it is a multi CSC), it chooses XSG rather than AFG no matter what I do.
onurd said:
What else can this factory binary do? Can it restore the original CSC? I had an AFG CSC phone and after playing around with different roms, when I go back to the original firmware (although it is a multi CSC), it chooses XSG rather than AFG no matter what I do.
Click to expand...
Click to collapse
No it doesn't. Where are you seeing the CSC?
Sent from my SM-G935F using Tapatalk
CuBz90 said:
No it doesn't. Where are you seeing the CSC?
Sent from my SM-G935F using Tapatalk
Click to expand...
Click to collapse
I haven't seen CSC. anywhere. I was just wondering what this firmware had up its sleeves to "fix" things.
onurd said:
I haven't seen CSC. anywhere. I was just wondering what this firmware had up its sleeves to "fix" things.
Click to expand...
Click to collapse
What I meant is that when you say you now have a different CSC, how did you know this.
This firmware basically just feels the phone where to read the imei, baseband, and other info. This does not include the CSC.
PM me for my email address and then if you email me a backup of your EFS, I will have a look and restore your CSC for you.
Sent from my SM-G935F using Tapatalk
The original firmware of the phone was AFG for csc. Now even after using odin to get the same firmware, it defaults to xsg. Not a big deal but I don't know where the csc information is stored.
Sent from my SM-G935F using XDA Premium 4 mobile app
That's what I mean by the original csc having disappeared.
sent a PM about getting an EFS file, I hope you get it
onurd said:
That's what I mean by the original csc having disappeared.
Click to expand...
Click to collapse
Read this
Code:
http://forum.xda-developers.com/showpost.php?p=49425630&postcount=3
hiepgia said:
Read this
Code:
http://forum.xda-developers.com/showpost.php?p=49425630&postcount=3
Click to expand...
Click to collapse
I see. Phone info won't show the original csc without root.
But how do you explain that despite using the appropriate firmware with odin, it always defaults to xsg rather than the original afg from the multi csc firmware?
Hey so I tried flashing the G935_Factory_Binary.tar file on a galaxy s7 edge, and the thing is stuck on splash screen. any idea why?
onurd said:
I see. Phone info won't show the original csc without root.
But how do you explain that despite using the appropriate firmware with odin, it always defaults to xsg rather than the original afg from the multi csc firmware?
Click to expand...
Click to collapse
Because you flashed another region firmware, wipe data -> All original csc will get remove. You flash back and will only get default csc. If you rooted, you can change to afg csc
Thank you CuBz90 for your great work.
I flashed the superman rom but selected the wrong CSC.
I always backup my EFS in internal storage, but today I accidently wiped my entire internal storage. LOL
I have tried your method but unfortunately my imei is still missing, I'm totally frustrating. I will follow your thread. hope some expert can figure this out.
To everyone that has PM'd me, please bare with me. I have received a hell of a lot of PM's and I am trying to get through them all. Don't worry, I will definately reply and help you as best as I can.
Please make sure you are on your original stock firmware before trying this method. I notice a lot of people have PM'ed about CSC, I will PM you with info on how to revert this but please follow my steps exactly how I write them, a lot of people have PM'ed me to say "it's not working" but I have later found they are not following my steps exactly how I say and instead are taking shortcuts. If you take shortcuts then it's not going to work. I want to help you but you need to follow my exact instructions.
How to backup Efs without root?
Wanam app only works with root.
Sent from my SM-G935F using XDA-Developers mobile app
Help me?
Who can tell me efs file? Thank
Gửi từ SM-G930F của tôi bằng cách sử dụng Tapatalk

Categories

Resources