yashsingh1/xdaforums huggingface dataset:
[Android Software/Hacking General [Developers Only]] peppelt:
Sorry for my bad english. Your phone is rooted? My sister can't root her acer z110 duo
[Android Software/Hacking General [Developers Only]] sawaldibali:
1. i try format sdext use cwm recovery, no luck for me it give me error E:can't mount sdext... then i using mini tool partition to formated, then running mount2sd w/ file system check enable, still give me error and there is one more error appear.

2. next, i am doing factory data reset on cwm which is still error at E:can't mount sdext... but after that i start mount2sd w/ file system check enable, error/warning gone.

i don't know what happen here:confused::confused:

is it fully working now?

thanks

sorry for my bad english
[Android Software/Hacking General [Developers Only]] dk_zero-cool:
The logcat is not complete. Your missing the beginning of the log, which means all the important M2SD entries.

From these screenshots, the script has been working fine all along. The issues you had was handling journal and you got some errors from the file system check. The rest however has been working fine, the partition was mounted, content was moved to sd-ext and so fourth.

Your biggest problem is using CWM to format the partitions. This recovery is known to f*** up your file systems, both the sd-ext and the regular fat32. Use another recovery to format your partitions, or do it from your PC.
[Android Software/Hacking General [Developers Only]] Dr.Thrilla:
Hi Dk, I just wanted to show my eternal gratitude here for the amazing work you've done.

I never would have thought that I still would use my old G1 after so long time. I am running Evervolv 4.2.1 from the 19 Dec without any problems. Installation has been like a walk in the park. Thank you for all the time and effort you've put in to this.

For the people that would like to know. I am always using 4ext as my recovery. I partitioned 1024 ext4 and 256 swap but swap it not supported by this rom. This has been the first time that I left the fat32 partition intact. Simply because I am abroad and I don't have my PC with me.

I installed Mounts2sd from the market after I installed the Rom and tiny gapps. ( I let it settle first)

I moved apps, dalvik and cache to sd-ext. Left journal of course disabled. Check file system on boot. Then I rebooted and let the phone settle for a couple of minutes.

Hope it is useful to someone.
[Android Software/Hacking General [Developers Only]] sawaldibali:
ok, thanks for tips, I'll looking for another recovery, and great thanks for the app.

sorry for my bad english
[Android Software/Hacking General [Developers Only]] rkmiks:
I don't use cwm recovery to format the sd-ext , I use minitools partition wizard on pc to format the ext and i use ext2 or ext3 because ext4 is not supported on my kernel. Every time i install the scripts it works fine for the first time with filesystem error and after one or two reboots the apps start force closing and when i again check the filesystem it automatically gets changed to ext2 no matter earlier it was ext2 or ext3. I cannot figure out whats wrong the script or the kernel or the ROM or the partition formatting software. But I get no errors mounting the ext partiton with link2sd .
[Android Software/Hacking General [Developers Only]] dk_zero-cool:
Most other scripts does not look for issues.

But I will need a log when your issues start in order to try to fix it. Also enable debug.
[Android Software/Hacking General [Developers Only]] elcocolo50:
Thats happen to me and I lost everithing this ereased my sd card and intenal memory and I have 2gbs lost.
[Android Software/Hacking General [Developers Only]] jcgechevarria:
Sorry if thats a noob question, what i need is custom rom or custom kernel?
[Android Software/Hacking General [Developers Only]] dk_zero-cool:
You need a custom boot.img with init.d support. The kernel and ROM does not matter. It's the ramdisk inside the boot.img that contains the init.d execution.

You can even add this to the original yourself if you know how.
[Android Software/Hacking General [Developers Only]] encik_racun:
On galaxy y we dont need that, only apply a simple term-init mod then the init.d will work...

Spoiler content hidden.
[Android Software/Hacking General [Developers Only]] mai77:
on Galaxy Y putting /data & apps on SDcard works like a charm. :D

