yashsingh1/xdaforums huggingface dataset:
[Android Software/Hacking General [Developers Only]] Skippernl:
Hi,

Just tried the las test apk on a desire HTC with nikez jelly been. A2sd was active.

After installing the script and rebooting the internal memory was full. As all programs kept getting stop messages I reverted to a nandroid.

Can you give me some hints to fix this?

Skippernl

Verstuurd vanaf mijn GT-P7510 met Tapatalk 4
[Android Software/Hacking General [Developers Only]] Nightshadow931:
New version FC's here.It just says collection device configuration, and then FC's.

HTC Wildfire S, jellybean 4.1.2.
[Android Software/Hacking General [Developers Only]] vivebatu:
Has anyone tried the latest update? Scared to try it now after 2 fails ( 26 and the penultimate ver) ;-))

On stock miui 2.2.23
[Android Software/Hacking General [Developers Only]] do3in:
2.2.6 and 3 not working for me.

i have Desire and same settings from 2.2.0 (selected apps, swap, - ext4 and class8)
[Android Software/Hacking General [Developers Only]] alexctk:
didnt work for me neither, im on nightly 256, wildfire

i use the default options and after the apps, data, cache, swap, ext2
[Android Software/Hacking General [Developers Only]] vivebatu:
Another question on the side ....it seems all such scripts do not work when the rom has already been used for a while....I have seen innumerable suggestions for a2sd scripts to be used while instalimg the rom for the first time but that does not solve the issue when you ran out of space after using the rom for a while...attempts to install scripts after rom use have failed quite miserably for me ( phone stuck in bootloop, if booted then many apps diappearimg, if all apps present then force closes after a while etc etc)...this is true of amarullz scripts and also other d2sd scripts...only and only darktremor seems to work for such cases...so the question is,

A) is there any script other than darktremor that works?

B) if a script does the same thing at each boot, should it not be independent of the state from which the phone is booting ( first boot or say the 50th boot)?

I hope this script provides answers to try above issues
[Android Software/Hacking General [Developers Only]] gianguido:
"Missing Mounts2SD Busybox" on Sandvold's ICS for Desire 0.4.4.4.1 :-/
[Android Software/Hacking General [Developers Only]] Old User:
The same message I got.
[Android Software/Hacking General [Developers Only]] hello247:
use legacy version. it seems to work for me.
[Android Software/Hacking General [Developers Only]] vassie79:
Sorry, wrong thread, please delete
[Android Software/Hacking General [Developers Only]] dk_zero-cool:
Well no wonder it did not work. Ran the additional a2sd removal script twice. Once after installing m2sd which removes it again.

I have added a new version in this comment with a fixed installer. Will add it to main page once I know that it is working. Tried it on my phone, but that says nothing.

One of the problems for some I guess, is that their system partition does not have enough space left for the m2sd busybox version (1.1mb). So this ZIP has a script that installs the custom busybox only if there is enough space for it on /system. Otherwise the script has been changed to try an use the internal ROM busybox version. This will work for most ROM's. Also in most cases the m2sd busybox will be installed.

So try it out.
[Android Software/Hacking General [Developers Only]] gianguido:
Resolved my error manually, for a strange reason /system/xbin/busybox.m2sd gave me segfault.

Copied that file from an old release of Mount2SD did the trick
[Android Software/Hacking General [Developers Only]] vivebatu:
On miui 2.2.23 (gb)...third time lucky with 3.0.2!!! The phone boots now :-)

However the script loads in safe mode due to sysinit issue mentioned in the op

I feel asking the roms devs to change the sysinit method will be a long shot

So request script dev to consider enabling the script for roms where sysinit is run as a service pls

Cheers
[Android Software/Hacking General [Developers Only]] Old User:
OK, I succeed to install the script and boot the device to work normally, but here what I get in terminal, no matter what i did enabled/disabled, of course, following the instructions from previous pages:

$ export PATH=/data/local/bin:$PATH
$ su
# m2sd log
- Log file is empty!
# m2sd status

Status:
-------
Mounts2SD []
- Apps []
- Data []
- Dalvik []
- CmDalvik []
- Cache []
- SWAP []
- RMount []

