J700T imei repair failed (binary 3) - GSM-Forum

Zaki Bouzidson · 10-09-2018, 19:27

I started a new thread as old ones didn't resolve my problem
And I think the problem is the nv_data file, because I can't find any working one

I tried both files in this thread here and none of them had worked for me

1- Here the first log (binary 3 system 6.0.1):

Waiting ADB device... OK
Reading phone info...
Model: SM-J700T
Android version: 6.0.1
PDA version: J700TUVS3AQF1
CSC version: J700TTMB3AQF1
Phone version: J700TUVS3AQF1
Product code:
CSC country code: USA
CSC sales code: TMB
Phone SN:
IMEI: 000000000000000
HW version:
RF cal date:
Chip name: EXYNOS7580
Modem board: SHANNON310
Security patch: 2017-06-01
Boot Warranty bit: 1
Checking Super user right... true
Reading NV data... OK
Checking NV data... OK
Reading data... OK
Detecting MODEM... OK
Reading MODEM... OK
Calculating... OK
Writing zTool... OK
Initialization zTool... OK
Running zTool, please wait...
Start... OK
Initialization... OK
Generate and check client proof... OK
Verify proof by client... OK
Reading data... error (1 19)
Initialization zTool... OK
Running zTool, please wait...
Start... OK
Initialization... OK
Generate and check client proof... OK
Verify proof by client... OK
Reading data from phone... error (0)
Try downgrade modem if possible

Downgrading the modem didn't work either..

2- And here is the second log after downgrading to an earlier version (binary 2 system 6.0.1):

Waiting ADB device... OK
Reading phone info...
Model: SM-J700T
Android version: 6.0.1
PDA version: J700TUVU2APK6
CSC version: J700TTMB2APK6
Phone version: J700TUVU3AQC1
Product code:
CSC country code: USA
CSC sales code: TMB
Phone SN: 00000000000
IMEI: 000000000000000
HW version:
RF cal date:
Chip name: EXYNOS7580
Modem board: SHANNON310
Security patch: 2016-11-01
Boot Warranty bit: 1
Checking Super user right... true
Reading NV data... OK
Checking NV data... OK
Initialization zTool... OK
Running zTool, please wait...
Start... OK
Initialization... OK
Generate and check client proof... OK
Verify proof by client... OK
Reading data from phone... OK
Modem board: SHANNON310
HWID: 57 D9 01 9F F3 92 E2 81 98 C0 57 C4 C7 AD F6 7C
Calculating...
hmac mismatch, this can damage phone continue? Yes OK
Repairing... OK
Writing NV data... OK
Rebooting phone... OK
Repair done

But the repair is not done as I face an unknown Baseband after the alleged repair

Does anyone have a working nv_data file?

souma_k · 10-09-2018, 22:32

Quote:

Originally Posted by Zaki Bouzidson

I started a new thread as old ones didn't resolve my problem
And I think the problem is the nv_data file, because I can't find any working one

I tried both files in this thread here and none of them had worked for me

1- Here the first log (binary 3 system 6.0.1):

Waiting ADB device... OK
Reading phone info...
Model: SM-J700T
Android version: 6.0.1
PDA version: J700TUVS3AQF1
CSC version: J700TTMB3AQF1
Phone version: J700TUVS3AQF1
Product code:
CSC country code: USA
CSC sales code: TMB
Phone SN:
IMEI: 000000000000000
HW version:
RF cal date:
Chip name: EXYNOS7580
Modem board: SHANNON310
Security patch: 2017-06-01
Boot Warranty bit: 1
Checking Super user right... true
Reading NV data... OK
Checking NV data... OK
Reading data... OK
Detecting MODEM... OK
Reading MODEM... OK
Calculating... OK
Writing zTool... OK
Initialization zTool... OK
Running zTool, please wait...
Start... OK
Initialization... OK
Generate and check client proof... OK
Verify proof by client... OK
Reading data... error (1 19)
Initialization zTool... OK
Running zTool, please wait...
Start... OK
Initialization... OK
Generate and check client proof... OK
Verify proof by client... OK
Reading data from phone... error (0)
Try downgrade modem if possible

Downgrading the modem didn't work either..

2- And here is the second log after downgrading to an earlier version (binary 2 system 6.0.1):

