Welcome to our peer-to-peer forums, where owners help owners. Need help now? Visit eSupport here.

Motorola Community

Unlockable PhonesMOTOROLA Android Developer Community
All Forum Topics
Options

9 Posts

10-22-2018

Italy

6 Signins

124 Page Views

  • Posts: 9
  • Registered: ‎10-22-2018
  • Location: Italy
  • Views: 124
  • Message 1 of 17

I can no longer connect to the mobile network after "losing" the imei code

2018-10-22, 21:47 PM

I wanted to install a different firmware of version 7.1.1 nougat of my phone, so I unlocked the bootloader and I unfortunately ran from fastboot the command  

fastboot erase all

believing to do a complete cleaning except the important files, instead they are deleted !

 

Those who are deleted are:

 

modemst1

modemst2

hob

dhob

fsg

fsc

clogo

keystore

customize

carrier

 

besides userdata, system, cache etc..

 

So after I installed a nougat rom again, but the sim is no longer connected to the network!

If I run 'fastboot getvar imei', I see my original imei but if I do it from the phone it's an imei 0

 

How can I solve?

 

 

 

 

 

Reply
Options

28352 Posts

02-02-2016

United States of America

5842 Signins

132780 Page Views

  • Posts: 28352
  • Registered: ‎02-02-2016
  • Location: United States of America
  • Views: 132780
  • Message 2 of 17

Re: I can no longer connect to the mobile network after "losing" the imei code

2018-10-22, 22:07 PM

moved to developer forum - we don't allow discussion of modded phones in regular forums.


* Search box is your friend * I don't respond to PM if question belongs in forum
Reply
Options

9 Posts

10-22-2018

Italy

6 Signins

124 Page Views

  • Posts: 9
  • Registered: ‎10-22-2018
  • Location: Italy
  • Views: 124
  • Message 3 of 17

Re: I can no longer connect to the mobile network after "losing" the imei code

2018-10-22, 22:13 PM
sorry, ok thx..
Reply
Options

76 Posts

01-21-2017

India

211 Signins

2530 Page Views

  • Posts: 76
  • Registered: ‎01-21-2017
  • Location: India
  • Views: 2530
  • Message 4 of 17

Re: I can no longer connect to the mobile network after "losing" the imei code

2018-10-23, 7:27 AM
Can I share the XDA link for null IMEI fix here?
Arya
Reply
Options

9 Posts

10-22-2018

Italy

6 Signins

124 Page Views

  • Posts: 9
  • Registered: ‎10-22-2018
  • Location: Italy
  • Views: 124
  • Message 5 of 17

Re: I can no longer connect to the mobile network after "losing" the imei code

2018-10-23, 8:48 AM

I have already tried tons of topic on xda without success .

 

I also tried to open the diag port and use qpst and other program but the phone does not go into diagnostic mode via the command 'setprop sys.config.usb diag, adb'

 

.. maybe I should flash those files from another same phone, but some say it did not work that either.

 

Why did Motorola make things so complicated? At this point, perhaps there are better phones and with less risk for modding and more..

Reply
Options

28352 Posts

02-02-2016

United States of America

5842 Signins

132780 Page Views

  • Posts: 28352
  • Registered: ‎02-02-2016
  • Location: United States of America
  • Views: 132780
  • Message 6 of 17

Re: I can no longer connect to the mobile network after "losing" the imei code

2018-10-23, 11:59 AM

 wrote:
Can I share the XDA link for null IMEI fix here?

Yes you can. The Moto developer forum allows such discussions. 

 

And this is not a moto issue. All phones can lose their imei if flashed wrong.  


* Search box is your friend * I don't respond to PM if question belongs in forum
Reply
Options

76 Posts

01-21-2017

India

211 Signins

2530 Page Views

  • Posts: 76
  • Registered: ‎01-21-2017
  • Location: India
  • Views: 2530
  • Message 7 of 17

Re: I can no longer connect to the mobile network after "losing" the imei code

2018-10-23, 12:40 PM

Did you try this one?

Arya
Reply
Options

9 Posts

10-22-2018

Italy

6 Signins

124 Page Views

  • Posts: 9
  • Registered: ‎10-22-2018
  • Location: Italy
  • Views: 124
  • Message 8 of 17

Re: I can no longer connect to the mobile network after "losing" the imei code

2018-10-23, 14:44 PM

 wrote:

Did you try this one?


I tried it now, and it's an interesting thing that can come in handy, but it did not work for me ..


From what I understand, there is a problem with the persist file (since the hdob, hob, fsc etc..files have been deleted)

 