Device info:
------------
SD-EXT device []
Cache device []
- Location []
Swap device []
#

and

# df

/dev: 106780K total, 12K used, 106768K available (block size 4096)

/mnt/asec: 106780K total, 0K used, 106780K available (block size 4096)

/system: 163840K total, 130424K used, 33416K available (block size 4096)

/data: 280704K total, 247612K used, 33092K available (block size 4096)

/cache: 30720K total, 1316K used, 29404K available (block size 4096)

/mnt/sdcard: 1328440K total, 1020264K used, 308176K available (block size 4096)

/mnt/secure/asec: 1328440K total, 1020264K used, 308176K available (block size 4096)

I'm not sure what is that I am doing wrong....

P.S. I have three partitions on SD card, FAT/ext3(512MB)/swap(128MB)
[Android Software/Hacking General [Developers Only]] EViollet:
Hi.

Same here.

I enabled "m2sd apps enable" and "m2sd data enable".

After reboot, it doesn't seem to work :

root@android:/ # m2sd status
m2sd status

Status:
-------
Mounts2SD [loaded]
- Apps []
- Data []
- Dalvik []
- CmDalvik []
- Cache [loaded]
- SWAP []
- RMount []

Device info:
------------
SD-EXT device []
Cache device [tmpfs]
- Location [/cache/download]
Swap device []

root@android:/ # df
df
Filesystem Size Used Free Blksize
/dev 202M 32K 202M 4096
/mnt/asec 202M 0K 202M 4096
/mnt/obb 202M 0K 202M 4096
/system 145M 137M 7M 4096
/data 287M 245M 42M 4096
/cache 5M 796K 4M 4096
/sd-ext 1G 32M 1G 4096
/cache/download 128M 0K 128M 4096

root@android:/ # m2sd log
m2sd log

v/Initiating Mounts2SD (v:3.0.2) [Wed Mar 28 22:02:00 GMT 2012]
v/Checking configurations...
v/Optimizing /system readahead...
v/Disabling /system atime & diratime...
v/Optimizing /data readahead...
v/Waiting for sdcard to initiate...
v/sdcard found at /sys/block/mmcblk0...
v/Setting sdcard readahead to 512kb...
w/The sd-ext partition is already mounted!
v/Mounting /cache/download at tmpfs...
v/Mounts2SD has been loaded!

Registered properties:
----------------------
[mounts2sd.cache.device]: [tmpfs]
[mounts2sd.cache.path]: [/cache/download]
[mounts2sd.cache.status]: [loaded]

Mount Points:
-------------
/dev/block/mmcblk0p2 1.5G 32.0M 1.4G 2% /sd-ext

Regards,
[Android Software/Hacking General [Developers Only]] Old User:
At least, you have Mounts2SD and Cache [loaded] and /sd-ext showen among other things... and I tried every single combination... :)

Regards!
[Android Software/Hacking General [Developers Only]] RichmondoUK:
Cannot mount sd-ext. Did on 3.0.0 updated

v/Initiating Mounts2SD (v:3.0.2) [Thu Mar 29 06:38:12 BST 2012]

v/Checking configurations...

w/SYSINIT MISSING: This script works best using sysinit as an executable rather than an service! Switching to safe mode...

v/Disabling /system atime & diratime...

v/Waiting for sdcard to initiate...

v/sdcard found at /sys/block/mmcblk1...

v/Setting sdcard readahead to 512kb...

v/Running e2fsck on sd-ext...

e/Error while mounting the sd-ext partition!

v/Mounts2SD has been loaded!

Registered properties:

----------------------

[mounts2sd.sdext.device]: [/dev/block/mmcblk1p2]

Mount Points:

-------------

from my HTC Sensation XE with Beats Audio using xda premium
[Android Software/Hacking General [Developers Only]] dk_zero-cool:
if you red the log you will see that another script has already mounted sdext. To avoid problems i changed the script to skip sdext when another a2sd script is detected.

Remove the other script and m2sd will work fine.

Enable the debug option. Then you can check /system/etc/m2sd/debug.logcat and see why the partition fails on mount

