Phone_ICCID_unknown Phone ICCID compare with SIM ICCID: Error

[BArgue]

After having a replacement charging board, I am getting this error: Phone_ICCID_unknown, Phone ICCID compare with SIM ICCID: Error. It returns an ICCID for the SIM but not for the phone. However, my phone signal is erratic and drops during calls or when dialling. Sometimes I can make/receive a call but other time it gives a message indicating I can't make calls.

The SIM works fine in another G5 and I have been onto my network provider (Virgin) with no progress. I have tried restarting, turning aircraft mode on/off, re-registering the network but no joy. How can I reinstate the phone's missing ICCID?

These instructions didn't work either:

1. Turn Off
2. Hold VOL- and push POWER button for 1sec.
3. Now on screen should be visible the Fastboot menu
4. VOL- to set blue bar on BP Tools
5. VOL+
6. Now phone will start

I tried to do this but it just sat there saying <waiting for device>.

Install ADB/Fastboot on your PC
Once installed enable developer options on your phone
Plug your phone into your PC and run the following commands from a command prompt
adb reboot bootloader
fastboot erase modemst1
fastboot erase modemst2
fastboot reboot

Any help appreciated. I'm not very techie, so assume you are explaining to Homer Simpson

 

[TheFixItMan]

If reflashing the entire stock firmware via fastboot doesn't work & the sim card is of working order take it back to whoever replaced the bored and get the to fix your phone properly

Firmware can be found here - if you don't know which is right one just use latest retail
https://mirrors.lolinet.com/firmware/moto/cedric/official/

Assuming you have fastboot setup correctly on pc

fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1 
fastboot erase modemst2 
fastboot flash fsg fsg.mbn
fastboot erase cache 
fastboot erase userdata 
fastboot oem fb_mode_clear
fastboot reboot

 

[BArgue]

Head scratching done! I installed the right board, same part number but different batch and the mic works. I reflashed the phone but it still has the same issue. I used a bundle I downloaded as it already had batch files. I think it has less of these lines: fastboot flash system system.img_sparsechunk. Does that matter? Anyway, it all booted up OK. Oddly, I can sometimes make a call and then the next minute I get an error saying cell calls unavailable. I'd expect it to work or not, not intermittently.

I guess that eliminates any software issues? Is there anything else to try or is it a hardware problem?

 

[TheFixItMan]

Head scratching done! I installed the right board, same part number but different batch and the mic works. I reflashed the phone but it still has the same issue. I used a bundle I downloaded as it already had batch files. I think it has less of these lines: fastboot flash system system.img_sparsechunk. Does that matter? Anyway, it all booted up OK. Oddly, I can sometimes make a call and then the next minute I get an error saying cell calls unavailable. I'd expect it to work or not, not intermittently.

I guess that eliminates any software issues? Is there anything else to try or is it a hardware problem?

Sparsechunk 0-8 is the stock rom files themselves

Nougat has less parts than oreo but all parts needs to be flashed (oero having parts 0 to 8)

If you have flashed firmware for your region the only thing that has changed on your device is the hardware
If a different sim doesn't solve the issue then as said the only difference is the board that was replaced assuming there's no other hardware issues

 

[BArgue]

Thanks. My mistake, this batch file did have more of those lines. This is what I used (Motorola_Moto_G5_XT1675_CEDRIC_RETEU_SS_8.1.0_OPP28.85-19-4-2_CID50):

