Database Info

Relocate .NET Compact Framework 2.0 to your storage card!

One of the biggest complaints with Microsoft's Compact Framework 2 (CF2 for short) (and, consequently, with programs relying on it - Hitchhiker, SMS Notifier, Webby, IBE Mail etc.) has always been its storage needs, which, by default, is some 5.4 Mbytes. See for example this thread for users' opinions on the memory consumption on CF2 and their subsequent not wanting to install it.
I've always tried to reduce the main memory load on Pocket PC - with great success. Just search for the word-start "relocat" in the Pocket PC Magazine Expert Blog and on my old homepage for some examples of them. No wonder I've also decided to look into this, so far, unsolved problem to greatly help my fellow Pocket PC users. And, after a day's work and testing, I can present you a 100% working solution, which has been thoroughly tested on four of my WM2003+ PDA's, all with success. This IS a big thing, considering that internal memory is still precious, even with most Windows Mobile 5 (WM5) Pocket PC's. (For example, most WM5 PPC's are shipped with 128M of ROM, of which in general 40-45 Mbytes is free.) The situation is even worse with pre-WM5 Pocket PC's, where the available RAM is very rarely (only with devices shipped with 128 Mbytes of RAM) over 50 Mbytes, from which CF2 takes away 5.4 Mbytes.
Note that this will work on all Pocket PC and Pocket PC Phone Edition devices that are able to run CF2 (that is, all WM2003+ devices, including WM5).
The complete tutorial
* create a directory on your storage card or, if you have, in the built-in File Store. (Note that the files, as they are surely not needed at boot time (unlike some Today plug-in DLL's), may also be relocated to a storage card. That is, they don't need to be stored in the more scarce File Store - if it's available at all; that is, if you have a pre-WM5 device). Let's assume you give this directory the name "DLLs".
* move the following files from \Windows to this directory:
cgacutil.exe
MSCOREE2_0.dll
netcfagl2_0.dll
netcfd3dm2_0.dll
GAC_CustomMarshalers_v2_0_0_0_cneutral_1.dll
GAC_Microsoft.VisualBasic_v8_0_0_0_cneutral_1.dll
GAC_Microsoft.WindowsCE.Forms_v2_0_0_0_cneutral_1.dll
GAC_Microsoft.WindowsMobile.DirectX_v2_0_0_0_cneutral_1.dll
GAC_mscorlib_v2_0_0_0_cneutral_1.dll
GAC_System.Data_v2_0_0_0_cneutral_1.dll
GAC_System.Drawing_v2_0_0_0_cneutral_1.dll
GAC_System.Messaging_v2_0_0_0_cneutral_1.dll
GAC_System.Net.IrDA_v2_0_0_0_cneutral_1.dll
GAC_System.Web.Services_v2_0_0_0_cneutral_1.dll
GAC_System.Windows.Forms.DataGrid_v2_0_0_0_cneutral_1.dll
GAC_System.Windows.Forms_v2_0_0_0_cneutral_1.dll
GAC_System.Xml_v2_0_0_0_cneutral_1.dll
GAC_System_v2_0_0_0_cneutral_1.dll
(netcf2_0license.txt can also be copied here - or just deleted.)
This means only Microsoft .NET CF 2.0.GAC and mscoree.dll needs to stay in \Windows. Never ever try to touch the former (Microsoft .NET CF 2.0.GAC). Even if you copy it back to \Windows (after starting any CF2-dependent app), CF2 won't work again until you reinstall it.
Copying the files can be done in several ways, of which I show the one way that requires no third-party apps, that is, without having to resort to, for example, the WindowsCE File System plug-in of the desktop-based Total Commander.
Start the built-in (Pocket) File Explorer and navigate to \Windows. Tap and hold an empty (not highlighting any file or directory) region anywhere (for example, the end of the list) and enable "View All files" in the context menu:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Now, click the "Name" drop-down menu in the upper right corner; a "Sort By" list will be displayed, defaulting to "Name". Switch it to "Date":
Scroll to the region with filedates of Aug 26 and, with cgacutil.exe, 27, 2005 (this is the easiest way to find the files) and mass-highlight all files that are listed in the above list. Note that mscoree.dll should not be highlighted (as has been pointed out, it should be left in \Windows). Also note that the filedates of the current, 2.0 version of CF2 are all dated at Aug 26/27 last year. They will only have a different filedate if you've restored them from a backup. Then, they will have the timestamp of the restoration and you'll may end up having to hunting for them one-by-one, based on their name.
Now tap-and-hold the selection somewhere so that the context menu comes up. Choose Cut:
Go to the target directory (in this case, DLLs on your storage card); tap-and-hold an empty area and choose Paste:
The transfer of the files will start:
Note that you can also use other file handler tools on the Pocket PC; for example Resco File Explorer or Total Commander. In Resco, go to File/Options/Browser and make sure "Show all files" is chosen (instead of the default "Hide hidden files and files...") as can be seen in this screenshot.
* get a registry editor that is able to (flawlessly (!)) edit multiline strings (that is, all known, up-to-date registry editors except PHM Registry Editor and Total Commander; please check out The Ultimate Roundup of Registry Editors for the Pocket PC for a thorough explanation of why I don't recommend these two applications if interested). In this tutorial, I use Resco Registry Editor (Resco for short). It's commercial, but the 14-day, unrestricted trial version is fully sufficient for our purposes. Start it.
* First, we'll modify the so-called "System Path" (which is a bit similar to the PATH in traditional operating systems) so that it includes our new directory. To do this, go to HKEY_LOCAL_MACHINE\Loader:
Note that, in here, I've switched to "Tree Mode" in View/Show Tree View as can be seen in here.
Now, click SystemPath (highlighted in this screenshot); you'll be presented the following dialog:
Note that there may be some values already in the text input area in here. For example, if you've ever had SKTools or MemMaid relocate DLL's for you, the target directory will be in here. Also, by default (if you haven't ever touched the System Path), there may be a \Release\ or \windows\oem\ in here. These can be safely deleted as they're not used. You can, naturally, leave them in there; of course, then, you must make sure the new path is entered in a new row as can be seen in this x51v or this HTC Wizard (latest Qtek ROM) screenshot. Once again: you can safely delete them.
All you have to do is entering the full path of your new DLL directory in here. For example, if you've moved the CF2 files to a directory named DLLs on your storage card named CF-Card (Storage Card, CF Card, SD Card, SD-MMCard are also widely used), enter
\CF-Card\DLLs\
in here, as can also be seen in here:
Don't forget to add the leading and the trailing backslash characters (\)!
Now, click OK in the upper right corner and answer Yes:
In the list view, the new, just-entered value should be shown as can be seen in here:
Note that, again, if you want to keep the previous values of System Path, then, the new entry should be put in a separate row. For example, if the previous value of HKEY_LOCAL_MACHINE\Loader has been
\SD-MMCard\Programs\CrEme\bin\
\LOOXstore\DLLs\
then, you need to add the new value in a new row as can be seen in here:
* now comes a bit more complicated part. First, go to HKEY_LOCAL_MACHINE\ SOFTWARE\ Microsoft\ .NETCompactFramework\ Installer\ Assemblies\ Global.
Note that, on some devices, in the above path, SOFTWARE may not (all) be uppercase. This varies from model to model and shouldn't be paid attention to. (Also note that I’ve added spaces after every backslash characters (\) in the above registry path so that the blog engine nicely renders it. In the reality, it should not contain any spaces!)
Here, look for names (on the left) that have 2.0 in them. Note that almost all values (except for CustomMarshalers, Microsoft.WindowsMobile.DirectX and Microsoft.WindowsMobile.DirectX, which have all been introduced in CF2 and didn't exist in CF 1.x) seem to be duplicated and their name will start with the same (Microsoft.*, mscorlib.*, System* etc.); it's only after this that they start to be different. One set of them will continue in Version=1.0, the other set will continue in Version=2.0. The only exception from this "must contain Version=2.0" law is the value starting with "Microsoft.VisualBasic, Version=8.0.0.0" (that is, 8.0 instead of 2.0).
In all these Version=2.0 values, you'll need to modify the original path referring to \Windows to the new home of the relocated files - for example, in our case, \CF-Card\DLLs.
In order to be able to see this as easily as possible, enabling Show Header in the View menu is highly recommended, as can be seen in here. Then, you'll be able to greatly increase the displayed length of the value names if you drag the header to the right. Of course, switching to Landscape and/or VGA mode (if possible) is highly recommended. Then, you'll be able to see the version number in all the values. For example, this screenshot shows a QVGA WM5 device in Landscape - here, it's also possible to increase the width of the "Name" column so that the version number can also be seen without having to click every value.
All you need to do is just click all the values that have Version=2.0 in their name (except, as has already been pointed out, the 8.0 Microsoft.VisualBasic) and just change \Windows to the new value in the first row. An example of this:
before:
after:
Another example of a changed value (WM5, QVGA device, with files relocated to \Storage Card\_):
and with the VGA x51v in standard VGA mode:
Note that, much as it refers to the main storage (\Program Files\.NET CF 2.0\), you don't need to pay attention to the second row in all these values. Just leave them there.
Consider using a PC-based Pocket PC controller tool to do this (please read this article for more info on them if not sure). Using them, you can speed up the registry modification by orders of magnitude, particularly if you use copy/paste to insert the new directory path.
After you've modified all the affected values, check once more if it was successful. Fortunately, you'll see all the names (showing that a given value is 2.0-specific) and values (showing whether it refers to the original \Windows directory in the main storage or somewhere else) on the same screen as in this screenshot.
You may also want to export the just-modified branch to a registry (.reg) file. Then, in case you reinstall CF2 and want to avoid hand-editing the entire stuff, you'll only need to reimport this file. To do this, tap-and-hold Globals in the upper, tree pane and choose Export:
On WM5 devices, you will also want to make sure the changes are flushed back to the ROM (as the Registry is kept in RAM and changes are rarely flushed back to ROM, which will result in a simple soft reset getting rid of all changes and, therefore, CF2 not working after the relocation). To do this, on many WM5 devices (like the HTC Wizard), just long-press the Power button. On some other devices, you must explicitly configure the device to shut the PDA completely down upon a long-press (instead of just dimming the screen). For example, on the x51v, you must go to Settings/System/Power/Power Button and enable "Full power off" instead of the default "Dim/light the display" as can be seen in this screenshot. You'll only need to power off your PDA for some seconds because it's before shutting it down that the Registry is flushed back to the ROM; that is, you can safely switch it back on instantly.
Congratulations! Now, the relocated CF2 will be working! If you've modified the System Path, you'll need to reboot; otherwise, you can start your CF2 apps right away.
Advanced remarks for geeks/advanced hackers
* Exporting, editing and re-importing the contents of HKEY_LOCAL_MACHINE\ SOFTWARE\ Microsoft\ .NETCompactFramework\ Installer\ Assemblies\ Global (so that you can much easier change all occurrences of \Windows to the new path) just won't work because the values in here are multiline strings, which are exported as hexadecimal values by all export-capable Pocket PC-based registry editors (I've checked this!) like in here:
* The \Windows paths in HKEY_LOCAL_MACHINE\ SOFTWARE\ Microsoft\ .NETCompactFramework\ Installer\ Assemblies\ Reference (note that the last word is Reference, not Global!) don't need to be modified. Actually, you can even get rid of the entire subkey because it's not used at all.
* Technically, the GAC*.dll files don't need to be in the System Path; it's only with the other files (cgacutil.exe, MSCOREE2_0.dll, netcfagl2_0.dll and netcfd3dm2_0.dll) that must be. That if, you have already set up a relocated DLL directory somewhere in the System Path, you can safely move the files to there. It's in order to be as easy as possible for a novice user that I've instructed copying all relocated files to the same directory in the System Path.

one better make damm sure that one dont have any .net programs running when the pda is off too
because then the SD interface get shutdown to save power
and then programs which are running which depend on the framework crash and burn

Rudegar said:
one better make damm sure that one dont have any .net programs running when the pda is off too
because then the SD interface get shutdown to save power
and then programs which are running which depend on the framework crash and burn
Click to expand...
Click to collapse
Yup, but you can also play with PNPUnloadDelay to avoid problems because of this (see http://www.pocketpcthoughts.com/forums/viewtopic.php?t=44488 for more info).

how does this method compare to the way the new beta allows GAC to be installed to the storage card?
http://www.microsoft.com/downloads/...53-a418-42d9-a481-19ba3ceca1a6&displaylang=en
from what another user told me, the beta allows you to install about 80% of the framework to the storage card.
-jeff

jeffreii said:
how does this method compare to the way the new beta allows GAC to be installed to the storage card?
http://www.microsoft.com/downloads/...53-a418-42d9-a481-19ba3ceca1a6&displaylang=en
from what another user told me, the beta allows you to install about 80% of the framework to the storage card.
-jeff
Click to expand...
Click to collapse
Yes !!! Thanks for the council.
Before with the previous version of net framework 2 my free memory was of 25,80 Mb.
After to have installed the Sp1 new beta on the Storage Card is of 29,78 Mb.

Hi Menneisyys. Would MUCH appreciate your guidance;
I'm using a ROM image that works great - except that the CF 2.0 SP1 installation is buggy. I can't de-install it as it's not in my installed apps. Any idea what files I need to delete so the install proggie thinks it's gone and does a reasonable re-install? Currently the install proggie says "you already have this verison installed".

craigiecraigie4 said:
Hi Menneisyys. Would MUCH appreciate your guidance;
I'm using a ROM image that works great - except that the CF 2.0 SP1 installation is buggy. I can't de-install it as it's not in my installed apps. Any idea what files I need to delete so the install proggie thinks it's gone and does a reasonable re-install? Currently the install proggie says "you already have this verison installed".
Click to expand...
Click to collapse
Unfortunately, it's not only files but also registry entries. Try deleting all the above-listed, 2.0-only (don't touch the CF1-specific ones!) registry entries.
Do you have WM5 or a previous OS? If you have the latter, I can send over an .unload file and a registry import so that you can directly delete these without any manual registry editing.

Menneisyys said:
Unfortunately, it's not only files but also registry entries. Try deleting all the above-listed, 2.0-only (don't touch the CF1-specific ones!) registry entries.
Do you have WM5 or a previous OS? If you have the latter, I can send over an .unload file and a registry import so that you can directly delete these without any manual registry editing.
Click to expand...
Click to collapse
Hi Mennei, I'm on WM5 and would TRLUY appreciate a .unload file! Thanks a stack.

craigiecraigie4 said:
Hi Mennei, I'm on WM5 and would TRLUY appreciate a .unload file! Thanks a stack.
Click to expand...
Click to collapse
Unfortunately, you can't easily hack WM5 (as opposed to pre-WM5 OS'es) to think it has a program installed - you don't have write rights on \Windows\AppMgr and, tehrefore, can't copy the (un)install DLL there. That is, with WM5, it's, to my knowledge, not possible to automatically remove stuff.

Menneisyys said:
Unfortunately, you can't easily hack WM5 (as opposed to pre-WM5 OS'es) to think it has a program installed - you don't have write rights on \Windows\AppMgr and, tehrefore, can't copy the (un)install DLL there. That is, with WM5, it's, to my knowledge, not possible to automatically remove stuff.
Click to expand...
Click to collapse
hmmm.....
maybe if you installed a "dummy" program that would reference the appropriate uninstall file for CF2.0?
just an uneducated noob suggestion. (feel free to educate me! i'm always eager to learn)

blazoner said:
hmmm.....
maybe if you installed a "dummy" program that would reference the appropriate uninstall file for CF2.0?
just an uneducated noob suggestion. (feel free to educate me! i'm always eager to learn)
Click to expand...
Click to collapse
It might work.

CF2 late question
I know there has been no action on this thread but as a late commer I was wondering if the CF files can be copied and included into the extended ROM (instead of the storage card) and then flashed onto the device?

mnazmi said:
I know there has been no action on this thread but as a late commer I was wondering if the CF files can be copied and included into the extended ROM (instead of the storage card) and then flashed onto the device?
Click to expand...
Click to collapse
Yup, I think so - after all, when unlocked, the extended ROM is just another drive in the file system. WHEN unlocked, I think.

FYI
i downloaded the .Net CF2.0 SP1 fr http://www.microsoft.com/downloads/...88-59e2-4eba-a70e-4cd851c5fcc4&DisplayLang=en
i selected Storage Card during the installation. all GAC* files are installed automatically\directly onto my Storage Card\Windows folder. when i checked on HKEY_LOCAL_MACHINE\ SOFTWARE\ Microsoft\ .NETCompactFramework\ Installer\ Assemblies\ Global, all 14 2.0 and 8.0 entries are already with the correct folder path (\Storage Card\Windows). therefore, i only needed to move 4 files below onto the \Storage Card\Windows folder, and added value Storage Card\Windows\ into the SystemPath in HKEY_LOCAL_MACHINE\Loader
cgacutil.exe
MSCOREE2_0.dll
netcfagl2_0.dll
netcfd3dm2_0.dll
thanks for the tips!

TUTORIAL: How can (and why should) I change the standard File Dialog?

In the Smartphone & Pocket PC Mag VIP Help forum, I’ve received the following question:
“When I create an email on my Mogul (HTC4000) and go to insert file, my memory card is not a listed option to pick from any ideas? My Moto Q did this as did my 6700 before that”
The explanation and cure for this is pretty simple. (Note that if this problem doesn’t apply to you, don’t stop reading: in the second part of this tutorial, I provide you with some really useful tips. Also note that this article deprecates my pre-WM5 one published HERE. I also explain the difference between the MS Smartphone and Pocket PC platforms, file dialog-wise.)
First, the explanation. Let’s see the case of the Moto Q – that is, MS Smartphone devices. In which way is the MS Smartphone (that is, touchscreen-less) platform different from the “big brother”, the Pocket PC OS? In several ways, of course – it’s much dumber in almost every respect (I miss the ability to fine-tune the backlight level the most). In a way, however, it’s (at least for many users) much more useful and usable than the Pocket PC operating system: its file dialog box is entirely different from that of Pocket PC’s. This, however, greatly confuses users switching between the two platforms.
When you go to Menu / Insert / File (or, more generally, you select a file from any program - again, this tutorial is a generic one), you’ll have direct access to all the directories (including the storage card(s)) as can be seen in the following screenshot:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Here, if you do select the storage card (by going to Menu / Storage Card), you’ll be taken directly to the card and, there, can select (left softkey) any file, in any directory, as can be seen for example in the following screenshot:
On Pocket PC’s, the situation is vastly different. When, upon composing a mail, you select Menu / Insert / File, you’re shown ALL the (accessible – see the rules later) files in one listbox as can be seen in the following screenshot:
There can be several hundred or even thousand files in the list, which results in both at time huge loading times and a lot of work to actually find the file you need; therefore, you can restrict the selection to a subdirectory only by using the “Folder” drop-down list:
The results of the restriction can be seen in HERE, showing an example of listing the contents of the “cities” subdirectory.
Note that – this is VERY important! – the “Folder” drop-down list only contains subdirectories under \My Documents in the built-in storage memory and the direct descendants (subfolders) of the root folder of the storage card. That is, if you have a file you’d like to add in, say, a second descendant of the root of your card, (say, \a\b), it won’t be accessible at all. The same stands for the subdirectories of \My Documents on the storage card – they won’t be listed either. This has always a BIG problem with Windows Mobile and has widely been criticized (see for example THIS for links).
In addition, there’s no way to “select only the root (without its visible subdirs) of the storage card” from the list – as opposed to the above-shown Smartphone screenshot. You will ONLY see the contents of the root of the card if you leave the “Folder” drop-down menu on its default, “All Folders” setting. Then, happy hunting for the file - after the list, finally, loads ; )
If you find this all (1, the HUGE number of the files shown 2, the inability to access anything outside \My Documents in the built-in storage memory and the direct subdirectories of the root of the storage card) a pain in the back, rejoice: there are decent solutions to the problem. Of them, I explain the two most widely used and important ones; one of them being even free.

1.1 Spb Pocket Plus 4
As has already been mentioned in my quick review of the IEM plug-in of Spb Pocket Plus, the, particularly with the new and indeed vastly improved version, highly recommended all-in-one system helper application, there’s built-in support for changing the system-level file dialog to something much better.
If you do get Spb Pocket Plus 4+, your problems are already solved: after installing it, the new file dialog will take effect at once, as can be seen in the following screenshot:
That is, it’ll work just great; you’ll be able to freely navigate the entire directory structure and won’t be flooded with hundreds or thousands of files at the same time, making it pretty hard to find the right one (or even wait for the list to load).
1.2 Y. “Mad Programmer” Nagamidori's FileDialogChanger
Before the (recent) release of Spb Pocket Plus 4, this was the suite I recommended the most for Windows Mobile users. Now that Spb Pocket Plus 4 also supports this functionality AND is a highly recommended all-in-one tool, I no longer do this - FileDialogChanger won't be needed any more if you go the Spb Pocket Plus 4 route. If you, however, don't (or REALLY need the exception defining capabilities, which I explain in the next subsection), make sure you get and install FileDialogChanger.
Get THIS ZIP file, extract gsgetfile.dll from the ARMRel directory and transfer it to \Windows on your Pocket PC. Then, get THIS file and, from the ARM directory, copy filedlgchg.cpl also to \Windows. Note that you MUST right-click these two links and select Save As to directly save it - if you just left-click it (as usual), you'll be taken to an error page because of the invalid referrer.
Now, go to Settings / System and tap the new File Dialog Changer icon and make sure you enable the Exchange Standard File Dialog checkbox as can be seen in the following screenshot:
That’s all; now, you can safely traverse the file system when adding attachments (or, again, looking for a file to load - or, a directory to save your current one to). Note that, unlike with Spb Pocket Plus, there’s no a quick drop-down tree list containing the current directory, all its parents the storage card(s). However, you can always use the left softkey (up) to go up to the parent (to the root, as it starts with \My Documents), where you can already click Storage Card (or any other directory):
1.2.1 Defining exceptions
Note that Mad Programmer’s FileDialogChanger also allows for defining exceptions (Spb’s program is incapable of this). That is, if, for some reason, you do not want to rely on the new file dialog in a given program, just add the given application to the exception list. For example, you prefer seeing all your, still sticking with emulators, ROM files on your PDA at once, and don’t want to manually navigate the directories to find them, then, you might want to add the emulator to the exception list so that FileDialogChanger knows it shouldn't be used with that specific app.
An example with PocketHobbit, the Commodore 64 emulator (discussed HERE), which uses the default file dialog box (screenshot HERE; with Mad Programmer’s tool, HERE). Then, all you need to do is clicking ADD, go to the directory with the executable file and double-click it. In this example, I’ve added all the three EXE files visible in the previous screenshot, resulting in the following exception list:
After this, PocketHobbit will start using the standard file dialog, while the rest of the system (all the other apps) will still use the redefined one - that is, that of FileDialogChanger.
(Note that I’ve chosen this emulator for this explanation not because of its (pretty much missing) merits but because it’s based on the system-level dialog box. If you are really into C64 emulation, forget this emulator at once and go for something better.)
1.3 Why will you want to consider changing the file dialog?
No, not only when you want to add attachments to a mail. The new dialog can be used much more widely. As a rule of thumb, whenever and wherever you’ve, in the past, encountered the standard, dumb and, in many cases, very annoying file dialog control, the new one will be used instead at both loading and saving. Yes, even at saving - for example, when you save Word Mobile files, you can tell the system in exactly which directory it should be stored to as can be seen in THIS screenshot.
As the standard file dialog only lists files under \My Documents in the main memory and files one level deep in the file system of the card (without showing the user where they really come from), in many cases, your only choice will be using third-party file dialogs like these two.
Again, just an example of the utility of these third-party applications: in order to keep the directory structure clean, you keep, for example, your emulator ROM image files two levels deep on your storage card under, say, \ROMs\SNES. Unless you use direct invocation (you click the given file from File Explorer to make the system invoke the associated emulator) and (when you do need them) you don’t copy around these files to a directory already visible to the standard file dialog, you won’t see these files at all. Unless, of course, install a better, third-party file dialog - one of the apps introduced in this tutorial.

UPDATE (11/16/2007): HowardForums forum member BeyondTheTech has just created a CAB installer of Mad Programmer’s FDC. This greatly simplifies installation – you just download the ZIP file from HERE, unZIP it, transfer the CAB file to your handset (if it’s not already there) and execute it in order to be installed. (Install it into main memory!) After a reset, you're all set – you only need to enable it as explained above (by checking in the checkbox).
Note that being put in a CAB installer also means you can uninstall it if you want if, for some reason, disabling the above-mentioned checkbox isn’t sufficient for you (because, for example, you want to remove all third-party stuff from your PDA without hard / clean resetting it).

FDC 1.70 Beta with thumbnail view

I was using this one when I am still in the pocketpc era....
http://tillanosoft.com/ce/tgetfile.html
But apparently, it don't support every applications out there...

ww2250 said:
I was using this one when I am still in the pocketpc era....
http://tillanosoft.com/ce/tgetfile.html
But apparently, it don't support every applications out there...
Click to expand...
Click to collapse
Yup, very few.
It's mostly on the MS Smartphone platform that it's useful - several of Masterall's kick-ass emulators use it.

It exist also gsgetfile.dll for Smartphones.
"http://www.geocities.jp/hou_ming_2/gsgetfile-i_sp.zip"
PS: "http://www.geocities.jp/hou_ming_2/beta/FakeCursorSP.zip" also for Smartphones.

Word?
Nice solutions! The free one especially since, well, it's free!
However, this doesn't seem to effect Word Mobile. Even with the FDC Word still only let's one search one directory deep...
Any thoughts on that one?
EDIT: to clarify, while saving files it works, but i'm reffering to the OPEN-file dialog. Which still s**cks.

DopamineNL said:
Nice solutions! The free one especially since, well, it's free!
However, this doesn't seem to effect Word Mobile. Even with the FDC Word still only let's one search one directory deep...
Any thoughts on that one?
EDIT: to clarify, while saving files it works, but i'm reffering to the OPEN-file dialog. Which still s**cks.
Click to expand...
Click to collapse
Yup, Office Mobile has a different file dialog. I don't know how it can be changed.

CharlyV said:
It exist also gsgetfile.dll for Smartphones.
"http://www.geocities.jp/hou_ming_2/gsgetfile-i_sp.zip"
PS: "http://www.geocities.jp/hou_ming_2/beta/FakeCursorSP.zip" also for Smartphones.
Click to expand...
Click to collapse
Thanks; as usual, you're GREAT!

CharlyV said:
FDC 1.70 Beta with thumbnail view
Click to expand...
Click to collapse
WOW... thumbnails... sounds nice.
How good is it though considering it's still BETA? Menneisyys, have you had a go at this? Any problems reported... speed, stability etc?
Would be great if you could do a review of it.
Cheers

Menneisyys said:
Yup, Office Mobile has a different file dialog. I don't know how it can be changed.
Click to expand...
Click to collapse
Office Mobile use own open file dialog, no workaround exist.

CharlyV said:
FDC 1.70 Beta with thumbnail view
Click to expand...
Click to collapse
I just downloaded FDC 1.70 Beta. It doesn't have the gsgetfile.dll so I used the same gsgetfile.dll from v1.66 and extracted it along with the v1.70 filedlgchg.cpl you have provided in the link.
When I tried to configure it, I had the option to enable the thumbnail view but when I actually used the File Dialog, I couldn't see anything different from the older v1.66.
Any help would be appreciated.

[TOOL][Forensic] Andriller - data acquisition from Android devices

Moderators: if this thread is in wrong place please forgive and move it to a location best suitable for this thread.
Self-introduction I come from law-enforcement digital forensics background aimed at data extractions from mobile devices.
I would like to introduce a tool that I created.
Andriller
http://andriller.com
Andriller is a Windows GUI forensic tool, that performs read-only, forensically sound, non-destructive acquisition from Android devices. The executable is run from a terminal or by executing directly; it produces results in the terminal window, and a report in a HTML format.
Usage:
Download Andriller from the download page and install. To use the software you need to obtain a license key (free trial available). Instructions on doing this will be provided on the page
Note: Android version 4.2.2+ requires to authorise the PC to accept RSA fingerprint. Please do so, and tick the box to remember for future.
Note: Devices with Superuser or SuperSU App require to authorise root access from an unlocked screen. Please grand permissions if requested.
Description:
Once andriller is executed, it will produce permilinary results in the terminal window; for rooted devices it will download and decode the content automatically. It will produce a new folder in the location where it was executed, where the main "REPORT.html" file can be opened in a web browser.
Supported data extraction:
Non-root devices (Android versions 2.x):
- Android device make and model
- IMEI, build version, OS version
- Wifi mac address
- Time and date check
- SIM card details (for a some Galaxy Sx devices only)
- Synchronised accounts
Non-rooted devices (via backup method, Android versions 4.x and above)
- Wi-Fi passwords (WPA-PSK/WEP)
- Call logs (Samsung) register
- Android browser saved passwords
- Android browser browsing history
- Google Chrome saved passwords
- Google Chrome browsing history
- Facebook* chat messages
- Facebook* user viewed photographs
- Facebook* user notifications
- WhatsApp* contacts list
- WhatsApp* chat messages
- Kik Messenger* chat messages
- BBM* chat messages (Blackberry Messenger)
- Viber* chat messages
Rooted devices (via root adbd or 'su' binary, any Android versions):
- Security lockscreen pattern gesture extraction (decoding online)
- Security lockscreen PIN code cracking (up to 8 digits long)
- Wi-Fi passwords (WPA-PSK/WEP)
- Synchronised accounts and profile picture
- Bluetooth mac address and name
- Phonebook contacts
- Call logs register
- Call logs (Samsung) register
- SMS messages
- Android browser saved passwords
- Android browser browsing history
- Google Chrome saved passwords
- Google Chrome browsing history
- Facebook* friends list
- Facebook* chat messages
- Facebook* user viewed photographs
- Facebook* user notifications
- WhatsApp* contacts list
- WhatsApp* chat messages
- Kik Messenger* chat messages
- BBM* chat messages (Blackberry Messenger)
- Viber* chat messages
* = if an Application is installed
Disclaimer:
Andriller comes with absolutely no warranty. Even though Andriller was written in a way to be a forensically sound read-only utility, I do not take any responsibility to any damage or harm caused to your computer systems or your Android devices, which may be believed to have been caused by executing Andriller. I also do not take any responsibility of any unsolicited, non-consensual or unlawful misuses of this utility. It is the end user's responsibility to believe an appropriate consent or a lawful excuse was obtained if the utility is used with an other's Android devices, and they are aware what the utility does.
Visit http://andriller.com to download the latest software

Andriller performing AB extraction
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Reporting in HTML
Android Decoders
Password Cracking

Update 14/10/2013
Version 1.0.0a
Python-based compiled executable for MS Windows uploaded.
http://andriller.com
Update 07/11/2013
Version 1.1.0a
Added support to the latest Facebook App.
Minor improvements to decoding method.
Updated 13/01/2013
Version 1.2.0a
Added support for:
- Lockscreen PIN cracking
- Wi-Fi passwords
- Android web browser
--- Saved passwords
--- Browsing history
- Google Chrome web browser
--- Saved passwords
--- Browsing history
- Synchronised accounts
- Kik Messenger
- BBM (Blackberry Messenger)
Improvements to downloading and decoding.
Minor bugs fixed.
Updated 03/02/2013
Version 1.3.0a
Added support for:
- Data extraction via backup method (android version 4.x), no need for root.
Updated 17/02/2013
Version 1.3.1a
Added support for:
- Android (default) E-mail client:
--- Account and passwords
--- E-mails support
Minor bugs fixed.
Updated 21/02/2013
Version 1.3.2a
Improved data handling.
Bugs fixed for PIN cracking.
Updated 01/04/2014
Version 2.0.0
Graphical User Interface (GUI) - for Windows XP/Vista/7/8
Lockscreen cracking for:
--- Pattern
--- PIN
--- Password (using a wordlist file)
Decoding of individual of databases
Also includes all features from previous versions of Andriller
Requires registration, free 7 days license
Updated 19/04/2014
Version 2.0.1
Transferred to andriller.com domain
- Minor bugs fixed
- Added support for decoding Grindr App messages & users (Apple iOS)
- Window size reduced to accommodate smaller resolutions
- Default font changed to Consolas
- License key filename is now stored as the unique id
Updated 29/04/2014
Version 2.0.2
- Installer; Andriller now comes as a Setup Installer for Windows
- Improved PIN and Password cracking speed of up to 48% faster than previously
- Minor bugs fixed
- Some descriptions clarified
Updated ??/05/2014
Version 2.0.3
- Decoders in menus were fixed for error handling
- Typing mistakes corrected (oops)
- Minor improvements all-round
Updated 14/05/2014
Version 2.0.4
- Added support for Viber Messages chat (Android)
- Fixed a bug in Email decoder, so the feature is working now
- Chrome web browser decoding works for any mobile/desktop operating system (Android, iOS, Windows, Unix, Mac)
- Fixed Facebook chat messages decoding for the latest App version
- Decoders; if [Output] if chosen, the decoded data will be saved there; else the decoded data will be displayed in a temporary directory
- Error handling improved within file browsing/saving, license key registration

seriously awesome dude
dude i am working on presentation on forensics ill surely give out your tool in the first place all the others congs :angel::angel::angel:

stealthroot said:
dude i am working on presentation on forensics ill surely give out your tool in the first place all the others congs :angel::angel::angel:
Click to expand...
Click to collapse
Thanks buddy, all the best luck with your presentation and forensics! :good:

Andriller is awesome, customer of yours since half a year, cannot recommend it enough.
This deserves a bump.^^

Hi.
Does your tool support retrieving (at least as a read-only) applications installed and their data from dead Android phones (particularly from those which are not rooted and stuck on boot and showing only logo)?
Do you know any other open-source solution for this?
Thank you.

john2014 said:
Hi.
Does your tool support retrieving (at least as a read-only) applications installed and their data from dead Android phones (particularly from those which are not rooted and stuck on boot and showing only logo)?
Do you know any other open-source solution for this?
Thank you.
Click to expand...
Click to collapse
What you are looking for does not exist (to my knowledge). There isn't a single tool to magically repair half-broken Android devices. It's handset make model dependant. This will require extensive manual interactions to repair boot loops, re-flashing individual partitions, etc. If not successful, the options left are JTAG or even chip-off.

den4uk said:
What you are looking for does not exist (to my knowledge). There isn't a single tool to magically repair half-broken Android devices. It's handset make model dependant. This will require extensive manual interactions to repair boot loops, re-flashing individual partitions, etc. If not successful, the options left are JTAG or even chip-off.
Click to expand...
Click to collapse
Thanks for your reply.
Actually, what I want primarily is not to repair the device itself, but to extract some apps installed with their data which are important.
If there is no a single solution, could you please tell what open source solutions can be used as a complex in this case and what sources would you advise to read (as a starting point and to have a general idea) in order to get a better understanding of possible solutions for this kind of problems?

Andriller is actually working!!!!
Thanks !

Thanks 4 this very useful tool!
At work i use UFED and XRY to aquire and analyse mobile datas...
...but this tool is definitly worth to use beside this two programs.... :good:
greets from austria
chris_forens!c

what is andriller reg. key

Can't extract/decode call logs
I'm able to extract the backup, but I'm not getting call logs for some reason. Is there a different way I should be using the decoder? I ran the adb extraction and got account info, phone MAC, build, wifi passwords and download history. After playing around a bit, I extracted the ab image using 'tools' then parsed the extracted folder which gave me chrome saved passwords and chrome history. I tried parsing .tar and .ab files extracted and didn't get anything useful. Using the call log decoder, i tried to access the com.android.calllogbackup file but theres only a manifest file there (no .db). Any advice on getting call/text logs? Will i need to root the phone? Its a Samsung Galaxy On5, on 6.0.1

[APP][4.0.3+] Facebook Patcher 100+ -Avoid using Messenger, send messages from FB app

PATCHED APK'S HERE - by @wolfballz
What to do if you don't want to use Messenger, rather to send messages from the Facebook app itself?
a) If you'd like to use the voip function, use 55.0.0.18.66 patched.
Do NOT use the unpatched app with Messenger 1.0 because it won't let you see your messages, instead it will ask you to update Facebook.
b) If you don't care about voip calls, but need Facebook's new features and a rich messaging interface like in Messenger, use either 85.0.0.0.18 patched or 78.0.0.16.67 patched (both for ARM only).
It also offers some extra features that the APK patched with 2.9 doesn't have:
● Version modified to 999 so the app won't ask you to update.
● Fixed crash when opening gallery from composer.
● No duplicate emoji buttons in composer.
● Bubble style delivery state icons like in Messenger.
● Blue title bar to fit FB's design (v85 only).
c) If you'd like to stay up-to-date, you can always patch the latest version using Facebook Patcher 100+. The latest version where message notifications work is 106.0.0.26.68. Note that you'll only see the mobile messaging site in the in-app browser on the latest versions!
● 106.0.0.26.68 patched for ARM devices (51.9 MB)
● 106.0.0.26.68 patched for x86 devices (54.8 MB)
FEATURES
● Send messages directly from the main Facebook app without the need to install Messenger.
● Send emojis and stickers.
[The following features aren't offered by Facebook Patcher 100+, just by FBPatcher 2.9 up to version 85.0.0.0.18]
● Use QuickCam to capture & send images and short videos instantly.
● Edit images and videos before sending them.
● Share images from conversations to Facebook.
● Send hot likes, audio clips, events and locations.
● See cool snow fall and floating hearts when sending the appropriate emojis.
● Play Messenger's basketball and soccer game (unfortunately, without score submission).
[The following features are only applicable to Facebook Patcher 100+]
● No matter what variant you download, the patched APK will be a 4.0.3+ one.
● Removes lots of junk from the APK and compresses it --> much smaller app size!
USAGE
0. Install the latest Java runtime if you don't have it yet.
1. Download a Facebook APK from apkmirror.
2. Download the patcher (from V100, use Facebook Patcher 100+), start it with double click and follow the instructions.
3. Uninstall the official Facebook app.
4. Copy the patched apk to your device, install and enjoy!
TROUBLESHOOTING
Can't start the patcher
Firstly, update to the latest Java -- the patcher requires version 1.8 at least. If you can't start it with double click on Windows, you should associate jar files with 'javaw.exe' (NOT 'java.exe' as it won't work). It's in the bin folder of your Java installation (typically 'Program Files\Java\jre*').
On Linux/Mac, you should use 'chmod +x' on the jar file before the first run to get execution permission. Google it if you're not familiar with that command.
Got an error while patching
● Most likely: Facebook changed something in the code, please wait for patcher update.
● Very unlikely: you don't have enough space (<100MB) for the patcher's temporary files.
● Very unlikely: APK file is corrupted, try to download it again.
If nothing helps, post a log or screenshot here.
Can't install patched APK
● You have the official Facebook app installed, you should uninstall it first.
● You have it preinstalled (flashed on 'system') -- you can only get rid of it with root, sorry, not my fault.
● You're trying to install a 4.0.3+ variant over a 5.0+ one and vice versa, uninstall the app first.
● You're trying to install a 5.0+ variant on a pre-Lollipop system, try patching & installing a 4.0.3+ variant.
Patched app quits on start
● If you've just updated to a patched alpha, you may have to clear app data before first start. Some alphas may get in an infinite loop on start if old app data is present. This is not the patcher's fault, the original app also has this issue.
● It's very likely that you've downloaded an APK built for an architecture that's different from your device's one. For example, you have an x86 device and installed an ARM APK that won't work. Since x86 mobile devices are rather rare, you could hardly find any x86 APK's. To obtain one for your device, you should install it from Google Play and save the APK with a backup application or Total Commander. Then you can pull it to your PC and patch it. Don't forget to uninstall the original app before trying to install the patched one!
KNOWN ISSUES
These issues are known and can't/won't be fixed.
● On some versions prior to 75.0.0.23.69 the app crashes when scrolling down 20 messages in thread list, this is not the patcher's fault, use a later version to avoid this bug (85.0.0.0.18 is recommended).
● Back and info buttons on title bar, GIF and Payment buttons don't do anything.
● On Android 6.0+, clicking the blue button in the Messenger permission request window causes a crash. Grant the permissions for the app from Settings/Apps.
● Your basketball and soccer score won't be submitted to the thread.
● From v107, message notifications don't work because Facebook messed up something - use v106 stable instead.
QUESTIONS & ANSWERS
Q: What does it do to the Facebook app?
A: FBPatcher is a desktop Java application that needs a Facebook APK file as input and will provide you a patched APK as output, with Messenger functionality. It only does minimalistic (but yet not trivial) modifications to some classes and the manifest, new code isn't inserted into the app -- the Messenger window with all of its resources and code is in the original APK, this patcher just makes it accessible.
Q: Will the patched app be updated via Play Store?
A: No, you should always download, patch and install the latest version manually to be up-to-date.
Q: Is there any way to make VoIP calls working?
A: From V56, no. Use 55.0.0.18.66 if you need free calls.
DESCRIPTION
Operations performed by the patcher
● Extracts manifest and dex files.
● Finds patchable classes in the dex files by searching for patterns that identify those classes.
● Disassembles dex files that contain patchable code, automatically modifies the classes and reassembles the files.
● Patches the manifest to remove FB specific permissions and modify the Messenger window's theme.
● [100+ only] Reduces app size by removing unused files.
● Updates the APK with the patched files and signs it.
List of patched stuff
● AndroidManifest.xml -- modifies ThreadViewActivity's theme and removes FB specific permissions to allow other FB apps to be installed, also adds CreateThreadActivity again.
● ForceMessenger -- enables in-app messaging.
[The following classes don't exist from a specific version / aren't touched by Facebook Patcher 100+]
● MessengerMSiteUriIntentBuilder -- creates entry points for Messenger code instead of mobile messaging site, also enables some features.
● DiodeMessengerActivity -- replaces the 'Install Messenger' Fragment with Messenger thread list.
● ThreadListFragment -- defines an on-click event for thread list items (ThreadViewActivity will be opened with the selected thread / mobile site will show up when tapping message request).
● FacebookActivityDelegate(Impl) -- crash fix for ThreadViewActivity.
● MuteThreadWarningNotification -- crash fix for ThreadViewActivity.
● BballView(.3) -- crash fix for basketball game.
● SoccerFeedbackEmojisView -- crash fix for soccer game.
● MessagesVideoConfigModule -- Enables gallery video sending/transcoding.
● InboxFilterManager.NoSaveStateBehavior -- was missing, added again
● TwoLineComposerView -- remove Payment button action
● ThreadListContextMenuHelper -- remove 'Mute thread' option
Included third party libs
● XZ for Java by Tukaani
● smali/baksmali by JesusFreke
● SignApk (part of AOSP)
Click to see licenses.
Licensing of XZ for Java
All the files in this package have been written by Lasse Collin and/or Igor Pavlov. All these files have been put into the public domain. You can do whatever you want with these files.
This software is provided "as is", without any warranty.
Licensing of smali/baksmali
[The "BSD licence"]
Copyright (c) 2010 Ben Gruver (JesusFreke)
All rights reserved.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in thedocumentation and/or other materials provided with the distribution.
3. The name of the author may not be used to endorse or promote products derived from this software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE AUTHOR "AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
Licensing of SignApk
Copyright (C) 2007 The Android Open Source Project
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and limitations under the License.
FOR ADVANCED USERS ONLY -- If you place a file called 'fbpatcher.dev' next to the FBP100+ jar file, containing the following text: 'I want my intern settings menu!', internal settings will be enabled in the Facebook app.
Free of Facebook code.
WHAT'S NEW
Version 2.9, 07-21-2016
● Support for latest versions (web view messaging only)
Version 2.8, 07-06-2016
● Fixed crashing new message option (mobile site fallback)
● Patchability check (does not proceed if Messenger code is missing)
Version 2.7, 06-25-2016
● Support for message requests
Version 2.6, 06-17-2016
● Fixed new message option for 83.0.0.0.39
Version 2.5, 06-16-2016
● OS native look and feel with support for high DPI displays
● Sticker search feature
● Fixed new soccer game
● Removed crashing options (mute thread & payment)
Version 2.4, 06-08-2016
● Same as 2.3 but has a GUI
● Reduced size (425KB)
Version 2.3, 06-04-2016
● Support for latest versions (tested up to 81.0.0.0.49 alpha)
● Reduced size thanks to proguard
Version 2.2, 06-01-2016
● Support for latest versions (tested up to 81.0.0.0.20 alpha)
● Removed aapt without losing backwards compatibility
Version 2.1, 05-30-2016
● Support for latest versions (tested up to 80.0.0.0.44 alpha)
● Much faster patching (dex files are assembled in memory)
Version 2.0, 05-26-2016
● 'New message' function: tap [<-] button on title bar in thread list
Version 1.9, 05-25-2016
● Support for latest versions (tested up to 80.0.0.0.18 alpha)
● Resource name obfuscation resistance
Version 1.8, 05-21-2016
● Bugfixes for latest stable and beta versions
Version 1.7, 05-21-2016
● Support for latest versions (tested up to 79.0.0.0.52 alpha)
Version 1.6, 05-20-2016
● Support for latest versions (tested up to 79.0.0.0.39 alpha)
● Basketball game re-fix
● Much faster and error-free patching
● APK verification
● Reduced size (removed apktool, wrote own manifest hacking routine)
● Improved cleanup method - requires less free space
Version 1.5, 05-07-2016
● Better logging and error handling
● Other Facebook apps can now be installed
● Backwards compatibility down to V59
Version 1.4, 05-04-2016
● Video sending from gallery
● Inline video playback
● Floating hearts
● Linux aapt permission fix
Version 1.3, 05-01-2016
● Easy starter batch file included for Windows users
● Reduced size
● No more separate 'tools' directory, everything is within 'fbpatcher.jar'
● More readable and structured command line output
● Error codes
Version 1.2, 04-30-2016
● Apktool/smali logging
● Safety cleanup on start
● Support for latest versions (tested up to 76.0.0.0.49 alpha)
● Messenger thread list instead of mobile site
● QuickCam video sending
● Basketball game fix
Version 1.1, 04-27-2016
● Support for latest versions (tested with 73.0.0.18.66 stable and 76.0.0.0.19 alpha)
If you like FBPatcher, you can support its development, or simply click Thanks or share this thread on social media sites.

