Too much things in the original post "HTC Sapphire/Vodafone Magic G1 Port".
I'd like to focus on solutions to solve the market issues on 5.0.xG versions.
PLEASE : NO TROLL such as "move to 5.0.xH version, it's better, and it works". Move to another post to troll.
We are here to find solution.
Few ideas have been discussed in the original post such as vendink.apk version or build.prop.
Does anybody have more ideas ?
here is a dump of HTTP packets transiting during a Market application request (useful siwtchers)
It was done (and failed) with 5.0.1G
It could be very interesting to view the same exchange with a working Market version such as 5.0.2H or ADP1. Anybody can do the same capture ? I used BackTrak Linux distribution to did that.
We can see an interesting string in the Market HTTP request : "location,1.0,android,android,en_US.5........g...........g:loc/ql...........1.0.Tandroid/tmobile/kila/dream/trout:1.1/PLAT-RC33/126986:user/ota-rel-keys,release-keys.#2:ddGVOXszuvQlZm8K:1TxOlLJHRfpoZ92D*.fr_FR2.....F SFR .(......server.checkin....settings....location....systemupdater....android....providers.subscribedfeeds....providers.settings"
http://koxx3.free.fr/http_android.cap
http://koxx3.free.fr/http_android.txt
No. Time Source Destination Protocol Info
217 4.254998 192.168.0.104 209.85.229.104 HTTP [TCP Previous segment lost] Continuation or non-HTTP traffic
Frame 217 (881 bytes on wire, 881 bytes captured)
IEEE 802.11 Data, Flags: ...P...T
Logical-Link Control
Internet Protocol, Src: 192.168.0.104 (192.168.0.104), Dst: 209.85.229.104 (209.85.229.104)
Transmission Control Protocol, Src Port: 43119 (43119), Dst Port: http (80), Seq: 139, Ack: 1, Len: 797
Source port: 43119 (43119)
Destination port: http (80)
Sequence number: 139 (relative sequence number)
[Next sequence number: 936 (relative sequence number)]
Acknowledgement number: 1 (relative ack number)
Header length: 32 bytes
Flags: 0x18 (PSH, ACK)
Window size: 5840 (scaled)
Checksum: 0xe072 [correct]
Options: (12 bytes)
[SEQ/ACK analysis]
Hypertext Transfer Protocol
Data (797 bytes)
Data: 00020000226C6F636174696F6E2C312E302C616E64726F69...
0000 08 11 2c 00 00 14 bf 26 7c d8 00 18 41 f3 15 41 ..,....&|...A..A
0010 00 14 bf 26 7c d6 f0 0e aa aa 03 00 00 00 08 00 ...&|...........
0020 45 00 03 51 cd c2 40 00 40 06 f2 15 c0 a8 00 68 [email protected]@......h
0030 d1 55 e5 68 a8 6f 00 50 92 10 67 a4 c3 69 e7 ee .U.h.o.P..g..i..
0040 80 18 0b 68 e0 72 00 00 01 01 08 0a 00 05 aa b6 ...h.r..........
0050 92 94 e5 d0 00 02 00 00 22 6c 6f 63 61 74 69 6f ........"locatio
0060 6e 2c 31 2e 30 2c 61 6e 64 72 6f 69 64 2c 61 6e n,1.0,android,an
0070 64 72 6f 69 64 2c 65 6e 5f 55 53 87 35 04 ae 15 droid,en_US.5...
0080 0b e4 9a 00 01 67 00 00 02 e4 00 01 00 00 09 00 .....g..........
0090 08 67 3a 6c 6f 63 2f 71 6c 00 00 00 00 02 d2 0a .g:loc/ql.......
00a0 97 01 0a 03 31 2e 30 12 54 61 6e 64 72 6f 69 64 ....1.0.Tandroid
00b0 2f 74 6d 6f 62 69 6c 65 2f 6b 69 6c 61 2f 64 72 /tmobile/kila/dr
00c0 65 61 6d 2f 74 72 6f 75 74 3a 31 2e 31 2f 50 4c eam/trout:1.1/PL
00d0 41 54 2d 52 43 33 33 2f 31 32 36 39 38 36 3a 75 AT-RC33/126986:u
00e0 73 65 72 2f 6f 74 61 2d 72 65 6c 2d 6b 65 79 73 ser/ota-rel-keys
00f0 2c 72 65 6c 65 61 73 65 2d 6b 65 79 73 1a 23 32 ,release-keys.#2
0100 3a 64 64 47 56 4f 58 73 7a 75 76 51 6c 5a 6d 38 :ddGVOXszuvQlZm8
0110 4b 3a 31 54 78 4f 6c 4c 4a 48 52 66 70 6f 5a 39 K:1TxOlLJHRfpoZ9
0120 32 44 2a 05 66 72 5f 46 52 32 0e 08 05 12 05 46 2D*.fr_FR2.....F
0130 20 53 46 52 20 0a 28 d0 01 12 10 0a 0e 73 65 72 SFR .(......ser
0140 76 65 72 2e 63 68 65 63 6b 69 6e 12 0a 0a 08 73 ver.checkin....s
0150 65 74 74 69 6e 67 73 12 0a 0a 08 6c 6f 63 61 74 ettings....locat
0160 69 6f 6e 12 0f 0a 0d 73 79 73 74 65 6d 75 70 64 ion....systemupd
0170 61 74 65 72 12 09 0a 07 61 6e 64 72 6f 69 64 12 ater....android.
0180 1b 0a 19 70 72 6f 76 69 64 65 72 73 2e 73 75 62 ...providers.sub
0190 73 63 72 69 62 65 64 66 65 65 64 73 12 14 0a 12 scribedfeeds....
01a0 70 72 6f 76 69 64 65 72 73 2e 73 65 74 74 69 6e providers.settin
01b0 67 73 22 bc 03 0a ac 01 0a 0e 08 98 2a 10 90 ce gs".........*...
01c0 04 18 0a 20 d0 01 28 08 10 a7 a1 c4 82 8b 24 1a ... ..(.......$.
01d0 1f 08 ff ff ff ff ff ff ff ff ff 01 10 ff ff ff ................
01e0 ff ff ff ff ff ff 01 18 0a 20 d0 01 28 14 40 72 ......... ..([email protected]
01f0 1a 20 08 ff ff ff ff ff ff ff ff ff 01 10 ff ff . ..............
0200 ff ff ff ff ff ff ff 01 18 0a 20 d0 01 28 00 40 .......... ..([email protected]
0210 94 03 22 12 08 98 2a 10 90 ce 04 18 0a 20 d0 01 .."...*...... ..
0220 28 08 30 c7 f4 07 22 12 08 98 2a 10 8e ce 04 18 (.0..."...*.....
0230 0a 20 d0 01 28 09 30 d3 d6 07 22 12 08 98 2a 10 . ..(.0..."...*.
0240 90 ce 04 18 0a 20 d0 01 28 09 30 f2 9e 04 22 12 ..... ..(.0...".
0250 08 98 2a 10 8e ce 04 18 0a 20 d0 01 28 08 30 f6 ..*...... ..(.0.
0260 ba 03 28 02 12 85 02 08 f7 a5 c4 82 8b 24 12 13 ..(..........$..
0270 0a 11 30 30 3a 31 34 3a 62 66 3a 32 36 3a 37 63 ..00:14:bf:26:7c
0280 3a 64 38 12 13 0a 11 30 30 3a 31 61 3a 36 62 3a :d8....00:1a:6b:
0290 62 34 3a 61 34 3a 34 65 12 13 0a 11 30 30 3a 31 b4:a4:4e....00:1
02a0 36 3a 34 31 3a 30 34 3a 32 65 3a 35 65 12 13 0a 6:41:04:2e:5e...
02b0 11 30 30 3a 31 61 3a 32 62 3a 36 63 3a 66 65 3a .00:1a:2b:6c:fe:
02c0 62 34 12 13 0a 11 30 30 3a 30 37 3a 63 62 3a 35 b4....00:07:cb:5
02d0 30 3a 32 31 3a 35 36 12 13 0a 11 30 30 3a 31 36 0:21:56....00:16
02e0 3a 34 31 3a 30 34 3a 36 34 3a 64 61 12 13 0a 11 :41:04:64:da....
02f0 61 32 3a 34 61 3a 35 35 3a 61 33 3a 34 33 3a 66 a2:4a:55:a3:43:f
0300 37 12 13 0a 11 37 65 3a 62 64 3a 66 33 3a 39 35 7....7e:bd:f3:95
0310 3a 64 39 3a 36 37 12 13 0a 11 30 30 3a 31 36 3a :d9:67....00:16:
0320 63 65 3a 32 35 3a 37 36 3a 64 32 12 13 0a 11 30 ce:25:76:d2....0
0330 30 3a 30 33 3a 63 39 3a 36 66 3a 64 38 3a 65 31 0:03:c9:6f:d8:e1
0340 12 13 0a 11 30 30 3a 32 32 3a 33 66 3a 32 65 3a ....00:22:3f:2e:
0350 33 38 3a 35 37 12 13 0a 11 30 30 3a 30 37 3a 63 38:57....00:07:c
0360 62 3a 35 31 3a 39 38 3a 34 37 18 02 9a 06 02 08 b:51:98:47......
0370 01 .
No. Time Source Destination Protocol Info
236 4.440358 209.85.229.104 192.168.0.104 HTTP [TCP Previous segment lost] Continuation or non-HTTP traffic
Frame 236 (419 bytes on wire, 419 bytes captured)
IEEE 802.11 Data, Flags: ..m...F.
Logical-Link Control
Internet Protocol, Src: 209.85.229.104 (209.85.229.104), Dst: 192.168.0.104 (192.168.0.104)
Transmission Control Protocol, Src Port: http (80), Dst Port: 43119 (43119), Seq: 289, Ack: 936, Len: 335
Source port: http (80)
Destination port: 43119 (43119)
Sequence number: 289 (relative sequence number)
[Next sequence number: 624 (relative sequence number)]
Acknowledgement number: 936 (relative ack number)
Header length: 32 bytes
Flags: 0x18 (PSH, ACK)
Window size: 8384 (scaled)
Checksum: 0x10b9 [correct]
Options: (12 bytes)
[SEQ/ACK analysis]
Hypertext Transfer Protocol
Data (335 bytes)
Data: 0002000001478100000900C8000167000001F21F8B080000...
0000 08 22 2c 00 00 18 41 f3 15 41 00 14 bf 26 7c d8 .",...A..A...&|.
0010 00 14 bf 26 7c d6 a0 39 aa aa 03 00 00 00 08 00 ...&|..9........
0020 45 00 01 83 f5 7f 00 00 34 06 18 27 d1 55 e5 68 E.......4..'.U.h
0030 c0 a8 00 68 00 50 a8 6f c3 69 e9 0e 92 10 6a c1 ...h.P.o.i....j.
0040 80 18 00 83 10 b9 00 00 01 01 08 0a 92 94 e6 bb ................
0050 00 05 aa b6 00 02 00 00 01 47 81 00 00 09 00 c8 .........G......
0060 00 01 67 00 00 01 f2 1f 8b 08 00 00 00 00 00 00 ..g.............
0070 00 8d 90 3f 4b c3 50 14 c5 1b eb 10 82 4a 4c 29 ...?K.P......JL)
0080 84 68 21 a8 20 74 7a 79 7f 93 33 b9 09 76 f1 23 .h!. tzy..3..v.#
0090 f8 f2 8f 82 8b ae 3a 08 ae 2e 4e 22 88 f5 03 b8 ......:...N"....
00a0 fa 11 04 c1 41 9c 9c fd 02 6e ee 7a 4b 5b 43 d1 ....A....n.zK[C.
00b0 c1 37 3d ee 39 f7 77 0e d7 6d 05 1f 6d b7 15 84 .7=.9.w..m..m...
00c0 9e b7 fc 76 b8 de eb b2 e7 dc 09 af 9c 78 97 dd ...v.........x..
00d0 3d 3d 9e 5f 6c 45 9b 5e 87 b4 95 21 69 ef 19 69 ==._lE.^...!i..i
00e0 9f ed 78 b0 b3 10 2c b9 d7 7d ff f2 65 31 f4 e2 ..x...,..}..e1..
00f0 57 27 ea 05 6b ee d7 ec 39 7e f3 fd 97 dc 8d 3a W'..k...9~.....:
0100 de 2a 63 48 34 64 02 26 a1 25 4a 1b 6d 7b 3e 25 .*cH4d.&.%J.m{>%
0110 1f 9f 51 f2 f0 86 92 07 f1 7e 63 2c 2a 70 05 a3 ..Q......~c,*p..
0120 51 f2 c9 be e5 90 16 4a c1 0a 48 81 da fc 60 39 Q......J..H...`9
0130 87 a8 c1 2b 88 14 ca 4c b1 e2 94 b0 1b f7 84 3d ...+...L.......=
0140 68 b0 16 3c 87 2e 50 57 c8 65 53 cb 42 e7 34 80 h..<..PW.eS.B.4.
0150 95 90 d5 64 6c c8 51 a2 16 c8 14 ca 0c 7a 86 dd ...dl.Q......z..
0160 1b 63 4f 46 73 6d 99 41 91 43 51 91 04 4a 37 58 .cOFsm.A.CQ..J7X
0170 89 9c 6a 69 98 02 65 fa fb 08 54 58 55 53 ac df ..ji..e...TXUS..
0180 27 ec c3 51 31 87 15 28 28 b9 a6 65 54 c9 d4 c8 '..Q1..((..eT...
0190 c6 f9 b8 fd 2b 3f 41 96 42 9a 6f d5 ef 07 79 f2 ....+?A.B.o...y.
01a0 01 00 00 ...
Click to expand...
Click to collapse
I've been following the haykuro megathread...so I wanted to throw out what people are talking about there.
It's possible that there is a difference between the way H and G builds are identifying themselves. We've got a dump from the G build, can anyone get one from the H build so we can compare? That's the first step to either identifying this as the problem or ruling it out. If we can rule out the identification factor it may come down to the actual vending.apk just having a bug, or maybe that specific version of vending.apk is being identified by google. Anyway, it's a start.
TemporalShadows said:
I've been following the haykuro megathread...so I wanted to throw out what people are talking about there.
It's possible that there is a difference between the way H and G builds are identifying themselves. We've got a dump from the G build, can anyone get one from the H build so we can compare? That's the first step to either identifying this as the problem or ruling it out. If we can rule out the identification factor it may come down to the actual vending.apk just having a bug, or maybe that specific version of vending.apk is being identified by google. Anyway, it's a start.
Click to expand...
Click to collapse
do you know if anybody try do pick a vendor.apk from H and run it on G ?
another intersting thing can be to explore build.prop (because it is really used for Market exchange) difference to be sure we can't use G market app (with H build.prop file).
can anybody post a /system/build.prop file in H & G versions here ?
koxx said:
do you know if anybody try do pick a vendor.apk from H and run it on G ?
another intersting thing can be to explore build.prop (because it is really used for Market exchange) difference to be sure we can't use G market app (with H build.prop file).
can anybody post a /system/build.prop file in H & G versions here ?
Click to expand...
Click to collapse
H version of vendor.apk doesn't work on G. At least when I tried it.
Hasn't this already been fixed?
http://code.google.com/p/sapphire-port-dream/downloads/list
koxx said:
another intersting thing can be to explore build.prop (because it is really used for Market exchange) difference to be sure we can't use G market app (with H build.prop file).
can anybody post a /system/build.prop file in H & G versions here ?
Click to expand...
Click to collapse
There's no need; they are identical. If you don't believe me, open H and G update.zip in an archive manager and look at the build.prop checksums. They are identical.
ok ... "good".
here is 5.0.1G build.prop
http://koxx3.free.fr/build.prop.5.0.1G
we really need 5.0.2H build.prop file
do you konw how to get it ?
grokdesigns said:
Hasn't this already been fixed?
http://code.google.com/p/sapphire-port-dream/downloads/list
Click to expand...
Click to collapse
That fix did not resolve the issue.
build.prop from 5.0G and 5.0H are exactly the same..
i'm looking into the issue now. will post back here when it is resolved.
common string between build.prop and HTTP request :
ro.build.fingerprint=tmobile/kila/dream/trout:1.1/PLAT-RC33/126986:user/ota-rel-keys,release-keys
HTTP request : "location,1.0,android,android,en_US.5........g.... .......g:loc/ql...........1.0.Tandroid/tmobile/kila/dream/trout:1.1/PLAT-RC33/126986:user/ota-rel-keys,release-keys.#2:ddGVOXszuvQlZm8K:1TxOlLJHRfpoZ92D*.fr_FR2. ....F SFR .(......server.checkin....settings....location.... systemupdater....android....providers.subscribedfe eds....providers.settings"
Hey Koxx; do you have any quick way of getting your tcp-dump data easily? I'd be glad to help then.
haykuro said:
build.prop from 5.0G and 5.0H are exactly the same..
Click to expand...
Click to collapse
OK, no need to look into this point.
haykuro said:
i'm looking into the issue now. will post back here when it is resolved.
Click to expand...
Click to collapse
Can the "new" G market application transmit more or different informations with same build.prop ?
emms007 said:
Hey Koxx; do you have any quick way of getting your tcp-dump data easily? I'd be glad to help then.
Click to expand...
Click to collapse
easy, not exactly, but not too long.
You need a Laptop with Wifi & a home acces point.
You download a Linux distribution specialized for wifi security test (suck as BackTrak, here : http://www.remote-exploit.org/backtrack_download.html)
You boot on this Live CD.
Here are commands to log wifi packets :
ifconfig wlan0 up
airmon-ng start wlan0
airodump-ng wlan0
airodump-ng wlan0 -c 7 -w nom_fichier # 7 etant le canal wifi des echanges entre ton AP et ton G1
easy
J'avais jamais fait, ca m'a pris moins d'une heure.
Typically...if we're talking about the old rules (no tinfoil hats) the build was identified by the market using the ro.build.fingerprint from the build.prop.
That's what we had to change to make PAID apps work in both builds.
BUT, you can copy the H build.prop to G and it doesn't fix the problem.
I have yet to see anywhere what Haykuro did to make the R2 builds.
Try copying H version's gtalkservice.apk along with Vending.apk
TheDudeOfLife said:
BUT, you can copy the H build.prop to G and it doesn't fix the problem.
Click to expand...
Click to collapse
Did you read what I (and subsequently Hakuro) wrote above? the build properties are identical.
I did a tcpdump on my 5.0.2H and did a successful download. follow the tcpstream in wireshark and I don't see anything similar to
HTTP request : "location,1.0,android,android,en_US.5........g .... .......g:loc/ql...........1.0.Tandroid/tmobile/kila/dream/trout:1.1/PLAT-RC33/126986:user/ota-rel-keys,release-keys.#2:ddGVOXszuvQlZm8K:1TxOlLJHRfpoZ92D*.fr_FR2. ....F SFR .(......server.checkin....settings....location.... systemupdater....android....providers.subscribedfe eds....providers.settings"
Click to expand...
Click to collapse
As I said in the other thread I am sure the market issue has something to do with the market application version. With the almost same build.prop between H and G there's no difference exchanging them.
The interesting part is that G says for "build number" (directly on the phone) PLAT-RC33 (or something like that, forgotten) with the same build.prop. So I edited the build.prop many many times and tried much more options and and and.
Yesterday I flashed back to JF. Installed all my apps directly from the market again. This morning I've downloaded a new application and after that I saw the new uploaded Haykuro build which said "fixed market". I've flashed (wiped twice before and once after) and then configured (APN, wireless networks, etc.) and rebooted the device. After the device rebooted I saw the arrow-down-icon in the notification bar - the application I've downloaded this morning was automatically downloaded and installed. I was happy and thought "Cool, it's really fixed!". But: I couldn't download anything form the market (stalled "downloading file").
My guess is, that Google updated something in the communication between server (market online) and client (market application) for the upcoming Android phones and/or SDK 1.5 - so the "old" client versions act like before and the "new" client versions are somehow blocked/stalled/whatever.
whatchamccallum said:
I did a tcpdump on my 5.0.2H and did a successful download. follow the tcpstream in wireshark and I don't see anything similar to
Click to expand...
Click to collapse
perfect !!!!
can you give all the exchange ? with hexa values ?
and the HTTP answer from google server ?
mrcrb said:
As I said in the other thread I am sure the market issue has something to do with the market application version. With the almost same build.prop between H and G there's no difference exchanging them.
The interesting part is that G says for "build number" (directly on the phone) PLAT-RC33 (or something like that, forgotten) with the same build.prop. So I edited the build.prop many many times and tried much more options and and and.
Yesterday I flashed back to JF. Installed all my apps directly from the market again. This morning I've downloaded a new application and after that I saw the new uploaded Haykuro build which said "fixed market". I've flashed (wiped twice before and once after) and then configured (APN, wireless networks, etc.) and rebooted the device. After the device rebooted I saw the arrow-down-icon in the notification bar - the application I've downloaded this morning was automatically downloaded and installed. I was happy and thought "Cool, it's really fixed!". But: I couldn't download anything form the market (stalled "downloading file").
My guess is, that Google updated something in the communication between server (market online) and client (market application) for the upcoming Android phones and/or SDK 1.5 - so the "old" client versions act like before and the "new" client versions are somehow blocked/stalled/whatever.
Click to expand...
Click to collapse
sounds solid, they're probably updating for 1.5 and did something so that only version 1.5 would be effected by the maintenance, thus causing the slowdown for us(my guess this is probably just a different market application, maybe one that goes through a different server). It definitely isn't blocking downloads though as I've had 3 go through so far. Each one just took a ridiculously long time.
i use LPT connection jtag.but ntrst no connection.
jtag eror:
upper and lower flash memory ID does not match.
You may have a damaged flash memory.
upper half reads:90
lower half reads:A
help me,thanks
http://wiki.xda-developers.com/index.php?auto_redirect=1&pagename=TitleSearch&s=jtag
here are some jtag guides
thank you
use h-jtag connection CPU（PXA270）success.but connection FLASH error.
LPT connection jtag:
LPT2=TCK;
LPT3=TDI;
LPT4=TMS;
LPT11=TDO;
LPT18-25=battery(-);
NTRST=null
jflashmm pxa27x32 ebo_a.nb0 N 0 PAR
jflashmm pxa27x32 ebo_a.nb0 N 3F40000 PAR
upper and lower flash memory ID does not match.
You may have a damaged flash memory.
upper half reads:90
lower half reads:A
i have find flash.
M-Systems
Flash Disk Pioneers
DiskOnChip MCP
MS25-010SD9-B3-P
japan 064IKAD-P23718
I have a cell phone X01T/g900. When brushing IPL, I brushed OS ROM（*.dip）document through my own carelessness.Now the phenomenon of my phone boot is: after the green light and keyboard light lit,and then the keyboard light went out.In addition, the phone can be a normal charge.
Now we consider the JTAG brush method.There are TCK, TMS, TDI, TDO, NTRST on Board.I used TCK to access LPT D2,TMS to access LPT D4,TD0 to access LPT D11,TDI to access LPT D3,NTRST to access grounding.I used the following command, and the results are as follows.Thanks for giving helps.
The eboot_m3m4.nb0 is in Recovery.7z. It also contains FLASH.DIO，IPLMDOC.nb0，FLASH_RESERVE.DIO，xldr_mdoc4.nb0，TF__ORCA.xld file.
jflashmm pxa27x32 eboot_m3m4.nb0 N 0 PAR
JFLASH Version 5.01.007
COPYRIGHT (C) 2000 - 2003 Intel Corporation
PLATFORM SELECTION:
Processor= PXA27x
Development System= Mainstone
Data Version= 1.00.001
PXA27x revision ??
Failed to read the Flash ID. Retrying 4 more times...
Failed to read the Flash ID. Retrying 3 more times...
Upper and Lower flash memory ID does not match.
You may have a damaged flash memory.
Upper half reads: 90
Lower half reads: A
Failed to read the Flash ID. Retrying 2 more times...
Upper and Lower flash memory ID does not match.
You may have a damaged flash memory.
Upper half reads: 90
Lower half reads: A
Failed to read the Flash ID. Retrying 1 more times...
Upper and Lower flash memory ID does not match.
You may have a damaged flash memory.
Upper half reads: 90
Lower half reads: A
Failed to read the Flash ID. Retrying 0 more times...
Cannot open input file: Flash_A_2_32.dat
This program supports flash devices defined by DAT files
contained in the same directory as the executable program.
If the file cannot be opened, there are four possibilities:
1 - The flash device installed is not supported.
2 - The flash device is a licensed product.
3 - The device ID could not be read, resulting in a poorly
constructed filename. The first numeric value in the
filename is the device ID. Verify this value with the
component specification.
4 - The memory bus is not functional. Check all CPLD and FPGA
devices. Make sure that you are using the correct
platform data file.
jflashmm pxa27x32 eboot_m3m4.nb0 N 3F40000 PAR
JFLASH Version 5.01.007
COPYRIGHT (C) 2000 - 2003 Intel Corporation
PLATFORM SELECTION:
Processor= PXA27x
Development System= Mainstone
Data Version= 1.00.001
PXA27x revision ??
Upper and Lower flash memory ID does not match.
You may have a damaged flash memory.
Upper half reads: 90
Lower half reads: A
Failed to read the Flash ID. Retrying 4 more times...
Upper and Lower flash memory ID does not match.
You may have a damaged flash memory.
Upper half reads: 90
Lower half reads: A
Failed to read the Flash ID. Retrying 3 more times...
Upper and Lower flash memory ID does not match.
You may have a damaged flash memory.
Upper half reads: 90
Lower half reads: A
Failed to read the Flash ID. Retrying 2 more times...
Upper and Lower flash memory ID does not match.
You may have a damaged flash memory.
Upper half reads: 90
Lower half reads: A
Failed to read the Flash ID. Retrying 1 more times...
Upper and Lower flash memory ID does not match.
You may have a damaged flash memory.
Upper half reads: 90
Lower half reads: A
Failed to read the Flash ID. Retrying 0 more times...
Cannot open input file: Flash_A_2_32.dat
This program supports flash devices defined by DAT files
contained in the same directory as the executable program.
If the file cannot be opened, there are four possibilities:
1 - The flash device installed is not supported.
2 - The flash device is a licensed product.
3 - The device ID could not be read, resulting in a poorly
constructed filename. The first numeric value in the
filename is the device ID. Verify this value with the
component specification.
4 - The memory bus is not functional. Check all CPLD and FPGA
devices. Make sure that you are using the correct
platform data file.
debuglog.txt
Parsing Platform Data File: PXA27X32.dat
WORDARRAY: 0 PXA27x
WORDARRAY: 1 Mainstone
WORDARRAY: 2 1.00.001
WORDARRAY: 3 VL00000001
WORDARRAY: 4 504
WORDARRAY: 5 7
WORDARRAY: 6 X0
WORDARRAY: 7 X7E
WORDARRAY: 8 X7F
WORDARRAY: 9 61
WORDARRAY: 10 303
WORDARRAY: 11 240
WORDARRAY: 12 239
WORDARRAY: 13 238
WORDARRAY: 14 285
WORDARRAY: 15 60
WORDARRAY: 16 59
WORDARRAY: 17 72
WORDARRAY: 18 71
WORDARRAY: 19 68
WORDARRAY: 20 1111
WORDARRAY: 21 25
WORDARRAY: 22 24
WORDARRAY: 23 23
WORDARRAY: 24 22
WORDARRAY: 25 21
WORDARRAY: 26 20
WORDARRAY: 27 19
WORDARRAY: 28 18
WORDARRAY: 29 17
WORDARRAY: 30 16
WORDARRAY: 31 15
WORDARRAY: 32 14
WORDARRAY: 33 13
WORDARRAY: 34 12
WORDARRAY: 35 11
WORDARRAY: 36 10
WORDARRAY: 37 9
WORDARRAY: 38 8
WORDARRAY: 39 7
WORDARRAY: 40 6
WORDARRAY: 41 5
WORDARRAY: 42 4
WORDARRAY: 43 3
WORDARRAY: 44 2
WORDARRAY: 45 1
WORDARRAY: 46 0
WORDARRAY: 47 491
WORDARRAY: 48 490
WORDARRAY: 49 489
WORDARRAY: 50 488
WORDARRAY: 51 487
WORDARRAY: 52 486
WORDARRAY: 53 485
WORDARRAY: 54 484
WORDARRAY: 55 483
WORDARRAY: 56 482
WORDARRAY: 57 481
WORDARRAY: 58 480
WORDARRAY: 59 479
WORDARRAY: 60 478
WORDARRAY: 61 477
WORDARRAY: 62 476
WORDARRAY: 63 475
WORDARRAY: 64 474
WORDARRAY: 65 473
WORDARRAY: 66 472
WORDARRAY: 67 471
WORDARRAY: 68 470
WORDARRAY: 69 469
WORDARRAY: 70 468
WORDARRAY: 71 467
WORDARRAY: 72 466
WORDARRAY: 73 465
WORDARRAY: 74 464
WORDARRAY: 75 463
WORDARRAY: 76 462
WORDARRAY: 77 461
WORDARRAY: 78 460
WORDARRAY: 79 57
WORDARRAY: 80 56
WORDARRAY: 81 55
WORDARRAY: 82 54
WORDARRAY: 83 53
WORDARRAY: 84 52
WORDARRAY: 85 51
WORDARRAY: 86 50
WORDARRAY: 87 49
WORDARRAY: 88 48
WORDARRAY: 89 47
WORDARRAY: 90 46
WORDARRAY: 91 45
WORDARRAY: 92 44
WORDARRAY: 93 43
WORDARRAY: 94 42
WORDARRAY: 95 41
WORDARRAY: 96 40
WORDARRAY: 97 39
WORDARRAY: 98 38
WORDARRAY: 99 37
WORDARRAY: 100 36
WORDARRAY: 101 35
WORDARRAY: 102 34
WORDARRAY: 103 33
WORDARRAY: 104 32
WORDARRAY: 105 31
WORDARRAY: 106 30
WORDARRAY: 107 29
WORDARRAY: 108 28
WORDARRAY: 109 27
WORDARRAY: 110 26
WORDARRAY: 111 2222
WORDARRAY: 112 32
WORDARRAY: 113 X00000000
WORDARRAY: 114 X04000000
WORDARRAY: 115 0
WORDARRAY: 116 X04000000
WORDARRAY: 117 X08000000
WORDARRAY: 118 1
WORDARRAY: 119 X08000000
WORDARRAY: 120 X0C000000
WORDARRAY: 121 2
WORDARRAY: 122 X0C000000
WORDARRAY: 123 X10000000
WORDARRAY: 124 3
WORDARRAY: 125 X10000000
WORDARRAY: 126 X14000000
WORDARRAY: 127 4
WORDARRAY: 128 X14000000
WORDARRAY: 129 X18000000
WORDARRAY: 130 5
WORDARRAY: 131 1001001001100101
WORDARRAY: 132 00000001001
WORDARRAY: 133 1
WORDARRAY: 134 A0
WORDARRAY: 135 A1
WORDARRAY: 136 B0
WORDARRAY: 137 B1
WORDARRAY: 138 C0
WORDARRAY: 139 C2
WORDARRAY: 140 ??
WORDARRAY: 141 ??
WORDARRAY: 142 ??
WORDARRAY: 143 ??
WORDARRAY: 144 ??
WORDARRAY: 145 ??
WORDARRAY: 146 ??
WORDARRAY: 147 ??
WORDARRAY: 148 ??
WORDARRAY: 149 ??
WORDARRAY: 150 61
WORDARRAY: 151 303
WORDARRAY: 152 182
WORDARRAY: 153 240
WORDARRAY: 154 119
WORDARRAY: 155 239
WORDARRAY: 156 118
WORDARRAY: 157 238
WORDARRAY: 158 117
WORDARRAY: 159 285
WORDARRAY: 160 164
WORDARRAY: 161 9999
WORDARRAY: 162 59
WORDARRAY: 163 60
WORDARRAY: 164 69
WORDARRAY: 165 70
WORDARRAY: 166 71
WORDARRAY: 167 72
WORDARRAY: 168 73
WORDARRAY: 169 74
WORDARRAY: 170 75
WORDARRAY: 171 319
WORDARRAY: 172 318
WORDARRAY: 173 321
WORDARRAY: 174 325
WORDARRAY: 175 492
WORDARRAY: 176 494
WORDARRAY: 177 316
WORDARRAY: 178 195
WORDARRAY: 179 269
WORDARRAY: 180 148
WORDARRAY: 181 228
WORDARRAY: 182 107
WORDARRAY: 183 313
WORDARRAY: 184 192
WORDARRAY: 185 312
WORDARRAY: 186 191
WORDARRAY: 187 311
WORDARRAY: 188 190
WORDARRAY: 189 310
WORDARRAY: 190 189
WORDARRAY: 191 9999
WORDARRAY: 192 9999
WORDARRAY: 193 9999
WORDARRAY: 194 9999
WORDARRAY: 195 9999
WORDARRAY: 196 9999
WORDARRAY: 197 Enabled
WORDARRAY: 198 7
WORDARRAY: 199 Controller
WORDARRAY: 200 Last
WORDARRAY: 201 Disabled
WORDARRAY: 202 0
WORDARRAY: 203 Other
WORDARRAY: 204 More
WORDARRAY: 205 Disabled
WORDARRAY: 206 0
WORDARRAY: 207 Other
WORDARRAY: 208 More
WORDARRAY: 209 Disabled
WORDARRAY: 210 0
WORDARRAY: 211 Other
WORDARRAY: 212 More
WORDARRAY: 213 Disabled
WORDARRAY: 214 0
WORDARRAY: 215 Other
WORDARRAY: 216 More
WORDARRAY: 217 9999
WORDARRAY: 218 1
WORDARRAY: 219 9999
WORDARRAY: 220 1
WORDARRAY: 221 9999
WORDARRAY: 222 1
WORDARRAY: 223 9999
WORDARRAY: 224 1
WORDARRAY: 225 3333
WORDARRAY: 226 2
WORDARRAY: 227 58
WORDARRAY: 228 BUFFER
Devices_before = 0
Devices_after = 0
Device controller at position 0
JFLASH Version 5.01.007
COPYRIGHT (C) 2000 - 2003 Intel Corporation
PLATFORM SELECTION:
Processor= PXA27x
Development System= Mainstone
Data Version= 1.00.001
Parallel Com port found at I/O address: 378
begin test logic reset
finish test logic reset
begin test logic reset
finish test logic reset
begin pre-IR scan code
begin controller scan code = 7e
Controller IR value: FFFFFFFF
begin post-IR scan code
begin pre-DR scan code
error, failed to read device ID
check cables and power
ACT: 1111 1111111111111111 11111111111 1
EXP: **** 1001001001100101 00000001001 1
failed to read device ID for this Platform
F A I L U R E A N A L Y S I S
Processor ID: Not Found
Flash ID: Not Found
Flash Lock Status: Not Unlocked
Verification: No Data Verified
Flash Erase Status: Not Erased
You have a serious failure.
The ID of the processor was not detected.
Check all cable attachments.
Check for power on Pin 1 of your JTAG connector.
Check seating of processor and cards in sockets or connectors
If the bits for the ID string appear to be shifted left or right,
then you probably have a JTAG routing switch set in the wrong state.
If the ACTual bits are all 0s or 1s, you may have a
cable or a power problem on this board.
who can help me?please help me,thank you cery much.
who can help me?please help me,thank you cery much.
i have same problem like springrain8888
cand some 1 help me pls ?
In case you need to know how to poll GPIO values from photon, here is a small how-to:
First of all, read THIS:
http://htc-linux.org/wiki/index.php?title=HaRET_Documentation#Polling_GPIOs
To disable automatic launch of Android when you execute HarET, you must rename your file "startup.txt" to "default.txt"
The issue is, when you poll for GPIOs with Haret, you got a numeric value that does not match with GPIOs in Linux (board-photon.h)
To translate "HarET GPIO" to "Linux GPIO", here is a trick:
Haret gives you this line:
009.179 GPIOS 92f00808(117)=300100
Click to expand...
Click to collapse
Take the number between parenthesis: 117
Divide it by 32:
117/32 = 3, rest = 21
3 is the GPIO bank:
bank0 = 0 to 15
bank1 = 16 to 42
bank2 = 43 to 67
bank3 = 68 to 94
bank4 = 95 to 106
bank5 = 107 to 121
in our example, bank3 starts at value 68, so the Linux GPIO is:
68 + 21(rest of division) = 89
note: if the bank number is higher than 5, it means it is the following bank, or the one after. in this case, remove 6 or 12 to the bank number so you have a value between 0 and 5, and do the normal computation.
I must to say THANK YOU!
hmm I not understand (rest) I got 3,65625 (bank 3, rest 65626)
r0bin said:
117/32 = 3, rest = 21
Click to expand...
Click to collapse
Also next situation:
057.215 GPIOS 92f0083c(313)=61c8102
9,78125 (bank 9, rest 78125)
munjeni said:
hmm I not understand (rest) I got 3,65625 (bank 3, rest 65626)
Also next situation:
057.215 GPIOS 92f0083c(313)=61c8102
9,78125 (bank 9, rest 78125)
Click to expand...
Click to collapse
lol
on my sample, another way to say it:
117/32 = (3 * 32) + 21
or:
117/32 = 3.65625, you take the 3, rest 0.65625 * 32 = 21
in your case:
303/32 = 9.78125, you take the 9, rest 0.78125 * 32 = 25
9 is too big, remove 6 => it's bank3
bank3 = 68+25 = 93
in board-photon.h, it is defined like:
LIBERTY_GPIO_LS_EN 93
in the code (board-photon.c) it seems it's the GPIO for power
thanks, understand now \o/
Hi,
I got slightly different format for GPIOS.
Please refer to here
http://pastebin.com/xr4p3cd8
How to I convert them?
Thanks in advance
Author: Apriorit (Device Team)
Permanent link: www(dot)apriorit(dot)com/dev-blog/58-samsung-obex-specification
This article describes the protocol of data exchange that is the modification of the well-known OBEX protocol used in the GSM Samsung phones from the SHP family. The described modification of this protocol lets you write data to the phone and also get and save them.
Introduction
This article describes the protocol of data exchange that is the modification of the well-known OBEX protocol used in the GSM Samsung phones from the SHP family. The described modification of this protocol lets you write data to the phone and also get and save them.
Samsung Corporation made the new line of phones from SHP family and implemented the support of OBEX protocol in them that had not been used in the phones of this company before. Tries to use the common OBEX protocol did not succeed. This problem was solved by means of sniffing the Samsung PC Studio 3.0 utility. The obtained results are given in the main part of the article.
This article will be useful for those who develop utilities for writing/reading information from the phones. The described protocol modification will solve the problem of communicating with the device.
First we consider three main types of the protocol commands. Then we pay our attention to the sequence of the commands sent to connect with the device, read data and finish the session. Then I will give some examples for the main commands. At the end of the article some summary will be given.
Main protocol commands format
All protocol commands can be divided into 2 types:
1. AKN-packages. They are packages to confirm the data receiving and request the next part of the extended package.
2. Data packages. They are initialization, acquiring, closing etc. There can be Request and Answer packages.
AKN package is one block with 3 bytes length: 0x83 0x00 0x03.
Request package has the following structure:
Size (bytes) Meaning Description
1 Package ID 0x80 Select the answering device, obtain the properties and establish connection
0x81 Finish the connection session
0x82 Write an object
0x83 Read an object
0x84 Reserved
0х85 Select the default directory on the receiving side
0хFF Cancel current operation
2 Package size The size of the whole package (from the zero byte and to the end)
… Data blocks Some number of data blocks that depends on the context of the command containing them.
Format:
Size (bytes) Meaning Description
1 Type Set the type of the data in the block
2 Size The size of the whole data block (from the zero byte and to the end)
N-3 Data Some data depending on the type specified by the first byte
The description of the Answer packages is given in the table below.
Size (bytes) Value Description
1 Package ID 0x90 Successful but not completed (received package is a part of the extended package)
0xA0 Successful and completed
0xC3 Access denied
0xC4 Not found
0xC9 Conflict
2 Package size The size of the whole package (from the zero byte and to the end)
… Data blocks Some number of data blocks that depends on the context of the command containing them.
Format:
Size (bytes) Meaning Description
1 Type Set the type of the data in the block
2 Size The size of the whole data block (from the zero byte and to the end)
N-3 Data Some data depending on the type specified by the first byte
The sequence of commands
As any standard communication protocol modified OBEX consists of the sequence of requests and answers. In general the communication session can be divided into 3 phases:
1. Initialization
2. Acquiring data
3. Closing the session
Table with the session description is given below.
Initialization phase
Request 41 54 2B 53 59 4E 43 4D 4C 3D 4D 4F 42 45 58 53 54 41 52 54 0D 0A AT+SYNCML=MOBEXS
Answer 41 54 2B 53 59 4E 43 4D 4C 3D 4D 4F 42 45 58 5354 41 52 54 0D 4F 4B 0D 0A AT+SYNCML=MOBEXSTART.OK..
Request 80 00 0F 11 00 FF FF 46 00 08 4D 4F 42 45 58 А.... F..MOBEX
Answer A0 00 14 12 00 05 78 CB 00 00 00 01 4A 00 08 4D 4F 42 45 58 а.....x╦....J..MOBEX
Acquiring phase
Request A series of requests and answers for acquiring data
Answer Note: if the first byte of the package is equal to 0x90 then it is so-called extended package and then the sending of AKN-package (0x83 0x00 0x03) is required,
after it the device will give us the other parts of the package.
Closing phase
Request 81 00 08 CB 00 00 00 01 Б..╦....
Answer A0 00 03 а..
Commands examples
Let’s consider some examples of the data acquisition. They will be the examples of working with the file system.
Obtaining the list of subfolders of the folder(m-obex/fs/folder_listing)
Request
83 00 29 CB 00 00 00 01 42 00 1C 6D 2D 6F 62 65 ?.)E....B..m-obex/fs/folder_listing..../.
78 2F 66 73 2F 66 6F 6C 64 65 72 5F 6C 69 73 74
69 6E 67 00 01 00 05 2F 00
Size (bytes) Value Description
1 0x83 Reading
2 0x00 0x29 Package size
1 0xCB Data block type
4 0x00 0x00 0x00 0x01 Reserved
1 0x42 Data block type (text)
2 0x00 0x1C Block size
N-3 m-obex/fs/folder_listing Block data (command name)
1 0x01 Block type (list)
2 0x00 0x05 Block size
N-3 0x2F 0x00 Block data
Note: “/” for the root, “/” for the other folders
Answer
A0 00 FC 42 00 1B 6D 2D 6F 62 65 78 2F 66 73 2F .uB..m-obex/fs/
66 6F 6C 64 65 72 5F 6C 69 73 74 69 6E 67 C3 00 folder_listingA.
00 00 D6 49 00 D9 41 75 64 69 6F 2C 30 2C 31 31 ..OI.UAudio,0,11
31 30 30 31 30 31 30 2C 32 30 30 34 3A 30 33 3A 1001010,2004:03:
30 31 20 30 31 3A 30 33 3A 30 30 5C 72 5C 6E 47 01 01:03:00\r\nG
72 61 70 68 69 63 73 2C 30 2C 31 31 31 30 30 31 raphics,0,111001
30 31 30 2C 32 30 30 34 3A 30 33 3A 30 31 20 30 010,2004:03:01 0
31 3A 30 33 3A 30 30 5C 72 5C 6E 56 69 64 65 6F 1:03:00\r\nVideo
2C 30 2C 31 31 31 30 30 31 30 31 30 2C 32 30 30 ,0,111001010,200
34 3A 30 33 3A 30 31 20 30 31 3A 30 33 3A 30 30 4:03:01 01:03:00
5C 72 5C 6E 4D 75 73 69 63 2C 30 2C 31 31 31 30 \r\nMusic,0,1110
30 31 30 31 30 2C 32 30 30 34 3A 30 33 3A 30 31 01010,2004:03:01
20 30 31 3A 30 33 3A 30 30 5C 72 5C 6E 4F 74 68 01:03:00\r\nOth
65 72 20 46 69 6C 65 73 2C 30 2C 31 er Files,0,1
31 31 30 30 31 30 31 30 2C 32 30 30 34 3A 30 33 11001010,2004:03
3A 30 31 20 30 31 3A 30 33 3A 30 30 5C 72 5C 6E :01 01:03:00\r\n
Size Value Description
1 0xA0 Successful operation
2 0x00 0x0F Package size
1 0x42 Block type
2 0x00 0x1C Block size
N-3 m-obex/fs/folder_listing(0x00) Block data
1 0xCB Block type
4 0x00 0x00 0x00 0xD6 Reserved
1 0x49 Block type
2 0x00 0xD9 Block size
N-3 Block data
Note: the list items are separated with the pair of symbols “\r\n”
Each element of the list is the folder description: [Name][Size(always 0)][Attributes][Modified][Created].
So in the example of these two commands you can see the general structure of the package in the modified OBEX protocol.
In conclusion I want to mention that the records in the phone book as well as the calendar are represented in VCard as it was in the previous versions of the OBEX protocols.