m2sd debug enable
[Android Software/Hacking General [Developers Only]] RichmondoUK:
--------- beginning of /dev/log/main

I/rmt_storage( 109): rmt_storage user app start.. taking cmd line parameters

I/rmt_storage( 109): modem_fs1 [/dev/block/mmcblk0p26]

I/rmt_storage( 109): modem_fs2 [/dev/block/mmcblk0p27]

I/rmt_storage( 109): radio_config [/dev/block/mmcblk0p18]

I/rmt_storage( 109): rmt_storage open success

D/CABLDaemon( 110): ------ Starting CABL daemon ------

D/CABLDaemon( 110): ABL_QUALITY_HIGH:2

D/CABLDaemon( 110): MSMFB_HISTOGRAM_STOP do nothing

D/CABLDaemon( 110): CABL Original backlight level 255

D/QCAbl ( 110): start reset_cmap

D/QCAbl ( 110): reset_cmap

E/QCAbl ( 110): Ver.20110901.v1

D/CABLDaemon( 110): Wait Terminal Signal

D/CABLDaemon( 110): CABL Waiting for start notification

V/mounts2sd( 138): Initiating Mounts2SD (v:3.0.2) [Thu Mar 29 08:13:45 BST 2012]

V/mounts2sd( 142): Checking configurations...

I//system/xbin/busybox( 107): cat: can't open '/system/etc/init.local.rc': No such file or directory

W/mounts2sd( 223): SYSINIT MISSING: This script works best using sysinit as an executable rather than an service! Switching to safe mode...

V/mounts2sd( 249): Disabling /system atime & diratime...

V/mounts2sd( 261): Waiting for sdcard to initiate...

V/mounts2sd( 270): sdcard found at /sys/block/mmcblk1...

V/mounts2sd( 279): Setting sdcard readahead to 512kb...

V/mounts2sd( 327): Running e2fsck on sd-ext...

I//system/xbin/busybox( 107): e2fsck 1.41.12 (17-May-2010)

I//system/xbin/busybox( 107): /dev/block/mmcblk1p2: clean, 11/262656 files, 49269/1048576 blocks

I//system/xbin/busybox( 107): mount: No such device

E/mounts2sd( 342): Error while mounting the sd-ext partition!

V/mounts2sd( 564): Mounts2SD has been loaded!

But have busybox installed with symlinks
[Android Software/Hacking General [Developers Only]] RichmondoUK:
Can someone post the init.d script of 3.0.0 updated version. :)
[Android Software/Hacking General [Developers Only]] EViollet:
Thanks.

I thought the error message was because it was already mounted by m2sd as the first post states that the script removes previous a2sd files.

For your information, the file names I removed are:

06mountdl and 05mountext

After changing that I had the same problems as the previous people :

root@android:/ # m2sd status
m2sd status

Status:
-------
Mounts2SD [loaded]
- Apps []
- Data []
- Dalvik []
- CmDalvik []
- Cache [loaded]
- SWAP []
- RMount []

Device info:
------------
SD-EXT device [/dev/block/mmcblk0p2]
Cache device [tmpfs]
- Location [/cache/download]
Swap device []

root@android:/ # m2sd log
m2sd log

v/Initiating Mounts2SD (v:3.0.2) [Thu Mar 29 07:25:04 GMT 2012]
v/Checking configurations...
v/Optimizing /system readahead...
v/Disabling /system atime & diratime...
v/Optimizing /data readahead...
v/Waiting for sdcard to initiate...
v/sdcard found at /sys/block/mmcblk0...
v/Setting sdcard readahead to 512kb...
v/Running e2fsck on sd-ext...
e/Error while mounting the sd-ext partition!
v/Mounting /cache/download at tmpfs...
v/Mounts2SD has been loaded!

Registered properties:
----------------------
[mounts2sd.cache.device]: [tmpfs]
[mounts2sd.cache.path]: [/cache/download]
[mounts2sd.cache.status]: [loaded]
[mounts2sd.sdext.device]: [/dev/block/mmcblk0p2]

Mount Points:
-------------

Debug gives the following:

