Some success
The updated Windows drivers will allow connection to the phone in AT (Hayes) mode, and one software title, p2ktools, provides an AT console. Motorola has deviated from and much extended the Hayes Command set originaly designed to issue modem instructions, for interfacing their mobile phones. I read through the guide provided by Motorola, but it contained nothing useful. I did find some new undocumented AT commands by running a USB sniffer while using MPT, it seems that MPT blocks access to the files stored, because the commands revealed where able to find and delete them from the AT console.
AT+MDIR=?
This will reveal the directory structure in the form of a list of folders, ie. ; “u:\mobile”, “u:\mobile\java”, etc.
AT+MR?
This will return a list of all files stored on the internal storage and the micro sd card in the form (“type”, “location”, “name”, size) , ie. ;
(“GIF”,”u:\mobile\picture\preload”,”amplitude.gif”,54344)
AT+MW=”type”, “location”, “name”, size
this will apparently transfer a file to the phone, with proper changes made to “type”, “location”, “name” and , size of course. I never tried to work this one out on the AT command console since I never had a problem sending files to the phone via bluetooth.
AT+MDFILE=”type”, “location”, “name”, size
This will delete the file specified after the equal sign. This one was the big one for me, it allowed me to remove all the crap that Motorola preloaded on the phone, opening up a gigabyte of space.
AT+MFLAG
This will tell the phone to start in flash mode next time you restart it.
AT+MRES
This command will restart the phone, if you first entered AT+MFLAG it will restart in flash mode.
To connect to the phone in AT mode, it must be set to ‘Modem’ mode from; ‘Settings’ -> ‘Phone Settings’ -> ‘USB Connection Type’ in the phone menu. In this mode the phone is recognised by the computer as a Motorola USB Modem, with a device ID of 4081. In flash mode the it reads as a LOCOSTO flash device with a USB device ID 4082. I have not found a driver that connects to this device. If a driver is located it should allow bulk reading and writing of the entire contents of the phones memory, allowing tweaking of the entire operating system.
This last problem is important for a couple of reasons. First, T-Mobile somehow stuck two backgrounds, two screen savers, and two java programs on there somewhere that the AT command console did not reveal and that I would really like to remove. The second reason is that it is impossible to install a fully functional java program without first replacing the security certificate. I you replace the security certificate with your own, you can self sign your own applications giving them access to all the capabilities of the java VM and through them, all of the phones hardware.
More mysteries! and technical gibberish! pt 3
