Develop Bugs

How to completely remove certification from rom

Hello,
how can i completely remove certification from rom (wm2005) prior to flashing?
The registry tweak only disables the security prompt.
This is not enough, as some dll's won't load at startup.
I know this has been done with the himalaya roms but how???
Thanks

i would realy appreciate some input here.
Thanks

i will join the in the hunt .

I found a post from maimach
Find in nk.nba bytes:
F0 40 2D E9 08 D0 4D E2 01 70 A0 E1 00 60 A0 E1 7C 41 9F E5
patch their beginning to:
01 00 A0 E3 1E FF 2F E1
and find F0 4F 2D E9 2C D0 4D E2 03 90 A0 E1 02 A0 A0 E1 01 B0 A0 E1 00 50 B0 E1 00 40 A0 E3 0C 40 8D E5
patch to:
01 00 A0 E3 1E FF 2F E1
find F0 43 2D E9 50 D0 4D E2 03 80 A0 E1 02 50 A0 E1 01 60 A0 E1 00 90 A0 E1 38 E1 9F E5
patch to:
01 00 A0 E3 1E FF 2F E1
first is CertVerify function, second is VerifyFile, third is VerifyCab. Only the first patch is necessary.
Click to expand...
Click to collapse
But when my prophet boots, my screen starts to flicker and it just hanngs at the first screen.
Any comments?

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 :

OBEX and other Transfer Protocol

It seems Kies use OBEX...
AT+SYNCML=MOBEXSTART
First time I saw OBEX was in Brew Mobile Commander in 2006.
Also there was an Plugin for Total Commander...
But this seems not work with S8500.
Other used Protocol is TFS... Samsungs Test Commands. For instance in TkFileExplorer_2.2.exe used.
Hmmm. I need more info/practice about OBEX...
Best Regards

TFS - I saw references to that on the boot loader stuff that was decrypted elsewhere on this forum... Tiny File System, Transparent File System.....?????

New year... old questions.
In Kies you can find several OBEX Commands... like:
m-obex/system/memory
m-obex/application/count
apps_c...
m-obex/fs/info
m-obex/fs/mem_size
In bada 2.0 it seems removed obex... replaced by other stuff...
Anyway. For learning I wish I could use obex Commands successfully.
At the moment no idea how.
Maybe someone could help me.
Best Regards
Edit 1.
Found something via Google...
http://wammu.eu/docs/manual/protocol/m-obex.html
But I sent on XXJL2 AT Command, but can't see any results...
AT+SYNCML=MOBEXSTART

For instance I use WinComm...
AT Commands work on my Port 5...
But if I send this:
AT+SYNCML=MOBEXSTART
AT Commands not more work on COM 5...
Also I get no answer for obex Commands like this:
m-obex/application/count
Is obex open new port?
Or if I sent on 5 I should receive on COM 5 ?
Again many Questions.
Thanx for reading.
Best Regards

