AutoRun Problem On The XDA II - Windows Mobile Software Development

I am trying to get a software installation (AutoRun) app to run on the XDA 2. The purpose of this app is to load application binaries from an MMC or SD into the ROM of the XDA.
This app works fine on the XDA 1, but I am having problems running it on the XDA 2. Specifically, the app runs via "AutoRun" and therefore executes without "Shell32".
Consequently, any attempt to access data files on the MMC (e.g. using the "FindFirst/FindNext" or "CreateFile") using a pathname of the form \\Storage Card\\ results in failure (WIN ERR 03 (ERROR_PATH_NOT_FOUND)).
It must be possible to access files on the MMC/SD without Shell32, as the "CheckAutoRun.exe" program in the Windows Start-Up folder achieves this successfully.
Can anyone advise me of the appropriate device driver(s) that must be loaded to access MMC/SD card files without Shell32 running?
Any advice would be greatly appreciated.

Related

for the Professionals htc p3300 users

Maybe someone can help me with the following problem:
I installed a 4 gb memory card using the patch and it works perfectly. The phone identifies it and I use it for music files and the tom-tom without any problems. However, when I wanted to install a new program I was asked where I want to install it (phone, memory card or Bluetooth). I chose the memory card, the program begins with the installation but then I get the following message: “your telephone has not enough memory. Delete old or unused items to create new memory”. It seems (although I chose for the memory card) that the program is trying to be installed on the phone memory. Does anybody have a solution for this problem? The HTC help service said its because the memory card is 4 gb which they don’t recommend.
Hi,
Many .cab files are setup to copy some files on internal memory even if you choose "Storage Card".
You can try to download WINCE Cab Manager to check your cab file and change location of destination files using this program.
WHat is the software you are trying to install? Is it actually a CAB file or desktop installer?
Does this happen for all software you try to install?
Please let us know.
thanks for your reply,
the program is called " the 5 minute veterinary consult feline and canine".
its from skyscape and its specially for wm users.
when i installed the tom tom on the memory card i didn't have any problems. i will try to install the WINCE Cab Manager.
thanks a lot for your advise. i will let you know if it worked.

How to read/write to any application in isolated storage on any device

