Develop Bugs

Help in HEX convert need

Hi.
i need a litle help in hex convert.
in Bepe threads i fond this.
- nb file: 0x000001F5: short value + 0x48 (e.g: 0xA7+0x48=0xEF)
- nb file: 0x000001FB: short value + 0x48
A7 00 + 0x48 = EF 00
DB 05 + 0x48 = 23 06
i dont know if that is correct or not but if yes wath the value for this?
A2 01 + 0x48 = ??????
Thx and regards

I think you are not adding the columns correctly here. See your examples below along with a base 10 (the way we normally count) example (notice the numbers are lined up just as you would if you were adding base 10 numbers, from the least significant column to the most significant column, right to left)
A7 00 DB 05 100 (base 10 example)
+ 48 + 48 + 10
-------- ------ ----
A7 48 DB 4D 110
A7 + 48 does add to EF, but that is leaving out 2 entire orders of significance at the end of the A7 00 number.
So, the answer to your next question then would be:
A2 01
+ 48
------
A2 49
Also, just FYI here, the Calculator program that comes w/ Windows based computers will do Hex arithmetic for you. To get it to hex mode, start the Calculator, click on the View menu and choose Scientific. The calculator will then change it's view so that you can do Hex, Decimal (base 10), Octal or Binary arithmetic.
Hope that makes sense. If not, ask and I'll try to do a better job explaining.

Help wanted for interesting hack job

I'm trying to hack my in car satnav, it runs CE and I'm able to decompile one of the binary images and see some of the applications that the device runs, however I am trying to decompile the OS binary and the same decompile process will not work.
Anyone got any thoughts on what to try?
Oh it's an SH4 device btw and the ROM etc is loaded from DVD.
Thanks in advance for any help.
Cheers

Quick one,
E:\>ImgfsToDump.exe 07AVNe.bin
ImgfsToDump 2.0 RC 3
guidBootSignature: 42 30 30 30 46 46 A 0 0 6 80 FC C2 4F 0 0
dwFSVersion: 10800600
dwSectorsPerHeaderBlock: 99000000
dwRunsPerFileHeader: 09000002
dwBytesPerHeader: 01000900
dwChunksPerSector: 2B0009D0
dwFirstHeaderBlockOffset: 58000940
dwDataBlockSize: 40880356
szCompressionType:
dwFreeSectorCount: 97000000
dwHiddenSectorCount: 45000002
dwUpdateModeFlag: DC434543
Compression DLL does not support compression type ''!
Anyone that can point me in the right direction would be appreciated

All GAC/Managed are "Test Signed"

