XT1562 IMEI Issues - X Play Q&A, Help & Troubleshooting

Greetings,
I have an XT1562 which I attempted to flash cm13 on but I was stuck in a bootloop. I read somewhere that using fastboot erase all would fix this problem and indeed it did but at the cost of setting my IMEI to 0. The getvar imei command returns the correct IMEI value. I tried reflashing the modem, reverting to stock, QPST (device manager couldn't detect the COM port) and using dd from TWRP terminal to overwrite hob, dhob and fsc with similar files I found for Moto G. This somewhat helped by restoring 2G functionality but only lasted until reboot. At this point, I am out of ideas, so any assistance is immensely appreciated.

AegisBg said:
Greetings,
I have an XT1562 which I attempted to flash cm13 on but I was stuck in a bootloop. I read somewhere that using fastboot erase all would fix this problem and indeed it did but at the cost of setting my IMEI to 0. The getvar imei command returns the correct IMEI value. I tried reflashing the modem, reverting to stock, QPST (device manager couldn't detect the COM port) and using dd from TWRP terminal to overwrite hob, dhob and fsc with similar files I found for Moto G. This somewhat helped by restoring 2G functionality but only lasted until reboot. At this point, I am out of ideas, so any assistance is immensely appreciated.
Click to expand...
Click to collapse
Flashing the stock rom should have solved this problem.
Sent from my XT1562 using Tapatalk

Related

Developers please help for resolve problem of sim 2 imei 0

because of modem update in hydrogen os 2.5 this whole mess starts pls help
Rohanlovely said:
because of modem update in hydrogen os 2.5 this whole mess starts pls help
Click to expand...
Click to collapse
This new modem firmware is quite unstable, I advise you against using it. My solution to get working second SIM was to restore OOS 3.1 modem and format modemst1, modemst2 and persist partitions. Not until after formatting the partitions did it work again (CM14 keept rebooting/crashing).
pitrus- said:
This new modem firmware is quite unstable, I advise you against using it. My solution to get working second SIM was to restore OOS 3.1 modem and format modemst1, modemst2 and persist partitions. Not until after formatting the partitions did it work again (CM14 keept rebooting/crashing).
Click to expand...
Click to collapse
How u got back the sim 2 working ?
pitrus- said:
This new modem firmware is quite unstable, I advise you against using it. My solution to get working second SIM was to restore OOS 3.1 modem and format modemst1, modemst2 and persist partitions. Not until after formatting the partitions did it work again (CM14 keept rebooting/crashing).
Click to expand...
Click to collapse
how do you format the partitions? through TWRP? so steps are, flash oos 3.1 then format the modemst1 and 2?
Rohandd said:
how do you format the partitions? through TWRP? so steps are, flash oos 3.1 then format the modemst1 and 2?
Click to expand...
Click to collapse
Sim 2 start working after that ?? U tried that ?
Like I said, both SIM cards work again after flashing OOS 3.1 ROM (or firmware files manually) and then using the ordinary fastboot format command to format modemst1 and modemst2, then used fastboot flash persist persist.img with the persist partition dump found in this forum.
pitrus- said:
Like I said, both SIM cards work again after flashing OOS 3.1 ROM (or firmware files manually) and then using the ordinary fastboot format command to format modemst1 and modemst2, then used fastboot flash persist persist.img with the persist partition dump found in this forum.
Click to expand...
Click to collapse
could you please list out the exact steps you have done to fix your issue?
there are many users who are getting this issue including me.
please list the steps with the links of files you flashed. it would be a great help.
​
pitrus- said:
Like I said, both SIM cards work again after flashing OOS 3.1 ROM (or firmware files manually) and then using the ordinary fastboot format command to format modemst1 and modemst2, then used fastboot flash persist persist.img with the persist partition dump found in this forum.
Click to expand...
Click to collapse

			
				
https://drive.google.com/file/d/0B9IqSEI0OM37RTM5M09Ib180U0E/view
I got it
Persist.img for oneplus 2?
Rohanlovely said:
https://drive.google.com/file/d/0B9IqSEI0OM37RTM5M09Ib180U0E/view
I got it
Persist.img for oneplus 2
Click to expand...
Click to collapse
Did you tried with this??
any fix??
ashu01 said:
Did you tried with this??
any fix??
Click to expand...
Click to collapse
My laptop windows crashed after repairing that i will try
Rohanlovely said:
My laptop windows crashed after repairing that i will try
Click to expand...
Click to collapse
can you join this telegram group link
https://telegram.me/joinchat/CbL5zUA-vInKg1B5M8baqQ
Had the same problem
Hi,
Just to give you all a quick background. I was in the same situation as you. Flashed H2OS didn't like the jumpy signal therefore wanted to go back to OOS.
First boot of OOS resulted in no connectivity (no wifi, no data, no Bluetooth). I followed the method above and deleted modemst1 and modemst2 and formatted modemst (all done thru fastboot)
Once I did that I was able to boot into OOS to get the signals. As petris said above, wiping and then booting into the software results in a fresh re-write of those modem partitions.
At this point I factory resetted the OOS software (just to be safe) and also installed the stock recovery (somehow my device wasn't booting into TWRP everytime I installed it).
After the factory reset I checked my IMEI's and saw my IMEI2 as 0. Luckily I don't use slot 2 so getting it to show IMEI wasn't a priority. However my camera wasn't working. Everytime I opened up the camera it would show a black screen for 30 seconds and then close with a message showing "Unknown error"
At this point I tried searching the persist.img file that someone suggested in this thread. I downloaded that from google drive and clean flashed it thru fastboot.
After a reboot I was able to get the camera working again.
So all in all for now everything works as expected. I am on the latest OOS 3.1.0 software and have no intentions of doing anything else until there is fix for IMEI2. I am regularly checking oneplus forums where people like me have esclated the issues. I think on the recognized developers Naman is working for a fix and seeing into this issue.
TLDR : IMEI2 shows 0
ashu01 said:
can you join this telegram group link
https://telegram.me/joinchat/CbL5zUA-vInKg1B5M8baqQ
Click to expand...
Click to collapse
now new is problem started in my mobile telegram guys i able start d 2nd sim in my mobile but now sim 1 imei is 0
Rohanlovely said:
https://drive.google.com/file/d/0B9IqSEI0OM37RTM5M09Ib180U0E/view
I got it
Persist.img for oneplus 2
Click to expand...
Click to collapse
u tried it? works?
lockmunk said:
u tried it? works?
Click to expand...
Click to collapse
I tried and was fine.
First i did full wipe, then flash this zip + any rom and rom started fine.
pitrus- said:
Like I said, both SIM cards work again after flashing OOS 3.1 ROM (or firmware files manually) and then using the ordinary fastboot format command to format modemst1 and modemst2, then used fastboot flash persist persist.img with the persist partition dump found in this forum.
Click to expand...
Click to collapse
I get this error while trying to format modem
formatting 'modemst1' partition... Formatting is not supported for filesystem with type ''. FAILED ()
---------- Post added at 07:45 PM ---------- Previous post was at 07:43 PM ----------
rajatdixit said:
Hi,
Just to give you all a quick background. I was in the same situation as you. Flashed H2OS didn't like the jumpy signal therefore wanted to go back to OOS.
First boot of OOS resulted in no connectivity (no wifi, no data, no Bluetooth). I followed the method above and deleted modemst1 and modemst2 and formatted modemst (all done thru fastboot)
Once I did that I was able to boot into OOS to get the signals. As petris said above, wiping and then booting into the software results in a fresh re-write of those modem partitions.
At this point I factory resetted the OOS software (just to be safe) and also installed the stock recovery (somehow my device wasn't booting into TWRP everytime I installed it).
After the factory reset I checked my IMEI's and saw my IMEI2 as 0. Luckily I don't use slot 2 so getting it to show IMEI wasn't a priority. However my camera wasn't working. Everytime I opened up the camera it would show a black screen for 30 seconds and then close with a message showing "Unknown error"
At this point I tried searching the persist.img file that someone suggested in this thread. I downloaded that from google drive and clean flashed it thru fastboot.
After a reboot I was able to get the camera working again.
So all in all for now everything works as expected. I am on the latest OOS 3.1.0 software and have no intentions of doing anything else until there is fix for IMEI2. I am regularly checking oneplus forums where people like me have esclated the issues. I think on the recognized developers Naman is working for a fix and seeing into this issue.
TLDR : IMEI2 shows 0
Click to expand...
Click to collapse
Did u get such type of an error:
formatting 'modemst1' partition... Formatting is not supported for filesystem with type ''. FAILED ()
If not just tel me the steps u followed
ashokmor007 said:
I get this error while trying to format modem
formatting 'modemst1' partition... Formatting is not supported for filesystem with type ''. FAILED ()
---------- Post added at 07:45 PM ---------- Previous post was at 07:43 PM ----------
Did u get such type of an error:
formatting 'modemst1' partition... Formatting is not supported for filesystem with type ''. FAILED ()
If not just tel me the steps u followed
Click to expand...
Click to collapse
Make sure your bootloader is unlocked
rajatdixit said:
Make sure your bootloader is unlocked
Click to expand...
Click to collapse
yes it is unlocked

XT1642: IMEI show as 0 (even after reflashing to original unrooted)

Hi,
I have G4 Plus XT1642 (retapac). It came shipped with 6.0.1 MPJ24.139-48 preinstalled.
Well i flashed, deleted, maybe bricked and then made it work again with the latest version i wanted to have (139-63) and then rooted it. Everything worked/works, but the wifi mac shows as 02 000000 or something (but no problem with that, wifi mac is fixed with some earlier backup i have, it also gets fixed when i flash to original).
But the worst thing is: Both IMEI show as 0. In the setting menu, and also when dialing the command *#06# (Both IMEIs show 0).
It gave some errors at fastboot because of "downgrade" or so, but i think that's not the issue.
I tried everything, also reflashed to my original version (ATHENE_MPJ24.139-48_cid50_subsidy-DEFAULT_CFC.xml.zip). Everything is fine, wifi mac displays as original also, but IMEIs still are 0.
No matter what I do, both IMEI show as 0, and SIM cards don't work ofcourse (they work, show carrier names etc but don't get accepted, ---> "emergency calls only", because IMEI is 0 i think.
Before you ask: No i don't have a very early TWRP backup from before flashing, deleted it because I had later backup I though everything was working, didn't try any SIM at that time.
How can I fix this? Is there any hope?
What gives me the little hope: At "boot thing" when I type fastboot getvar imei, it shows the correct imei! It doesn't list the second sim though.
Thanks in advance!
bauss1 said:
Hi,
I have G4 Plus XT1642 (retapac). It came shipped with 6.0.1 MPJ24.139-48 preinstalled.
Well i flashed, deleted, maybe bricked and then made it work again with the latest version i wanted to have (139-63) and then rooted it. Everything worked/works, but the wifi mac shows as 02 000000 or something (but no problem with that, wifi mac is fixed with some earlier backup i have, it also gets fixed when i flash to original).
But the worst thing is: Both IMEI show as 0. In the setting menu, and also when dialing the command *#06# (Both IMEIs show 0).
It gave some errors at fastboot because of "downgrade" or so, but i think that's not the issue.
I tried everything, also reflashed to my original version (ATHENE_MPJ24.139-48_cid50_subsidy-DEFAULT_CFC.xml.zip). Everything is fine, wifi mac displays as original also, but IMEIs still are 0.
No matter what I do, both IMEI show as 0, and SIM cards don't work ofcourse (they work, show carrier names etc but don't get accepted, ---> "emergency calls only", because IMEI is 0 i think.
Before you ask: No i don't have a very early TWRP backup from before flashing, deleted it because I had later backup I though everything was working, didn't try any SIM at that time.
How can I fix this? Is there any hope?
What gives me the little hope: At "boot thing" when I type fastboot getvar imei, it shows the correct imei! It doesn't list the second sim though.
Thanks in advance!
Click to expand...
Click to collapse
https://firmware.center/firmware/Motorola/Moto G4 (Plus)/Stock/XT1642/
#for marshmallow
Try to flash modem files for your phone
https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369
#for nougat
BlackBeats said:
https://firmware.center/firmware/Motorola/Moto G4 (Plus)/Stock/XT1642/
#for marshmallow
Try to flash modem files for your phone
https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369
#for nougat
Click to expand...
Click to collapse
Yes. Did exactly that. Flashed the files of XT1642_ATHENE_6.0.1_MPJ24.139-48_cid50_subsidy-DEFAULT_CFC.xml.zip ... with the commands
Code:
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 modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
fastboot reboot
Showed some "errors" at fastboot at some, but I think that was normal. And flashing worked.
But in the end, both IMEI are still 0.
Even reflashed the NON-HLOS.bin. IMEI numbers are still 0.
Additional information:
The original version this retapac XT1642 G4 plus came shipped with was MPJ24.139-48.
I then wanted to update to the latest non-nougat version, which is MPJ24.139-63.
I could not update directly to MPJ24.139-63 from MPJ24.139-48. (Because the internal recovery showed error, that flashed version must origin from MPJ24.139-23.4).
So I overflashed (with fastboot) to MPJ24.139-23.4. So the version then was even lower than it came shipped with lol. Then from MPJ24.139-23.4, used the internal recovery (not TWRP), to apply the OTA update file MPJ24.139-63. Since then the Wifi mac was 020000000 or something, sometimes random wifi disconnects, and imei 0. After going back to original again, wifi mac is fixed, but sim imei numbers still are 0.
Edit: not sure if the imei and wifi errors accured since MPJ24.139-23.4, or after the OTA update file, or sometime inbetween because i deleted something in TWRP.
bauss1 said:
Additional information:
The original version this retapac XT1642 G4 plus came shipped with was MPJ24.139-48.
I then wanted to update to the latest non-nougat version, which is MPJ24.139-63.
I could not update directly to MPJ24.139-63 from MPJ24.139-48. (Because the internal recovery showed error, that flashed version must origin from MPJ24.139-23.4).
So I overflashed (with fastboot) to MPJ24.139-23.4. So the version then was even lower than it came shipped with lol. Then from MPJ24.139-23.4, used the internal recovery (not TWRP), to apply the OTA update file MPJ24.139-63. Since then the Wifi mac was 020000000 or something, sometimes random wifi disconnects, and imei 0. After going back to original again, wifi mac is fixed, but sim imei numbers still are 0.
Click to expand...
Click to collapse
Try flashing nougat I guess downgrade created a problem
BlackBeats said:
Try flashing nougat I guess downgrade created a problem
Click to expand...
Click to collapse
I don't want nougat. Can I go back to MPJ24.139-63 from nougat? But maybe worth a try if nobody knows any other possibility
bauss1 said:
I don't want nougat. Can I go back to MPJ24.139-63 from nougat? But maybe worth a try if nobody knows any other possibility
Click to expand...
Click to collapse
Try removing oem fb set command
If it doesn't work then flash nougat then use 6.0.1 custom ROM
Edit fb_mode_set
Flashed everything again, without the fastboot oem fb_mode_set (MPJ24.139-48). Both IMEIs are still 0, everything else is fine though, original wifi mac.
---
Then took original over the air update it offered me (NPJ25.93-14). Installed without problems.
But, guess what.... it made things worse.
Now i am on NPJ25.93-14, the IMEIs still are 0, and the wifi mac address is at 02:00:00:00:00:00 again.
What I noticed is, in settings it shows the IMEI SV (Slot1) and IMEI SV (Slot2). They both changed to 08. I think they were 03 or so before.
Edit: In the boot recovery thing it says the usual stuff:
Battery OK (Charging)
flashing_unlocked
Software status: Official
...
So... updating to Nougat did not help, made things worse (wifi mac weird again, IMEI still 0).
Any other ideas?
Anyone looking for the solution to this problem, it has been fixed here: [Guide] [XT16XX] [Solve] Moto G4/Plus IMEI=0 issue

Ruined my modem partition... Please help

i downloaded factory image of 7.12.29 oreo
i used flash_factory.bat
it reflashed partitioning
apparently it had a command "fastboot flash modem_a NON-HLOS.bin"
the NON-HLOS.bin file does not exist in images folder nor in any fastboot rom
now i dont have any connectivity... signal.. wifi etc..
can anybody provide NON-HLOS.bin file for the A1
Hello,
Inside the fastboot ROM file "tissot_images_7.12.19_20171219.0000.00_7.1_d39fa89aaf.tgz" (Nougat 7.1.2) ... in the file "flash_all_lock_crc.bat" for example, these lines appear:
fastboot %* flash modem_a %~dp0images\modem.img || @ECHO "Flash modem_a error" && exit /B 1
fastboot %* flash modem_b %~dp0images\modem.img || @ECHO "Flash modem_b error" && exit /B 1
It seems that the file is called "modem.img", not "NON-HLOS.bin".
May be?
Regards!
PS: Sorry for my English!
i managed to flash all images from fast boot to partitions manually step by step
except something called fsg and persist partitions
which i managed to flash through twrp using dd command via terminal
now it boots but i dont have imei number "says imei number unknown"
and it reboots after less than a minute
i read something about qcn file restore and editing from another mi A1
and that i can edit it to put my imei numbers back
anybody please provide a valid qcn number and how can i restore it
m.hashem said:
i managed to flash all images from fast boot to partitions manually step by step
except something called fsg and persist partitions
which i managed to flash through twrp using dd command via terminal
now it boots but i dont have imei number "says imei number unknown"
and it reboots after less than a minute
i read something about qcn file restore and editing from another mi A1
and that i can edit it to put my imei numbers back
anybody please provide a valid qcn number and how can i restore it
Click to expand...
Click to collapse
if it is under warranty just brick your phone and give it to service centre they will flash it and give you back
m.hashem said:
i downloaded factory image of 7.12.29 oreo
i used flash_factory.bat
it reflashed partitioning
apparently it had a command "fastboot flash modem_a NON-HLOS.bin"
the NON-HLOS.bin file does not exist in images folder nor in any fastboot rom
now i dont have any connectivity... signal.. wifi etc..
can anybody provide NON-HLOS.bin file for the A1
Click to expand...
Click to collapse
i have same problem last night
then i reflash 7.12.19 using miflash 2016.08.30.0
my imei normal again
Wow! The file NON-HLOS.bin is the modem for other Xiaomi phone. May be you use a batch file (flash_factory.bat) for other phone, not Mi A1. Please use Mi Flash with right rom.
this is method not working
bangir said:
i have same problem last night
then i reflash 7.12.19 using miflash 2016.08.30.0
my imei normal again
Click to expand...
Click to collapse
this is method not working
gautamaurya said:
this is method not working
Click to expand...
Click to collapse
What happens if you try to re-flash your modem with the flash_all or flash_all_except_storage scripts from here: https://forum.xda-developers.com/mi-a1/how-to/ota-official-fastboot-image-n2g47h-7-12-t3728929 ?
Can you please report, if it works and if should not work, please attach the terminal/ shell outpout of the failed flashing attempt here.
modemst1 and modemst2
hey ... i managed to flash the fastboot rom via miflash via hsusb 9008 mode through miflash tool (run as administrator)
the remainig problem is 2 partitions modemst1 and modemst2
which are dev/block/mmcblk0p14 & 15 respectively
can somebody please send me a backup of modemst1 and modemst2
it's doable via twrp
fastboot boot twrp3.1.1.1.img
advanced
terminal
dd if=/dev/block/mmcblk0p14 of=/sdcard/modemst1.img
dd if=/dev/block/mmcblk0p15 of=/sdcard/modemst2.img
i'll flash them back and edit the imei numbers via hex after qcn backup
thanks everybody
m.hashem said:
hey ... i managed to flash the fastboot rom via miflash via hsusb 9008 mode through miflash tool (run as administrator)
the remainig problem is 2 partitions modemst1 and modemst2
which are dev/block/mmcblk0p14 & 15 respectively
can somebody please send me a backup of modemst1 and modemst2
it's doable via twrp
fastboot boot twrp3.1.1.1.img
advanced
terminal
dd if=/dev/block/mmcblk0p14 of=/sdcard/modemst1.img
dd if=/dev/block/mmcblk0p15 of=/sdcard/modemst2.img
i'll flash them back and edit the imei numbers via hex after qcn backup
thanks everybody
Click to expand...
Click to collapse
I have done some digging in order to assist you to get this fixed. I think I have 2 very hot leads (untested as I don't have any issues with my IMEI):
1. http://www.androidbrick.com/ultimat...agon-xiaomi-mi5-imei-and-baseband-repair-fix/ & http://www.androidbrick.com/ultimate-guide-qualcomm-snapdragon-imei-baseband-repair-fix-part-2/
2. https://androidmtk.com/use-qualcomm-smartphone-write-imei-tool (looks almost to easy, but worth a try?)
Please report your feedback here
hey bro how to the editting modem1st.img
m.hashem said:
i downloaded factory image of 7.12.29 oreo
i used flash_factory.bat
it reflashed partitioning
now i dont have any connectivity... signal.. wifi etc..
Click to expand...
Click to collapse
Hello!
I made the same mistake. Is there a way to solve this problem?
m.hashem said:
i downloaded factory image of 7.12.29 oreo
i used flash_factory.bat
it reflashed partitioning
apparently it had a command "fastboot flash modem_a NON-HLOS.bin"
the NON-HLOS.bin file does not exist in images folder nor in any fastboot rom
now i dont have any connectivity... signal.. wifi etc..
can anybody provide NON-HLOS.bin file for the A1
Click to expand...
Click to collapse
Same problem here. Phone doesn't work correctly now. Boots, freezes and reboots. :crying:
persist image problem
https://xiaomifirmware.com/guides-and-tips/restore-persist-partition-xiaomi-mi-a1/
try ghis to restore persist img from twrp see if it fixes the freeze and reboot problem
also download the persist.img from the guide not from a fastboot rom... it should be 32 mb in size
i actually bricked my phone via doing fastboot flash partition partition-both-gpt.bin from fastboot folder then fastvoot reboot.... warning this bricks the phone completely... theres no bootloader now... i gave it to service center... ill take my chances for replacement
m.hashem said:
https://xiaomifirmware.com/guides-and-tips/restore-persist-partition-xiaomi-mi-a1/
try ghis to restore persist img from twrp see if it fixes the freeze and reboot problem
also download the persist.img from the guide not from a fastboot rom... it should be 32 mb in size
i actually bricked my phone via doing fastboot flash partition partition-both-gpt.bin from fastboot folder then fastvoot reboot.... warning this bricks the phone completely... theres no bootloader now... i gave it to service center... ill take my chances for replacement
Click to expand...
Click to collapse
thank you very much broo my device is fixed freezee and reboots problem
Ok. But what is the persist partition? Someone tried already? Doesn't want to brick my phone completely.
how to the editting qcn file beacuse my imei 0 null please help me editting brother
m.hashem said:
https://xiaomifirmware.com/guides-and-tips/restore-persist-partition-xiaomi-mi-a1/
try ghis to restore persist img from twrp see if it fixes the freeze and reboot problem
also download the persist.img from the guide not from a fastboot rom... it should be 32 mb in size
i actually bricked my phone via doing fastboot flash partition partition-both-gpt.bin from fastboot folder then fastvoot reboot.... warning this bricks the phone completely... theres no bootloader now... i gave it to service center... ill take my chances for replacement
Click to expand...
Click to collapse
The freeze and reboot problem is fixed. Thanks. Still one problem. IMEI1 is 0 and IMEI2 is null. Anyone has an idea?
Nordland_ua said:
Hello!
I made the same mistake. Is there a way to solve this problem?
Click to expand...
Click to collapse
Me tooo
Sent from my Mi A1 using Tapatalk
https://www.androidfilehost.com/?fid=673956719939818468
Replace the IMEi with UR Own IMEI . if not it's illegal to use this QCN
Password : testnreport
if you don't know how to change IMEI Using hex editor , try my method . DO NOT use QCN to restore .
(hex and imei provided in order for u to find n replace)
i lost my imei n spent me about 6days n 8 hours per day to find a way to fix it .
actually it's easy to fix the problem .
My own method
1. download the older rom (7.8.23) Link
2. Use flash_all.bat
3.reboot into fastboot mode , erase modemst1 and modemst2 .
fastboot erase modemst1
fastboot erase modemst2
4. reboot
5. go to phone , enter *#*#717717#*#*
6.got to settings enable USB Debugging (ADB)
7. disconnect your phone n connect it back
8.Use WriteDualIMEI(W+G_eMMC) Remember run as administrator , enter your IMEI .
9.if success , go to phone enter *#*#717717#*#* to disable the diag port
10. reboot
Done .

xt1768 imei 0

I picked up a Moto E4 (perry) xt1768 for Lineage OS. I don't know if it was something I did (one of my earlier builds failed to boot) or was already like that, but I found out after I put in a SIM when Lineage 14.1 seemed to be otherwise running OK, that the phone says IMEI is 0, radio is off, and won't connect to network. fastboot getvars does show a reasonable value but no ROM I have tried can see it.
I searched for possible fixes, tried reflashing stock with and without SIM inserted etc, but so far nothing I tried has helped. Any new ideas?
aaopt said:
I picked up a Moto E4 (perry) xt1768 for Lineage OS. I don't know if it was something I did (one of my earlier builds failed to boot) or was already like that, but I found out after I put in a SIM when Lineage 14.1 seemed to be otherwise running OK, that the phone says IMEI is 0, radio is off, and won't connect to network. fastboot getvars does show a reasonable value but no ROM I have tried can see it.
I searched for possible fixes, tried reflashing stock with and without SIM inserted etc, but so far nothing I tried has helped. Any new ideas?
Click to expand...
Click to collapse
Try
Code:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
Sent from my mata using XDA Labs
sd_shadow said:
Try
Code:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
Sent from my mata using XDA Labs
Click to expand...
Click to collapse
Thanks for responding but I guess my multiple attempts to flash to stock already included those commands. Only thing is that the flash script has fsg before modemst1/2, but I presume the order should not matter.
aaopt said:
Thanks for responding but I guess my multiple attempts to flash to stock already included those commands. Only thing is that the flash script has fsg before modemst1/2, but I presume the order should not matter.
Click to expand...
Click to collapse
It does matter
Sent from my Moto E (4) using Tapatalk
aaopt said:
I picked up a Moto E4 (perry) xt1768 for Lineage OS. I don't know if it was something I did (one of my earlier builds failed to boot) or was already like that, but I found out after I put in a SIM when Lineage 14.1 seemed to be otherwise running OK, that the phone says IMEI is 0, radio is off, and won't connect to network. fastboot getvars does show a reasonable value but no ROM I have tried can see it.
I searched for possible fixes, tried reflashing stock with and without SIM inserted etc, but so far nothing I tried has helped. Any new ideas?
Click to expand...
Click to collapse
Hi
have a look here
[allaboutflashing-dot c o m /motorola-e4-mediatek-xt1762-imei-repair-without-box-free-solution/]
Hi,
I have the same problem with XT1768//Moto E4 Amazon prime one // bootloader locked // Qualcomm Snapdragon chip.
It's my wife phone, issue(null imei) appear out of the blue...
I did try the above fastboot commands with files got from here: https://firmwarefile.co/flash-file-motorola-moto-e4-xt1768-firmware-download-stock-rom/
but without success...same null IMEI.
Do you have any ideas how to fix the Qualcomm E4 ? thanks

IMEI 0 after Fastboot erase commands

I have Lenovo K6 Power K33a42 which had network issue. Either of the sims worked at any time on whichever sim the mobile data was enabled. I referred XDA forums and based on suggestions ran these commands
adb reboot bootloader
fastboot erase modemst1
fastboot erase modemst2
fastboot reboot
After which networks of both sims weren't connecting. On checking IMEI 1 AND 2 found it was 0. The baseband is however intact.
I have done factory reset which didnt help, even flashed through Rescue and Smart Assistant tool yet the IMEI 0.
I am pretty sure many had faced this and there could be working solution, kindly share the solution to restore IMEI number.
Note that, I have the phone box which has IMEI number.
There could be many ways of dealing this, each and every one of yours solution may help. Kindly share.

Categories

Resources