Motorola w755 | developer.brewmp.com Motorola w755 | developer.brewmp.com

Developer

Motorola w755

I am having problems with the Motorola w755. I am only able to connect to the handset using QPST EFS Explorer. I am able to create directories in the BREW folder but I am unable to write files to the created directories as well as the MIF folder. When attempting to write to the handset EFS displays the error stating "failed to transmit request packet".

Might anyone know why this might be and how to correct the problem?

bigskilet wrote:I am having problems with the Motorola w755. I am only able to connect to the handset using QPST EFS Explorer. I am able to create directories in the BREW folder but I am unable to write files to the created directories as well as the MIF folder. When attempting to write to the handset EFS displays the error stating "failed to transmit request packet".
Might anyone know why this might be and how to correct the problem?
I am facing the same problem on the Moto W210. Seems to be due to some kind of a lock (put in place by manufacturer Motorola).
No solution yet...

bigskilet wrote:I am having problems with the Motorola w755. I am only able to connect to the handset using QPST EFS Explorer. I am able to create directories in the BREW folder but I am unable to write files to the created directories as well as the MIF folder. When attempting to write to the handset EFS displays the error stating "failed to transmit request packet".
Might anyone know why this might be and how to correct the problem?
I am facing the same problem on the Moto W210. Seems to be due to some kind of a lock (put in place by manufacturer Motorola).
No solution yet...

on the W755, im getting EFS2 error, cannot load files. Is this the same issue or related to yours ?
any tips?

on the W755, im getting EFS2 error, cannot load files. Is this the same issue or related to yours ?
any tips?

Correct solution is to connect using normal BREW 3.x, and use EFS1 mode instead of autodetect setting.
This just worked for us.

Correct solution is to connect using normal BREW 3.x, and use EFS1 mode instead of autodetect setting.
This just worked for us.

Same here, when I manually set the EFS1 instead of auto detect, I was able to create a module with all the files copied correctly.

Same here, when I manually set the EFS1 instead of auto detect, I was able to create a module with all the files copied correctly.