I noticed when going through the GAC_* from the WP7 Emu dump, that ALL have the same signature.
There is a "TEST Cert" applied so they become "trusted" by the phone, or else it just exit the app.
I think this is the certificate that they apply before adding it to marketplace list, that the app gets "OK".
"C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\Silverlight\v4.0\Profile\WindowsPhone\Microsoft.Phone.Interop.dll"
Signatures:
Microsoft Code Signing PCA
Microsoft Time-Stamp PCA
Microsoft Time-Stamp Service
Microsoft Corporation
"C:\Program Files (x86)\Microsoft SDKs\Windows Phone\v7.0\Emulation\Images\dump\GAC_Microsoft.Phone.Interop_v7_0_0_0_cneutral_1.dll"
Signatures:
One certificate?
Windows Mobile TCB Test CA (mobile WTF?, is'nt this Windows "Phone")
--->
//****************************************************************************
//Authenticode Signature
This digital signature is not valid.
Digest Algorithm = SHA1
Link Checksum = 0000D5FF
Real Checksum = 0000D5FF
Signed File Hash = B5 58 B3 7E AE 00 1F 68 A3 20 79 A5 E1 4B 90 BD BC 1A D2 17
Real File Hash = B5 58 B3 7E AE 00 1F 68 A3 20 79 A5 E1 4B 90 BD BC 1A D2 17
//****************************************************************************
//****************************************************************************
//Signature Details
//----------------------------------------------------------------------------
//Item 0 (Not available)
This digital signature is not valid.
Name of Signer = Not available
Email Address = Not available
Signing Time = Not available
Version = 2
Issuer = Common Name = Windows Mobile TCB Test CA
Serial Number = AA 5F 33 25 37 24 96 86 4F 18 FE D0 30 94 E7 7D
Digest Algorithm = SHA1 (2B 0E 03 02 1A)
Digest Encryption Algorithm = RSA (2A 86 48 86 F7 0D 01 01 01)
Authenticated Attributes:
1.3.6.1.4.1.311.2.1.12 = 30 00
Content Type = 06 0A 2B 06 01 04 01 82 37 02 01 04
1.3.6.1.4.1.311.2.1.11 = 30 0C 06 0A 2B 06 01 04 01 82 37 02 01 15
Message Digest = 04 14 7E C2 F2 A6 12 C9 44 EE 2F EF C5 05 3F 4B
42 FF BC 23 AF 2E
//****************************************************************************
//****************************************************************************
//Certificate Details
//----------------------------------------------------------------------------
//Item 0 (Windows Mobile TCB Test Signing Cert)
Version = 3
Issued by = Windows Mobile TCB Test CA
Issued to = Windows Mobile TCB Test Signing Cert
Valid from = 1/1/2001 7:00:00 AM
Valid to = 1/1/2039 7:00:00 AM
Issued to:
Common Name = Windows Mobile TCB Test Signing Cert
Issued by:
Common Name = Windows Mobile TCB Test CA
Serial Number = 00 AA 5F 33 25 37 24 96 86 4F 18 FE D0 30 94 E7
7D
Signature Algorithm = SHA1 with RSA
Issuer = Common Name = Windows Mobile TCB Test CA
Valid from = 1/1/2001 7:00:00 AM
Valid to = 1/1/2039 7:00:00 AM
Subject = Common Name = Windows Mobile TCB Test Signing Cert
Size = 864
Signature = 0B 5D 0D 72 A2 43 0D 43 BA 6E EB 88 D9 71 09 27
DF DF 49 E6 8F FB 82 D7 AC 04 BD 22 40 44 C2 3B
3C 89 24 56 5B 2A 1A BE D4 F6 07 82 80 DC 91 24
FA 93 AD D6 11 8C F6 71 65 AC 3E A8 55 72 D1 3D
F5 18 6B 07 80 C6 BA BC B7 CD 9D F8 6A 93 11 B0
7D 2B 9D 3D 09 30 82 59 B2 C2 BF 84 B3 2D 00 C5
99 5C 40 12 90 B7 47 0F 84 3C 3E 14 FF 65 77 DD
91 7E EE 6A 40 1A 4D 93 8A 58 1A 48 25 56 A2 53
7A 89 62 E8 73 C8 E0 E4 EE 20 45 96 C3 4E A3 FB
BD A0 81 05 CB 29 28 5C 18 AD 5E 58 C3 AC 26 55
04 96 3E 5A FD E2 6D 07 A9 DA D7 A5 FB 91 81 F0
8C 8B DF F2 44 67 78 CB D7 93 35 B0 A6 A4 06 5B
A8 29 AC D3 58 1A 36 32 DD D6 64 CE D6 AA 7A 03
50 53 69 F9 57 62 D3 FB AC 6F 54 1F A4 5C 60 5C
6C 6E 33 A7 B6 39 F4 0B B3 B9 7A 71 71 D2 DF CF
DA 6B 92 77 16 97 D1 6F 2F C7 3D 05 BD 9D 90 3D
Self signed = False
Public key = RSA (2056)
RSA Modulus = 00 8E AF 08 1B 5A 81 60 78 84 8B E0 ED 43 75 7D
D1 F4 4C CE 72 07 2C F4 94 2D FA 51 B7 0F 28 CF
60 D5 36 02 7B 89 01 3E D2 26 85 85 F8 2D 18 FF
89 19 23 F3 41 19 77 C7 46 C2 E5 02 28 F0 AD 25
E0 FF 1D E1 4D 63 0A 5F 2E 77 26 3C D3 13 01 87
06 90 FD 12 7F 6B 29 0B 3C 91 06 EC 3A 27 80 79
D4 28 D8 63 FD FB 1A 29 D1 D0 C5 66 48 2A 99 D4
FB 75 81 8F AE 42 A7 D1 49 33 32 EC 25 42 B5 C7
DB 7B AF 63 74 0A 8E CD 4A B8 C5 3D 99 9C 24 FF
AD 6C 4F 0F 2A BD E8 5E 08 67 AC D1 F0 26 13 35
95 BD D0 45 39 FC A8 9F 6F 43 F2 A4 FA 46 C8 ED
18 B0 17 A8 3E 05 AF AB 14 A2 60 15 1A 37 70 2D
44 2A D2 FE 3F EF 53 B7 30 B9 FF A1 D4 7C DC A8
48 9C 74 69 01 56 94 6B 4D 22 CB 74 48 DC A9 93
6C 48 CB 94 6E D4 76 C2 8C 02 FD DA 47 33 44 D3
67 A7 5A 7A 09 CE 97 35 56 9A A6 A1 40 E3 DB 12
99
RSA Public Key = 01 00 01
Authority Key Identifier = Authority Cert Serial=70 12 58 A6 24 F4 3B 46 96 4D E9 64 47 83 EA 20
Key Identifier=31 74 43 25 4D 91 FC 02 0D 5D EF 29 D5 CE 98 A4
Authority Cert Issuer.Directory Name=Common Name = Windows Mobile Test Signing Root
Basic constraints = 30 04 03 02 06 40
Extended key usage = Code signing, Custom Usage : 0
//****************************************************************************

Nice. Did you check to see what the executables are signed with? Say, TIMETEST.exe or ToggleDog.exe? That would be useful to know.

Just using my lovley program "PE Explorer" -> possible to see everything the exe is containing, including signings.
Ther is another way to, the easy way but not all signature data gets extracted
-right click dll -> properties -> {tab} Digital signatures ->
The only info i can get from the dll (ur question), no info about what program it was signed with
  0‚  *†H†÷

*‚ñ0‚í

10 + 0h
+

‚7
*Z0X03
+

‚7
0%
 * ¢€ < < < O b s o l e t e > > >0!0 + ö½ô⹏ì½cÑzi{E…]Õ#ˆ*‚†0‚‚0‚n*
WLj.pA¬MÇе÷´)¡0 + 081604U-Windows Mobile Restricted Rights Test Cert CA0
010101070000Z
[email protected]>U7Windows Mobile Restricted Rights Test Cert Signing Cert0‚
"0
 *†H†÷



 ‚
 0‚

