yashsingh1/xdaforums huggingface dataset:
[Android Software/Hacking General [Developers Only]] dk_zero-cool:
People need to read the whole message. It says that the script could not be copied to the init.d folder, and that HTC owners should make sure that they don't have S-On. It does not say that you specifically DO have S-On, only that this COULD be the problem.

And if the older script does not work either, then you need to update your busybox (NOT from market), because that has always been the issue regarding version 4 of the script. Either that, or your system partition does not have any more space available.

The menu you get when you open the app, above the script install, you should see a busybox install or configure option (Depending on your specific busybox issue). Try running that first (After you check how much space you have on /system of cause)
[Android Software/Hacking General [Developers Only]] dk_zero-cool:
When the app is opened the first time after boot, it matches the MD5 of the script in init.d. If this does not match, you are sent to the settings menu where you will get the option to install the script. When you click, the script is transferred to the apps local folder (can't write to system from inside the app) and then the root class will move the script from the local folder into the init.d folder. After this, the app checks to see if the file exists in init.d and that it now matches the MD5. If not, you will get this error message.

What can go wrong?

1: mounting system as RW fails do to S-On

2: Busybox creates an issue with the command (Maybe some commands like MD5 is not supported by the current version)

3: System is full, so not the whole script was moved whereas the MD5 will not match

4: You tell me?

This is why the App is still not in stable version. There are still a few safeguards and fixes needed for the different enviroments. Android might be more or less the same on each device, but the shell depends on things like busybox which are never the same for each device. Some commands are missing in some versions, while other commands are more limited than others and so on.

So check some of the things mentioned and let me know. That way I can add more scenarios.

The App has been tested on HTC One X (4.0.3), Samsung Galaxy Y (2.3.6), HTC Desire (4.1.1) and Samsung Galaxy SII (4.0.3). I have no more phones to test on, and it works fine on these (Of cause the One X complaints about missing sdcard since the device does not support external cards)
[Android Software/Hacking General [Developers Only]] dimmy1405:
I installed the latest rom from vijendras... and the phone is fully clear, there is free space... i installed busybox since it requested, the problem persisted at the 2nd request about the init.d.... however i installed the older version aroma from recovery....
[Android Software/Hacking General [Developers Only]] Fleky911:
go to system/app and delete some app

that solved problem for me
[Android Software/Hacking General [Developers Only]] knsys:
I just tried the new app + new version of script and the same thing happens. Eternal rom loading animation (30minutes+), flashed back old aroma and things go fine
[Android Software/Hacking General [Developers Only]] dk_zero-cool:
New version which should fix most if the problems, also for people with S-On or other installation problems, as the APP now will reboot into recovery and run an update.zip if installation fails from inside the OS.

I have also added separate update.zip files for both the older MTD devices and the newer Ext4 devices. This is usefull when updating an OS that already has the script installed with content moved to sd-ext.

If you have any issues, please add a log. It can be saved to the sdcard from inside the Log Viwer. And, if possible, enable debug first as it will provide a more extended log entry.
[Android Software/Hacking General [Developers Only]] pedrofidalgo:
So i have s on, and im not understanding, i have to install the apk, configure the busibox, and then at .zip i have to install throw recovery to make the script work well ?
[Android Software/Hacking General [Developers Only]] dk_zero-cool:
No. You have two options

1: Install the APK, on first run you will get the option to install the script. This will of cause fail as you have S-On which will invoke the APPs auto recovery installation. In other words, the phone will reboot into recovery, auto install the script and reboot back into Android.

2: Download one of the ZIP files instead (The one that matches your device). Flash it in recovery which will install both the Script and the APK.
[Android Software/Hacking General [Developers Only]] knsys:
I tried your last app, and this time the bug is solved and the rom starts flawlessly :)

But app-asec is still not moved, I attach you the debug version of the app log (All seems good)

Thanks for your awesome script :)

EDIT:

Found the bug, you got a typo:

d/Looking in /data/app-assec to see if something should be moved into /sd-ext/app-assec

v/Attaching /sd-ext/app-assec to /data/app-assec

It's app-asec with ONE "s"
[Android Software/Hacking General [Developers Only]] zikyHD:
Hi!

