Related
I assume no liability for any damage to your phone!
You can use my complete rom or parts of it to make your own rom. Only post a small thanks on your owm thread.
Big thanks to: iaio72, spear1403, tgzw, Quarx, Simondo, ein1002, santimanuel, epsylon3 and ...
Language support for final 4.0 --> da, de, el, en, es, fi, fr, hr, hu, id, it, nb, nl, pl, pt, pt-BR, sv, th, ti, vi, zh_CH, zh_TW + arabic* and ru*
MS2Ginger 4.0
- based on 4.5.2-109-DHT-25 - Android 2.3.6 blur lite rom
- support for Defy, Defy+, Milestone 2, Bravo
- MS2Ginger4 can used as 2nd-system (tested on GB kernel only) !! system image file have to be >= 350 MB
- multibootmanger app by royale1223
- new bootmenu 1.1.8, CWM 5.0.5/6, multiboot big thanks to m11kkaa
- 2 way to boot the rom: normal and via 2nd-init (default)
- new reboot option form cm7.2 --> trigger: all keys at the same time vol- , vol+ , power (only tested on Defy)
- disabled blurhome rotation
- button backlight can set from 10-100 % via build.prop
- mmcfix from CM7
- CPU settings default safe 30/300 38/600 {48/800} 58/1000
- Camera will work on SOC and Bayer camera (green* and red)
- better camera support for bayer camera
- new 720p record* and play (Milestone 2 - Android 2.3.6 files)
- 720p record in m4v (h264 can be enabled via build.prop)
- Milestone 2 froyo camara app for SOC camera (fixed green strips)
- BlurHome from Milestone 2 - 2.3.6 (no widget updating bug)
- Battery min. 2-5 mA/h
- no wifi, apn, vpn bugs
- wifi channels 12, 13, 14 enabled
- bootmenu + cwm (vsel4/clk4 added) "did not work for SOC camera with greenbreadMOD"
- bootmenu with Stable, Custom, Stock-Recovery
- call record libs
- init.d support
- zipalign at boot
- ramscript
- backlight button fix for Defy with bayer camera (can removed via optional patch)
- deepsleep support
- max 10 finger multitouch
- support for farsi-arabic, hebrew (thanks to MMarv)
- CyanogenMod-settings not finished (alpha) - sorry, will try to fix it if i have more time.
(* via greenbreadmod for MS2Ginger4.0 and if you never flashed a Android 2.3.6 full sbf with bl7)
(* 720p record only for Bayer camera Defy and Milestone 2)
Download: ROM, BlurApps, Greenbread: (MS2Ginger4.0.zip, BlurApps-MS2Ginger4.zip,Milestone2patchMS2Ginger4.0withbaseband.zip )
Mirror 1 (google)
Mirror 2 (Dev-Host)
More information for BlurApps --> LINK
Soft-sim-unlock for MS2Ginger 4.0
based on Dabb guide: http://forum.xda-developers.com/showthread.php?t=1447950
Install View attachment 1129769 via CWM.
If you like MS2Ginger feel free to donate! Donations will be used to purchase a Defy with SOC camera (green lens)
Bugs and problems Reporting: http://code.google.com/p/ms2ginger/issues/list?can=1&q
- wifi bug like all 2.3.6 Motorola roms http://forum.xda-developers.com/showthread.php?t=1502817
(fixed, disable unlimited lease time for IP adress on your rooter)
Timeline:
19.06.12 - MS2Ginger 4.0 released
05.02.12 - MS2Ginger 3.0 released
Patch and updates for current release
none for MS2Ginger 4.0
HOW to INSTALL:
To begin:
Put the Nandroid backup folder MS2Ginger on the SDCard in this folder: /sdcard/clockworkmod/backup
Put "Milestone2patchMS2Ginger4.0withbaseband.zip" to the root of your sdcard
Put "Milestone2-GB-kernel-update.zip*" to the root of your sdcard (only if you have a froyo kernel)
-------------------------------------------------------
Root your Milestone 2 and Install BOOTMENU - CWM for Milestone 2
REBOOT
run 2nd-init (voldown on blue LED)
Go to "Recovery"
Go to "Latest or Stable or Custom Recovery"
"wipe data and cache"
Go to "Backup and Restore"
Go to "Advance Restore"
Select "MS2Ginger4.0"
"restore system"
Go to "install zip from sdcard"
select and install "Milestone2patchMS2Ginger4.0withbaseband.zip"
"Install "Milestone2-GB-kernel-update.zip" via install zip" (only if you have froyo kernel)
reboot
Booting up can take a while, max is about 10 minutes.
Team:
- walter79
- spear1403 (theming)
- santiemanuel
- Defy red lens tests spear1403
- Defy greens lens tests luciferps and Cristi_10
- Defy plus tests Dollo73 and free2live
- Milestone 2 tests Carolinux and Motodoido
Translation Team: (each language max. 4 person) View attachment 806172
Brazillian Portuguese: pupiloalpha , Cassinander , filipeazev
Bulgarian Auris 1.6 vvt-i
Farsi: MMarv
Hungarian: szabof1 , balika01
Polish: yackoo , szacuken , Antszej
Serbian: atomskasarma
Spanish espaciosalter20
Spanish-Argentina YaPeL
walter79 said:
Welcome.
The idea:
Defy is running Milestone 2 Android 2.2.2 ROMs. (DACH retail based)
So maybe we could make a working Gingerbread for Milestone 2.
- Defy has rooted only Android 2.3.4 /system nandroid-backup http://forum.xda-developers.com/showpost.php?p=14793844&postcount=8
- it is also possible to run 2nd-init on milestone 2
- read this (Defy 2nd-int + froyo kernel + Gingerbread-system working) http://forum.xda-developers.com/showthread.php?t=1130656
- i think it could be possible to get gingerbread working on milestone 2
- basband should be change with original milestone 2 files
- /lib/hw/ from milestone 2 needed
- kernel from milestone 2
- fix for camera
Whats your opinion?
Click to expand...
Click to collapse
I'm sorry to kill your optimism, but we are unable to flash onto /system for now. Big files at least..
Did clockworkmod not work?
http://www.gamaze.com/blog/2010/11/installing-clockworkmod-recovery-on-motorola-milestone-2/
walter79 said:
Did clockworkmod not work?
http://www.gamaze.com/blog/2010/11/installing-clockworkmod-recovery-on-motorola-milestone-2/
Click to expand...
Click to collapse
It works, it's just that.. it doesn't flash big update.zip's, which overwrite the whole system. Problem could be caused by us not having a recovery build specifically for our devices.
But nandroid backup works, or?
Mikevhl said:
It works, it's just that.. it doesn't flash big update.zip's, which overwrite the whole system. Problem could be caused by us not having a recovery build specifically for our devices.
Click to expand...
Click to collapse
So build one: https://github.com/koush/Droid2Bootstrap
Edit: Check this out "use an update.zip that waits a bit longer for the system to settle then unmounts tmp and remounts /"
dangpzanco said:
So build one: https://github.com/koush/Droid2Bootstrap
Edit: Check this out "use an update.zip that waits a bit longer for the system to settle then unmounts tmp and remounts /"
Click to expand...
Click to collapse
Nice. Will try to get a clean nandroid backup of my /system, unyaffs it and create my own update.zip formatting /system and using this trick to see if I it works.
r2beta0 said:
Nice. Will try to get a clean nandroid backup of my /system, unyaffs it and create my own update.zip formatting /system and using this trick to see if I it works.
Click to expand...
Click to collapse
Lol, I think it's a lucky shot finding this...
Sent from my Milestone 2 XDA App
Hey, what happens if I flash Defy's SBF on M2? Besides other problems is it possible to enter bootloader mode and flash another sbf, or it will corrupt the device?
I didn't, but I saw it was a prerequisite for the Rom posted here, so if there's theorical trouble, then I won't try.
Also I found out that Droid 2 bootloader image has the same first and last bytes as M2 (but different check sums), and Defy's is little different.
dangpzanco said:
Hey, what happens if I flash Defy's SBF on M2? Besides other problems is it possible to enter bootloader mode and flash another sbf, or it will corrupt the device?
I didn't, but I saw it was a prerequisite for the Rom posted here, so if there's theorical trouble, then I won't try.
Also I found out that Droid 2 bootloader image has the same first and last bytes as M2 (but different check sums), and Defy's is little different.
Click to expand...
Click to collapse
Did not work.
dangpzanco said:
Hey, what happens if I flash Defy's SBF on M2? Besides other problems is it possible to enter bootloader mode and flash another sbf, or it will corrupt the device?
I didn't, but I saw it was a prerequisite for the Rom posted here, so if there's theorical trouble, then I won't try.
Also I found out that Droid 2 bootloader image has the same first and last bytes as M2 (but different check sums), and Defy's is little different.
Click to expand...
Click to collapse
I don't think RSD Lite will allow you to do that. Even if it does, I don't think it's a good idea since it may replace your bootloader potentially bricking your phone.
r2beta0 said:
I don't think RSD Lite will allow you to do that. Even if it does, I don't think it's a good idea since it may replace your bootloader potentially bricking your phone.
Click to expand...
Click to collapse
Yeah, I thought about that bricking stuff... (maybe linux/mac sbf_flash would flash it)
Did the "update.zip that unmount tmp and remounts /" work?
Sent from my Milestone 2 XDA App
dangpzanco said:
Yeah, I thought about that bricking stuff... (maybe linux/mac sbf_flash would flash it)
Did the "update.zip that unmount tmp and remounts /" work?
Sent from my Milestone 2 XDA App
Click to expand...
Click to collapse
Not yet, still working on it on my free time. Unfortunately 'free time' is a scarce resource
Maybe if you point the update-script to another script:
Code:
#!/system/bin/sh
#This was in Apex 1.4.1 /etc/init.rc folder (wait for system to settle?)
sleep 24s
#unmount tmp
busybox umount /tmp
#remount /
busybox mount -o remount -rw -t rootfs /
Will it work?
dangpzanco said:
Maybe if you point the update-script to another script:
Code:
#!/system/bin/sh
#This was in Apex 1.4.1 /etc/init.rc folder (wait for system to settle?)
sleep 24s
#unmount tmp
busybox umount /tmp
#remount /
busybox mount -o remount -rw -t rootfs /
Will it work?
Click to expand...
Click to collapse
First attempt failed. I had some problems formatting /system partition. The only way I could get it to format was through Recovery Menu. Maybe the problem is reformatting the system. The command mount("MTD", "system", "/system") also doesn't work. I'm starting to think that Motorola messed with the file system. Will try again using delete_recursive instead of format.
There is any d2 / d2g rom based on GB?
With all the problems developers were facing lately, I guess motorola add the same "weird" protections in m2 2.2 to GB d2 rom
It's very hard to make a custom ROM with all these protections and without knowing what happens when phone tries to boot. All we get is the damned M logo and no info at all. Without some output from the phone everything we can do is guessing.
I was reading that new fission roms based on GB (for d2), were facing the "motorola logo" stuck problem. That´s why the developer gave up.
But, like you say, there is no way to know if it´s the same problem.
I have no knowledge at all on android platform. I´d stuck on winmo 6.
If you need some testing, I can try, there is nothing more I can offer
Second attempt failed. It may have nothing to do with format or system file. I'm really clueless Jut the M logo again. Maybe the /system protection checks for some date/time on some random file? Will reflash with RSD and 'touch' everything in /system to see if the damned thing still boots.
Did you compare the hash of apex files to the moto original files?
Automatically mount and dismount USB sticks on various devices like the Galaxy Nexus, Nexus 7 and Nexus 10. The Nexus 4 is not supported - this is an issue with the device, not with StickMount !
!!! REQUIRES ROOT !!!
Various Nexus and "stock Android" devices do not automatically "mount" mass storage devices (such as USB sticks). StickMount has been made to solve this problem, and give you access to the files on your USB connected storage from all your apps.
StickMount is known to work on many devices, but is built only with Nexus devices in mind.
Once StickMount is installed and you connect a USB stick with a USB host / OTG cable, the device will show you a popup if you want to open StickMount. It is advised to tell the device that you want to do this by default.
If you have just installed StickMount and you already had a USB stick connected, you must manually launch the program, or disconnect/reconnect the USB stick for StickMount to start working.
Mass storage devices are mounted to /sdcard/usbStorage/xxxx/.
(Pro) Kill apps preventing unmount
Sometimes an app has a file in use located on the USB device, and won't let go of it. This can prevent StickMount from unmounting the USB device. It will seem like the device stays connected (this is harmless). StickMount Pro provides an option that attempts to kill (terminate) all the apps that are preventing the unmount from succeeding.
(Pro) Media scan
StickMount Pro supports triggering the media scanner on each (un)mount action. This will automatically make the files on your USB device available in apps like Gallery and Music. Please note that the media scanner is not a visible process on all Android devices - it might actually work silently in the background without any visual cues. It may take a minute for your files to show up, so don't panic if they don't show immediately.
Even if you have this option enabled, you can prevent folders from being scanned by placing an empty file called .nomedia in that folder. If you put it in the root of the USB device, the entire device will not be scanned.
(Pro) Mount as partition label
Instead of using the block device name (sda1, sda2, sdb1, etc) for the partition, use the partition label as mount name. If the label is not available, fall back to the partition uuid (unique id). Only if that is not available either, use the block device name as mount.
This helps to keep your files in the same and easily identifiable place!
(Pro) Create symbolic links
Create symbolic links in /mnt and /storage to the actual mounts in /sdcard/usbStorage/, handy with some file managers and some apps that auto-detect storage locations.
Filesystem support
The filesystems supported depends on your device firmware. On most devices, at least vfat/fat/fat32 and ext2/3/4 are supported. On the latest Android versions, ntfs is also supported in read-only mode. Some devices also support exfat out the box, but most do not.
StickMount can utilize the ntfs-3g and mount.exfat-fuse binaries to add support for ntfs (untested) and exfat, but these are not included. If you place the ntfs-3g or mount.exfat-fuse files in the root of your internal storage ( /sdcard ), StickMount will automatically use them.
You can find the needed files here:
ntfs-3g
mount.exfat-fuse
Troubleshooting
For some users, the app appears not to work, while in fact it is the device itself or the cable not working. One OTG cable is not the other OTG cable. If you have a USB stick with a light on it, it should light up when you connect it to the Galaxy Nexus using your OTG cable. If it does not, either your cable or your Nexus is faulty. 99 out of 100 times it is going to be your cable. That the cable works fine with another device does not mean anything! Cables known to work on a one devices may not work on another device.
SD card unmounting: If your SD card unmounts when unmounting a USB device, you have a bug in your kernel. This is not a bug in StickMount !
Download
StickMount
StickMount Pro (add-on, requires the free StickMount app)
Changelogs
18.01.2017 - v3.50
- (C) 2017
- Handle HTTP redirects when downloading additional tools
23.03.2016 - v3.40
- (C) 2016
- Improve systemless SuperSU compatibility
- Add mount cleanup option
09.10.2015 - v3.33
- Basic M compatibility
13.12.2014 - v3.26
- Minor su policy adjustment
30.11.2014 - v3.25
- Fix unmount+kill issue on L
16.11.2014 - v3.23
- Fix exFAT write issue on L
15.11.2014 - v3.22
- Fix exFAT mount issue on L
06.11.2014 - v3.20 - RELEASE NOTES
- Basic L theming
- Updated SELinux handling, fixes a number of mount/read/write issues on enforcing devices
01.07.2014 - v3.10
- Android "L" Preview compatibility
23.03.2014 - v3.01
- Fix possible force close
23.03.2014 - v3.00
- (Pro) Make mounts available by label or uuid instead of block device name
- (Pro) Make mounts available through /mnt and /storage
- White notification icon for KitKat
10.02.2014 - v2.50
- Fixed a number of (un)mounting issues
- Fixed one possible cause of /sdcard disappearance
- Anticipate and work-around '4.5' issues
- Suggest FS support add-on download
08.02.2014 - v2.40
- Forced a number of commands to toolbox, prevent busybox confusion
- Add mount master usage if available, and warning if not
On Android 4.3 and 4.4, using SuperSU v1.93 or newer is advised, as it provides some features that greatly improve reliability of (un)mounting, versus older versions of SuperSU or other Superuser management apps.
02.11.2013 - v2.30
- Android KitKat 4.4 related fixes
14.12.2012 - v2.20
- Adjustment to NTFS mounting
- UTF-8 mount adjustment (now enabled by default for new users)
- Changed (un)mounting strategy to repetitive scan
- Rearranged preference order
- Adjusted partition detection
- Reworked notification (Jelly Bean +)
- Toast notification no longer shown if turned off in preferences
02.12.2012 - v2.10
- More Android Jelly Bean 4.2 related fixes
- Only works for primary user
- Twitter/G+ spam now included
20.11.2012 - v2.0
- Android Jelly Bean 4.2 related fixes
- Various bug fixes
- Various text changes
- exFAT mounting if "mount.exfat-fuse" is present
- Fixed mounting sdXXYY (as opposed to sdXY) block devices
- (Pro) Kill processes that are preventing unmounting
- (Pro) Trigger media scanner on (un)mount
09.07.2012 - v1.5
- "The Jelly Bean Update"
- ActionBar restored (by many requests !)
- Modified permissions
- Async mounting
- Force holo theme
11.03.2012 - v1.3
- Modified NTFS mounting process
- Various texts adjusted
- App no longer quits on rotate
- ActionBar removed (double title)
- Added codepage and UTF8 options (experts only, will mount with default options on failure)
02.01.2012 - v1.2
- Modified mounting process
- Support different partition layouts
- Support mounting extX partitions
- Support mounting ntfs partitions (if kernel module present and loaded)
20.12.2011 - v1.1
- Added option to disable visual notifications of (un)mounting
- Fixed a number of possible crashes
Oh, hell yes....
{
"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"
}
Working perfectly on GSM 4.0.2. Thanks Chainfire!
i believe this requires custom kernel with USB-OTG enabled?
i tried this on stock 4.0.2, the usb port is just not kicking out any power still.
As stated, rooted ICL53F should work.
Any chance of an option to disable the notification icon as well as the pop ups?
Chainfire said:
As stated, rooted ICL53F should work.
Click to expand...
Click to collapse
tried on my stock rooted 4.0.2, first of all, its not requesting for root permission.
and second of all, nothing happen when i plugged in a usb stick. the usb stick did not even lit up.
any ideas?
qwerp_ said:
tried on my stock rooted 4.0.2, first of all, its not requesting for root permission.
and second of all, nothing happen when i plugged in a usb stick. the usb stick did not even lit up.
any ideas?
Click to expand...
Click to collapse
Doesn't light up... are you using the right cable? I think my USB stick lit up even when I was using the original no-USB-host Nexus kernel ?
Chainfire said:
Doesn't light up... are you using the right cable? I think my USB stick lit up even when I was using the original no-USB-host Nexus kernel ?
Click to expand...
Click to collapse
i am using the usb-otg cable from my xoom. (which works on my xoom. original cable from motorola).
Weird. As I said, it works on my stock rooted Galaxy Nexus (no custom kernel, the ICL53F kernel but rooted). And your USB lighting up actually has nothing to do with StickMount. The device already talks to the USB stick - the only thing StickMount does is mount the partition.
Chainfire said:
Weird. As I said, it works on my stock rooted Galaxy Nexus (no custom kernel, the ICL53F kernel but rooted). And your USB lighting up actually has nothing to do with StickMount. The device already talks to the USB stick - the only thing StickMount does is mount the partition.
Click to expand...
Click to collapse
weird for me. thanks for the support anyway.
for some reason, it just won;t supply any 5+ to the usb devices.
can i know what usb-otg cable you using?
WhiterThanWhite said:
Any chance of an option to disable the notification icon as well as the pop ups?
Click to expand...
Click to collapse
Maybe v1.1. I like to see them, but I can understand if you don't
Hello Chainfire,
Thank you for all your help so far. I am trying this, using the OTG cable that worked with my Motorola Xoom. Unfortunately, it is not working. The drive lights up, but it does not mount the partition.
Galaxy Nexus (CDMA) - Rooted
ROM: Android Revolution HD 2.1.1 LTE
Android Version: 4.0.2 (ICL53F)
Kernel version: 3.0.8-gaaa2611 [email protected] # 1
dahotz said:
Hello Chainfire,
Thank you for all your help so far. I am trying this, using the OTG cable that worked with my Motorola Xoom. Unfortunately, it is not working. The drive lights up, but it does not mount the partition.
Galaxy Nexus (CDMA) - Rooted
ROM: Android Revolution HD 2.1.1 LTE
Android Version: 4.0.2 (ICL53F)
Kernel version: 3.0.8-gaaa2611 [email protected] # 1
Click to expand...
Click to collapse
Do you know the filesystem of the stick ? fat32 ? ntfs ? ext ?
I should probably make a log function for info I need, heh.
is there any chance the mount location can be changed so it's not within the /sdcard folder? Perhaps /mnt unless that isn't the proper place to for mounted devices?
The reason I ask is for backing up the /sdcard. It would be easier to copy /sdcard to a folder that wasn't within the /sdcard path.
Chainfire said:
Do you know the filesystem of the stick ? fat32 ? ntfs ? ext ?
I should probably make a log function for info I need, heh.
Click to expand...
Click to collapse
It is formatted FAT32.
Luxferro said:
is there any chance the mount location can be changed so it's not within the /sdcard folder? Perhaps /mnt unless that isn't the proper place to for mounted devices?
The reason I ask is for backing up the /sdcard. It would be easier to copy /sdcard to a folder that wasn't within the /sdcard path.
Click to expand...
Click to collapse
The reason this stuff is usually under /sdcard is because all programs that can work with the external storage can then access it...
i can confirm it works!
Awesome stuff, works 100% with 4.0.2 and 4.0.3
Sent from my Galaxy Nexus using Tapatalk
I had a hard time searching for full NTFS read-write support for android. This thread is the fruit of that search..
I am posting it here with the hope that it will be useful for many more users of android.
Warning: I will take no responsibility for data loss or corruption that may occur on NTFS drives, though ntfs-3g has been known to be safe.
Q. Why would someone need this?
1. To support NTFS formatted partition(s) of USB-OTG mounted drives
2. To support NTFS partition(s) in microSD card
Q. What are requirements?
1. Fuse driver fuse.ko (compiled for the ROM kernel sources)
2. Latest ntfs-3g binary (see download below)
3. arm powered rooted android device (including SONY, Samsung, Motorola, HTC etc devices)
Q. Steps to get it working?
1. Push fuse.ko to /system or /data, chmod 644, and insmod
2. Push ntfs-3g to /system/xbin/, chmod 755
3. Mount USB OTG device (See script below)
For sdcard, only minor changes required!
4. Unmount as usual with "busybox umount /path/to/mount/"
Download
ntfs-3g
mount script
Update: My USB OTG Helper app has been updated to include this and more. Check it out!!
All-in-one for Sony Xperia 2011 devices -> Here
All-in-one for Samsung Galaxy SII -> Here
Reported working on Samsung Galaxy Note - link - thanks globalthrasher
Touble-shooting!:
For debugging..
1. Download this script and extract to sdcard
2. Connect your drive (pen drive, flash disk, powered HDD)
3. Run the script with script manager
4. Copy the output file from /sdcard/usb_otg_debug.txt and post here
Technical details
---------------------------------------------------------------------------------------------
As the ntfs driver in linux 2.6 kernel does not have write support, the only feasible way was ntfs-3g
Steps:
1. Fuse support (fuse.ko) to be compiled for the respective device from kernel source.
2. The ntfs-3g module was compiled with codesourcery toolchain (arm-none-linux-gnueabi)
Code:
./configure --enable-really-static -host=arm-none-linux-gnueabi
make
ntfs-3g: Main site | More details | Release History
NTFS Utils
NTFS Utils reference:
NTFS UTILITIES
==============
The ntfsprogs includes utilities for doing all required tasks to NTFS
partitions. In general, just run a utility without any command line
options to display the version number and usage syntax.
ntfsfix - Attempt to fix an NTFS partition and force Windows to check NTFS.
mkntfs - Format a partition with the NTFS filesystem.
ntfslabel - Display/change the label of an NTFS partition.
ntfsundelete - Recover deleted files from an NTFS volume.
ntfsresize - Resize NTFS volumes.
ntfsclone - Efficiently create/restore an image of an NTFS partition.
ntfscluster - Locate the owner of any given sector or cluster on an NTFS partition.
ntfsinfo - Show some information about an NTFS partition or one of the files or directories within it.
ntfsls - List information about files in a directory residing on an NTFS partition.
ntfscat - Concatenate files and print their contents on the standard output.
ntfscp - Overwrite files on an NTFS partition.
Click to expand...
Click to collapse
This is great. The fat32 4 GB size limit suck. Hope to get some exFAT support in the future also since exFAT is currently supported by both Mac and Windows 7,8.
Sent from my EVO 4G LTE
david279 said:
This is great. The fat32 4 GB size limit suck. Hope to get some exFAT support in the future also since exFAT is currently supported by both Mac and Windows 7,8.
Sent from my EVO 4G LTE
Click to expand...
Click to collapse
exFAT is working just fine on my SGS III (XXALE9)
Thnx Shardul,
This is great.
This is great news, imma give it some time before trying it though !
Will try it tomorrow
Great news. I was able to make ntfs work with my SG2 and now i hope to do the same with my sg3. Thanks!
This is indeed awesome news. Thanks for the head's-up.
Ciao
Great news....
Gonna try it soon...my galaxy fit would have external hardisk from now
Is it posible to include it when i compile with my own kernel rather than push the fuse.ko directly to the system?
Sorry for my bad english...
Sent from my GT-S5670 using xda premium
dodoik said:
Great news....
Gonna try it soon...my galaxy fit would have external hardisk from now
Is it posible to include it when i compile with my own kernel rather than push the fuse.ko directly to the system?
Sorry for my bad english...
Sent from my GT-S5670 using xda premium
Click to expand...
Click to collapse
Ofcourse you can compile it as built-in rather than a module
anything for Transformer Prime?
working on galaxy nexus?
Great!
Anyone tried it on Samsung Galaxy Tab 10.1 (P7500)?!?
HERE the way to use it on SGS2 (I9100), I didn't try it.
I'll try on SGT10.1, but there is a way to auto-mount devices on connect?
See update in OP.. Easier to use with my updated app!
Edit: and auto start also!
shardul_seth said:
See update in OP.. Easier to use with my updated app!
Edit: and auto start also!
Click to expand...
Click to collapse
Thank you! I'll try tomorrow on both devices!
A couple of quick question, as I'm not sure about this, although "microSD" is mentioned in the first post...
1. Will this work for 64GB microSDXC expansion cards to be formatted as NTFS, usable and fully recognized? Or this is only for USB-OTG support for NTFS storage?
2. Does updated app (Helper) in the other thread take care of all the steps mentioned in original post when it comes to enabling microSDXC support mentioned above?
3. Has anyone successfully done this for Samsung Galaxy Note yet?
Sorry, if those are questions for obvious answers...
Thx.
globaltrasher said:
A couple of quick question, as I'm not sure about this, although "microSD" is mentioned in the first post...
1. Will this work for 64GB microSDXC expansion cards to be formatted as NTFS, usable and fully recognized? Or this is only for USB-OTG support for NTFS storage?
2. Does updated app (Helper) in the other thread take care of all the steps mentioned in original post when it comes to enabling microSDXC support mentioned above?
3. Has anyone successfully done this for Samsung Galaxy Note yet?
Sorry, if those are questions for obvious answers...
Thx.
Click to expand...
Click to collapse
1. Yes, just issue the commands on terminal
2. No
3. Not tried, but possible if kernel support
How can I obtain a working fuse.ko for my Samsung Galaxy Tab 10.1 (P7500) with pershoot kernel?
maxwarp79 said:
How can I obtain a working fuse.ko for my Samsung Galaxy Tab 10.1 (P7500) with pershoot kernel?
Click to expand...
Click to collapse
Just ask pershoot and I am sure he will oblige..
Edit: I think it is already enabled. See here
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.
In 2021 This thread and device are pretty much defunct; links in OP are updated though as I've been seeing a few requests lately.
Many thanks to all of the following. This small project would not be possible without their work/research.
Sergio Poverony
BSDgeek_Jake
raishiro
Koush
Garner
Basian Mile
rovo89
Prevailious
arctablet.com
This is a customized version of the most recent stock firmware (v4) for the Monster M7 tablet designed to make your tablet bloat free and easily rooted. Otherwise known as a custom ROM. The android version is 4.1.1.
In order to fully enjoy all the features of this ROM it needs to be flashed via some type of flashing tool through your computer, such as the Rk Batch Tool. Please see the instructions in the second post for setting up this tool properly.
Note that you can simply rename the .img file to update.img and flash it through your phone's recovery, but you'll be missing 3GB of storage in addition to having the manufacturer default allocation for app storage. Everything else should work correctly should you decide to use such a method.
Features:
Pre-Rooted (Koush SuperUser)
Very slim
xPosed framework
Modified Hosts file. Blocks large amount of advertising.
App storage increased to 3GB
All Monster bloatware removed.
DPI set at 160. (you can change this with an app.)
4.4 E-mail and News&Weather Apps.
4.2 Clock App.
Stock Browser with Adobe Flash 11
Added ArcTools for easy CWM installation.
ro.secure=0
ADB debug enabled by default.
Download
Let me know if there are things you would like to see added. Higher android version at this point is beyond me, and I'm not even sure if it's possible as there is no source code yet available for this particular device. (Let me know if you somehow acquire source code for this device though )
Instructions for setting up the RK Batch Tool and drivers. Thanks to sab99
Shutdown the M7 tablet
Run the RK Batch Tool, Open Device Manager
Connect the USB cable to the PC, while pressing the volume down button on the side of the M7. You will see nothing on the screen, but at this point, Windows should be alerting you to a USB device insertion. At this point my Win 8.1 x64 box kept detecting the device and popping up a failed device message - the Win 7 x64 detected the device and left it as unknown (which is expected).
Go into the device manager, find the unknown device, and update its driver with the Rk Batch Tool driver for your bitness and os.
Now the RK Batch Tool should show green for your tablet.
Load the ROM and press the Recover button.
Have a beer while it flashes.
reserved
reserved
reserved
Open.
Could you please provide a correct drivers for Monster M7? Drivers from Rk Batch Tool you've provided are not working. I've tried on Win8/Win7, 32/64, driver can't start and always shows error 10. I also tried to install on the "Android-free" PC (Win7, 32), no android usb drivers are previously installed - no luck.
P.S. And of course I've tried different USB ports and cables (what is really stupid 'cause my Nexus 7 2013 and all WinPhones are using these cables without problems)
sensboston said:
Could you please provide a correct drivers for Monster M7? Drivers from Rk Batch Tool you've provided are not working. I've tried on Win8/Win7, 32/64, driver can't start and always shows error 10. I also tried to install on the "Android-free" PC (Win7, 32), no android usb drivers are previously installed - no luck.
Click to expand...
Click to collapse
I had an issue with my Windows 8.1 x64 machine, but it worked on a Win 7 x64 machine. The steps to use the RK Batch tool with the M7 are:
Shutdown the M7 tablet
Run the RK Batch Tool, Open Device Manager
Connect the USB cable to the PC, while pressing the volume down button on the side of the M7. You will see nothing on the screen, but at this point, Windows should be alerting you to a USB device insertion. At this point my Win 8.1 x64 box kept detecting the device and popping up a failed device message - the Win 7 x64 detected the device and left it as unknown (which is expected).
Go into the device manager, find the unknown device, and update its driver with the Rk Batch Tool driver for your bitness and os.
Now the RK Batch Tool should show green for your tablet.
Load the ROM and press the Recover button.
Have a beer while it flashes.
Thanks for the cleanups on this ROM, kaiserII101. 3GB, no crapware, and all source code is the way everything should be shipped. At least you fixed 2 of the 3. When you start looking at these 'value' tablets they are all pretty much the same. If you REALLY wanted to sell a ton of your hardware, releasing the source would encourage the modding community here and be worth more advertising dollars than your razor thin margins could ever support.
sab99, thanks for the help but yesterday I figured out by myself (it costs me a few hours of sleep but fortunately it's a weekend )
But definitely TS should add your instructions to the first post! Also, #3 is very important - it's absolutely unclear from TS post and another discussion (someone referred to the bootloader mode as a "flashing mode" that is confusing).
Also, using topic starter's image and RK29xxImageTools, I've increased userdata (internal memory) up to 8GB. Here is parameters for partitioning (I also attached my parameter file):
Code:
CMDLINE: console=ttyFIQ0 androidboot.console=ttyFIQ0 init=/init initrd=0x62000000,0x00800000 mtdparts=rk29xxnand:[email protected](misc),[email protected](kernel),[email protected](boot),[email protected](recovery),[email protected](backup),[email protected](cache),[email protected](userdata),[email protected](kpanic),[email protected](system),[email protected](user)
I'm curious: is it possible to completely get rid of "user" (aka "internal sdcard") partition? This "monster" works perfectly with 32GB microsd, so we don't need to waste important nand space...
Also, could we change mtdparts order, to simplify calculations? I mean something like this (showing just the end of CMDLINE string):
Code:
... [email protected](cache),[email protected](kpanic),[email protected](system),[email protected](userdata)
I can't try now: my daughter (3.5 yo) just grabbed the tablet and started installing and reinstalling her favorite games (actually, I've bought this "monster" 'cause her old Gtab 7'' just broke - probably, LCD screen connection problem - but I can't fix it, need a special screwdriver to disassemble. BTW, this Galaxy Tab is a great product - very old but still working).
sab99, could you try "user"-less partitioning (i.e. without "internal sdcard")? Actually it will be great, and this option (if works of course) will significantly improve tablet value.
P.S. Seems like to be able to do this, we also need to comment that line in \system\etc\vold.fstab and repack system.img. Probably, TS can help us...
Code:
## Vold 2.0 Generic fstab
## - San Mehat ([email protected])
##
#######################
## Regular device mount
##
## Format: dev_mount <label> <mount_point> <part> <sysfs_path1...>
## label - Label for the volume
## mount_point - Where the volume will be mounted
## part - Partition # (1 based), or 'auto' for first usable partition.
## <sysfs_path> - List of sysfs paths to source devices
######################
## Example of a standard sdcard mount for the emulator / Dream
# Mounts the first usable partition of the specified device
#dev_mount sdcard /mnt/sdcard auto /devices/platform/goldfish_mmc.0 /devices/platform/msm_sdcc.2/mmc_host/mmc1
### dev_mount flash /mnt/sdcard auto /dev/block/mtd/by-name/user <-- we need to comment this line (in case we don't want to have "internal sdcard"
dev_mount sdcard /mnt/external_sd auto /devices/platform/rk29_sdmmc.0/mmc_host/mmc0
dev_mount udisk /mnt/usb_storage auto /devices/platform/usb20_otg/usb1
## Example of a dual card setup
# dev_mount left_sdcard /sdcard1 auto /devices/platform/goldfish_mmc.0 /devices/platform/msm_sdcc.2/mmc_host/mmc1
# dev_mount right_sdcard /sdcard2 auto /devices/platform/goldfish_mmc.1 /devices/platform/msm_sdcc.3/mmc_host/mmc1
## Example of specifying a specific partition for mounts
# dev_mount sdcard /sdcard 2 /devices/platform/goldfish_mmc.0 /devices/platform/msm_sdcc.2/mmc_host/mmc1
Added the instructions for setting up the RK Batch Tool in the second post.
Possible bug with velvet.apk (search) force quitting.. May need to revert to an older version as soon as I can start building again.
As far as eliminating the user partition, I would say, yes it is probably possible. Personally though, I'm not sure I want to do that. Will certainly try experimenting with it though.
Also, please everyone feel free to take the ROM, modify it, and post a link to your modified version (preferably list the changes you made). In order to modify update.img contents easily and repack them into flashable form you can use Sergio Poverony's tools. http://forum.xda-developers.com/showthread.php?t=2445406
I will be travelling to Russia wednesday for 5 months, and so I probably will be out of action here for a week at least I imagine. I will have internet access there eventually, as I'll be getting a sim-card, but important thing is to get settled in there first.
Thanks for your tip but I suggest a better link for the Sergio Poverony's tools
Unfortunately I can't experiment with Monster M7: a little Alice completely occupied a new toy Probably, some guys (also this Monster currently on sale for $75 at Walmart) can do some experiments.
P.S. For us, my "mod" (if I can say) is enough; 8GB + 4GB "internal sd" fits well my daughter's "play pattern" - she has (and download new stuff every day ) a lot of relatively small children games, so these games has all assets packed into .apk.
P.P.S. Here is the link to the "8GB" image: https://www.dropbox.com/sh/3bj2thbf9sfshz8/M_RCCWtsek
Hey congrats on this! Hope you can make many more improvements for a lot of people out there.
Would it be possible to perform an update the regular way after modifying the storage space parameters?
Prevailious said:
Would it be possible to perform an update the regular way after modifying the storage space parameters?
Click to expand...
Click to collapse
I don't think so. But it's not a big problem - we always can do this trick again; the main problem is about update; I don't think the manufacturer will release any major update (like KitKat) for this device
P.S. BTW, we've got exactly what we paid for... What are you expecting for $75 device?
Awesome!
i wasn't expecting much from this tablet, but daaaang, good job guys. i was expecting to have to try Kingo or Framaroot to get a root on this. you guys have it rooted AND the user partition expanded!! too cool. +1000!
Zzz73 said:
i wasn't expecting much from this tablet, but daaaang, good job guys. i was expecting to have to try Kingo or Framaroot to get a root on this. you guys have it rooted AND the user partition expanded!! too cool. +1000!
Click to expand...
Click to collapse
Same here.
The link to the RK Batch Tool in the OP doesn't work. Will this version work?
http://www.freaktab.com/showthread.php?5173-New-Rockchip-Batch-Tool-v1-7-Plus-v3-5-Drivers
Just picked up two of these tablets for my kids and would like to remove the extra crap and increase the size of the internal storage partition.
---------- Post added at 10:30 PM ---------- Previous post was at 09:40 PM ----------
OK, so what am I doing wrong? I'm trying to follow the instructions in POwer #2
I powered off the M7 by holding down the power button and choosing to Shut Down. When I plug in the usb cable, nothing happens. Windows doesn't detect anything at all.
Was I just supposed to turn off the screen but not shut down the entire tablet? I don't get any Device Connected messages, nothing shows up in Device Manager, etc.
OK, well. No idea why the heck it didn't work last night but it worked fine just now. Whole process took like 3 minutes. Wasn't even enough time to go get a beer.
Update:
Well, looks like I spoke too soon. It boot sup to the Monster screen and then just stops. It never continues on. Anyone have any suggestions?
Update2:
I flashed it again and this time it gave me the sphere after the update and then came up. One thing I notice is that some of the fonts seem hard to read in the Play Store. Not sure if that's because of the DPI setting change or what. Nice to see such a small list of apps when I view the All Apps page.
Anyone use the image in the OP and have trouble using the Clear Notifications button when you swipe up the notification bar? It takes me like 1o tries to tap it because most of the time it just registers that I'm tapping the whole bar and toggles between notifications and whatever the other screen is.
I'm guessing it's just my fat fingers but thought I'd see if I'm really going insane or not...
kelemvor33 said:
Anyone use the image in the OP and have trouble using the Clear Notifications button when you swipe up the notification bar? It takes me like 1o tries to tap it because most of the time it just registers that I'm tapping the whole bar and toggles between notifications and whatever the other screen is.
I'm guessing it's just my fat fingers but thought I'd see if I'm really going insane or not...
Click to expand...
Click to collapse
it's not just you. I have noticed the touchscreen not being very responsive. drives me nuts. also the touch accuracy is a little off... no big deal, still a decent tablet for what I paid.
Sent from my Optimus G using Tapatalk
So I got an update prompt for SuperUser today. I tried the "Install" button and instantly got an error. So I then tried the Recovery Install option and the tablet has been sitting there for 10+ minutes and I don't know if it's doing anything.
Anyone know if this should eventually work or what's going on?
Thanks.