‚

 óAE¡{òïÝ?±Ù‡- Œ,ý‹Øcƒë7Ã*ô]j»,Ïtí²Q›k•ÜÒl¿*&{fiQEòyu¢ð
Ø@y]õù‚Ž¨ñk]¦bÒ€trýu”¯µ^J$´Br6Ûv,ª±Šþ0`„-HÕ,úˆ°iM£¬\&pGÏ¥aCì-Ýk’pÑ‘I3ù£º`¢7ZN˘èÖÅõükª†œÈ¬ãv—y°ÉåP«ù<B¥»¬âHÄòǁ@sÀ1àjgìç3Xzô&ÊO2ŸŸ¼Eµ’»fíçbÈZ¥•ŸhˆZjýKØ
Bºã]t% ¥zõòëÖúoA2±A
 
£…0‚0
U
0@0U%0
+
0\U
U0S€€ðy>¶gSf¡ÆÚց¡j¡-0+1)0'U Windows Mobile Test Signing Root‚#šÉg'x¬¤O»n¯—ï"Ã0 + ‚

 "Oáìw‹¢$&O‚Ø*žÝê ‰õB…eÒw
¢z°-s²`Î\§.N‡>x„²"(.yÝНð£l§ø«ºí†pS„%bžjŠíÉÌ[email protected]‰»
l;ôù2ñhE©§é/":“¥;*׳šÒ‘†¥ûÔ®–(Nd‹Q ¶Ù|}2ÀA·½ÿyô‰Öiµ“Þ’(8aßÛ*ãªx*ÆA8Øü`XÂ5Ê¥²†VöŠWîqƒ!z;*p¿èò•ÁHóŠ›ÄHáÃáíyûî!GÃÊáé¬íâ`‚*üá-Ok°W¤`ñEQnÏ„hé†3ñÔw6*1‚
å0‚
á