lux:/ # find /persist -type f
/persist/WCNSS_wlan_dictionary.dat
/persist/data/sfs/iwrTKdtvtBAlyJOeEUsNwpp8c68_
/persist/data/sfs/mTM1y9gxs+cPKiwqmKrNvzJu2AE_
/persist/data/sfs/rEioE3MvjUnZr9HR0ybnv81pXEU_
/persist/data/sfs/fIQuNkLirIE+RMib5MQYs40hIZs_
/persist/data/sfs/Cr0YuwxkP6Uk9O2SabFzN9T3KY4_
/persist/data/sfs/TpQVL5B2h9zsbXf5vufr96nMRLY_
/persist/data/sfs/9R8cMLpJ-nB0Hd-dzBN3n+xpsQQ_
/persist/data/sfs/WHhOT5m0ZYQEzOhSHH2LGZzFcrk_
/persist/data/sfs/lTMKY0q5V2aWLRe16IdfHHJTK+c_
/persist/data/sfs/8mGV2zgvRodk4QUzkJgXYhOWQYQ_
/persist/data/sfs/U1Ag3KsfWUQyCxtqB6heoFV8OXw_
/persist/data/sfs/npHBfNlLQWVsw0EFwTeY0PV1mrc_
/persist/data/sfs/-PveJJLeFx8O4fIcKmBr6x-8Yfo_
/persist/data/sfs/+xVjlGmU9I0bFvp1Xmqz0Rr1QTw_
/persist/data/sfs/jFdTRb8-OyOnCIe5jf1fjo-Uqg4_
/persist/data/tz/tz_counter
/persist/data/tz/tz_counter.bak
/persist/data/app_g/wv_usage
/persist/camera/ledcal/rear
/persist/factory/fti
/persist/security/keymaptable.dat
/persist/security/iprm.dat
/persist/mdm/oma_dm_update
/persist/.bt_nv.bin
/persist/bluetooth/.bt_nv.bin
/persist/alarm/powerOffAlarmSet
/persist/.twrps
lux:/ #

and

lux:/ # ls -l /persist
total 184
-rw-r--r-- 1 root      root       10419 2015-08-04 00:43 WCNSS_wlan_dictionary.dat
drwxrwx--- 2 system    system      4096 2016-10-24 12:32 alarm
drwxr-xr-x 2 mot_pwric mot_pwric   4096 1970-01-01 01:00 batt_health
drwxrwx--- 2 bluetooth bluetooth   4096 2017-12-26 20:45 bluetooth
drwxr-xr-x 2 mot_tcmd  bluetooth   4096 1970-01-01 01:00 bt
drwxr-xr-x 3 mot_tcmd  mot_tcmd    4096 1970-01-01 01:00 camera
drwx------ 5 system    system      4096 2018-09-13 13:12 data
drwxrwx--- 2 system    graphics    4096 1970-01-01 01:23 display
drwxrwx--- 2 system    system      4096 1970-01-03 01:26 drm
drwxr-xr-x 2 mot_tcmd  mot_tcmd    4096 2015-08-04 00:43 factory
drwxrwx--- 3 rfs       rfs_shared  4096 1970-01-03 01:26 hlos_rfs
drwx------ 2 root      root        4096 1970-01-01 01:00 lost+found
drwxrwx--- 2 radio     radio       4096 1970-01-03 01:26 mdm
drwxrwx--- 2 system    system      4096 1970-01-03 01:26 misc
drwxr-xr-x 8 mot_tcmd  mot_tcmd    4096 1970-01-01 01:00 public
drwx------ 4 rfs       rfs         4096 1970-01-03 01:26 rfs
drwx------ 2 root      root        4096 1970-01-03 01:26 sds
drwxrws--- 2 mot_tpapi mot_tpapi   4096 2015-12-16 07:57 security
drwxrwx--- 2 system    system      4096 1970-01-03 01:26 sensors
drwxr-xr-x 2 mot_tcmd  mot_tcmd    4096 1970-01-01 01:00 wifi
drwxrwxr-x 2 mot_drm   mot_drm     4096 1970-01-01 01:00 wmdrm
lux:/ #

It seems that there are personal files that are unique and are generated with your id and have a md5, so if I copy them from an equal device these will not work the same, because it are unique ..
I should regenerate maybe, I do not know ..

in my case there are just some files in the file persist and perhaps this does not work well ..

Before while I was trying and "craking" a strange thing happened, I entered the sim card I opened the secret menu with *#*#4636 #*#* and going to sim state and booom for more than 40 seconds my operator had the connection with the signal again at the most!

But as soon as I tried to make a call after a few seconds the line fell ... and again the mobile connection disappeared and it never came back.

So I do not know what happened, before I even tried to fiddle with xposed and modules like device id changer, imei changer, id changer etc..if I do * # 06 # show me my original imei (the one in the box) and even if I go into the settings .. but the network does not come back ..

