Sunday, 17 July 2016

IMEI=0 problem.Everything we know till now.



Hi guys.

Disclaimer:


Quote:









Changing or messing up with IMEI may be banned in your area or country of residence. Please check with your local regulations before attempting to modify the IMEI and related information of your phone. I take no responsibility whatsoever for your attempts to change any such information. This thread does not support in anyway to deliberately modify the identity of the phone.




1. PDS partition does not determine IMEI.
As you know PDS is actually at /dev/block/mmcblk0p26 or /dev/block/platform/msm_sdc.1/by-name/pds. When the phone boot it mounts this partition at /pds. After blowng up my IMEI, this partition was still mounting at /pds and had data untouched in it. So this partition is really not important. Also i read on another thread, people with backup also cud not restore their IMEI.

2.When giving command "fastboot erase all", the following partitions are erased:
a. hob (located at /dev/block/platform/msm_sdcc.1/by-name/hob)
b. dhob (located at /dev/block/platform/msm_sdcc.1/by-name/dhob)
c. fsc (located at /dev/block/platform/msm_sdcc.1/by-name/fsc)
There are other partitions erased as well such as fsg,modemst1, modemst2 etc. But these partitions are restored when we flash stock ROM. So they can be taken out of picture.

Possible solutions:

1.Restoring a QCN backup through QPST after putting the phone in BP Tools mode.

Unfortunately this doesn't work as the NV area of the Moto E2(possibly all motos) is write protected.i.e,we won't be able to restore the modified qcn file.

So no luck here.

2.Restoring fsc,hob and dhob files from a working Moto E 2015.

This is something that could work.

As confirmed by many users,restoring these partitions from a working device gives back the radio functionalities but not the IMEI.

If any has more info,they are more than welcome.

Let's get these babies working again.

Sources:http://forum.xda-developers.com/moto...imei0-t2925970 and ofcourse me(solutions part).



No comments:

Post a Comment