T720 + AppLoader == developer insanity | developer.brewmp.com T720 + AppLoader == developer insanity | developer.brewmp.com

Developer

T720 + AppLoader == developer insanity

I am at my wit's end trying to get files onto a Motorola T720 using AppLoader.

I'm using AppLoader 2.1.1.3 with a Future Dial USB cable and Future Dial drivers.

I was able to copy my MIF file onto the phone, but whenever I try to copy my application files to the phone (.BAR, .SIG, .MOD, etc.) I get the following error:

"Error - Low-level EFS operation failed. Could not write to the device EFS"

I have been told that the phone has been test-enabled. Is there any way I can verify this? (i.e. is there a config screen on the phone that displays whether the phone is test enabled?)

I sometimes get that error when transferring very large files,
but otherwise it works fine for me most of the time.
I have heard that USB can corrupt the file system of
several phones (T720 being one of them), but I have
not had this problem.
I think Qualcomm will probably tell you to use serial if
you contact them.
Quote:Originally posted by jthrash
I am at my wit's end trying to get files onto a Motorola T720 using AppLoader.
I'm using AppLoader 2.1.1.3 with a Future Dial USB cable and Future Dial drivers.
I was able to copy my MIF file onto the phone, but whenever I try to copy my application files to the phone (.BAR, .SIG, .MOD, etc.) I get the following error:
"Error - Low-level EFS operation failed. Could not write to the device EFS"
I have been told that the phone has been test-enabled. Is there any way I can verify this? (i.e. is there a config screen on the phone that displays whether the phone is test enabled?)

I sometimes get that error when transferring very large files,
but otherwise it works fine for me most of the time.
I have heard that USB can corrupt the file system of
several phones (T720 being one of them), but I have
not had this problem.
I think Qualcomm will probably tell you to use serial if
you contact them.
Quote:Originally posted by jthrash
I am at my wit's end trying to get files onto a Motorola T720 using AppLoader.
I'm using AppLoader 2.1.1.3 with a Future Dial USB cable and Future Dial drivers.
I was able to copy my MIF file onto the phone, but whenever I try to copy my application files to the phone (.BAR, .SIG, .MOD, etc.) I get the following error:
"Error - Low-level EFS operation failed. Could not write to the device EFS"
I have been told that the phone has been test-enabled. Is there any way I can verify this? (i.e. is there a config screen on the phone that displays whether the phone is test enabled?)

Instead of transferring these files individually you should send them over as a module. Start AppLoader and in the Module menu select "New". Then simply point to the directory where all your application files are - including the MIF and SIG files - and determine the name you want it to appear as on the phone, and off you go.

Instead of transferring these files individually you should send them over as a module. Start AppLoader and in the Module menu select "New". Then simply point to the directory where all your application files are - including the MIF and SIG files - and determine the name you want it to appear as on the phone, and off you go.

wow. I never even noticed that "Module" menu item before. I'll have to start using that instead of the drag-n-drop method I'm currently using.
thanks for the info guys! :)

wow. I never even noticed that "Module" menu item before. I'll have to start using that instead of the drag-n-drop method I'm currently using.
thanks for the info guys! :)

Hi JtThrash
I have recieved a similar problem when writing .mod files to subdirectories on a device. I received the following message: "Could not write to the device EFS". It appears that long file names (for example names with more than 12 characters) seem to cause this problem.
Kirk

Hi JtThrash
I have recieved a similar problem when writing .mod files to subdirectories on a device. I received the following message: "Could not write to the device EFS". It appears that long file names (for example names with more than 12 characters) seem to cause this problem.
Kirk

I was hoping I would get my t720 and it would just work...fat chance!!!
Here's my problem:
After getting the t720 back from Qualcomm test bit enabled I used a USB cable and ran AppLoader. The directory structure displayed in the Apploader (v2.1.1) pane (although all that displayed was a "/"...an empy root). I tried to create a new module but I get the following error -
"Error - Low-level EFS operation failed. Could not write to the device EFS"
Same happens if I try to create a file. Interestingly I can create directories without problems. After reading through all the posts here about problems with the t720 I got a serial cable as this seemed more likely to work - not so!! I get the same problem with a serial cable.
I guess the question is: Is my phone fried, or do I need to do something extra?
BTW, I can type ###3 at the App menu and it shows "Debug Avail" - this means it has in fact been test bit enabled, right?
Any help would be great...
-m

