Related
Hi
I'm using the htc desire with ClockworkMod Recovery v5.0.2.0
I wan't to enable data2sd . So first I made a a partition in the recovery 1025mb and 0 swap and installed the redux custom rom . afterwards trying to install data2sd. didn't work
so i wiped everything mada a a partition again and installed Supernova custom rom. Still there is only about 50 mb internal storage.
tried to make a partition with pc and clockworkmod.. no success.
please I try this for many hours now..
Thank you for your help I want to use my desire again
Your ext3 need to be ext4 clockwork mod cant convert ext3 into ext4.
I used MiniTool Partition Wizard
if someone is still searching for this...
read instructions here try a ROM with full support: StarBurst ROM
As I was getting low on my LG-P500 phone, I tried looking for some app2sd solution, doing the following steps:
- Backup all SD card content to PC
- Boot into recovery (CWM5.0.2.7)
- From recovery, create sd-ext partition
- From recovery, format the new partition
- From recovery, mount usb device, restore all SD card content from PC.
- Reboot device, installed link2sd and managed to link applications to sd.
Now link2sd seems to work fine- I tried linking quite a few applications and all of them work fine, no complaints. It only gave me an error with some apps which I have previously *moved* to SD using Titanium backup, but upon moving them to internal storage link2sd picked them okay.
However, I noticed that using file explorer, root explorer etc- they all show the sd-ext partition as empty, with size of 0 bytes??
Then, I booted into recovery and tried to mount the sd-ext partition, but I get an error message... (all other partitions I can mount/unmount just fine).
To be sure, after each reboot it looks like all the applications linked2sd work appropiately, so everything looks fine.
However, now I am concerned whether I can create (and restore, of course) nandroid backups- what will happen with all these apps linked to sd? Am I right that CWM may not be able to backup (and therefore restore) anything that is on this partition?
Am I going to lose all these apps and data? Does TiB backup these apps+data and be able to restore them fine to sd-ext? I'm asking about TiB as a mediocre workaround of restoring applications that were in sd-ext (and thus omitted by CWM backup). That is, after restoring nand backup- doing an additional restore from TiB??
Any help/insight is welcome
Ah, yes, some more info:
Phone: LG optimus P500
ROM: Lupohirps CM9 4.0.3 from this thread http://forum.xda-developers.com/showthread.php?t=1558213
Recovery: CWM 5.0.2.7 (By the way, whenever I try to flash 5.0.2.0 I get an error...)
that's weird since the app working. what ekstension do you have on sd card fat? fat32?
Can you open Android Terminal (https://play.google.com/store/apps/details?id=jackpal.androidterm) and issue these commands:
su
busybox ls -la /sd-ext/
busybox mount
If /sd-ext doesn't show up in mount, then it is not mounted.
Actually CM9 for P500 lacks file /system/etc/init.d/05mountsd (this file is responsible for mounting /sd-ext). IMHO You should ask ROM developer about sd-ext support.
If you want to test (and potentially restore your Nandoid backup or reflash CM9 afterwards) I can give you this script from CM7 (actually modified version that allows any ext version).
Your sd-ext files are actually in data/sdext2, not in /sd-ext.
Also Try using Amonra 3.0.6, overall it has better sd-ext support, I find it mounts and wipes things like dalvick cache inside the sd-ext partition as well , which is handy, unlike CWM.
Thanks for all your replies!
Sdcard file system is fat32. For the partition I have no idea as cwm didn't ask for any specific (e.g. ext2/3/4) and I haven't seen any way to get this Info...
Anyway, following this thread, I did find that all the app/data is in /data/sdext2- not sure what it means in terms of nandroid backup& recovery but it looks more reassuring..
As to RA recovery, I'm not in particular in love with cwm- it is just what I'm used to from other android devices I've been using. Actually on my htc mt4g I was using ext4 touch recovery and that one I really liked, but it is not supported in lots of devices. That phone was stolen, unfortunately. I'll give it a try, though.
Sent from my GT-P7510 using Xparent Cyan Tapatalk 2
DavisNT said:
Can you open Android Terminal (https://play.google.com/store/apps/details?id=jackpal.androidterm) and issue these commands:
su
busybox ls -la /sd-ext/
busybox mount
If /sd-ext doesn't show up in mount, then it is not mounted.
Actually CM9 for P500 lacks file /system/etc/init.d/05mountsd (this file is responsible for mounting /sd-ext). IMHO You should ask ROM developer about sd-ext support.
If you want to test (and potentially restore your Nandoid backup or reflash CM9 afterwards) I can give you this script from CM7 (actually modified version that allows any ext version).
Click to expand...
Click to collapse
Thanks! Looks likeb system/ cache/ data are all yaffs2, /mnt/Sdcard is vfat and /data/sdext2 is ext4. Not sure what all the output means (relatime, barrier=1, data= ordered etc. etc.)
So, can I figure out where the /data/sdext2 is physically stored? Is it actually the sd-ext/ext4 partition? Looks like must have, as its contents are way bigger than phone's 200MB internal storage...
Thank you all again
Sent from my GT-P7510 using Xparent Cyan Tapatalk 2
jaibar said:
Thanks! Looks likeb system/ cache/ data are all yaffs2, /mnt/Sdcard is vfat and /data/sdext2 is ext4. Not sure what all the output means (relatime, barrier=1, data= ordered etc. etc.)
So, can I figure out where the /data/sdext2 is physically stored? Is it actually the sd-ext/ext4 partition? Looks like must have, as its contents are way bigger than phone's 200MB internal storage...
Thank you all again
Sent from my GT-P7510 using Xparent Cyan Tapatalk 2
Click to expand...
Click to collapse
/data/sdext2 is the mountpoint for the ext4 partition thats on your sd card, physically its obviously on your sd card, but If you use linux, data/ is where the all partitions other then home partition get "attached"/mounted to, the 11link2sd script made by link2sd in yout init.d folder actually mounts it sdext2, the name means nothing, just something link2sd names it as.
---------- Post added at 08:40 PM ---------- Previous post was at 08:30 PM ----------
So Basically nandroid will not back it up under /data/sdext2 as the script runs after recovery, the best way to backup apps that are on the ext partion is back them up using Titanium Backup, as that saves the real apks, and when you restore all your apps, select link2sd to automatically move them to sd-ext partition.
Hi at all,
at first sorry for my bad english.
I had a similar case. If I made a backup with cwm 5.0.2.7, cwm cant mount/read the sd-ext.
In a other thread a user wrote, that cwm 5.0.2.8 had problems with the sd-ext.
And he does downgrade to cwm 5.0.2.0, and than cwm will work.
So, I did this:
I open the rommanager and choose the option "install Clockworkmod", now I choose the "LG Optimus One (old BB)".
But i have the new baseband on my O1.
The basis of this is, if you choose the new baseband in the rommanager, he will install cwm 5.0.2.7. For the old is it the 5.0.2.0 version.
Now, Rommanger made the installation with cwm 5.0.2.0. to my phone.
After this i go in to the recovery and made my nand-backup. It works perfekt!
No problems with the sd-ext, after I did this.
May be this will help.
Fietz said:
Hi at all,
I open the rommanager and choose the option "install Clockworkmod", now I choose the "LG Optimus One (old BB)".
But i have the new baseband on my O1.
The basis of this is, if you choose the new baseband in the rommanager, he will install cwm 5.0.2.7. For the old is it the 5.0.2.0 version.
Click to expand...
Click to collapse
Thanks for the tip..
I have tried in the past to flash cwm 5.0.2.0 via Rom Manager, but I kept getting an error message, so I gave up.
Now I thought to give it a second chance, but as it fails to flash with Rom Manager (in the menu when I choose LG optimus one I don't get any choice between old BB or new or anything- it just reflashes 5.0.2.7) and from the "all recoveries menu I can only choose 5.0.2.0 but it gives an error message), so I downloaded the zip files from this thread http://forum.xda-developers.com/showthread.php?t=1523050 (including also Amon Ra 3.06) and tried to manually flash from recovery.
It flashed and showed recovery as "5.0.2.0" but nothing worked- every submenu that I tried to enter was black screen (with the CWM logo on background) and it gave me the creeps- I don't like being stuck without a functional recovery so I rebooted and flashed 5.0.2.7 again from Rom Manager.
I'll try to flash Amon Ra and see how it works.
[EDIT] flashed AmonRa 3.06 and it seems to work fine- able to mount/unmount all partitions including sd-ext, and it also has an option to check each of them in separate during nandroid backups.
A noobish question: it has also an option to include the ".android_secure" . Isn't this one a redundancy with sd-ext (e.g. contains all the apps/data that has been moved/linked2sd)?
jaibar said:
As I was getting low on my LG-P500 phone, I tried looking for some app2sd solution, doing the following steps:
- Backup all SD card content to PC
- Boot into recovery (CWM5.0.2.7)
- From recovery, create sd-ext partition
- From recovery, format the new partition
- From recovery, mount usb device, restore all SD card content from PC.
- Reboot device, installed link2sd and managed to link applications to sd.
Now link2sd seems to work fine- I tried linking quite a few applications and all of them work fine, no complaints. It only gave me an error with some apps which I have previously *moved* to SD using Titanium backup, but upon moving them to internal storage link2sd picked them okay.
However, I noticed that using file explorer, root explorer etc- they all show the sd-ext partition as empty, with size of 0 bytes??
Then, I booted into recovery and tried to mount the sd-ext partition, but I get an error message... (all other partitions I can mount/unmount just fine).
To be sure, after each reboot it looks like all the applications linked2sd work appropiately, so everything looks fine.
However, now I am concerned whether I can create (and restore, of course) nandroid backups- what will happen with all these apps linked to sd? Am I right that CWM may not be able to backup (and therefore restore) anything that is on this partition?
Am I going to lose all these apps and data? Does TiB backup these apps+data and be able to restore them fine to sd-ext? I'm asking about TiB as a mediocre workaround of restoring applications that were in sd-ext (and thus omitted by CWM backup). That is, after restoring nand backup- doing an additional restore from TiB??
Any help/insight is welcome
Ah, yes, some more info:
Phone: LG optimus P500
ROM: Lupohirps CM9 4.0.3 from this thread http://forum.xda-developers.com/showthread.php?t=1558213
Recovery: CWM 5.0.2.7 (By the way, whenever I try to flash 5.0.2.0 I get an error...)
Click to expand...
Click to collapse
Hi, Jaibar
I have LG Optimus One with JB 4.2.2, CM 10.1.
Here what I have done in order to gain extra space on my internal memory. All the steps that you have followed are the same as I did. BUT! There are two important things that I have followed that had greatly helped to succeed:
1) For every 100Mb internal memory - NO MORE than 512Mb of SD card memory(for my LG I have separated 965Mb on the SD card)
2) INT2EXT+ works with EXT2/3/4 partitions BUT INT2EXT4+ works with ONLY EXT4 partition. After I have watched this short video, and this blog post I have been able to restart my phone with extended internal memory.
Believe me, for three days I have been flashing my phone, trying to find the correct way. At the end I have noticed that the problem was that I couldn't mount /sd-ext I thought that maybe following this two rules will help - and it did!
I hope that it will help! Good luck
I finally upgraded the ICS Plus by Hehappy from CM 7 GB and I increased the ext partition from 1 gb to 2gb as i was falling short of space. However the ROM is not recognizing the new EXT4 which I partitioned using Mini tool partition wizard. It don't show on Titanium Backup or S2E app. Then I converted it into EXT3 it still recognize it. Can you tell me what the problem is? Am I missing something?
I was using EXT2 with GB which I created using Clockwork recovery. But now I wanna use EXT4. Can you help me? Thank You.
Tried formatting with CWM
I formatted the the sd-ext partition with CWM and it was recognized by the phone. TB and S2E showed the information of the partition. However when I checked the information on the Mini partition tool, It shows that its a EXT2 partition. How to get EXT4 working on my phone?
If you have formatted ext partition using CWM it must be ext2. CWM uses ext2 format
Just try to format whole card from the start and partition it using only either CWM or Mini tool partition manager. If your using the tool make sure you do this using the card reader.
sarus_b said:
If you have formatted ext partition using CWM it must be ext2. CWM uses ext2 format
Just try to format whole card from the start and partition it using only either CWM or Mini tool partition manager. If your using the tool make sure you do this using the card reader.
Click to expand...
Click to collapse
I partitioned it with Mini tool partition like I have mentioned in my first post. It was not being recognised. It was only after I formatted the sd-ext with CWM that the sd-ext was being recognized. What am I doing wrong?
I dont think you are doing anything wrong. Maybe its bug in rom which causes the problem. There are same issues reported by some members who do not have ext4 working.
You can try amonra recovery and format partition to ext4 and see if it helps
sweettaniyaa said:
I finally upgraded the ICS Plus by Hehappy from CM 7 GB and I increased the ext partition from 1 gb to 2gb as i was falling short of space. However the ROM is not recognizing the new EXT4 which I partitioned using Mini tool partition wizard. It don't show on Titanium Backup or S2E app. Then I converted it into EXT3 it still recognize it. Can you tell me what the problem is? Am I missing something?
I was using EXT2 with GB which I created using Clockwork recovery. But now I wanna use EXT4. Can you help me? Thank You.
Click to expand...
Click to collapse
Flash AmonRa recovery. Backup your SDcard. Erase SDcard from Settings> Storage.
Partition SDcard through recovery. Upgrade it first to ext3 then to ext4. You can see these options in AmonRa.
rr0yy said:
Flash AmonRa recovery. Backup your SDcard. Erase SDcard from Settings> Storage.
Partition SDcard through recovery. Upgrade it first to ext3 then to ext4. You can see these options in AmonRa.
Click to expand...
Click to collapse
Thanks I will try that but after I get back to my normal routine. Right now I am traveling. Till then I will go with EXT2. But I am facing a heavy battery drain. I have my wifi on almost all the time. Probably that's it. But its almost twice as that it was with GB. Any solution to it? Also the volume of the phone ring seems to be less than GB at its highest level.
sweettaniyaa said:
Thanks I will try that but after I get back to my normal routine. Right now I am traveling. Till then I will go with EXT2. But I am facing a heavy battery drain. I have my wifi on almost all the time. Probably that's it. But its almost twice as that it was with GB. Any solution to it? Also the volume of the phone ring seems to be less than GB at its highest level.
Click to expand...
Click to collapse
If you are sure its already ext2 then you just have to flash amonra recovery and upgrade it to ext4.I never used ext2 so i cant tell you any advantage of ext4 over ext2.
Download wifi TX power from playstore and reduce wifi txpower.. See if it helps.
Edit: Battery drain is due to v3 kernel.. No solution to it yet.
Please help me...I flashed the FlyROM V4 correctly but its stuck at boot animation...when i go to mount sd-ext..its shows "Error mounting sd-ext"..is that the problem? If it is..how to solve it?
Make Sure You Made A Sd-Ext Partition Correct, To Check Whether You Made A Partition Correct Or Not, Just Mount Sd-Ext In Recovery, If It Mounts Without Any Error Then Just Go Ahead, But If It Shows An Error, It Means You Didn't Make A Partition Correct. So Now What You Need To Do Is:
1. Don't Partion Your SD Card By Using Recovery.
2. Partition It Via "Minitool Partition Wizard" Manually.
3. Create A Ext 4 Partition As Primary.
4. Now, Install Yannou's Recovery (The One Which You Install While Rooting)
5. Finally, Mount Sd-Ext And Flash Any Sense 4 Rom..
Note: Don't Use CWM Recovery, It Never Mount Sd-Ext At Any Cost.. Use Yannou's Recovery Or Philz Touch Recovery Instead..
Sent from my HTC Explorer using xda premium
thanks for replying here..i got the problem solved by just
1. removing old partitions
2. changing to philz recovery
3. making a new partition using philz and then flashing..
But now am unable to install any kind of memory script to increase internal memory..even after installing successfully .. the memory isnt increasing..what's wrong?
First open ur rom zip, navigate to system/etc/init.d and remove that 78mv2ext file and replace it with ur desired script and then reflash rom..
But do this at your own risk, if u get into a bootloop just reflash the rom with 78mv2ext script again..
Note: in sense roms, internal memory will always be 150 mb, but when you install apps its internal memory will not decrease as it decreases usually because of that Sd-Ext Partition you created..
Sent from my HTC Explorer using xda premium
lol i didnt know internal memory is always 150mb..but it doesnt decreases..if its true..then there's no problem.
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.