https://redmine.replicant.us/https://redmine.replicant.us/favicon.ico?15984615062015-12-11T08:06:40ZReplicantReplicant - Issue #1467: i9300 lost IMEIhttps://redmine.replicant.us/issues/1467?journal_id=44072015-12-11T08:06:40ZEric Cirehaaber@web.de
<ul></ul><p>Hello again, still my phone can no longer make phone calls. Frustrating. I've been to all sites on the subject, no help available.</p>
<p>the <br />[code]<br />/efs/FactoryApp/serial_no<br />[/code]<br />contains the correct 11-digit IMEI now, but this seems to be ignored</p>
<p>Some people suggest using <strong>#*#197328640#</strong>#* to enter service mode & activate "Field test mode" FTM, but this one seems to be removed in replicant. All I get is "enter" option, but don't know what I could / should enter there. I found no help on FTM via adb either.</p>
<p>Since I am no longer on Samsung ROM, I am afraid of going to a shop who will run some more or less hazardous software they do not understand either.</p>
<p>I really need some help with this. Thank you, Eric</p> Replicant - Issue #1467: i9300 lost IMEIhttps://redmine.replicant.us/issues/1467?journal_id=45752015-12-11T14:51:53ZDenis 'GNUtoo' CarikliGNUtoo@cyberdimension.org
<ul><li><strong>Category</strong> changed from <i>117</i> to <i>Framework</i></li><li><strong>Device</strong> <i>Galaxy S 3 (I9300)</i> added</li></ul> Replicant - Issue #1467: i9300 lost IMEIhttps://redmine.replicant.us/issues/1467?journal_id=49292015-12-11T15:24:39ZEric Cirehaaber@web.de
<ul></ul><p>As additional information I may add that the problem seems to be a result of a deep battery discharge.<br />After recharging, the IMEI was gone.</p> Replicant - Issue #1467: i9300 lost IMEIhttps://redmine.replicant.us/issues/1467?journal_id=60632016-02-14T11:03:39ZPaul Kocialkowskipaulk@replicant.us
<ul><li><strong>Category</strong> changed from <i>Framework</i> to <i>Telephony and mobile data</i></li></ul> Replicant - Issue #1467: i9300 lost IMEIhttps://redmine.replicant.us/issues/1467?journal_id=64742017-02-19T23:16:06Zdoak complex
<ul></ul><p>Hi Eric, hi Paul,</p>
<p>I had also lost my IMEI, had no backup of the EFS partition and was just <em>able to recover</em> it.</p>
<p>First to the bug:<br />In Apr 2016 I suddenly couldn't connect to the network anymore after the battery was discharged completely and I swapped to another battery hours later. WLAN/BT (with firmware blobs) still worked. In the past it happened that the (correct) SIM-PIN was not accepted, which I always had fixed by removing and inserting the SIM.<br />Now, it seems removing the battery was the important part of this procedure.</p>
<p>Anyway, let me know, Paul, if I can help hunting this issue down. I am using 'Replicant v4.2 0004' which I have built myself.</p>
<p>Second to the fix of NV/IMEI:<br />As far as I understood, the EFS partition is mirrored to another partition containing an ext4 (or other standard) file system during installation of Replicant since CM10 (Android v4.x). So I tried to reinstall the stock ROM (from Samsung using Kies in Win7 inside a Qemu instance) to get the orginal EFS partition (with the not corrupted NV containing the IMEI) back.<br />And yes... <strong>it worked</strong>, after I reinstall Replicant I am able to connect to the mobile network again ;)</p>
<p>Regards,<br />doak</p> Replicant - Issue #1467: i9300 lost IMEIhttps://redmine.replicant.us/issues/1467?journal_id=64802017-02-21T20:59:42Zdoak complex
<ul></ul><blockquote>
<p>I am using 'Replicant v4.2 0004' which I have built myself.</p>
</blockquote>
<p>I am not sure if this was correct. My Replicant says about itself '4.2.2 eng.replicant20150409.114718'.</p> Replicant - Issue #1467: i9300 lost IMEIhttps://redmine.replicant.us/issues/1467?journal_id=64812017-02-21T21:20:37Zdoak complex
<ul></ul><blockquote>
<p>Anyway, let me know, Paul, if I can help hunting this issue down. I am using 'Replicant v4.2 0004' which I have built myself.</p>
</blockquote>
<p>I stored the failing EFS partition. If it would help in any way, I could restore that and get logs. But I guess it would be important to get logs at the time when the corruption of 'nv_data.bin' had happened.</p>
<p>Are there any hints how to store as most information as possible if that happen again? Just run 'logcat'?</p>
<p>Regards,<br />doak</p> Replicant - Issue #1467: i9300 lost IMEIhttps://redmine.replicant.us/issues/1467?journal_id=64992017-03-05T21:30:28ZWolfgang Wiedmeyerwreg@wiedmeyer.de
<ul></ul><p>I opened <a class="issue tracker-3 status-15 priority-21 priority-default closed parent" title="Issue: The installation pages lack advice to backup the EFS partition (Resolved)" href="https://redmine.replicant.us/issues/1778">#1778</a> so that at least hints are added in the wiki that recommend to backup the EFS partition.</p> Replicant - Issue #1467: i9300 lost IMEIhttps://redmine.replicant.us/issues/1467?journal_id=67582017-06-14T20:26:26ZWolfgang Wiedmeyerwreg@wiedmeyer.de
<ul><li><strong>Related to</strong> <i><a class="issue tracker-3 status-15 priority-21 priority-default closed parent" href="/issues/1778">Issue #1778</a>: The installation pages lack advice to backup the EFS partition</i> added</li></ul> Replicant - Issue #1467: i9300 lost IMEIhttps://redmine.replicant.us/issues/1467?journal_id=75222019-08-16T20:54:51ZKurtis HannaKurtis@riseup.net
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>Closed</i></li><li><strong>Resolution</strong> set to <i>wontfix</i></li></ul><p>This issue has been closed because Replicant 4.2 is no longer supported or maintained.</p>