Network / IMEI Problem

Search This thread

moizsami

Senior Member
Jun 23, 2011
473
73
cairo
OnePlus 7T
Hey guys im worried now, iwas thinking to buy this phone, but im afraid of this problem, i was going to buy it from india and without warranty.
what should i do now?
Is there any solution out there yet..?
 

thiagodark

Senior Member
Nov 1, 2010
689
103
Old City-ES
Hey guys im worried now, iwas thinking to buy this phone, but im afraid of this problem, i was going to buy it from india and without warranty.
what should i do now?
Is there any solution out there yet..?

no, there is no solution out there yet

flashing .imgs (radios, roms, bootloaders) doesn't solve the problem... there is absolutely no radio or rom that makes it works right. I tried everyone.

and i'm pretty sure it is not related to efs/factory partition


to be honest with you, without warranty i wouldn't buy the, not at all... it's a pretty expensive device to take the risk to end with a VERY expensive mp3 player... even the chance is not that high!!

i'm seeing several threads about this and no fix til now:

http://xdaforums.com/showthread.php?t=1643015
http://xdaforums.com/showthread.php?t=1618163
http://xdaforums.com/showthread.php?p=26340507
http://xdaforums.com/showthread.php?p=26369207

but it's up to you! =o)
 
Last edited:
  • Like
Reactions: moizsami

moizsami

Senior Member
Jun 23, 2011
473
73
cairo
OnePlus 7T
hey just got a question... so if i dont use my mobile network at all i.e keep 2g/3g off all the time. would i still face this problem...?
im very keen on buying this phone..

Please reply....Thanks
 

thiagodark

Senior Member
Nov 1, 2010
689
103
Old City-ES
JTAG didn't work.

-_-

Not. Happy. Camper. I'm rarely stumped.

really? i guess nothing else can be done... wtf, weird problem


hey just got a question... so if i dont use my mobile network at all i.e keep 2g/3g off all the time. would i still face this problem...?
im very keen on buying this phone..

Please reply....Thanks

well, that's depends on... i'm able to use the phone as a dumb one, with no data active activeted (except wi-fi), but Naezor, on the other hand, has a device that can't be used in anyway, no data, no voice... only wifi, bt, etc...
 
Last edited:

Chaosin1983

Senior Member
Oct 28, 2011
127
2
really? i guess nothing else can be done... wtf, weird problem




well, that's depends on... i'm able to use the phone as a dumb one, with no data active activeted (except wi-fi), but Naezor, on the other hand, has a device that can't be used in anyway, no data, no voice... only wifi, bt, etc...

I on the other hand have a phone that cannot be used as a phone, no GSM signal, only WiFi...but every now and then I will have GSM signal out of the blue!

But just because this happened to us doesn't mean it will happen to you, there are millions of people that never had this problem...for the price, this is a damn fine phone...

Hey guys, does any of you know how to claim warranty for this phone if it was bought online?
 

thiagodark

Senior Member
Nov 1, 2010
689
103
Old City-ES
I on the other hand have a phone that cannot be used as a phone, no GSM signal, only WiFi...but every now and then I will have GSM signal out of the blue!

But just because this happened to us doesn't mean it will happen to you, there are millions of people that never had this problem...for the price, this is a damn fine phone...

Hey guys, does any of you know how to claim warranty for this phone if it was bought online?

i think that depends... you should ask for warranty directly from where you bought from...
 

ottoTheGreat

New member
Jul 3, 2012
1
0
I have the exactly the same problem -.-

Jeez. The signal just dropped one night. No baseband, No IMEI.

I tried every freaking thing with the risk of bricking my phone.

I agreed with thiagodark, it doesn't seem to be a EFS problem. I looked at them,

they seemed to be perfectly fine. The date of modification and etc went way back

before my problem appeared, when I did not even root my phone.

So disappointed.
 

geoffcorey