<phone_model model="cedric"/>
<software_version version="cedric-user 8.1.0 OPP28.85-19-4-2 3447de release-keysM8937_46.42.02.75R"/>
<subsidy_lock_config MD5="d41d8cd98f00b204e9800998ecf8427e" name="slcf_rev_d_default_v1.0.nvm"/>
<regulatory_config SHA1="da39a3ee5e6b4b0d3255bfef95601890afd80709" name="regulatory_info_default.png"/>
<sparsing enabled="true" max-sparse-size="268435456"/>
<interfaces>
<interface name="AP"/>
</interfaces>
</header>
<steps interface="AP">
<step operation="getvar" var="max-sparse-size"/>
<step operation="oem" var="fb_mode_set"/>
<step MD5="9f3a13b8222b08e2171d2519e5276c31" filename="gpt.bin" operation="flash" partition="partition"/>
<step MD5="9ea732d853c838d9ed8486ca6df10321" filename="bootloader.img" operation="flash" partition="bootloader"/>
<step MD5="3605a87a6e4ba36c2f995204a7ec2aa6" filename="NON-HLOS.bin" operation="flash" partition="modem"/>
<step MD5="77aec885e43c1441ae775a36add08125" filename="fsg.mbn" operation="flash" partition="fsg"/>
<step operation="erase" partition="modemst1"/>
<step operation="erase" partition="modemst2"/>
<step MD5="bded198b6f1d31e9ce664376503b223b" filename="adspso.bin" operation="flash" partition="dsp"/>
<step MD5="0f114b5a2ab83e18444fa0d8e79a8e0e" filename="logo.bin" operation="flash" partition="logo"/>
<step MD5="4559fd8bad5404d1ec16a98614b3765a" filename="boot.img" operation="flash" partition="boot"/>
<step MD5="864a8060abe29e56fe2e8e93cac2c4a3" filename="recovery.img" operation="flash" partition="recovery"/>
<step MD5="39b15d4e645ba9576e819edfaf5b668e" filename="system.img_sparsechunk.0" operation="flash" partition="system"/>
<step MD5="ed64b41d92f7cf5f4079442fc446e0af" filename="system.img_sparsechunk.1" operation="flash" partition="system"/>
<step MD5="aef832b70ded5b7b5788bf87b61a8ad6" filename="system.img_sparsechunk.2" operation="flash" partition="system"/>
<step MD5="31c52fe5f412ac621e325f879a08e6e8" filename="system.img_sparsechunk.3" operation="flash" partition="system"/>
<step MD5="982e8d23a01a1017c72c23c56aed3ca2" filename="system.img_sparsechunk.4" operation="flash" partition="system"/>
<step MD5="1ef6cd540e95e3fe2c80d934376b6f3a" filename="system.img_sparsechunk.5" operation="flash" partition="system"/>
<step MD5="66a2a34e2bacd1ab0f5065524e2ce141" filename="system.img_sparsechunk.6" operation="flash" partition="system"/>
<step MD5="052ca5a46c322450dacad5678c31ac0e" filename="system.img_sparsechunk.7" operation="flash" partition="system"/>
<step MD5="0a20486510c1c5f45d1d8dbfcf0b9975" filename="system.img_sparsechunk.8" operation="flash" partition="system"/>
<step MD5="1e60bbc27184845acdc99d789f503c0c" filename="oem.img" operation="flash" partition="oem"/>
<step operation="erase" partition="cache"/>
<step operation="erase" partition="userdata"/>
<step operation="erase" partition="DDR"/>
<step operation="oem" var="fb_mode_clear"/>
</steps>
</flashing>

Does that look right? I seem to recall a message about some process or other not being able to run before the board change. Can't recall what it was though. It was plugging it into the charger shortly after that burned out the port.

I think I need a proper grown-up to look at it as I'm already hopelessly out of my depth

 

[TheFixItMan]

Thanks. My mistake, this batch file did have more of those lines. This is what I used (Motorola_Moto_G5_XT1675_CEDRIC_RETEU_SS_8.1.0_OPP28.85-19-4-2_CID50):

<phone_model model="cedric"/>
<software_version version="cedric-user 8.1.0 OPP28.85-19-4-2 3447de release-keysM8937_46.42.02.75R"/>
<subsidy_lock_config MD5="d41d8cd98f00b204e9800998ecf8427e" name="slcf_rev_d_default_v1.0.nvm"/>
<regulatory_config SHA1="da39a3ee5e6b4b0d3255bfef95601890afd80709" name="regulatory_info_default.png"/>
<sparsing enabled="true" max-sparse-size="268435456"/>
<interfaces>
<interface name="AP"/>
</interfaces>
</header>
<steps interface="AP">
<step operation="getvar" var="max-sparse-size"/>
<step operation="oem" var="fb_mode_set"/>
<step MD5="9f3a13b8222b08e2171d2519e5276c31" filename="gpt.bin" operation="flash" partition="partition"/>
<step MD5="9ea732d853c838d9ed8486ca6df10321" filename="bootloader.img" operation="flash" partition="bootloader"/>
<step MD5="3605a87a6e4ba36c2f995204a7ec2aa6" filename="NON-HLOS.bin" operation="flash" partition="modem"/>
<step MD5="77aec885e43c1441ae775a36add08125" filename="fsg.mbn" operation="flash" partition="fsg"/>
<step operation="erase" partition="modemst1"/>
<step operation="erase" partition="modemst2"/>
<step MD5="bded198b6f1d31e9ce664376503b223b" filename="adspso.bin" operation="flash" partition="dsp"/>
<step MD5="0f114b5a2ab83e18444fa0d8e79a8e0e" filename="logo.bin" operation="flash" partition="logo"/>
<step MD5="4559fd8bad5404d1ec16a98614b3765a" filename="boot.img" operation="flash" partition="boot"/>
<step MD5="864a8060abe29e56fe2e8e93cac2c4a3" filename="recovery.img" operation="flash" partition="recovery"/>
<step MD5="39b15d4e645ba9576e819edfaf5b668e" filename="system.img_sparsechunk.0" operation="flash" partition="system"/>
<step MD5="ed64b41d92f7cf5f4079442fc446e0af" filename="system.img_sparsechunk.1" operation="flash" partition="system"/>
<step MD5="aef832b70ded5b7b5788bf87b61a8ad6" filename="system.img_sparsechunk.2" operation="flash" partition="system"/>
<step MD5="31c52fe5f412ac621e325f879a08e6e8" filename="system.img_sparsechunk.3" operation="flash" partition="system"/>
<step MD5="982e8d23a01a1017c72c23c56aed3ca2" filename="system.img_sparsechunk.4" operation="flash" partition="system"/>
<step MD5="1ef6cd540e95e3fe2c80d934376b6f3a" filename="system.img_sparsechunk.5" operation="flash" partition="system"/>
<step MD5="66a2a34e2bacd1ab0f5065524e2ce141" filename="system.img_sparsechunk.6" operation="flash" partition="system"/>
<step MD5="052ca5a46c322450dacad5678c31ac0e" filename="system.img_sparsechunk.7" operation="flash" partition="system"/>
<step MD5="0a20486510c1c5f45d1d8dbfcf0b9975" filename="system.img_sparsechunk.8" operation="flash" partition="system"/>
<step MD5="1e60bbc27184845acdc99d789f503c0c" filename="oem.img" operation="flash" partition="oem"/>
<step operation="erase" partition="cache"/>
<step operation="erase" partition="userdata"/>
<step operation="erase" partition="DDR"/>
<step operation="oem" var="fb_mode_clear"/>
</steps>
</flashing>

Does that look right? I seem to recall a message about some process or other not being able to run before the board change. Can't recall what it was though. It was plugging it into the charger shortly after that burned out the port.

I think I need a proper grown-up to look at it as I'm already hopelessly out of my depth

Why use a batch file? Being lazy and using batch files someone else created can cause issues if not done right

All the commands to flash the latest stock firmware are written in my post above
Flash each part as written in the order I've written them

Firmware download from
https://mirrors.lolinet.com/firmware/moto/cedric/official/

Try the latest retail version

 

[BArgue]

Why use a batch file?

Largely because my skills in this area are dwarfed by Homer Simpson's and my typing is notoriously inaccurate; I was trying to avoid bricking my phone through my incompetence With some trepidation, I will have a go at your suggestion...

 

[BArgue]

To my amazement, I managed to re-flash the phone using your instructions. The bad news is that it made no difference. Still emergency calls only. Oddly, it still seems to register incoming calls as I woke up to 2 missed ones today.

Update:

Went up to the repair shop, got the phone out to show the problem and it had a full strength signal! Maybe some issue with my local cell tower?

I installed Network Cell Info Lite. I have no idea what half the info displayed means. For example, it seems to swap between HSPA, EDGE and GSM. With the phone in the same spot, ASU seems to vary between 1-5

Curiously, the signal drops off to -110dBm approx. indoors at home but I can get -89 outside the back door. In the garden, -81 and ASU up to 16. I have never had a bad signal at home before. My g/f's Moto G5, also on Virgin, seems OK and her SIM in my phone seems OK and vice versa. So, it seems to be reception related. The question is: Why would the same phone on the same network differ in its ability to receive a signal?