If I had done a backup now I could restore the lost files, but even here I have some doubts that everything would work well

 

 

Reply
Options

9 Posts

10-22-2018

Italy

6 Signins

124 Page Views

  • Posts: 9
  • Registered: ‎10-22-2018
  • Location: Italy
  • Views: 124
  • Message 9 of 17

Re: I can no longer connect to the mobile network after "losing" the imei code

2018-10-23, 14:47 PM

 wrote:

 wrote:
Can I share the XDA link for null IMEI fix here?

Yes you can. The Moto developer forum allows such discussions. 

 

And this is not a moto issue. All phones can lose their imei if flashed wrong.  


The problem is that motorola could make these files more protected from accidental format and did not do it ..

 

I managed "to spoof" the imei from os ..
first the original one was displayed also from fastboot but it does not work the same ..

 

C:\adb 1> fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8939-80.F3
(bootloader) product: lux
(bootloader) board: lux
(bootloader) secure: yes
(bootloader) hwrev: 0x82C0
(bootloader) radio: 0x4
(bootloader) emmc: 16GB Toshiba REV=07 PRV=00 TYPE=57
(bootloader) ram: 2048MB Samsung S8 SDRAM DIE=4Gb
(bootloader) cpu: MSM8939
(bootloader) serialno: ZY2232F5L9
(bootloader) cid: 0x0007
(bootloader) channelid: 0x40
(bootloader) uid: 2EAA680400000000000000000000
(bootloader) unlocked: yes
(bootloader) securestate: unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) mot_sst: 3
(bootloader) max-download-size: 268435456
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: 358967066237783
(bootloader) meid:
(bootloader) date: 12-17-2015
(bootloader) sku: XT1562
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Tue Oct 23 12:47:57 UTC 2018"
(bootloader) ro.build.fingerprint[0]: motorola/lux_reteu/lux:7.1.1/NPD26
(bootloader) ro.build.fingerprint[1]: .48-24-1/1:user/release-keys
(bootloader) ro.build.version.full[0]: Blur_Version.26.31.1.lux_reteu.re
(bootloader) ro.build.version.full[1]: teu.en.EU
(bootloader) ro.build.version.qcom: LA.BR.1.2.9-01810-8x16.0
(bootloader) version-baseband: M8936_20250112.18.05.38y LUX_EMEA_CUST
(bootloader) kernel.version[0]: Linux version 3.10.49-gd043ad1-00008-gbc
(bootloader) kernel.version[1]: f239c (hudsoncm@ilclbld31) (gcc version
(bootloader) kernel.version[2]: 4.8 (GCC) ) #1 SMP PREEMPT Mon Sep 11 02
(bootloader) kernel.version[3]: :03:43 CDT 2017
(bootloader) sbl1.git: git=MBM-NG-V80.F3-0-gd925c02
(bootloader) rpm.git: git=MBM-NG-V80.F3-0-g932f716
(bootloader) tz.git: git=MBM-NG-V80.F3-0-gcf5b5ba
(bootloader) hyp.git: git=MBM-NG-V80.F3-0-gcf5b5ba
(bootloader) aboot.git: git=MBM-NG-V80.F3-0-g8dc6510
(bootloader) partition-type:modem: raw
(bootloader) partition-type:sbl1: raw
(bootloader) partition-type:DDR: raw
(bootloader) partition-type:aboot: raw
(bootloader) partition-type:rpm: raw
(bootloader) partition-type:tz: raw
(bootloader) partition-type:hyp: raw
(bootloader) partition-type:utags: raw
(bootloader) partition-type:misc: raw
(bootloader) partition-type:padA: raw
(bootloader) partition-type:abootBackup: raw
(bootloader) partition-type:rpmBackup: raw
(bootloader) partition-type:tzBackup: raw
(bootloader) partition-type:hypBackup: raw
(bootloader) partition-type:utagsBackup: raw
(bootloader) partition-type:logs: raw
(bootloader) partition-type:frp: raw
(bootloader) partition-type:padB: raw
(bootloader) partition-type:modemst1: raw
(bootloader) partition-type:modemst2: raw
(bootloader) partition-type:hob: raw
(bootloader) partition-type:dhob: raw
(bootloader) partition-type:fsg: raw
(bootloader) partition-type:fsc: raw
(bootloader) partition-type:cid: raw
(bootloader) partition-type:metadata: raw
(bootloader) partition-type:logo: raw
(bootloader) partition-type:clogo: raw
(bootloader) partition-type:persist: raw
(bootloader) partition-type:kpan: raw
(bootloader) partition-type:boot: raw
(bootloader) partition-type:recovery: raw
(bootloader) partition-type:ssd: raw
(bootloader) partition-type:padC: raw
(bootloader) partition-type:sp: raw
(bootloader) partition-type:keystore: raw
(bootloader) partition-type:customize: raw
(bootloader) partition-type:oem: raw
(bootloader) partition-type:carrier: ext4
(bootloader) partition-type:cache: raw
(bootloader) partition-type:system: raw
(bootloader) partition-type:userdata: raw
(bootloader) partition-size:modem: 0x00000000027e0000
(bootloader) partition-size:sbl1: 0x0000000000080000
(bootloader) partition-size:DDR: 0x0000000000020000
(bootloader) partition-size:aboot: 0x0000000000113000
(bootloader) partition-size:rpm: 0x000000000003e800
(bootloader) partition-size:tz: 0x000000000008c000
(bootloader) partition-size:hyp: 0x0000000000020000
(bootloader) partition-size:utags: 0x0000000000080000
(bootloader) partition-size:misc: 0x0000000000080000
(bootloader) partition-size:padA: 0x000000000036f000
(bootloader) partition-size:abootBackup: 0x0000000000113000
(bootloader) partition-size:rpmBackup: 0x000000000003e800
(bootloader) partition-size:tzBackup: 0x000000000008c000
(bootloader) partition-size:hypBackup: 0x0000000000020000
(bootloader) partition-size:utagsBackup: 0x0000000000080000
(bootloader) partition-size:logs: 0x0000000000200000
(bootloader) partition-size:frp: 0x0000000000080000
(bootloader) partition-size:padB: 0x000000000022f000
(bootloader) partition-size:modemst1: 0x0000000000180000
(bootloader) partition-size:modemst2: 0x0000000000180000
(bootloader) partition-size:hob: 0x000000000007a000
(bootloader) partition-size:dhob: 0x0000000000008000
(bootloader) partition-size:fsg: 0x0000000000180000
(bootloader) partition-size:fsc: 0x0000000000000400
(bootloader) partition-size:cid: 0x0000000000020000
(bootloader) partition-size:metadata: 0x0000000000080000
(bootloader) partition-size:logo: 0x0000000000600000
(bootloader) partition-size:clogo: 0x0000000000600000
(bootloader) partition-size:persist: 0x0000000000800000
(bootloader) partition-size:kpan: 0x0000000000800000
(bootloader) partition-size:boot: 0x0000000002000000
(bootloader) partition-size:recovery: 0x0000000001ffc000
(bootloader) partition-size:ssd: 0x0000000000002000
(bootloader) partition-size:padC: 0x000000000061e000
(bootloader) partition-size:sp: 0x0000000000800000
(bootloader) partition-size:keystore: 0x0000000000800000
(bootloader) partition-size:customize: 0x0000000002000000
(bootloader) partition-size:oem: 0x0000000001000000
(bootloader) partition-size:carrier: 0x0000000001000000
(bootloader) partition-size:cache: 0x0000000030000000
(bootloader) partition-size:system: 0x00000000aa000000
(bootloader) partition-size:userdata: 0x00000002c03e0000
(bootloader) qe: qe 1/1
(bootloader) frp-state: no protection (77)
(bootloader) ro.carrier: reteu
all: listed above
finished. total time: 1.062s
Reply
Options