todo: implement it in bterm
Code:
Request: AT
41 54 0D 0A
Answer: AT OK
41 54 0D 0D 0A 4F 4B 0D 0A
Request: ATZ
41 54 5A 0D 0A
Answer: ATZ OK
41 54 5A 0D 0D 0A 4F 4B 0D 0A
Request: AT+SYNCML=MOBEXSTART
41 54 2B 53 59 4E 43 4D 4C 3D 4D 4F 42 45 58 53 54 41 52 54 0D 0A
Answer: AT+SYNCML=MOBEXSTART OK
41 54 2B 53 59 4E 43 4D 4C 3D 4D 4F 42 45 58 53 54 41 52 54 0D 4F 4B 0D 0A
Request:
80 00 0F 11 00 20 00 46 00 08 4D 4F 42 45 58
Answer:
A0 00 14 10 00 20 00 CB 00 00 00 01 4A 00 08 4D 4F 42 45 58
#########################################
# Additional command goes here...
#########################################
Request:
81 00 03
Answer:
A0 00 03
Request: ATZ
41 54 5A 0D 0A
Answer: ATZ OK
41 54 5A 0D 0D 0A 4F 4B 0D 0A
commands examples
Code:
Request: m-obex/connection_packet
82 00 23 CB 00 00 00 01 42 00 1B 6D 2D 6F 62 65 78 2F 63 6F 6E 6E 65 63 74 69 6F 6E 5F 70 61 63 6B 65 74
Answer:
A0 00 03
Request: m-obex/security/privacylock
83 00 27 CB 00 00 00 00 42 00 1F 6D 2D 6F 62 65 78 2F 73 65 63 75 72 69 74 79 2F 70 72 69 76 61 63 79 6C 6F 63 6B 00
Answer:
A0 00 12 C3 00 00 00 02 4C 00 05 00 00 49 00 05 00 00
Request: m-obex/fs/privacy_lock
83 00 22 CB 00 00 00 00 42 00 1A 6D 2D 6F 62 65 78 2F 66 73 2F 70 72 69 76 61 63 79 5F 6C 6F 63 6B 00
Answer:
A0 00 0D C3 00 00 00 02 49 00 05 4E 4F *
Request: m-obex/application/count
83 00 27 CB 00 00 00 00 42 00 1C 6D 2D 6F 62 65 78 2F 61 70 70 6C 69 63 61 74 69 6F 6E 2F 63 6F 75 6E 74 00 4C 00 03
Answer:
A0 00 14 C3 00 00 00 04 4C 00 05 00 00 49 00 07 2C 00 00 00
Request: m-obex/system/imsi
83 00 21 CB 00 00 00 00 42 00 16 6D 2D 6F 62 65 78 2F 73 79 73 74 65 6D 2F 69 6D 73 69 00 4C 00 03
Answer: IMSI ;)
A0 00 1F C3 00 00 00 0F 4C 00 05 00 00 49 00 12 .......
Request: ƒm-obex/system/mnc
83 00 20 CB 00 00 00 00 42 00 15 6D 2D 6F 62 65 78 2F 73 79 73 74 65 6D 2F 6D 6E 63 00 4C 00 03
Answer: 02
A0 00 12 C3 00 00 00 02 4C 00 05 00 00 49 00 05 30 32
Request: ƒm-obex/system/csc
83 00 20 CB 00 00 00 00 42 00 15 6D 2D 6F 62 65 78 2F 73 79 73 74 65 6D 2F 63 73 63 00 4C 00 03
Answer: S8500OXAJID
A0 00 1B C3 00 00 00 0B 4C 00 05 00 00 49 00 0E 53 38 35 30 30 4F 58 41 4A 49 44
Request: m-obex/system/openapiversion
83 00 2B CB 00 00 00 00 42 00 20 6D 2D 6F 62 65 78 2F 73 79 73 74 65 6D 2F 6F 70 65 6E 61 70 69 76 65 72 73 69 6F 6E 00 4C 00 03
Answer: 1.2.0_1009152352_LIS_S8500XXJID_XEO
A0 00 33 C3 00 00 00 23 4C 00 05 00 00 49 00 26 31 2E 32 2E 30 5F 31 30 30 39 31 35 32 33 35 32 5F 4C 49 53 5F 53 38 35 30 30 58 58 4A 49 44 5F 58 45 4F
Request: m-obex/application/getinstallsetting
83 00 33 CB 00 00 00 00 42 00 28 6D 2D 6F 62 65 78 2F 61 70 70 6C 69 63 61 74 69 6F 6E 2F 67 65 74 69 6E 73 74 61 6C 6C 73 65 74 74 69 6E 67 00 4C 00 03
Answer:
A0 00 14 C3 00 00 00 04 4C 00 05 00 00 49 00 07 01 00 00 00
---------- Post added at 06:31 PM ---------- Previous post was at 06:29 PM ----------
PS. tested on bada 2.0

