Database Info

ext, app2sd & strange behaviour

I have a complex problem i'm trying to get around to for month now. Maybe someone has a tip for me:
When installing a new ROM, there are always preinstalled programs turning up that are not part of the ROM. I assume those are on my SDCard because of the Apps2SD/Link2SD setups i have been running for awhile. Was still a bit wondering why they are turning up, because they are not "linked" (didnt reinstall apps2sd or link2sd), but they are available nevertheless ...
What remains is that i need to check/fix my apps2sd setup, but i cant access the linux partitions from my PC because of USB/cardreader problems..
Is there an app out there that lets me access (and maybe even change) my ext partitions content ? Commandline stuff is fine for me.
System: CM7 XT70, 16GB SD with SWAP and Ext3
Ps.: If i can even change to ext4 that way, that would be awesome.

One thing you can do is make an nandroid backup of the "SD Data" partition (that's what nandroid calls the ext partition). For that partition, nandroid backs everything up into a *.tar and a *.md5. You can then copy the tar file to your computer, extract it, modify it etc. When you're done create a new *.tar file and a corresponding *.md5 and use nandroid to restore your new *.tar. When nandroid restores the "SD Data" partiton, it first reformats the entire partition to ext2 and then extracts the tar onto it. If you use XT720 OpenRecovery there's a "SD utilities" function that you can use to convert the existing ext2 to ext3 or ext4 (be aware that ext4 requires ROM support--I think most of the recent ones do...). The regular OpenRecovery does not support ext4 (you won't be able to make a nandroid of "SD Data")--you next XT720 OpenRecovery.
If you want to repartition... I don't know if that can be done on the phone itself.
If you want to just disable app2ext, look inside /system/etc/init.d and find the script that mounts /sd-ext and then move/delete/rename it.

i reclaimed control over my phone! thx
it turned out all /data/app was linked to the ext3 partition ... another reason why my phone was slow.

[MOD] Move to sd-ext | Simple app, private-app and Dalvik cache to SD solution

This is a simple and effective (moves most space hogging folders from internal memory to sd-ext) APP2SD solution.
It moves the following things from /data partition to ext partition on SD card:
/data/app => /sd-ext/app
/data/app-private => /sd-ext/app-private
/data/dalvik-cache => /sd-ext/dalvik-cache
and creates symlinks to new locations in place of original folders.
Solution consists of 2 via recovery flashable ZIPs:
sd-ext_patch-signed-vXX.zip - this updates/creates CyanogenMod 7/9 script that mounts SD card ext partition to /sd-ext so /sd-ext can be any ext version (by default it can be only ext3) and installs e2fsck. This must be re-flashed after each ROM update (unless you know that ROM will mount your /sd-ext out of the box).
to_sd-ext_patch-signed-vXX.zip - actually moves folders to ext partition on SD card. This can be flashed only after first boot into ROM after wiping /data. It should be re-flashed only in conjunction with wiping /data and /sd-ext.
This mod requires ext2/ext3/ext4 partition on SD card.
Always make full Nandroid backup before flashing this mod or updating ROM with mod installed!
Disclaimer: I am not responsible for anything that may happen as a result of using this mod.
Installation/usage:
To install mod on a working ROM:
Flash sd-ext_patch-signed-vXX.zip via Recovery.
Flash to_sd-ext_patch-signed-vXX.zip via Recovery.
After updating ROM:
Re-flash sd-ext_patch-signed-vXX.zip without booting into updated ROM.
After wiping /data from Recovery:
Delete moved folders from /sd-ext (in most cases you will want to do this by wiping /sd-ext from Recovery).
Boot into your ROM.
Re-flash to_sd-ext_patch-signed-vXX.zip via Recovery.
This mod is tested with CyanogenMod 7 (7.1 by mik_os and 7.2 official builds) and CyanogenMod 9 by hephappy and Amon RA recovery 3.0.6.
If you are using Clockworkmod Recovery see this post.

+1
Is this mod developed by you?

DJoptimus-One said:
Is this mod developed by you?
Click to expand...
Click to collapse
Yes