28352 Posts

02-02-2016

United States of America

5842 Signins

132780 Page Views

  • Posts: 28352
  • Registered: ‎02-02-2016
  • Location: United States of America
  • Views: 132780
  • Message 10 of 17

Re: I can no longer connect to the mobile network after "losing" the imei code

2018-10-23, 14:58 PM

 wrote:

 wrote:

 wrote:
Can I share the XDA link for null IMEI fix here?

Yes you can. The Moto developer forum allows such discussions. 

 

And this is not a moto issue. All phones can lose their imei if flashed wrong.  


The problem is that motorola could make these files more protected from accidental format and did not do it ..

 

 

 


Sorry, I disagree.. most people are not running into this. And besides, when you unlock the bootloader you are saying "I know what I am doing" - if you don't know what you are doing, you should not be erasing ROM or flashing phone. 

 

Samsung users were corrupting EFS partition and losing IMEI many years ago - should Samsung have prevented this? No, it was user error. Same as users taking OTA downloads after flashing and bricking their phones. 

 

If you install Linux on a windows machine and erase part of Windows when partitioning for Linux, should MS have made windows better protected? 

 

If you unlock bootloader, anything and everything you do is now your responsibility. 

 


* Search box is your friend * I don't respond to PM if question belongs in forum
Reply
Forum Home

Community Guidelines

Please review our Guidelines before posting.

Learn More

Check out current deals!

Go Shop
X

Save

X

Delete

X

No, I don’t want to share ideas Yes, I agree to these terms