root@android:/data # cat /system/etc/m2sd/debug.logcat
cat /system/etc/m2sd/debug.logcat
--------- beginning of /dev/log/main
I/ev ( 80): Welcome to Android 4.0.3 / Desire Beta 0.4.4.2
I/ev ( 81): Attempting to boot Evervolv AOSP ICS ROM.
I/ev ( 82): Please visit www.evervolv.com for updates.
I/ev ( 83): Also follow @preludedrew on twitter for latest n greatest.
I/ev ( 84): __________ ______
I/ev ( 85): ___ ____/__ ________________ __________ /__ __
I/ev ( 86): __ __/ __ | / / _ \_ ___/_ | / / __ \_ /__ | / /
I/ev ( 87): _ /___ __ |/ // __/ / __ |/ // /_/ / / __ |/ /
I/ev ( 88): /_____/ _____/ \___//_/ _____/ \____//_/ _____/
I/ev ( 89):
I/run-parts( 75): vm.swappiness = 20
I/run-parts( 75): vm.min_free_kbytes = 8192
I/run-parts( 75): vm.dirty_ratio = 60
I/run-parts( 75): vm.dirty_background_ratio = 20
I/run-parts( 75): vm.vfs_cache_pressure = 40
I/nonrot ( 93): Finished
V/mounts2sd( 111): Initiating Mounts2SD (v:3.0.2) [Thu Mar 29 07:27:04 GMT 2012
]
V/mounts2sd( 115): Checking configurations...
V/mounts2sd( 219): Optimizing /system readahead...
V/mounts2sd( 224): Disabling /system atime & diratime...
V/mounts2sd( 234): Optimizing /data readahead...
V/mounts2sd( 240): Waiting for sdcard to initiate...
V/mounts2sd( 247): sdcard found at /sys/block/mmcblk0...
V/mounts2sd( 256): Setting sdcard readahead to 512kb...
V/mounts2sd( 305): Running e2fsck on sd-ext...
I/run-parts( 75): e2fsck 1.41.11 (14-Mar-2010)
I/run-parts( 75): /dev/block/mmcblk0p2: clean, 11/98496 files, 14389/393216 bl
ocks
I/run-parts( 75): mount: No such device
E/mounts2sd( 320): Error while mounting the sd-ext partition!
V/mounts2sd( 419): Mounting /cache/download at tmpfs...
V/mounts2sd( 442): Mounts2SD has been loaded!

Regards
[Android Software/Hacking General [Developers Only]] dk_zero-cool:
The script should not allow this issue. It should always make sure to NOT move anything if there is not enough space on the partition it tries to move to. I will have a look at that.

If you want it working right away, you could make sure to configure it to match your current setup. For an example, if you have /data/data on /sd-ext with your current script, make sure to enable the data option in the configure part of the app. You can see your current setup in the overview part of the app. That way it will not move anything, and you should not be getting any full disk issues.

I logcat from the crash would help locate the issue
[Android Software/Hacking General [Developers Only]] Nightshadow931:
Lemme know if this helps

http://db.tt/W0lEdJ3E
[Android Software/Hacking General [Developers Only]] siavash2death:
Hello,DK. Could you please help me to solve this problem? I never had such problem in previous beta version! (3.0.2)

V/Setting up the script enviroment

V/Collecting MMC partition information

V/The external MMC was located at /dev/block/mmcblk0

V/Located the sd-ext partition at /dev/block/mmcblk0p2

V/The internal MMC was located at /dev/block/mtdblock0

V/Located the system partition at /dev/block/mtdblock3

V/Located the data partition at /dev/block/mtdblock5

V/Located the cache partition at /dev/block/mtdblock4

V/Optimizing MMC devices and partitions

V/Setting readahead on /dev/block/mtdblock0 to kb

W/Could not change scheduler on /dev/block/mtdblock0. The scheduler type is not supported!

V/Setting readahead on /dev/block/mmcblk0 to kb

W/Could not change scheduler on /dev/block/mmcblk0. The scheduler type is not supported!

V/Setting optimized mount parameters on /dev/block/mtdblock3

V/Setting optimized mount parameters on /dev/block/mtdblock5