Is it possible to add an option in Mount2SD to move "/data/data/*/lib" in sd-ext instead of moving all the folder "/data/data" like in the app link2sd? It saves a lot of space on data without loosing performance.
[Android Software/Hacking General [Developers Only]] dk_zero-cool:
My mistake. I have typed assec instead of asec. Will fix this as soon as I have time. But glad its finally working. May I ask which package you used?
[Android Software/Hacking General [Developers Only]] knsys:
I've used the new version of the App to install the script. So at least on the nexus one the app is working and stable :)
[Android Software/Hacking General [Developers Only]] Prof.Dr.Moura:
R-mount not working

I´ve being using the m2sd on evervolv nexus one for almosta a year now.. always using this fantastic m2sd, the flashable legacy zip.

Now I am testing the new Evervolv android 4.2 version... when i flash the legacy, I do loose access to the play store. So I tried the new apk. Everything is working, however I cannot user the r-mount option I am used to!

Under the Reversed Mount on the apk, it says: It was not possible to move the internal data mount point!

Anyone has any ideas???
[Android Software/Hacking General [Developers Only]] dk_zero-cool:
It means that the command "mount --move /data /sd-ext" failed. I will need a complete bootup logcat in order to find the issue, it will contain any shell errors which is not in the regular log.

I am no Windows shell expert, in Linux I would turn the phone off, plug-in the USB cable, run the command "adb logcat | grep -i mounts2sd" (which will sort out any non-m2sd related log entries) and turn the phone on.

This is most likely an issue with the init.d method. If evervolv runs init.d as a service rather than an execute command, the boot process is not stalled while init.d is running, and /data might be used by some boot process making it impossible to move the mount point do to a busy signal. But again, a complete logcat will help more.

In the mean time, I will look for script bugs regarding this issue
[Android Software/Hacking General [Developers Only]] pedrofidalgo:
Every time i used the re-mount option, and i install pimp my rom, i get a lot of fc's .. i think its related to davilk cache, since the recovery cant wipe it .. it should appear something like: optimizing app 3 of 99 and it dont .. i think its because it dont wipe davilk
[Android Software/Hacking General [Developers Only]] dk_zero-cool:
Almost all recoveries has sd-ext included, which means that they wipe both /data/dalvik-cache and /sd-ext/dalvik-cache. I would switch my recovery if yours don't.

However, if your phone runs m2sd in safe-mode and you disable this in order to use r-mount, then there is your problem. Safe-mode means that the device will not work well with r-mount which is why safe-mode was added. Some times it will work with dalvik-cache, and maybe moving /data/data, which is why I made an option to disable it. But r-mount will almost never work in this situation.
[Android Software/Hacking General [Developers Only]] dk_zero-cool:
And the /data/asec typo has now been fixed ...
[Android Software/Hacking General [Developers Only]] Prof.Dr.Moura:
Ok... this is the best I could do!!! Any ideais?
[Android Software/Hacking General [Developers Only]] knsys:
Thanks alot!! Now it's fully working including app-asec :D
[Android Software/Hacking General [Developers Only]] nickyikra:
Work cm9 & cm10?

Sent From XDA Pertamax GT-S5830
[Android Software/Hacking General [Developers Only]] dk_zero-cool:
There is no errors, so no. From what I can see, it should work. Does for me. Will see what I can do at some point to get better info about this.

Any ROM with init.d support (which means most custom once, inc. all CM once), so yes
[Android Software/Hacking General [Developers Only]] nickyikra:
Ok, thkz

Sent From XDA Pertamax GT-S5830
[Android Software/Hacking General [Developers Only]] Trialz Nexus One:
:good:

Many thanks DK_Zero. I am now using the apk on my N1 with CM7.2 Euroskank of Dec17th. Worked perfectly!
[Android Software/Hacking General [Developers Only]] dk_zero-cool:
You can try with the new version. I added an additional attempt to reverse the mount point in case --move fails.

But again, if you have disabled safe-mode, please backup your data before attempting this.
[Android Software/Hacking General [Developers Only]] rkmiks:
My samsung galaxy Y keeps on showing the boot animation and doesn't start with the new script and application. However the older script used to work perfectly.
[Android Software/Hacking General [Developers Only]] dk_zero-cool:
Not in any way to sound like an ass, but how do you expect me to help you with this little infomation? I have a Galaxy Y my self as test Phone which is working perfectly fine with this. I need more if I am to help. Grap a logcat while you try to boot your phone. That should contain some infomation about the reason to this issue.

