Develop Bugs

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] 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.

.efs_private directory

When I was messing with BitPim earlier, I tried out the Protocol Analyser and got this:
18:52:09.717 Other CDMA Phone: Listing files in dir: '.efs_private'
18:52:09.717 Other CDMA Phone: sendbrewcommand Data - 20 bytes
<#! phones.p_brew.listfilerequest !#>
00000000 59 0b 00 00 00 00 0d 2e 65 66 73 5f 70 72 69 76 Y.......efs_priv
00000010 61 74 65 00 ate.
18:52:09.765 Other CDMA Phone: brew response Data - 17 bytes
<#! phones.p_brew.listfileresponse !#>
00000000 13 0b 00 00 00 0d 2e 65 66 73 5f 70 72 69 76 61 .......efs_priva
00000010 74 t
18:52:09.765 Other CDMA Phone: Failed to list files in dir .efs_private
18:52:09.780 Other CDMA Phone: Listing subdirs in dir: '.efs_private'
18:52:09.780 Other CDMA Phone: X recurse=0
18:52:09.780 Other CDMA Phone: sendbrewcommand Data - 20 bytes
<#! phones.p_brew.listdirectoryrequest !#>
00000000 59 0a 00 00 00 00 0d 2e 65 66 73 5f 70 72 69 76 Y.......efs_priv
00000010 61 74 65 00 ate.
18:52:09.780 Other CDMA Phone: brew response Data - 17 bytes
<#! phones.p_brew.listdirectoryresponse !#>
00000000 13 0a 00 00 00 0d 2e 65 66 73 5f 70 72 69 76 61 .......efs_priva
00000010 74 t
18:52:09.780 Other CDMA Phone: Failed to list dir .efs_private
18:52:11.015 Other CDMA Phone: Listing files in dir: 'CGPS_ME'
18:52:11.015 Other CDMA Phone: sendbrewcommand Data - 15 bytes
<#! phones.p_brew.listfilerequest !#>
00000000 59 0b 00 00 00 00 08 43 47 50 53 5f 4d 45 00 Y......CGPS_ME.
18:52:11.030 Other CDMA Phone: brew response Data - 47 bytes
<#! phones.p_brew.listfileresponse !#>
00000000 59 0b 00 00 00 00 00 0f 00 01 00 93 1a e0 00 00 Y...............
00000010 6c 00 00 bb 1a e0 00 08 16 43 47 50 53 5f 4d 45 l........CGPS_ME
00000020 2f 43 47 50 53 43 65 6c 6c 44 42 46 69 6c 65 /CGPSCellDBFile
18:52:11.030 Other CDMA Phone: sendbrewcommand Data - 15 bytes
<#! phones.p_brew.listfilerequest !#>
00000000 59 0b 01 00 00 00 08 43 47 50 53 5f 4d 45 00 Y......CGPS_ME.
18:52:11.046 Other CDMA Phone: brew response Data - 55 bytes
<#! phones.p_brew.listfileresponse !#>
00000000 59 0b 00 01 00 00 00 0f 00 01 00 93 1a e0 00 2c Y..............,
00000010 00 00 00 bb 1a e0 00 08 1e 43 47 50 53 5f 4d 45 .........CGPS_ME
00000020 2f 43 47 50 53 43 65 6c 6c 44 42 4f 74 61 50 6f /CGPSCellDBOtaPo
00000030 73 52 65 63 6f 72 64 sRecord
18:52:11.046 Other CDMA Phone: sendbrewcommand Data - 15 bytes
<#! phones.p_brew.listfilerequest !#>
00000000 59 0b 02 00 00 00 08 43 47 50 53 5f 4d 45 00 Y......CGPS_ME.
18:52:11.062 Other CDMA Phone: brew response Data - 47 bytes
<#! phones.p_brew.listfileresponse !#>
00000000 59 0b 00 02 00 00 00 0f 00 01 00 93 1a e0 00 3c Y..............<
00000010 00 00 00 bb 1a e0 00 08 16 43 47 50 53 5f 4d 45 .........CGPS_ME
00000020 2f 67 70 73 6f 66 66 73 65 74 73 2e 62 69 6e /gpsoffsets.bin
18:52:11.062 Other CDMA Phone: sendbrewcommand Data - 15 bytes
<#! phones.p_brew.listfilerequest !#>
00000000 59 0b 03 00 00 00 08 43 47 50 53 5f 4d 45 00 Y......CGPS_ME.
18:52:11.078 Other CDMA Phone: brew response Data - 3 bytes
<#! phones.p_brew.listfileresponse !#>
00000000 59 0b 1c Y..
18:52:11.092 Other CDMA Phone: Listing subdirs in dir: 'CGPS_ME'
18:52:11.092 Other CDMA Phone: X recurse=0
18:52:11.092 Other CDMA Phone: sendbrewcommand Data - 15 bytes
<#! phones.p_brew.listdirectoryrequest !#>
00000000 59 0a 00 00 00 00 08 43 47 50 53 5f 4d 45 00 Y......CGPS_ME.
18:52:11.092 Other CDMA Phone: brew response Data - 3 bytes
<#! phones.p_brew.listdirectoryresponse !#>
00000000 59 0a 1c Y..
18:52:12.953 Other CDMA Phone: Getting file contents 'CGPS_ME/gpsoffsets.bin'
18:52:12.953 Other CDMA Phone: sendbrewcommand Data - 27 bytes
<#! phones.p_brew.readfilerequest !#>
00000000 59 04 00 17 43 47 50 53 5f 4d 45 2f 67 70 73 6f Y...CGPS_ME/gpso
00000010 66 66 73 65 74 73 2e 62 69 6e 00 ffsets.bin.
18:52:12.983 Other CDMA Phone: brew response Data - 71 bytes
<#! phones.p_brew.readfileresponse !#>
00000000 59 04 00 00 00 3c 00 00 00 3c 00 ff ff 38 00 00 Y....<...<...8..
00000010 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00000020 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00000030 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00000040 00 00 00 00 00 00 00 .......
Near the beginning of these, it says things about being unable to open up the .efs_private directory, along with its subfolders. If someone were able to open these, we may find something interesting. Hope this helps!

i got interest in:
p_brew.readfileresponse
if brew lets you load things. i can do test like i did with mtp, through raw USB.

I wondered the same thing about the listing of "brew" there. Can't wait to see if John finds anything.
Using BitPim, which (I believe, from my google searches) references QPST content, the .efs_private folder seems to be specific to QPST. If we're seeing an error trying to list that area, it's probably because bitpim is designed to look for some standard folders, which the Kin does not have.

if we had a worthwhile alternative to BitPim, we may be able to see what's in there. And when you said QPST, does that have anything to do with Qualcomm? I was also looking at the configuration settings for the phone's modem, and i think it mentioned that. So this file could contain hardware, storage, and other files that we could use to break through the restrictions on the phone.

Yes, many phones use Qualcomm hardware or functionality, including Verizon ones. Bitpim simply takes advantage of some common functionality between these phones.
Which file did you mean?

<HELP! bricked galaxy nexus!>

hello guys,
1 month ago my galaxy nexus just bricked, and i don't know why?
i was unlocking my password then just stunned and won't be able to power on..i though that was the battery problem so i bought a new battery, but some how it still won't power on...so i when to google and search how to unbrick galaxy nexus, but no luck...try many method but i still can't power on...but the only thing i found out when i plug in my usb without the battery it will show out OMAP 4440 is this a soft bricked or completely dead? can i still fix it...the only thing i haven't try is usb jig...will it works? or i can fix it using usb jig? some one please teach me....PLEASE
Thanks

Have you tried using any of the unbricking methods that are currently posted in this forum?
Sent from my Galaxy Nexus using Tapatalk 2

Viola.
http://forum.xda-developers.com/showthread.php?t=1760787
Edit:
Prior to the "Add Legacy Hardware" step you must click your Username in Device Manger so that it's highlighted or the option won't show.

yes, but has some problem...
i tried this but i have some problem with it
00494-008-rx: failed: unknown command dir
operation failed <remote ::unknown command dir>
Jubakuba said:
Viola.
http://forum.xda-developers.com/showthread.php?t=1760787
Edit:
Prior to the "Add Legacy Hardware" step you must click your Username in Device Manger so that it's highlighted or the option won't show.
Click to expand...
Click to collapse

thanks for reply...can you give me some link?? Thanks..
miketoasty said:
Have you tried using any of the unbricking methods that are currently posted in this forum?
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse

areyoumad said:
i tried this but i have some problem with it
00494-008-rx: failed: unknown command dir
operation failed <remote ::unknown command dir>
Click to expand...
Click to collapse
Did you unzip the entire folder to a new folder first?

?OMAPFlash v4.15 (Aug 12 2011)
?-v
?Entering parameter file:Targets\Projects\tuna\omap4460_tuna_hs_pro.txt at line:
1
? -omap 4
? -t 36000
? -p OMAP4460_TUNA_8G_HS_PRO
? -2
? -t 36000
? -p OMAP4460_TUNA_8G_HS_PRO
? -2
? -rxtx_trace
? chip_download EMMC Targets\Projects\tuna\MLO_4460_HS_PRO
? chip_download EMMC Targets\Projects\tuna\sbl.img
? command cold_sw_reset
?Leaving parameter file:Targets\Projects\tuna\omap4460_tuna_hs_pro.txt
[email protected]\Projects\tuna\omap4460_tuna_hs_pro.txt
?Looking for device (omap usb)
?Please turn on device
?Waiting for device (omap usb)
?Found device (omap usb)
?Requesting ASIC id
00130-000-TX 4 raw bytes: 03 00 03 F0 '????'
?AsicId items 05
?AsicId id 01 05 01 44 40 07 01
?AsicId secure_mode 13 02 01 00
?AsicId public_id 12 15 01 FC 8B E7 3E 3D 56 B8 06 04 D7 0E 77 F4 A8 F3
C1 4E 6B B7 23
?AsicId root_key_hash 14 21 01 67 98 9B 35 54 CC 86 B4 67 32 47 05 36 74 E2
25 F0 9D A3 5C F4 59 B9 C9 3A 13 E0 B9 58 1E 5A BC
?AsicId checksum 15 09 01 22 9E 85 BA DC 58 74 BC
00130-001-TX 4 raw bytes: 02 00 03 F0 '????'
?Searching 2nd for: OMAP4460_TUNA_8G_HS_PRO 444007 01 HS
?Loading second file Targets/2nd-Downloaders/dnld_startup_omap4_hs_8g_es2.s2.sig
ned.2nd.hs_pro
?Entering parameter filemapflash2nd.txt at line: 46
? -pheriphalboot_reopen
?Reading board configuration file Targets\Configurations\configuration_omap4460_
tuna_8g.txt
?Reading definition file .\targets\definitions\definitions_omap4.txt
? -board_config Targets\Configurations\configuration_omap4460_tuna_8g.txt
?Leaving parameter filemapflash2nd.txt
?Sending size of second file (0x000071B0 bytes)
00130-002-TX 4 raw bytes: B0 71 00 00 '?q??'
?Transferring second file to target (0x71B0 bytes)
00130-003-TX 29104 raw bytes: B0 1C 00 00 00 4D 00 00 00 00 00 00 00 00 00 00
'?????M??????????' ...
?Closing boot connection
?Found device (omap usb)
?Waiting for 2nd
00463-004-TX ACK
00554-005-RXKAY: 2nd started
?Found 2nd
?Looking for a driver for 'EMMC'
?chip_driver EMMC Targets\Flash-Drivers\emmc_drv.bin sid 0 width 4 delay 9 rpapi
_base 0x00030400
?Downloading driver
00385-006-TX:driver EMMC sid 0 width 4 delay 9 rpapi_base 0x00030400
00463-007-TX ACK
00494-008-RX:FAIL: Unknown command dri
?Operation FAILED (Remote: : Unknown command dri)
?Elapsed time: 0:17.143
Press any key to continue . . .
Jubakuba said:
Did you unzip the entire folder to a new folder first?
Click to expand...
Click to collapse

Driver wasn't installed correctly.
Look around in the thread I posted, I'm off to school, sorry!
Maybe someone had the same issue.

can you give me the link please...i can't find it...Thank you so much..
Jubakuba said:
Driver wasn't installed correctly.
Look around in the thread I posted, I'm off to school, sorry!
Maybe someone had the same issue.
Click to expand...
Click to collapse

Any News? I got the same Problem.....

[WEC7][DL]Download System Image Flash.Store.bin[PB]

Structure flash.store.bin:
Flash.Store.Bin - the wm7 image in a new format (D000FF, containing several sections)
Code:
00000000: "D000FF\n"
00000007: 00000000
0000000b: 00000800 -- sectorsize
0000000f: 0000f79d -- total nr of sectors
00000013: 00000009 -- nr of sections
00000017: 00000000
0000001b: 00000004
0000001f: 00000000
type offset idlen id
00000023: 00000002 00000040 00000008 54 53 55 4e 41 47 49 00 ; MODEM
00000037: 00000002 00000180 00000008 4c 4f 47 4f 00 ff ff ff ; LOGO
0000004b: 00000002 00000240 00000008 42 4c 44 52 00 ff ff ff ; BLDR
0000005f: 00000002 00000080 00000008 42 53 50 00 ff ff ff ff ; BSP
00000073: 00000003 00000400 00000002 1b 00
00000081: 00000003 00001600 00000002 20 00
0000008f: 00000003 00000740 00000002 23 00
0000009d: 00000003 0000fc7f 00000002 25 00
000000ab: 00000003 0002453f 00000002 04 00
Code:
2048 Oct 22 23:24 section-0.bin "MODEM" "META!7.27.1!DFP-SDCAOWZM-221001-1! "
81920 Oct 22 23:24 section-1.bin "LOGO" bitmaps
636928 Oct 22 23:24 section-2.bin "BLDR" bootloader
2048 Oct 22 23:24 section-3.bin "BSP"
86016 Oct 22 23:24 section-4.bin type 1b 'exfat'
4624384 Oct 22 23:24 section-5.bin type 20 compressed xip
3500032 Oct 22 23:24 section-6.bin type 23 xip
119576576 Oct 22 23:24 section-7.bin type 25 imgfs
1310720 Oct 22 23:24 section-8.bin type 04 'exfat'
Big thank's for Itsme
Use Format Image flash.store.bin in Platform Builder
Only this format image We use in PB. All OS image (FLPart etc, we not download in PB)
How flash this file in PB?
...copy this file format in general directory PB (replace/rename to nk.bin)
How to get Download Image in Device?
...in bootloader menu, select "USBFn Serial " or in my device, this possible - Press and Hold - Volume Key down + Power Key.
Then see:
--BLDR/MODEM/BOOTME Info version
--Bootloader comm. info/process.
--And at the bottom of the screen - inscription "Downloading Image..."
How to run Download process?
Connect Device via USB, Click "Attach Device", and wait 3-4 min...
More Method/Info
Comming Soon...
Nokser