Database Info

[KERNEL] [15/04/10][5.1/3G+WIFI][Fix for empty directories after mount] [V18]

Hey Guys,
mkasick released in his thread a fix for the mounting problems in Android >= 4.2.
Description of the issue:
mkasick said:
Android >= 4.2 breaks Dalvik-apps that mount file systems to be shared with other apps. This includes CifsManager, Mount Manager, essentially anything that mounts cifs shares, FUSE file sytems, etc. The symptom is that the mounted contents appear fine to app that peforms the mount operation (assuming the app itself provides the ability to browse the contents), but every other app only sees an empty directory at the mount point.
Click to expand...
Click to collapse
As I said - mkasick released a solution - so I compiled my own kernel. Now we can again easy mount cifs and others! All old apps should work. Only limitation: the mount point needs to be outside of /storage (and also /mnt/sdcard/). Fix for this: Mount within /data/media/0 -- android will redirect the mount so you can access the mounted-files from this folders.
The kernel is a "stock kernel" and also includes:
mkasick Patch
Built-In cifs, md4, utf8, nfs, f2fs (Since V17)
kexec hardboot patch (The full patch, allows boot as host and as guest)
As Modules: .ko: snd-usb-audio and all of its devices (Installed, but not modprobe'd since V17)
[Since V16/Android 5.0.2] Fix for baseband_xmm_power wakelock on tilapia (see Hints and Bugs since V16 / Android 5.0 / Lollipop ; for Android 4.4.4 see this post)
mkasick recommends in his thread to patch dalavik, but for the stock-roms it is easier to patch the kernel.
Known Bugs:
Since Android 5.0.X/V16: SELinux is now blocking the access of cifs/nfs even in read. Also nfs isn't loaded at boot time anymore. For more information look below.
Since Android 4.4.X: There is a known bug with mounting cifs (you can't write). The solution is (try at your own risk) here. If you want to do this workaround at boot-time, you can flash the zip linked here.
With SuperSU >= 1.50 && < 1.65 the mounted folders are empty. Please update! (For more Info see hide-box "SuperSU Information" below)
Hints and Bugs since V16 / Android 5.0 / Lollipop:
SELinux, cifs and nfs
SELinux is since Android 5.0 "more" enforced. Because of that, even the read on nfs / cifs isn't working anymore without disabling selinux by "setenforce permissive" as root. Be careful, disabling selinux is an security hole. USB is still working with selinux at enforcing.
Because of the same reason the nfs and sound modules are not loaded at boot anymore. Because I don't want to mess around with selinux at boot time, you can modprobe them yourself, if you need it. Run the following commands as root to use nfs / sound modules (a installed busybox is required):
Activate sound modules:
Code:
busybox modprobe snd-usb-audio
Activate NFS File System:
Code:
busybox modprobe nfs
Workaround for baseband_xmm_power wakelock
Some people have massive issues with tegra3 + cellular devices with the baseband_xmm_power wakelock. The wakelock drains all the battery. With V16 I included a possible fix for this. The fix is based on the work of jfmcbrayer and Sgt. Meow. By default, the fix isn't active and the kernel uses the stock behaviour.
If you want to disable the wakelock entirely, you can flash this zip: CWM_activate_baseband_xmm_power_wakelock_workaround_vorcers_rev2.zip
I used this this workaround for some time with Android 4.4.4 and I had no issues. Well, I did not test the mobile data... Please tell me, if something isn't working (And the workaround is active). I just wanted to get rid of that battery drain. I was on flight mode all time.
Technical:
The workaround is enabled by echoing a number into a baseband_xmm_power module parameters:
Code:
echo 0 > /sys/module/baseband_xmm_power/parameters/bb_timeout
Possible Values:
< 0 - disable workaround, stock behaviour [Default (-1)]
= 0 - disable the baseband_xmm_power wakelock completely
> 0 - how long the wakelock can stay active, every time the wakelock is triggered, in 10ths of a second. Meaning: Value 5 = 500 ms, 10 = 1 second, 20 = 2 seconds....
You find the patch I used in the actual Patchset. (Included since Android 5.0.2)
Downloads
(Kernels since v8 are only tested by me for the 3G version (tilapia) - but should also work with wifi (grouper).)
The flash of the kernel shouldn't break anything, but I recommend to backup your system.
Download-Links for grouper and tilapia:
Android 5.1: Kernel: Grouper: boot-grouper-vorcers-gf5d7b8b-v18.zip ; Tilapia: boot-tilapia-vorcers-gf5d7b8b-v18.zip
Android 5.0.2: Kernel: Grouper: boot-grouper-vorcers-g6ff7a51-v16.zip ; Tilapia: boot-tilapia-vorcers-g6ff7a51-v16.zip
Android 4.4.4: Kernel: Grouper: boot-grouper-vorcers-g1e42d16-v13.zip ; Tilapia: boot-tilapia-vorcers-g1e42d16-v13.zip
In V11 the kernel modules are placed in /data instead of /system. If you are upgrade from < V11 and you want to delete the modules in /system, you can delete the folder "/system/vorcers_kernelmodules" manually, or you use this CWM-Zip to delete.
Download-Links only for grouper: (try on tilapia at your own risk)
Android 4.3: Kernel: boot-grouper-vorcers-g1e8b3d8-v7.zip Kernelmodules: integrated
Android 4.2.2: Kernel: boot-grouper-vorcers-g05b777c-v4.zip Kernelmodules: kernelmodules-vorcers-g05b777c-v2.zip
Extra-Links:
My Repository for this Kernel (also contains old versions): https://www.mediafire.com/folder/j9iocde4l20c7/Kernel
Stock-Kernels: https://www.mediafire.com/folder/d3mj3k3v61jzu/Stock Kernels
A zip which contains the Patches and modifications I made: https://www.mediafire.com/folder/kvdmcsl16x0ox/Sources
Integration wishes for new kernelmodules to support new hardware are always welcome (you will get .ko's for my kernel)
Have a lot of fun!
Sources:
http://forum.xda-developers.com/showthread.php?t=2106480 (Mount fix)
http://forum.xda-developers.com/showthread.php?t=2104706 (Hardboot patch)
http://source.android.com/source/building-kernels.html
http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack,_Edit,_and_Re-Pack_Boot_Images
http://nek0s.blogspot.de/2012/12/nexus-7-ramdisk.html
Changelog:
Android 5.1: gf5d7b8b-v18 (2015/04/10)
- Switched to gf5d7b8b / android-tegra3-grouper-3.1-lollipop-mr1
- Build-In nfs
- Disabled Module auto loading for snd-usb modules -- are still installed
- Added f2fs Filesystem, untested, standard is ext4
Android 5.0.2: g6ff7a51-v16 (2015/01/31)
- Switched to g1e42d16 / android-tegra3-grouper-3.1-lollipop-release
- Added Workaround for the baseband_xmm_power wakelock on tilapia (Please see "Hints and Bugs since V16 / Android 5.0 / Lollipop" for more information)
- NFS and Sound Modules are not loaded anymore by default but can loaded manual via "busybox modprobe nfs" / "busybox modprobe snd-usb-audio".
Android 4.4.4: g1e42d16-v13 (2014/06/06)
- Switched to g1e42d16 / android-tegra3-grouper-3.1-kitkat-mr2
Android 4.4.3: g4776c68-v12 (2014/06/03)
- Updated Grouper and Tilapia ramdisks for Android 4.4.3.
Android 4.4.2: g4776c68-v11 (2014/01/11)
- To save space in /system, the kernel-modules had been moved from /system/vorcers_kernelmodules to /data/vorcers_kernelmodules.
If you want to delete the modules in /system, you can use this zip: CWM_delete_system_vorcers_kernelmodules.zip
- Nothing else is new
Android 4.4.2: g4776c68-v10 (2013/12/11)
- Updated Kernel Config and Ramdisks. (Both changed in Android 4.4.2/KOT49H)
Android 4.4: g4776c68-v9 (2013/12/10)
- Created separate files for grouper and tilapia (their ramdisk differ, kernel not)
Android 4.4: g4776c68-v8 (2013/12/07)
- Switched to Android 4.4: g4776c68 ; KRT16O (?) ; android-tegra3-grouper-3.1-kitkat-mr1 KRT16S is gee1a0b2 / (?)(?) android-tegra3-grouper-3.1-kitkat-mr0 (?)(?)
Android 4.3: g1e8b3d8-v7 (2013/09/01)
- Modules Support for Android 4.3
- Packed all modules inside zip...
- I go back to the old version scheme and only count up the numbers...
Android 4.3: g1e8b3d8-v6 (2013/07/29)
- Forgot somehow UTF8
- Really added /proc/config.gz
Android 4.3: g1e8b3d8-v5-km-v4 (2013/07/25)
- Switched to Android 4.3: g1e8b3d8 ; jwr66v ; android-tegra3-grouper-3.1-jb-mr2
- This kernel has also: /proc/config.gz and an loadable module support (Stock has not)
- I also provided the patchset I used for Android 4.3
Android 4.2.2: g05b777c-v4-km-v2 (2013/02/19)
v4-Kernel (boot-grouper-vorcers-g05b777c-v4.zip):
- Switched to different version schema: boot-grouper-vorcers-<android-kernel-hash>-v<count of changes of kernel (overall)> ; For the kernelmodules it is: kernelmodules-vorcers-<android-kernel-hash>-v<count of changes of kernel-modules (overall)>. This means for you: if the number is higher, there is something new Version-Number at Changelog: <android-kernel-hash>-v<count of changes of kernel (overall)> -km-v<count of changes of kernel-modules (overall)>
- Added init.d (/system/etc/init.d/) support to the kernel/init.rc. If the directory exists, the scripts inside the directory get run via "run-parts" from busybox. This means: The script need to be runable (+x) and mustn't have an file-extension.
- Removed the mount of /mounts out of init.rc (is now in an script called by init.rc)
v2-Kernelmodules (kernelmodules-vorcers-g05b777c-v2.zip):
- Made a CWM flashable package which autoloads the modules in my kernel.
Android 4.2.1: v3 - boot-grouper-4.2.2-vorcers-v3.zip : (2013/02/15)
- Switched to Android 4.2.2 - Kernel, jdq39, g05b777c, android-tegra3-grouper-3.1-jb-mr1.1
- Added Modules for OTG-USB-Sound (see kernelmodules*.zip)
Android 4.2.0: v2 (2013/01/19)
- I added a tmpfs mount for /mounts, so you don't need to do "mount -o remount rw /" and create your inital-mountpoint yourself. /mounts is writeable by all apps. (done in init.rc)
Android 4.2.0: v1 (2013/01/19)
- inital release
SuperSU Information:
Information for SuperSU Users
It seemed that SuperSU >= 1.50 && < 1.65 doesn't work correctly with this kernel. Well, the Version 1.65 seems to work again (The folders where empty after mount). The SuperSU Version 1.45 worked the best. If you want to use 1.45, you can download the old Flashable-Version here: http://download.chainfire.eu/343/SuperSU/UPDATE-SuperSU-v1.45.zip.
As I said, the version 1.65 seems to work again. It maybe can happen, that the folders gets empty, after some time. This has been noticed with Version 1.60. But 1.65 not (yet).
If you still have problems with the empty folders on my kernel, you should try superuser by koush.
koush's superuser is opensource and is the same as in cyanogenmod. And with that, the mount-technique is working without bugs: https://play.google.com/store/apps/details?id=com.koushikdutta.superuser
Some gimmick: One"click"mount-Shell-Script
Because I want to get rid of stickmount, I written a little shell-script to mount all connected devices. It is very similar to stickmount, but it supports: ext, fat32, ntfs. Well, ntfs only, if you provide the path to an ntfs-3g binary. (In the variable NTFS_BINARY) I used in the script the paragon-ntfs binary. Just install the Paragon-App.
Download V2.2: http://www.mediafire.com/download/rjmsdt06cf0cp6b/oneclickmountv22.sh.gz
Download V3: http://www.mediafire.com/download/xppx2m3awcf3oq3/oneclickmount-v3-20130221172223.tar.gz
glimmling created a tasker apk for this script. I but it still bases on v11 of the script.
from v3 on, ocm needs -m parameter. If you want the old behavior, use "-m auto"
from v3 on, ocm also mounts /dev/block/sdX partitons (e.g. /dev/block/sda), but only if my script can use a busybox with blkid with TYPE output. (I provided one)
I added in v3 an fstab-like future usable with -f <file> see my example.
Please be careful with the new v3. I works, but I would call it "beta"...
You can't run ocm >= v3 inside /mnt/sdcard. All files (except for ocm.fstab and ocm-library) need the x right. Copy the files too /data/local/, "chmod 777 *" them and run ocm from /data/local.
example for ocm.fstab.
syntax:
Code:
<device> <mountpoint> <fs-type> <options>
example:
It is is very importent that the options seperated by one space!
Code:
//192.168.100.1/username username cifs username=<username>,password=password,ro
192.168.100.1:/home/username nfs nfs nolock,ro
/dev/sda1 sda1 ntfs
Thanks to:
mkasick - for the patch
farhanito - for the basic code in the .zip
glimmling - for the tasker apk's running the One"click"mount-Shell-Script
jfmcbrayer / Sgt. Meow - for the baseband_xmm_power wakelock workaround

Hi and thanks for this!
I'm a Linux noob and have some questions.
If I understand it correctly, I don't need Stickmount anymore with your kernel. Do I need to mount an usb stick in the terminal or is there a way to automate this with tasker for example?
What is the correct mount command syntax?
The old way to mount a network share with cifs manager in 4.1.2 I used this guide with external modules:
http://forum.xda-developers.com/showpost.php?p=29055478&postcount=10
Can you please show an example configuration for Cifs Manager, when I use your kernel?
Many thanks!

You still can use stickmount. You will see no difference, because stickmount uses the old "debuggerd" method. (Well, I did not test stickmount with the new fix, but it should work...)
For cifs:
I already included cifs in my kernel. You don't need to load them anymore. You can now easy use cifs manager, if you are mounting under /mounts (with the v2 of my kernel)
Here an screenshot of an configuration I use with CifsManager:
{
"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"
}
It is only important, to use a path in /mounts/. As I tested, CifsManager automatically creates the mount-point inside /mounts/.
It is possible, that applications which doesn't support browsing in file system, can't access /mounts. But some provide an option to the start directory or something like that (OfficeSuite for example) the directory just need to be set to /mounts. This is the reason, why stickmount uses an mountpoint inside /mnt/sdcard ... I am using OI Filemanager. It is a quite nice application. It also supports starting apps with the selected file.
I hope, I could help you.

AW: [KERNEL][WIFI][4.2.X] Included "Fix for empty app-mounted directories"
Thank you.
Cifs is working for me now, but I want to get rid of stickmount.
Since android 4.2.x I always get empty folders with stickmount, even with the latest version. I want to replace it with a new method. But I don't know the mount command and the device name to mount a standard usb-stick.
mount [devicename?] /mounts/usb ???
EDIT: I replaced stickmount with usb otg helper http://forum.xda-developers.com/showthread.php?t=1588940. Now I can see the files of a mounted usb-stick in every app, no more empty folders.
Gesendet von meinem Nexus 7 mit Tapatalk 2

Ah. I forgot USB-OTG helper. Well, with this app, the mounting of devices already worked without the fix. It also uses the "debuggerd" workaround like stickmount. You will need the kernel-fix only for mounting cifs.
I stay at my new oneclickmount-shellscript, because I want to know what the applications do ^^ I don't trust stickmount and usb-otg-helper...

AW: [KERNEL][WIFI][4.2.X] Included "Fix for empty app-mounted directories"
Can you please share your script?
Gesendet von meinem Nexus 7 mit Tapatalk 2

Look in the first post, I attached it there

Re: [KERNEL][WIFI][4.2.X] Included "Fix for empty app-mounted directories"
Thanks vorcers,
Here is flashable zip of v2
http://www.mediafire.com/download.php?gnn4n5p8plhdkv8
Md5= 0394f49ae911ec7a2d7cf845c5916fb6
Hope you can figure out the /storage problem
Every other kernel should implement this fix
Sent from my Nexus 7 using Tapatalk 2

This is a great! Question, since the mount point needs to be outside of /storage and /mnt/sdcard does that mean I can not use this to mount app data? ex. gameloft, etc (using Directory Bind)

It would be really awesome if a fix or hack to this issue (empty directories if app is not launched before mounting) could be found without requiring a kernel patch.
I tried the debuggerd method supposedly used by StickMount and found that it didn't work: app still sees empty mount if its process is started after mount.
Btw, app sees mounts if its process is started before because mounts are propagated in that case. They are just not inherited on process creation due to how zygote spawn app processes and initializes their mounts.
I never understood how hacking debuggerd could work to fix this issue as this is not much different to me than running a shell script invoking adb shell in loopback mode (requires root), since debuggerd and adbd run with identical priviledges:
Code:
setprop service.adb.tcp.port 5555
stop adbd
start adbd
adb connect localhost
adb shell mount ....
I've found a workaround that involves hijaking the obb directory by mounting whatever you want over /mnt/shell/emulated/obb. This directory is systematically bind mounted by the Zygote process in <external storage root>/Android/obb (see source code) when it spawns an app's process
Unfortunately this hack is not very usable because it has the side effect that any app expecting its data in the obb directory will not find it. And you can only mount one filesystem here.
Conclusion: with the new 4.2 multiuser support, Google made miserable all apps dealing with mounting.

Re: [KERNEL][WIFI][4.2.X] Included "Fix for empty app-mounted directories"
I havent tried this kernel yet, but it might appear by simply set the mount point to /data/media/0/MOUNTNAME
Might appear in storage that way.
worked for me using sshfsandroid mounting the pc harddrive over the wifi.
EDIT: I just flashed this kernel and its working the way I said. THANKS A BUNCH.:thumbup:
Sent from my Transformer TF101 using Tapatalk HD

Half-OT: Did someone tested with the new fix the superuser-function in non-primary accounts?
----------------------------------
farhanito said:
Thanks vorcers,
Here is flashable zip of v2
http://www.mediafire.com/download.php?gnn4n5p8plhdkv8
Md5= 0394f49ae911ec7a2d7cf845c5916fb6
Hope you can figure out the /storage problem
Every other kernel should implement this fix
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
Very nice, If you don't object, I would use your zip in the future as base and would only offer .zip's.
Doncabezon said:
This is a great! Question, since the mount point needs to be outside of /storage and /mnt/sdcard does that mean I can not use this to mount app data? ex. gameloft, etc (using Directory Bind)
Click to expand...
Click to collapse
As mkasick said in his patch, also fixing the /storage/ folder, can cause other problems:
mkasick in his patch said:
Unfortunately bind mounts from outside /storage may retain the recursive-shared property (bug?). This means any additional namespace-specific bind mounts (e.g., /storage/emulated/0/Android/obb) will also appear, shared in all namespaces, at their respective source paths (e.g., /mnt/shell/emulated/0/Android/obb), possibly leading to hundreds of /proc/mounts-visible bind mounts. As a workaround, mark /mnt/shell/emulated also as recursive-slave so that subsequent bind mounts are confined to their namespaces.
Click to expand...
Click to collapse
To "fix" the /storage problem, only 6 lines of the patch need to be removed. But it also can break the multiuser-feature. I will test it in the next days.
bubbleguuum said:
It would be really awesome if a fix or hack to this issue (empty directories if app is not launched before mounting) could be found without requiring a kernel patch.
Click to expand...
Click to collapse
As an alternative (which is not really an alternative...) is to use the dalavik patch. But I think the Kernel-Patch is easy for stock.
Anyway, I think there will never be a 100% solution without patching. Only Google can solve this problem, by changing their multiuser architecture... (Or they mark by stock the root folder as non-slave, but that wouldn't fix the /storage problem...)

Re: [KERNEL][WIFI][4.2.X] Included "Fix for empty app-mounted directories"
What if I don't need multiuser support. Don't care much if it becomes broke, since my son has a kindle and my wife dare not touch my tablet save for playing Temple Run Brave
Sent from my Nexus 7 using xda premium

Re: [KERNEL][WIFI][4.2.X] Included "Fix for empty app-mounted directories"
vorcers said:
----------------------------------
Very nice, If you don't object, I would use your zip in the future as base and would only offer .zip's.
Click to expand...
Click to collapse
Of course, no problem
Sent from my Nexus 7 using Tapatalk 2

Thank you so much for that kernel! That is exactly what I have been looking for!

I added .zip's and released a new oneclickmount.sh version. :highfive:

Re: [KERNEL][WIFI][4.2.X] Included "Fix for empty app-mounted directories"
YayYouFixedIt said:
I havent tried this kernel yet, but it might appear by simply set the mount point to /data/media/0/MOUNTNAME
Might appear in storage that way.
worked for me using sshfsandroid mounting the pc harddrive over the wifi.
EDIT: I just flashed this kernel and its working the way I said. THANKS A BUNCH.:thumbup:
Sent from my Transformer TF101 using Tapatalk HD
Click to expand...
Click to collapse
So using this method, directory bind works?
Sent from my Nexus 7 using xda premium

Re: [KERNEL][WIFI][4.2.X] Included "Fix for empty app-mounted directories"
Actually it did seem too. No idea why. Both on the n7 and tf101 for sshfsandroid only.
But eventully I just made it mount to /Removable/pcharddrivefoldermountpointnamelong examplee and that was OK for me too. Ssomone mentioned it can be mounted anywhere outside storageed
EDIT: only using this kernel and I am using dirty aokp2.8 ATM.
I just checked again and the bind works as /data/media/0/PC which wouldnbe good if you want to download directly from dolphin into the PC.

vorcers said:
I added .zip's and released a new oneclickmount.sh version. :highfive:
Click to expand...
Click to collapse
Just wanted to give a HUGE THANKS for compiling your kernel and making it available, to farhanito for the flashable zip, and of course to mkasick for the concept
CIFS Manager works like a charm, and DeaDBeeF Player can see my shares, so me=HAPPY!
Nice to be on 4.2.1 now.
Y'all rule :highfive:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~
I'll just add that Mount Manager also works like a charm, automounting under /mounts whatever shares you define.

I created a new oneclickmount version, with some bug-fixes.
http://forum.xda-developers.com/attachment.php?attachmentid=1690089&d=1359582536
They appeared if you use more then one device at the nexus parallel. It simply only mounted one device.
I also set the standard-mountpoint to /data/media/0/mounts. With that, we can use our files also in /mnt/sdcard. :highfive: (Android re-directs it...)
This also works for bind's. I could bind /mounts/ to /data/media/0/mounts . It also works... Maybe someone helps that for using some games.

[APP][4.0+] Craze - ADB Toolkit

{
"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"
}
DESCRIPTION
Did you ever want to..
.. get pass your friends (or any other persons) lockscreen within seconds?
.. download those photos, videos or files he/she never wanted to show you?
.. edit files and apps from phone-to-phone?
.. access anyones saved WiFi Networks, Access Point login data or Google Token?
Craze is a mobile application based on the Android Debugging Bridge (ADB) to maintain, recover and play around with other android devices.
If you are tired of typing tons of ADB commands into a shell or you are just not familiar with ADB commands - check it out!
It will save you lots of time and pain - trust me.
REQUIREMENTS
SU binary installed
Busybox installed
ADB binary installed
!!! Root access !!!
USB: USB Host Mode / OTG Support (supported by android version 3.1 - 4.x)
WiFi: Requires a "WiFi ADB" app on the target device (available for android versions 2.3.3 - 4.x)
FEATURES
++++++++++++++++++++++++++++++++++
+ Handle multiple devices at the same time
++++++++++++++++++++++++++++++++++
Built-In Remote File Browser
Image Preview
Multi - Upload
Multi - Download
Multi - Copy
Multi - Cut/Move
Multi - Delete
Select All
Unselect All
Built-In File Chooser
Image Preview
Choose files/folder to upload
Choose APKs to install
Built-In Remote Package Browser
3rd party packages
System packages
Multi - Install
Multi - Uninstall
Multi - Backup
Select All
Unselect All
Recover Data [..:: Target needs root access ::..]
WiFi Networks
WiFi Access Point
Google Token
Lockscreen
Bypass
Remove [..:: Target needs root access ::..]
Power Options
Reboot
Recovery
Bootloader
Contact
Email
XDA Developers
About
About Craze
+++++++++++++++++++++++++
+ More features will come soon
+++++++++++++++++++++++++
INSTRUCTIONS
How to connect devices together..
..via USB:
Take your USB OTG Cable (here)
Take a normal USB-to-Micro-USB cable
Plug them together and connect both devices (make sure that the USB OTG cable is plugged into the host device - where Craze is running)
or
Take this MicroUSB-to-MicroUSB-OTG cable from Hak5 (here)
Plug both devices together (the red end of the cable into the host device, the black end into the target device)
..via WiFi (logically you have to be in the same WiFi network):
Install a WiFi ADB app on the target device (any of these)
Start the WiFi ADB app on the target device
Start Craze, press "Connect" in the action bar and enter the targets IP address (you can see it in the WiFi ADB app)
Now you are ready to connect !
NOTE
++++++++
+ First
++++++++++++++++++
+ This app REQUIRES root access on YOUR phone!
+ If you don't have it - go and get it or Craze will immediately close itself.
++++++++++
+ Second
++++++++++++++++++
+ Disable the SU notifications for Craze if you don't want to get spammed.
++++++++
+ Third
++++++++++++++++++
+ It's completely up to you what you are using this app for.
+ I am not responsible for any damage, lost data or unauthorized and illegal use of Craze!
++++++++++++++++++++++++++++++++++++++++++++++++++++++
Mail: [email protected]
PAYPAL
If you want to show me your appreciation for my hard work, I'd love to receive a donation of any amount from you.
..and please rate (and comment) my application in the Play Store if you like it.
KNOWN BUGS
No bugs
Note: Bugs marked as done will be fixed with the next update!
CHANGELOG
v2.2 - 14.11.2013
Removed all ad banner (!)
Added support for Android 4.4
v2.1 - 25.08.2013
A few UI changes
Minor performance enhancements
Fixed a sqlite3 binary bug in "Google Token"
v2.0 - 20.08.2013
Support restricted to Android 4.0 and higher
Massiv UI changes
Slide-In Menu
..and much more!
Multiselect File Browser
Multiselect File Chooser
Multiselect Package Browser
Recover WiFi Access Point
Reboot into bootloader
Contact
Email
XDA Developers
About
v1.8 - 28.05.2013
If you click once on any ad in the app, all ads will be removed until the next start
Minor UI changes
v1.7 - 23.05.2013
Bug fixes
"Connect over Network" bug
Filebrowser folder double click bug
Filebrowser download bug
Filebrowser delete bug
Several source code and performance improvements
Some UI changes
v1.6 - 09.05.2013
Bug fixes
Sometimes the root check was wrong (now it should always be correct)
A filebrowser bug that occured while browsing the sdcard(s)
Minor UI changes (Filebrowser, Package Manager & Filechooser)
v1.5 - 07.05.2013
Bug fixes
Files with blank characters in their names couldn't been deleted with the filebrowser
The sdcard(s) couldn't been browsed with the filechooser for any reason
APKs with blank characters in it couldn't been installed
Minor UI change at the lockscreen removal dialog
Some source code improvements
v1.4 - 06.05.2013
"Google Token Extraction" added
You can extract the google token from the target device and generate an AUTH request to interact with that google account *** target must be rooted ***
Manual "Google Auth Request" added
If you have got a saved token from a previous session you can manually request a new AUTH with that specific token
cURL for android included
Sqlite 3.7.11 included
Minor fixes
v1.3 - 04.05.2013
Bug fixes
Improved adb connection
There should be no more problems with establishing a connection
Minor UI changes
v1.2 - 03.05.2013
Some UI changes
Added "Connect over Network" menu
Only android versions >= 3.1 support USB Host Mode - so I implemented this feature.
You can use my app now with older devices (without USB Host Mode support)
Android versions from 2.3.3 - 3.1 can only connect to other devices over wifi - NO usb (!)
Changed the supported android versions
Now supported: 2.3.3 - 4.x
New screenshots added
v1.1 - 01.05.2013
Minor fixes
New icon
Changed supported android versions
v1.0 - 01.05.2013
First launch
SCREENSHOTS
..for more screenshots visit Craze in the Play Store.

It would be awesome if some of you guys test my app to give me some feedback.

Nice work, I've no WiFi until it's installed on fri and I have no mini usb to mini usb to try, gutted as soon as I can connect the devices I will leave feed back.love the idea tho
Sent from my LT26i using xda premium

v1.2 is here !
Take a look at the changelog.
The app should be available in the play store soon.

I take it both phones need the app to connect to each other? Just had my WiFi installed today, thought it was next week. I quickly checked this app on my dinner with another phone but wouldn't it wouldn't detect the other device. I didn't have time to install the app on the other phone but will do later. Thanks
Edit... Just had the update so when I get home ill check it with the network option
Sent from my LT26i using xda premium

nice

danlivesey said:
I take it both phones need the app to connect to each other? Just had my WiFi installed today, thought it was next week. I quickly checked this app on my dinner with another phone but wouldn't it wouldn't detect the other device. I didn't have time to install the app on the other phone but will do later. Thanks
Edit... Just had the update so when I get home ill check it with the network option
Sent from my LT26i using xda premium
Click to expand...
Click to collapse
No. The app only has to run on the host device, the target device has to have USB Debugging enabled.
Take a look at the instructions (just edited them into the first post):
evo.dev.m1nd said:
INSTRUCTIONS
How to connect devices together..
..via USB:
Take your USB OTG Cable (here)
Take a normal USB-to-Micro-USB cable
Plug them together and connect both devices (make sure that the USB OTG cable is plugged into the host device - where Craze is running)
or
Take this MicroUSB-to-MicroUSB-OTG cable from Hak5 (here)
Plug both devices together (the red end of the cable into the host device, the black end into the target device)
..via WIFI (logically you have to be in the same wifi network):
Install a WIFI ADB app on the target device (any app of these)
Start the WIFI ADB app on the target device
Start Craze, press "Connect over network" in the menu and enter the target device's IP (you can see it in the WIFI ADB app)
Now you are ready to connect !
Click to expand...
Click to collapse

I've tried connecting the target phone with a otg cable and usb/micro usb, but the target phone needs to have WiFi adb but you need to be rooted to turn WiFi adb on and the target phone is not rooted. You say that some of the commands that the app does, does not need to be rooted but how do you use the commands that don't need root if you can't turn On WiFi adb? How do I connect the devices if the the target phone is not rooted?
Host device Xperia s jb stock rooted
Target Xperia j ics stock not rooted
Sent from my LT26i using xda premium

danlivesey said:
I've tried connecting the target phone with a otg cable and usb/micro usb, but the target phone needs to have WiFi adb but you need to be rooted to turn WiFi adb on and the target phone is not rooted. You say that some of the commands that the app does, does not need to be rooted but how do you use the commands that don't need root if you can't turn On WiFi adb? How do I connect the devices if the the target phone is not rooted?
Host device Xperia s jb stock rooted
Target Xperia j ics stock not rooted
Sent from my LT26i using xda premium
Click to expand...
Click to collapse
Yes, for the wifi connection the target device has to be rooted.
But now to your case:
Connect both devices via usb together (the host part of the cable into the Xperia S). Make sure that "USB Debugging" is enabled on the Xperia J. Without USB Debugging enabled, on the target device, it won't work !
Then start Craze on the Xperia S an press "Refresh". A serial number should appear now (the serial number of your target device - Xperia J). Select it and press the connect button.
That should work.

v1.3 is now available in the Play Store - check out the changelog !
[+] Instructions added to the 1st post

r.shakur79 said:
nice
Click to expand...
Click to collapse
Thanks !

very nice , working great

syahazu said:
very nice , working great
Click to expand...
Click to collapse
Awesome - thank you for your reply

evo.dev.m1nd said:
Awesome - thank you for your reply
Click to expand...
Click to collapse
no , i should thanks to you for posting the thread :good:

v1.4 is now available in the Play Store !
Features from the 1st post updated
Check out the changelog !

Update to v1.5 - now available in the Play Store !
Several bug fixes
No more crashes or bugs in the tests
This version is running smooth and stable now
*** Check out the changelog in the 1st post ***
If you face face any problems or bugs feel free the tell me about that. I'll fix them as soon as possible.
..and last but not least, if you like this app please leave a rating in the Play Store.

Dear guys,
I'm traveling through australia for the next 3 months. So there will be no big updates till the end of july.
BUT if you detect any bugs or any other problem - just post it in this thread and I'll do my best to fix it.
Sent from my GT-I9300 using xda app-developers app

thanks, nice work

I recognized that there were two big bugs in the app. I fixed them and the new APK (v1.6) is now available in the Play Store and ready to be downloaded !
For exact information please check out the changelog in the first post.

LeosApps said:
thanks, nice work
Click to expand...
Click to collapse
Thanks !

All About Cherry Mobile Fuze (Q390)

Fuze (Q390) is an Android-powered smart phone sold by Cherry Mobile, a local brand in the Philippines. Fuze is powered by Mediatek MT6582 Quad-Core SoC (@1.3GHz), partnered with a 1GB RAM and is equipped with a 5.0in TN screen/display panel. Its SRP is 5,499 in Philippine Peso (or approximately US$125.00). Physically, it looks the same as the Micromax A96, but they differ internally (at least in the amount of RAM).
For more info, I recommend that you take a look at this in-depth, detailed review of this device (courtesy of [email protected])
Basic Specifications
CPU: Mediatek MT6582 (@1.3GHz) SoC
GPU: Mali 400MP
RAM: 1.0GB
Storage: 4GB (eMMC)
Display: 5.0" (TN panel, DragonTrail surface) @854 x 480 resolution
Camera: 8MP main / 1.3mp secondary
GPS: Yes
Bluetooth: Yes
WiFi: Yes
Sensors: Accelerometer, Proximity, Ambient Light
USB-OTG: Yes
SIM: Dual Standby
Battery: 4000mah

CMFuze Recovery Installer
CMFuze Recovery Installer
This app can be used to install TWRP for Fuze, CWM for Fuze or Fuze Stock Recovery. There's no need to download a separate recovery file. Its all in this app.
NOTES
Your phone needs to be rooted.
INSTRUCTIONS
Download the APK file
Install in your Fuze
Once installed, launch the app "CMFuze Recovery Installer"
Tap the recovery of your choice from the set of buttons
Confirm to Install
Reboot to recovery to test
DOWNLOADS (Kindly not mirror these files somewhere else without my knowledge/permission)
from mediafire
{
"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"
}
THANKS TO
our Creator
TeamWin
ClockWorkMod
Android Open Source Comunity

[ROM] Genesis 1.0
This is simply a debloated stock ROM of CM Fuze
Features
init.d support enabled
zram (compcache) enabled (see compcache/zram at wikipedia)
zipalign on the fly (for newly installed apps)
Seeder (2.0)
Rooted (no SuperSU apk. just get it from PlayStore)
busybox with symlinks
debloated (only essential apps remained)
deodexed
zipaligned
Google boot animation
JB keyboard with swipe
There are no performance tweaks done, as its intention is to become the baseline for ROM porting.
Debloated - removed apps that are optional
removed CM apps and bundled apps
removed CM wallpapers
removed CM tones
removed Google apps that can be downloaded from PlayStore (Map, G+, Calendar, GMail, Notes, Voice Search, etc.)
remained are essential apps, enough to properly run Fuze.
removed faceunlock
removed voice unlock
removed day dreams
removed engineer mode
DOWNLOADS (Kindly not mirror these files somewhere else without my knowledge/permission)
ng0tkul4.CMFuze_GenesisV1.0.zip
INSTALLATION (requires custom recovery: CWM/TWRP)
Backup, backup, backup
Download the zip and flash via custom recovery
(Optional) Factory reset / Data, cache wipe
NOTE: Factory reset is optional, but it may cause bootloop if you didn't do factory reset.
THANKS TO
our Creator
Android Open Source Community
xda-devs

LewaOS v5 for Cherry Mobile Fuze
Flashable via TWRP/CWMR
Ported from official LeWaOSv5 for JIAYU G2F
Should work in all version of Fuze (v4, v5)
Rooted (Lewa is rooted)
Google Playstore included (just download other Google apps from PlayStore if you need them)
No tweaks
No voice unlock/face unlock (removed)
No engineering mode apps (get if from your stock ROM if you need it)
HOW TO INSTALL
Download the flashable zip file (and Google Apps - if you need it)
Install ROM (flash via TWRP/CWMR)
Do factory wipe (cache and data wipe)
DOWNLOADS (Kindly not mirror these files somewhere else without my knowledge/permission)
ng0tkul4.CMFuze_LeWaOS5.1_14.03.28.zip
BUGS
(you tell me...)
TO ENABLE ROOT
- Security Center -> Details -> Permission management -> Perm -> ROOT
THANKS TO
our Creator
Lewa OS5 team/devs (www.lewaos.com)
xda-devs

MIUIV5 for CM Fuze
MIUI V5 for Cherry Mobile Fuze
Flashable via TWRP/CWMR
Ported from Lenovo JIAYU J2F
Should work in all version of Fuze (v4, v5)
Rooted (MIUI is rooted -> Enable in Security App)
Google Playstore included (just download other Google apps from PlayStore if you need them)
No tweaks
No voice unlock/face unlock (removed)
NOTES
MIUI Torch/Flashlight does not work. Just download one from PlayStore like 'Simple Torch'
HOW TO INSTALL
Download the flashable zip file (and Google Apps - if you need it)
Install ROM (flash via TWRP/CWMR)
Do factory wipe (cache and data wipe)
DOWNLOADS (Kindly not mirror these files somewhere else without my knowledge/permission)
ng0tkul4.Fuze.MIUIv5_4.3.21.zip
BUGS
Torch/Flashlight
(you tell me...)
TO ENABLE ROOT
- Security App -> Permission -> Root Permission
THANKS TO
our Creator
MIUI devs (@miui.com)
[email protected] (for his MIUI port for G'Five A800)
[email protected] (for his miui porting guide)
xda-devs

<reserved 5>

thanks sir nice rom can you make not 3 or s4 rom

Nice job sir ... We are waiting for color OS...

colorOS
addictz10 said:
Nice job sir ... We are waiting for color OS...
Click to expand...
Click to collapse
ColorOS --- i'm hesitant to upload because it has few yet ignorable problems. it uses the GB/ICS's /sdcard0/external_sd approach to fetch and enum files... the effect is Oppo Music and Filemanager is failing to get the files (we can use different music player and filemanager). Also OTG storage mounts ok, but there's no easy way to properly unmount it (i.e. unmount via terminal) ... unlike LewaOS that there's an item in its "Storage" settings that can be used to properly/safely unmount the storage.
I will try again after two weeks...

ng0tkul4 said:
ColorOS --- i'm hesitant to upload because it has few yet ignorable problems. it uses the GB/ICS's /sdcard0/external_sd approach to fetch and enum files... the effect is Oppo Music and Filemanager is failing to get the files (we can use different music player and filemanager). Also OTG storage mounts ok, but there's no easy way to properly unmount it (i.e. unmount via terminal) ... unlike LewaOS that there's an item in its "Storage" settings that can be used to properly/safely unmount the storage.
I will try again after two weeks...
Click to expand...
Click to collapse
ok sir... Im still waiting for my fuze...

Just bought a Fuze, and wondering if my unit is defective or it really has issues with the edges of the touch screen. Whenever I use Touchpal X, I have trouble pressing the "a" key. I need to press slightly between "a" and "s" to get it to register.
I have the same issue with some games, when tapping on the very edge of the screen wont register. I have show touches enabled, and it shows the white circle, but the game won't respond at all. Any ideas? I'm running rooted stock rom with gravity box. The only other module i'm using is root cloak for avabel online.
Anyone have similar problems?
EDIT: Found the cause. I had Pie Controls set to 15px so it was eating a lot of screen space for activation. I disabled Pie and it works fine now

How to do screenshot..
Thanks in advance

Elucidator21 said:
How to do screenshot..
Thanks in advance
Click to expand...
Click to collapse
press volume down and power button at the same time..

I need help
I formatted my PC (due to virus) then my Backup for Cherry Mobile Fuze Q390 is lost.
Now my Q390 phone got corrupted and after formatting the phone Baseband is Unknown and IMEI is NULL. I need help by any chance any user with backup that I can use? I cannot write my IMEI because the phone its self has nothing to write on to. Phone is working can boot and etc except the baseband is gone and evidently no IMEI.

phaw16 said:
I formatted my PC (due to virus) then my Backup for Cherry Mobile Fuze Q390 is lost.
Now my Q390 phone got corrupted and after formatting the phone Baseband is Unknown and IMEI is NULL. I need help by any chance any user with backup that I can use? I cannot write my IMEI because the phone its self has nothing to write on to. Phone is working can boot and etc except the baseband is gone and evidently no IMEI.
Click to expand...
Click to collapse
if you can get hold of a NVRAM partition from others phone (not necessarily Q390 - at least same SoC: MT6582), then you can flash it to your phone.
BUT, your phone will have the same IMEI as the source phone. So if you and source phone would use the same SP (Service Provider or network), and IF this SP is strict about cloned IMEIs, they could block this IMEI. Leaving both phones unusable to this network. So if you can get hold of NVRAM partition from somebody living abroad (i.e. foreigner), the better.
if you are rooted, and terminal (adb shell) savvy, you can write it it via dd, i.e.:
$ dd if=/path/of/nvram of=/dev/nvram
or you can flash it via SPFT memory write ("Window" menu -> "Write Memory").
1) Select "Write Memory" tab (after it is shown)
2) Select "EMMC" for the memory setting
3) Select/browse ("Open Raw Data") the NVRAM image for the "File Path"
4) "Begin Address (Hex)" = 0x1800000
5) "Container Length (Hex)" = 0x500000
6) Click "Write Memory"
7) Connect your phone to PC (must be turned off as you may already know)
The NVRAM image could be named as nvram.bin or something else. But it must be a raw image of NVRAM partition (/dev/nvram) from other phone. TWRP can do a backup of this partition by selecting it when you are about to perform TWRP backup.
If you want to temporarily restore your IMEI, you can try MTKDroidTools or Mobile Uncle Tools (apk)