however, the revert mount point function ends in "stuck in boot logo". :crying: :(

everything else can be made to work nicely. :good: :o
[Android Software/Hacking General [Developers Only]] Zapdude:
Hello, i ve downloaded the latest version zip file. I would like to know how can i install it in my ROM and pre-configure it before flashing the ROM on my phone. Since there is no shell command m2sd anymore im a little lost here. Could someone please help me?

Thank you.
[Android Software/Hacking General [Developers Only]] CsabiDuke:
Hi DK!

I made a new fresh logcat. Maybe this will good.
[Android Software/Hacking General [Developers Only]] playitlouder:
Hi,

I heard from your script a few weeks ago, and installed it on a HTC Desire with the Aroma installer without any problems whatsoever.

Great!

Then I updated a Sony Ericsson X10Mini Pro to 4.1.2 (MINI CM10), works great so far!

The only problem was, that i didnt had enough internal memory, so I decided to try your script again.

I used the App this time. I had some problems installing busybox, but Version 1.19.3 finally worked.

I set my prefered settings in your app and rebooted.

But your script has some problems with my SD, it is not able to mount the SD_EXT partition, no matter if I format it in Clockworkmod or on my PC . I even erased the partition table and tried again.

The Recovery can mount the /sd_ext without problems and it is ext4 formated (i heard that should give the best performance), oh by the way, it is a Kingston 8gb Class4 card.

I did a log cat, and try to attach it onto here, maybe someone can help me :good:
[Android Software/Hacking General [Developers Only]] dk_zero-cool:
There is still not start entry. You need the very first part of the log, this contains the last part.

Thanks. I see the issue in the log, but I need to be sure about the solution and the main problem before adding it to the script. So could you try opening a terminal on your phone and type

busybox mount /dev/block/mmcblk0p2 /sd-ext

If this does not provide an error, then try typing

busybox umount /sd-ext
busybox mount -t ext4 /dev/block/mmcblk0p2 /sd-ext
[Android Software/Hacking General [Developers Only]] daemonarch21:
im getting all the time a warning everytime i reboot.at logs says: Error detected while checking sd-ext.Auto correction was performed!.Running CM7 at my HTC Desire.4ext recovery and my old script was the latest with the aroma installer u have.
[Android Software/Hacking General [Developers Only]] playitlouder:
It seems to have worked :cyclops:

127|root@android:/ # su
root@android:/ # busybox mount /dev/block/mmcblk0p2 /sd-ext
root@android:/ # busybox umount /sd-ext
root@android:/ # busybox mount -t ext4 /dev/block/mmcblk0p2 /sd-ext
root@android:/ #

I think you can apply the fix in your app :p

Oh and what do you think, which partitions should I move to the SD?

I have tinked Applications, Dalvik Cache and Cache to the SD i heard somewhere that this would be the best configuration. Is that true?
[Android Software/Hacking General [Developers Only]] qbase775:
Unfortunately it didn't work for me. I'm also running CyanogenMod 7.2 on my Nexus One. I switched to 4EXT and recreated all partions on the sd-card with 4EXT. I still get stuck at the Nexus boot logo, is 10 minutes long enough? I created a 1.5Gb ext4 partion on my class 10 sd-card...

I installed Mounts2sd from the Play store and applied the default settings.

Any ideas how to solve this?
[Android Software/Hacking General [Developers Only]] dk_zero-cool:
read what it says.

I will get working on this :)

No idea without a log
[Android Software/Hacking General [Developers Only]] CsabiDuke:
I don't know where is the start of the log. I send the original logcat after the boot. What should i do?
[Android Software/Hacking General [Developers Only]] playitlouder:
I did the logcat through the Android SDK.

Open ddms in the tools folder. Connect your phone and reboot it. Set the log settings in the right center to debug. Wait, until the phone fully booted up, then click one log entry and press 'STRG'(or CTRL depending on your Keyboard Layout) and 'A'. After that hit the little diskette icon, give the logcat a good name and attach it to here.

