yashsingh1/xdaforums huggingface dataset:
[Android Software/Hacking General [Developers Only]] jasonkhoo87:
Why I tried with other JB rom such as Ultimate ROM, Amnix, SVA.. all will cause bootloop?
[Android Software/Hacking General [Developers Only]] dk_zero-cool:
/system/etc/init.d/02cooper

This file is handling your SWAP partition. So either remove this file or disable SWAP in m2sd. I will later on add a beter way of handling SWAP when already enabled.

You might as well also remove the sqlite file to. Sqlite does not work until after the phone as booted. So it does not really do anything.

I don't know. I mean, you don't tell me what device you have, you don't provide any log information or anything else. You just ask why your phone loops. It's like asking you why my car sounds funny when driving it.
[Android Software/Hacking General [Developers Only]] jasonkhoo87:
Im using Galaxy Note. By the way, as soon I reboot, then I get boot loop, How can I see the log?

before this Im using other rom its work. So, I think its because of rom not compatible? And, I didnt tick and dalvik nor cache.
[Android Software/Hacking General [Developers Only]] paradoxiumwind:
Thanks :) I'll try that.
[Android Software/Hacking General [Developers Only]] dk_zero-cool:
I had the same issue on my SGS3 because the phone was booting to fast when the ROM uses a Service version of the init.d implementation (Sadly used on most ROM's). I added a fix that at least got it working on my phone, but depending on the boot speed of the device, it could still be an issue.

Try disabling safe-mode in the settings. This will trigger another hack for your type of init.d which will slow down the boot until the script is done. It is still a very experimental feature, but seams to be working on most devices.

Also note that I have to idea how this script or app will react on devices with Multi-Users enabled. I have added support for this new Android feature based on what I know about it, but I do not have any device to test it on. So if you have this enabled, it might be an issue as well.
[Android Software/Hacking General [Developers Only]] jasonkhoo87:
I think I understand what u mean by.... So, I need to untick the safe mode 1st for the 1st time installation until my phone restart and boot normally. Then I can tick again after the succesful 1st boot? Am I correct? Im going to try it now.. Hope it work...

But, if this case happen, can it happen next time while I still on the same rom? (Restart -> boot succesful -> Restart again -> continue the process)

for your information, i didn't use Multi-Users function.

UPDATED:

After reflash the affected rom, I can make it work as this step:

1. Flash rom.

2. Install Busybox and update it.

3. Install mounts2sd and update the busybox and install the script

4. Reboot the device (Didn't change any settings on the mounts2sd)

5. Now reboot and boot succesfully.

Now, I tried with Dalvik Cache, and disable safe mode option checked:

1. Reboot device and voila.. It did boot succesful..

What I can see here, on the 1st install, do not change the mounts2sd settings. Just make a normal reboot 1st.

:)

Btw, I still want to know whether, it will affect me on the future and cause bootloop even now I succesful boot to homescreen... ??
[Android Software/Hacking General [Developers Only]] dk_zero-cool:
No. If it works when safe-mode is disabled, then keep it disabled.

Also note that the apps option is the only option that is allowed when you are in safe-mode. Dalvik and data will be automatically disabled on boot if you enable them. So keeping this disabled also provides more options for you.

The first boot with empty sd-ext and a full data partition is the most unstable part. This is where the script spends time creating folders, checks and moves content around and so on. Once this is done, the boot will become more stable as the script has nothing else to do other than creating some mount points (Linking) between the sd-ext folders and the data folders.

So no, when your device is configured like you want it, then it will make no difference whether you reboot twice or 1000 times.
[Android Software/Hacking General [Developers Only]] jasonkhoo87:
Nice explaination... :) Now it work as I configure... By the way, can u add a function which can clear the partition as for preparation to make the partition clean. As what I can see, if there any files/folders left over on the partition. I flash new rom and then reinstall mounts2s the files/folders still there and i need manually delete it.. just a suggestion..
[Android Software/Hacking General [Developers Only]] lichan:
I have an EVO 4G running Kendalc123's JellyBread (Gingerbread 2.3.7-based) ROM. I removed the included Darktremor a2sd scripts

and am running m2sd (starting with 1.2 and now the most current version). At one point I had to insert the devise_provisioned value

into the sqlite3 settings.db file to correct an inactive Home, Search and unlock buttons. I recently started getting the dreaded

492 Play Store download error and none of the remedies I have found has worked. I have cleared data and cache in Play Store