LeWaOSV5.1 for CMFuze
- apps that show as 0.00kb in "All" and "Downloaded" are now shown ok
- added engineering mode to settings
- corrected some misspeling in english translation
- etc.

ng0tkul4 said:
if you can get hold of a NVRAM partition from others phone (not necessarily Q390 - at least same SoC: MT6582), then you can flash it to your phone.
BUT, your phone will have the same IMEI as the source phone. So if you and source phone would use the same SP (Service Provider or network), and IF this SP is strict about cloned IMEIs, they could block this IMEI. Leaving both phones unusable to this network. So if you can get hold of NVRAM partition from somebody living abroad (i.e. foreigner), the better.
if you are rooted, and terminal (adb shell) savvy, you can write it it via dd, i.e.:
$ dd if=/path/of/nvram of=/dev/nvram
or you can flash it via SPFT memory write ("Window" menu -> "Write Memory").
1) Select "Write Memory" tab (after it is shown)
2) Select "EMMC" for the memory setting
3) Select/browse ("Open Raw Data") the NVRAM image for the "File Path"
4) "Begin Address (Hex)" = 0x1800000
5) "Container Length (Hex)" = 0x500000
6) Click "Write Memory"
7) Connect your phone to PC (must be turned off as you may already know)
The NVRAM image could be named as nvram.bin or something else. But it must be a raw image of NVRAM partition (/dev/nvram) from other phone. TWRP can do a backup of this partition by selecting it when you are about to perform TWRP backup.
If you want to temporarily restore your IMEI, you can try MTKDroidTools or Mobile Uncle Tools (apk)
Click to expand...
Click to collapse
under NVRAM folder. It has nothing. Literally nothing inside the nvram folder.