Thank you very much.
I got it now.
Tested on bada 1.x
Older then XXJL2 seems to have other syntax...
But I can confirm work also on XXKL6.
Wow. Every little mistake have lead to no further connection...
Best Regards

Oh "surprise"...
Again obelix power...
m-obex/system/restore/start
.
.
See here:
http://forum.xda-developers.com/showpost.php?p=21541765&postcount=4
Best Regards

[Q] Cyanogenmod 7 Nightlies PPTP problem

Hello,
i´m using the latest nightly build of cyanogenmod an i have problems connecting via pptp. Connections is up but no traffic is flowing.
The server is throwing out this in the log file
Code:
2011:03:15-12:41:40 gateway pppd-pptp[14189]: rcvd [LCP ProtRej id=0x59 60 89 31 13 72 c3 22 be 21 d4 f3 ba b1 31 bd 53 33 6a 68 de 9c 22 3c 18 33 77 0d 2f 2d 58 ea c4 ...]
2011:03:15-12:41:40 gateway pppd-pptp[14189]: Protocol-Reject for unsupported protocol 0x6089
2011:03:15-12:41:41 gateway pppd-pptp[14189]: rcvd [LCP ProtRej id=0x5a 00 7d 8a 81 f9 02 5c 2d 7d 46 ed 77 a3 f8 af 9a ee 6e 90 0d 11 d3 db d7 49 c6 a3 a3 cd 32 99 b4 ...]
2011:03:15-12:41:41 gateway pppd-pptp[14189]: Protocol-Reject for unsupported protocol 0x7d
2011:03:15-12:41:42 gateway pppd-pptp[14189]: rcvd [LCP ProtRej id=0x5b 32 c0 30 78 97 25 fd 0b 05 35 5b dd 37 a8 6f 19 3c e4 a0 21 17 e7 21 98 58 c9 e4 3f 4f 1a ed c0 ...]
2011:03:15-12:41:42 gateway pppd-pptp[14189]: Protocol-Reject for unsupported protocol 0x32c0
2011:03:15-12:41:43 gateway pppd-pptp[14189]: rcvd [LCP ProtRej id=0x5c 48 33 fa 47 8a 95 fb cf 32 93 85 1d d1 67 2f bc 9e b2 c5 60 c6 4e 67 7c 65 c8 2f cb c3 c5 93 2a ...]
2011:03:15-12:41:43 gateway pppd-pptp[14189]: Protocol-Reject for unsupported protocol 0x4833
i thought this was fixed a few builds ago in the nightlies?
Sorry for posting here, but i have not enought postings i to ask my question in
the nightlies thread.

Enter S8600 store with your Wave 1 or 2...

Any idea how Kies identify model? It seems not via AT Commands...
Or I am dumb...
AT+DEVCONINFO
I have used portmon to sniff communication...
Maybe it is the name, what Explorer shows?...
So the mass thingie USB driver...
How for instance S8600 answers in Explorer?
Best Regards

May be it?
http://forum.xda-developers.com/showpost.php?p=11286021&postcount=78

amss.bin I have checked... maybe not.
I have tried MANY combinations... maybe I have something not seen.
Maybe much easier.
Little example how bada Version is checked... Attention, high protection...
extreme hardcoded to prevent change...
2 parts needed...
Part 1:
SystemFS\User\OspSys\registry\buildnumber.ini
Part 2:
SystemFS/User/OspSys/registry/systeminfo.ini
Compare with latest Firmware and you know how to prepare your bada 1.x device for bada 3.0 Apps.
Anyway, I'm blind to manage Kies to work as S8600...
Best Regards

Okay, I've found Original Screenshot of S8600...
But I know where this Text String is stored...
But I can remember, I've tried this... and was not enough...
Maybe I'll try again.
Best Regards

It can be usb device description string in USB driver on phone or PC side (if it's PC side, description is paired with certain PID and VID), try to connect phone to linux in kies mode and use lsusb -a (aint sure if it's -a, anyway the thing is to get verbose info about device)

