Re: Preliminary enV2/VX9100 Support

Its all good, just had a long day and thought my patch had made it  
through and been broken. I do think it would be useful to detect DMv6  
to avoid the inevitable if fw_vers==blah code as DMv6 is added to  
older phones.

Had you received my description of DMv6 or did you independently  
discover how DMv6 works? I don't think LG hid the key very well though  
they did a reasonable log of making the assembly a pain to follow.

I find it potentially troubling that your implementation did not work  
with Aaron's phone but did work on yours. Was the phone activated? It  
could mean the ESN could be more important than I though in  
determining the location of the key bytes. Of course we could always  
set every byte of each new key to the corresponding XOR key byte. i.e  
if the xor key is 0xaabbccdd then the 16-byte key would become  
ddddddddccccccccbbbbbbbbaaaaaaaa. Which should always work (now that I  
think about it).

 > I thought it'd be cleaner to separate them out since the length of  
the 0xFE command is different from v5 (7 bytes) to v6 (either 8 or 24  
bytes), though
 > that may or may not make any practical differences.

It doesn't appear to make any real difference if the 0xfe 00 command  
is one byte shorter but I could be wrong. On the other hand I know  
that neither the VX-10000 nor VX-8600 are affected if the 0xfe 00  
command is too long. Both phones just ignore the extra bytes. What is  
really interesting is that if I send a full length 0xfe 03 command to  
my phone where the key0 is the DMv5 key the phone still unlocks.

-Nathan

On Jun 28, 2008, at 11:11 PM, Joe Pham wrote:

>> From what I can tell the DMv6 code as it is in SVN is wrong and
>> doesn't reflect the patch I sent in.
>
> It's not the patch that you posted.  Something must have happened to  
> my mail server since I didn't see your patch 'till today.  Anyway,  
> from what I could tell, it does pretty much the same thing.  It  
> worked fine on the enV2 that I have access to.  I don't want to  
> spend any more time on this than I have to so I'm more than happy to  
> use your patch; but I'm interested in a protocol log showing the  
> current code is not working correctly.
>
> -Joe Pham
>
>
> ____________________________________________________________
> Click here to lower your monthly payments.  Act now and save!
> http://thirdpartyoffers.netzero.net/TGL2231/fc/Ioyw6ijnhBcJTsP45a4XLAm8ZJfGO2fD1jEAMsbj4ULYzM4DzWygok/
>
> -------------------------------------------------------------------------
> Check out the new SourceForge.net Marketplace.
> It's the best place to buy or sell services for
> just about anything Open Source.
> http://sourceforge.net/services/buy/index.php
> _______________________________________________
> BitPim-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/bitpim-devel


-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php