V3c broken on latest P2KCommander versions

[tomman]

I was working with an old V3c here, and it does not work with P2K Commander 4.9.E... When you plug the phone, the program simply freezes when detecting the P2K interface.. and in some extreme cases, i even get a BSOD from USBPORT.SYS! (using WinXP SP2 and SP3)

3.3.0 AFAIK is the last version that properly works with V3c. Oddly enough, his sucessor (the V3m) DOES work nicely with 4.9.E (and probably with the 5.x.x versions too). And the problem seems to be more firmware-related: Flash a V3m with V3c firmware (they do use the same hardware, sans the MicroSD slot on V3c, so crossflashing is safe in this case), and it will NOT work with 4.9.E. Flash back to V3m firmware, and it works again!?

Other tools also have problems with the V3c: for example, the recently released p2k05 seem editor for CDMA works with the V3m, but not with the V3c and older phones (again, the app just sits there and freeze).

So, the V3c needs some special workarounds? I can grab 3.3.0 and use it whenever i need to work with a V3c, but that's not the idea

[s5vi]

pls compare 3.3.2 and 4.9.c option settings
as i remember config files are not compatible , so you must look in options dialog (without phone plugged)

thats true , above 3.3 i use new device detection code.
in device manager is usb modem, or app. can switch to p2k mode?

[tomman]

Sorry for the long, LONG delay Real life sucks, but i have done a LOT of testing with a few random CDMA phones here.

The V3c never gets switched to P2K mode by 3.3.2, but it does get switched by 4.9.E. 3.3.2 is set to "Standard P2K commands". 4.9.E is also set to the same P2K commandset.

I have flashed that V3c to Sprint' V3m firmware (risky to flash away, so DON'T DO IT!)... and Sprint firmwares do implement the USB device in a quite different way: instead of your classic USB modem, you get a "USB Composite device" with two COM ports: one standard modem, and a "diagnostic" port (actually a interface for Qualcomm CDMA service apps, like QPST. BitPim only works on this port). However, P2K Commander FAILS to detect the COM port! (perharps because of the non-conventional USB composite device?) But... if i force P2KC to use the COM port of the modem part, it successfully puts the phone on P2K mode and i can work with the phone. BTW: P2K05 Seem Editor DOES recognize this scenario, so you may want to use it to put your phone in P2K before toying with it on P2KC

I also got a K1m, and it works without problems. It had stock firmware from Movistar Venezuela, but i flashed it to generic (DST), and then upgraded with Telus to get Java - no problems so far, and it's much more stable than the V3m. FYI, both the K1m and the Sprint-flashed V3c works under Linux with moto4lin, but the V3m fails miserably (yes, i still have my genuine V3m, with Motorola firmware). So, V3c P2K implementation sucks, Motorola fixed somehow it on the V3m, but they didn't get it right until the K1m (and Sprint's V3m/K1m/L7c firmware).

Here is a short table of my research results:

- V3c: needs P2KC =< 3.3.2, fails with modern P2K apps. With V3m firmware: same as any V3m
- V3m (DST-Moto): works with most modern P2K apps (P2KC-latest, P2K05 Seem Editor), but fails with Moto4lin
- V3m (Sprint): works with most modern P2K apps, but P2KC fails to detect in AT-mode, due to composite USB device
- K1m/L7c (DST-Moto): works with most modern P2K apps, very stable. K1m and L7c share the same firmware.
- K1m/L7c (Sprint): same as Sprint V3m, they all share the same firmware.
- U6c: WILL NOT WORK WITH P2KC, BECAUSE IT HAS NO FILESYSTEM! Also fails with BitPim/QPST, so don't bother... P2K seem editors are OK.
- There are three major families of Motorola firmwares: DST (most used, available in BREW and BREW+Java builds), Verizon (crappy BREW-based UI), Sprint (built over DST but with a LOT of differences, has Java and their odd USB modes). All of them have a BREW EFS (embedded filesystem?), and a somewhat-limited P2K filesystem that gives access to some of the EFS files and folders.


I hope that this helps you to improve even more the CDMA support in P2KCommander

[s5vi]

Many thanks for testing
Did you tried V-6.0.0 ?
I gave you VIP ststus, so you can doad it from "hot stuff".
6.0.0 contains some cdma code, recognition...etc
i have tested with V3m, v9m, v950, ve240

[tomman]

Nice, thanks!

Just tested v6.0.0. Indeed, the Sprint composite USB device is now handled properly, so there is no need to mess with COM port settings.

Reading the model name on CDMA is also a nice touch I've tested with my K1m, my Sprint-V3m-flashed V3c, and with my stock V3m:

- DST V3m can be sometimes slow to read file list (sometimes it even freezes for a few seconds, it happens randomly). K1m and Sprint are fast. Also happened with old versions, so i suppose that it's one of the many Motorola firmware quirks...

I will keep playing with v6.0.0 for a while, so thanks