What do you think how long you have to work on the bug I experienced? (I want to use the Phone :p)
[Android Software/Hacking General [Developers Only]] dk_zero-cool:
It will be uploaded within a few hours
[Android Software/Hacking General [Developers Only]] dk_zero-cool:
Just flash the ROM and then flash M2SD. After that, reboot into the system, open the app, change the default settings and reboot the phone.

If you have already configured M2SD and then flashed a ROM without formatting your data partition (Factory reset), then just flash the script afterwards. All your prev. settings will remain intact as they are saved in /data/property.

Try version 1.0.4 and see of it works for you now. I have implemented multiple mounting attempts with different options in order to gain a successful mount on devices with limited support of mount options, which seams to be the problem on your device.
[Android Software/Hacking General [Developers Only]] Zapdude:
Hi,

Thank you for your reply. Im customizing my ROM on my pc, i want to pre-configure m2sd so after i flash my ROM i wont have to make any changes to m2sd can i do that in some way? is there a settings file?

thanks again
[Android Software/Hacking General [Developers Only]] dk_zero-cool:
I will write a list on the first page tomorrow explaining the configs which you can use
[Android Software/Hacking General [Developers Only]] playitlouder:
Thanks a lot!

It works fine now, great job! :good:
[Android Software/Hacking General [Developers Only]] Sepero:
I have looked over the script and you have some very intelligent code writing in the file. If I may add a humble humble humble critique- this code would be more clean/readable (and possibly more maitainable) if it made heavy use of functions to take care of set tasks. It otherwise looks like great stuff. I only wish I had more time, so I could help contribute. Great stuff.
[Android Software/Hacking General [Developers Only]] dk_zero-cool:
I use functions in the script for things that is used multiple times. It's true that you could add some more for some other stuff as well, but every tiny thing you change, ends up creating some sort of problem for some device or some busybox/toolbox version and takes time to adjust, meanwhile creating a lot of issues for people that is using it. So if I was to rewrite everything in order to split things into more functions, it could end up breaking a lot of devices that I and the users of them have spent a lot of time fixing.
[Android Software/Hacking General [Developers Only]] qbase775:
Ok, I made three logs. Not sure what logs you need :o

log-installation.txt - which a log from when I ran and configured mounts2sd(play store).

log-boot.txt - the first boot.

log-boot-after-flashed-busybox.txt - I flashed your busybox zip file after the first boot failed and rebooted once again.

Still running CyanogenMod 7.2 on my Nexus One.
[Android Software/Hacking General [Developers Only]] Zapdude:
Thank you very much ;)
[Android Software/Hacking General [Developers Only]] dk_zero-cool:
From what I get from the log, you have another script that is messing with the sd-ext partition. Do a nand restore, locate and delete that script before installing this. Also if you could give me the name of it so that I can add it to the auto delete script which should remove any existing scripts.
[Android Software/Hacking General [Developers Only]] qbase775:
I haven't installed any scripts that I know of. I'm running standard CyanogenMod 7.2 which I reflashed last week. I have restored a few apps from Titanium backup.

# pwd

/system/etc/init.d

# ls -la

drwxr-xr-x 1 root root 2048 Dec 29 12:04 .

drwxr-xr-x 1 root root 2048 Dec 29 12:04 ..

-rwxr-x--- 1 root shell 365 Dec 29 12:04 00banner

-rwxr-x--- 1 root shell 27 Dec 29 12:04 01sysctl

-rwxr-x--- 1 root shell 229 Dec 29 12:04 03firstboot

-rwxr-x--- 1 root shell 201 Dec 29 12:04 04modules

-rwxr-x--- 1 root shell 1452 Dec 29 12:04 05mountsd

-rwxr-x--- 1 root shell 445 Dec 29 12:04 06mountdl

-rwxr-x--- 1 root shell 925 Dec 29 12:04 20userinit

#

