XT1640 no service after update to 8.1

[Tetcare99]

Was your device booted to fastboot for this procedure, as requested by the script? Does your device properly communicate with your computer in fastboot (i.e. if you type fastboot devices into an ADB terminal, does your device respond with its serial number)?

I did it but there is no changes:crying:

 

[echo92]

I did it but there is no changes:crying:

Still no signal? Can I see the results of the persist check from step 1 and step 2 of the IMEI thread please, as previously asked for?

 

[Tetcare99]

Still no signal? Can I see the results of the persist check from step 1 and step 2 of the IMEI thread please, as previously asked for?

It's showing something bro..

athene_f:/ $ su
athene_f:/ # chown -R rfs:rfs/persist/rfs
See chown --help
chown: Need 2 arguments
1|athene_f:/ # chown -R rfs:rfs_shared/persist/hlos/rfs
See chown --help
chown: Need 2 arguments
1|athene_f:/ # chown -R 3012:3012/persist/rfs
See chown --help
chown: Need 2 arguments
1|athene_f:/ # chown -R 3012:3013/persist/hlos_rfs
See chown --help
chown: Need 2 arguments
1|athene_f:/ #

---------- Post added at 01:35 PM ---------- Previous post was at 01:31 PM ----------

athene_f:/ $ su
athene_f:/ # chown -R rfs:rfs/persist/rfs
See chown --help
chown: Need 2 arguments
1|athene_f:/ # chown -R rfs:rfs_shared/persist/hlos/rfs
See chown --help
chown: Need 2 arguments
1|athene_f:/ # chown -R 3012:3012/persist/rfs
See chown --help
chown: Need 2 arguments
1|athene_f:/ # chown -R 3012:3013/persist/hlos_rfs
See chown --help
chown: Need 2 arguments
1|athene_f:/ #

 

[echo92]

It's showing something bro..

<snip>
1|athene_f:/ #

That doesn't look like steps 1 or 2, that looks like step 3, which was not what I requested. I asked for the output from the:

ls -l /persist

AND

find /persist -type f

commands as listed in steps 1 and 2:

Step 1: Check if there is a problem with persist

Note: The below commands are to be typed in a terminal app or adb shell.
Q) How to type in adb shell?
A) Open command prompt in the folder where you have adb and fastboot installed and type:
Code:

adb shell

So lets start now!

Code:

su

This command it to get root access for the terminal/shell. Grant the root access and you will see that the $ symbol is replaced with # symbol which means that root access has been granted.

Code:

ls -l /persist

If your presist has some problem, then you can see the following as the output.

Step 2: Check for the key persist files
Code:

find /persist -type f

Not sure if there's something that is not understood.

 

[Tetcare99]

Here the results bro

athene_f:/ $ su
athene_f:/ # Is -I /persist
/system/bin/sh: Is: not found
127|athene_f:/ # ls -l/persist
See ls --help
ls: Unknown option /persist
1|athene_f:/ # ls -l /persist
total 96
drwxrwx--- 2 system system 4096 1970-02-07 22:53 alarmdrwxr-xr-x 2 mot_pwric mot_pwric 4096 1969-12-31 19:02 batt_health
drwxrwx--- 2 bluetooth bluetooth 4096 2018-01-22 22:58 bluetooth
drwxr-xr-x 2 mot_tcmd bluetooth 4096 1969-12-31 19:02 bt
drwxr-xr-x 4 mot_tcmd mot_tcmd 4096 1970-02-07 22:52 camera
drwxr-xr-x 2 root root 4096 1970-02-07 22:52 coresight
drwx------ 4 system system 4096 1970-02-07 22:52 data
drwxrwx--- 2 system graphics 4096 1969-12-31 19:02 display
drwxrwx--- 2 system system 4096 1969-12-31 19:02 drm
drwxr-xr-x 4 mot_tcmd mot_tcmd 4096 1970-02-07 22:52 factory
drwxrwx--- 3 system system 4096 1970-02-07 22:52 hlos_rfs
drwxrwx--- 2 root root 4096 1970-02-07 22:52 lost+found
drwxrwx--- 2 radio radio 4096 1970-02-07 22:52 mdm
drwxrwx--- 2 system system 4096 1970-02-07 22:53 misc
drwxrwx--- 2 system system 4096 1970-07-07 05:32 properties
drwxr-xr-x 8 mot_tcmd mot_tcmd 4096 1970-02-07 22:52 public
drwx------ 6 system system 4096 1970-02-07 22:52 rfs
drwxrwx--- 2 system system 4096 1970-01-03 15:34 secnvm
drwxrws--- 2 drmrpc drmrpc 4096 1969-12-31 19:02 security
drwxrwxr-x 3 system system 4096 1970-01-03 15:34 sensors
drwxrwx--- 2 system system 4096 2019-01-29 13:09 time
drwxrwx--- 2 media media 4096 1970-01-03 15:34 vpp
drwxr-xr-x 2 mot_tcmd mot_tcmd 4096 1969-12-31 19:02 wifi
drwxrwxr-x 2 mot_drm mot_drm 4096 1969-12-31 19:02 wmdrmathene_f:/ # find /persist-type f
find: /persist-type: No such file or directory
find: f: No such file or directory
1|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
/persist/data/tz/tz_counter
/persist/data/tz/tz_counter.bak
/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
/persist/public/hiddenmenu/life_calls
/persist/public/hiddenmenu/life_timer
/persist/mdm/oma_dm_update
/persist/rfs/shared/server_info.txt
/persist/rfs/msm/mpss/safe/sfs/uim/simlock/config
/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
/persist/time/ats_1
/persist/time/ats_2
/persist/time/ats_16
athene_f:/ #

 

