Related
Hello all,
I would like to share a method that solved this tricky issue with my S4 GT-I9500. While flashing with some new ROMs, I ended up with a generic IMEI on my S4. I read everything I could find here in XDA foruns, and no method worked for me. This one below, from fellow colleage douglasgalves at brasildroid foruns saved my phone. Here the link to the original post (portuguese only, sorry)
http://brasildroid.com.br/discussoe...efs-resolver-esse-problema-11.html#post299796
The method is quite simple, and althogh it does not make complete sense (why Trinida Tobago for example) it worked for me! Here it is.
1. You have a I9500 with a generic IMEI.
2. Install a official stock ROM with ODIN. Not any Stock ROM, but specifically Trinida & Tobago April 2013 ROM. You can browse it on Sammobile, or also get it from this link on XDA -> http://forum.xda-developers.com/showthread.php?t=2257645
The ROM I used is:
Build Date: 24.04.2013
Region: TTT (Trinidad and Tobago)
PDA: I9500UBUAMDK
Changelist: 534999 Android: 4.2
3. Once installation is finished, disconnect the cable;
4. Reboot to recovery and wipe data and cache;
5. Install KIES on your PC and let it update to its latest version.
6. Once KIES is updated, connect your S4 to the PC, no need for USB Debug, etc, just connect it.
7. KIES will detect it and say a new version of firmware is available. Perform the update. It takes a long time.
8. Once the update is finished, you get a dialog in KIES asking you to disconnect and connect the cable again, with a confirm button "Confirm". This is the moment it fixes your IMEI. One more reboot and voilà, your IMEI should be back.
I have no idea how/why this worked, if someone more experienced can explain, I would like to understand.
Also, no idea if this would work on other models, with a different ROM, or on a Mac instead of a PC, or with steps on different order. All I know is that, by doing exactly this, I gave life back to my beloved S4.
Now, off to make some 5 backups of the /efs folder before flashing ROMs again.
Good luck there with your generic-IMEIed S4s!
Did some more tweaking to try to understand what happened. Hope some guru can jump in and help me.
1. After I recovered my IMEI, I installed Philz Touch 5.11.2. It went well, I rebooted in CWM recovery, then chose Reboot->Root. It rebooted the phone. Then I went to make a backup of the /efs folder with Root Explorer, and discovered that despite it looking as rooting went well, the phone was not rooted.
Question 1: Why does Philz did not get to root the device? At that stage the firmware version was MG9 for region TTT (Trinidad & Tobago). Is that firmware somehow imcompatible for Philz to root?
Then ...
2. I flashed Firmware for Colombia with ODIN (my phone was bought in Colombia) from April, version UBUAMDE. Got Generic IMEI again. Then followed the same procedure from post 1, and got my IMEI back with KIES. The strange thing is that on KIES, my phone still shows as TTT (Trinidad) after that.
Question 2: It looks like more than the ROMs, it is the last step on KIES that recovers the IMEI. Is it so tha ODIN may be screwing up the IMEI?
Question 3: why I keep with my phone showing as TTT? Is that a problem?
3. Then I flashed the ChainFire recovery. Strangely, this went well and rooted my phone, so it may be something with Philz. I again flashed Philz and it installed well.
Question 4: may I get any problems by using Philz but having rooted with Chainfire?
Thanks a lot for any clarification you gurus out there can give me!
Thanks
You've given a considerable amount of hope to those that are stuck on the genereic imei. Thank you for providing this solution.
However, I am stuck:
After using ODIN 3.07; clicking nothing other than PDA for selecting the firmware you said to download: Hotfile:GT-I9500-TTT-I9500UBUAMDK-1366814146.zip The firmware was successfully installed.
Then before the boot completed, I went into recovery and wiped data and cache. The phone restarted and it booted up, Kies was already updated to the latest version. So once the phone booted up, I connected the phone to the computer and kies displayed this message:
Your device's current firmware version is not supported to update firmware via Kies.
Current firmware version: PDA:MDK / PHONE:MDK / CSC:MDK (XXX)
How can I go about resolving this issue?
As I said in the second post, I also got successful using the ROM for Colombia from April.
I would sugesst you to go to sammobile's firmware database. Download any older ROM which supports firmware via KIES (there is an icon showing that over there) and do the same procedure. It looks like what really solves it is the final step in KIES.
Sent from my GT-I9500 using XDA Premium 4 mobile app
I think this is due to flashing Previous Version of Modem (Its Including in Stock Firmware). When You flash Previous Version of Modem, Somehow IMEI retains. Here are some facts:
1) When we try to Flash any MOD of any dev then its depend on which Modem (i.e country's Firmware) the dev is using.
2) After flashing the MOD, Our IMEI becomes Fake.
3) Flashing Previous Version of Modem take back the IMEI.
In your above method you did the same. You flashed the Whole stock firmware but too old by date. After flashing, it retains.
BTW, have you checked your IMEI after flashing the Firmware using ODIN.? It was there.? was it Generic.?
Notice that I never refer to mod ROMs. I got a fake IMEI by flashing stock ROMs with ODIN.
Even during the recovery process, when I flashed the old stock ROM, the IMEI is not back. It only gets back at the last step with KIES.
When checking the IMEI after flashing with ODIN I get always the generic 499 IMEI.
Looks to me like something not going well with ODIN and 9500.
Sent from my GT-I9500 using XDA Premium 4 mobile app
partimers said:
Notice that I never refer to mod ROMs. I got a fake IMEI by flashing stock ROMs with ODIN.
Even during the recovery process, when I flashed the old stock ROM, the IMEI is not back. It only gets back at the last step with KIES.
When checking the IMEI after flashing with ODIN I get always the generic 499 IMEI.
Looks to me like something not going well with ODIN and 9500.
Sent from my GT-I9500 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Flashing ROM from ODIN given you Fake IMEI.? This is something strange. We all flashed from ODIN & never got that. BTW, If its like that, I would recommend above ^ ^ your steps but wait...... Did you flashed any other country's firmware.?
Disturbed™ said:
Flashing ROM from ODIN given you Fake IMEI.? This is something strange. We all flashed from ODIN & never got that. BTW, If its like that, I would recommend above ^ ^ your steps but wait...... Did you flashed any other country's firmware.?
Click to expand...
Click to collapse
It is indeed strange Disturbed, but I can reproduce it. I flash for example, April ROMs (happened with all countries that I tested, Trinidad, Colombia and Brazil), the IMEI gets generic. It is not that the /efs folder is deleted. It is there, it is just that somehow, the IMEI does not get correctly read from the files that are there.
It only gets fixed after KIES updates the ROM for the latest one, and only at the very last stage where KIES ask to disconnect/reconnect the cable.
I first get into trouble when after flashing CWM Philz, I tried to restore stock ROM.
I live in Brazil, but travel very often on business to Colombia, and bought the phone on a good sale. That is why I am trying different countries, but the problem first happened when re-installing Stock ROM for the first time, and at that time I was just using the ROM for Colombia.
Only when things got bad (generic IMEI) I tried other countries ROMs, modems, etc, and finally got to this method that fixed it for me.
[/QUOTE]
Hi have you taken a backup of the EFS and saved?
U are a lucky guy u hv it all this working
As per what i know possibly there will be 1 more folder in the system root other then efs main which has imei details etc which must be corrupted and takes place while flashing so u have fake imei
Also check do u have any lockscreen issue???
I m telling this coz I was mad solving imei issue for 2 days with note 2 just a week ago
Sent from my GT-I9505 using XDA Premium 4 mobile app
exclaimed said:
I connected the phone to the computer and kies displayed this message:
Your device's current firmware version is not supported to update firmware via Kies.
Current firmware version: PDA:MDK / PHONE:MDK / CSC:MDK (XXX)
How can I go about resolving this issue?
Click to expand...
Click to collapse
*FIX*
I had the same problem, so I did the following to fix the problem:
Root the device,
Install CSC Changer,
Select the CSC which matches the firmware you are trying to update,
Then start the guide above again from the beginning (including reinstalling the firmware through Odin, even if you are currently using it - to remove the root...)
and now Kies is updating my device!
*UPDATE*
IMEI is not fixed...
Thank you for your suggestion.
I've tired CSC Changer, but to no avail. After changing my CSC to TTT, the phone is restarted, and I put it in download mode; follow all the steps above, but I still see XXX on KIES.
I even tried changing my CSC by opening Preconfig via android terminal emulator, but I still see XXX on KIES.
exclaimed said:
Thank you for your suggestion.
I've tired CSC Changer, but to no avail. After changing my CSC to TTT, the phone is restarted, and I put it in download mode; follow all the steps above, but I still see XXX on KIES.
I even tried changing my CSC by opening Preconfig via android terminal emulator, but I still see XXX on KIES.
Click to expand...
Click to collapse
Please note that KIES does not require Download mode, just connect the phone to the PC running KIES. Maybe it is that, I don`t know.
Hi have you taken a backup of the EFS and saved?
U are a lucky guy u hv it all this working
As per what i know possibly there will be 1 more folder in the system root other then efs main which has imei details etc which must be corrupted and takes place while flashing so u have fake imei
Also check do u have any lockscreen issue???
I m telling this coz I was mad solving imei issue for 2 days with note 2 just a week ago
Sent from my GT-I9505 using XDA Premium 4 mobile app[/QUOTE]
Hey 123hiten, I had no lockscreen issues, only Generic IMEI. Solve it with KIES.
So now I have tried this solution in many different ways,
even though kies does update the FW, it doesn't restore the IMEI,
So on several occasions after updating and not see'ing the IMEI being restored
I put the old Columbian FW back on and restarted the process following every last detail exactly as stated but to no avail....
So I can only conclude that this solution must not work for the I9500 (Exynos S4)....
SmilerOnline said:
So now I have tried this solution in many different ways,
even though kies does update the FW, it doesn't restore the IMEI,
So on several occasions after updating and not see'ing the IMEI being restored
I put the old Columbian FW back on and restarted the process following every last detail exactly as stated but to no avail....
So I can only conclude that this solution must not work for the I9500 (Exynos S4)....
Click to expand...
Click to collapse
It is really frustrating when a solution works in some cases and not on others. Sorry to hear it did not fix it for you. But for my I-9500 it fixed it perfectly. I do not know why :/
One thing I may remark: the IMEI only came back on the very last stage, when after finishing the upgrade to latest firmware in KIES, I rebooted the phone, disconnect the cable, connected it again and pressed "Confirm" on KIES. At that exact point it fixed it. I did not have to do anything with CSC.
partimers said:
It is really frustrating when a solution works in some cases and not on others. Sorry to hear it did not fix it for you. But for my I-9500 it fixed it perfectly. I do not know why :/
One thing I may remark: the IMEI only came back on the very last stage, when after finishing the upgrade to latest firmware in KIES, I rebooted the phone, disconnect the cable, connected it again and pressed "Confirm" on KIES. At that exact point it fixed it. I did not have to do anything with CSC.
Click to expand...
Click to collapse
I did exactly as you said but the Kies button said "OK" not "Confirm"...
and the only reason the CSC change was required for me was to allow my device to be updated by kies (if your device was from Columbia & you updated it with that fw that may be why you didn't need to change the csc... as the csc was already the Columbia csc)
Device is from Colombia but somehow it let me update via KIES using the TTT rom
Sent from my GT-I9500 using XDA Premium 4 mobile app
partimers said:
Device is from Colombia but somehow it let me update via KIES using the TTT rom
Sent from my GT-I9500 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
@partimer, I am curious, what app or program did you use to backup your IMEI after restoring it to its original form or did you just copy the efs folder.
Thanks.
Copy the efs folder using root Explorer to the Sd card. From there I created a tarball and backed it up to my file server and cloud.
Sent from my GT-I9500 using XDA Premium 4 mobile app
From my time on the S2 I had efs problems too. It was established that the IMEI number is individual to each device and is not included on any firmware be it stock or custom. Several roms now automatically create backups when being flashed so it's worth exploring your system to find any backups.
Sent from my GT-I9505 using XDA Premium 4 mobile app
I have tried to flash the Android 5.0.1 stock firmware N910FXXU1BOC3 on my Note 4 N910F and I'm getting some error in Odin when it's writing the hidden.img.ext4 and failing. On the device, in Download Mode i see the error message volume size is too big.
Right now i'm on Android 4.4.4 N910FXXU1ANK4.
First thought was that i left Reactivation Lock on and saw a bunch of other threads where it says that this might be the main issue as I am flash a different CSC Region ROM. I managed to get back to N910FXXU1ANK4 after the failed flash of N910FXXU1BOC3 with Kies3 and Emergency re-initialization (thank you Samsung for finally doing something useful with Kies). I disabled the reactivation lock and attempted again to flash N910FXXU1BOC3 but failed with the same error.
After some searching, i found that the issue might be because i have to re-partition the device in order to fit the new partiton sizes for Android 5.0.1.
This should be done with the Odin option to Re-partition but that requires a PIT file in order to have the re-partition information.
I have looked into the md5 archive for the N910FXXU1BOC3 ROM and initial 5.0.1 release for N910F N910FXXU1BOB4 ROM but I could not find a PIT file in order to re-partition.
Now my question is, when going from Android 4.4.4 N910FXXU1ANK4 to Android 5.0.1 N910FXXU1BOC3, do I have to re-partition with Odin, and if so, where do I get the correct PIT file ?
Thanks.
lolozaur said:
I have tried to flash the Android 5.0.1 stock firmware N910FXXU1BOC3 on my Note 4 N910F and I'm getting some error in Odin when it's writing the hidden.img.ext4 and failing. On the device, in Download Mode i see the error message volume size is too big.
Right now i'm on Android 4.4.4 N910FXXU1ANK4.
First thought was that i left Reactivation Lock on and saw a bunch of other threads where it says that this might be the main issue as I am flash a different CSC Region ROM. I managed to get back to N910FXXU1ANK4 after the failed flash of N910FXXU1BOC3 with Kies3 and Emergency re-initialization (thank you Samsung for finally doing something useful with Kies). I disabled the reactivation lock and attempted again to flash N910FXXU1BOC3 but failed with the same error.
After some searching, i found that the issue might be because i have to re-partition the device in order to fit the new partiton sizes for Android 5.0.1.
This should be done with the Odin option to Re-partition but that requires a PIT file in order to have the re-partition information.
I have looked into the md5 archive for the N910FXXU1BOC3 ROM and initial 5.0.1 release for N910F N910FXXU1BOB4 ROM but I could not find a PIT file in order to re-partition.
Now my question is, when going from Android 4.4.4 N910FXXU1ANK4 to Android 5.0.1 N910FXXU1BOC3, do I have to re-partition with Odin, and if so, where do I get the correct PIT file ?
Thanks.
Click to expand...
Click to collapse
hi,
i have a N910F.. When i went from stock Android v 4.4.4 to Lollipop .. German Rom.. BOB4 and after that again to BOC3 I did not repartion anything. in fact repartion must be untick , I only made sure that auto reboot was ticked and F. Reset Time ticked then, place the tar/(md5 )file in AP section of Odin. Switch phone off, boot into download mode, connect phone via usb and wait for blue color to light up ID:COM box (above auto reboot) check if everything is connected and correct boxes ticked and then flash.( see screenshot ) After flash your phone will "try" to boot up but will optimise apps first. This can take some time (my case about 10 min? or so)
Plse take note that i am referring from stock Rom v4.4.4 to stock Lollipop
v 5.0.1 Also you only flash the one file....... "tar"/(md5 ) thats all.
good luck
willcor said:
hi,
i have a N910F.. When i went from stock Android v 4.4.4 to Lollipop .. German Rom.. BOB4 and after that again to BOC3 I did not repartion anything. in fact repartion must be untick , I only made sure that auto reboot was ticked and F. Reset Time ticked then, place the tar/(md5 )file in AP section of Odin. Switch phone off, boot into download mode, connect phone via usb and wait for blue color to light up ID:COM box (above auto reboot) check if everything is connected and correct boxes ticked and then flash.( see screenshot ) After flash your phone will "try" to boot up but will optimise apps first. This can take some time (my case about 10 min? or so)
Plse take note that i am referring from stock Rom v4.4.4 to stock Lollipop
v 5.0.1 Also you only flash the one file....... "tar"/(md5 ) thats all.
good luck
Click to expand...
Click to collapse
Thank you for the reply, thinking back I don't think i tried to flash BOB4 first and then BOC3. I will try this today and come back with some feedback.
lolozaur said:
Thank you for the reply, thinking back I don't think i tried to flash BOB4 first and then BOC3. I will try this today and come back with some feedback.
Click to expand...
Click to collapse
hi ,
i personally , don't think it will make any difference or matters,
if you flash the one or the other ..but hey ..who knows ..?
Only reason ,i flashed BOB4 as it was the first Lollipop available and BOC3 was a later date ( March 2015 )
good luck
I have the similar issue. KK and BOB4 roms work and install perfectly. however I am having the same issues while installing BOC3 rom be it Stock or Custom.
So I finally managed to solve the issue. Seems that the image I was downloading from Sammobile was not that good.
I was trying to install N910FXXU1BOC3_N910FVFG1BOC2_CNX - Romania Vodafone. I was unable to install it no matter what I tried.
I was able to install N910FXXU1BOC3_N910FTPD1BOC1_TPD - Netherlands unknown, without any issues.
Something that i noticed is that when loading the tar with issues in Odin, total binary size was shown as 0 mb, while on the Netherlands tar file it was showing 3.3gb.
Also the tar sizes where a bit strange : RO CNX 3.6gb - NL TDP 3.4gb. So I would imagine that extra 200mb might be an issue for the partition size (suspecting bloatware maybe?).
Long story short, the tar file I was trying was the issue and downloading a different CSC file solved this for me.
Also, I tried an advice from the forum, where you extract the recovery.img and convert to tar and first flash that tar before the ROM, but that did not work in this case.
Thank you for the replies and support.
Does it void the warranty ? I am also on 4.4.4 ANK version and want to update fo 5.0.1 BOC3.
Sent from my SM-N910F using XDA Free mobile app
I installed the BOB4 like said willcor and do an antutu and, I know that it are subjective information, but I was exhausted of see the Meizu above our fairy note 4 (including with the last 4.4.4), but now, I will sleep much more well than yesterday...
Beko68 said:
Does it void the warranty ? I am also on 4.4.4 ANK version and want to update fo 5.0.1 BOC3.
Sent from my SM-N910F using XDA Free mobile app
Click to expand...
Click to collapse
If you're talking about knox (hehe of course, what else) knox still 0x0 after installation...
Doing this kept my knox counter at 0x0, but I did not root or install any custom recovery.
Slightly off topic but I would stay away from BOC3. Many people I know have had problems with BOC3 Firmware.
I am going to be re-flashing BOC3 when I get back home... I must admit when I flashed BOC3 I didn't do a fresh wipe before flashing it so might have been my problem.
Have you wiped your phone before flashing the firmware?
BNerd89 said:
Slightly off topic but I would stay away from BOC3. Many people I know have had problems with BOC3 Firmware.
I am going to be re-flashing BOC3 when I get back home... I must admit when I flashed BOC3 I didn't do a fresh wipe before flashing it so might have been my problem.
Have you wiped your phone before flashing the firmware?
Click to expand...
Click to collapse
Yes, I wiped from the recovery before and after the BOC3 upgrade and I must say that I like how BOC3 feels.
Battery life feels about the same for me - 50% when I get home (9-5), considering i have BT on all day as i have a smartwatch paired, exchange account, 3 gmails, skype push and a few others.
Love the new Smart Lock features with Trusted Places an On Body Detection.
One thing I noticed, manual check for updates on Security Policy Updates does not give any results, not sure if that is working correctly.
I tried rooting my galaxy j7 with Odin and the feedback I get Is binary size too large
Kindly help me out
#19
I have fixed when up wrong file pit
My phone is samsung note9 128gb
When i try to up file pit on rom . I had loss my store from 128gb to 32gb
I don't find any solotion on web
And i have go to setting , open development setting. Choose lock OEM. After that my phone restart and recover to 128gb
Please share this solution . I hope it can help many people up wrong file pit and loss data store like me .
File up wrong pit file odin by Lock Oem
Recover Lost data store .
Good day!!!
Newb to firmware flashing here - a little back story first
Some days ago (before the holidays so more or less 2 weeks ago) my Note 4 started to turn off or reboot into download mode indicating mmc read fail (at the moment I was running CM12.1 under the N910FXXU1ANIE baseband) so I went and googled this and that and general data found was --> FLASH STOCK FIRMWARE (then do you custom stuff)
So after some more searching and asking around here (thank God for XDA) I found out which firmware I had to flash... here is where my problems started
The CSC:AMO firmwares I found always return error due to partition size errors
I found and downloaded the following files
AMO/N910FXXU1ANIE/N910FAMO1ANI4/ I was more intent on this one since its CSC is AMO & it was showing the same baseban name as I had before
AMO/N910FXXU1COI3/N910FAMO1COI1/ It was the only other AMO file on the site for the N910F....
So I recalled that on other Samsung phones I had to flash the Pit with the recovery and so else since the pit has the partition values and etc... so I tried using the default PIT file found here (in XDA) but I have the same partition size error (just different size number error?)
So after staying up till morning I was told by a user @ G+ to try with the N910FXXU1COJ3/N910FBTUCOI1.... and it worked!!!! but the thing is I want to try and get my phone as it was before (AMO/N910FXXU1ANIE) or at least with the "latest" (AMO/N910FXXU1COI3/N910FAMO1COI1) any way you could help me out with the pit file???
http://m.youtube.com/watch?v=LqoX7wNhotk
Did you still have the PIT file for AMO?
i need it man
The Story
Don't even know where to start. Okay so I have a SM-935W8 (Canadian Version) and it was working perfectly fine running Project Dream rom the S8 one. I decided to flash angelo's Pixel rom for S7 Edge and for some reason when it booted, the network had a cancel sign meaning no network. Once I finished the initial setup, calling, messaging , and data weren't working. Luckily I have a backup for EFS and RADIO in tar, img. and tar.gz formats. So I downloaded the Partitions Backup app and restored the EFS and Radio files, it said successfully restored. I rebooted my device and the issue was still there, no network. So then I installed the stock ROGERS (Provider) rom from SAM MOBILE and it came up with some DRK error and my phone would not boot. So then I quickly used ODIN to flash twrp and then flash Superman Rom (Love it) and use dm-verity bypass.zip to get past the drk error. Then I attempted many other things but to no avail such as flashing the EFS tar through ODIN which caused a "Software Error" and phone to be stuck on a light blue software error screen so I had to use smart switch to FULLY restore the phone back to booting up, then once again I flashed twrp and Superman rom with dm-verity so I atleast have root and a decent rom to work from.
The Problem and What I Have at Disposal
So essentially, I currently have a new section in settings under Connections called "SIM card manager" for managing sim cards even tho I only have 1 slot, it shows that the SIM is ROGERS and LTE/3G/2G in there, but it can't connect to a network and keeps saying Not Registered on a Network. Also, there are 2 IMEI's since my phone thinks theres 2 SIM slots but I really only have 1 slot. BUT HERE IS THE MAIN ISSUE, THE ROOT OF ALL PROBLEMS, the IMEI is reading as "000000000000000" and the IMEISV is "01". Hence im getting Not Registered on a Network. No secret codes such as *#06# are working, keeps giving the Not Registered on a Network error.
I have the EFS and RADIO backups in img, tar, and tar.gz formats as well as screenshots of all my MAC and Bluetooth addresses, IMEI and Serial #'s and all that information. So essentially I feel fully ready to solve the problem but everything I try keeps failing. My EFS restoration says successful in the APP but upon reboot, theres no change. Flashing the EFS through ODIN messes up phone harder. When I use EFS Professional Tool, where do I place the partitions so they show up in the tool?
I used this post to try to fix it: https://forum.xda-developers.com/s7-edge/how-to/guide-how-to-fix-check-drk-imei-issues-t3379516
BUT when I'm flashing the combination through ODIN in AP, it goes to NAND write or whatever and gets stuck, sometimes it gets stuck on Analyzing files or something. I tried every single ODIN version. I really could use some expertise on this issue. A step by step written tutorial, some method anything!!!! Help on this post or even teamviewer or skype for live help would be appreciated. Please help and I'm willing to compensate for successfully helping me fix my issue..
Did you ever sort this out? I'm in a similar situation, except that it does occasionally show my IMEI but also 'baseband unknown'. But still no network access.
i hope i dont risk a warning, but you can use xposed and with root you can change your imei and baseband info.
012345678 said:
i hope i dont risk a warning, but you can use xposed and with root you can change your imei and baseband info.
Click to expand...
Click to collapse
Thanks, I've done so much to this phone now...
I did try xposed and have tried a different IMEI, it seems like it's a modem issue but there doesn't seem to be a firmware solution - I have tried so many stock roms(All the way back to the first Marshmallow and a bunch in between) and different custom roms too but in the end the error is always there: Not registered to Network.
I saw somewhere in my troubleshooting that some kind of cert needs to be patched because the phone did an update on a modified rom without the OEM unlock being on and then the EFS data was messed up or something like that (all of the research and troubleshooting is starting to blur). It seems like that fix isn't doable without a rather expensive piece of hardware (expensive if your just fixing your one phone I guess) and there isn't any firmware-only fix that can accomplish this patch so I'm stuck again.
jamesroodney said:
Thanks, I've done so much to this phone now...
I did try xposed and have tried a different IMEI, it seems like it's a modem issue but there doesn't seem to be a firmware solution - I have tried so many stock roms(All the way back to the first Marshmallow and a bunch in between) and different custom roms too but in the end the error is always there: Not registered to Network.
I saw somewhere in my troubleshooting that some kind of cert needs to be patched because the phone did an update on a modified rom without the OEM unlock being on and then the EFS data was messed up or something like that (all of the research and troubleshooting is starting to blur). It seems like that fix isn't doable without a rather expensive piece of hardware (expensive if your just fixing your one phone I guess) and there isn't any firmware-only fix that can accomplish this patch so I'm stuck again.
Click to expand...
Click to collapse
i think i can help you out with that. install that with odin, it should get your efs and imei back:
Samsung S7 Edge Cert and Efs (SM-G935F)
https://drive.google.com/file/d/0B5829G4TER3CZmZYVU9PY21qT2c
012345678 said:
i think i can help you out with that. install that with odin, it should get your efs and imei back:
Samsung S7 Edge Cert and Efs (SM-G935F)
https://drive.google.com/file/d/0B5829G4TER3CZmZYVU9PY21qT2c
Click to expand...
Click to collapse
Sorry, I should have clarified. I have an S7 (SM-G930W8). I only tried this thread because the issue was identical to mine and I couldn't find anything similar referencing the S7 specifically.
For anyone coming across this thread in the future, although mine was an S7 I think the issue would apply to both. I ended up ordering a z3x in order to use the patch certificate. But it wasn't that easy; the firmware had to be downgraded to marshmallow first which wouldn't work in Odin until I tried just flashing the BL and CP files first, then rebooting and flashing the AP and CSC files separately. In fact, the AP file froze the first time but passed on the second attempt. After that, everything was downgraded to android 6 and then the patch certificate option worked and my s7 connects to the network again.
I'm having a similar problem with my sm-g935w8 Rodgers but has been unlocked. A couple days ago i looked at my phone and it was showing a no signal symbol and I look for my phones information and it showed unknown in all categories, the imei say unknown, and it's not reading the sim. Help me
I am having the same problem after installing TGP ROM.
Graschuk said:
I am having the same problem after installing TGP ROM.
Click to expand...
Click to collapse
Did u Found any solution? am still in the same position as u r in.. i have also installed TGP ROM ... I Have Also Posted there my issue that i selected the latest bootloader nd modem blah blah
Wipe everything in twrp advanced and..
Flash latest stock rom for your model and it'll fix the issue
I think u need to see this
https://forum.xda-developers.com/showthread.php?p=78868375#post78868375
These two threads are the fountains of info :
https://forum.xda-developers.com/s7-edge/how-to/guide-how-to-fix-check-drk-imei-issues-t3379516
This one specifically for S7 edge, whole lots of info.
https://forum.xda-developers.com/note-4/general/fix-drk-dm-verity-factory-csc-serial-t3422965
This one for advanced users who know what they are doing.. it isn't specifically for s7 series but has a universal approach to understand concepts.. don't use the provided drk (prov data) and csc restoring files, they aren't for s7 edge.
Always backup efs and all radio/serial related info firstly after rooting. Good luck
Sent from my S7 Edge using XDA Labs
Greetings Folks
I have a N910C and as mentioned in title recently I got stuck in to this issue
How it happened
I had CF-Rooted my phone and Odin flashed TWRP for custom ROMS so I tried a few and was not getting the perfomance thought SimplROM would do it for me in order to install that ROM it said in instructions to install latest Modem and Bootloader
So i tried downloading the ones given in v6C BL was downloaded but CP kept on giving me errors getting stuck at 7% on mega so being stupid I downloaded DPCB(MODEM) While ROM was offering DPK4
So everything went fine until after boot I realized am facing Not Registered to Network
Since I had experienced this before on other phone I went ASAP in dialer to check my IMEI & SN both are still intact
I knew about EFS unfortunately I backed it up on Phone Storage which was wiped for ROM and I forgot (So dont have EFS Backup )
I do recall years ago back when I had S3 I experienced this and sometimes flashing different firmware(CSC ,Modem) fixed it
What I have tried so far
I have already tried several stock ROMs most of em had DPI1 Baseband except 2 other ROMS no luck
tried combination file method too (the one that helps downgrade to kitkat i believe ) no luck
Tried XEO repair Firmware no luck
any suggestions ??
and on that contrary now that I am not on stock is there any way to find out which CSC and Stock ROM this phone originally was one or came with with IMEI or Serial I believe ?
Thanks in Advance
Anyone??
under the battery there's the serial number
install on your pc samsung smart switch program
run it with option of emergency software recovery - device initialisation
input the model of your phone
input the serial number
start
have patience and a good connection
your phone will (eventually) get the latest official firmware
https://www.blogtechtips.com/2017/06/24/easily-restore-samsung-device-firmware-with-smart-switch/
at least you'll have a working phone with stock rom
from here on you can try again and get informed better on what to do
good luck
w41ru5 said:
under the battery there's the serial number
install on your pc samsung smart switch program
run it with option of emergency software recovery - device initialisation
input the model of your phone
input the serial number
start
have patience and a good connection
your phone will (eventually) get the latest official firmware
https://www.blogtechtips.com/2017/06/24/easily-restore-samsung-device-firmware-with-smart-switch/
at least you'll have a working phone with stock rom
from here on you can try again and get informed better on what to do
good luck
Click to expand...
Click to collapse
Hey there bud I have almost tried most of fixes I could I'll give Smart Switch a try as I recall I checked before it didn't have initialization just the recovery mode, while in Kies 3 I did try initialization method by model and SN but it prompted device doesn't support initialization
Anyways do you think it could fix network?
Sent from my Pixel 2 XL using Tapatalk
crossmedia said:
Hey there bud I have almost tried most of fixes I could I'll give Smart Switch a try as I recall I checked before it didn't have initialization just the recovery mode, while in Kies 3 I did try initialization method by model and SN but it prompted device doesn't support initialization
Anyways do you think it could fix network?
Click to expand...
Click to collapse
Maybe restore the efs from recovery, if you have a backup that was working.
w41ru5 said:
Maybe restore the efs from recovery, if you have a backup that was working.
Click to expand...
Click to collapse
Jist checked not getting initialization option on smart switch ill see a work around it if its a version thing , as for working backup I lost it mate it was in twrp folder in phone storage it got wiped recovery softwares out there only help recovering media mostly if mass storage mount was option could have tried recovering for PC but that has been long gone since ICS
Sent from my Pixel 2 XL using Tapatalk
Yep. Same problem as mine. Im kinda lost now since i dont have anything; even in stock rom it cannot go beyond connecting to my carrier. It only able to read my contact.
Im guessing its a motherboard problem? Isnt it @w41ru5?
VannM said:
Yep. Same problem as mine. Im kinda lost now since i dont have anything; even in stock rom it cannot go beyond connecting to my carrier. It only able to read my contact.
Im guessing its a motherboard problem? Isnt it @w41ru5?
Click to expand...
Click to collapse
I don't know. Usually it's a modem issue when not recognizing the sim.
If it's a 910F snapdragon it might be the infamous eMMC issue.
If you have an EFS backup try to restore it from recovery TWRP.
Assuming its modem problem, its related to motherboard i guess, right?
Finally got the phone working, only to discovered that SIM not working. Really wasting my time and hype!
Plus, its hard to search for n910c replacement board here.
VannM said:
Assuming its modem problem, its related to motherboard i guess, right?
Finally got the phone working, only to discovered that SIM not working. Really wasting my time and hype!
Plus, its hard to search for n910c replacement board here.
Click to expand...
Click to collapse
The firmware, not the physical one.
Did you try to flash the 4 files repair firmware?
This is an example, I don't know what phone you have
https://firmware.gem-flash.com/index.php?a=downloads&b=folder&id=7081
Did you try the SmartSwitch pc program?
"...4 file repair..."- what? Ive google it until im almost run out of data here and you have a possible solution? You must be active in note4 forum.
One thing i noticed that, the IMEI and Serial Number are different from the sticker included.
I will try it, but not immediately; waiting for thurday-friday for data renewal.
My phone is n910c
EDIT : just checked the page you gave. I have few question;
What should i do with the files? What are the step? What are the program needed?
Is it related to SmartSwitch as you mention; need to use it?
Thanks!
VannM said:
"...4 file repair..."- what? Ive google it until im almost run out of data here and you have a possible solution? You must be active in note4 forum.
One thing i noticed that, the IMEI and Serial Number are different from the sticker included.
I will try it, but not immediately; waiting for thurday-friday for data renewal.
My phone is n910c
EDIT : just checked the page you gave. I have few question;
What should i do with the files? What are the step? What are the program needed?
Is it related to SmartSwitch as you mention; need to use it?
Thanks!
Click to expand...
Click to collapse
1. It's good you still have the IMEI. Not so important if they're different from the sticker. Where did you buy the phone from?
2. So if you go to check the 4 files repair, you need to search on that site the files for a 910C.
3. Did the phone worked on your country provider? If yes, maybe you need to search for the 4files corresponding to your region code.
4. These 4files have to be flashed with Odin
https://zfirmware.com/download-samsung-repair-firmwares/
5. SmartSwitch is an alternative to get the latest firmware for your phone according with the model and serial number.
https://www.sammobile.com/forum/threads/29914-SmartSwitch-Install-amp-update-or-replace-firmware
the "firmware.gem" are useless. the error says i need another package (i assume a quota) to download the needed files.
im currently testing "zfirmware", but have a doubt since it only give 1 type file (which country is it i dunno). but yeah, since my phone like that, it wouldnt hurt to try
EDIT : yep, nothing changed. the device not even bricked.
VannM said:
the "firmware.gem" are useless. the error says i need another package (i assume a quota) to download the needed files.
im currently testing "zfirmware", but have a doubt since it only give 1 type file (which country is it i dunno). but yeah, since my phone like that, it wouldnt hurt to try
EDIT : yep, nothing changed. the device not even bricked.
Click to expand...
Click to collapse
If something does not work, why do you give up so easy?
http://www.mediafire.com/file/a2fdo0xm9nat5jt/N910CXXS2DPJ3_N910CZTO2DPE2_ZTO.zip - this is marshmallow
https://androidfilehost.com/?fid=24269982087001472 - this is for lolipop
Put the phone in download mode, open Odin and try.
And try the smartswitch also.
w41ru5 said:
If something does not work, why do you give up so easy?
Click to expand...
Click to collapse
That hurts. A lot. Explanation below.
w41ru5 said:
http://www.mediafire.com/file/a2fdo0xm9nat5jt/N910CXXS2DPJ3_N910CZTO2DPE2_ZTO.zip - this is marshmallow
https://androidfilehost.com/?fid=24269982087001472 - this is for lolipop
Put the phone in download mode, open Odin and try.
And try the smartswitch also.
Click to expand...
Click to collapse
I tried files from LP and MM. It didnt work. And also smartswitch.
I was hoping that it will brick the phone (if i ever missed a step or incorrect file) but it didnt.
Might as well try looking for replacement board (or even a refurbished note4).
Thanks though for the suggestion @w41ru5!
Greetings again folks reading your replies above I have been trying almost every fix there is out there
First of all about Emergency Calls Only/Not Registered on Network
It can be due to several causes its can be Hardware ie faulty modem
it can be bad network coverage
it can be bad simcard
it can be SW with EFS problems or maybe even on rare occasion a modem file that you flashed
EFS can be either bad IMEI with CERT : FAIL or Just Network with IMEI and SN intact
just dial *#0011*# and see if you have CERT : PASS ( also someone with good IMEI/CERT and working network can share screenshot so i can compare whats wrong)
I am certain mine is EFS related because it happened after flashing modem DPCB modem via ODIN (I had TWRP EFS backup but the blunder I made was backing it up on phone storage and being careless forgot it was there and was wiped for custom ROM flashing process)
So far what I have tried
Combination File Method (and even downgrade to KK 4.4.4 )
Repair Firmware that include AP,BL,CP,CSC and even PIT
Kies 3 or Older Smart Switch says (Device doesn't support initialization ) since initialization feature was removed by Samsung on newer Smartswitch(since it was being used for wrong reasons? read somewhere)
Several different firmware's
OTA update
My IMEI CERT says PASS if only we had a network patch like Ariza Patch (for Galaxy S3) for Note 4 then we would be in luck so far at this point I dont think flashing ROM's would even help with bad EFS our only luck is Box e.g Z3x or Octo dont know if we are allowed to talk about those here (ill edit post if not)
these box applications have Network Patch for most Samsung models but I don't see one for N910C in most versions
for those with bad IMEI they can try writing good cert or efs on note 4 since they have already lost it I am sitting on it because my EFS is good on that part and for some reason box app isnt allowing me to back up my CERT if I am able to back up current cert then ill give those a try but I would prefer current IMEI since in my country IMEI should be verified to use the phone or you have to pay tax
I know its Bad EFS for sure because using Box application I chose reset EFS(after backing up current faulty EFS with good IMEI) upon reboot phone's imei was changed with no SN network came back for few seconds then gone again ,this happened to many users that have tried resetting EFS so I restored my original EFS
if anyone here with N910C and root can give me EFS folder I can corelate if any file required for network is missing since i have good IMEI
Cheers!