Project

General

Profile

Actions

Issue #1845

open

Matching nv_data md5 failed after I got my cellphone unlocked (I have a efs backup)

Added by ariel enter almost 5 years ago. Updated over 1 year ago.

Status:
New
Priority:
Urgent
Assignee:
-
Category:
-
Target version:
Start date:
11/03/2017
Due date:
% Done:

0%

Estimated time:
Resolution:
Device:
Galaxy S 2 (I9100)
Grant:
Type of work:
Unknown

Description

Some how I got my cellphone locked again to use only the original cellphone company's SIM chips, as described in my last submitted issue [[https://redmine.replicant.us/issues/1840]].

I decided to take my cellphone to a technician on my city. He told me that he could only unlock it if the cellphone was running the stock ROM, so after instilling it, I took it back to him and sure enough, he unlocked it and I was able to use other company's SIM chips.

Unfortunately after installing replicant back, I was still unable to get service.

I'm sending my encrypted full radio logs from replicant and lineageos, and I'm sharing some of the content where I believe may lies the problem.

Replicant log:

D use-Rlog/RLOG-RIL-IPC: Checked nv_data path
D use-Rlog/RLOG-RIL-IPC: Checked nv_data md5 path
D use-Rlog/RLOG-RIL-IPC: Calculated nv_data md5: 3db13216a5302aa00a00d5548ef826b6
D use-Rlog/RLOG-RIL-IPC: Read nv_data md5: 00309e92dfbccc5fcd2bc1a43c27b387
D use-Rlog/RLOG-RIL-IPC: Matching nv_data md5 failed
D use-Rlog/RLOG-RIL-IPC: Checking nv_data failed
D use-Rlog/RLOG-RIL-IPC: Checking nv_data backup path failed
D use-Rlog/RLOG-RIL-IPC: Checking nv_data backup path failed
D use-Rlog/RLOG-RIL-IPC: Checking nv_data backup failed
D use-Rlog/RLOG-RIL-IPC: Restoring nv_data failed
D use-Rlog/RLOG-RIL-IPC: Loading nv_data failed

Lineageos Log:

E use-Rlog/RLOG-RIL: Modem_Boot:
E use-Rlog/RLOG-RIL: check_cracking
E use-Rlog/RLOG-RIL: check_cracking: cracking detected: lockProblemPatch 0x01
E use-Rlog/RLOG-RIL: check_cracking: cracking detected: patch was done
E use-Rlog/RLOG-RIL: load_md5_state: MD5 state 1
E use-Rlog/RLOG-RIL: md5_enable: on 1
E use-Rlog/RLOG-RIL: check_nv_data_validity: 
E use-Rlog/RLOG-RIL: check_nv_data_size: 
E use-Rlog/RLOG-RIL: check_md5: 
E use-Rlog/RLOG-RIL: compute_md5: path /efs/nv_data.bin
E use-Rlog/RLOG-RIL: check_md5: checksum fail
E use-Rlog/RLOG-RIL: NV data tainted! Restoring...
E use-Rlog/RLOG-RIL: check_md5: 
E use-Rlog/RLOG-RIL: compute_md5: path /efs/.nv_data.bak
E use-Rlog/RLOG-RIL: compute_md5: open(/efs/.nv_data.bak) fail. No such file or directory.
E use-Rlog/RLOG-RIL: No valid backup data. Create default nv data.
E use-Rlog/RLOG-RIL: can't open a phone image from (/dev/block/mmcblk0p8) / Permission denied.
E use-Rlog/RLOG-RIL: create_default_nv_data: 
E use-Rlog/RLOG-RIL: => create new nv_data file(/efs/nv_data.bin).
E use-Rlog/RLOG-RIL: create_default_nv_data: Open a phone image from (/dev/block/mmcblk0p8).
E use-Rlog/RLOG-RIL: can't open a phone image from (/dev/block/mmcblk0p8).
E use-Rlog/RLOG-RIL: compute_md5: path /efs/nv_data.bin
E use-Rlog/RLOG-RIL: /efs/nv_data.bin  md5 : 2d44b1b4d8b512c006e8dfa559eaad1a
E use-Rlog/RLOG-RIL: make_md5_file: (/efs/nv_data.bin.md5)
E use-Rlog/RLOG-RIL: make_md5_file: fd 7
E use-Rlog/RLOG-RIL: make_md5_file: write 32
E use-Rlog/RLOG-RIL: make_md5_file: fd 7 errno 13
D use-Rlog/RLOG-RIL: wait Modem boot ready

After the technician finished unlocking the phone I asked him if he used a special PIN code or something to unlock it, but he said he used some tool that allows the system to “jump” the lock.

I'm guessing he modify some how nv_data.bin and that's what replicant and lineageos is picking on. It appears that the .bak files where deleted to prevent the system from overriding the unlock, and the permissions for mmcblk0p8 where alter so lineageos can't use it to fix it either.

Fortunately, I made a efs backup before I took it to the technician. I suppose I could use it to override what the technician did, but I fear the phone will become locked again. Maybe I could just copy the bak files from the backup I made or fix the permissions on mmcblk0p8 that is preventing lineageos to use it.

Could it be possible that I could made a new md5sum of the modified nv_data.bin and it would work?

I'm a little frustrated because when I first got the phone it was unlocked and I didn't have any problem using replicant. Could it be that the unlocked was made in a different way back then? Using a PIN number perhaps?

Any way, could you guys tell me what I should do next? I could just push the entire efs backup back in if necessary, even if it means I get back to 0 on the unlocking issue. I know I should have asked you guys first how I could unlocked it on the first place.

Anyway, Thank you very much for any advice you can give me on this. Thank you.


Files

replicant.log.gpg (10.6 KB) replicant.log.gpg ariel enter, 11/03/2017 04:43 PM
lineageos.log.gpg (24.3 KB) lineageos.log.gpg ariel enter, 11/03/2017 04:43 PM
lineageos2.log.gpg (13.3 KB) lineageos2.log.gpg ariel enter, 11/03/2017 07:54 PM
Actions

Also available in: Atom PDF