Thank you for helping me.
[Android Software/Hacking General [Developers Only]] dk_zero-cool:
05mountsd and 06mountdl should not be there, and 10mounts2sd is missing (this script). However the two cm scripts should be auto removed when installing m2sd
[Android Software/Hacking General [Developers Only]] qbase775:
This is how it looks when Mounts2sd has been installed. The init scripts looks OK, but it's not working.

I tried changing the owner of your script, but it's not possible. Perhaps that's normal, I haven't used the adb shell that much :eek:

# chown root:shell 10mounts2sd

chown: 10mounts2sd: Read-only file system

# pwd

/system/etc/init.d

# ls -la

drwxr-xr-x 1 root root 2048 Dec 29 22:04 .

drwxr-xr-x 1 root root 2048 Dec 29 12:04 ..

-rwxr-x--- 1 root shell 365 Dec 29 12:04 00banner

-rwxr-x--- 1 root shell 27 Dec 29 12:04 01sysctl

-rwxr-x--- 1 root shell 229 Dec 29 12:04 03firstboot

-rwxr-x--- 1 root shell 201 Dec 29 12:04 04modules

-rwxrwx--x 1 root app_86 64981 Dec 29 22:04 10mounts2sd

-rwxr-x--- 1 root shell 925 Dec 29 12:04 20userinit

#

# pwd

/

# ls -la

drwxr-xr-x 15 root root 0 Dec 29 22:05 .

drwxr-xr-x 15 root root 0 Dec 29 22:05 ..

drwxr-xr-x 3 root root 0 Dec 29 22:05 acct

drwxrwx--- 2 system cache 4096 Dec 29 22:06 cache

dr-x------ 2 root root 0 Dec 29 22:05 config

lrwxrwxrwx 1 root root 17 Dec 29 22:05 d -> /sys/kernel/debug

drwxrwx--x 1 system system 2048 Dec 29 22:06 data

-rw-r--r-- 1 root root 118 Jan 1 1970 default.prop

drwxr-xr-x 12 root root 1320 Dec 29 22:05 dev

lrwxrwxrwx 1 root root 11 Dec 29 22:05 etc -> /system/etc

-rwxr-x--- 1 root root 94452 Jan 1 1970 init

-rwxr-x--- 1 root root 1677 Jan 1 1970 init.goldfish.rc

-rwxr-x--- 1 root root 3469 Jan 1 1970 init.mahimahi.rc

-rwxr-x--- 1 root root 15332 Jan 1 1970 init.rc

drwxrwxr-x 6 root system 0 Dec 29 22:05 mnt

dr-xr-xr-x 81 root root 0 Jan 1 1970 proc

drwxrwx--x 2 system system 0 Dec 29 22:06 props

drwx------ 2 root root 0 Nov 13 2011 root

drwxr-x--- 2 root root 0 Jan 1 1970 sbin

drwxrwx--x 10 system system 4096 Dec 29 22:06 sd-ext

lrwxrwxrwx 1 root root 11 Dec 29 22:05 sdcard -> /mnt/sdcard

drwxr-xr-x 16 root root 0 Dec 29 22:05 sys

drwxr-xr-x 1 root root 2048 Dec 29 22:06 system

-rw-r--r-- 1 root root 0 Jan 1 1970 ueventd.goldfish.rc

-rw-r--r-- 1 root root 26 Jan 1 1970 ueventd.mahimahi.rc

-rw-r--r-- 1 root root 4078 Jan 1 1970 ueventd.rc

lrwxrwxrwx 1 root root 14 Dec 29 22:05 vendor -> /system/vendor
[Android Software/Hacking General [Developers Only]] dk_zero-cool:
You can't change permissions on the /system partition before you run "mount -o remount,rw /system" in order to remount it with write permissions. However, the perms does not matter as the script runs as root. Also I can see that the script does execute as the folder /props/ has been created (This belongs to M2SD).

Try booting your phone, if it get's stuck at the logo again, plug in your USB cable and use ADB to get the content of the file "/props/content.log". This is the log file created by the script and should tell us where it get's stuck.