0L081604U-Windows Mobile Restricted Rights Test Cert CAWLj.pA¬MÇе÷´)¡0 + *p0
+

‚7
10 0 *†H†÷

 1
+

‚7
0
+

‚7
10
+

‚7
0# *†H†÷

 1¬Ò×ǵrb=Âê«Šü±H:W0
 *†H†÷



 ‚
 A““¸¤~*§
_z§‚^³ü ¢0yyLIU§ç/óh*a}8a·).Ž/n2böþÊ(ºYúAy9´“]ùi”Ö=Ôg5ô¨Ò_ Ëm3Á¼O!ÃWL~bïÅóœþš’v굌†÷®~Õæ+_ê#Nu/ÊÍbö %TTâ´æ¨D©1^GÕø(A¦È¾Ó_ö¬¥Š«£– ¡ØY·Ž0ðš·‘[÷¥«Ç~«#×Á<Cü§¨³ÔÛMQTwn{ Ù-ðÞhò!`òšò,Èc)˜QæC.7TÔp}¯Â+8±@OËÓ‡Wèí³E!åý

A few things...
Unless you've got the private key (you don't) there's no way to just sign our apps. So it doesn't really matter what they're signed with or the signatures, etc. The public key does us no good.
WP7 was referred to as Windows Mobile 7 by the teams inside Microsoft probably up until the Mobile World Congress announcement earlier in the year. It's obvious because many of the softies kept calling it that even after the launch. It takes some time to get used to a name change like that.
Who cares that it says "Windows Mobile"? You don't just create new certificates/CAs willy nilly. And besides, what's the point? The only people that will ever see it are people like us who are poking at things we're not supposed to be poking at.
Are you looking at RTM/production binaries or just the emulator dump? I wouldn't be surprised if they were signed using two different certs. Either way, it doesn't really matter (see above).
They probably just used signtool. I've never heard of TIMETEST or ToggleDog and google shows nothing. signtool has long since been the Microsoft signing tool of choice and there's no sign of that changing anytime soon.

here you go :

[Q] Help with unbricking XPeria Play r800i

Good night.
I have an Xperia Play r800i . I put this kernel http://forum.xda-developers.com/showthread.php?t=1804003 but it froze the first time I was on. Frozen after half an hour, I took the battery and I could not turn it over .
No lights and not vibrate when I press the power . When I connect the USB on the PC recognizes it as Qualcomm QDLoader Device ( COM3 ) and fastboot or flashmode not work.
I tried to identify with Omnius and appears :
[code ]
Action journal
Identify 22:16:10
22:16:10 Shows detailed information about the connected phone .
22:16:10 Operating system : Microsoft Windows NT 6.2 (build 9200 ) , 64 - bit
22:16:10 Application version: 1.41.4828
22:16:10 . The action name is ' Identification '
22:16:10 Selected phone type : R800
22:16:10 Selected connection method: USB ROM
22:16:10 i Instructions
22:16:10 i 1 . Make sure the phone battery is charged to at least 50 % .
22:16:10 i 2 . Switch off the phone !
22:16:10 i 3 . Remove the phone battery and wait at least 5 seconds , then insert the battery back to the phone !
22:16:10 i 4 . Connect the testpoint to phone 's ground ( battery negative pole , metallic shielding circuit , GND ) and leave it connected !
22:16:10 i 5 . Shortly press the power button !
22:16:10 i 6 . Disconnect the testpoint !
22:16:10 i 7 . Connect the cable to the phone !
22:16:10 [ picture ]
22:16:10 . The action started waiting for the user
22:16:18 . The action finished waiting for the user
22:16:18 Connecting via Qualcomm QDLoader Device ( COM3 ) ...
22:16:18 Device driver version: 2.1.0.5
22:16:18 Qualcomm ROM ID : 06010100900000
22:16:18 Sending loader ...
22:16:19 Waiting for loader response ...
22:16:19 . The action started waiting for the user
Additional details
---
2F B4 6E 69 5C EB 9C F5 36 FD 40 C1 3A DB D8 84
D9 94
---
[ / code ]
appears in the status bar : waiting for lc112.zopim.com and is infinititamente this screen.
Anyone have any suggestions on how to fix my phone ?
Thank you.