Instructions
To keep all discussion on this thread I'm coping my reply here as well.
How do I do that?
2. Run the patcher: java -jar fbpatcher.jar <input_apk> <output_apk>
Click to expand...
Click to collapse
Here is step by step instructions i followed to get it work on windows ( i think linux users knows how to do this simple things )
this guide was written for earlier version of patcher, but @lorantm is providing much easier automated patcher version now (from v1.3+ ) so just follow OP's USAGE GUIDE
still you can go through my guide for some deeper details and reference it wouldn't hurt and you will learn some history of patcher !
1. you need JAVA installed in PC if not install it from here https://java.com/en/download/
2. Download official (Not patched ) apk of latest stable Facebook(for now v76 here ) or as per recommendation of OP according to patcher version.(USE V75+ TO AVOID THE THREAD LIST SCROLL DOWN BUG! )
3. download patcher by @lorantm from OP
4. extract patcher in fbpatcher folder (use extract to fbpatcher/ )
5. put donloaded FB version form 2nd point in this folder and rename it to fb.apk for ease.
6(new). hold Shift and right click on empty space, then select open command prompt here in empty space of your folder that contains fb.apk & fbpatcher.. now No need to copy cmd.exe at that folder...this method will open your system inbuild cmd so skip directly to Point 9
8. now your folder should look like this
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
9. open cmd.exe and write java -jar fbpatcher.jar fb.apk fbpatched.apk (mind on spaces... see below pic for clarity )
10. wait for 5-10 min and let patcher do its job you will get fbpatched.apk as patched file.
Install & enjoy