Waiting ADB device... OK
Reading phone info...
Model: SM-J700T
Android version: 6.0.1
PDA version: J700TUVU2APK6
CSC version: J700TTMB2APK6
Phone version: J700TUVU3AQC1
Product code:
CSC country code: USA
CSC sales code: TMB
Phone SN: 00000000000
IMEI: 000000000000000
HW version:
RF cal date:
Chip name: EXYNOS7580
Modem board: SHANNON310
Security patch: 2016-11-01
Boot Warranty bit: 1
Checking Super user right... true
Reading NV data... OK
Checking NV data... OK
Initialization zTool... OK
Running zTool, please wait...
Start... OK
Initialization... OK
Generate and check client proof... OK
Verify proof by client... OK
Reading data from phone... OK
Modem board: SHANNON310
HWID: 57 D9 01 9F F3 92 E2 81 98 C0 57 C4 C7 AD F6 7C
Calculating...
hmac mismatch, this can damage phone continue? Yes OK
Repairing... OK
Writing NV data... OK
Rebooting phone... OK
Repair done

But the repair is not done as I face an unknown Baseband after the alleged repair

Does anyone have a working nv_data file?

try samfix to repair unknown baseband and check again

Sent from my Le X829 using Tapatalk

Zaki Bouzidson · 10-09-2018, 22:42

Baseband comes back after removing nv_data files.

Zaki Bouzidson · 10-15-2018, 06:41

Is it even possible to repair IMEI on binary 3, I mean.. is it supported?

10-09-2018, 19:27	#1 (permalink)
Zaki Bouzidson Freak Poster Join Date: Nov 2014 Location: Algeria Posts: 193 Member: 2287326 Status: Offline Thanks Meter: 54	J700T imei repair failed (binary 3) I started a new thread as old ones didn't resolve my problem And I think the problem is the nv_data file, because I can't find any working one I tried both files in this thread here and none of them had worked for me 1- Here the first log (binary 3 system 6.0.1): Waiting ADB device... OK Reading phone info... Model: SM-J700T Android version: 6.0.1 PDA version: J700TUVS3AQF1 CSC version: J700TTMB3AQF1 Phone version: J700TUVS3AQF1 Product code: CSC country code: USA CSC sales code: TMB Phone SN: IMEI: 000000000000000 HW version: RF cal date: Chip name: EXYNOS7580 Modem board: SHANNON310 Security patch: 2017-06-01 Boot Warranty bit: 1 Checking Super user right... true Reading NV data... OK Checking NV data... OK Reading data... OK Detecting MODEM... OK Reading MODEM... OK Calculating... OK Writing zTool... OK Initialization zTool... OK Running zTool, please wait... Start... OK Initialization... OK Generate and check client proof... OK Verify proof by client... OK Reading data... error (1 19) Initialization zTool... OK Running zTool, please wait... Start... OK Initialization... OK Generate and check client proof... OK Verify proof by client... OK Reading data from phone... error (0) Try downgrade modem if possible Downgrading the modem didn't work either.. 2- And here is the second log after downgrading to an earlier version (binary 2 system 6.0.1): Waiting ADB device... OK Reading phone info... Model: SM-J700T Android version: 6.0.1 PDA version: J700TUVU2APK6 CSC version: J700TTMB2APK6 Phone version: J700TUVU3AQC1 Product code: CSC country code: USA CSC sales code: TMB Phone SN: 00000000000 IMEI: 000000000000000 HW version: RF cal date: Chip name: EXYNOS7580 Modem board: SHANNON310 Security patch: 2016-11-01 Boot Warranty bit: 1 Checking Super user right... true Reading NV data... OK Checking NV data... OK Initialization zTool... OK Running zTool, please wait... Start... OK Initialization... OK Generate and check client proof... OK Verify proof by client... OK Reading data from phone... OK Modem board: SHANNON310 HWID: 57 D9 01 9F F3 92 E2 81 98 C0 57 C4 C7 AD F6 7C Calculating... hmac mismatch, this can damage phone continue? Yes OK Repairing... OK Writing NV data... OK Rebooting phone... OK Repair done But the repair is not done as I face an unknown Baseband after the alleged repair Does anyone have a working nv_data file?

10-09-2018, 22:42	#3 (permalink)
Zaki Bouzidson Freak Poster Join Date: Nov 2014 Location: Algeria Posts: 193 Member: 2287326 Status: Offline Thanks Meter: 54	Baseband comes back after removing nv_data files.

10-15-2018, 06:41	#4 (permalink)
Zaki Bouzidson Freak Poster Join Date: Nov 2014 Location: Algeria Posts: 193 Member: 2287326 Status: Offline Thanks Meter: 54	Is it even possible to repair IMEI on binary 3, I mean.. is it supported?