XT1640 no service after update to 8.1

echo92

Senior Member
Jan 1, 2017
3,730
1,987
223
Plymouth
I confidently say that this file I did installed

Sent from my G4 Plus using XDA Labs
If you've flashed stock Oreo 8.1, that file might not do much since your permissions should be updated. It won't hurt though.

You're certain you did not flash any other persist images whilst trying to fix your device? Just that your persist files list looked unusual as heeth21 mentioned
 

echo92

Senior Member
Jan 1, 2017
3,730
1,987
223
Plymouth
Sent from my G4 Plus using XDA Labs
Hmm, I just loaded up the persist details from my device and comparing them to your device, there seem to be quite a few things missing. I do not know if that's expected or if something happened to your persist from the earlier flashes/attempts to repair. However, I cannot advise you to flash the persist image from my device - doing so would mean losing the persist image unique to your device and make it impossible to repair unless you made a backup. (Note again, I do not mean the TWRP persist fix file - that is okay to flash since all it does is repair permissions. I am referring to a persist image obtained from another device, which is flashed over your device's persist image that causes these issues.) For reference, I've posted my persist and the files that seem to be missing/different to yours are in bold formatting:
Code:
athene_f:/ # find /persist -type f
/persist/coresight/qdss.agent.sh
/persist/coresight/qdss.config.sh
/persist/coresight/qdss.functions.sh
/persist/sensors/sensors_settings
[B]/persist/data/sfs/7mLKiiOHb38oWJOzMMgT1MJTuc8_
/persist/data/sfs/okknld0N60fHVxB75aMrYq7zPfo_
/persist/data/sfs/Gzq2vgdYuPNmo2ogNpKaWoxHA0g_
/persist/data/sfs/4GActXHfqptJhhS7vCRMKD+0o+4_
/persist/data/sfs/aOrpxVxYpTOmCc-fuhWWMcviurM_
/persist/data/sfs/CjqM3QO0MLXGyjpByH6FdPMKnQw_
/persist/data/sfs/V099eO8L1QQNgWO5y9Uycia-3Lk_
[/B]/persist/data/tz/tz_counter
/persist/data/tz/tz_counter.bak
/persist/data/app_g/wv_usage
/persist/camera/focus/offset_cal
/persist/camera/ledcal/rear
/persist/factory/audio/temp
/persist/factory/audio/cnt
/persist/factory/audio/acc
/persist/factory/audio/f0
/persist/factory/audio/ref_diff
/persist/factory/fti
/persist/public/hiddenmenu/data/mobile_data_rx
/persist/public/hiddenmenu/data/mobile_data_tx
/persist/public/hiddenmenu/data/wifi_data_rx
/persist/public/hiddenmenu/data/wifi_data_tx
/persist/public/hiddenmenu/data/activation_date
[B]/persist/public/hiddenmenu/data/factoryreset_time[/B]
/persist/public/hiddenmenu/life_calls
/persist/public/hiddenmenu/life_timer
[B]/persist/security/18.bin[/B]
/persist/mdm/oma_dm_update
/persist/rfs/shared/server_info.txt
[B]/persist/rfs/msm/mpss/datablock/id_00
/persist/rfs/msm/mpss/datablock/id_01[/B]
/persist/rfs/msm/mpss/server_check.txt
/persist/rfs/msm/mpss/dhob.bin
/persist/rfs/msm/mpss/shob.bin
/persist/rfs/msm/adsp/server_check.txt
/persist/.bt_nv.bin
/persist/bluetooth/.bt_nv.bin
[B]/persist/alarm/powerOffAlarmSet
/persist/alarm/timezone
/persist/alarm/powerOffAlarmInstance[/B]
/persist/time/ats_1
[B]/persist/time/ats_12
/persist/time/ats_13[/B]
/persist/time/ats_2
/persist/time/ats_16
[B]/persist/time/ats_15[/B]
athene_f:/ #
As heeth21 has mentioned, your persist is missing /persist/rfs/msm/mpss/datablock/id_00
and /persist/rfs/msm/mpss/datablock/id_01 at least, and I do not know how to generate them even if you can. For added reference, this persist was generated from a XT1642 (retgb) running stock 8.1 Oreo, with an EMEA baseband.
 

echo92

Senior Member
Jan 1, 2017
3,730
1,987
223
Plymouth
Please share that the link XT1642 (retgb) stock Oreo 8.1.0 I will try it bro
As I mentioned, I cannot advise you flash my persist image onto your device. Doing so, unless you have a back up, will likely damage your device permanently since the encrypted IMEI in my persist would not match up with the IMEI on your device, do you'd have no service. The IMEI fix thread and other threads have mentioned if you flash another device's persist image to your device, there is no way to fix your device. The TWRP IMEI fix flash is okay to use. Thus, I will not provide this file.

It's the same Oreo firmware as you've been installing, OPJ28.111-22
 
Last edited:

echo92

Senior Member
Jan 1, 2017
3,730
1,987
223
Plymouth
Do can I go to repair center? Maybe it's working:confused:
Could always go to the nearest repair centre, see if they can do anything. They may say that your device needs a motherboard replacement, however, which would be rather expensive (8000 rupees or more, from what I understand).
 

Tetcare99

Senior Member
Jan 15, 2019
60
10
0
As I mentioned, I cannot advise you flash my persist image onto your device. Doing so, unless you have a back up, will likely damage your device permanently since the encrypted IMEI in my persist would not match up with the IMEI on your device, do you'd have no service. The IMEI fix thread and other threads have mentioned if you flash another device's persist image to your device, there is no way to fix your device. The TWRP IMEI fix flash is okay to use. Thus, I will not provide this file.

It's the same Oreo firmware as you've been installing, OPJ28.112
If I lost that imei stored file But why it's showing (imei numbers) from fastboot command
 

echo92

Senior Member
Jan 1, 2017
3,730
1,987
223
Plymouth
If I lost that imei stored file But why it's showing (imei numbers) from fastboot command
Your device has still got a persist file - else the commands from step 1 and 2 of the IMEI thread would not work. Normally, you do not see the persist partition unless you use dd commands or root commands.

The fact you can still see your IMEI suggests your device still has it stored, but for some reason your firmware/persist partition cannot properly read the IMEI and use the IMEI to get your SIM network working. The missing files from your persist partition might be responsible for this, but I do not know how your persist file got like that. I do not know if those tools you mentioned using (https://forum.xda-developers.com/showpost.php?p=79596036&postcount=699) would have done anything.

Unless someone else has ideas or the paid service can help you, the easiest way to fix this would be to pay for a motherboard replacement or a new device. I don't know if we have methods of repairing a persist partition. Attempting to replace your persist partition with another persist partition from a working device appears to be a really bad idea and not recommended.
 
Last edited:

Jasman singh

Member
Feb 18, 2018
20
1
0
I am asking that when you flashed the Oreo OTA, did you observe DFLT_FSG in your baseband?

You could try:

Download the factory firmware here: https://forum.xda-developers.com/showpost.php?p=76406797&postcount=11 Do not flash this firmware.

Extract the firmware, and open the extracted firmware folder.

Find the programutags.bat in the folder.

Run the .bat script and follow the instructions.

Credit to: https://forum.xda-developers.com/moto-g4/how-to/baseband-change-t3762270
i tried to download the file from the website but it is not downloading and when i tried to download it from another website and extract the files from it just like the website said it shows that the file is corrupt any solution?
 
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone