[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Opening a .SQ file



Yes it is a file related to the Tmobile Sidekick. Its a device key
which isgenerated by danger for each device (the serial # is embedded
in the file '010298000899201'.

My friend let me have his device key but Danger no longer issues out
device keys so i wanted to see if i could alter the original key to
match my own serial#.

I greatly appreciate the help.  From the sample of the file that you
pasted below. I see a portion of the serial #. I am trying to figure
out if i alter that will it work or will i need to decrypt the rest of
this file.


Andy McFadden wrote:
> Michael J. Mahon <mjmahon@aol.com> wrote:
> >> : http://www.fastbreaknyunltd.com/downloads/fbnyunltd.sq
> >>
> >> It can't find the page/file in the link.  :o)
> >
> > He mis-capitalized it--try trimming the link and exploring.
>
> http://www.fastbreaknyunltd.com/downloads/fbnyUnltd.sq
>
> It starts like this:
>
> 0000000: 474f 5244 1802 0000 0000 0000 1800 0000  GORD............
> 0000010: 4144 3332 5c8b 5ccf 4649 4c45 2b00 0000  AD32\.\.FILE+...
> 0000020: 0600 0000 4950 4331 021e 0000 6c6f 636b  ....IPC1....lock
> 0000030: 5f74 6f5f 696d 6569 5f30 0030 3130 3239  _to_imei_0.01029
> 0000040: 3830 3030 3839 3932 3031 0000 5349 474e  8000899201..SIGN
> 0000050: dc01 0000 3082 01d8 0201 0131 0b30 0906  ....0......1.0..
>
> Unfortunately, this isn't an Apple II SQ file.  Comments from
NuLib2's
> Squeeze.c:
>
>  * The SQ file format begins with this:
>  *  +00  magic number (0xff76)
>  *  +02  checksum on uncompressed data
>  *  +04  filename, ending with \0
>  * The NuFX format skips the above, starting immediately after it:
>  *  +00  node count
>  *  +02  node value array [node count], two bytes each
>  *  +xx  data immediately follows array
>
> The file itself might be a data file from a T-Mobile Sidekick
(developed by
> Danger Research in Palo Alto, CA), and does not appear to be
compressed.
> It looks like they use a "chunk" format, where they have a 4-byte
text
> chunk name followed by a 4-byte little-endian length (except in cases
> like "AD32" where the length is implied -- perhaps an Adler32
checksum?).
> This is a pretty common way of doing things.
>
> If it is what I think it is, this is a fairly recent and probably
> proprietary format, and Apple II utilities aren't going to help.
>
> --
> Send mail to fadden@fadden.com (Andy McFadden) -
http://www.fadden.com/
> CD-Recordable FAQ - http://www.cdrfaq.org/
> CiderPress Apple II archive utility for Windows -
http://www.faddensoft.com/
> Fight Internet Spam - http://spam.abuse.net/spam/ &
http://spamcop.net/