yashsingh1/xdaforums huggingface dataset:
[Android Software/Hacking General [Developers Only]] Sachin Thomas:
Here's the df output with int2extv2+ in use:

Filesystem Size Used Available Use% Mounted on
tmpfs 200.4M 48.0K 200.4M 0% /dev
tmpfs 200.4M 0 200.4M 0% /storage
tmpfs 200.4M 0 200.4M 0% /mnt/secure
tmpfs 200.4M 0 200.4M 0% /mnt/asec
tmpfs 200.4M 0 200.4M 0% /mnt/obb
tmpfs 200.4M 0 200.4M 0% /mnt/fuse
/dev/block/mtdblock3 235.3M 228.3M 6.9M 97% /system
/dev/block/mtdblock5 960.7M 208.4M 752.3M 22% /data
/dev/block/mtdblock4 59.0M 2.4M 56.6M 4% /cache
/dev/block/mmcblk0p2 960.7M 208.4M 752.3M 22% /data
/dev/block/mtdblock5 150.0M 61.0M 89.0M 41% /data/app-asec
/dev/block/mtdblock5 150.0M 61.0M 89.0M 41% /data/app-lib
/dev/block/mtdblock5 150.0M 61.0M 89.0M 41% /data/backup
/dev/block/mtdblock5 150.0M 61.0M 89.0M 41% /data/data
/dev/block/mtdblock5 150.0M 61.0M 89.0M 41% /data/dontpanic
/dev/block/mtdblock5 150.0M 61.0M 89.0M 41% /data/drm
/dev/block/mtdblock5 150.0M 61.0M 89.0M 41% /data/local
/dev/block/mtdblock5 150.0M 61.0M 89.0M 41% /data/lost+found
/dev/block/mtdblock5 150.0M 61.0M 89.0M 41% /data/media
/dev/block/mtdblock5 150.0M 61.0M 89.0M 41% /data/mediadrm
/dev/block/mtdblock5 150.0M 61.0M 89.0M 41% /data/misc
/dev/block/mtdblock5 150.0M 61.0M 89.0M 41% /data/property
/dev/block/mtdblock5 150.0M 61.0M 89.0M 41% /data/radio
/dev/block/mtdblock5 150.0M 61.0M 89.0M 41% /data/resource-cache
/dev/block/mtdblock5 150.0M 61.0M 89.0M 41% /data/security
/dev/block/mtdblock5 150.0M 61.0M 89.0M 41% /data/ssh
/dev/block/mtdblock5 150.0M 61.0M 89.0M 41% /data/system
/dev/block/mtdblock5 150.0M 61.0M 89.0M 41% /data/user
/dev/block/vold/179:1
908.1M 841.3M 66.8M 93% /storage/sdcard0
/dev/block/vold/179:1
908.1M 841.3M 66.8M 93% /mnt/secure/asec

Recovery doesn't get mounted here. And some people have even reported that the play store version of Mounts2SD works for them without any issues, when reverse mount and cache is disabled
[Android Software/Hacking General [Developers Only]] dk_zero-cool:
Well now it makes even less sense. Could you install it again, and this time make sure to have debug enabled in the application before rebooting? It will provide more entries in the log which I will need to figure this out. And of cause, attach a new M2SD log :)

EDIT:

Also, what other scripts do you have? And do you have apps installed that could mess with mount locations (Only consider apps with Root permissions).

/dev/block/vold/179:1 908.1M 827.8M 80.3M 91% /storage/sdcard0
/dev/block/vold/179:1 908.1M 827.8M 80.3M 91% /mnt/secure/asec
/dev/block/mtdblock1 5.0M 1.5M 3.5M 30% /sd-ext

This is the strange part. You say that this is a result of having Mounts2SD installed, but according to this output from 'df', the recovery is mounted after the script is executed, even after Android has booted and entered into the UI.

/dev/block/vold/179:1 is your regular storage partition (Fat32) which is handled by Android once the system boot is complete (Just look in the notification after a boot, it will mention something about "Preparing the sdcard..."), and the recovery is mounted after this. This means that it is mounted by a script with a large timeout, an application with an onBoot receiver, or by Android (ROM Issue).
[Android Software/Hacking General [Developers Only]] dk_zero-cool:
Which flags? Someone must have chosen /sd-ext as the mount location somewhere, especially this location as it has nothing to do with Android, it's something some free-time developer came up with at some point that we have all used since.