DavisNT said:
Yes
Click to expand...
Click to collapse
Nice work, I'm surely gonna try
Keep up.

Good work here!! Really nice to see some REAL development here
Will try it and report soon.........
Sent from heaven, wandering with Steve Jobs

Any feedback yet? Would love to give it a try :thumbup:
Sent from my LG-P500 using XDA

FitAmp said:
Any feedback yet? Would love to give it a try :thumbup:
Sent from my LG-P500 using XDA
Click to expand...
Click to collapse
Don't ask for that, try it yourself!!

nice work will try

Does this work on gb?2.3.3?
How to move app's ? Does this automatically moves it?
Sent from my LG-P500 using XDA

Just flashed on cm9 weekly... so for so good
Sent from my LG-P500 using XDA

Good work. Nice example of KISS approach - three symlinks + few lines of other code

dynamite33 said:
Does this work on gb?2.3.3?
How to move app's ? Does this automatically moves it?
Click to expand...
Click to collapse
You can make full Nandroid backup (Nand backup in recovery) and try whether it works on your ROM.
This requires the following things:
ext partition on SD card (you must have partitioned your SD card)
ROM that supports init.d scripts
kernel that supports ext filesystem version that is on SD card
You can test all this by (making full Nandroid backup and) flashing sd-ext_patch-signed-vXX.zip, booting in Android and issuing the following commands in Terminal Emulator:
Code:
su
mount
mount | grep sd-ext
If you see line like this somewhere in the output:
Code:
/dev/block/mmcblk0p2 on /sd-ext type ext4 (rw,noatime,nodiratime,barrier=1,data=ordered)
then /sd-ext is mounted and you can proceed to flashing to_sd-ext_patch-signed-vXX.zip.
Apps are moved when flashing to_sd-ext_patch-signed-vXX.zip.

DavisNT said:
You can make full Nandroid backup (Nand backup in recovery) and try whether it works on your ROM.
This requires the following things:
ext partition on SD card (you must have partitioned your SD card)
ROM that supports init.d scripts
kernel that supports ext filesystem version that is on SD card
You can test all this by (making full Nandroid backup and) flashing sd-ext_patch-signed-vXX.zip, booting in Android and issuing the following commands in Terminal Emulator:
Code:
su
mount
mount | grep sd-ext
If you see line like this somewhere in the output:
Code:
/dev/block/mmcblk0p2 on /sd-ext type ext4 (rw,noatime,nodiratime,barrier=1,data=ordered)
then /sd-ext is mounted and you can proceed to flashing to_sd-ext_patch-signed-vXX.zip.
Apps are moved when flashing to_sd-ext_patch-signed-vXX.zip.
Click to expand...
Click to collapse
Ok thanx a lot! Will try it.
Sent from my LG-P500 using XDA

hi DavisNT
i use Link2sd now, and want to try ur script, can i remove link2sd and use ur script without problem and without losing my apps ?

GonDr said:
i use Link2sd now, and want to try ur script, can i remove link2sd and use ur script without problem and without losing my apps ?
Click to expand...
Click to collapse
Try it, but remember to take full Nandroid backup before trying.
You can do this:
do full Nandroid backup from recovery
With Link2SD move all applications back to internal memory
delete mount scripts created by Link2SD (probably there is a kind of uninstall option in Link2SD)
install my mod
If you don't have enough space in internal memory, then it is possible to use Titanium Backup to backup and restore apps (however I am not sure whether Titanium Backup can backup data of applications linked with Link2SD - probably can, but I am not sure).

DavisNT said:
Try it, but remember to take full Nandroid backup before trying.
You can do this:
do full Nandroid backup from recovery
With Link2SD move all applications back to internal memory
delete mount scripts created by Link2SD (probably there is a kind of uninstall option in Link2SD)
install my mod
If you don't have enough space in internal memory, then it is possible to use Titanium Backup to backup and restore apps (however I am not sure whether Titanium Backup can backup data of applications linked with Link2SD - probably can, but I am not sure).
Click to expand...
Click to collapse
I don't think that titanium can restore anything to sdext, it just saves anything, including linked stuff and if trying to restore everything together it will fail, if the total of backed apps is larger than internal storage...
However, if link2sd is installed, the later will start linking data/apps 'on the fly' as Tib restores them. That's why it is essential to install link2sd or similar before going to batch-restore everything.
I guess this script should handle it in a similar way? I'm going to try anyway.