I tried again on a computer with windows 7 and the following message appeared:
Code:
Action journal
00:37:56 Repair S1-boot
00:37:56 Repairs the S1-boot via USB.
00:37:56 Operating system: Microsoft Windows 7 Ultimate Edition Service Pack 1 (build 7601), 64-bit
00:37:56 Application version: 1.41.4828
00:37:56 . The action name is 'Repair'
00:37:56 Selected phone type: R800
00:37:56 Selected connection method: USB ROM
00:37:56 i Instructions
00:37:56 i 1. Make sure the phone battery is charged to at least 50%.
00:37:56 i 2. Switch off the phone!
00:37:56 i 3. Remove the phone battery and wait at least 5 seconds, then insert the battery back to the phone!
00:37:56 i 4. Connect the testpoint to phone's ground (battery negative pole, metallic circuit shielding, GND) and leave it connected!
00:37:56 i 5. Shortly press the power button!
00:37:56 i 6. Disconnect the testpoint!
00:37:56 i 7. Connect the cable to the phone!
00:37:56 [picture]
00:37:56 . The action started waiting for the user
00:38:05 . The action finished waiting for the user
00:38:05 Connecting via Zeus USB Flash Device (USB1)...
00:38:05 Device driver version: 2.2.0.5
00:38:05 Qualcomm ROM ID: 06010100900000
00:38:05 Sending loader...
00:38:06 Waiting for loader response...
00:38:06 . The action started waiting for the user
00:38:06 . The action finished waiting for the user
00:38:06 Connecting via SEMC USB Flash Device (USB1)...
00:38:06 Device driver version: 3.0.0.0
00:38:06 Sending loader...
00:38:06 Waiting for loader response...
00:38:07 Detected chipset: MSM7X30
00:38:07 IMEI:
00:38:07 Device ID: F37DBE0CA8F291778C06FE8482216B546A9B8601
00:38:07 Minimum loader AID: 0001
00:38:07 Color: Brown
00:38:07 i Waiting for connection to the server...
00:38:10 Receiving news...
00:38:10 i News
00:38:10 i Omnius 1 Year licenses now gained unlimited android unlocking!
00:38:13 Writing S1 boot…
00:38:13 e Failed!
00:38:13 . The action entered shutdown phase
00:38:13 . The action reported failure
Error code
# 9A3F228FFFA50326
Error details
---
33 BB 2A 34 AB BB 7D 90 D1 F8 DE 61 DD 52 9B 0D
D6 E7 F9 DC A7 56 E3 57 7F 7A 61 E8 8A E0 35 0E
27 3A 67 2D 9B FA 1D 9E CF F5 31 D2 3D 3F CC D8
D9 4F 67 04 EB 9C 24 57 B4 94 AF E9 13 A2 2B 59
F0 D5 3C FE 3B DA 43 23 D4 78 7D 4B 30 AB F3 8D
BB 3B 93 45 48 68 3E 81 0B F5 F3 06 76 3B 27 1A
C6 BD 45 6D 88 15 60 F2 BC F3 C2 7B AF 57 E4 1B
05 2F 8A 6F 09 11 68 72 F3 85 EC E8 EC CA 5C DB
3A FC 00 1E 32 32 B8 4F 1C D3 5C 76 66 97 B7 DA
08 F6 20 12 8A BB 84 43 C2 D8 A7 05 9A D2 D0 EC
79 36 26 B4 92 F4 F4 64 D4 56 E9 27 EF 92 0B F9
85 4F 74 19 E1 8F 1F 93 43 21 81 D2 8C 22 55 A8
4D 83 08 4C 89 08 6F D0 11 AA A1 6C 1D 92 21 23
7F 1A 52
---
Can anyone help me?