And since not all sd-ext scripts results in this partition being mounted, it means that it has some trigger that get's pressed by some of the options that only Mounts2SD has.

There is no doubt that this is a strange ROM issue, but I really hate unexplained issues that makes no sense. I have a compulsion of some sort that forces me to figure this out :D
[Android Software/Hacking General [Developers Only]] MetinKale38:
Yeah, i just tried to mout the recovery paritions manually, because i was not sure how it works and i got an empty folder mounted and a wiped recovery :)

Tapatalked... just Tapatalked...
[Android Software/Hacking General [Developers Only]] dk_zero-cool:
@Sachin Thomas

It think it could be the Application. I need a few things in order to check and also to fix it if that is the case. You don't have to install the Application again right now, just make sure to grap these things from with Android and not from the Recovery.

ALL the files in your / directory (Not folders, just files)

/proc/mtd

That's it, you have already provided the rest :)
[Android Software/Hacking General [Developers Only]] Rashed97:
Hm, can I have a link to that ROM? I might be able to find something in it that could help identify what's wrong.

And for feature requests just use DevDB right?
[Android Software/Hacking General [Developers Only]] dk_zero-cool:
Actually, I think this one might be the problem

Yes, and future issues as well :)

But make sure to read the OP, I have added a section where current requests is written to avoid repeats.
[Android Software/Hacking General [Developers Only]] Sachin Thomas:
Here's my /proc/mtd

dev: size erasesize name
mtd0: 00100000 00040000 "misc"
mtd1: 00500000 00040000 "recovery
mtd2: 00400000 00040000 "boot"
mtd3: 0eb40000 00040000 "system"
mtd4: 03b00000 00040000 "cache"
mtd5: 09600000 00040000 "userdata
mtd6: 00a00000 00040000 "devlog"

Please see the attachment for files in root directory:

View attachment root.7z

Edit:

Apps with root access are:

CM File Manager

ES File Explorer

Terminal Emulator

Titanium Backup

Mounts2SD

I don't have any other scripts installed

Titanium Backup always shows the exact sd-ext partition stats
[Android Software/Hacking General [Developers Only]] dk_zero-cool:
Thanks. I think I found the issue in RootFW, I just need to find the cause. However I changed the app so that it will no longer be affected by it. Will have an update by tomorrow.
[Android Software/Hacking General [Developers Only]] Rashed97:
Just a quick probably stupid question: What happened to the reversed mount?
[Android Software/Hacking General [Developers Only]] dk_zero-cool:
It's useless and creates to many problems, so I removed it. It's not worth the trouble.
[Android Software/Hacking General [Developers Only]] mikebeatrice:
I'm having a strange issue. It started with 3.1.8, but even trying to rollback to older versions isn't helping.

Even though the script is installed and working, the app displays the message that no script is installed and it wants me to go to settings and install. When I do this, it completely hoses m2sd and it doesn't run on boot. When this happens, I end up with 10mounts2sd-run in my init.d folder instead of the normal file.

Not sure what to try...and I can't get a m2sd log since it thinks no script is running.

I've never had another a2sd style script on this phone, so I know it's not a conflict like that. Help?
[Android Software/Hacking General [Developers Only]] xeraphael:
Sorry if this has already been answered, but a search didn't turn up much: what happened to the recovery ZIPs to be flashed after you format /system and update your ROM? Or are they unnecessary anymore with the latest version?

Thanks in advance.
[Android Software/Hacking General [Developers Only]] dk_zero-cool:
The script has been moved to /system/etc/mounts2sd.sh and is executed using /system/etc/init.d/10mounts2sd-runner in order to control the shell environment being used. You cannot revert back from the latest version without reflashing your ROM to reset /system, because older versions cannot strip the new init.d file. But when you install the script from settings, make sure it did not fail (Check the script info in settings), and then check to see if both the above mentioned files is available.

They will be back. I have not officially released this version yet (Check Play Store), and once I do, I will add recovery packages and all that again.
[Android Software/Hacking General [Developers Only]] mikebeatrice:
Thanks for the info. I don't know what went wrong the first time, but the script installed successfully this time and also executed as expected upon reboot.

Is there a tutorial somewhere that explains any advantages/disadvantages of the various mmc schedulers and read ahead selections?
[Android Software/Hacking General [Developers Only]] swat4samp:
The latest version gave me random reboots, even it doesnt boot into system. Sorry but this is the first time im trying this app. I installed script from the app and rebooted. Is there something i must do before?
[Android Software/Hacking General [Developers Only]] klncdc:
Sd-ext not mounted

