That would be really awesome... u may try the steps i mentioned above
That would be really awesome... u may try the steps i mentioned above
In a nutshell u can follow these steps:
Description of the use of Apps2SD on Xiaomi phones
1. We have a Rooted Xiaomi Redmi Note 5 Pro phone with Magisk installed and custom recovery (for example Orange Fox 10.1) and MIUI 10.3.1.0 firmware Android 9 stable. How to organize full Android access to a flashcard is not discussed here. BusyBox must be installed on the system.
2. Since we will use the 2nd partition with the f2fs file system on the flashcard, we need to install a custom kernel with support for this file system (I don’t know if the stock kernel supports this file system, I don’t use it!). I am using the Ancient-EAS kernel which can be downloaded from the link Click here!... Install the kernel in the usual way as a zip archive through custom recovery. After installation, you need to boot into the system and reinstall Magisk, then reboot, this will increase the overall stability of the system!
3. Next, you need to install a Magisk module called Init.d Injector from the Magisk repository.
4. After that, we reduce the size of the first partition of the flashcard and create a primary second partition there and format it for the f2fs file system. I am using a 128 GB flash drive, the second partition is 32 GB.
5. Boot with the repartitioned flashcard, launch Apps2SD and mount the second section of the flashcard. The section should mount perfectly!
6. In the Apps2SD settings, in the "Set path su.d ..." parameter, set the path data / adb / post-fs-data.d
7. Check the box for "Get sleep ban"
8. Check the box "Use CP instead of RSync" ...
9. Check the "Backup Apps2SD database" checkbox.
10. The "Restart Apps2SD service" checkbox should be ticked.
11. After that, go to "Bind applications to SD card" and select "Recreate mount script". Select the f2fs file system and select the item "My device supports init.d" and create a script. To be honest, I didn’t create any scripts until I ran the mounts, I don’t know where, when and what scripts are created, so you can go through all the points for reliability, but you should create everything when you select init.d.
12. Find and save the scripts 00000000apps2sd-main.sh, 01apps2sdinit, apps2sh-mountscript.sh in the data / adb / post-fs-data.d and data / adb / service.d folders, and then give these files permission 755. Trace to give apps2sd permission 777 in the data / adb folder.
13. That's it, you can reboot the phone, the 2nd section of the sd card will be mounted at boot, you can go to Apps2SD and move custom applications to the 2nd section of the sd card!
NB: this was translated so caution is advised
It looks like you're trying to unset the immutable and append attributes on vold. And then copy vold_apps2sd, but with the name of vold. But it's not letting you, because the file doesnt exist.Sorry I'll try to explain better. My Samsung note 8 (android pie), have a partition, with many app linked. I had some problem with them, so I try to recreate the script, with "Advanced method" that worked fine untill than. But Device stuck in bootloop after creating mount script using the "Advanced method". So i tried to resolv the problem with a solution finded in the site "https://www.apps2sd.info/kedb.html" a the title " Device stuck in bootloop after creating mount script using the "Advanced method" ". So the device restarted and this time i try to recreate the script with "Normal method" but device go again in bootloop but this time i tried again the solution but it didn't work and terminal says so.....
just TWRPIt looks like you're trying to unset the immutable and append attributes on vold. And then copy vold_apps2sd, but with the name of vold. But it's not letting you, because the file doesnt exist.
In TWRP, mount system partition, open file manager, go to /system/bin/, do you see more than one vold file? And what are their names?
Are you able to boot into Android? Or just TWRP?
Rename vold to voldbak (actually it doesnt matter if it is bak or anything else), then rename vold.original to vold. Then try booting into Android. If it works, you can delete voldbak. Apps2SD possibly replaced your vold file with something that isnt compatible. The vold.original should be the one your Android had before the app made any changes.
I have no idea how to repair the partition and get the apps relinked.
I meant linking the internal data (located in the userdata partition of the device). To my knowledge fbind can't do that. But even if it's possible to bind mount an entire user, it's not something I would recommend doing. Too much opportunity for weird bugs, crashes, etc to occur. I don't know that much about fbind beyond using it to link some stuff from internal storage to external storage. So if you have questions about it, I'd ask in that thread. @VR25 also has Telegram chat channels you can join.
Su.d was originally a function of SuperSU. But it's basically nothing more than a function of auto running scripts on boot. Init.d has been able to do that for a long time, and Magisk also. I'm using /data/adb/service.d. if you're using Apps2SD on Android 11/12 in particular, I would also enable the setting to not let the app modify system partition. Too much chance of a bootloop/inability to boot on newer Android versions. It happened to me once on 11, I had to go through a somewhat complicated process to undo Apps2SD's changes and get back into Android. Setting the su.d path works fine though, since it doesn't modify Android's system files.
Can't advise much with adoptable storage and issues relates to linking/binding with it. I tried it once a few months ago and lost over 150GB of files that can't be recovered. Much of it wasn't critical, but some was. Still reeling a bit recovering from that. As a result, I won't use AS again unless I'm confronted with a scenario where there are no other viable options.Great, thanks for all the tips. I had already heeded your advice to choose not to have the app modify the sys partition when it asked me.
I'm finishing setting up my new Nokia 6.1 with LineageOS 18.1 (Android 11), also running latest Magisk and latest LSPosed. I've formatted my SD card as internal aka "adoptable storage" for encryption. Above all what I want to do is move and bind 2 apps' data from #/data/data/app.path to adoptable storage. Before on my Samsung (SD as regular mobile) I achieved that via Symlinks with Root Explorer or FX Explorer [root], but this is not working anymore in my new setup. And XInternalSD isn't helping here.
Get rid of adoptable storage while you can, go back to what Android calls "portable storage".Sorry to hear about your data loss due to messing with AS. I know how that feels.
Thanks for your explanation of how AS works. Already having read many pros and cons about it, I'm still lamenting if how AS works is really what I want. Esp. because of the way migrating works - that I can't choose what is getting migrated but am forced to migrate everything. I initially had thought AS would only merge the SD card into Internal Storage, and not also move /data/apps and data/data hidden in the background. Esp. since hardly and app works if run from AS anyway and I had to enable a switch to install and keep apps on internal. I think much rather I'd prefer to have all apps and data on internal by default, and continue to choose willingly via XinternalSD and root Symlinks what exactly to move to SD card.
Re. backups: very good points - here's how I've been doing it:
- backup via TWRP -> images to PC
- phone booted into Android & connected to PC: manual copies of Internal and SD-card's folders/files -> PC
- with SD formatted as AS: SD-card via adapter into PC then 1:1 RAW clone saved as compressed image
The path to folder with the encryption keyfile in /data/misc/vold is great to know - I just backed the entire folder up