My idea was backing up most of apps with Titanium Backup while using Link2SD, then removing them (and moving left apps back to internal memory, uninstalling Link2SD mount scripts) and restoring after installing my script (Move to sd-ext).
Move to sd-ext links all applications (and dalvik cache, but not application data and library files extracted to data folders) at once - Titanium Backup will restore directly to SD card

can you explain me what's the difference between this mod and d2sd ungaze?
thanks

mutia said:
can you explain me what's the difference between this mod and d2sd ungaze?
thanks
Click to expand...
Click to collapse
If I correctly got what D2SD ungaze does, then it moves applications, applications data and libraries (/data/app, /data/app-private and /data/data) to SD card ext partition and leaves Dalvik cache (/data/dalvik-cache) on internal memory (/data partition).
While my mod moves and links applications and Dalvik cache (see first post in this thread for details), leaving all other folders (some system configuration and application data and libraries) in internal memory (/data partition).
Also technical implementation is very different from my mod. D2SD ungaze copies everything and links back certain things. It looks like D2SD ungaze also doesn't free space on /data partition.

DavisNT said:
You can make full Nandroid backup (Nand backup in recovery) and try whether it works on your ROM.
This requires the following things:
ext partition on SD card (you must have partitioned your SD card)
ROM that supports init.d scripts
kernel that supports ext filesystem version that is on SD card
You can test all this by (making full Nandroid backup and) flashing sd-ext_patch-signed-vXX.zip, booting in Android and issuing the following commands in Terminal Emulator:
Code:
su
mount
mount | grep sd-ext
If you see line like this somewhere in the output:
Code:
/dev/block/mmcblk0p2 on /sd-ext type ext4 (rw,noatime,nodiratime,barrier=1,data=ordered)
then /sd-ext is mounted and you can proceed to flashing to_sd-ext_patch-signed-vXX.zip.
Apps are moved when flashing to_sd-ext_patch-signed-vXX.zip.
Click to expand...
Click to collapse
i flashed the first zip file, then made this test through Terminal Emulator and got a line similar to the one you mentioned (my sd-ext is type 3, and the info in brackets was a bit different).
then i flashed second zip file.
the free RAM space increased (which necessarily means that things were moved to the sd-card, right?)
i then installed an app - and saw RAM decreasing accordingly, plus - the sd-ext folder is empty
how can i know if it works ?!?

[Q] TF101 Installing Custom ROM on Encrypted device

I recently managed to successfully root my TF101.
I installed CWM (Via ROM Manager) and downloaded CM9
I boot into CWM and attempt to do a nandroid...can't find path.
I attempt to just install from SDCard...can't find path
Realization (and research) hits that CWM can't see the external sd, and the system doesn't see it as SDCARD but EXT-.
CWM can't see the internal SDCard because apparently on the Tablet the ICS encryption locks that down (but doesn't on my EVO since the SC Card isn't part of the internal storage)
I attempt to perform a factory data wipe to clear out the encrtyption , but upon reboot CWM loads. I try to perform the boot-launcher data wipe, but then CWM loads.
I try to use CWM to factory reset but since it can see the damned SDCard because of the encryption, no dice.
My machine is not bricked, as I can still boot into the previous install but I can't seem unable to format the thing to install CM9.
What to do, and thanks.

It has been said multiple times before DO NOT USE ROM MANAGER.
Either use Thing O Doom's peri to install a different CWM or Gnufabio's Recovery installer or NVFlash a rom to completely wipe. And don't use encryption there is no point 99% of the time

I didn't check here first, which is obviously what was my first mistake.
Will any of those recoveries be able to access and format the SD Card area?
Also, I use encryption as I do have sensitive things on my machine that I don't want exposed in case the machine is stolen. First time I've ever had it give me a problem, as the phone encrypts differently.