[Tetcare99]

Here the results bro

athene_f:/ $ su
athene_f:/ # Is -I /persist
/system/bin/sh: Is: not found
127|athene_f:/ # ls -l/persist
See ls --help
ls: Unknown option /persist
1|athene_f:/ # ls -l /persist
total 96
drwxrwx--- 2 system system 4096 1970-02-07 22:53 alarmdrwxr-xr-x 2 mot_pwric mot_pwric 4096 1969-12-31 19:02 batt_health
drwxrwx--- 2 bluetooth bluetooth 4096 2018-01-22 22:58 bluetooth
drwxr-xr-x 2 mot_tcmd bluetooth 4096 1969-12-31 19:02 bt
drwxr-xr-x 4 mot_tcmd mot_tcmd 4096 1970-02-07 22:52 camera
drwxr-xr-x 2 root root 4096 1970-02-07 22:52 coresight
drwx------ 4 system system 4096 1970-02-07 22:52 data
drwxrwx--- 2 system graphics 4096 1969-12-31 19:02 display
drwxrwx--- 2 system system 4096 1969-12-31 19:02 drm
drwxr-xr-x 4 mot_tcmd mot_tcmd 4096 1970-02-07 22:52 factory
drwxrwx--- 3 system system 4096 1970-02-07 22:52 hlos_rfs
drwxrwx--- 2 root root 4096 1970-02-07 22:52 lost+found
drwxrwx--- 2 radio radio 4096 1970-02-07 22:52 mdm
drwxrwx--- 2 system system 4096 1970-02-07 22:53 misc
drwxrwx--- 2 system system 4096 1970-07-07 05:32 properties
drwxr-xr-x 8 mot_tcmd mot_tcmd 4096 1970-02-07 22:52 public
drwx------ 6 system system 4096 1970-02-07 22:52 rfs
drwxrwx--- 2 system system 4096 1970-01-03 15:34 secnvm
drwxrws--- 2 drmrpc drmrpc 4096 1969-12-31 19:02 security
drwxrwxr-x 3 system system 4096 1970-01-03 15:34 sensors
drwxrwx--- 2 system system 4096 2019-01-29 13:09 time
drwxrwx--- 2 media media 4096 1970-01-03 15:34 vpp
drwxr-xr-x 2 mot_tcmd mot_tcmd 4096 1969-12-31 19:02 wifi
drwxrwxr-x 2 mot_drm mot_drm 4096 1969-12-31 19:02 wmdrmathene_f:/ # find /persist-type f
find: /persist-type: No such file or directory
find: f: No such file or directory
1|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
/persist/data/tz/tz_counter
/persist/data/tz/tz_counter.bak
/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
/persist/public/hiddenmenu/life_calls
/persist/public/hiddenmenu/life_timer
/persist/mdm/oma_dm_update
/persist/rfs/shared/server_info.txt
/persist/rfs/msm/mpss/safe/sfs/uim/simlock/config
/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
/persist/time/ats_1
/persist/time/ats_2
/persist/time/ats_16
athene_f:/ #

Bro...

 

[echo92]

Here the results bro
<snip>
find: /persist-type: No such file or directory
find: f: No such file or directory
1|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
/persist/data/tz/tz_counter
/persist/data/tz/tz_counter.bak
/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
/persist/public/hiddenmenu/life_calls
/persist/public/hiddenmenu/life_timer
/persist/mdm/oma_dm_update
/persist/rfs/shared/server_info.txt
/persist/rfs/msm/mpss/safe/sfs/uim/simlock/config
/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
/persist/time/ats_1
/persist/time/ats_2
/persist/time/ats_16
athene_f:/ #

Thanks for that - your persist permissions look to be okay. For some reason your device appears to have fewer entries related to persist than other devices' entries I've seen. Not sure how that happened, any ideas @Heeth21 ?

I'll have a look at what my device reports in terms of persist.

---------- Post added at 08:23 PM ---------- Previous post was at 08:14 PM ----------

Bro...

Yup, what were you asking about?

 

[Tetcare99]

1.imei numbers issue
2.sims not detecting
These are major issue in my mobile

 

[echo92]

1.imei numbers issue
2.sims not detecting
These are major issue in my mobile

I'm aware of that, I was asking what you posted 'bro' for?

 