Senior Member
Apr 24, 2010
2,156
484
I got my phone back from repair, they had to do a pba replacement. There was a physical fault with the modem.

Sent from my Galaxy Nexus using Tapatalk 2
 
  • Like
Reactions: thiagodark

thiagodark

Senior Member
Nov 1, 2010
689
103
Old City-ES
I'm in the same boat .. and the repair cost!? my warranty is out: (

Sorry dude, you cant fix it here in brazil, i took it to a samsung service center and they said they couldnt do anything because the device was not made here...

As your warranty is "out", my guess is that your phone is imported too. Since gnex was released here in feb..
 

dhuberto

Senior Member
Jan 9, 2012
105
21
Recife
Sorry dude, you cant fix it here in brazil, i took it to a samsung service center and they said they couldnt do anything because the device was not made here...

As your warranty is "out", my guess is that your phone is imported too. Since gnex was released here in feb..

Thank you, and if a physical problem of the pba (modem) I will send him or seller! EUhueh :(
 

ozzman54

Senior Member
Sep 22, 2010
176
16
Fixed by sending in for warranty

Just an update...I was having all of these symptoms...unknown IMEI, Baseband, etc...basically gave me an expensive media player for a few months while waiting for a fix on XDA. After no update I decided to call up Samsung and after talking to 3 different technicians, I was able to send it in. Just a note for anyone about to do the same, they will try very hard to blame it on the carrier/SIM card, so save yourself some trouble and just say you already went to the physical store of your carrier (calling isn't enough)and they couldn't get it working. Once you get past that, they will email you a printable 2-day UPS shipping label so you can ship it to them for free. It took 2 weeks from the time I called to having a working phone back in my hands.

This was their fix:

Problem found:
NO PCS SERVICE

Solution:
REPLACED PBA

After a quick search I found that the PBA is the motherboard, so it's definitely a hardware issue. Hope you guys are still under warranty because I've heard this is ~$200 to fix otherwise.

Good luck.
 
  • Like
Reactions: Maonela

Maonela

Member
Sep 26, 2011
13
1
Kitwe
Samsung Galaxy S21+
I can help you restore your original imei but I have to have your phone with me

Sent from my Galaxy Nexus using XDA

Hello! I have a nexus s gsm version with an IMEI problem... I cant access my sim card network. it says No Service. it seems you can restore the original but have to have the op's phone. cant you make a guide for all of us to try? :D

Your help will be grat!! :good:
 

Top Liked Posts

  • There are no posts matching your filters.
  • 4
    This is after fdocomo v3, right? So your files get rebuild from what's in the factory and you still get what, unknown IMEI? This may also be that files in factory are simply broken and were broken before backup. They contain IMEI, so if something happened to them, this would show as such problem. However, if /factory is lost, I don't know how to fix it. There are things worth trying though - you may try restoring nv_data files from nv_core files, which is actually pretty simple if you have busybox. With rw mounted factory and airplane mode on, do:
    Code:
    shell@android:/factory # cd /factory
    shell@android:/factory # rm nv_data.bin*
    shell@android:/factory # rm .nv_data.bak*
    shell@android:/factory # rm /data/radio/nv_data.bin.*
    shell@android:/factory # ls -la
    -rwx------ radio    radio     1048576 2012-04-20 03:13 .nv_core.bak
    -rwx------ radio    radio          32 2012-04-20 03:13 .nv_core.bak.md5
    -rwx------ radio    radio           1 2012-04-20 03:13 .nv_state
    drwxr-xr-x radio    radio             2011-01-03 15:26 bluetooth
    -rw------- radio    radio         640 2011-01-03 15:26 hdcp.keys
    drwxrwxr-x radio    radio             1999-12-31 16:02 imei
    drwx------ root     root              1969-12-31 16:00 lost+found
    -rw------- radio    radio        4674 2012-04-20 03:13 nv.log
    drwxrwx--- system   radio             1999-12-31 16:00 wifi
    -rw-r--r-- radio    radio         144 2011-01-03 15:26 wv.keys
    # busybox killall rild
    wait lets say 30 secs

    Code:
    shell@android:/factory # ls -la
    -rwx------ radio    radio     1048576 2012-04-20 03:13 .nv_core.bak
    -rwx------ radio    radio          32 2012-04-20 03:13 .nv_core.bak.md5
    -rwx------ radio    radio     2097152 2012-05-10 00:34 .nv_data.bak
    -rwx------ radio    radio          32 2012-05-10 00:34 .nv_data.bak.md5
    -rwx------ radio    radio           1 2012-04-20 03:13 .nv_state
    drwxr-xr-x radio    radio             2011-01-03 15:26 bluetooth
    -rw------- radio    radio         640 2011-01-03 15:26 hdcp.keys
    drwxrwxr-x radio    radio             1999-12-31 16:02 imei
    drwx------ root     root              1969-12-31 16:00 lost+found
    -rw------- radio    radio        4847 2012-05-10 00:34 nv.log
    -rwx------ radio    radio     2097152 2012-05-10 00:34 nv_data.bin
    -rwx------ radio    radio          32 2012-05-10 00:34 nv_data.bin.md5
    drwxrwx--- system   radio             1999-12-31 16:00 wifi
    -rw-r--r-- radio    radio         144 2011-01-03 15:26 wv.keys
    shell@android:/factory # cat nv.log
    (...)
    Thu May 10 00:34:19 2012: NV backup has been rebuilt.
    Thu May 10 00:34:19 2012: backup NV restored from Secondary bak.
    Thu May 10 00:34:23 2012: MD5 open fail. (No MD5 file) : /data/radio/nv_data.bin.md5
    Thu May 10 00:34:23 2012: NV restored.(GED)

    What this does is gives rild (radio interface Samsung daemon) chance to rebuid /factory from .nv_core backup. It knows how to do it, but normally can't do it on startup, since /factory is ro mounted. By mounting it rw, deleting files that are broken and killing daemon (which is service, so it gets restarted by android magicaly almost immediatelly), it gets chance. So try this. If you don't have busybox, just do ps, find rild there and PID number and do kill <PID>.

    If this doesn't help, your secondary backup .nv_core.bak is also broken or it's really HW issue. In either case, this would require special tools to fix. But this is worth trying as last resort. I did it on my phone just to test this theory again.

    EDIT: And I don't believe it's HW issue. If it was, generic IMEI wouldn't work. But it does for you and generic IMEI is nothing else then nv_data.bin that is hardcoded somewhere in the system to be used if factory doesn't exist. But if your /factory is broken and you don't have backup, you'd still need SPTBox or something similar to generate new files from scratch. So send it to somebody or find some Samsung repair place...
    1
    well, i noticed that /factory was totally messed up due my attempt to fix it. I retore and fix permssions to looks just like yours but for a strange reason i can't restore .nv_data.bak and .nv_data.bak.md5 through root explorer...

    screenshot_2012-05-09-09-40-53.png


    in any case, even with /factory without almost all files inside the issue was exactly the same and i was able to make radio works with the "battery remove" workaround...

    edit: exactly same problem, but now with a generic imei! =o)

    i'm gonna restore my backup when get in home...
    Your /factory still as wierd permissions. Most of the files are owned by root and are not readable by radio, which will cause problem. This is probably result of restore. You made nv_data.bin owned by radio, but without accompanying nv_data.bin.md5 system will just ignore it and probably give you generic IMEI, which is what we were seeing here when md5 files didn't match bin files.

    Anyway, generic IMEI looks promising. We know how to fix generic IMEI if you have backup of /factory - so please don't loose it.

    So yes, restore /factory, fix the permissions
    Code:
    # cd /factory
    # chown radio.radio .*

    and try checking the log file in /data/radio/log again. Since you have the directory, I still think there must be something in there.
    1
    done, restored factory from backup, what was strange is that even after all files restored. with right permisions and with right owner, the generic imei remained and i had to install f*ckdocomo.apk to get it back...

    now i just have the original problem =o)

    i really didn't have any file inside /data/radio path before, but now it has a log and i believe is due the /factory problem and not related with the original problem

    anyway, that's log in /data/radio/log

    9 09:44:21 2012: MD5 is turned on.

    Wed May 9 09:44:21 2012: truncate 10276 -> 5156 bytes
    Wed May 9 09:44:33 2012: __refresh_md5_file: Can't open /factory/nv_data.bin.md5. Permission denied.
    Wed May 9 09:44:33 2012: MD5 is turned on.
    Wed May 9 09:44:44 2012: __refresh_md5_file: Can't open /factory/nv_data.bin.md5. Permission denied.
    Wed May 9 09:44:44 2012: MD5 is turned on.

    REPEAT FOR A LONG LONG TIME AND THEN I RESTORE FILES IN /RECOVERY copying files from sdcard

    Wed May 9 09:53:20 2012: __refresh_md5_file: Can't open /factory/nv_data.bin.md5. Read-only file system.
    Wed May 9 09:53:20 2012: MD5 is turned on.
    Wed May 9 09:53:31 2012: __refresh_md5_file: Can't open /factory/nv_data.bin.md5. Read-only file system.
    Wed May 9 09:53:31 2012: MD5 is turned on.
    Wed May 9 09:53:43 2012: __refresh_md5_file: Can't open /factory/nv_data.bin.md5. Read-only file system.

    REPEAT FOR LOOOONG TIME AND THEN I RESTORE MY .IMG BACKUP AND USE F*UCKDOCOMO.APK

    Wed May 9 14:24:50 2012: /data/radio/nv_data.bin does not exist.
    Wed May 9 14:24:50 2012: MD5 fail. orignal md5 'f6afbceb74ee4290c4563e046f24' computed md5 '6ec535b7b029665813c18d6283c7' (rild)
    Wed May 9 14:24:50 2012: MD5 fail. orignal md5 '861f9436276afbcbdc44f58d473a' computed md5 'de37d01ec798841e4944ee69cf5f' (rild)
    Wed May 9 14:24:51 2012: default NV restored.
    Wed May 9 14:26:07 2012: /data/radio/nv_data.bin does not exist.
    Wed May 9 14:26:07 2012: /data/radio/nv_data.bin does not exist.

    oh, and i think all files is just fine in /factory path, but no fix at all.

    i start to think it should be a hardware fault...

    screenshot_2012-05-09-21-35-21.png
    1
    I just bought a new Galaxy Nexus. And I don't wanna experience the same problem. What should i do? Is there a way to backup files containing IMEI and if any problem occurs i can restore them?

    Thanks in advance.

    at the moment nobody knows what is this problem and why it happens... so just be lucky! =o)

    oh, and meanwhile, make a efs backup, the easiest way is this: http://xdaforums.com/showthread.php?t=1510906

    =o)
    1
    Hey guys im worried now, iwas thinking to buy this phone, but im afraid of this problem, i was going to buy it from india and without warranty.
    what should i do now?
    Is there any solution out there yet..?

    no, there is no solution out there yet

    flashing .imgs (radios, roms, bootloaders) doesn't solve the problem... there is absolutely no radio or rom that makes it works right. I tried everyone.

    and i'm pretty sure it is not related to efs/factory partition


    to be honest with you, without warranty i wouldn't buy the, not at all... it's a pretty expensive device to take the risk to end with a VERY expensive mp3 player... even the chance is not that high!!

    i'm seeing several threads about this and no fix til now:

    http://xdaforums.com/showthread.php?t=1643015
    http://xdaforums.com/showthread.php?t=1618163
    http://xdaforums.com/showthread.php?p=26340507
    http://xdaforums.com/showthread.php?p=26369207

    but it's up to you! =o)