and Google Services Framework and rebooted into recovery (Smelkusmod) to wipe cache and dalvik-cache, fixed permissions

and still encountered error 492 after reboot. I have removed Play Store updates, removed Play Store, installed a new Play Store,

deleted sdcard/.android_secure, removed my Google account on the phone and re-added it all to no avail. I am running m2sd with

apps, app data, app cache and dalvik-cache enabled, tmpfs disabled. Everything in the df command shows plenty of space available

(I have a 64 GB xsd card). The only thing I haven't tried that I have read about is backing up, reformatting and restoring the sdcard

which I am going to do tonight. Evidently the 492 error is like the Medieval disease Fever which was so inexplicable because it was

just a symptom of many underlying diseases and I haven't been able to correct the hidden cause of the error. Any one have any ideas?

I post the question here because it seems to be akin to moving apps around to different places. Thanks.
[Android Software/Hacking General [Developers Only]] impactor:
What is the gradation of things (dalvik, data, apps) to be left in internal memory in order of highest operating speed and least reads from sd-ext?
[Android Software/Hacking General [Developers Only]] NeoFox69:
Hello DK again!

Just to let you know that I've tried a number of ways to make the Mounts2SD work in v4.6 of the ROM, but with no success.

I've tried to update busybox before install, I've tried to clear cache, disable safe mode (every-time I used a fresh ROM installation), and so on, but same problem of "no space" every-time.

In v4.5, it works flawless, but in v4.6 it don't.

Just to let you know.

Be cool, and thanks for this amazing script!

P.S.: If you need any help translating this to PT-PT, let me know!
[Android Software/Hacking General [Developers Only]] impactor:
I am on v4.6 and Mounts2SD work fine for me.
[Android Software/Hacking General [Developers Only]] NeoFox69:
Really? What's your settings?
[Android Software/Hacking General [Developers Only]] dk_zero-cool:
Well apps are the best thing to move. The rest depends on your sdcard type (Manufacturer, Class and such). Just try the settings you want and see how it behaves.

Your problem is most likely a bad formated sd-ext partition. What do you use as Recovery?
[Android Software/Hacking General [Developers Only]] impactor:
Yes, but my impression can be very subjective, so I prefer to know what in theory is better to place on sd card: data or dalvik-cache.