same problem , anyone have a solution pleaseeeee

Wynna said:
I tried again on a computer with windows 7 and the following message appeared:
Code:
Action journal
00:37:56 Repair S1-boot
00:37:56 Repairs the S1-boot via USB.
00:37:56 Operating system: Microsoft Windows 7 Ultimate Edition Service Pack 1 (build 7601), 64-bit
00:37:56 Application version: 1.41.4828
00:37:56 . The action name is 'Repair'
00:37:56 Selected phone type: R800
00:37:56 Selected connection method: USB ROM
00:37:56 i Instructions
00:37:56 i 1. Make sure the phone battery is charged to at least 50%.
00:37:56 i 2. Switch off the phone!
00:37:56 i 3. Remove the phone battery and wait at least 5 seconds, then insert the battery back to the phone!
00:37:56 i 4. Connect the testpoint to phone's ground (battery negative pole, metallic circuit shielding, GND) and leave it connected!
00:37:56 i 5. Shortly press the power button!
00:37:56 i 6. Disconnect the testpoint!
00:37:56 i 7. Connect the cable to the phone!
00:37:56 [picture]
00:37:56 . The action started waiting for the user
00:38:05 . The action finished waiting for the user
00:38:05 Connecting via Zeus USB Flash Device (USB1)...
00:38:05 Device driver version: 2.2.0.5
00:38:05 Qualcomm ROM ID: 06010100900000
00:38:05 Sending loader...
00:38:06 Waiting for loader response...
00:38:06 . The action started waiting for the user
00:38:06 . The action finished waiting for the user
00:38:06 Connecting via SEMC USB Flash Device (USB1)...
00:38:06 Device driver version: 3.0.0.0
00:38:06 Sending loader...
00:38:06 Waiting for loader response...
00:38:07 Detected chipset: MSM7X30
00:38:07 IMEI:
00:38:07 Device ID: F37DBE0CA8F291778C06FE8482216B546A9B8601
00:38:07 Minimum loader AID: 0001
00:38:07 Color: Brown
00:38:07 i Waiting for connection to the server...
00:38:10 Receiving news...
00:38:10 i News
00:38:10 i Omnius 1 Year licenses now gained unlimited android unlocking!
00:38:13 Writing S1 boot…
00:38:13 e Failed!
00:38:13 . The action entered shutdown phase
00:38:13 . The action reported failure
Error code
# 9A3F228FFFA50326
Error details
---
33 BB 2A 34 AB BB 7D 90 D1 F8 DE 61 DD 52 9B 0D
D6 E7 F9 DC A7 56 E3 57 7F 7A 61 E8 8A E0 35 0E
27 3A 67 2D 9B FA 1D 9E CF F5 31 D2 3D 3F CC D8
D9 4F 67 04 EB 9C 24 57 B4 94 AF E9 13 A2 2B 59
F0 D5 3C FE 3B DA 43 23 D4 78 7D 4B 30 AB F3 8D
BB 3B 93 45 48 68 3E 81 0B F5 F3 06 76 3B 27 1A
C6 BD 45 6D 88 15 60 F2 BC F3 C2 7B AF 57 E4 1B
05 2F 8A 6F 09 11 68 72 F3 85 EC E8 EC CA 5C DB
3A FC 00 1E 32 32 B8 4F 1C D3 5C 76 66 97 B7 DA
08 F6 20 12 8A BB 84 43 C2 D8 A7 05 9A D2 D0 EC
79 36 26 B4 92 F4 F4 64 D4 56 E9 27 EF 92 0B F9
85 4F 74 19 E1 8F 1F 93 43 21 81 D2 8C 22 55 A8
4D 83 08 4C 89 08 6F D0 11 AA A1 6C 1D 92 21 23
7F 1A 52
---
Can anyone help me?
Click to expand...
Click to collapse
The loader is Brown? I've never used omnius after unlocking bootloader but do you have a hdmi xperia play or something? Because your loader should be red aka a retail phone. Brown loaders are developer phones. Please let me know. May be able to help.
Sent from my LT28i using XDA Free mobile app
---------- Post added at 10:48 PM ---------- Previous post was at 10:47 PM ----------
icedheart said:
same problem , anyone have a solution pleaseeeee
Click to expand...
Click to collapse
Did you get the same omnius log
Sent from my LT28i using XDA Free mobile app
---------- Post added at 10:49 PM ---------- Previous post was at 10:48 PM ----------
Also after you installed kernel did you install a Rom from recovery?
Sent from my LT28i using XDA Free mobile app