phaw16 said:
under NVRAM folder. It has nothing. Literally nothing inside the nvram folder.
Click to expand...
Click to collapse
correct.
there's shouldn't be anything there...as it is not supposed to be a folder. for one, dd will not work in folder, so i really expect /dev/nvram to be not a folder, rather than a device file pointing to NVRAM partition (offset 0x1800000) of your Fuze's EMMC.
if you see /dev/nvram as a folder/directory (rather than a device file), then something's gone really wrong in your EMMC partitions.

Grawrz said:
Just bought a Fuze, and wondering if my unit is defective or it really has issues with the edges of the touch screen. Whenever I use Touchpal X, I have trouble pressing the "a" key. I need to press slightly between "a" and "s" to get it to register.
I have the same issue with some games, when tapping on the very edge of the screen wont register. I have show touches enabled, and it shows the white circle, but the game won't respond at all. Any ideas? I'm running rooted stock rom with gravity box. The only other module i'm using is root cloak for avabel online.
Anyone have similar problems?
EDIT: Found the cause. I had Pie Controls set to 15px so it was eating a lot of screen space for activation. I disabled Pie and it works fine now
Click to expand...
Click to collapse
Sir the multi touch for Fuze works well your device is not defective. You can't do multi touch if you press already on the left part for me it doesnt really makes sense why'd do that. Example you press arrow up button then you want to press A should you still use your right thumb well in fact the left thumb is already near it furthermore it doesnt affect when your playing games. Its just whenever your using the keyboard.
ng0tkul4 said:
correct.
there's shouldn't be anything there...as it is not supposed to be a folder. for one, dd will not work in folder, so i really expect /dev/nvram to be not a folder, rather than a device file pointing to NVRAM partition (offset 0x1800000) of your Fuze's EMMC.
if you see /dev/nvram as a folder/directory (rather than a device file), then something's gone really wrong in your EMMC partitions.
Click to expand...
Click to collapse
As I mentioned on my post. I factory formatted the partition. Well I sent back the device to Cherry Mobile so that they can repair it.I just have to wait for 1 month.