From your latest post it seams that you know your way around the linux shell so I guess you know how to get file content from it as well?
[Android Software/Hacking General [Developers Only]] qbase775:
Yeah, been using linux for several years. But on Android I haven't done much more than rooting and flashing CyanogenMod...

This is after a couple of minutes:

# cat /props/content.log

v/Preparing configurations

v/Optimizing the internal nand partitions

v/Setting system nand readahead to 4kb

v/Setting optimized mount parameters on system

v/Setting data nand readahead to 4kb

v/Setting optimized mount parameters on data

v/Setting cache nand readahead to 4kb

v/Setting optimized mount parameters on cache

v/Waiting for sdcard to initiate

v/The sdcard device was located at /dev/block/mmcblk0

v/Setting sdcard readahead to 512Kb

v/Checking sdcard partitions

v/Using /dev/block/mmcblk0p1 as fat32 (sdcard)

v/Using /dev/block/mmcblk0p2 as ext4 (sd-ext)

v/Running file system check on sd-ext

w/Error detected while checking sd-ext. Auto correction was performed!

v/Setting optimized mount parameters on sd-ext

v/The sd-ext partition was mounted successfully at /sd-ext

v/Preparing to move content between /data and /sd-ext

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

v/Attaching /sd-ext/dalvik-cache to /data/dalvik-cache

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

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

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

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

v/Looking for new system apps in /data/app-system to link to /system/app

v/Preparing to replace the cache partition

v/Unmounting internal cache partition

v/Attaching /sd-ext/cache to /cache

#
[Android Software/Hacking General [Developers Only]] dk_zero-cool:
Hmm, the script runs all the way to the end, so wherever it hangs, it is not from the script. It could be something after the script which reacts badly to some of the content being moved.

Could you try restoring and installing the app again. This time disable all the content settings (Apps, Data and dalvik) and of cause no r-mount. That way the script will only mount sd-ext but not really use it for anything. Then enable one option at a time and reboot in between, starting with apps, then dalvik and data last.
[Android Software/Hacking General [Developers Only]] qbase775:
Configure Busybox and reboot - OK

Install script and disabled all content - boots up OK, but Mounts2sd notified me about an Error/warning

The script seem to have moved the Data and Dalvik Cache, without it been enabled when I rebooted the phone.

# cat /props/content.log

v/Preparing configurations

v/Optimizing the internal nand partitions

v/Setting system nand readahead to 4kb

v/Setting optimized mount parameters on system

v/Setting data nand readahead to 4kb

v/Setting optimized mount parameters on data

v/Setting cache nand readahead to 4kb

v/Setting optimized mount parameters on cache

v/Waiting for sdcard to initiate

v/The sdcard device was located at /dev/block/mmcblk0

v/Setting sdcard readahead to 512Kb

v/Checking sdcard partitions

v/Using /dev/block/mmcblk0p1 as fat32 (sdcard)

v/Using /dev/block/mmcblk0p2 as ext4 (sd-ext)

v/Running file system check on sd-ext

v/Setting optimized mount parameters on sd-ext

v/Disabling ext4 journal on sd-ext

v/The sd-ext partition was mounted successfully at /sd-ext

v/Preparing to move content between /data and /sd-ext

v/Moving content from /data/data to /sd-ext/data

v/Moving content from /data/dalvik-cache to /sd-ext/dalvik-cache

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

v/Attaching /sd-ext/dalvik-cache to /data/dalvik-cache

v/Looking for new system apps in /data/app-system to link to /system/app

w/Did not find any SWAP partition!

v/Executing the final steps of the script

v/Changing permissions on /data/local/tmp

v/Attaching /data/local/tmp on /sd-ext/data@local@tmp

v/Storage threshold is set to 1%

#