sorry for late , no my problem i change the kernel in flashtolls after that my phone broken , nothing , and now i conect in my pc show me QHSUSB_LOAD ¬¬

icedheart said:
sorry for late , no my problem i change the kernel in flashtolls after that my phone broken , nothing , and now i conect in my pc show me QHSUSB_LOAD ¬¬
Click to expand...
Click to collapse
Still fixable have to get back to you on that one tho
Sent from my LT28i using XDA Free mobile app

how can I do so , i think my problem is the boot partion , and already I looked everywhere, but not against any solution for restoring the damaged part
anybody have anyone solucion? i can try anything

How to flash samsung device with Odin SS_DL.dll file

how i can flash device via SS_DL.dll
these are the exported function i have found in SS_DL.dll but does not know the paramater and calling sequence
26 00016EF0 Odin_CheckMD5
40 27 00016C70 Odin_Create
41 28 00016FF0 Odin_Destroy
42 29 00016D30 Odin_EnableMD5Check
43 2A 00016FD0 Odin_EndDownload
44 2B 00016CB0 Odin_Init
45 2C 00016E20 Odin_SetBinaryPath
46 2D 00016DF0 Odin_SetDumpPath
47 2E 00016EC0 Odin_SetExtraBinaryPath
48 2F 00016D50 Odin_SetOption
49 30 00016D80 Odin_SetOptionErase
50 31 00016D70 Odin_SetOptionReboot
51 32 00016D90 Odin_SetPacketSize
52 33 00016DC0 Odin_SetPitPath
53 34 00003650 Odin_SetSalesCode
54 35 00016F50 Odin_StartDownload
55 36 00016F90 Odin_StartMultiDownload
pls help any sample code

johnson3143 said:
how i can flash device via SS_DL.dll........
Click to expand...
Click to collapse
Its been a while since I had dealt with this dll file but, I believe that you also need to use the pit file as well.
~~~~~~~~~~~~~~~
UNLESS asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX Forum App on my Enigma Machine {aenigma = Latin for "Riddle"}.

SS_DL.dll exported functions
do you know the no of parameter and parameter types and return type of each function?

johnson3143 said:
how i can flash device via SS_DL.dll
these are the exported function i have found in SS_DL.dll but does not know the paramater and calling sequence
26 00016EF0 Odin_CheckMD5
40 27 00016C70 Odin_Create
41 28 00016FF0 Odin_Destroy
42 29 00016D30 Odin_EnableMD5Check
43 2A 00016FD0 Odin_EndDownload
44 2B 00016CB0 Odin_Init
45 2C 00016E20 Odin_SetBinaryPath
46 2D 00016DF0 Odin_SetDumpPath
47 2E 00016EC0 Odin_SetExtraBinaryPath
48 2F 00016D50 Odin_SetOption
49 30 00016D80 Odin_SetOptionErase
50 31 00016D70 Odin_SetOptionReboot
51 32 00016D90 Odin_SetPacketSize
52 33 00016DC0 Odin_SetPitPath
53 34 00003650 Odin_SetSalesCode
54 35 00016F50 Odin_StartDownload
55 36 00016F90 Odin_StartMultiDownload
pls help any sample code
Click to expand...
Click to collapse
how you exported this functions can you tell me if you can? and thanks for everyting.

You can download the SS_DL.dll files from the website and put them in the C:\\Windows\System32\SS_DL.dll