You can search google on how to get a logcat if you don't already know how.
[Android Software/Hacking General [Developers Only]] CsabiDuke:
The software on my Xperia Arc S is always stops after the initialize. :(

Somebody know this issue?

After I reboot with the script, the /sd-ext size is 0.0/0,0MB in "Partition Table" program from Market. Like if not mounted.

My config:

Kernel: [KERNEL]ARC/S-Advanced stock-4.1.B.0.587-[ROOT+INIT.D+CWM+SD-EXT]

Rom: [ROM]=- Xperia Ultimate HD™ 2.0.2 -= [ Fastest ICS ROM ] & [ Most Stable + Best UI ]

Rooted, open bootloader.
[Android Software/Hacking General [Developers Only]] dk_zero-cool:
It it shows 0Mb, then it is most likely not mounted. Could you please provide the log? You can save it to the sdcard from within the Log Viewer. I cannot guess what the problem is, as it could be a lot of different things. So the log for starters would help.
[Android Software/Hacking General [Developers Only]] ForMartha:
Hey DK,

I'm using Evervolv's (Derwis - Texasice) 4.2 rom for N1, and i wanted to use the APK that you provided.

after restarting the phone - i saw that the R-mount didnt work..

i had to Nandroid back to 4.1,

what can cause the problem?

BTW why the BCM project has stoped? i miss it a lot! it was the best!!...

Bye.
[Android Software/Hacking General [Developers Only]] dk_zero-cool:
Many things, a log would help. However, the script do have safe guards for this that makes sure that even if rmount fails, the other settings adapt so that all content remains on the same partitions. So don't see why you would need to do a nand restore?

It did not stop. It moved to the SpazeDog thread which should be getting an update soon. Just had other projects, like this one, that also needed some more attention. It can all be a little time consuming and it can be difficult to find the time for everything.
[Android Software/Hacking General [Developers Only]] CsabiDuke:
Where can i find the Log Viewer? On the Market? :)
[Android Software/Hacking General [Developers Only]] dk_zero-cool:
Open the app and click on "View Log".
[Android Software/Hacking General [Developers Only]] CsabiDuke:
Ok. The app is not opening. After the initialize, it stops every time with warning :-/

I make a full fresh rom install.
[Android Software/Hacking General [Developers Only]] dk_zero-cool:
And what is the warning?
[Android Software/Hacking General [Developers Only]] CsabiDuke:
"the application is stoped." "Report", "OK"
[Android Software/Hacking General [Developers Only]] dk_zero-cool:
Well that does complicates things. I will need a different log for this. You need to grab the logcat while opening the app. Search logcat on play store, you can find an app to grab the it with.
[Android Software/Hacking General [Developers Only]] CsabiDuke:
I made a full rom reintall. The issue is same. The app is run first nice. Everything seems ok, apply the bussybox, and the script to the init.d. And after reboot the phone, the app is chrash allways. Attached some screenshot. I will do logcat tomorrow. Thank you the lot of help!
[Android Software/Hacking General [Developers Only]] ForMartha:
thanks for the lightning quick answer.

FYI - I've downloaded the new app from the Playstore (finaly you made it go there... the best ext script program out there).

and everything works like charm.

only thing is that entering the app seems pretty slow ..

thanks for everything,

wating for updates in SpazeDog rom :]

Mor
[Android Software/Hacking General [Developers Only]] dk_zero-cool:
The first launch after a reboot or app update is slow because all the script properties, busybox status check, superuser checks an all that is loaded into the apps configurations. After that, everything runs from the apps shared preferences and should not slow down the launch. I made it this way to limit the usage of the root account. This way the app does not have to gain root every time you open it, only when you change something in the configurations.

This is only done ONCE after each phone reboot. And most of the time, it should be handled by the boot listener in the background when the phone boots. If it loads forever each time you open it, let me know, because then something has to done. That is not the idea.
[Android Software/Hacking General [Developers Only]] flippy12:
I just discovered this script, and applied it.

The script is correctly applied, I can see with TB that space is now occupied on the sd-ext partition.

But I have the same problem with the app: Busybox is correctly configured, and the script for init.d can't be applied. And then, the app always crash during the "Loading Configurations".

For info: my sdext is formatted as ext4, and I installed the package "Ext4 ZIP" by recovery.
[Android Software/Hacking General [Developers Only]] dk_zero-cool:
I still need a logcat of the crash
[Android Software/Hacking General [Developers Only]] flippy12:
Ok, I will extract one, let me some time for some tests and then to recover my last backup ;)