Tomi_Ohl said:
Nice guide! Only one thing: I think it would be enough to hold Shift and right click on empty space, then select open command prompt here (in step 6).
@lorantm köszönöm szépen, nagyszerű!! (Thanks, it's awesome!)
Working fine with the suggested FB version on Xiaomi Mi3 with Marshmallow
Waiting for the version with that message icon, right now I can't access groups from app if there are no new messages.
Click to expand...
Click to collapse
that's nice suggestion ! actually i forgot about it while writing guide.

How do you patch the apk on a mac?

Smoking Monkey said:
How do you patch the apk on a mac?
Click to expand...
Click to collapse
I never had a Mac, but I think you should do it just like on Windows or Linux. Install Java, open a command line and run it from there.

So when using patched facebook app, when we click on msg icon, msg interface is loaded in mobile web mode inside the fb app itself. But i am using latest fb app, and latest facebook chat enabler , and it do the same thing. What's the benefit of patching ?
Sent from my MI 3W using XDA-Developers mobile app

a.broken.star said:
So when using patched facebook app, when we click on msg icon, msg interface is loaded in mobile web mode inside the fb app itself. But i am using latest fb app, and latest facebook chat enabler , and it do the same thing. What's the benefit of patching ?
Sent from my MI 3W using XDA-Developers mobile app
Click to expand...
Click to collapse
I replied in the other thread.

lorantm said:
I never had a Mac, but I think you should do it just like on Windows or Linux. Install Java, open a command line and run it from there.
Click to expand...
Click to collapse
I don't think .exe files work on mac, so where would i be able to find the mac .dmg equivalent of the cmd.exe file?

Smoking Monkey said:
I don't think .exe files work on mac, so where would i be able to find the mac .dmg equivalent of the cmd.exe file?
Click to expand...
Click to collapse
It's Terminal. Open it, navigate to the directory (with the cd command) where you have extracted the patcher and the official apk. Then run java -jar fbpatcher.jar FB72.apk FB72P.apk.

Smoking Monkey said:
I don't think .exe files work on mac, so where would i be able to find the mac .dmg equivalent of the cmd.exe file?
Click to expand...
Click to collapse
http://www.wikihow.com/Get-to-the-Command-Line-on-a-Mac
personally even i never used Mac so i don't know how to open it in any specific folder (like windows has Shift+right click in empty space of folder ) but you can try to navigate to your folder via cd/ commands ( try to google it )

For anyone doing this on a mac you open up terminal and type cd /
Then drag the fbpatcher folder into terminal and press enter.
Copy and paste java -jar fbpatcher.jar FB72.apk FB72P.apk then press enter again.

Work perfect thanks

I use the latest version Facebook*73.0.0.18.66 APK and it work perfect thanks
Sent from my LG-H631 using XDA-Developers mobile app

:crying::crying::crying::crying:
guys i have problem.. when i try cmd.exe i get error saying it isnt compatible with my windows..
i searched and to fix i do run command scf/scann something like that and after scan it found conflict but it didnt fix it. :crying:
am very bad at command prompt if i go to accessories and use the comand promt there it works , is there a way for me to do it from there or it must have the cmd.exe in folder.?
if not can osme upload it and share please.. or help fix why cmd says its not compatible.? windows tiny7.

raptorddd said:
:crying::crying::crying::crying:
guys i have problem.. when i try cmd.exe i get error saying it isnt compatible with my windows..
i searched and to fix i do run command scf/scann something like that and after scan it found conflict but it didnt fix it. :crying:
am very bad at command prompt if i go to accessories and use the comand promt there it works , is there a way for me to do it from there or it must have the cmd.exe in folder.?
if not can osme upload it and share please.. or help fix why cmd says its not compatible.? windows tiny7.
Click to expand...
Click to collapse
hold Shift and right click on empty space, then select open command prompt here in empty space of your folder that contains FB.apk & fbpatcher..No need to copy cmd.exe at that folder...this method will open your system inbuild cmd

jineshpatel30 said:
hold Shift and right click on empty space, then select open command prompt here in empty space of your folder that contains FB.apk & fbpatcher..No need to copy cmd.exe at that folder...this method will open your system inbuild cmd
Click to expand...
Click to collapse
thanks it worked :highfive:

Hi, I want to ask, there is no call function on this "messenger"?
and when are you going to release the one with working messenger button?
Thanks!!

Guys Plz Share ur Patched APK file I want to use on Android Lollipop

New version!
V1.1 is out! I successfully patched 73.0.0.18.66 and 76.0.0.0.19 alpha with it and they worked perfectly.
The new version of FBPatcher can be downloaded from the first post, I updated the link.
Explanation: a method in com.facebook.messaging.banner.MuteThreadWarningNotification had to be dummied to make it work.

motfis said:
Hi, I want to ask, there is no call function on this "messenger"?
and when are you going to release the one with working messenger button?
Thanks!!
Click to expand...
Click to collapse
You can't make calls. Facebook removed WebrtcIncallActivity from the manifest and its theme from the resources so even if the voip code is still in there, it's not possible. Also, native library fb-webrtc-jni that is needed to make calls was removed. Earlier I tried to add it from Messenger's apk and hack the code to be able to start a call. It was ringing out, but the conversation could not be started because the in-call UI theme was not present and the app crashed immediately.
I plan to add Messenger thread list feature at the weekend or next week but I already wrote that it will not work on all devices.

Tool to extract Samsung Motion Photos to plain jpg and mp4

First off, I've been browsing here for some time, but I've just registered so I'm sorry if I'm breaking any etiquette or conventions on posting.
I ran across goofwear's tool to extract videos and photos from Samsung Motion Photos and thought it was useful. But I really wanted something that I'd be able to throw a whole album of motion photos at, rather than doing one at a time with this or the share app. I looked at the .bat file they used and implemented the same technique in C, so it could quickly process many photos. It's written with some direct Win32 API calls, so it's pretty much Windows only though making a cross platform command line version without the open dialog would be trivial. It is a simple program though, so it should work fine on Linux or Mac through Wine.
Here's the exe.
See the main page of that Github repository for more complete instructions and full source.
How to use:
1. Copy your Motion Photos off your Samsung phone, to your PC. Just copy them out of the DCIM folder.
2. Run the program. An "open" dialog appears. Apart from that there's no GUI on this program.
3. Browse to your photos and select them. Hold ctrl to select more than one, or shift to select a range. Or, ctrl+A to select all in a folder.
4. Click Open.
5. Wait. Depending how many you selected, it might take a little bit. When it's done, a message box will appear.
6. You should see *_photo.jpg and *_video.mp4 files next to the originals in the source directory. Note that this program does not modify the original files. It doesn't even open them with write permissions enabled.
Alternately, drag one or more photos from Windows Explorer onto the exe's icon instead of using the open dialog.
Screenshots:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Version History:
1.0: Initial release
1.1: Added optional compile-time option to delete the original file after extracting
2.0: Refactored a bit, added a proper build system, and multilanguage support; moved to a 'real' Github repo
2.1: It now preserves timestamps when making the extracted files, and now supports a -r flag to rename the original file instead of appending _photo and _video to the extracted ones.
Andylain has written a Chinese language explanation of the usage of this program, and kindly translated the UI to Chinese (Traditional). To use it in Chinese, either have your Windows set to Chinese language, or rename the exe to put _zh at the end of the name. To use it in English on a Chinese Windows, put _en at the end of the name.
If for some reason you want the old version exe, the old "delete-original" exe, or the old source code, you can still have them.

Can you help to make a version that delete the source after successfully exact?

@Andylain Here's one that deletes the original file after splitting it into photo and video.
Oops -- turns out it was smaller because I forgot to include the icon last time. I've updated the link now and it points at a new build that has an icon.

This is super helpful, Thank you! Oh, there is no beautiful icon in this version.
BTW, I am a Chinese blogger live in Taiwan, I blogged this tool and made a Chinese user guide in my blog "andylain‧blogspot‧com/2017/07/SamsungMotionPictureExtractor.html" .
(Sorry, I am a new user and not allowed to post link.)
If you think that's not a great idea, please tell me and I'll delete my post.

@Andylain Thanks for linking me to your post, and thanks for writing a Chinese explanation for how to use it. I'm happy for people to use my program if they find it useful.
Would a proper Chinese language version of the program be helpful, or are most people there able to read enough English to understand the few error and status messages the program has?

@Andylain Please update your link to the "delete original" version to this one. I forgot to include the icon when building it yesterday.

Chupi383 said:
@Andylain Thanks for linking me to your post, and thanks for writing a Chinese explanation for how to use it. I'm happy for people to use my program if they find it useful.
Would a proper Chinese language version of the program be helpful, or are most people there able to read enough English to understand the few error and status messages the program has?
Click to expand...
Click to collapse
I think it's not hard to understand the status messages
However, a proper Chinese language version of the program would be much more helpful for girls and elderly since Samsung sell a lot of pink S8/S7 for this target.
I really love this app (super helpful for me) and I am happy to translate it , but I don't know how to code BTW. :silly: (just a blogger/photographer)
---------- Post added at 12:55 PM ---------- Previous post was at 12:47 PM ----------
Chupi383 said:
@Andylain Please update your link to the "delete original" version to this one. I forgot to include the icon when building it yesterday.
Click to expand...
Click to collapse
Thank you for the update. I update the link to my blog and facebook fanpage

@Andylain I've extracted all the user-facing strings from my code. The text in [square brackets] are comments giving some context for the message that follows, and don't appear anywhere in the program.
Code:
=====
[this message is shown in a dialog box if you click cancel on the open photos dialog]
You can use this program 3 different ways:
GUI USE: Just run it. You'll get an file-open dialog where you can open .jpg files. Use ctrl or shift or drag to select more than one.
DRAG & DROP USE: Drag one or more motion photos onto the icon for this exe.
COMMAND LINE USE: Run this program with one or more motion photo file names as arguments. Remember to use "quotes" if there are spaces in the names.
Any way you run it, the original files will not be modified. The extracted photo and video will be stored in *_photo.jpg and *_video.mp4 where * is the name of the original file, minus the .jpg extension.
Coded by Chupi383. All credit for the method goes to goofwear at the XDA forums. I've just ported their .bat file to plain C and Win32.
=====
[this is the title of the program]
Samsung Motion Photo Batch Extractor
=====
[this is displayed in the open dialog, under the box where you can type a filename, in a drop-down list]
Motion Photos (*.jpg)
All Files (*.*)
=====
[this is the title bar of the open dialog]
Open some Samsung Motion Photos
=====
[this message is shown if the user selected a file with a really really long name]
Skipping too-long path: <filename goes here>
=====
[title bar for error dialogs]
Error
=====
[error if the user selects over the maximum number of files (currently 10000)]
You've selected too many files. I can only do up to 10000 at a time.
=====
[error if the user selects so many files the Windows "open" dialog box gives up]
You've selected too many files. Try selecting fewer files and process them in bunches.
=====
[appended to names of extracted files - not sure if these should be translated]
_photo
_video
=====
[error if enough memory couldn't be allocated, possibly because the computer is out of RAM]
Can't allocate RAM to read <number> bytes from <filename>
=====
[error if a file can't be read for some reason, perhaps a damaged disk]
Skipping due to read error:
<filename>
=====
[error if an output file can't be written, generally because of full disk, read only disk, file exists and is read only, or permissions on the folder]
Can't write to <filename>
=====
[message on completion]
Finished extracting Motion Photos
Photos extracted: <number>
Videos extracted: <number>
=====
[added to the end of the previous success message if some files didn't contain a photo and a video]
<number> files were skipped because they weren't Motion Photos
=====
[title bar of completion message if at least 1 file was processed successfully]
Success
=====
[title bar of completion message if nothing was done successfully]
Failure
=====
["description" shown in right-click->properties dialog for the exe file]
Extract Samsung Motion Photos to jpg and mp4
=====
["product name" shown in properties dialog for the exe file]
Motion Photo Batch Extractor Utility
If you translate these for me, I'll put them back into my program to make either a Chinese or multi-language version.

Here is the translation of Chinese, sorry for the delay of this reply.
BTW, maybe a dialog for user to choose whether delete original files would be a great idea?
Code:
=====
[this message is shown in a dialog box if you click cancel on the open photos dialog]
有三種方式可以使用本軟體：
一：點開軟體後選擇你要轉存的照片，你可以使用Ctrl或是Shift來多選檔案。
二：把你要的照片拖移到本軟體的icon上也能轉存！
三：你也能使用Command Line來處理喔！ （記得用”quotes”取代空格）
請放心：無論你怎麼做，原始檔案都不會被修改。轉存成功的檔案將會存在原始檔案位置，並新增為 *_photo.jpg 和 *_video.mp4。
GUI軟體由Chupi383撰寫，軟體內核由XDA forums的goofwear撰寫，Andylain翻譯正體中文，詳細中文使用教學請上「安迪連碎碎念」。
=====
[this is the title of the program]
三星動態相片批次轉存工具
=====
[this is displayed in the open dialog, under the box where you can type a filename, in a drop-down list]
動態相片 (*.jpg)
所有檔案 (*.*)
=====
[this is the title bar of the open dialog]
開啟一些動態相片
=====
[this message is shown if the user selected a file with a really really long name]
已忽略太長的路徑：<filename goes here>
=====
[title bar for error dialogs]
發生錯誤
=====
[error if the user selects over the maximum number of files (currently 10000)]
你一次選太多檔案了。我一次只能處理一萬個檔案。
=====
[error if the user selects so many files the Windows "open" dialog box gives up]
你一次選太多檔案了。嘗試選少一點檔案吧！
=====
[appended to names of extracted files - not sure if these should be translated ]
_photo
_video
=====
[error if enough memory couldn't be allocated, possibly because the computer is out of RAM]
記憶體定位錯誤，無法讀取 <number> bytes 上的 <filename> 檔案，有可能電腦的RAM不足。
=====
[error if a file can't be read for some reason, perhaps a damaged disk]
由於讀取錯誤，已跳過處理：
<filename>
=====
[error if an output file can't be written, generally because of full disk, read only disk, file exists and is read only, or permissions on the folder]
無法寫入 <filename> 可能目的地已滿或是為唯讀。
=====
[message on completion]
動態相片轉存結果：
有 <number> 張照片輸出成功！
有 <number> 個影片輸出成功！
=====
[added to the end of the previous success message if some files didn't contain a photo and a video]
<number> 個檔案被跳過了，因為它們不是三星動態相片。
=====
[title bar of completion message if at least 1 file was processed successfully]
轉存成功
=====
[title bar of completion message if nothing was done successfully]
轉存失敗
=====
["description" shown in right-click->properties dialog for the exe file]
批次把三星動態相片轉存成JPG照片和MP4影片！
=====
["product name" shown in properties dialog for the exe file]
動態相片轉存工具
[/CODE]

I'm sorry I'm being slow on this. My work has been especially busy lately. This thread isn't forgotten -- I'll make the translated app once I'm over this hump in workload.

Chupi383 said:
I'm sorry I'm being slow on this. My work has been especially busy lately. This thread isn't forgotten -- I'll make the translated app once I'm over this hump in workload.
Click to expand...
Click to collapse
That is very nice of you to do this!
Take your time and I am willing to help!

@Andylain Thank you for the translation! I've finally got a working bilingual exe -- see the original post. Sorry it took a while.
The "delete original" feature is now built into the main exe. You use the /d command line option to activate it. To make a drag-and-drop icon that will delete the original, right-drag it and create shortcut. Then right click the shortcut, go to properties, shortcut tab, and add a space and /d to the end of the target, after the closing quote.
BTW, if you could, please link people to "https://github.com/joemck/ExtractMotionPhotos/releases/latest" to get the exe -- that's a special link that will always go to the latest version I've posted there.
Coming up, I'd like to add an option to add/remove Explorer context menu integration.

This is absolutely amazing. Thank you so much!!
Chupi383 said:
First off, I've been browsing here for some time, but I've just registered so I'm sorry if I'm breaking any etiquette or conventions on posting.
I ran across goofwear's tool to extract videos and photos from Samsung Motion Photos and thought it was useful. But I really wanted something that I'd be able to throw a whole album of motion photos at, rather than doing one at a time with this or the share app. I looked at the .bat file they used and implemented the same technique in C, so it could quickly process many photos. It's written with some direct Win32 API calls, so it's pretty much Windows only though making a cross platform command line version without the open dialog would be trivial. It is a simple program though, so it should work fine on Linux or Mac through Wine.
Here's the exe.
See the main page of that Github repository for more complete instructions and full source.
How to use:
1. Copy your Motion Photos off your Samsung phone, to your PC. Just copy them out of the DCIM folder.
2. Run the program. An "open" dialog appears. Apart from that there's no GUI on this program.
3. Browse to your photos and select them. Hold ctrl to select more than one, or shift to select a range. Or, ctrl+A to select all in a folder.
4. Click Open.
5. Wait. Depending how many you selected, it might take a little bit. When it's done, a message box will appear.
6. You should see *_photo.jpg and *_video.mp4 files next to the originals in the source directory. Note that this program does not modify the original files. It doesn't even open them with write permissions enabled.
Alternately, drag one or more photos from Windows Explorer onto the exe's icon instead of using the open dialog.
Screenshots:
Version History:
1.0: Initial release
1.1: Added optional compile-time option to delete the original file after extracting
2.0: Refactored a bit, added a proper build system, and multilanguage support; moved to a 'real' Github repo
Andylain has written a Chinese language explanation of the usage of this program, and kindly translated the UI to Chinese (Traditional). To use it in Chinese, either have your Windows set to Chinese language, or rename the exe to put _zh at the end of the name. To use it in English on a Chinese Windows, put _en at the end of the name.
If for some reason you want the old version exe, the old "delete-original" exe, or the old source code, you can still have them.
Click to expand...
Click to collapse

Thanks
Just wanted to add my thanks for this fantastic tool.
I can't quite believe there's no official Samsung Motion Photo viewer (The Windows app doesn't appear to play Motion Photos). And there's practically no 3rd party support around for what you would think would be in high demand.
So I registered on XDA to show my appreciation. Thanks again.

Chupi383 said:
It's written with some direct Win32 API calls, so it's pretty much Windows only though making a cross platform command line version without the open dialog would be trivial. It is a simple program though, so it should work fine on Linux or Mac through Wine.
Click to expand...
Click to collapse
I also wanted to say thanks! That program is a wish-come-true! I wanted to create some script to batch-process JPG's and extract videos but that .exe is even better.
I have just one suggestion. Would you be able to modify program to set video's
Windows date modified
and maybe even date taken (EXIF) attributes
values to correct date, not current date when the extraction takes place?
It would help a lot, because Gallery apps or cloud services like Google Photos shows videos sorted / grouped by the date attribute which is different thandate of photo (when you extract old photos from last couple of months you will have a mess).
For now only way is to use some bulk date changer software to fix that - changing dates based on filename pattern, but it would be a nice feature for your exe. Do you think it's doable?
And yes. I created my XDA account just to say thank you for your great program!

Thanks a lot for this tool, Chupi383!
I'd like to "vote" for konieckropka's suggestion as well. Having the corrent timestamps on the extracted images and videos would be important for a correct file management.
The tool basically needs to read the original "modified timestamp" and set it to the created files (same for "created timestamp").
Could this please be added?

Fair point. I'll add it in a bit when I have the time.

Sorry for the delay, guys. I've added timestamp preservation and a -r flag to rename the original instead of adding _photo and _video. You can use -dr to delete the original and don't append _photo or _video to the extracted files.

This is super helpful, Thank you!

Chupi383 said:
Sorry for the delay, guys. I've added timestamp preservation and a -r flag to rename the original instead of adding _photo and _video. You can use -dr to delete the original and don't append _photo or _video to the extracted files.
Click to expand...
Click to collapse
Works perfectly now! THANKS A LOT!!