I was hoping I would get my t720 and it would just work...fat chance!!!
Here's my problem:
After getting the t720 back from Qualcomm test bit enabled I used a USB cable and ran AppLoader. The directory structure displayed in the Apploader (v2.1.1) pane (although all that displayed was a "/"...an empy root). I tried to create a new module but I get the following error -
"Error - Low-level EFS operation failed. Could not write to the device EFS"
Same happens if I try to create a file. Interestingly I can create directories without problems. After reading through all the posts here about problems with the t720 I got a serial cable as this seemed more likely to work - not so!! I get the same problem with a serial cable.
I guess the question is: Is my phone fried, or do I need to do something extra?
BTW, I can type ###3 at the App menu and it shows "Debug Avail" - this means it has in fact been test bit enabled, right?
Any help would be great...
-m

I have exactly the same problem with my T720.
The only diference is that apploader shows the directories and files of the already installed applications.
Did you managed to upload any application on yours?
Thanks in advance,
Thiago

I have exactly the same problem with my T720.
The only diference is that apploader shows the directories and files of the already installed applications.
Did you managed to upload any application on yours?
Thanks in advance,
Thiago

I didn't get any joy. I ordered a new handset and it is currently being test-bit enabled.
I'll post a reply if I get it working....
-m

I didn't get any joy. I ordered a new handset and it is currently being test-bit enabled.
I'll post a reply if I get it working....
-m

I'm having the exact same problem Murderizer described. I've been in touch with an experienced BREW developer who has suggested that I try finding a T720 specific driver. My current driver is called Motorola Handset USB Driver.exe and came from Verizon. What drivers have others been using?

I'm having the exact same problem Murderizer described. I've been in touch with an experienced BREW developer who has suggested that I try finding a T720 specific driver. My current driver is called Motorola Handset USB Driver.exe and came from Verizon. What drivers have others been using?

Unfortunately I wasn't able to solve the problem. I ordered a new t720, got it test bit enabled and it worked fine.
The original t720 I was working with seemed to somehow get fried before I even got my app onto the device. All I can suggest is dump your current t720 and try a new one - not ideal I know.

Unfortunately I wasn't able to solve the problem. I ordered a new t720, got it test bit enabled and it worked fine.
The original t720 I was working with seemed to somehow get fried before I even got my app onto the device. All I can suggest is dump your current t720 and try a new one - not ideal I know.

Glad you got your new phone to work, Murderizer. I solved my problem too. Turns out it was a simple miscommunication about whether the phone was test enabled.

Glad you got your new phone to work, Murderizer. I solved my problem too. Turns out it was a simple miscommunication about whether the phone was test enabled.

I was having this same problem recently on Samsung A610. Any file over a certain amount would give the Low Level EFS error. But smaller sizes would work fine (load). Files that would load were like 200K.
ANyways , I checked my Device Manager, and update my USB controller driver, and this fixed it. So I think it is USB/driver related.

I was having this same problem recently on Samsung A610. Any file over a certain amount would give the Low Level EFS error. But smaller sizes would work fine (load). Files that would load were like 200K.
ANyways , I checked my Device Manager, and update my USB controller driver, and this fixed it. So I think it is USB/driver related.

Hi all,
I got the same exact problem with a C343 (Error - low level EFS operation failed. Could not write to the device EFS ), can create folder but cannot upload any file (etheir mif or sig or mod), even when using the module techinique.
I saw some questions here but no one did answers, I wonder if anyone knows them:
1) If doing the ###3 shows the debug availble msg, does that mean that the phone is test enable ?
2) Is there any way to check if the phone is test enabled ?
Thanks in advance, any help will be apreciate.
Manric

Hi all,
I got the same exact problem with a C343 (Error - low level EFS operation failed. Could not write to the device EFS ), can create folder but cannot upload any file (etheir mif or sig or mod), even when using the module techinique.
I saw some questions here but no one did answers, I wonder if anyone knows them:
1) If doing the ###3 shows the debug availble msg, does that mean that the phone is test enable ?
2) Is there any way to check if the phone is test enabled ?
Thanks in advance, any help will be apreciate.
Manric

I got support from Qualcomm here in Brazil, and they told me that the new devices are coming with the EFS locked by the manufacturers, so no one can get a cable and upload files to the device.
So you must send the phone to Motorola to get it unlocked.
[]'s
Witto

I got support from Qualcomm here in Brazil, and they told me that the new devices are coming with the EFS locked by the manufacturers, so no one can get a cable and upload files to the device.
So you must send the phone to Motorola to get it unlocked.
[]'s
Witto

I think most devices anymore will delete your app/mif files on reboot of the phone if the device is not test enabled..
-Tyndal

I think most devices anymore will delete your app/mif files on reboot of the phone if the device is not test enabled..
-Tyndal

Don't you think...
Developer_Insanity = T720 + AppLoader
...is more correct

Don't you think...
Developer_Insanity = T720 + AppLoader
...is more correct