Team roug's recovery has internal and external sd support and i think the encryption is an ics/tegra 2 bug more than anything

Ok, so I managed to get the new recovery on via Thing O Doom's peri. And I was able to install Revolver via the ext card...but upon boot I was prompted for my encryption pin and got the message that android was updating...My Build number is now Revolver but everything is the same as it was. I still can't factory wipe this damned thing.
Upon request to wipe, it boots back to recovery and says formatting data and cache, data wipe failed.
Tis site states http ://0xfeedface.org/blog/lattera/2012-06-04/installing-cm9-encrypted- android-tablet
The dilemma
When you encrypt your Android device, the /data partition is what gets encrypted. The partition in full is encrypted and cannot be mounted within CWM. CWM also cannot perform a wipe, since it cannot mount the /data partition. And CWM cannot mount the external SD card. This is our dilemma. No access to the internal SD. No access to the external SD. No way to perform a wipe and format the internal SD from CWM.
The Solution
What we need to do, then, is use adb while the tablet is in recovery mode to reformat the internal SD card, thereby removing the encryption. On the US Transformer Prime, the internal SD card is at /dev/block/mmcblk0p8. The partition for our spare SD card will be at /dev/block/mmcblk1p1. You will need to replace those device entries for any other device you might attempt this on. After formatting the internal SD card, we will mount it and then mount the external SD card at /data/media:
In CWM, wipe cache
adb shell
mke2fs -t ext4 /dev/block/mmcblk0p8 # Warning: This can take a while. Be patient.
mount /data
mount /dev/block/mmcblk1p1 /data/media
Now go back to CWM on your device, then go ahead and flash your CM9 and gapps zips like normal. You now have CM9 installed! The /data partition is not encrypted. If you do not need to flash any other ROMs (unlikely if you're reading this article), feel free to re-encrypt your device.
Click to expand...
Click to collapse
I don't know the block numbers for the TF01

you need to undo the encryption before you can wipe anything

You can't. Hence my problem. I cannot mount,delete, or format the SDCard. It sounds like the process in the above post is the solution, but I don't know how to find out what block numbers the tf101 uses.

If you don't mine losing your data NVflashing a rom will resolve all the problems

Yep nvflash will do the trick otherwise as the solution you found yourself explains
Use adb in recovery ( in other words hook it up on a pc ) for this you will need android sdk runnin on your pc
More info about adb u can find here
http://forum.xda-developers.com/showthread.php?t=1751439&highlight=adb+help
Good luck

Thanks to all, I have resolved my issue!
I had to download the stock rom, extract the blob, and use Wheelie for PC to NVFlash everthing abck to stock. I was then able to update over OTA, and use the excellent Thing O Doom's peri to re-root and flash the working recovery.
There should be several items in the Root FAQ up top, such as:
If you are encrypted and going to root, factory reset to get rid of the encryption FIRST since the encryption locks down the SDCARD partition (Unlike on the phone)and none of the recoveries can access it to mount. DON"T use ROM manage on the TF101 and always, always check XDA first.
:good:

darthrater said:
Thanks to all, I have resolved my issue!
I had to download the stock rom, extract the blob, and use Wheelie for PC to NVFlash everthing abck to stock. I was then able to update over OTA, and use the excellent Thing O Doom's peri to re-root and flash the working recovery.
There should be several items in the Root FAQ up top, such as:
If you are encrypted and going to root, factory reset to get rid of the encryption FIRST since the encryption locks down the SDCARD partition (Unlike on the phone)and none of the recoveries can access it to mount. DON"T use ROM manage on the TF101 and always, always check XDA first.
:good:
Click to expand...
Click to collapse
That FAQ is sadly pretty outdated, I wish I could liberate the OP
Glad all is working now though.

Can't backup sd-ext even though I partitioned it correctly.

Hi,
I used ROM Manager Premium v5.0.1.5 to partition my sd card and linked the apps with link2sd which worked just fine.
Problem is, when I wanted to backup the system ROM Manager didn't recognize my partition.
Why would that happen since I used ROM Manager itself to create the partition in the first place?
Doesn't make much sense that the app creates it and then can't backup it at all.
Can anyone shed some light on this issue?
Thanks!

Used EASEUS Partition Manager and it actually showed the partition as OTHER so I formatted it into EXT3. Still no luck mounting it through ROM Manager.
EDIT: Flashed CWM Recovery v.5.0.2.0 and after partitioning the sd card again it now mounts/backups it correctly. You can get it from: http://forum.xda-developers.com/showthread.php?t=1523050
EDIT: The earlier version of CWM doesn't work either. Flashed AmunRa recovery and it seems to work now.

i think its prblm with the clockwork mod recovery. instead of usng it try amonra recovery(flash amonra recovery and dnt use rom manager for this)

clockworkmod told me sd-ext backup is not supported on my device...
when i cleared my sdcard partition and did a backup it backed up sd-ext also.
i believe i just had not enough space on my sdcard..? may fix your problem

MM internal memory solution

Hi guys,
I'll share some scripts (flashable) that I've made to help with xperia l internal memory shortage.
1. First one is the link2sd-enabler.zip: http://www24.zippyshare.com/v/UduJGjqJ/file.html.
For this to work you'll need a second partition on the external sdcard formated as ext4. So first partition is the vfat one, the second primary partition on the external sd card is the ext4 one. Currently I have a 8Gb ext4 second partition.
Installation procedure: prepare your external sdcard, flash the zip, install link2sd application.
2. Second is the 01link2sdmm: http://www86.zippyshare.com/v/9DSgorlH/file.html.
The link2sd application does not automatically link the oat directory of the application. This directory contains the compiled application in the form of an odex file. For big apps this file is pretty big. So this script will automatically link this directory to the sdcard second partition for the applications that are linked to the sdcard. This works in conjunction with the link2sd-enabler.zip script.
Installation procedure: put this script in the /etc/init.d directory with the proper permissions. This way it will run at boot. If you want to run this directly after you link an app you'll need to use automagic and make a rule to run this script after you exit the link2sd application.
Observations: This script is not needed if you switch the internal partitions because you'll have enough space to keep the odex file internally. It's your choice.
3. Third script is the mm-partition-swapper.zip: http://www10.zippyshare.com/v/eyRO7gLw/file.html.
This one will switch your sdcard and userdata partition on your current mm rom. This was tested on rr573 that I have installed, but it should work in other mm roms as well.
Installation procedure: Make sure you have enough space on the external sd card so the script will be able to save your current data partition files. Save the files that you need from your internal partition to your external sd card. Make a backup of your current rom from twrp in case something wrong happens. Format from TWRP the internal sd card as ext4. Flash the zip. If everything works ok then you'll have a rom with the internal partitions swapped and you'll have 4Gb of user data available (minus your space for the already installed apps).
!!!!!!!!!!!!!!!!!!Very important!!!!!!!!!!!!!!!!!!
Don't try formatting the internal sdcard as ext4 with twrp version 3.0.2! It seems that his twrp version does not support this. I'm using twrp 2.8.7.0 by Barbarosa.
Observations: Twrp does not support backing up/restoring internal sd. If you swap partitions you'll have to backup your ext4 internal sd manually from within twrp connected through adb (with a simple tar command)
4. I think 256 ZRAM for the rr573 rom is too big so this zip will change this to 128MB:
mm-128Mb-zram.zip:http://www103.zippyshare.com/v/XjVAnXEl/file.html.
Please make a backup before flashing the swap zip and report if this worked for you.
Hope this helps,
Thanks.

cojocar.andrei said:
Hi guys,
1. First one is the link2sd-enabler.zip:
For this to work you'll need a second partition on the external sdcard formated as ext4. So first partition is the vfat one, the second primary partition on the external sd card is the ext4 one. Currently I have a 8Gb ext4 second partition.
Installation procedure: prepare your external sdcard, flash the zip, install link2sd application.
Click to expand...
Click to collapse
I've been struggeling for quite some time to get the link2sd app working since I flashed MM.
I've done a clean install, flashed the zip, installed link2sd, but I still get a 'mount script error, Cannot create script, mount: no such file or directory.' Anyone got an idea what I do wrong?
thx!

mikelektro said:
I've been struggeling for quite some time to get the link2sd app working since I flashed MM.
I've done a clean install, flashed the zip, installed link2sd, but I still get a 'mount script error, Cannot create script, mount: no such file or directory.' Anyone got an idea what I do wrong?
thx!
Click to expand...
Click to collapse
Check if you have in the /etc/init.d directory the 00link2sd script. For this script to work you need a rom with a working init.d (otherwise this won't work obviously...). If you have the script there, then check if you see a directory /data/sdext2 (if this directory is missing, but you have the 00link2sd script in the /etc/init.d directory, then this means you don't have init.d support in the rom). If you partition your sdcard correctly then the second ext4 partition of you sdcard should me mounted in the /data/sdext2 directory ... All these you need to check before installing the link2sd app...

Awesome! Thank you. I'll try this

cojocar.andrei said:
Check if you have in the /etc/init.d directory the 00link2sd script. For this script to work you need a rom with a working init.d (otherwise this won't work obviously...). If you have the script there, then check if you see a directory /data/sdext2 (if this directory is missing, but you have the 00link2sd script in the /etc/init.d directory, then this means you don't have init.d support in the rom). If you partition your sdcard correctly then the second ext4 partition of you sdcard should me mounted in the /data/sdext2 directory ... All these you need to check before installing the link2sd app...
Click to expand...
Click to collapse
I have the init.d folder, but it seems the sdext2 folder was only created after I installed the link2sd app.
I tried doing it all over again, but it still doesnt work, same messages...

mikelektro said:
I have the init.d folder, but it seems the sdext2 folder was only created after I installed the link2sd app.
I tried doing it all over again, but it still doesnt work, same messages...
Click to expand...
Click to collapse
Then your rom doesn't have init.d support. You need a kernel/rom (more precisely a ramdisk) with init.d support to use this ... The rr573 supports init.d ... Try it with this one ...

cojocar.andrei said:
Then your rom doesn't have init.d support. You need a kernel/rom (more precisely a ramdisk) with init.d support to use this ... The rr573 supports init.d ... Try it with this one ...
Click to expand...
Click to collapse
Thx! Which do you recommend? I've tried several in the last two or three months. Now I'm running AOSP-OMS.
I ran slim, RR and CM 13 beta before without any problems, just the storage issue.

mikelektro said:
Thx! Which do you recommend? I've tried several in the last two or three months. Now I'm running AOSP-OMS.
I ran slim, RR and CM 13 beta before without any problems, just the storage issue.
Click to expand...
Click to collapse
I've just told you. RR573. For a completely working camera on this one just replace a camera library... Search the rr thread...
Sent from the center of the galaxy

3. Third script is the mm-partition-swapper.zip: http://www10.zippyshare.com/v/eyRO7gLw/file.html.
This one will switch your sdcard and userdata partition on your current mm rom. This was tested on rr573 that I have installed, but it should work in other mm roms as well.
Installation procedure: Make sure you have enough space on the external sd card so the script will be able to save your current data partition files. Save the files that you need from your internal partition to your external sd card. Make a backup of your current rom from twrp in case something wrong happens. Format from TWRP the internal sd card as ext4. Flash the zip. If everything works ok then you'll have a rom with the internal partitions swapped and you'll have 4Gb of user data available (minus your space for the already installed apps).
Click to expand...
Click to collapse
I use rom AOSP OMS . file zip working?
Brick and problem other ?
Thx you building script .
Thx advanced

I am on stryflex MM ROM and TWRP 3.0.2.
I formatted internal storage as ext4, then flashed mm-partition-swapper.zip.
Says that there is no ext4fs partition and I tried reboot recovery and my phone is dead now, can't turn it on...
I don't blame you, I blame myself for trying. But please help. Flashtool doesn't recognize flash mode.
Don't use this method. Not safe.

Option58 said:
I am on stryflex MM ROM and TWRP 3.0.2.
I formatted internal storage as ext4, then flashed mm-partition-swapper.zip.
Says that there is no ext4fs partition and I tried reboot recovery and my phone is dead now, can't turn it on...
I don't blame you, I blame myself for trying. But please help. Flashtool doesn't recognize flash mode.
Don't use this method. Not safe.
Click to expand...
Click to collapse
Sorry to hear this. If the script gave you this error then the script did nothing to your phone. It just aborted the procedure because it did not find the sdcard formated as ext4. It must be the twrp version. I'm using twrp 2.8.7.0 by barbarosa. I think twrp 3.0.2 does not support formatting the internal sdcard as ext4. Most pobably the twrp version 3.0.2 formated something else as ext4 or whatever instead of internal sd... I did not know this. Sorry again...
Try to search the brick threads. If you still have a blue light when in flashmode I think you still have a chance to resurect it...
Sent from the center of the galaxy

I've modified the post to warn people of this twrp version. So, people, use only twrp 2.8.x.x to format the internal sdcard. I'm using 2.8.7.0 twrp version by Barbarosa. I don't know if other twrp versions support ext4 on internal sdcard.
Sent from the center of the galaxy

Thanks for the solutions. So now if I only need to swap internal sd and /data, i just need to flash 3rd script? I'm quite confusing about partitioning and memory stuffs

newguyknowsnothing said:
Thanks for the solutions. So now if I only need to swap internal sd and /data, i just need to flash 3rd script? I'm quite confusing about partitioning and memory stuffs
Click to expand...
Click to collapse
You have to have twrp 2.8.7.0, then format internal sdcard as ext4 (wipe settings) and then flash the zip...
Sent from the center of the galaxy

Yes, formatting internalSD as ext4 is tricky. My recovery was broken. Probably formatted something else. It wasn't your script.
However I have no volume up button on my phone (fell out) - no fastboot. And just volume down button (flash mode) and a somewhat broken USB cable. Phone not recognized by flashtool at all...

cojocar.andrei said:
You have to have twrp 2.8.7.0, then format internal sdcard as ext4 (wipe settings) and then flash the zip...
Sent from the center of the galaxy
Click to expand...
Click to collapse
Ok thanks! One more question, If I somewhat want to undo this, I need to back up the current MM rom before flashing the script? Will the internal sd and /data automtically be swapped back when I restore the back up?

newguyknowsnothing said:
Ok thanks! One more question, If I somewhat want to undo this, I need to back up the current MM rom before flashing the script? Will the internal sd and /data automtically be swapped back when I restore the back up?
Click to expand...
Click to collapse
After swapping the partitions your old backups of the rom will not work anymore (or probably they would just revert the swapping. Anyway if you want to restore a backup that's been done prior to swap it's better to format back by hand the internal sdcard to vfat and data to ext4)
For backing up a rom with swapped partitions you'll have to select the sdcard instead of data partition in the backup options... I did not try it yet...
Sent from the center of the galaxy

Option58 said:
Yes, formatting internalSD as ext4 is tricky. My recovery was broken. Probably formatted something else. It wasn't your script.
However I have no volume up button on my phone (fell out) - no fastboot. And just volume down button (flash mode) and a somewhat broken USB cable. Phone not recognized by flashtool at all...
Click to expand...
Click to collapse
I don't know, sorry. You have to search the brick threads...
Sent from the center of the galaxy

I ran the the link2sd enabler script on my rr573, works like a charm now.
Thank you so much, I needed this!
Didn't swapped the storages yet.

The dream is real!
Congratulations.
Seeking a long time for a script like mm-partition-swapper.zip
Before seeing your post, I had already made the formatting of SD0 (ext4) to try to install Link2SD to work with SD0 without work.
I used the TWRP 3.0.2.
I could easy return the partition to FAT.
I intend to make a clean installation of ROM on my device to then install your mm-partition-swapper.zip script.
As both the "DATA" as SD0 are empty you still think need to format with TWRP 2.8.7?
No way to change this script without the data transfer?
Only formatting partitions and inverted mounts?
If not necessary then ok...but... please clear this my doubts.
Again without getting tired ... very thank you even for your script.