Hi,
how to read/write to any application in isolated storage. It is cumbersome, but works:
- You want the data from application A which uses GUID 1
- Install application and let it write its data
- Now you write your own litte wp7 application B which talks to a WCF hosts to transmit files and uses the exact same GUID as Application A
- Deploy application B with Visual Studio
-> here comes the trick: Visual Studio does an Update-Installation if it finds the GUID of the application to deploy on the phone, therefore AppData is not wiped and only the program files (which were already in the original XAP file are replaced) are replaced by yours.
- You now have access from your application B to all data which was written by application A
- If you are finished you install application A with an XAP Deployer which can also perform update installations (like http://forum.xda-developers.com/showthread.php?t=1016766)
Regards,
-t
Nice finding! IsolatedStorage WTF!1!!1!
Very nice! Won't this lead to more pirating?
Sent from my {Samsung Focus} using XDA Windows Phone 7 App
finalfan3241 said:
Very nice! Won't this lead to more pirating?
Sent from my {Samsung Focus} using XDA Windows Phone 7 App
Click to expand...
Click to collapse
Probably not. Accessing the application storage doens't let you run the app on another phone, you need the application installation for that (which is not readable by an app itself).

Can't transfer files via Android File Transfer

It seems I can't transfer files via Android File Transfer. On another note (haha pun), I can't believe anytime I want to access my storage I need to load this oddball program, which doesn't even work. I miss USB mass storage.
When I try to copy a file, it tells me "Could not replace file, could not copy file (filenamehere)." This is so frustrating.
Anyone have any ideas? I'm running OS X 10.6.8.
Thanks.
I too am having problems tranfering file to and from the computer. Whats frustrating is that I did not have this problem when I got the note2.
Same problem on the Mac. Had to boot into my windows side. Quite annoying if you ask me
Samsung Galaxy Note II
I have no problem transferring files running latest version of OSX on a mbp... The only time I see any error is if my screen is locked when I connect it, I have to make sure it's unlocked when i connect it for the file transfer program to work. It sees the phone and sd card perfectly fine. I see many people on int version complaining of this too but worked first time for me.
Regurgitated From My Giant Note II
When I connect to my PC, my Note shows up as "SPH-L900". Phone icon, but I can click it to open and use just like any other folder. Absolutely no issues whatsoever moving files to/from sd card.
Do you have the Samsung drivers installed? :shrug:
I can't copy or move files from the device either. I am able to copy/move files to the device.
Running Windows 7 64-bit with Samsung drivers installed.
I was really hoping to get some expert insight on this... I am bummed... I can't even get this to work on Mac or windows... what's the deal with this MTP stuff?
Samsung Galaxy Note II
I can't even notice a difference when using the mtp. Phone shows up under my computer and when i double click i can see the external and internal sd cards. I just go on with business as usual...
What kernel are you guys using?
The new Perseus kernel seems to have fixed this issue for me.
http://forum.xda-developers.com/showthread.php?t=1975262
Stock kernel...
Samsung Galaxy Note II
Hi guys, i know that´s bit older thread, but i need help with Android File Transfer.
I don´t see all files in window on Mac.
I miss there *.mpo file from images folder
have you tried something like this?(https://play.google.com/store/apps/...mNvbS5kb29ibG91LldpRmlGaWxlRXhwbG9yZXJQUk8iXQ..) i bought it havent tried it in Mac OS X but can in a bit if youd like
I can´t use it... I have Mac in work... It´s older Mac without Wi-Fi card, and we don´t have Wi-Fi network.
Bluetooth is slow for bigger files, therefore I wanted to use Android File Transfer.
Please read forum rules before posting
Questions and help issues go in Q&A
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
FIX?
hi guys.. I had this same problem trying to use android file transfer from my 2013 nexus 7 to macbook air.
I remembered I had a password set to access ES FILE EXPLORER on my Nexus 7 and opened the app, typed in my password and that made the trick... No more problems transferring from my Nexus 7 to the Macbook air. Tested with a 800 mb mp4.
Use ADB to transfer on OSX
I know this thread is old, but I just happened upon it. I am using OSX mountain lion, and could not transfer to my mac using the OSX Finder GUI. However, there is a workaround…. ADB PULL! (Note: this is nothing fancy/special, its just using command-line utilities instead of GUI and Android File Transfer)
**You must have ADB installed (Google, its not very hard to install it)**
1. Connect via USB
2. Disable MTP on your phone
3. open terminal and enter:
Code:
adb pull YOURFILENAME LOCATIONONCOMPUTER[optional]
benbeel said:
I know this thread is old, but I just happened upon it. I am using OSX mountain lion, and could not transfer to my mac using the OSX Finder GUI. However, there is a workaround…. ADB PULL! (Note: this is nothing fancy/special, its just using command-line utilities instead of GUI and Android File Transfer)
**You must have ADB installed (Google, its not very hard to install it)**
1. Connect via USB
2. Disable MTP on your phone
3. open terminal and enter:
Code:
adb pull YOURFILENAME LOCATIONONCOMPUTER[optional]
Click to expand...
Click to collapse
You can use Android file transfer and that way you get the same mtp functions as Windows... Get it from here:
http://www.android.com/filetransfer/
Sent from my SPH-L900 using Tapatalk
jocarog said:
You can use Android file transfer and that way you get the same mtp functions as Windows... Get it from here:
http://www.android.com/filetransfer/
Sent from my SPH-L900 using Tapatalk
Click to expand...
Click to collapse
My point was for people for whom android file transfer wasn't working.
Why so defensive? Anyways good point!
Sent from my SPH-L900 using Tapatalk
I received the message "Could not copy file [filename]" and "your phone is locked" (dont remember exact wording) from the Android File Transfer app when trying to transfer a file.
The file size was small. The filename didn't seem to matter BUT i have to say: I got 3-4 successive failures with the original filename - which contained a few brackets and parentheses, but then was successful on the first attempt with a renamed file containing no special characters. But later, I was able to copy using the original filename.
Sometimes after unplugging/replugging the phone back in to restart Android File Transfer, I'd see the file appear in the location I copied it to even though it gave me an error earlier.
This did not happen consistently - sometimes it'd work normally, sometimes it'd work but appear to fail with an error, and sometimes it would just fail with an error. The phone was unlocked and on the home screen at all times.
Pretty strange. This is with Nexus 5 stock rom on 4.4.3, Android File Transfer 1.0.50.2266.

[Root] NookManager - graphical rooter for 1.2.x and beyond

This is a graphical, interactive rooting system with the ability to create/restore backups and factory settings.
This has been tested on systems 1.1.5, 1.2.0 (US/UK), and 1.2.1. It will probably work on earlier versions and should be safe to use on future versions. For best results, however, you should be on 1.2.1 before using this tool.
If you've tried rooting your nook unsuccessfully with another utility, it's best to do a factory restore (from NookManager, choose the "Rescue" option and then "Restore factory.zip") and, if your nook came with older firmware, upgrade to the latest 1.2.1 firmware.
Features:
Root your Nook
Backup/Restore
Restore to factory settings
Disable B&N Apps
Custom plugins
How to root:
1. Download NookManager.
2. Unzip the file you downloaded and write the NookManager.img file to an empty SD card. On Windows, you can use disk imager. Linux and mac users can use dd.
Use a real SD card adapter when writing the image, DO NOT USE YOUR NOOK AS THE SDCARD ADAPTER.
If possible, you should use a dedicated SD card for the NookManager image (so you can easily restore from a backup should you ever screw up your Nook). A 512Mb card is big enough for the NookManager image plus a backup of your Nook.​
3. Power off your Nook, insert the SD card and power on.
You should see the NookManager boot screen followed within 15 seconds by the welcome screen.​
4. Choose "No, continue without wireless"
the wireless option is for advanced users looking to connect directly to their device​
5. Make a backup using NookManager! Choose "Rescue" then "Backup" then "Format remaining space on SD card" and finally "Create backup"
Because NookManager cleans the empty space on the Nooks' internal partitions and compresses the backup, it will take at least 15 minutes (and up to 45 minutes) for the backup to complete. Be patient. The final backup file can be as small as only be a few hundred megabytes, depending on the number of downloaded or sideloaded books you have.​
6. Copy the backup image to your computer. Connect your Nook to your computer using the USB cable. Copy the 'backup.full.tgz' and 'backup.full.md5' files from the NookBackup drive to your computer.
This is your backup in case anything happens to your SD card. This backup is tied to your individual Nook so keep it safe. It's important to copy this file while your Nook is still booted from the SD card because Windows will normally hide the NookBackup partition on the SD card. If you ever need access to the NookBackup partition again, just boot your Nook using the NookManager SD card and connect the Nook to your computer with the USB cable.​
7. Root! After your backup, press "Back" and "Back" to return to the Main Menu. Press "Root" and then "Root my device"
8. That's it! After rooting, pres "Back" and then "Exit". Remove the SD card and put it someplace safe, in case you need to restore to your backup later.
After rooting, you can install Google Apps using straygecko's excellent NTGAppsAttack package if you want to use Google Market/Gmail/Calendar/etc.
[/LIST]
Technical stuff:
The actual rooting function is minimal and as non-invasive as possible:
uRamdisk is patched to enable ADB
the internal database setting is changed to allow installation of non-market apps
the DroidSansFallback font is replaced with the updated font from jellybean to add support for extended characters
the su/Superuser binary/package is installed
Relaunch is installed
ADB Konnect is installed for enabling/disabling ADB over wireless
on systems running firmware 1.2+, the ModManager jars and package are installed
on 1.2+ systems, the PackageInstaller.apk from the 1.1.2 firmware is installed to resolve issues with package installers
and, finally, the Amazon appstore is installed just to have some easy way of downloading new apps. You can uninstall it using ReLaunch if you don't use it.
The uRamdisk patching is done with scripts rather than copying pre-compiled binaries, so this should be safe for all existing versions of the Nook firmware and (hopefully) will be forward compatible with any new releases.
The rooting procedure is non-destructive and can be run multiple times without causing problems.
Under the hood, this is a minimal linux environment with the nook drivers/binaries and a few core android binaries. The display is generated with imagemagick and written directly to the framebuffer.
If you're connecting to NookManager wirelessly over SSH, the username/password is root/root
Wherever possible, the parts of this system are compiled from source including the Linux kernel, uBoot, and all of the buildroot utilities. The hardware drivers and associated binaries are extracted from the 1.2.0 upgrade package.
The source for the project, including an automated buildscript is available at GitHub.
Support for custom menu items and scripts is documented here.
https://github.com/doozan/NookManager/downloads
NookManager.zip
17.9MB · Uploaded 14 hours ago
File was not found.
Click to expand...
Click to collapse
??
Weird. I deleted/re-upped the file and the download link seems to be working now.
ok..now it works. Thanks
Will this work with NoRefresh?
Thanks for the work on this - it was easy and worked great. And if you're planning to update, maybe add ES File Explorer or Titanium Backup in the pre-installed apps; that would make it easier to install apks directly from your SD card instead of having to do it over wireless adb. But thanks regardless.
Can confirm no refresh works great. Installed FBReader, Opera Mobile, ES File Explorer and Kindle app. Great
I just came from a firmware that had the ability to change the hardware buttons for page turning, any chance of this being added?
Thanks for this! Giving it a try.
Just curious though... I'm trying to create the backup of the device and it seems to take forever to format the free space. It also took forever to find the wireless network and I eventually just rebooted it. How long does it usually take?
I'm using a NST on 1.2.0 and have tried a 2GB Sandisk and a 8GB Dane-elec microsd card.
Gonna try redownloading and re-installing the image.
Install apk
Hi, i successfully root my NGL(1.2.0) but, if i try to install apk (Cool Reader) i got an error window "Out of space" and i'm almost sure it must be enough space to install, may someone can help with this ?
mobamoba said:
maybe add ES File Explorer or Titanium Backup in the pre-installed apps
Click to expand...
Click to collapse
Good suggestion, I've added ES File Explorer
Gvr4-330 said:
it seems to take forever to format the free space..and wifi
Click to expand...
Click to collapse
Thanks for reporting this. There was a glitch with the script that formats the SD card and with the wifi loading. Both issues have been fixed in the latest release.
asprin said:
if i try to install apk (Cool Reader) i got an error window "Out of space"
Click to expand...
Click to collapse
How are you trying to install the apk? I'm also using Cool Reader it installed with "adb install" and runs just fine. For best Nook compatibility, use coolreader 3.1.2-27 (12/11/2012 build) or later.
Originally Posted by asprin
if i try to install apk (Cool Reader) i got an error window "Out of space"
Click to expand...
Click to collapse
You get this error when you try to install application from an .apk file on sdcard or when you try to update application via it's built in updater.
ADB install works fine.
Good suggestion, I've added ES File Explorer
Click to expand...
Click to collapse
I use
Rhythm Software - File Manager
http://rhmsoft.com/?p=96
osowiecki said:
You get this error when you try to install application from an .apk file on sdcard or when you try to update
Click to expand...
Click to collapse
I'm not able to replicate this: I can copy coolreader to my sd card, and install it from there with no problems using ES File Explorer or ReLaunch. Maybe you really do have a disk space issue. Try openinng an adb shell and run "df -h" to see disk usage on your mounted partitions.
mobamoba said:
maybe add ES File Explorer
Click to expand...
Click to collapse
osowiecki said:
I use Rhythm Software - File Manager
Click to expand...
Click to collapse
It turns out you can install apks using the file browser in ReLaunch, so I'll be removing ES File Explorer in any future versions.
jeff_kz said:
I'm not able to replicate this: I can copy coolreader to my sd card, and install it from there with no problems using ES File Explorer or ReLaunch. Maybe you really do have a disk space issue. Try openinng an adb shell and run "df -h" to see disk usage on your mounted partitions.
It turns out you can install apks using the file browser in ReLaunch, so I'll be removing ES File Explorer in any future versions.
Click to expand...
Click to collapse
Thx for respond, mate, I tried install with file browser in ReLaunch from sd card, and i cant imagine that can be space issue cause i just start procedure after factory reset and rooting, anyway, thanks for tip, will try tomorrow install new build, and adb install. In general great work you did :good:
jeff_kz said:
I'm not able to replicate this: I can copy coolreader to my sd card, and install it from there with no problems using ES File Explorer or ReLaunch. Maybe you really do have a disk space issue. Try openinng an adb shell and run "df -h" to see disk usage on your mounted partitions.
It turns out you can install apks using the file browser in ReLaunch, so I'll be removing ES File Explorer in any future versions.
Click to expand...
Click to collapse
df :
/dev: 116452K total, 0K used, 116452K available (block size 4096)
/sqlite_stmt_journals: 4096K total, 0K used, 4096K available (block size 4096)
/rom: 16116K total, 227K used, 15888K available (block size 512)
/system: 285583K total, 210922K used, 74661K available (block size 1024)
/data: 824424K total, 304344K used, 520080K available (block size 4096)
/cache: 237987K total, 4179K used, 233808K available (block size 1024)
/media: 245484K total, 40K used, 245444K available (block size 4096)
/sdcard: 31149680K total, 6924320K used, 24225360K available (block size 16384)
Are you using UK or US Nook?
I'm on US Nook FW 1.2 + v176 kernel
I'm able to reproduce the apk install problems now. The "Not enough free space" error is what android throws when the internal PackageManager can't create the temporary apk file. In this case, it turns out that it's a permissions-related read error from the sdcard. I don't know if this is a matter of the internal PackageManager not running with elevated permissions, or if it's that the sdcard is mounted too restrictively.
If I re-mount the sdcard without the restrictive permissions, I can install apks from the sdcard without any errors:
Code:
umount /sdcard
mount -t vfat /dev/block//vold/179:17 /sdcard
If anyone else has any ideas for making this work, I'm open to any suggestions. In the meantime, "adb install" works just fine for installing packages.
I really suggest grabbing Android Commander if you're new to adb to graphically install apps.
jeff_kz said:
Thanks for reporting this. There was a glitch with the script that formats the SD card and with the wifi loading. Both issues have been fixed in the latest release.
Click to expand...
Click to collapse
Thanks for the quick update. I'm going to try it out now and will report back. I'm very excited
It works! Thanks so much for this! Very easy way to root and backup.
With your tool now I use this to read comics, RSS and books. First I need to say thank you.
I installed "D7 Google Reader" and "Google Drive" which requires Google Login. How could I use this software? Thanks
Also I installed version 0.2, I saw 0.3 comes out. Can I just update 0.2 to 0.3 directly? Thanks
so glad I decided to check the nook thread. Finally BN apps gone . Thank You
hi all, anyone have test factory reset on nstg US ? my backup is corrupt.
Envoyé depuis mon GT-N7100 avec Tapatalk

[Q] how to let my note 2 be detected as a mass storage?

Hey there
Can anyone be a lifesaver ?
How to let my pc (windows 7) detect my phone as a mass storage device?
So far I tried the terminal emulator and the ums app.the terminal emulator, although I entered usb.config mass_storage, it only shows conneceted as an installer.
Please help
Title and content has been edited due to typo and left out . Sorry for the lack of info provided earlier
Just search on play store for USB mass storage app. They actually work although a bit buggy at times.
Sent from my GT-N7100 using XDA Premium 4 mobile app
I used one recommended by asoftech.it didnt work. im trying to recover photos lost when doing a wipe. Should I move on to another app?
I am not able to access my internal storage. Anyone can help me with this? It says on the app that we cant because of the limitations set by Linux

Categories

Resources