Sir, how can i install xposed installer properly? I'm getting bootlooped both in MIUI and LEWA rom. I really need this for greenify. Thank you in advance.
Sent from my Q390 using Tapatalk

LetsGoApp(App follow Me)

Google Play Store：
https://play.google.com/store/apps/details?id=tseng.lets.go.app
User guide
http://www.letsgoapp.net/?cat=15
Description:
App follow Me
After replace Android device, the Apps can still be run at MicroSD or OTG by LetsGoApp.
LetsGoApp is a App, which is a kind of solution for storage shortage and backup data.
Apps can be run by LetsGoApp within the MicroSD or OTG on the most of Android devices .
Support Android 4.1.X~4.3
HTC bufferfly、SONY Z 、ZL、MI 2X/3X、IAOMI – Redmi、 Sumsung S2/S3/S4/Note2
Support Android 4.4 , and it need fixed SD card write/read permissive
Contents.
（1）Foreword.（2）What should I prepare？
Step 1：Creating ＆ Formatting the storage device – MicroSD and OTG.
Step 2：Rooting Android Device.
Step 2a：Step 2a：Fix Android 4.4 SD card write/read permissive
Step 3：Installing the Applications – BusyBox、USB OTG Helper and Link2SD.
（3）Operating Instruction for LetsGoApp.
Step 1：About User Interface.
Step 2：How to use LetsGoApp with the storage device – MicroSD and OTG？
（4）To Unlink the App’s link from storage device.（5）About LetsGoApp.（6）Q & A.
（1）Foreword.
LetsGoApp can execute all the other Apps on OTG and MicroSD(not install). Therefore, it can effectively solve the problem of the shortage of ROM of the portable device and to easy backup your Apps.
The LetsGoApp is an application aimed at solving the shortage of ROM’s applications for portable device. It often happens when a portable storage device has been installed a large number of applications in it.
Because the manufacturer’s limit, Android’s users frequently may meet the following problem：The ROM is not enough！ There are 3 ways to fix this issue :
First, pay extra money to buy a better Smart Phone for more ROM.
Second, remove unwanted data or Apps to release more space.
Third, synchronize data with the computer .
There is a better way , LetsGoApp has solution of ROM at portable devices.
NOTE：According to user choices, there are different Third-Party Apps for mounting the OTG and MicroSD.
The User Guide will be elaborated.
（2）What should I prepare？
Preparing a MicroSD or OTG device, you must to create 2 partitions（1st-FAT32、2nd-EXT3） and formating it by EaseUS Partition Master. The partition steps for both MicroSD and OTG are the same.
Step 1：Creating ＆ Formatting patition.
（A）. Installing EaseUS Partition Master for Windows.
Download by： http://www.partition-tool.com/download.htm
（B）. Right-click on the OTG, and choose “Create partition”.
{
"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"
}
（C）. Setting size 3 ~ 5 GB or more for FAT32 as 1st-partition, and Create as “Primary”.
（D）. Setting EXT3 partition for over space, and Create as “Primary”.
（E）. Right-click on the EXT3 and choose “Set active” ,then “Apply” it.
（F）. Removing the OTG device after the work is finished.
Step 2：Rooting Android.
Each portable device has different ways to Rooting Android device. Please google, and then rooting your portable device.
HTC’s device need S-OFF. Samsung S4 use OTG for Android 4.3↑, You need close KNOX .
Android 4.4 need fixed SD card write/read permissive
Step 3：Installing the Applications – BusyBox、USB OTG Helper and Link2SD.
First of all, you have to installing BusyBox for Android by “Play Store”. User can choose USB OTG Helper or Link2SD to mount the OTG or MicroSD. We recommend to installed both.
(A）BusyBox：
Touching “Install” , then “Smart Install”.
（B）USB OTG Helper (If you use OTG)
Please download by http://www.letsgoapp.net/?p=241 , then installing USB OTG Helper and mounting with the OTG device. There will be a notice of 2 drives mounted to complete. If it is not. As long as reboot Android Device, and repeat the above steps.
Remind！You must to downloading USB OTG Helper by our provided！
（C）Link2SD (If you use MicroSD)
Selecting the sector format-EXT3 of your MicroSD’s second partition, then Reboot device.
（3）Operating Instructions for LetsGoApp.
This chapter will be explanation run all the other Apps on OTG or MicroSD.
NOTE：Make sure created and format 2 partitions(1st-FAT32、2nd-EXT3) within MicroSD or OTG .
Step 1：About User Interface.
There are four UI controls ：Switching the storage device of target by 1.Main＆2.Vice-Spinner. Showing 3.Menu by menu button. Finally, all of the above steps results will be presented on the 4.App list.
Step 2：How to use LetsGoApp with the storage device – MicroSD or OTG？
（The operating steps for both MicroSD and OTG are the same, this example is for OTG.）
（A）Touching the option “Phone ROM” of Vice-Spinner to show the App’s menu list, and you can choose the target to moving .（For example：Candy Crush Saga）
（B）After finished, you can touch the option “OTG” of Spinner, and select “Remove” for Candy Crush Saga.
Remind！This is removing the App from the Phone ROM, not OTG.
（C）Pressing Candy Crush Saga again, and “Install” it.
Remind！This step is linking App to Android Device, not copy App to phone ROM.
（D）Touch the button “Cancel” to retune to step(A), to move the other Apps if you have needs. After all of the moving work is finished, and then touching the option “Quick Reboot” to rebooting by Menu button.
（E）After rebooting, (Fig.1、2) the application “Candy Crush Sage” can be run by LetsGoApp and Android Desktop. Conversely, (Fig.3) when the OTG device is not mounted, there is only unlinked icon to show within Android Application Manager.
（4）To Unlink the App’s link from MicroSD or OTG.
Actually, maybe there are many storage devices, and then sometimes must to be replace. Therefor, the replacement behavior perhaps cause the application update fails or recognition errors.
（The operating steps for both MicroSD and OTG are the same, please follow example steps for OTG.）
（A）Pressing Menu button to show the menu list, and then release link from storage device.
（B）Pressing the option “OK" will unlink for APK.
（5）About LetsGoApp.
Version：4.020814
Update date：02. August. 2014
Release date：01. July. 2014
Content Rating：All
Support Android V 4.1.x ~V 4.3 with：SAMSUNG – S2/S3/S4 / Note 2、HTC – Butterfly、
SONY – Z / ZL、XIAOMI – Redmi / Mi 2/3
Technical support to visit LetsGoApp official web http://letsgoapp.net ,
or contact by E-mail：[email protected]
（6）Q & A.
Q：What the Android’s version has supported, and portable device brand can be supported by LetsGoApp?
A：For now, LetsGoApp stable supported for Android v4.1.x ~ 4.3, and continuing to support for all class.
Q：What is internal ROM and portable storage device？
A：The ROM is an storage capacity within portable device, that has limited by Manufacturer’s specifications. The portable storage device is MicroSD and USB On-The-Go.
Q：Before run LetsGoApp, should I have to install the Third-Party application first？
A：Exactly, and must to downloading USB OTG Helper from LetsGoApp official web.
Q：How to Rooting for portable device？
A：Please go website and google to see how to rooting your own portable device.
HTC’s device need S-OFF. Samsung S4 use OTG for Android 4.3↑, You need close KNOX .
Android 4.4 need fixed SD card write/read permissive
Q：About MicroSD and OTG’s specifications, whether there is limited？
A：User can choose capacity and brand, but recommendation for the brand withMicroSD is SanDisk.
Q：The OTG’s temperature is always high. Is this is correct？
A：Yes. It’s useable.
Q：No the other methods to solve?
A：Actually, there is suggestion for this problem. You can use SanDisk’s MicroSD for storage device.
Q：How to solve of USB OTG Helper to mounting with only one drive？
A：You can check busyBox install has completed. The other way, you can press “mount" twice or let the portable device reboot, and try again.
Q：Can I hold the portable storage device use for mobile phone for more than one？
A：Yes. This is the concept of LetsGoApp.
Q：How can I plan the space of partitions？Can I still storing private data into the partition FAT32?
A：YES. For example：Photos、Videos、or be Storage Disk to use for PC, and then storing for all of your private data. As for partition-EXT3, it is to store for applications. Anyway, space size with personal preferences.
Q：Can I still update within portable device from Google Play Store？
A：Yes. But the portable storage need has been mount.
Q：Reading a lot of above for user guide, I confused still. What is the point of LetsGoApp？
A：In fact, every day we have to face a lot of data. These including photos、videos、music and the increasingly entertainment features of Apps. What the better solve method is a important problem, wherein is LetGoApp lets you develop a personalized storage device, and then run with it, that just like as a portable Cloud.
Q：About “LetsGoApp", it is look like as Link2SD.
A：Yes, but not almost for all. For example with MicroSD：The program only run App by Link2SD from the single portable device. If there are more than one with mobile phone, that is not allowed to share of the applications with each other. But now, LetsGoApp was already to solve this problem.
Updated Info：
02/08/2014 ver 4.020814
1. unlock most 5 Apps restrictions.
2. language fix.
3. add “About Us" info.
4. bug minor fixes
5. supported Android 4.3 or later (must to close Application-KNOX)
Download
LetsGoApp APK v4.020814
Google Play Store：
https://play.google.com/store/apps/details?id=tseng.lets.go.app
MEGA：
https://mega.co.nz/#!odYlRKRQ!DDjk_7ChjgszwnPvJxpYbN0bffeVuREQaEg4_pmbnAU
MediaFire：
http://www.mediafire.com/download/1xq7j117033mtqv/LetsGoAppv4.020814.apk
Google Drive：
https://drive.google.com/file/d/0Bx-q46LRtv6QRXlBTlI1TjgySWc/edit?usp=sharing
Firedrive：
https://www.firedrive.com/file/34E01D2277BEFE2
Baidu：
http://as.baidu.com/a/item?docid=6808010
USB OTG Helper APK
MEGA：
https://mega.co.nz/#!8VghSDqL!oWraUGWUv8K-kEnUk2qoxEikQ4g2rC9t7Mg4uwlBrsA
MediaFire：
http://www.mediafire.com/download/1z7d114q4kwkamt/USB_OTG_Helper-SignFile.apkGoogle Drive：
https://drive.google.com/file/d/0Bx-q46LRtv6Qck9tSFY2ekxrbUU/edit?usp=sharingFiredrive：
http://www.firedrive.com/file/494F2C92170269BE
Manual
MEGA：
https://mega.co.nz/#!RURmxYIa!qcScIJJiWqs-R5cDCo3rI06uQSdgXqNbXEEswZW3AtU
MediaFire：
http://www.mediafire.com/view/xor06hf219a7voi/User_Guide_EN.pdf
Google Drive：
https://drive.google.com/file/d/0Bx-q46LRtv6Qd1FONi1jVmRDOEU/edit?usp=sharing
Firedrive：
https://www.firedrive.com/file/D6400AE7314C0E91

it looks good. I just installed, hope it work like it's described.

It's amazing !
This solves the problem of my internal storage space, and I found that all can share App to pay for my friends directly through MicroSD and OTG.
I love it.......

Duglaj said:
It's amazing !
This solves the problem of my internal storage space, and I found that all can share App to pay for my friends directly through MicroSD and OTG.
I love it.......
Click to expand...
Click to collapse
thank you
and get this app to you friend

woff said:
thank you
and get this app to you friend
Click to expand...
Click to collapse
of course!:good:

Really amazing,
I have two phones, I try to move APP from one to another,
and two phones are different gmail,
then successful and can operate APP.

windwater08 said:
Really amazing,
I have two phones, I try to move APP from one to another,
and two phones are different gmail,
then successful and can operate APP.
Click to expand...
Click to collapse
thank you,The letsgoapp is very convertion

windwater08 said:
it looks good. I just installed, hope it work like it's described.
Click to expand...
Click to collapse
you will like it

I use LetsGoApp,It is so easy to mve app to otg and sd
I use to backup app and move to the other smart phone so easy
this is so news idea,thanks

It look like to link2SD
LetsGoApp more better than Link2SD
because LetsGoApp can change smart phone by SD or OTG and run APP
LetsGoApp backup so easy and save ROM
LetsGoApp can 100% move App to SD or OTG
thank you LetsGoApp

I have installed busybox on xiaomi mi3 Indian version
I have created two partition as well ext3 and fat32
I get an error on OTG helper

stucked in otg helper.....
in usb otg helper app , it shows no drives mounted, i rebooted,downloded from ur source, but showing same.....
pls help asap...................

This stupidity has gone on for long enough.
All of your threads are being spammed by your multiple accounts, giving bogus feedback.
THREAD CLOSED!

[APP][ROOT] USB MASS STORAGE Enabler v1.6

This app is to enable Mass Storage Mode for mounting your Memory Card as a USB Drive in Computer from your rooted device [Android 4.0+]..
It does not mount internal storage, and it will not work if your device doesn't have External Memory Card Support..
Download Link:
UMS Enabler (Universal) v1.6.2.apk
(can also be downloaded from XDA Labs)
(click here for older versions of app)
Steps to Enable UMS:
1. Connect phone using USB cable to Computer or TV or DVD/Audio Player or Mac (or even to other phone with OTG) or whatever.
2. Open the 'UMS Enabler' app and press 'Enable Mass Storage' and give it root access.
(Try 2-3 times if it doesn't work the first time itself)
3. Before disconnecting USB, eject from Computer and then press 'Disconnect Mass Storage' in app.
If it doesn't work, go to App Settings and choose the required settings, and try again.
Avoid using memory card from phone when in UMS mode..
Screenshot:
View attachment 3935226
Note:
This will work only if there is USB Gadget support in your kernel..
It is recommended to unmount the memory card from Settings->Storage before enabling UMS, to avoid issues.
(Not required if you don't make changes in memory card from computer, that is, if you're just using for read-only purpose.)
And remount similarly after use. (required only if /dev/block/mmcblk1 is used, instead of the particular memory card partition mmcblk1p*)
Testers, please try and reply.
If it works, please leave a reply with your device model & ROM (and custom kernel if any) in which it's working so that I can make a list of working devices.
Hit the Thanks:good: button if it worked for you..
Contributors
@GokulNC
@vikasb32 (Material Design)
@maais (Russian Localization)
@WormsWarII (French Localization)
Version Information
Status: Stable
Latest Version: 1.6.2
Last Release Date: 2017-02-26
Created 2015-11-03
Last Updated 2017-02-26
Source Code: https://github.com/GokulNC/USB_Mass_Storage_Enabler
(Feel free to contribute)

Device Compatibility List
(Only the devices with external memory card support are listed)
Working on Devices:
Alcatel One Touch Pixi3
Asus Zenfone 2
Asus Zenfone 6
BQ Aquaris M4.5
Cherry Mobile One
Dell Venue 7
Doogee X5 Pro
Evercoss One X
Gionee S plus
Honor 5X
HTC 10
HTC One M8
Huawei Ascend Mate 2
Huawei Honor 4x
Huawei Honor 6
Huawei Honor 7
Huawei Mate 7
Huawei Mate 8
Huawei P8 & Lite
Huawei P8 Max
Huawei P9 Lite
Karbonn Sparkle V (tested by @out386)
Lenovo A5000
Lenovo A7000
LG G2
LG G3
LG G4
LG G Pro 2
LG L70
LG L90
LG Spirit
Micromax Canvas A1 (tested by @out386)
Mito Impact
Moto E
Moto G
Moto G3
Moto G4
MyPhone Uno
Nexian Journey One
Oneplus X
QMobile A1
Samsung Galaxy Grand Prime SM-G530FZ
Samsung Galaxy J1 Ace
Samsung Galaxy Note 2
Samsung Galaxy Note 3 HLTE
Samsung Galaxy Note 4
Samsung Galaxy S2
Samsung Galaxy S3
Samsung Galaxy S3 i9300
Samsung Galaxy S3 Mini
Samsung Galaxy S4 i9505 & i9500 3G & i9515 LTE & i9502
Samsung Galaxy S4 Mini LTE
Samsung Galaxy S4 Mini Duos
Samsung Galaxy S5, KLTE, G900T, G900F
Samsung Galaxy S7
Samsung Galaxy S7 Edge
Samsung Galaxy Tab Pro 10.1
Sony Xperia L
Sony Xperia Z
Spice Dream Uno (tested by @out386)
Symphony Roar A50
Umi Rome
Wiko Highway Star 4G
Wiko WAX
Wildfire Buzz
Wileyfox Swift
Xiaomi Mi 4S
Xiaomi Mi Max
Xiaomi Redmi 1S
Xiaomi Redmi 2
Xiaomi Redmi 3
Xiaomi Redmi 3S Pro
Xiaomi Redmi 4
Xiaomi Redmi 4 Prime
Xiaomi Redmi Note 2
Xiaomi Redmi Note 3
Redmi Note 3 Pro
Xiaomi Redmi Note 4
Yu Yuphoria (tested by me)
Yu Yureka
Yu Yureka Plus
Yu Yunique
ZTE Nubia N1
Warning For These Devices Below:
HTC One M9

Changelogs :
To Do in Future:
* Reduce app size
* Automatically start app when USB is connected
* Create Notification when UMS is enabled, to unmount it easily.
* Force Mediascan after Unmount
* Add Dark Theme
* Enable ISO image mounting by selecting a compatible image.
* Find a way to enable ADB alone (in insecure mode)
* Switch completely to my RootShell class from Stericson's RootTools
Click here for latest changelogs: https://github.com/GokulNC/USB_Mass_Storage_Enabler/blob/master/Changelog.txt
v1.5.1 (25-Aug-2016):
-- Added Notification when UMS is enabled to unmount easily.
--fixed this bug in Advanced Settings
-- Removed the AsyncTask which caused high CPU utilization (to get USB Connection Status). Will use a BroadcastReceiver for that in the next Version.
v1.5.0 (21-Aug-2016):
-- Updated to Material Design by @vikasb32
(No changes other than UI)
* Report bugs if any
v1.4:
-- No need to manually unmount memory card (only required if memory card device block (/dev/block/mmcblk1) is directly used, instead of the particular partition mmcblk1p*)
-- Added Advanced Settings (in options) to choose the LUNs and partitions blocks manually from an automatically optimized searched list..
If you're choosing mmcblk1p1, you no need to unmount/remount from Storage Settings.
If you're using mmcblk1, unmount is required.
(Similarly for vold blocks, choose the right one.
For example in my phone, if there are 179:64 and 179:65 in /dev/block/vold/ , 179:64 refers to mmcblk1 and 179:65 refers to mmcblk1p1 )
v1.3:
-- App now automatically checks for External SD Card and presence of FUSE drivers.
-- Partial fix for devices in which it appears as CD Drive in Computer.
-- Properly Handled Exceptions and added Warning messages
v1.2:
--Optimized Code to remove stupid hackarounds & Fixed Bugs
--Added 'Help' page
--Used ProGuard (app size reduced to 34KB)
v1.1:
-- App now automatically disables SE Linux Enforcement thanks to @out386's idea
-- Added option to unmount Mass Storage
-- Changed the background to black
F.A.Q. :
1. "There's no drive for Internal Storage, only the memory card is there."
Solution: This app does not mount internal storage as UMS due to certain restrictions.
(The Internal Storage is actually present inside the /data partition which is formatted as EXT4/F2FS.)
This app can mount only the memory card. (You can try the USB Sharer app (link at bottom) for that purpose.)
2. An empty Removable USB Disk appears, upon clicking which appears "Please insert disk".
Solution:
Go to Advanced Settings and try using some other device block if any..
Also, make sure memory card is
a. inserted & formatted in recognizable file system format like FAT32, vFAT or exFAT.
b. not encrypted / adopted as Internal Storage (Since Android 6.0 Marshmallow, by which it's formatted as an EXT4 partition and encrypted).
3. It shows up as a CD-ROM or DVD (Optical) drive instead of USB (flash) drive, upon clicking which appears "Please Insert Disk / No Disk Inserted".
FrozenCow said:
The kernel needs support for this. Most stock kernels only have USB-emulation, some stock kernels only have CD-emulation. None of the stock kernels have the ability to switch between the two, that's why a custom kernel is needed. A number of CyanogenMod kernels have support for this.............
Click to expand...
Click to collapse
4. "It's working, but the drive is mounted as read-only."
(This issue was reported for Asus Zenfone 2)
Solution: Actually, one of the main purpose why this app needs to disable SE Linux is to remove the write-access restriction on memory card.
There might be occasions when even after setting SE Linux to Permissive, the memory card is mounted as read-only drive. In that case, follow these steps:
i. Unmount the memory card from the Storage Settings.
ii. Now 'Enable UMS' and see if you have write-access.
iii. After disconnecting USB, remount/mount the memory card again from Storage Settings.
5. App Force Close: "Unfortunately, app has stopped".
Please send the logcat.
6. "I've tried everything possible & I'm helpless" :
Solution: You can also try this if there's TWRP recovery for your device:
i. Boot into TWRP recovery & connect to USB.
ii. Select the option 'Mount'
iii. Click 'Mount USB Storage' (or something similar).
If that didn't help, you can also try the similar apps below:
Alternate Apps :
If this app doesn't work, there are several other alternative apps (by other developers) you can try:
(Might require SE Linux Mode set to 'Permissive')
1. Multi Mount SD-Card ( Lite | Pro )
2. USB Sharer ( Free | Full )
3. SD Card as USB Drive ( Free )
4. DriveDroid ( Free | Paid )
(Only to mount ISO/IMG files to PC using UMS)
Click to expand...
Click to collapse
Libraries Used :
1. RootTools by Stericson
2. Material Drawer by Mike Penz
3. NoNonsense-FilePicker
4. Firebase

Works perfectly on my LG L90. I don't have to deal with this stupid MTP anymore. CyanogenMod 11.

From my understanding this will work only if you have external sdcard storage.. ?

Working on my S3 Mini (CM12 ROM by Maclaw) with hard method.
Need some options (like unmount UMS/MTP),but finally I can use UMS on my device!
Thanks!

How is this different than the xposed module "HandleExternalStorage" which enables writing to the external SD card?

phone reboot immediately hit soft mode & empty (0bytes) partition on hard mode
onePlus One, 5.1.1 flexOS

OT-Xtreme said:
From my understanding this will work only if you have external sdcard storage.. ?
Click to expand...
Click to collapse
Yes, this will mount external sd storage only..
Internal storage is actually EXT4 format and is present in /data/media
GFOLDISCOOL said:
Need some options (like unmount UMS/MTP)
Click to expand...
Click to collapse
There's an option(button) for MTP.. You can use that.
I will add an option to 'Unmount UMS' soon
Spookymyo said:
How is this different than the xposed module "HandleExternalStorage" which enables writing to the external SD card?
Click to expand...
Click to collapse
That module enables read/write operation on memory card for all apps by editing /system/etc/permissions/platform.xml (I think so).
But this app is for enabling USB Mass Storage to mount memory card to computer directly like a flash drive..
mrhamed said:
phone reboot immediately hit soft mode & empty (0bytes) partition on hard mode
onePlus One, 5.1.1 flexOS
Click to expand...
Click to collapse
This works only if there's memory card in your device.
One Plus One doesn't have external memory support I think.

Thanks mate this is awesome its working on cm13.0 no need to download selinux enabler because its already on permisive

Version 1.1 added
-- App now automatically disables SE Linux Enforcement thanks to @out386
-- Added option to unmount Mass Storage
-- Changed the background to black

Thank you so much, this app works great on my LG L90 Official kitkat :good:

It perfectly works for me on my Galaxy Note 4 (N910F) on Emotion Rom R2.1 (Note 5 port) even with soft method
My only problem is neither my A/V system and my TV cannot recognise it and this would be my main need of this :/ Any solutions?

vegh_mark97 said:
It perfectly works for me on my Galaxy Note 4 (N910F) on Emotion Rom R2.1 (Note 5 port) even with soft method
My only problem is neither my A/V system and my TV cannot recognise it and this would be my main need of this :/ Any solutions?
Click to expand...
Click to collapse
If it's working in computer, then it should work everywhere..
Maybe wait for a minute or 2 after connecting to TV see if it detects.
Try both soft and hard method..
Also, trying in some other ROM might help.. (Not sure though)

GokulNC said:
If it's working in computer, then it should work everywhere..
Maybe wait for a minute or 2 after connecting to TV see if it detects.
Try both soft and hard method..
Also, trying in some other ROM might help.. (Not sure though)
Click to expand...
Click to collapse
I thought that too.. But either my TV and my A/V system recognises flash drives immideately :/ I tried another TV (a smart one) and this one wrote some failure messages with it :/ Thanks though I hope it will work in the near future somehow.

Works well on LG G2 Lollipop
Thanks

GokulNC said:
This app is for mounting your External SD (Memory Card) in Mass Storage in your rooted phone..
It does not mount internal storage, and it will not work if your device doesn't have External Memory Card Support..
(And this app automatically sets the SE Linux Enforcement to 'Permissive')
Note:
This will work only if there is FUSE driver built-in in your kernel..
(I'm currently working on installing FUSE drivers for phone with kernel which doesn't have it.
Until then, I'm leaving this app as 'Beta'.)
Download Link:
Universal USB Mass Storage v1.1.apk .
Steps to Enable UMS:
1. Connect phone to Computer or TV or DVD or whatever.
2. Open the 'UMS Universal' app and press 'Enable UMS' and give it root access.
{
"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"
}
Testers, please try and reply.
If it works, please leave a reply with your device model & ROM (and kernel) in which it's working so that I can make a list of working devices.
Thank you
Click to expand...
Click to collapse
About dang time! Just the app I needed! Woot Woot

thanks thanks thanks x999999999999999999..........
i'm using Motorola G 2014 LTE Rom Mokee 5.1.1

Will it work on Android 6.0.1 on sprout4?
Since this only mounts the SD Card, will it work if I had used SD Card as internal storage in Marshmallow?
I just want it mounted, I've got other programs on Windows that can support/read ext4 filesystem drives.
BTW External SD is encrypted and formatted to ext4 filesystem, when SD Card is used as internal storage, so even if it can mount it, using that program to read ext4 filesystem, can I actually access my SD or will it be unsuccessful?
One more, can I install OTA updates without errors if i used this?
Thanks.

Don't work in Glaxy Note 3 (N9005)