Hi, I think stune reads the same data that the kies when connected to the terminal.
I mean:
STUNE when you start telling us the firmware version terminal model of our product code, even our imei

Not fully correct
There is something in the PC driver that needs to be changed
You can see this in the driver details
Best Regards

Maybe Kies via Wi-Fi easier...
Not tested yet.
Best Regards

Bus reported device description is sent from device during USB enumeration. So model id is stored in Bada USB module. I'm nearly sure it's unicode string.

Maybe my fault...
AT+PROF="Device
Leads to file device.xml...
Will compare Wave 1, 2, 3 device.xml ...
Best Regards
Edit 1...
Code:
<ModelName value="GT-S8500"/>
<BaseModelName value="GT-S8500"/>
<ProjectName value="Lismore"/>
<FriendlyName value="Lismore"/>
<ProductLineup value="HHP"/>
Code:
<ModelName value="Wave 3"/>
<BaseModelName value="GT-S7250"/>
<ProjectName value="Wave3"/>
<FriendlyName value="Wave3"/>
<ProductLineup value="HHP"/>

Kies now shows other Error
Please, maybe someone can post from S8600 under Explorer...
Remember to remove IMEI...
I think this is MTP device... USB blabla portable Device Driver under Device Manager in Windows...
PS...
Text Samsung... in white Background is editable...
Edit 1.
Hmmm... Wave 2 can't edit ... grey colored...
Screenshot from S8600 would be nice.
Thanx in advance.

why do you think AT+DEVCONINFO is wrong? whole infos including imei in one packet

http://forum.xda-developers.com/showpost.php?p=20497198&postcount=15
Because I've found all files and positions to make 1:1 clone... including IMEI...
But this is not working for Kies.
Kies shows Error, that unsupported device is attached.
Best Regards

error it is kind of progress
what about these ones
Code:
Request: m-obex/connection_packet
82 00 23 CB 00 00 00 01 42 00 1B 6D 2D 6F 62 65 78 2F 63 6F 6E 6E 65 63 74 69 6F 6E 5F 70 61 63 6B 65 74
Answer:
A0 00 03
Request: m-obex/security/privacylock
83 00 27 CB 00 00 00 00 42 00 1F 6D 2D 6F 62 65 78 2F 73 65 63 75 72 69 74 79 2F 70 72 69 76 61 63 79 6C 6F 63 6B 00
Answer:
A0 00 12 C3 00 00 00 02 4C 00 05 00 00 49 00 05 00 00
Request: m-obex/fs/privacy_lock
83 00 22 CB 00 00 00 00 42 00 1A 6D 2D 6F 62 65 78 2F 66 73 2F 70 72 69 76 61 63 79 5F 6C 6F 63 6B 00
Answer:
A0 00 0D C3 00 00 00 02 49 00 05 4E 4F *
Request: m-obex/application/count
83 00 27 CB 00 00 00 00 42 00 1C 6D 2D 6F 62 65 78 2F 61 70 70 6C 69 63 61 74 69 6F 6E 2F 63 6F 75 6E 74 00 4C 00 03
Answer:
A0 00 14 C3 00 00 00 04 4C 00 05 00 00 49 00 07 2C 00 00 00
Request: m-obex/system/imsi
83 00 21 CB 00 00 00 00 42 00 16 6D 2D 6F 62 65 78 2F 73 79 73 74 65 6D 2F 69 6D 73 69 00 4C 00 03
Answer: IMSI ;)
A0 00 1F .....
Request: ƒm-obex/system/mnc
83 00 20 CB 00 00 00 00 42 00 15 6D 2D 6F 62 65 78 2F 73 79 73 74 65 6D 2F 6D 6E 63 00 4C 00 03
Answer: 02
A0 00 12 C3 00 00 00 02 4C 00 05 00 00 49 00 05 30 32
Request: ƒm-obex/system/csc
83 00 20 CB 00 00 00 00 42 00 15 6D 2D 6F 62 65 78 2F 73 79 73 74 65 6D 2F 63 73 63 00 4C 00 03
Answer: S8500OXAJID
A0 00 1B C3 00 00 00 0B 4C 00 05 00 00 49 00 0E 53 38 35 30 30 4F 58 41 4A 49 44
Request: m-obex/system/openapiversion
83 00 2B CB 00 00 00 00 42 00 20 6D 2D 6F 62 65 78 2F 73 79 73 74 65 6D 2F 6F 70 65 6E 61 70 69 76 65 72 73 69 6F 6E 00 4C 00 03
Answer: 1.2.0_1009152352_LIS_S8500XXJID_XEO
A0 00 33 C3 00 00 00 23 4C 00 05 00 00 49 00 26 31 2E 32 2E 30 5F 31 30 30 39 31 35 32 33 35 32 5F 4C 49 53 5F 53 38 35 30 30 58 58 4A 49 44 5F 58 45 4F
Request: m-obex/application/getinstallsetting
83 00 33 CB 00 00 00 00 42 00 28 6D 2D 6F 62 65 78 2F 61 70 70 6C 69 63 61 74 69 6F 6E 2F 67 65 74 69 6E 73 74 61 6C 6C 73 65 74 74 69 6E 67 00 4C 00 03
Answer:
A0 00 14 C3 00 00 00 04 4C 00 05 00 00 49 00 07 01 00 00 00
m-obex/system/csc and
m-obex/system/openapiversion ?

