I have a problem with and unlock my galaxy N9250T with Z3X SamsungToolPRO_24.3 it gives me this message.
Operation: Read Codes
Selected model: SM-N920T
Software version: 24.3
Please wait, generating hash codes file, this can take few minutes... OK
Waiting ADB device...
Please, allow USB debugging on phone... OK
Reading phone info...
Model: SM-N920T
Android version: 5.1.1
Product code: SM-N920TZWATMB
Phone version: N920TUVU2COJ5
PDA version: N920TUVU2COJ5
CSC version: N920TTMB2COJ5
CSC country code: USA
CSC sales code: TMB
HW version: REV0.2
Phone S/N: RF8G903HHRY
Modem board: SHANNON333
RF cal date: 20150902
IMEI:
Checking Super user right... true
Initialization AT RIL...
Exception: Access violation at address 004074E0 in module 'SamsungToolPRO.exe'. Read of address 00000000
Done with Samsung Tool PRO v.24.3
I have the same damn problem...
Operation: Unlock SPRNT
Selected model: SM-N920P
Software version: 24.3
Waiting ADB device... OK
Reading phone info...
Model: SM-N920P
Android version: 6.0.1
Product code: Not Active
Phone version: N920PVPS3BQB1
PDA version: N920PVPS3BQB1
CSC version: N920PSPT3BQB1
CSC country code: USA
CSC sales code: SPR
HW version: N920P.04
Phone S/N: 00000000000
Modem board: MDM9635M
RF cal date: 2016.01.21
IMEI:
Initialization AT RIL...
Exception: Access violation at address 004074E0 in module 'SamsungToolPRO.exe'. Read of address 00000000
Done with Samsung Tool PRO v.24.3
Related
Hello,
I installed EFS pro, all *seems* okay, phone is found, etc etc, messages say That things are going fine, unless the end:
Checking device connection... Device is connected!
Checking for block device: '/dev/block/mmcblk0'... Okay.
Extracting PIT from device for mapping... Skipped, already exists.
Checking backup folder location... Okay.
Backing up selected partition(s)...
EFS - read: /dev/block/mmcblk0p3 - write: efs.img... Okay.
20971520 bytes transferred in 0.648 secs (32363456 bytes/sec)
Creating archive: GT-I9300_20140813_011925.tar.gz... Okay.
Copying: GT-I9300_20140813_011925.tar.gz to PC storage... Okay.
Copied: remote object '/storage/extSdCard/EFSProBackup/GT-I9300_20140813_011925.tar.gz' does not exist
Cleaning up temporary files... Okay.
Operation successful!
And in fact the file GT-I9300_20140813_011925.tar.gz is not present anywhere neither on the phone nor on the PC.
I run EFS from the Win7 "My documents" folder, "as an administrator"...
Param on the phone for storage location is "/storage/extSdCard". I find the folder On the phone, EFS created a sub directory "/storage/extSdCard/EFSProBackup" but there is nothing inside...
Any suggestion?
Thank you
PS: Device info:
---------- Hardware Information ----------
Connected Device SN.: [REMOVED]
Device Manufacturer: SAMSUNG
Device Model: GT-I9300
Product Code: GT-I9300RWDXEO
Hardware Version: MP 1.100
---------- Firmware Information ----------
PDA Version: I9300XXUGNA5
Baseband Version: I9300XXUGNA8
CSC Version: I9300XEOGNC1
---------- Software Information ----------
Kernel Release: 3.0.31-2429075
Kernel Version: #1 SMP PREEMPT Thu Jan 16 23:47:54 KST 2014
ROM Build: m0xx-user 4.3 JSS15J I9300XXUGNA5 release-keys
Android Version: 4.3
BusyBox Version: 1.20.2-cm9
SU Binary Version: 2.00:SUPERSU
Nobody?
Ruzakuku said:
Hello,
I installed EFS pro, all *seems* okay, phone is found, etc etc, messages say That things are going fine, unless the end:
Checking device connection... Device is connected!
Checking for block device: '/dev/block/mmcblk0'... Okay.
Extracting PIT from device for mapping... Skipped, already exists.
Checking backup folder location... Okay.
Backing up selected partition(s)...
EFS - read: /dev/block/mmcblk0p3 - write: efs.img... Okay.
20971520 bytes transferred in 0.648 secs (32363456 bytes/sec)
Creating archive: GT-I9300_20140813_011925.tar.gz... Okay.
Copying: GT-I9300_20140813_011925.tar.gz to PC storage... Okay.
Copied: remote object '/storage/extSdCard/EFSProBackup/GT-I9300_20140813_011925.tar.gz' does not exist
Cleaning up temporary files... Okay.
Operation successful!
And in fact the file GT-I9300_20140813_011925.tar.gz is not present anywhere neither on the phone nor on the PC.
I run EFS from the Win7 "My documents" folder, "as an administrator"...
Param on the phone for storage location is "/storage/extSdCard". I find the folder On the phone, EFS created a sub directory "/storage/extSdCard/EFSProBackup" but there is nothing inside...
Any suggestion?
Thank you
PS: Device info:
---------- Hardware Information ----------
Connected Device SN.: [REMOVED]
Device Manufacturer: SAMSUNG
Device Model: GT-I9300
Product Code: GT-I9300RWDXEO
Hardware Version: MP 1.100
---------- Firmware Information ----------
PDA Version: I9300XXUGNA5
Baseband Version: I9300XXUGNA8
CSC Version: I9300XEOGNC1
---------- Software Information ----------
Kernel Release: 3.0.31-2429075
Kernel Version: #1 SMP PREEMPT Thu Jan 16 23:47:54 KST 2014
ROM Build: m0xx-user 4.3 JSS15J I9300XXUGNA5 release-keys
Android Version: 4.3
BusyBox Version: 1.20.2-cm9
SU Binary Version: 2.00:SUPERSU
Click to expand...
Click to collapse
I'm having a similar problem.....
I'm a noob so I really need some help. I have a sgs3 1747m from Canada. The phone is rooted (I followed xda CF method)
I wanted to back up the efs folder so I also followed the instructions on xda. (downloaded busybox and efs pro) Phone connects Everything says okay. The problems starts when I have to choose the device filter. I select sgs3 US - operation failed but then I thought the phone is from Canada so I tried a couple other selections all say operation failed. In addition, there are no partitions, files or folders shown for me to select to back up. Have I done something wrong? Does efs pro not work with my phone?
Greetings, I thank you all for help or guidance.
I have flashed several rom, this time loaded on my N8013 RLS8 Hyperdrive, to finish tablet reboot, but now a table is still displayed, picture detail:
PDA: N8013UEUCMD3
Phone: N/A
CSC: Unknown
H/W: Not Active
RF Cal Date: N/A
SMD: N/A, FrontCam: N/A
TSP: AT000010
TSK: N/A
Band: N/A, USB: N/A
UN: CMA075C77609BAF
best regards
UPDATE: I DONT KNOW IF CHANGING THE CABLE IS WHAT FINALLY DID IT, BUT IT IS DONE. THANK YOU ANYWAY. SORRY I POSTED SO SOON. I DONT USUALLY DO THAT. ALSO, IT WAS THE Z3X THAT FINALLY DID THE TRICK. ALSO THE FILE SIZE WAS 2.15K. ANY BODY ELSE THAT MAY WANT MORE DETAILS I WILL BE GLAD TO HELP.
Hey guys I really need some help and I am unable to find anything about it. I keep getting this error. Security damaged. I do the repair, it says its good then when I try and repair the imei it errors out. Here is the print out.
Platform: Samsung Android
Selected port: COM14
Selected model: SM-G925T
Please, press "OK" button on the phone to allow USB debugging..
Detected phone model: SM-G925T
Firmware compiled date: Sat Sep 19 16:29:03 KST 2015
PDA version: G925TUVU3DOI1
CSC version: G925TTMB3DOI1
SW version: G925TUVU3DOI1
Phone IMEI: Unknown
Phone SN: 00000000000
Android version: 5.1.1 (LMY47X)
Checking Root:
Phone is Rooted.
Reading security backup, please wait...
Backup saved as C:\Program Files (x86)\Octoplus\Octoplus_Samsung\BACKUP\Security-SM-G925T-Unknown14-10-2015_00-35-44-.asec file
Wiping EFS...
Phone will restart now. Please don't disconnect cable!
EFS wipe successfully
Searching for a phone. Please wait...
Detected phone model: SM-G925T
Firmware compiled date: Sat Sep 19 16:29:03 KST 2015
PDA version: G925TUVU3DOI1
CSC version: G925TTMB3DOI1
SW version: G925TUVU3DOI1
Phone IMEI: Unknown
Phone SN: 00000000000
Android version: 5.1.1 (LMY47X)
Repairing security
Security repair successfully
-----------------------------------------------------------------------------------
Platform: Samsung Android
Selected port: COM14
Selected model: SM-G925T
Selected file: C:\Users\John\Downloads\cert-sm-g925t_359146060661913_r58g50kgewk.cert
Detected phone model: SM-G925T
Firmware compiled date: Sat Sep 19 16:29:03 KST 2015
PDA version: G925TUVU3DOI1
CSC version: G925TTMB3DOI1
SW version: G925TUVU3DOI1
Phone IMEI: Unknown
Phone SN: 00000000000
Android version: 5.1.1 (LMY47X)
Checking Root:
Phone is Rooted.
Checking Certificate file...
Certificate file successfully checked
Phone connected successfully
Writing certificate...
Security damaged, please Repair Security and try again
Well I started comparing file size and the file that is in the phone is 2.15k, while the other g925t, as well as the other vairents of this cert are all 2.16k. Now when I flash with either octo or z3x I get the security damaged. I did find one file that was 2.15k and did get a successful flash, which gave me a ser #, but a defective imei. Please help.
Welcome to Octoplus/Octopus Box Samsung software version 2.0.4
-----------------------------------------------------------------------------------
To connect SM-G925T phone you have to perform the following steps:
1. Disconnect USB cable from phone.
2. Go to Menu->Settings->More->About Device.
3.Tap on "Build number" 7 times to enable developer options.
4. Go to Menu->Settings->More->Developer options.
5. Turn on "USB Debugging" option.
-----------------------------------------------------------------------------------
Platform: Samsung Android
Selected port: COM18
Selected model: SM-G925T
Selected file: C:\Users\John\Downloads\cert-sm-g920t-
357746060831994-r58g31myxyb.cert
Detected phone model: SM-G925T
Firmware compiled date: Sat Sep 19 16:29:03 KST 2015
PDA version: G925TUVU3DOI1
CSC version: G925TTMB3DOI1
SW version: G925TUVU3DOI1
Phone IMEI: Unknown
Phone SN: R58G50TKDNH
Android version: 5.1.1 (LMY47X)
Checking Root:
Phone is Rooted.
Checking Certificate file...
Certificate file successfully checked
Phone connected successfully
Writing certificate...
Security damaged, please Repair Security and try again
-----------------------------------------------------------------------------------
Platform: Samsung Android
Selected port: COM18
Selected model: SM-G925T
Selected file: C:\Users\John\Downloads\Cert-SM-G900-
358021058471446-RF1D93A24AK.cert
Detected phone model: SM-G925T
Firmware compiled date: Sat Sep 19 16:29:03 KST 2015
PDA version: G925TUVU3DOI1
CSC version: G925TTMB3DOI1
SW version: G925TUVU3DOI1
Phone IMEI: Unknown
Phone SN: R58G50TKDNH
Android version: 5.1.1 (LMY47X)
Checking Root:
Phone is Rooted.
Checking Certificate file...
Checking Certificate failed
Writing Certificate failed
-----------------------------------------------------------------------------------
Platform: Samsung Android
Selected port: COM18
Selected model: SM-G925T
Selected file: C:\Users\John\Downloads\cert-sm-g925f_
359521066036817_rf8g51vfezn.cert
Detected phone model: SM-G925T
Firmware compiled date: Sat Sep 19 16:29:03 KST 2015
PDA version: G925TUVU3DOI1
CSC version: G925TTMB3DOI1
SW version: G925TUVU3DOI1
Phone IMEI: Unknown
Phone SN: R58G50TKDNH
Android version: 5.1.1 (LMY47X)
Checking Root:
Phone is Rooted.
Checking Certificate file...
Certificate file successfully checked
Phone connected successfully
Writing certificate...
Security damaged, please Repair Security and try again
-----------------------------------------------------------------------------------
Platform: Samsung Android
Selected port: COM18
Selected model: SM-G925T
Detected phone model: SM-G925T
Firmware compiled date: Sat Sep 19 16:29:03 KST 2015
PDA version: G925TUVU3DOI1
CSC version: G925TTMB3DOI1
SW version: G925TUVU3DOI1
Phone IMEI: Unknown
Phone SN: R58G50TKDNH
Android version: 5.1.1 (LMY47X)
Checking Root:
Phone is Rooted.
Reading security backup, please wait...
Backup saved as C:\Program Files (x86)\Octoplus\Octoplus_Samsung
\BACKUP\Security-SM-G925T-Unknown14-10-2015_04-34-29-.asec
file
Wiping EFS...
Phone will restart now. Please don't disconnect cable!
EFS wipe successfully
Searching for a phone. Please wait...
Detected phone model: SM-G925T
Firmware compiled date: Sat Sep 19 16:29:03 KST 2015
PDA version: G925TUVU3DOI1
CSC version: G925TTMB3DOI1
SW version: G925TUVU3DOI1
Phone IMEI: Unknown
Phone SN: R58G50TKDNH
Android version: 5.1.1 (LMY47X)
Repairing security
Security repair successfully
-----------------------------------------------------------------------------------
Platform: Samsung Android
Selected port: COM18
Selected model: SM-G925T
Selected file: C:\Users\John\Desktop\cert-sm-g920f_35984506420518
_rf8g410tn3e.cert
Detected phone model: SM-G925T
Firmware compiled date: Sat Sep 19 16:29:03 KST 2015
PDA version: G925TUVU3DOI1
CSC version: G925TTMB3DOI1
SW version: G925TUVU3DOI1
Phone IMEI: Unknown
Phone SN: R58G50TKDNH
Android version: 5.1.1 (LMY47X)
Checking Root:
Phone is Rooted.
Checking Certificate file...
Certificate file successfully checked
Phone connected successfully
Writing certificate...
Security damaged, please Repair Security and try again
PLEASE PUT THIS IN THE RIGHT PLACE. I AM SO FLUSTERED BY THIS I may have PUT IT IN THE WRONG PLACE.
Hi,
Glad to know you got it fixed
Thread closed
Platform: LG Qualcomm
Selected port: COM18
Selected model: D820
Reading info...
Initializing ADB...OK
Waiting for phone...OK
Model ID: Nexus 5
Firmware version:
Kernel version: 3.4.0-g9eb14ba ([email protected]) (gcc version 4.7 (GCC) ) #3
SMP PREEMPT Tue Nov 26 12:04:50 CST 201
Android version: 4.4.4
Hardware: Qualcomm MSM 8974 HAMMERHEAD (Flattened Device Tree)
ARMv7 Processor rev 0 (v7l)
Performed by 2.4.6 Software version.
--------------------------------------------------------------------------------
Checking data...OK
Platform: LG Qualcomm
Selected port: COM18
Selected model: D820
Reading info...
Initializing ADB...OK
Waiting for phone...OK
Model ID: Nexus 5
Firmware version:
Kernel version: 3.4.0-g9eb14ba ([email protected]) (gcc version 4.7 (GCC) ) #3
SMP PREEMPT Tue Nov 26 12:04:50 CST 201
Android version: 4.4.4
Hardware: Qualcomm MSM 8974 HAMMERHEAD (Flattened Device Tree)
ARMv7 Processor rev 0 (v7l)
Switching to Fastboot mode...OK
Unlocking Bootloader...
Bootloader is unlocked.
Writing Bootloader...OK
Please, wait while the phone will turn on and press "Ok" button.
Trying to enable Diagnostics ports...
Initializing ADB...OK
Waiting for phone...OK
Checking root access...
Phone is already rooted.
Diagnostics ports are enbled!
Switching to Serial Port...
Failed!
Performed by 2.4.6 Software version.
Any Solution ?
I'm not sure what the problem would be since the software and box should force flash the phone, assuming the phone is not physically damaged.
I have been repaired, But what is the Solution Of " Mobile network Not Available ' And ' No Signal " ?
Was the phone dropped? Possible loose internal connection? Phone is showing the correct imei?
Yes It's Have A Correct Imei , I'm not dropped the phone ...
is The problem Of Hardware ?
I can´t flashing g950u. Error with odin 3.12.3, 3.12.5, 3.12.7, smart watch, z3x and chimera tool.
The screen was on earlier which is why I'm confused.
I cant really get a good picture but I can list the text here:
Build info: Apr 28 2017
Build info2: SWHE7706:dpi QB:13390971
Build Ver: FA70_G950UDQU1AQDB_11303241 [ user]
Chip Name: MSM8998
Chip Ver: 2.1
PM8998 Ver: 2.0/PM8005 ver: 2.0
HW Rev: 12
Model Name: SM-G950U
Serial Number
Cable: 3
Debug level: Mid
Carrier: SPR
Fused Open Loop Voltage: 986
CPR_IDDQ_INFO SILVER: 0x1A
CPR_IDDQ_INFO GOLD: 0x45
DDR Vendor: Samsung
Update fail
MDM MODE: CAN'T DOWNLOAD (bksecapp)
error chimera tool
RP SWREV: B1 (1, 1, 1, 1, 1) K1 S1
Downgrade: tz.mbn (1 -> 0)
solution??
mjrablvc said:
I can´t flashing g950u. Error with odin 3.12.3, 3.12.5, 3.12.7, smart watch, z3x and chimera tool.
The screen was on earlier which is why I'm confused.
I cant really get a good picture but I can list the text here:
Build info: Apr 28 2017
Build info2: SWHE7706:dpi QB:13390971
Build Ver: FA70_G950UDQU1AQDB_11303241 [ user]
Chip Name: MSM8998
Chip Ver: 2.1
PM8998 Ver: 2.0/PM8005 ver: 2.0
HW Rev: 12
Model Name: SM-G950U
Serial Number
Cable: 3
Debug level: Mid
Carrier: SPR
Fused Open Loop Voltage: 986
CPR_IDDQ_INFO SILVER: 0x1A
CPR_IDDQ_INFO GOLD: 0x45
DDR Vendor: Samsung
Update fail
MDM MODE: CAN'T DOWNLOAD (bksecapp)
error chimera tool
RP SWREV: B1 (1, 1, 1, 1, 1) K1 S1
Downgrade: tz.mbn (1 -> 0)
Click to expand...
Click to collapse
Hi
I have the same problem
Did you managed to get any solution for this??
Thanks in advance
looks like the screen that appears for the eng boot file. I had the same issue with a phone today. Probably a bad flash or file. Try flashing stock firmware from download mode via ODIN
snsmosko said:
Hi
I have the same problem
Did you managed to get any solution for this??
Thanks in advance
Click to expand...
Click to collapse
no solution yet
Get it in download mode and flash stock firmware again.
Before flashing engboot or combi, wipe cache and restart to bootloader