Hello,

I already have a script app2sd (sd-ext created and used) and I wanted to replace it with this application. mmcblk0p2=ext4.

When I install it, it installs correctly but when I restart all my apps (not system) have disappeared ... I reinstalled the application, restart and then I discovered the explanation of my problem: the application tells me sd-ext is not mounted ... why? The application does not itself handle the rise of this partition?

Thank you.
[Android Software/Hacking General [Developers Only]] dk_zero-cool:
Did you install the script?

The application does nothing by itself. Like your cuurent app2sd, it needs a script to perform the actions. You neex to install it from settings.
[Android Software/Hacking General [Developers Only]] Rashed97:
DK, is there a way to move some of the apps back to the /data partition? Everytime I try to select a theme it won't work since they have to be on the actual phone for some stupid reason.
[Android Software/Hacking General [Developers Only]] dk_zero-cool:
Sorry no. I don't think it is correct to do so for this reason. The only way to select individual applications to move or don't move to sd-ext, is by moving them to a non-android supported folder and then create a symlink file to the original android location. This will completely screw up android's package management, because it is not build to handle symlinks, so updates and removal of applications would fail. I allow this with system files, because those are not meant to be replaced or removed anyway, because the system partition is not meant to be wrietable.

That said, you could cheat this by reverting themes into system applications. If you move them to /data/app_s, they will be linked to /system/app. And unlike /data/app-system, this folder has it's own option, which means that you can keep that folder on /data while moving the others to /sd-ext.

But I can't see why it should not work. Folders from /sd-ext is mounted, and not linked, to it's equal /data folder. So there should be no different, system wise, where you place the content. I use themes on my own device which is moved to sd-ext. This is the exact reason why I created Mounts2SD in the first place, because all other sd-ext script used symlinks which screwed up things on newer Android systems. What issue to you get by using the themes, and what themes are we talking about, CM Themes?
[Android Software/Hacking General [Developers Only]] dk_zero-cool:
@Sachin Thomas

I have located your issue with your recovery partition.

You can see the problem here.

The problem was that you had an fstab.goldfish (Emulator file) in your ramdisk, and RootFW was not told to skip these on real devices. In this file, the /dev/block/mtdblock1 has been added as the /data partition, which is what RootFW returned as it read this file before the real fstab file.

Mean while I have also added some safety checks to the application which will help avoid these issues again, even if RootFW should return something wrong. And RootFW has of cause been fixed, so it should not, but better safe than sorry :)
[Android Software/Hacking General [Developers Only]] mikebeatrice:
Does this script do something to force /system to always boot up as read/write instead of read only?

Or possibly the init.d injector?

Ever since I started using the injector and the 3.x versions of this app, my system partition always boots to rw, and I haven't figured out if it's coincidence or not...
[Android Software/Hacking General [Developers Only]] klncdc:
Hello and thank you,

I did not say anything I did but of course I installed the script with "settings" and I have also checked it automatically deleted my old app2sd in init.d.

When I launch the application after reboot: they all disappeared ...

The application does not mount my sd-ext partition ...

Is there a log where you can monitor any error messages (other than the Application log that always shows empty even log in debug mode? :confused:
[Android Software/Hacking General [Developers Only]] dk_zero-cool:
No. Injector just add the feature of executing the init.d folder, it does not change mount arguments on any partition. And the script checks the current state before remounting system rw, and then it restores the same sate when it is done.

You can use logcat during boot.

Did you make sure that the script actually was installed? Above the install button, both "Installed" and "Bundled" should print the same thing.
[Android Software/Hacking General [Developers Only]] klncdc:
Yes, the script is installed "10mounts2sd-runner" replaces my old app2sd well. In the application: Installed: 6.0.8.

Sd-ext not mounted...
[Android Software/Hacking General [Developers Only]] swat4samp:
Of course i installed and then rebooted. AFter reboot, the phone goes into bootloop like i said before? My phone is galaxy fit running CM10.1

And its the first time i am using it.
[Android Software/Hacking General [Developers Only]] Nightshadow931:
Here's every init* file I found.

http://db.tt/WeIK3woU

I booted the device, it was unusable, then rebooted in recovery and tried to find the logs you're talking about, but there is no such file(s) or directories in /data.

Anyway, I decided to do a clean install with mounts2sd, I instaled the app and the script, rebooted, and nothing happens.When I go to m2sd it says that external memory is not detected, or not mounted, something like that.For driver it says not recognized.

For internal memory it shows my actual internal memory (150mb).

What could be the problem?
[Android Software/Hacking General [Developers Only]] dk_zero-cool:
There are two scripts, look for /system/etc/mounts2sd.sh ?

What ROM do you use? Is it an official CM, or an unofficial?

I will look at your rc files, thanks.

Are you able to grab a logcat while it is booting? If so, I could really use the first parts of the log to see if the script is executed, and if there is a shell error while it's being executed.
[Android Software/Hacking General [Developers Only]] Nightshadow931:
I will try.

For which situation you want the log, when I install the script over int2ext or now when I tried clean rom install with m2sd? :)
[Android Software/Hacking General [Developers Only]] dk_zero-cool:
When you boot with m2sd installed
[Android Software/Hacking General [Developers Only]] Nightshadow931:
Here it is, logcat while the device is booting.Hope it helps.

