Welcome to the HowardForums: Your Mobile Phone Community & Resource.
HowardForums is discussion board dedicated to mobile phones with over 1,000,000 members and growing!
For your convenience HowardForums is divided into 7 main sections; marketplace, phone manufacturers, carriers, smartphones/PDAs, general phone discussion, buy sell trade and general discussions. Just scroll down to see them!
Only registered members may post questions, contact other members or search our database of over 8 million posts. Why don't you join us today!
If you have time check out our sister sites: HowardChui.com - Where you can find the latest mobile phone news and reviews. HowardChui.com phone gallery - See interesting pictures of phones that we've taken. HowardForums Wiki - Our Mobile Phone Encylopedia. Niknon.com - Our sister site about Digital Photography. SlowFo.com - General Discussion.
It puts the phone in Suspend/diag mode and switches the phone into the "Moto USB Composite" Device, which installs Data Logging MCU Interface, Test Command Interface, Accessories Interface and Motorola Flash Interface needed for P2KSeem to connect!!
It also includes the latest P2K.inf and P2k.SYS so no extra drivers are needed either...
__________________ Verizon WirelessCustomer Council Member Verizon PHONE Hacking Info & How To's click -> HERE, <-- If you have suggestions PM me Need Help? PLEASE POST IN THE FORUMS instead of PM'ing me!!
Read -> An Open Letter to those who PM me for help!
Using up one of my dumb question chits...what is the software "really" designed to do?
It almost sounds like a phone firmware updater, but I understand that Verizon, T-Mobile, etc., have their own flavors that they control and provide to customers. MPT already has its own updater...so what is this updater going to be updating? I don't have any other SW for my e815 than MPT...
Mark, I was afraid to try it. I thought it was another "GSM" only program. How well does it work? Does it work with any other software? Can it be used for flashing a phone? Maybe it could help with getting the Bell flash to work.
My guess is that Motorola will have arrangements with the carriers to allow only sanctioned firmware updates. You have to hook up your phone to run this software, which then looks up the latest VZW-approved updates and applies them.
Phone(s):
1: Personal - Too Many.. see link in my signature
2:
3: Work - T-Mo 8320, 8800, BB Pearl, Backups: Blackberry 8700, 8800, 7290, 7230
Provider(s):
Personal - Verizon Wireless (CDMA) | Work - T-Mobile (GSM)
Joined: Dec 2002
From: Wilmington, DE
Posts: 14,102
Quote:
Originally Posted by Redflea
Using up one of my dumb question chits...what is the software "really" designed to do?
Good one
Its designed to "flash your phone at home" with updated firmware when its available so you don't have to drive into a "store"...
But to get the phone into suspend mode, the drivers to install, etc to the point at which P2KSeem will connect to the phone, you don't have to actually go thru the flash process.
Quote:
Originally Posted by Redflea
It almost sounds like a phone firmware updater, but I understand that Verizon, T-Mobile, etc., have their own flavors that they control and provide to customers. MPT already has its own updater...so what is this updater going to be updating? I don't have any other SW for my e815 than MPT...
MPT has nothing to do with the firmware. Its "updater" is to update the MPT software running under Windows, and not anything on the phone.
This Moto Software updater is going to be used for when the Wireless carrier has an updated flash/firmware available, you can get it from Moto and update your phone yourself.
Now, it remains to be seen if Verizon, T-Mobile, Cingular, etc.. make their firmwares available this way...
And I'm not saying to use this to update the firmware of your phone... Just use it to the point to get the phone into suspend mode, and have the P2K drivers get installed so you can use P2KSeem... This way... there is no need to look for and find a PIRATE copy of PST software.
Lets face it, a good copy of PST is hard to find... so, why pirate it, when you no longer need to??
Phone(s):
1: Personal - Too Many.. see link in my signature
2:
3: Work - T-Mo 8320, 8800, BB Pearl, Backups: Blackberry 8700, 8800, 7290, 7230
Provider(s):
Personal - Verizon Wireless (CDMA) | Work - T-Mobile (GSM)
Joined: Dec 2002
From: Wilmington, DE
Posts: 14,102
Quote:
Originally Posted by loooney2ns
Mark, I was afraid to try it. I thought it was another "GSM" only program. How well does it work? Does it work with any other software? Can it be used for flashing a phone? Maybe it could help with getting the Bell flash to work.
I'm also thinking along with what tbb1226 says... only after the wireless carrier has approved it, will the firmware get added and be available.
Right now, when I hook up both my V710 and E815.. it checks and says NO Updates are available... Well, that is true for my E815, but my V710 is still 1 level down (I got 1.40.0R but 02.03.00R is current). So Verizon's firmware is not there yet...
but the important part here, even if Verizon doesn't have there firmware there, is that it suspends the phone properly...
Phone(s):
1: Personal - Too Many.. see link in my signature
2:
3: Work - T-Mo 8320, 8800, BB Pearl, Backups: Blackberry 8700, 8800, 7290, 7230
Provider(s):
Personal - Verizon Wireless (CDMA) | Work - T-Mobile (GSM)
Joined: Dec 2002
From: Wilmington, DE
Posts: 14,102
Quote:
Originally Posted by jlbrightbill
Possibility of perhaps tricking the program into thinking you have a Bell Mobility E815 and picking up a flash that way?
Not sure how... or even if its possible... There are NVM strings that can't be changed... it might be reading those... along with the current firmware string...
Phone(s):
1: Droid, Omnia II, Tour, Storm, Curve, Pearl
2: Touch, Q9m, Dare, Voyager, Chocolate, VX7000
3: Flipshot, Juke, Mobi, Alias, Boulder, Razr, 2128i
Provider(s):
Verizon Wireless
Joined: Apr 2004
Posts: 1,857
Quote:
Originally Posted by Mark_Venture
but the important part here, even if Verizon doesn't have there firmware there, is that it suspends the phone properly...
Another good point of using this vs. PST is that once you connect your phone as directed by this software, the Motorola USB Device drivers remain there even if you close the updater software. You can then run P2KSeem and it connects fine.
__________________
Member, Verizon Wireless Customer Council
Phone(s):
1: Moto Droid: C_01.3E.01P ESD 56
2: Moto A4500 Napoleon
3: 2 Moto e815 BM_X_1.7.1P First on VZW!
Provider(s):
Verizon
Joined: Mar 2005
From: Philly
Posts: 5,886
Well, without any reverse engineering even, this could prove a very valuable tool for us here on HoFo and elsewhere. If it provides a stable installation of the latest drivers that can be made to work with all the other apps in our typical suite of hacking/modding software, that alone is uniquely valuable. It certainly stirs the imagination as to what could be done with it. I can't imagine them releasing it without the strictest possible security controls, I certainly don't know. But the fact that it is legal for public use and has this heretofore unique capability to load the USB Composite device drivers makes it a wonderful developement.
Exciting times on HoFo these days!
__________________
kbman
Droid Does Dictation! (and 1Ghz +WiFi tether too!)
If we knew what we were doing, they wouldn't call it research. - Albert Einstein
Phone(s):
1: Personal - Too Many.. see link in my signature
2:
3: Work - T-Mo 8320, 8800, BB Pearl, Backups: Blackberry 8700, 8800, 7290, 7230
Provider(s):
Personal - Verizon Wireless (CDMA) | Work - T-Mobile (GSM)
Joined: Dec 2002
From: Wilmington, DE
Posts: 14,102
Quote:
Originally Posted by Smuuth
Another good point of using this vs. PST is that once you connect your phone as directed by this software, the Motorola USB Device drivers remain there even if you close the updater software. You can then run P2KSeem and it connects fine.
When using PST on my E815, the Moto USB Device group remains after exiting PST... if I don't restart my phone via the software...
I.e. start PST, let the drivers load... exit PST... stays as Moto USB Device group, and does not flip back to Moto USB Modem until I unplug the phone, turn it off, and turn it back on, connect it back to the PC...
Not sure how... or even if its possible... There are NVM strings that can't be changed... it might be reading those... along with the current firmware string...
But its i nice thought...
Someone pointed out in the other thread the possibility of flashing with the Bell firmware we have, then running the update program. This isn't an area of expertise for me so I have no idea if it would work.
Phone(s):
1: Moto Droid: C_01.3E.01P ESD 56
2: Moto A4500 Napoleon
3: 2 Moto e815 BM_X_1.7.1P First on VZW!
Provider(s):
Verizon
Joined: Mar 2005
From: Philly
Posts: 5,886
All these ideas seem plausible but it still requires the cooperation of Bell Mobility to release an update. We have to see how quickly the carriers jump on this.
Phone(s):
1: Personal - Too Many.. see link in my signature
2:
3: Work - T-Mo 8320, 8800, BB Pearl, Backups: Blackberry 8700, 8800, 7290, 7230
Provider(s):
Personal - Verizon Wireless (CDMA) | Work - T-Mobile (GSM)
Joined: Dec 2002
From: Wilmington, DE
Posts: 14,102
One Side Note.... this apparently has 1 negitive side effect...
It includes a USBMOT2000.INF that re-introduces the USBSER.SYS problem
Not sure what I mean? re-read the background info section on my USBSER.SYS page...
Short version.... This is the driver that identifies the phone as "moto usb modem" to windows. Installing Moto's Software Update program forces Windows to re-install the driver for Moto USB Modem, and Windows Picks this one included by Moto that uses the USBSER.SYS that is a core component of windows, which can cause data transfer/communication problems when using USB cable with ANY Pogram that utilizes the Moto USB Modem driver (i.e. BitPim, MPT, DUN, FAX, etc...)... NOTE P2K type programs (P2KCommander, P2KSeem, etc) are NOT impacted as they use the P2K.INF/P2K.SYS drivers...
Work around process...
1. Disconnect your phone from the computer.
2. Install Moto Software Update.
3. Connect your phone and let the Windows Add New Hardware wizard run and detect/install what ever driver it wants to for your phone.
4. Disconnect your phone from the computer.
5. Run BVRP's Driver Tool...
As long as you don't re-install the Moto Software Update program, the BVRP version of the USBMOT2000 driver will be in use.
For info on how the USBMOT2000 from BVRP differs, again, see the background section of my USBSER.SYS page.
04-18-2006, 22:22
Linear Mode