Right now the Status icon is Orange with an exclamation point. Should I continue and enable the Applications content?
[Android Software/Hacking General [Developers Only]] dk_zero-cool:
The script might have hit a safe-guard. Did you clean the sd-ext partition? If you disable app, data and/or dalvik, the script will move these things back from sd-ext to data. However, if your sd-ext content takes up more space than you have available on data, it will re-enable the options and keep the content where it is in order to keep it from destroying anything.

Example. Let's say that you disable data and that you currently have the data on /sd-ext/data. When you reboot, the script will move /sd-ext/data back to /data/data because you have disabled this option. But before it moves anything, it will check /sd-ext/data to see how much space it uses. Let's say it uses 60Mb but you only have 45Mb left on /data. That means that your content in /sd-ext/data cannot fit into /data/data. The script will then re-enable the data option and keep everything in /sd-ext/data but warn you about it as the settings does not match the current state.

However, it should report this in the log file. Could you try enabling the debug option in the app configure screen and reboot? Then go to the app log viewer and save the log and paste it here. It will contain much more info than the current log. Do not enable any other option at this point. Also how much space is left in /data and /sd-ext?
[Android Software/Hacking General [Developers Only]] dk_zero-cool:
Everything in the log looks fine, and yes, the error/warning is the filesystem check.

And every option is disabled? Could you try looking in /data/property/m2sd.move_apps and see if it contains 1 or 0?
[Android Software/Hacking General [Developers Only]] qbase775:
All content option except the Cache is enabled, but I haven't enabled them. It's been enabled by itself when I rebooted the phone :confused:

# cat /data/property/m2sd.move_apps

1
[Android Software/Hacking General [Developers Only]] dk_zero-cool:
Hmm, did you touch the R-Mount option? This option in the app will auto-reverse all of the content options, so if you unchecked apps, data and dalvik and then unchecked R-Mount, that would re-enable apps, data and dalvik. The R-Mount option is made to be changed while keeping all the content on the same partitions in order to help people who get's confused about how to handle R-Mount. If you change the R-Mount option, you need to do this before changing any content options.
[Android Software/Hacking General [Developers Only]] qbase775:
I don't think so, that option seems to enable apps, data and dalvik at the same time. For me it first moved the Data and Dalvik, see post http://xdaforums.com/showpost.php?p=36041978&postcount=882

Anyway it seems to be working now, except the warning. I'm going away for the new years, don't have access to a computer. We can continue debugging this in a couple of days, if you want me to :cowboy:
[Android Software/Hacking General [Developers Only]] dk_zero-cool:
Strange issue, but glad it is working now at least. Have a good new year, and yes, if you have any further issues I will most certainly want to get them fixed :)
[Android Software/Hacking General [Developers Only]] qbase775:
Sounds good, I'll keep you informed. Thank you for your help and for your script that enable older devices a longer life.

In the holiday spirit I donated 20 euros to XDA :cool:
[Android Software/Hacking General [Developers Only]] CsabiDuke:
It is working!!! Thank you, and happy new year!!!!
[Android Software/Hacking General [Developers Only]] SCoUT80:
Script not found

Hy guy...can someone help me?

i'm trying to use this script to move some stuff on my external sd...but after installing it...the busybox installation goes ok...the init.d script not.

How can i use it???

THX
[Android Software/Hacking General [Developers Only]] mixednuts:
Does your ROM feature INIT.d?
[Android Software/Hacking General [Developers Only]] SCoUT80:
I'm using the cyanogen 10.

It should.
[Android Software/Hacking General [Developers Only]] dk_zero-cool:
Yes it should, I am using it myself on cm10 and 10.1

Could you explain the problem?
[Android Software/Hacking General [Developers Only]] SCoUT80:
I flashed the Rom...works great...them cause as2d doesnt work very well I decide to instal mounts2sd and I decided to do it from the play store. Installed it...and when I was trying to let it work I found this problem. Tried to instal the all, from recovery..but nothing I'm stucked at this page. Is there a way to flash manually the init.d?

Something strange that I noticed that even with the terminal I cannot find it.