[Tetcare99]

I'm aware of that, I was asking what you posted 'bro' for?

Just asking Have you seen my post or not?
That's why I am calling you bro.

 

[echo92]

Just asking Have you seen my post or not?
That's why I am calling you bro.

I saw your post when I had the time to view it and reply, especially since now we've got the info. I understand you're frustrated, and want to get your device fixed. Be patient please, I'm trying to figure out what's happened to your device's IMEI and network, given the usual fixes aren't working, and without knowing what happened before you hard bricked your device as well. Posting 'bro' and repeatedly not reading information is not helping. I don't know if the blankflash did anything (unlikely) or if there was a bad flash. Hopefully heeth21 or others can comment with their experience on your persist partition and offer other fixes.

 

[HeethJain21]

Thanks for that - your persist permissions look to be okay. For some reason your device appears to have fewer entries related to persist than other devices' entries I've seen. Not sure how that happened, any ideas @Heeth21 ?

I'll have a look at what my device reports in terms of persist.

Yes, somehow there has been some changes with the persist file.

The persist is missing "id_00" and "id_01" which is present in "/persist/rfs/msm/mpss/datablock/" directory.

The IMEIs are stored in "id_00" and "id_01" and somehow (maybe some arithmetic operation or something else) with the help of "dhob.bin" and "shob.bin", the IMEIs are generated.

I believe chances are that @Tetcare99 has restored some other device's persist from some Youtube video or some Internet forums, as the persist floating there does have "id_00" and "id_01" missing with a lot of other directories and files as well.

1.imei numbers issue
2.sims not detecting
These are major issue in my mobile

What are your IMEI/s right now? Are they 0?
And what is your baseband version seen from Settings>About Phone

 

[Tetcare99]

Yes, somehow there has been some changes with the persist file.

The persist is missing "id_00" and "id_01" which is present in "/persist/rfs/msm/mpss/datablock/" directory.

The IMEIs are stored in "id_00" and "id_01" and somehow (maybe some arithmetic operation or something else) with the help of "dhob.bin" and "shob.bin", the IMEIs are generated.

I believe chances are that @Tetcare99 has restored some other device's persist from some Youtube video or some Internet forums, as the persist floating there does have "id_00" and "id_01" missing with a lot of other directories and files as well.



What are your IMEI/s right now? Are they 0?
And what is your baseband version seen from Settings>About Phone

Imei =0
Basband version:M8952_700.30.25.03.77a ATHENE_INDIA_DSDS_CUST

Sent from my G4 Plus using XDA Labs

 

[HeethJain21]

Imei =0
Basband version:M8952_700.30.25.03.77a ATHENE_INDIA_DSDS_CUST

Sent from my G4 Plus using XDA Labs

Did you restore some other device's persist from some Youtube video or internet guide??

It doesn't seem to be the case since the baseband is ending with "a" which has been reported earlier as well and the current IMEI solution doesn't work with this baseband

 

[Tetcare99]

Did you restore some other device's persist from some Youtube video or internet guide??

It doesn't seem to be the case since the baseband is ending with "a" which has been reported earlier as well and the current IMEI solution doesn't work with this baseband

I did it bro .
But there is no changes appears.
I did download persist file from xda forum.

Sent from my G4 Plus using XDA Labs

 

[HeethJain21]

I did it bro .
But there is no changes appears.
I did download persist file from xda forum.

Sent from my G4 Plus using XDA Labs

Well that's the problems.
You used the persist file available on XDA.
Persist is unique to every device out there.

If you have backup of "YOUR" own persist then please restore it and IMEI will be recovered.

 

[Tetcare99]

Well that's the problems.
You used the persist file available on XDA.
Persist is unique to every device out there.

If you have backup of "YOUR" own persist then please restore it and IMEI will be recovered.

I don't have any backup persist file bro..I did back up system file like

Sent from my G4 Plus using XDA Labs

 

[echo92]

I don't have any backup persist file bro..I did back up system file like

Sent from my G4 Plus using XDA Labs

Just to clarify, by persist file you downloaded, do you mean the persist repair zip from the IMEI fix thread, or an actual persist image?

 

[Tetcare99]

Just to clarify, by persist file you downloaded, do you mean the persist repair zip from the IMEI fix thread, or an actual persist image?

Actually I did search for persist file in my phone but I can't find it .after that I did install persist file using twrp.that persist downloaded from xda thread

Sent from my G4 Plus using XDA Labs

 

[echo92]

Actually I did search for persist file in my phone but I can't find it .after that I did install persist file using twrp.that persist downloaded from xda thread

Sent from my G4 Plus using XDA Labs

My question is this persist file that you downloaded - is it the persist TWRP fix (from the IMEI=0 thread), or a persist image that you downloaded from XDA?

If you used the persist TWRP fix, then you might still be able to fix your device. If you downloaded someone else's persist image and flashed that, we might not be able to fix your device. There's a very important distinction between the two files, please clarify which file you downloaded and from which thread you used.