V/Setting optimized mount parameters on /dev/block/mtdblock4

V/Attaching noatime,nodiratime,relatime,noauto_da_alloc,data=ordered,commit=15,barrier=1,nouser_xattr,errors=continue,nosuid,nodev to /sd-ext

E/It was not possible to attach noatime,nodiratime,relatime,noauto_da_alloc,data=ordered,commit=15,barrier=1,nouser_xattr,errors=continue,nosuid,nodev to /sd-ext

V/Linking system content to the /system location
[Android Software/Hacking General [Developers Only]] gu5t3r:
Because LuPuS kernel was intended to be a ICS+CM9+GB kernel ramdisk has init sh script that chooses between CWM, TWRP and ICS ramdisks (Before it had also CM9 and GB but wedgess couldn't make WiFi work on CM9 and GB so it was removed). Script output is logged to /tmp/lupus.log (/tmp is mounted as tmpfs) and when phone boots up last script that is setting up integrated wifi modules is copying lupus.log both to /data/local/tmp and /cache partition and then deletes everything in /tmp and unmoutns tmpfs...

I didn't see point in keeping /tmp mounted as you can't read log from there if phone doesn't start... This way I can restart in CWM and read log (as it keep log from previous boot as lupus-old.log)

Isn't it better that you use /sd-ext (or your app data dir; or both; App can load newer one if both exists) for log, as this way you can't read log if phone bootloops for some reason?
[Android Software/Hacking General [Developers Only]] dk_zero-cool:
It does, thanks a lot. I will get this fixed :)

Looks strange, especially since this is not a part of the script that has been changed since the first beta release. How about the status? Is sd-ext mounted? I just need to know if this is actually a problem, or just a bug in the log output.

You know, I did use /data until the 4.x version of the script. There was a specific reason why I started using /tmp (Though I can't remember). But I will see about it, because it is true. Having an accessible log via recovery in case of boot issues would not be such a bad idea. Especially when ADB in most ROM's is set to be started so late in the boot process (I always change ADB to start before init.d is executed).
[Android Software/Hacking General [Developers Only]] dk_zero-cool:
Do you know how to use a shell? I could use an output from the command "df -k".

EDIT:

Never mind. Java cannot device by zero it seams (Bad calculator), which was causing issues when calculating usage percentage on partitions with 0 bytes used.
[Android Software/Hacking General [Developers Only]] dk_zero-cool:
The issue with you, is that none of the variables created by the script get's saved by your shell. Nothing in the script has been changed that could cause this, most of the changes since last release has been app changes which does not affect the script. Did you switch ROM or make any other changes besides updating Mounts2SD?

Try installing the last version on the same ROM and setup that does not work with the latest release. You can get them all here: https://sourceforge.net/projects/mounts2sd/files/Testing/
[Android Software/Hacking General [Developers Only]] siavash2death:
I don't know what causing this, but no. I even tested at 2 different versions of PA Rom! Same result! Pixeldroid v2, PA 3.68 AND PA 3.97. All of them have this problem only with latest version of m2sd! I used again V3.0.2 and it's working without any problem! I don't know, but maybe the problem is with the init.d script of m2sd, Because I even one time tried to install new version over previous version of m2sd. It told me that I use outdated script and after that and config the app, this problem happens after rebooting the Rom!

A question: does your app has conflicts with supersu 1.51? I always change default superuser app in roms r to supersu, can it cause problems? If you think that, could you please tell me where I can download latest version of superuser?
[Android Software/Hacking General [Developers Only]] dk_zero-cool:
Well I will look at it, but I don't get it. Only minor changes has been done to the script and none of them could cause this.

Yes, it should be compatible with any SuperUser binary, even the new Daemon mode versions for Android 4.3
[Android Software/Hacking General [Developers Only]] gu5t3r:
What did you use in 5.5.0 for log?
[Android Software/Hacking General [Developers Only]] Skippernl:
DK_Zero-cool,

Hi I send you a PM with a dutch XML could you check if it is sound?

Skippernl
[Android Software/Hacking General [Developers Only]] dk_zero-cool:
One major thing that did change in the last release, was the built-in busybox. Try the new release again, but this time go to Application Settings and uncheck "Use Built-in busybox binary" before rebooting.

I added the /tmp folder in one of the last 4.x versions and have been using it ever since. Only change has been the name of the log file.

Thanks, I will check it once I get home :)
[Android Software/Hacking General [Developers Only]] gu5t3r:
In old 2.2 app I can see the log from 5.5 script even thou /tmp is deleted?