https://dl.dropboxusercontent.com/u/49071599/logcaat.txt
[Android Software/Hacking General [Developers Only]] Rashed97:
Yeah CM themes. You'd think they'd work, right? Unless its my ROM thats screwed up (although they have worked before so IDK)

And yeah I think I'll try cheating them.
[Android Software/Hacking General [Developers Only]] dk_zero-cool:
I don't know your device, so I would not know if you can get an official or not. But unofficial CM ports has a tendency to add all kinds of different a2sd versions. Some of these are build into the kernel and uses by default sd-ext as data. Mounts2SD cannot be used on these since I cannot remove the builtin version.

So if you could provide a link to your ROM Thread, I can have a look and see how it is built?

Thanks, I will have a look at this tomorrow.

That is strange. I have been using CM Themes since CM9 while having everything moved to sd-ext, still works fine on 10.2
[Android Software/Hacking General [Developers Only]] Rashed97:
Haha, it might be my phone then. Weird since they used to work before.

Anyway, have you ever though about implementing an in-app switcher to move apps from /sd-ext/app to /data/app_s?

That would be far more convenient for the average user than having to physically move the APK (some of my ROM users don't even know where the APKs are...) Just throwing out some ideas ;)
[Android Software/Hacking General [Developers Only]] dk_zero-cool:
That is not gonna happen, but I am currently working on an in-app manager to move apps from /data/app to /data/app-system and then give that folder it's own option. This is the old /app placed system folder.

Some ROM's for older devices places a lot of different system content into /data, like /system/lib ~> /data/lib_s, /system/framework ~> /data/framework_s and so on. This is what I added the /data/[name]_s support for. All of this content is something that should have been on the real system, but where the device did not have enough space for it. So this content should be altered. Instead I have my older /data/app-system folder from prev. versions, which I will use for the apps feature of converting apps to and from system apps.

The reason why I said you should use /data/app_s instead of /data/app-system, is because /data/app-system is currently using the regular apps options. So if you moved /data/app to /sd-ext, then /data/app-system will be moved as well. And since you have problems with themes placed on sd-ext, this would not help you much.
[Android Software/Hacking General [Developers Only]] Rashed97:
Hm OK, thanks for the explanation BTW ;)

Another idea: Do you think it would be possible to use the /cache partition as a supplement to /system on devices with tiny /cache? For example, my device (P506- based on the P500) has a 64 MB /cache which is too small for anything, so we moved the cache to /data which leaves us with an empty /cache partition. So I was thinking if we could use that to store some of the /system overflow for our device (190 MB /system) instead of using /data/[folder]_s.
[Android Software/Hacking General [Developers Only]] dk_zero-cool:
Not possible without alering the ramdisk. Android clears the cache partition on each boot. Only folders defined in the ramdisk gets to stay.
[Android Software/Hacking General [Developers Only]] Rashed97:
Hm OK. Why does Android's file system and mounting have to be so complicated? :p
[Android Software/Hacking General [Developers Only]] swat4samp:
thanks..here's the link http://xdaforums.com/showthread.php?t=2406559

Ha ha ours is a low end device with only 280mb ram..so there wouldn't be official update
[Android Software/Hacking General [Developers Only]] acestars:
[MENTION=4662457]Rashed97[/MENTION]

Why dont you try to resize your cache and move it's space to data?

link:

http://xdaforums.com/showthread.php?t=717874

http://xdaforums.com/showthread.php?t=754805

[MENTION=3147360]dk_zero-cool[/MENTION]

did you remove the feature of mount /data/local/tmp to /sd-ext/data@local@tmp? i just aware recently :D