My card is Sandisk UHS-1, which I think is over 3 times faster than sd slot capabilities in Desire.
[Android Software/Hacking General [Developers Only]] MetinKale38:
AW: [App/Script] Mounts2SD - An All-in-one sd-ext solution (2.2.0/5.5.0 - Jan 26, 201

Why you have 2 versions?

You should be able to mount ext and mtd devices with the busybox mount command:

run_program("/sbin/busybox", "mount", "/system");

unmount("/system");

Tapatalked with my JellyBean powered HTC Desire
[Android Software/Hacking General [Developers Only]] paradoxiumwind:
After my phone running fine with this script, I made a CWM nandroid backup because it said my sd-ext was full and it couldn't move the dalvik cache there, so I made a nandroid backup, partitioned my SD card to have a larger sd-ext partition, and now every time my phone boots up it says "Android is upgrading..." "Optimizing app x of 86" every time, What gives?
[Android Software/Hacking General [Developers Only]] dk_zero-cool:
Re: [App/Script] Mounts2SD - An All-in-one sd-ext solution (2.2.0/5.5.0 - Jan 26, 201

It's not about the recovery script. The recovery binaries are different. Not all older devices works with the newer once and not all newer devices works with the older once.

Implement a proper init.d. Disabling safe-mode works perfect for some devices, others have small issues like this while a few can't boot at all. There is not much to do about it. Init.d should not run as a service, but on some roms it does and I have added as much hacks as possible to make it work on these roms, but hacks like these are far from a perfect solution.

You can try to clear dalvik in recovery, that might help. But thats all I got for you other than disabling the dalvik option.
[Android Software/Hacking General [Developers Only]] MetinKale38:
AW: [App/Script] Mounts2SD - An All-in-one sd-ext solution (2.2.0/5.5.0 - Jan 26, 201

That's the way titanium backup do (when creating a flashable zip of it), so it should work for all.

Tapatalked with my JellyBean powered HTC Desire
[Android Software/Hacking General [Developers Only]] paradoxiumwind:
I'm using CM10.1, should that not have proper init.d support by default? should I disable safe mode?
[Android Software/Hacking General [Developers Only]] dk_zero-cool:
No. That means nothing. Titanium is not a very quality build application. All the problems I have seen people have with their devices using that app, it is no surprise that they are getting this one wrong as well.

Not all devices can use the same binary. This has been proven by multiple user posts and PM's over a year ago which is why I use two.

Not all CM ROM's does, I was surprised as well. But if you do not yet have safe-mode disabled and are able to move dalvik, then you do have proper init.d, so disregard the last post.

Have you however tried wiping dalvik-cache?
[Android Software/Hacking General [Developers Only]] dk_zero-cool:
You have enabled safe-mode. So your ROM does have the service init.d version. Read the log a couple of lines down. This means that dalvik is no longer moved as it get's disabled by the script.

Note that the safe-mode checkbox in the app will not enable safe-mode when checked, it disables it. To enable you have to uncheck
[Android Software/Hacking General [Developers Only]] paradoxiumwind:
Oh damn, my mistake. I'll change that. Aside from that, I edited my previous post, can you comment on whether I should change any other settings for the optimum running of the phone?

Thanks again.
[Android Software/Hacking General [Developers Only]] dk_zero-cool:
Well about SWAP, I would set it at the minimum level, at least not higher than Linux default. Higher level means less RAM usage and more SWAP usage. RAM's are much faster than your sdcard or any other storage devices, so it's best to use the RAM's whenever possible and only use SWAP as fallback when your memory get's to low.
[Android Software/Hacking General [Developers Only]] paradoxiumwind:
Alright, I see, thanks again :) I love this app/script. Easiest etcetc2SD thing i've used.
[Android Software/Hacking General [Developers Only]] post-mortem:
You might actually find a Class 4 or 6 card to be faster than a Class 10 card. See this for more information: http://www.tomshardware.com/reviews/microsdhc-memory-card-performance,3011-12.html

Note that for mobile devices, the 4KB test is more applicable than the 512KB test. Other devices, like digital cameras (especially video), will have larger bursts of reading/writing, and will make better use of high speed SD cards.
[Android Software/Hacking General [Developers Only]] dk_zero-cool:
Same issue as I already posted for someone else a few posts back. Your problem is this line

v/script - /system/bin/servicemanager is running, Stalling System Server

You are running a bad implementation of init.d which executes scripts while the phone is booting instead of waiting with the boot until all scripts are done. This means that your device (If fast enough) will boot all the way before M2SD is done moving content. Because of this I added the small hack that you see in the log line above. What the script does it killing the System Server and keeps doing so until the script is done. This will trigger a soft-reboot (Resets the UI and all App related services) so that the script can handle the data without those services interfering.

Your problem is that your device is booting to far into the main system before the script start killing the System Server. This gives dexopt a chance to build some of the dalvik-cache files in /data, because the real cache is located in /sd-ext. The script sees this new dalvik data and deletes all dalvik related caches from both partitions to make sure that you get a clean working version of them.

You can try booting into recovery and clear dalvik-cache. This some times help. Otherwise your only choice is to avoid moving dalvik-cache at all, or implementing a better init.d support.
[Android Software/Hacking General [Developers Only]] paradoxiumwind:
I see, thanks for taking the time to explain. I have disabled the dalvik cache for now (will that actually even help the phone run faster having it on the SD-card?)

And, I am using stock CM10.1 on my phone, without any mods/scripts (except yours), how would I go about adding or fixing the init.d support? Or is that just something way out of my league?

Thanks again.
[Android Software/Hacking General [Developers Only]] dk_zero-cool:
Re: [App/Script] Mounts2SD - An All-in-one sd-ext solution (2.2.0/5.5.0 - Jan 26, 201

It's done by extracting the boot image, unpacking the ramdisk, change some files, repack and flash. Dont know how much knolege you have on this subject?
[Android Software/Hacking General [Developers Only]] paradoxiumwind:
Pretty much zero, and i'm too busy to teach myself how, so I guess i'll just live without it.

Thanks again.
[Android Software/Hacking General [Developers Only]] NeoFox69:
Hello DK again!

I use 4EXT Recovery Touch, and with the v4.5 of the ROM, it works great!

Maybe I'm just in bad luck or something... It had always worked ok for me, except since the v4.6 of the ROM.

Nevermind then, I'll continue to use v4.5. Maybe after an update to v4.7 or something, it will work.

Thanks Again, and Be Cool Everybody!
[Android Software/Hacking General [Developers Only]] luminata:
Re: [App/Script] Mounts2SD - An All-in-one sd-ext solution (2.2.0/5.5.0 - Jan 26, 201

Hi,

I am using the script on Nikez 4.2.1 HTC Desire ROM. Every time I restart the phone, m2sd app gives me an alert. When I open it I find this error "The Contents of /sd-ext/dalvik is to big to be reverted back to data". I searched the thread but did not see solution. Should I ignore it or is this something bad?

Thanks in advance.
[Android Software/Hacking General [Developers Only]] impactor:
Is there a program doing a better job at what Titanium Backup does (backing up/restoring apps and data between rom changes)?
[Android Software/Hacking General [Developers Only]] dk_zero-cool:
Re: [App/Script] Mounts2SD - An All-in-one sd-ext solution (2.2.0/5.5.0 - Jan 26, 201

The problem is what it says. You have dalvik-cache on sd-ext, but have dalvik disabled in settings. So the script tries to move it back to /data but there is not enough space left on data to contain dalvik-cache, so it gives you a warning and leaves dalvik where it is. Just re-enable dalvik in settings to remove the error, or make more space on /data for the dalvik-cache

Don't know. I have never used titanium myself.
[Android Software/Hacking General [Developers Only]] luminata:
Re: [App/Script] Mounts2SD - An All-in-one sd-ext solution (2.2.0/5.5.0 - Jan 26, 201

Thanks. I didn't know I enabled and disabled. Where is the best place for dalvik in your opinion.
[Android Software/Hacking General [Developers Only]] dk_zero-cool:
Re: [App/Script] Mounts2SD - An All-in-one sd-ext solution (2.2.0/5.5.0 - Jan 26, 201

I would have to say the partition with enough space to store it ;D

Sd-ext is fine. I have always had apps and dalvik on sd-ext
[Android Software/Hacking General [Developers Only]] MetinKale38:
AW: [App/Script] Mounts2SD - An All-in-one sd-ext solution (2.2.0/5.5.0 - Jan 26, 201

For me it's really working great (I have the pro version).

You could try the new carbon app, it is also very good but I stay on tb pro.

Tapatalked with my JellyBean powered HTC Desire
[Android Software/Hacking General [Developers Only]] NeoFox69:
I use Go Backup and it works great for me!

Be Cool ;)
[Android Software/Hacking General [Developers Only]] mixednuts:
You could try this thread for starters. dk did post some pointers to another dev some pages back.
[Android Software/Hacking General [Developers Only]] Beaksterboy:
Config Error

Hi,

I just installed Mount2SD in a fresh CM10 install on a LG p500. After install I am asked to click 2 buttons, 1 to configure busybox, and one to set up init.d. Both of these fail. The first fails with the message "BusyBox could not be configured". Any suggestions on what I can do differently?

Thanks
[Android Software/Hacking General [Developers Only]] mixednuts:
Re: [App/Script] Mounts2SD - An All-in-one sd-ext solution (2.2.0/5.5.0 - Jan 26, 201

Try the flashable zip linked on the first post.
[Android Software/Hacking General [Developers Only]] dk_zero-cool:
First of all if these fails, they should automatically launch an recovery install. If not, that means that your toolbox binary does not support the reboot option.

Second, since you don't have an HTC with the possibility of S-On protection, I would have to say that you most likely do not have any more space available on your /system partition. If this is not the case, then I would strongly recommend updating your busybox as this is the last possible issue and if so, your busybox will not be compatible with the script anyway and a manual recovery install will properly not be the solution.

So do the fallowing

1: Check available /system space

2: If you still have more than 1mb on /system, then update your busybox

3: If it still fails (Don't think it will at this point), try the manual recovery install
[Android Software/Hacking General [Developers Only]] jasonkhoo87:
Do u know how to remove link2sd mount point? Because after I mount using it then run mounts2sd and successful created the script, it won't mount to sd_ext. If possible to solve because lazy to re-flash the rom.
[Android Software/Hacking General [Developers Only]] dk_zero-cool:
You just need to remove the link2sd script, but that should already have been done by the app.
[Android Software/Hacking General [Developers Only]] Beaksterboy:
Please can you tell how how to update Busybox? Mount2SD says not to use the one from the market, and to use the one from here, but I can't find a recent download link on this forum.

Also how much space should I have free on /system? Currently I have 1.2meg. Any tricks for increasing that?
[Android Software/Hacking General [Developers Only]] post-mortem:
My recommendation is to reflash the ROM, sorry.
[Android Software/Hacking General [Developers Only]] dk_zero-cool:
Have a look at THIS

Do you know a link to the app without using play store? M2SD should remove any existing sd-ext scripts, if this does not work properly with link2sd, then this should be updated.
[Android Software/Hacking General [Developers Only]] post-mortem:
If you mean Link2SD, then here: http://xdaforums.com/showthread.php?t=1825777
[Android Software/Hacking General [Developers Only]] jasonkhoo87:
Now. It will not cleaned. I did try mounts2sd and null for ext partition. And I open link2sd it still linked.
[Android Software/Hacking General [Developers Only]] post-mortem:
That's what happened to me. I couldn't stop my ext partition from being mounted as /sdext2. I decided the best (and fastest) solution was to do a fresh reinstall of the ROM, and don't touch Link2SD.
[Android Software/Hacking General [Developers Only]] palicnjak:
AWESOME!!!

Thank you very much. Its working on my GB(2.3.7) xperia arc s.

Very good app.

You are the best.

Thanks
[Android Software/Hacking General [Developers Only]] mixednuts:
Re: [App/Script] Mounts2SD - An All-in-one sd-ext solution (2.2.0/5.5.0 - Jan 26, 201

You can also give this a try... it's not a flashable zip - extract it and run the script (with root permissions).
[Android Software/Hacking General [Developers Only]] acestars:
Re: [App/Script] Mounts2SD - An All-in-one sd-ext solution (2.2.0/5.5.0 - Jan 26, 201

Try remove link2sd script in /system/etc/init.d, something like 11link2sd or if you still want to use link2sd try rename so it listed before mounts2sd script.

Sent from my Z71
[Android Software/Hacking General [Developers Only]] gu5t3r:
It will not work, Link2SD keeps apk files in root of /sd-ext/, not in /sd-ext/app folder....

If you want to try it anyway, you need to remove 11link2sd from /system/etc/init.d/ and remove /system/etc/install-recovery.sh which Link2SD used when there is no init.d support.

At me, /data/sdext2 stayed mounted to sd-ext after reboot, I had to run Aroma file manager for CWM and delete /data/sdext2 forder from it.

But as many times I tried I could not migrate from Link2SD to Mounts2SD, but someone said it works on fresh install...
[Android Software/Hacking General [Developers Only]] post-mortem:
Yup, that's exactly what happened to me. So, I had to install everything fresh.
[Android Software/Hacking General [Developers Only]] Parastie:
Has anyone tried this on the newer Evervolv nightlies? I downloaded from Market, and it says busybox and script are installed correctly. However, when it does not appear to be editing the script (when I make configuration changes I do not notice any script changes when I look at it) and it does not appear to be working. I manually reboot after setting the status flag since I'm never asked to reboot while in the app and then when I relaunch no changes are noticed by the app..

Suggestions?
[Android Software/Hacking General [Developers Only]] dk_zero-cool:
Do you reboot while the configure screen is opened? The app saves changes when you leave the configure screen, to avoid the SuperUser app popping up on every click. Maybe the new Evervolv some how forgets to execute my closing methods upon a reboot. Try changing and then push the back button to close the configure screen and see if that helps. If so, then I will look at that problem.
[Android Software/Hacking General [Developers Only]] Parastie:
Yeah, that's what I've been doing. I back out of configuration, wait for the permission flag, then back out to the homescreen and reboot. Check the app, no changes were kept.

I'm using the Feb 4th build of Evervolv on HTC Desire. I wonder if the latest build of Evervolv has some kind of weird glitch.

EDIT:

Also, the External Data says N/A. It shouldn't say that right?
[Android Software/Hacking General [Developers Only]] dk_zero-cool:
Are you sure that the script is even executed? That would explain the configurations. The configs are saved in /data/property, but the app reads them from /props/ after the script has copied them from the property dir. This is because it fixes issues with R-Mount (Long Story). Never the less, the script saves them in /data/property, but if the script is not executed during boot, then the app will not have anything to read from in /props and just uses the defaults in the configure screen. Also sd-ext will not be mounted, and will say N/A.

What does the log say, and are you sure that for some reason (A mistake maybe) init.d support is not missing? Maybe someone at Evervolv broke init.d in the kernel.