---------- Post added at 11:59 AM ---------- Previous post was at 11:57 AM ----------

Didn't test latest v6 as I will wait until you fix that few buggies from pre-release version...
[Android Software/Hacking General [Developers Only]] siavash2death:
I didn't try for flashing new Rom and install m2sd again, but I overwrite new m2sd over previous version, and unticked busybox and reboot. It seems all warning and errors have gone, but it still an ignore message, it says it can't Change the mount point /cache to /cache-int. Any way to solve this or it doesn't matter?
[Android Software/Hacking General [Developers Only]] zasy99:
I extracted the boot.img from the ProBam 4.4.2 ROM (Galaxy Note 2 N7100) and injected it with your other program, flashed via recovery.

Mounts2SD v3.0.2-beta is still running in safe mode as before.

The Mounts2SD app also crashes a lot, takes about 3 - 6 tries to open and get it running, but it always eventually does.

It did this before injecting and flashing the above also.

ProBam v4.4.2 (Android 4.3)

Kernel Version 3.0.64-CM-gb07657a
[Android Software/Hacking General [Developers Only]] Skippernl:
Tried this script again.

After install of the apk tried to inject the driver got a failed to copy message. Rebooted nevertheless and my internal memory got full and I reverted to my nandroid this morning.

Pm me if you have tips to troubleshoot this on my desire HTC

Skippernl

Verstuurd vanaf mijn GT-P7510 met Tapatalk 4
[Android Software/Hacking General [Developers Only]] gaara6775:
I updated to new version but the script is showing errors. I even re-flash the ROM n install latest version apk but still mount2sd is not getting configured. so now I'm back on Beta apk. my problem is my device cannot download any app from play store if its SIZE is Over 35MB.. I think its issue of my Htc Desire :(
[Android Software/Hacking General [Developers Only]] Skippernl:
I updated to new version but the script is showing errors. I even re-flash the ROM n install latest version apk but still mount2sd is not getting configured. so now I'm back on Beta apk. my problem is my device cannot download any app from play store if its SIZE is Over 35MB.. I think its issue of my Htc Desire ￼

Of you are using titanium backup move some programs like Facebook tot SD this mostly works on my desire

Skippernl

Verstuurd vanaf mijn HTC Desire met Tapatalk 4
[Android Software/Hacking General [Developers Only]] siavash2death:
Uncheck built-in busybox binary in options. The new version working good for me with this solution.at least when I overwrite new version over previous version.
[Android Software/Hacking General [Developers Only]] dk_zero-cool:
Then I find it strange that it worked for you in general. The 2.x app does not use live overview. It just displays prop based information from the script which are all placed in /tmp.

Okay, I will revert back to the prev. busybox.

If it tries to move /cache to /cache-int, it means that you are using a CM based ROM with system dalvik-cache placed on /cache. The script will move the mount point to /cache-int in order to keep the dalvik-cache on the original cache partition when you enable the option to move cache to either data or sd-ext. I will need a complete log with debug enabled.

There are some ROM's which includes an init binary that's handling direct executions within init.rc differently than the standard way. This means that no mater what, init.d will run as a service, and there is no way around it. Why anyone would change this behaviour of init is beyond me, but some do it seams. And there are only two ways of executing third party script from within an init.rc file, in your case both uses sub-process.

I know, I found this issue myself to day. Just press the button again after it fails, and it will copy successfully. Still trying to figure out why it does this, because the log indicates no problems.

I need a bit more information about your problem, because I frankly do not understand what you mean, sorry. Also, if you get crashes or anything, a log will help.

About your play store issues, just enable the cache option. If your cache partition is to small, it makes sense that you have problems with large apps.