Sent from my Z71
[Android Software/Hacking General [Developers Only]] dk_zero-cool:
A new update is out which should fix the issues that has been mentioned here in the last couple of days. If you still encounter an issue, please use the Bug system for this thread. It makes it easier to keep track of issues.

Also, I have added an SQLite3 installer to the Application Settings. To many ROM's has broken SQLite3 binaries because ROM makers does not seam to know that it needs a few libraries to work. So they include the binary, but forget about the dependencies. You can use this if you have problems with the Storage Threshold.
[Android Software/Hacking General [Developers Only]] swat4samp:
Did u look into my ROM sir? Well dev said that CM doesn't support app2sd script. Is that the reason i am getting bootloops?
[Android Software/Hacking General [Developers Only]] gu5t3r:
I use sqlite3 from Titanium Backup, it's has 300kB and probably has all built-in in binary... (and it's also latest version I could find for ICS Arm; 3.7.6.3)
[Android Software/Hacking General [Developers Only]] dk_zero-cool:
If you can attach it, I could have a look at it?
[Android Software/Hacking General [Developers Only]] gu5t3r:
Here =)

All three from TB apk assets directory.
[Android Software/Hacking General [Developers Only]] viditbhargava:
Hi,

I am having a bit of a problem since the past few months since I started using Mounts2SD...may be this issue has been discussed before.

It is not a direct issue with Mounts2SD but rather a 'side-effect'.

Ok, here is my configuration:

Phone: Nexus One

Recovery: 4EXT

Hboot: Blackrose 160/8/268

SD card: 4gb stock...1GB EXT4 partitioned using 4EXT recovery

ROM: Evervolv Nightly (August 19 2013) Android 4.3 slimmed down to fit 160MB system (have this problem with other ROMs as well)

Mounts2SD: Reversed mounted, with Dalvik writes to internal data, and applications and data write to SD-ext. Cache is set to auto.

Before installing mounts2sd, if I go to System Settings -> Developer Options, it works fine.

After installing mounts2sd and configuring it, invoking Developer options causes Settings to crash every time and shows message 'Unfortunately, Settings has stopped.'.

I have had this problem with other ROMs as well (including Evervolv and CM10.1 ports). Even using the full version of the ROMs (as opposed to the slimmed down versions), does not fix this issue.

Thanks for the help.
[Android Software/Hacking General [Developers Only]] Skippernl:
Reverse mount has been removed in the new beta.

You can try this version. Location is in the OP

Skippernl

Verstuurd vanaf mijn HTC Desire met Tapatalk 4
[Android Software/Hacking General [Developers Only]] hacktrix2006:
Hi got a error on latest version that needs a look at DK, Its running like but not sure why the error is showing.

This is whilst running Sense 4.1 from mygamers. I don't get the error with CM10.1 or even CM10.2 so i know its based on the Sense rom but need to know where to look to resolve the Warning and Error.

Thanks in advance.

Other then that its working very well for me on Desire HD.
[Android Software/Hacking General [Developers Only]] dk_zero-cool:
Reversed mount has always caused problems. This is why it has been removed in the new release. Just disable rmount to fix your issue.

Your ROM already has something using the sd-partition and m2sd was not able to unmount it to do it's work.
[Android Software/Hacking General [Developers Only]] hacktrix2006:
right will look to see if there is any other script in the rom that is touching sd-ext.
[Android Software/Hacking General [Developers Only]] dk_zero-cool:
If so, let me know and I will add it to the auto remover. But it could also be included in the ramdisk, which would be a problem.
[Android Software/Hacking General [Developers Only]] hacktrix2006:
The only thing i can find is stuff in the etc/init.d folder which has some tweaks which talks to the whole SDcard in one go so going to edit the tweaks and see if that helps if it does i will gladly let you know.
[Android Software/Hacking General [Developers Only]] viditbhargava:
Thanks for the prompt response.

I downloaded and installed the version 3.2.0 and configured it.

Now the phone does not show the correct internal memory. It should show approx 1.0 GB as total memory but shows only 268 MB, which is the hboot partition size. Everything else seems to be working fine though.

Also, can you please provide a zip file for this version to flash via 4EXT recovery?
[Android Software/Hacking General [Developers Only]] dk_zero-cool:
The new app does not support rmount, so the real internal data is mounted as /data. Like mentioned above, rmount caused to many problems and was removed, so yes, the app does show the real data.

Recovery package will come once I add this to play store.