herewhere knocking motorolka when trying to get an update
request
1: A DNS query packet: DNS Standard query A motosb1fe.bitfone.com
2: The DNS response: DNS Standard query response CNAME mvfe1.bitfone.com A 216.90.91.100
3: After that there is some HTTP traffic going on which seems to encapsulate SYNCML data
POST / mvpdm / dm HTTP / 1.1
Accept: application / vnd.syncml.dm + wbxml
Accept-Language: en
Accept-Charset: utf-8
User-Agent: Mototorla Android Sync DM Client
Cache-Control: private
Content-Type: application / vnd.syncml.dm + wbxml
x-syncml-hmac: algorithm = MD5, username = "xxxxxxxxxxxxxxx", mac = xxxxxxxxxxxxxxxxxxxxxxxx
Connection: Close
Content-Length: 508
Host: motosb1fe.bitfone.com:80
... j .- // SYNCML // DTD SyncML 1.2 // ENmlq.1.2..r.DM / 1.2..e.4C9C .. [.1..nW.http: //motosb1fe.bitfone.com: 80 / mvpdm / dm..V.Motorola ... gW.IMEI: xxxxxxxxxxxxxxx..V.xxxxxxxxxxxxxxx ... Z..L.20000 ...... kFK.1..O.1201 ... `K.2..TgW ../ DevInfo / Mod ... O.Milestone ... TgW ../ DevInfo / Man ... O.motorola ... TgW ../ DevInfo / Lang ... O.de_DE ... TgW ../ DevInfo / DmV ... O.1.2 ... TgW ../ DevInfo / devId ... O .IMEI: xxxxxxxxxxxxxxx ... .FK.3..O.xxxx..TgW ../ DevDetail / Ext / SystemUpdate ... Z..G.xml..S.org.openmobilealliance.dm.firmwareupdate.userrequest ... ..
O ...... ..
and the answer
HTTP / 1.1 200 OK
Date: Sat, 02 Jan 2010 13:12:48 GMT
Content-Length: 591
Content-Type: application / vnd.syncml.dm + wbxml
Connection: Close
... j .- // SYNCML // DTD SyncML 1.2 // ENmlq.1.2..r.DM / 1.2..e.4C9C .. [.1..nW.IMEI: xxxxxxxxxxxxxxx ... gW.http: // motosb1fe. bitfone.com:80/mvpdm/dm..V.Motorola...a.http://motosb1fe.bitfone.com:80/mvpdm/dm?sid=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx..NZ..G.b64..S.syncml: auth-basic ... ..xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx = ... Z..L.xxxxx ...... kiK.1 .. \ .1..L.0..J.SyncHdr..o.http: //motosb1fe.bitfone.com: 80 /mvpdm/dm..h.IMEI:xxxxxxxxxxxxxxx..IZ..G.b64..S.syncml:auth-MAC..xxxxxxxxxxxxxxxxxxxxxxx......O.401...iK.2..\.1..L.1 ..J.Alert..O.401 ... iK.3 .. \. 1..L.2..J.Replace..O.401 ... iK.4 .. \. 1..L.3 .. J.Alert..O.401 ......
Bitfone - such venture desk that was in 2006, the year the company bought HP
just engaged the support of FOTA updates for different companies.
what we see?
1. for the update-th phone climbs to Google and not even to Motorola. those. in the process added another participant. Apparently after validation update in Google, or it will be sent back for revision, or it will give Motorola bitfonu for accommodation.
2. Authorization to the server goes through the IMEI transfer
it is possible that at first, the update will get not to all, but, for example, owners of non-branded devices.
Post has been editedm1chael - 17.01.10, 17:30