Here is that I saw for the moment:

- At the 1st boot (after package installation EXT4), it seems that some partitions remains unmounted (sdcard, cache). I didn't unmount them myself.

- After installation, when I launch the app the 1st time, script init.d can't be copied in the system (I launched file explorer, and it can't see anything): I suppose that it's due to the unmounted partition.

- So I reboot and mounted manually the partitions, boot, and when I launched the app, it creates the script in init.d and close immediatly the app (I just had time to see the checkbox to become green-ok).

If I try to launch it again, it crashes.
[Android Software/Hacking General [Developers Only]] CsabiDuke:
I made the logcat. It is showing a warning when I start the program:

2012-12-20 13:34:58.110 E 5638/AndroidRuntime: FATAL EXCEPTION: AsyncTask #1
java.lang.RuntimeException: An error occured while executing doInBackground()
at android.os.AsyncTask$3.done(AsyncTask.java:278)
at java.util.concurrent.FutureTask$Sync.innerSetException(FutureTask.java:273)
at java.util.concurrent.FutureTask.setException(FutureTask.java:124)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:307)
at java.util.concurrent.FutureTask.run(FutureTask.java:137)
at android.os.AsyncTask$SerialExecutor$1.run(AsyncTask.java:208)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1076)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:569)
at java.lang.Thread.run(Thread.java:856)
Caused by: java.lang.NumberFormatException: Invalid int: "N may be suffixed by k (x1024), b (x512), or m (x1024^2)."
at java.lang.Integer.invalidInt(Integer.java:138)
at java.lang.Integer.parse(Integer.java:375)
at java.lang.Integer.parseInt(Integer.java:366)
at java.lang.Integer.parseInt(Integer.java:332)
at com.spazedog.mounts2sd.SettingsHelper.loadConfigs(SettingsHelper.java:281)
at com.spazedog.mounts2sd.StatusActivity$LoadConfigsAsync.doInBackground(StatusActivity.java:73)
at com.spazedog.mounts2sd.StatusActivity$LoadConfigsAsync.doInBackground(StatusActivity.java:1)
at android.os.AsyncTask$2.call(AsyncTask.java:264)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:305)
... 5 more
[Android Software/Hacking General [Developers Only]] dk_zero-cool:
Great thanks. This makes it a lot easier. Will fix this later to day :)
[Android Software/Hacking General [Developers Only]] CsabiDuke:
Big THANK YOU! And also for the great app. :)
[Android Software/Hacking General [Developers Only]] dk_zero-cool:
The problem (From the looks of CsabiDuke's log) is that your busybox versions does not support the 'head' command in the matter of which it is used (The command is used to get the first line of a file). So I have switched the command to 'sed' instead which I know is proper supported in most versions of busybox. So install Mounts2SD 1.0.2 and see if that helps. Note that Play Store might take several hours to send out the update, but if you don't want to wait, just use some of the other manual downloads from the first post.

If you get any further issues with the new version, then we will have a little private testing party until everything works :) But this should do it, at least for the Crash Issue.
[Android Software/Hacking General [Developers Only]] CsabiDuke:
Nice!! The new version is installed, and it is running. But there is an error message: sd-ext can not be mounted... :(((

Attached the log file.
[Android Software/Hacking General [Developers Only]] dk_zero-cool:
Since busybox was the cause of your last issue, it is likely that it is the cause of this as well. I think it would be a good idea to update your busybox and see if that helps.

Try running this in your recovery. It will install and configure a busybox version that I know works properly. Also, could you first extract /system/xbin/busybox from your phone. If that is the root of your problems, I would like to play with it to see how limited it really is.
[Android Software/Hacking General [Developers Only]] CsabiDuke:
I reinstalled the system. I tried it without the busyboxinstaller, after with the installer. Sd-ext mount failed... :mad: :,,,,(
[Android Software/Hacking General [Developers Only]] dk_zero-cool:
Are you able to grab a logcat during boot? The mount command properly prints an error massage
[Android Software/Hacking General [Developers Only]] k0nt0l3:
Help.. Its work for my device or not?

I'Ve intall this app from google play. configuring busybox and script ok, but nothing happen even i restart my device. may I miss something? and the log file just have "Null".

My device : Acer Liquid z110

OS : GB 2.3.6

My microsd : 1st Partition FAT32 15GB (Primary)

2nd Partition EXT2 15 GB (Primary)

3rd Partition Swap Linux 2 GB (Primary)
[Android Software/Hacking General [Developers Only]] sawaldibali:
dear dk,

usually i'm using link2sd, today i try mount2sd by you...

1. i still got error/warning after reboot like pict i attach. is it bad? unfortunately i dont know how to do logcat:(

2. then i disable file system check, there is no error/warning. is it good?

3. but, i think its working, my app move to sd-ext.

btw, i still use link2sd to move some app that still on sdcard, but when i try move to internal, they are go into sd-ext that why my sd-ext is almost full.

so far i like with how mount2sd working... will use it from today:D

its great app.. and thank you very much.

device : HTC One V unlock bootloader/s-on

sorry for my bad english
[Android Software/Hacking General [Developers Only]] rkmiks:
Earlier I had reported that the this app was not working on my Samsung galaxyY . But now the Latest version works for me. However I have noticed that the it takes much more time to boot than the older version. My Ext partition is Ext2 , but when i select filesystem as Ext2 it shows an error message. And so does the filesystem check option. I have tried to grab a log both from adb and the application. However I don't know its helpful or not. Hope this helps to make this app better. Thanks
[Android Software/Hacking General [Developers Only]] dk_zero-cool:
Could be a busybox issue of your current version. I need a logcat from boot to see what is going on.

You have errors on your sd-ext partition. e2fsck tries to fix it, but is unable to. Disabling file system check removes error because the script is no longer checking the file system, it does not mean that the errors is gone.

This is most likely some corrupted blocks on your partition. You can format your sd-ext partition which could fix it, but no guarantee. It will properly not affect anything as the corrupted blocks will just be parsed by when writing to the disk (They will not be used).

I would properly make sure that your file system really is ext2. It seams that it is not as auto mode is working just fine. Try setting it as ext3 or ext4 and see what happens. My guess is that ext4 will work just fine, as you properly used your recovery to format sd-ext. And most recoveries uses ext4 as default. Those that don't, use ext3.

This all depends on the kernel and the modules that they implement. So if you are 100% sure that yours is ext2, then there could be an issue with your kernels modules identifying them as something else. Or the program you used to format your sd-ext could have an issue making their file systems being identified as something that they are not.

In any cases, this is not a script issue.
[Android Software/Hacking General [Developers Only]] BleedingIris:
@dk zero cool

What was the busybox version you posted?
[Android Software/Hacking General [Developers Only]] CsabiDuke:
HI!

The entries from logcat where the mounts2sd in the row at boot:

2012-12-21 17:59:43.712 W 1629/PackageManager: Not granting permission android.permission.REBOOT to package com.spazedog.mounts2sd (protectionLevel=3 flags=0x8be44)

2012-12-21 17:59:55.202 W 1629/PackageManager: Not granting permission android.permission.REBOOT to package com.spazedog.mounts2sd (protectionLevel=3 flags=0x8be44)

2012-12-21 17:59:58.802 I 1629/ActivityManager: Start proc com.spazedog.mounts2sd for broadcast com.spazedog.mounts2sd/.StartupReceiver: pid=2303 uid=10076 gids={1015}

2012-12-21 18:00:14.618 I 1629/ActivityManager: No longer want com.spazedog.mounts2sd (pid 2303): hidden #16
2012-12-21 18:00:27.288 I 1629/ActivityManager: START {cmp=com.spazedog.mounts2sd/.StatusActivity bnds=[0,112][480,208]} from pid -1

2012-12-21 18:00:27.298 W 1629/ActivityManager: startActivity called from non-Activity context; forcing Intent.FLAG_ACTIVITY_NEW_TASK for: Intent { cmp=com.spazedog.mounts2sd/.StatusActivity bnds=[0,112][480,208] }

2012-12-21 18:00:27.608 I 1629/ActivityManager: Start proc com.spazedog.mounts2sd for activity com.spazedog.mounts2sd/.StatusActivity: pid=6854 uid=10076 gids={1015}

2012-12-21 18:00:28.268 I 1629/ActivityManager: Displayed com.spazedog.mounts2sd/.StatusActivity: +711ms (total +29s215ms)

2012-12-21 18:00:30.018 I 1629/ActivityManager: START {flg=0x10000000 cmp=com.spazedog.mounts2sd/.LogActivity} from pid 6854
20

2012-12-21 18:00:30.368 I 1629/ActivityManager: Displayed com.spazedog.mounts2sd/.LogActivity: +334ms