Thank you.
m-obex I have no success because also not enough knowledge.
See here:
http://forum.xda-developers.com/showpost.php?p=20954943&postcount=3
Best Regards

I've somewhere correct sequence to start obex on wave. I will post later

Good afternoon if it will not for anything in this case but I found this on apps_compressed:
x40BF86FF 'kDHd:! eNULL: @ STRENGTH'
0x40BF8765 'eNULL:! ANULL: @ STRENGTH'
0x40BF8784:'/../ cx / source / Xsupplicant / src / auth_methods / eapfast / eapfast.c '
0x40BF889C:'/../ cx / source / Xsupplicant / src / auth_methods / eapfast / eapfast_key.c '
0x40BFAE8C '/ www.openssl.org / support / faq.html'
0x40BFB506: '23456789ABCDEF '
0x40BFC610 '] VOHyrkd'
0x40BFD099: '56789.: AbcdefABCDEF '

ferrloz said:
Good afternoon if it will not for anything in this case but I found this on apps_compressed:
x40BF86FF 'kDHd:! eNULL: @ STRENGTH'
0x40BF8765 'eNULL:! ANULL: @ STRENGTH'
0x40BF8784:'/../ cx / source / Xsupplicant / src / auth_methods / eapfast / eapfast.c '
0x40BF889C:'/../ cx / source / Xsupplicant / src / auth_methods / eapfast / eapfast_key.c '
0x40BFAE8C '/ www.openssl.org / support / faq.html'
0x40BFB506: '23456789ABCDEF '
0x40BFC610 '] VOHyrkd'
0x40BFD099: '56789.: AbcdefABCDEF '
Click to expand...
Click to collapse
Umm, sorry, it's not helping anything in that case. FYI there are literally tenths of thousands such char strings in apps_compressed. Good you're looking tho. ;P

Maybe my goal is not clear enough...
Most of us have NO S8600...
But S8600 has few nice NEW Apps.
You can download without attached handset EVERY App you can find via Kies.
BUT not install if attached handset is not valid...
My goal is to make S8500 valid to install S8600 Apps via Kies.
Solution 1 is wait...
Maybe Samsung will offer these Apps like Tintin before Christmas 2012...
Really realistic...
I think minimum 2-3 months not available for S8500/S8530 to be exclusive for S8600...
Solution...
Move your bu ehm brain.
This mission is NOT impossible.
Best Regards

Sorry for them to lose the time, now I will focus more on the subject.
ferrloz thanks.