Hello
The following guide will explain how to free your File System root partition by moving most of your apps/games to a new partition on your external SD Card.
I recommend to use at least a Class-10 SD-HC SD Card.
I've checked the following on my ZTE Nubia Z7 Mini, but AFAIK it should be working with all Z7's versions.
(please report if you can... )
IMPORTANT!
NEVER use custom TWRP recovery ver 2.8.1 (maybe 2.8.0.... latest 2.8.3) for re-partition microSD card in this phone!
When you try to perform this operation will be erase INTERNAL phone memory instead mircoSD, GPT partition table will be damaged and your's device turn into a Hard brick.
If you have not made a backup EFS+NV of your device, it may happen that it is impossible to recover and it will turn into iPods
Thank you @Harwest
1. Backup your 64gb SD card to PC.
2. Via PC - use MiniTool Partition Wizard to create 2 partitions on your SD card.
one partition should be formatted as exFat and will be your data partition (and so will be the largest!)
second directory should be EXT4 and will be your new system partition (all apps will be installed to this partition-will see that later)
my settings are - 54gb for exFAT partition 1, and the rest for the EXT4 partition.
3. after you've done all partitioning etc, insert the SD card to your phone.
4. go to Settings --> About Phone --> Storage --> Choose Primary Storage --> SD CARD
5. restart your phone.
6. Install "Link2SD" from Google Play.
7. when you first open the App, it will ask you which type of 2nd partition you have, choose EXT4, afterwards restart phone (it will ask you to do so).
8. open Link2SD and filter the list by "ON INTERNAL" and start moving applications by choosing the app you want to move and choose "Create Link". now make sure you check all 3 checkboxes (or 4 if you have the paid version on L2SD).
you'll see that your original system partition is getting bigger! that's all
Enjoy!
Thank for this info
tnx for the info.
i used a slightly different approach:
1. repartion the internal sdcard. (enlarged the 'userdata' partition to 11.7GB, shrunk the 'grow' (internal storage) partition to 1GB).
2. go to Settings --> About Phone --> Storage --> Choose Primary Storage --> SD CARD (== external sdcard)
so apps have 11.7GB, external storage is the full size of de sdcard (here 64GB).
done.
---
Per request a tutorial:
WARNING: DANGEROUS.
you can brick your device!
I do not know if this tutorial works with a rom other than stock (or stock based; i.e.: cuoco92). Because of the built in option to set external sd as primary storage. The partition tool should work on all z7 mini and z7 max.
What will this tutorial do?
Repartition tool:
it will :
backup your partitions (in a backup folder).
change the 'userdata' partition size to the given value
change the 'storage' (called: 'grow') partition (internal sd / sdcard0) to the size left on the internal sd.
i.e.: default 'userdata' = 2GB, 'storage' = 10GB, total 12GB. When giving 11GB to the repartition tool the new layout will be: 'userdata' 11GB, 'storage' 1GB, total 12GB.
Change primary storage in ROM:
The setting 'change primary storage to SD card will change symlinks in the rom from /storage/sdcard0 to /storage/sdcard1. Result is that every app in the rom thinks sdcard1 is sdcard0.
I do not know if other roms (i.e.: Mokee / CM11) have this built in option.
The tutorial:
Preparations:
MAKE A BACKUP OF EVERYTHING AND COPY TO A COMPUTER (or external SD).
Internal storage will be backuped by the tool (and restored). But for performance empty it.
external storage will not be emptied (make a backup to be safe).
clean install is highly recommended, but not necessary.
installed rom will NOT be wiped. You can boot normally after the procedure.
CWM recovery mandatory.
adb access to the phone (so install drivers etc).
Step1: Using the resize tool (resizeZ7_1024.Rayures.v01.zip):
Repartition Internal SD (z7 Mini and z7 Max):
reboot phone to recovery
i.e.: "adb reboot recovery"
unzip the zip
run RUN.bat
or: open 'command window' in the folder and run RUN.bat
select 1 (backup - delete - rebuild)
give size for 'userdata' partition
(Z7 mini: max = 11GB). 12GB gives no usable partition. 1GB internal data partition left, which i think is needed
done
notes:
just always use the 1 option and MAKE SURE the backup has been created! When the backup is missing or broken you WILL brick.
this thread also has a lot about the partition tool, use the search.
Step2: Set external SD as primary
Boot phone.
Go to: Settings --> About Phone --> Storage --> Choose Primary Storage --> SD CARD
reboot phone
done
The tool: resizeZ7_1024.Rayures.v01.zip (5.48 MB):
original from official nubia forum:
http://bbs.nubia.cn/
my changes:
-translated to English
-enhanced recognition of phone model
-added a 'partition info' option (to see the current partition layout)
tnx to:
-all the xda people who already used the tool in: <thread>
-original dev of the tool
Have an addition to this tutorial ? please do so via PM.
rayures said:
tnx for the info.
i used a slightly different approach:
1. repartion the internal sdcard. (enlarged the 'userdata' partition to 11.7GB, shrunk the 'grow' (internal storage) partition to 1GB).
2. go to Settings --> About Phone --> Storage --> Choose Primary Storage --> SD CARD (== external sdcard)
so apps have 11.7GB, external storage is the full size of de sdcard (here 64GB).
done.
Click to expand...
Click to collapse
Yea, I know that way , but I think it's more risky than my method...
repartitioning your internal memory can cause some trouble later on upgrades etc...
but thanks anyway, If you can, post a detailed guide so people can use your method also. :good:
Hi guys!
NEVER use custom TWRP recovery ver 2.8.1 (maybe 2.8.0.... latest 2.8.3) for re-partition microSD card in this phone!
When you try to perform this operation will be erase INTERNAL phone memory instead mircoSD, GPT partition table will be damaged and your's device turn into a Hard brick.
If you have not made a backup EFS+NV of your device, it may happen that it is impossible to recover and it will turn into iPods
Best way for repartitioning Nubia Z7 mini?
OK, but which is the best and most save way for repartitioning Nubia Z7 mini? Which custom ROMs are compatible with this mod and advisable? Thanks for your help!
tie-fighter said:
OK, but which is the best and most save way for repartitioning Nubia Z7 mini? Which custom ROMs are compatible with this mod and advisable? Thanks for your help!
Click to expand...
Click to collapse
Best & safe method for repartition microSD card:
Use a laptop/computer with a card reader and software like as "MiniTool Partition Wizard Home Edition" (freeware) http://www.partitionwizard.com/free-partition-manager.html
Insert to cardreader with your's sdcard, run "Partition Wizard", select existing partition on sdcard and press "Resize/Move".
Resize partition so that the end is left free space volume approx 1....2....3Gb (as you wish).
After that select free space and press "Create", create new primary partition, format EXT2 or EXT3.
Press "Apply" for start all process.
Resize procedure of existing partition is safe, nothing is lost. But just in case you can pray, drink or smoke:laugh:
Im struggling with this, although seems easier, i think I am doing something wrong.
fbloise said:
Im struggling with this, although seems easier, i think I am doing something wrong.
Click to expand...
Click to collapse
you don't need to struggle..
Just do the safe method on post #1, follow exactly the steps I wrote and you'll be OK.
if you have any specific question please post it here. :good:
I've used the ripartition method wit an EXT4 and a exFat on my 32 gb memory.
Link2SD goes very well also with the CM12 rom.
Just few questions ...
1 - Should I format the entire system for a clean reinstall of the ROM, what would happened to the programs in ext4 partition? Should I've to re-install them or they remain stored or should I do some other action?
2 - If I'll change memory ... I've to copy the program with linux, right?
lelepanz said:
I've used the ripartition method wit an EXT4 and a exFat on my 32 gb memory.
Link2SD goes very well also with the CM12 rom.
Just few questions ...
1 - Should I format the entire system for a clean reinstall of the ROM, what would happened to the programs in ext4 partition? Should I've to re-install them or they remain stored or should I do some other action?
2 - If I'll change memory ... I've to copy the program with linux, right?
Click to expand...
Click to collapse
1. I think the best way is to use MODACO titanium backup and after rom is replaced, to restore the apps.
other method is to use Link2SD to move the apps back to phone memory (not all of them..) and then use TB same as above...
2. you can just use any partition manager software in order to copy the partitions as it. try to use Gparted live, I think it's the most clean way..
please report back what was working best for you
thanks!
Related
hi yal
my internal memory have about 40mb left and is startting to get low ..
so is there a way to increase it ? i use tita backup to move apps but there still traces of bytes left ...i have about 60apps / games and themes ...so any help?
Look for "Link2Sd" in the market that's the easiest way I think.
Greetings !
Sent from my GT-S5830 using XDA App
link2sd needs partition sd card yes? how do i partition it by the way?
Flash cm7 and use s2e ..after that ull be trying to find apps to fill the memory but u will never be able to fill it cause even if u have 130apps (like i had) it uses ONLY 50 MB ..reamaning goes to sd ext..u can partition ur sd card using CWM5/CWM4...
Sent from my SGA rocking CM7.2 by vo-1 + all-in-one script
Link2SD:
What is needed:
- Root Permission
- The second partition on the SD Card, and both MUST PRIMARY
The first partition is the default storage of data on the SDcard. The second partition (which will be created) is a partition for storage applications for Link2sd.
download "MiniTool Partition Wizard Home Edition" on the PC, then plug the sdcard in the PC (u can directly use the phone, or card reader). by using this program, agan no need to format, partition, or delete data in the beginning, to create a new partition.
Install and open minitool, select the drive which will be partitioned sdcard, select resize the unallocated area. for PRIMARY, NOT logical. Free partition size is up. klo above 2GB FAT32 file system should pake. FAT32 support is generally on all phones. APPLY, and then turn on the phone.
(for more secure data back up anyway in the SD Card)
- Install Link2sd, have mounted, select FAT32, restart again and Tada!! Applications can be moved to SD, ga who need to use complicated script
Good luck. and must have successfully ...
Good Tutorial !
Sent from my GT-S5830 using XDA App
is there a difference between s2e and apps2sd? i used link2sd before on my old w8 (forgot how to partition now ) but it's quite unstable since apps constantly force crahses
oh oh ! can i partition using cwm ? like this
http://acetips.wordpress.com/2011/10/03/how-to-partition-your-sd-card/
i don't dare to use yet since i fear it will screw my phone
Do NOT use ClockWorkMod !!!
You can flash ClockWorkMod Recovery ,from where you can partition your Sd Card.
For cwm recovery there is no root needed,just flash it from stock recovery.
I hope that helped
Sent from my GT-S5830 using XDA App
oh ok then so i reboot to cwm then partition?
Yes, under the "advanced" tab
Select the Size of your 2nd Partition and 0mb for cache (not needed)
Remember that all your data from SD Card will be deleted !
Then reboot your Phone and start link2SD. When you´re asked about 2nd partition format, choose ext2 (I hope, I didn´t use this for ages!) If you get an error, it was the wrong format
Link2SD will ask you for a reboot and after that you can start to move your apps.
One Question, the build-in option to move apps is not enough ? I am not using so many apps, so I really don´t know.
Greetings!
Sorry if i sound like a noob but can i take advantage of the ext3 partition on my SD using this version of CM?
I partitioned my SD using clockworkmod, which is why it's ext3.
only app i've tried is Link2SD but when i tell it there is an ext3 partition on the card it creates a script and asks me to reboot.
Once that's done and i access the app again it goes through the same motions and informs me that - "if im seeing this message then the partition is unable to be mounted during boot"
Appreciate any help
Here's a quick way to install Link2sd.
I preassume that your device is rooted and your sdcard data is backed up.I think,the mount script didn't work because of inappropriate attributes..Ok heres,how i installed Link2sd...
1.First of all download and install MiniTool Partition Wizard in your windows PC.
Connect your handset to the PC via USB.
2.Launch MiniTool Partition,you should see your SDcard mentioned in the list Under Disk 2 probably.
3.Right click your SDcard mentioned in the list, press "Move/Resize Partition"
4.In the Partition size,allocate bigger chunk of partition for primary partition.This is the partition your phone will access for general purpose.Say you allocate 7GB from your 8GB memory card.
Click OK.
5.Now Under disk 2. you will see and unpartitioned space of about 1GB.This partition will be used by link2sd.You may allocate your sdcard as you may wish.
6.Right click the upartitioned space to create a new partition under "Create As".If a warning popup asks for permission click YES.
7.Under New window Create As,choose "Primary".For File System type choose 'FAT32'.though you may choose among ext3 or ext4,either is supported by link2sd.NTFS is not supported by Link2sd or android OS.For partition size take whole unallocated space.Click on OK
8.Click Apply button<upper left corner in the screen>.
9.Restart your phone.
Again use your Link2sd app to create mount script.Now your app should work fine.
Don't forget to hit THANKS if i helped you.
I would not suggest you to create the Link2sd partition as a FAT32 one: this way when you will connect your phone to a PC through the USB cable Windows will mount all the 2 partitions automatically (with all negative consequences you can imagine); this issue will not happen on Linux, however; while with the Link2sd partition formatted as extX you will be able to use your linked apps while the phone is connected to your PC and the first partition is mounted, it doesn't matter if you are on Linux or Windows (tested )
Regarding your problem: try to tell the Link2sd script activator that your partition is an ext4 and see if it works.. I hope so, anyway let us know..
@brainvision
yeah thanks,extX would be better..bt i think windows doesn't mount two sdcard Fat32 partition at a time.i may be wrong in this term, bt sometime back,when i used to use rooted android 2.1,windows would mount only my 1st primary partition of sdcard..however under ubuntu..both partition would load bt without affecting the phone apps.
thinkfreedom said:
@brainvision
yeah thanks,extX would be better..bt i think windows doesn't mount two sdcard Fat32 partition at a time.i may be wrong in this term, bt sometime back,when i used to use rooted android 2.1,windows would mount only my 1st primary partition of sdcard..however under ubuntu..both partition would load bt without affecting the phone apps.
Click to expand...
Click to collapse
oh sorry I'm not a winZoZZ user since a lot of time!! I'm a slacker now!!
Regarding Linx OS: I set up my Slackware so that it doesn't auto mount external disk, so i can plug in the phone and activate the USB Mass storage without still mounting it: this way I can mount only the first partition; but in a auto-mount situation I fear that the the phone apps would be affected by USB Mass storage activation!
After some 2+ years of constantly changing ROMs, I've noticed that my i9100 shows more often than not the message of "your storage is getting full" or whatever it says. It does not work by clearing apps' data or even removing some of them because it ends up showing the warning soon. Also, factory reset has proved not to do much, since it just does a data wipe.
So I have decided to proceed with a format by entering Recovery > Mounts & storage > Format sdcard.
I just want to check first wether I will be able, after the format has finished, to flash CyanogenMod back from the same recovery (having placed it in the external SD card, which I understand is not formatted together with the internal storage) and have it working all ok, or the format will disable me from doing something else.
So my questions are:
That 'format sdcard' option in the Recovery means the internal storage, right?
The external SD card (the actual physical one) is not affected by the format, right?
Will I be able to flash CyanogenMod back again from the same Recovery after the format?
In case yes, any reboot in between the format and the flashing would brick my phone?
Help is much appreciated! :laugh:
jago84 said:
After some 2+ years of constantly changing ROMs, I've noticed that my i9100 shows more often than not the message of "your storage is getting full" or whatever it says. It does not work by clearing apps' data or even removing some of them because it ends up showing the warning soon. Also, factory reset has proved not to do much, since it just does a data wipe.
So I have decided to proceed with a format by entering Recovery > Mounts & storage > Format sdcard.
I just want to check first wether I will be able, after the format has finished, to flash CyanogenMod back from the same recovery (having placed it in the external SD card, which I understand is not formatted together with the internal storage) and have it working all ok, or the format will disable me from doing something else.
So my questions are:
That 'format sdcard' option in the Recovery means the internal storage, right?
The external SD card (the actual physical one) is not affected by the format, right?
Will I be able to flash CyanogenMod back again from the same Recovery after the format?
In case yes, any reboot in between the format and the flashing would brick my phone?
Help is much appreciated! :laugh:
Click to expand...
Click to collapse
well as i had flashed a lot of Roms too, maybe i can help you...i'll try!
after formatting sdcard, u wont lose ROM. u will just format your sdcard(12 gb i think).
1) i think the "format sdcard" option is supposed to mean the internal storage. but in some roms that i flashed, sometimes the sdcard mean the external sdcard and EMMC means the internal sdcard...so first take a look. go to install zip and select install from internal sdcard or external sdcard and look up in the screen, if it shows that u are in /sdcard or in /emmc, so u can know what sdcard are u really going to format
2) if u select to format the internal sdcard, it will only format the internal sdcard. nothing else.
3)well, as i said in the beginning, you won't lose rom in the format...u just formated sdcard, the rom and its stuff are still there, in the device storage(not sdcard or external sdcard, but in a card that is only for system/phone stuff(its like the phone has 2 cards. one u can use and send stuff(12gb) and the other one is for system files(2gb))
4) i think it would not brick it, since u just formated the sdcard, the rom is still on your phone but in the device storage, like i said above.
the ROM files arent stored in internal sdcard or external sdcard(those u can send files by usb), they are stored in the storage of the device that is only for system files. so if u do a format it wont affect Rom or Recovery.
hope it helped a little...cheers
Short notice from my side: I doubt formatting your sdcard will help to solve your original problem (low memory). This message appears if the /data space (those 2GB where all the system settings and application data are stored) is almost used completely. The easiest way to clean up this data is a system reset (which will make you loose all your data) or you need to look whether there are applications occupying much data there and remove these apps / tell them to store their data on /sdcard (if this is possible) or to selectively remove some log files / temp data. But in this you should be very careful, because removing the wrong data might cause strange system behaviour.
Sent from my Nexus 7 using xda app-developers app
AndDiSa said:
Short notice from my side: I doubt formatting your sdcard will help to solve your original problem (low memory). This message appears if the /data space (those 2GB where all the system settings and application data are stored) is almost used completely. The easiest way to clean up this data is a system reset (which will make you loose all your data) or you need to look whether there are applications occupying much data there and remove these apps / tell them to store their data on /sdcard (if this is possible) or to selectively remove some log files / temp data. But in this you should be very careful, because removing the wrong data might cause strange system behaviour.
Click to expand...
Click to collapse
I think that is not quite the problem I am faceing now. I explain myself: when I get that "storage almost full" message, if I check on Settings > Storage, the Internal Storage section (1,97 GB in total) shows an availability of only 205 MB and the bar is half full (see attached). First incoherence. I try to update any small app such as, for example, Bitcoin Wallet (1.3 MB) and it says it can't be updated because there is not enough space. Incoherent with the bar shown. Also, if I navigate to /data, it shows there is an amount of 2.31 GB inside that directory (incoherent with the amount shown by the Storage Manager. Other data folders, such as the one in /sdcard/data or the one in /data/data, are always smaller (3 MB and 425 MB respectively, also don't match any of the figures shown by the Storage Manager).
Some ROM installs ago, I remember I was able to install around 190 apps and no problem at all, and now I'm 160 and have to keep removing apps when I want to install more.
That's why I think my problem is not related to data, or fixed by a data wipe or factory reset. I understand there are too many files inside that are just lost from ROM to ROM, and not even the system know where do they belong to. It is running everything but fluent. I don't even remember what Project Butter is :silly:
RonDelonge182 said:
well as i had flashed a lot of Roms too, maybe i can help you...i'll try!
after formatting sdcard, u wont lose ROM. u will just format your sdcard(12 gb i think).
1) i think the "format sdcard" option is supposed to mean the internal storage. but in some roms that i flashed, sometimes the sdcard mean the external sdcard and EMMC means the internal sdcard...so first take a look. go to install zip and select install from internal sdcard or external sdcard and look up in the screen, if it shows that u are in /sdcard or in /emmc, so u can know what sdcard are u really going to format
2) if u select to format the internal sdcard, it will only format the internal sdcard. nothing else.
3)well, as i said in the beginning, you won't lose rom in the format...u just formated sdcard, the rom and its stuff are still there, in the device storage(not sdcard or external sdcard, but in a card that is only for system/phone stuff(its like the phone has 2 cards. one u can use and send stuff(12gb) and the other one is for system files(2gb))
4) i think it would not brick it, since u just formated the sdcard, the rom is still on your phone but in the device storage, like i said above.
the ROM files arent stored in internal sdcard or external sdcard(those u can send files by usb), they are stored in the storage of the device that is only for system files. so if u do a format it wont affect Rom or Recovery.
hope it helped a little...cheers
Click to expand...
Click to collapse
Thanks for your help, dude! Much appreciated.
Anyway, I feel that, if formatting sdcard does not wipe everything, maybe then what I need is to go Recovery > Mounts and storage > format /system, format /data, etc. All of them except for the actual physical sdcard (wether it is /emmc or /sdcard) and the directory in which the recovery "lives".
So I have new questions now:
If I formatted /system, would the phone be bricked or the Recovery would still allow me to install a CM ROM stored in the sd card?
Is there any of the directories shown in Recovery > Mounts and Storage that represents the actual Recovery partition/space?
There's no recovery partition you can format.
You can format system, preload, and data partition.
But flash a ROM right after.
There are flashable scripts (ROM wipe or ROM nuke) you can use. It does all the formats and wipes, and even back up some of your folders.
Envoyé depuis mon Nexus 10 avec Tapatalk
jago84 said:
I think that is not quite the problem I am faceing now. I explain myself: when I get that "storage almost full" message, if I check on Settings > Storage, the Internal Storage section (1,97 GB in total) shows an availability of only 205 MB and the bar is half full (see attached).
Click to expand...
Click to collapse
It's a known bug, that Android's performance is decreasing very much as soon as there is less than 10% free on /data. Additionally I wouldn't trust the graphics you see, because especially if you have man small files, the space occupied on "disk" is much higher than the file size. If they are only adding the file size of the files stored there this will be misleading. As far as I know the block size is 4kb, so each file takes at least 4kb of the memory. You can try to move some apps to /sdcard, but this works only to an external one, so you can free some space. Otherwise have a look on /data/system/dropbox or /data/system/usagestats if you can find some files which can be removed.
jago84 said:
Thanks for your help, dude! Much appreciated.
Anyway, I feel that, if formatting sdcard does not wipe everything, maybe then what I need is to go Recovery > Mounts and storage > format /system, format /data, etc. All of them except for the actual physical sdcard (wether it is /emmc or /sdcard) and the directory in which the recovery "lives".
So I have new questions now:
If I formatted /system, would the phone be bricked or the Recovery would still allow me to install a CM ROM stored in the sd card?
Is there any of the directories shown in Recovery > Mounts and Storage that represents the actual Recovery partition/space?
Click to expand...
Click to collapse
well, as Sergeileduc said, u can't format Recovery. so answering your questions:
1) yes, you would still be able to flash any other Rom, since formatting /system does not affect recovery. Wiping this partition will remove Android from the device without rendering it unbootable, and you will still be able to put the phone into recovery or bootloader mode to install a new ROM.
2) i dont think so...u can't format recovery...
hope it helped you...cheers!
well the 4rth question is no it wouldent brick your phone it will just hang at the galaxy s logo p.s thanks for helpin me on the other fourm
Just to add my own experience.....
Some months ago, my phone was suffering from poor performance (I was running CM10.1 at the time)
I decided to do a full format to totally "pristine" wipe my phone and start fresh. I copied a fresh version of the rom and gapps to my removable micro SD card and rebooted into CWM. I formatted cache, dalvic, preload, emmc and sd.....then just to be certain, I factory reset too.....
After that and while still in CWM, I flashed the rom and gapps and rebooted without issue......I believe this is what you want to do, so to answer your question. ...yes it is safe and possible to do this.....my phone is proof of that.....
Sent from my Rooted, De bloated Stock JB powered S2 via PhilZ kernel and Tapatalk 2....
keithross39 said:
Just to add my own experience.....
Some months ago, my phone was suffering from poor performance (I was running CM10.1 at the time)
I decided to do a full format to totally "pristine" wipe my phone and start fresh. I copied a fresh version of the rom and gapps to my removable micro SD card and rebooted into CWM. I formatted cache, dalvic, preload, emmc and sd.....then just to be certain, I factory reset too.....
After that and while still in CWM, I flashed the rom and gapps and rebooted without issue......I believe this is what you want to do, so to answer your question. ...yes it is safe and possible to do this.....my phone is proof of that.....
Click to expand...
Click to collapse
Thanks! Great feedback.
Just to complete my question, did you notice a significant performance improvement after the wipe-and-reinstall process?
It seemed to help a bit, but not as much as I'd anticipated. ..
Sent from my Rooted, De bloated Stock JB powered S2 via PhilZ kernel and Tapatalk 2....
Hello all,
few days ag I asked how to move internal apps to SD with Titanium Backups. Hitesh2626 recommeded me to use another method : http://forum.xda-developers.com/showthread.php?t=2082465 and I did so.
I've followed the guide but I did not succeed and I think I konw why: when I run CWM I don't have any /sd-ext partition.
I've followed all the steps under "Partition SD Card" , and I've used ext2 for formatting the new "memory" .
Anyone has had the same problem? Anyone could help me to find what am I doing wrong?
TIA,
Arnau
pelacables79 said:
Hello all,
few days ag I asked how to move internal apps to SD with Titanium Backups. Hitesh2626 recommeded me to use another method : http://forum.xda-developers.com/showthread.php?t=2082465 and I did so.
I've followed the guide but I did not succeed and I think I konw why: when I run CWM I don't have any /sd-ext partition.
I've followed all the steps under "Partition SD Card" , and I've used ext2 for formatting the new "memory" .
Anyone has had the same problem? Anyone could help me to find what am I doing wrong?
TIA,
Arnau
Click to expand...
Click to collapse
Were you able to create the mount scripts? Can you elaborate the problem that you are facing?
mahithm said:
Were you able to create the mount scripts? Can you elaborate the problem that you are facing?
Click to expand...
Click to collapse
Hello, first of all, thanks for your answer.
I guess you are talking about step 11, just after chossing the filesystem type:
10) First , Choose ext2. If it don't work then restart Link2SD and when then don't choose ext2 but ext4. ( Don't worry , it works )
11) It will say mount script created. Reboot your phone now.
Click to expand...
Click to collapse
If so, yes, after chossing ext2 it does not complain. After reboot I see a second partition "/data/sdext2" : Total:0.89GB used 64,91MB Free: 850MB.
(is it ext2? If I plug the mobile into my linux box it says it's FAT32):
Code:
Device Boot Start End Blocks Id System
/dev/sdc1 1 13564453 6782226+ c W95 FAT32 (LBA)
/dev/sdc2 13564454 15564799 1000173 83 Linux
Teh "problem" comes when doing "Placing the 2nd partition of SD Card to internal." :
18) Foramt /data /sd-ext /system
Click to expand...
Click to collapse
I don't have that "/sd-ext" partition, so I cannot format it.
But I've continued with the manual and tried to install an app (whatsapp). Now Link2sd says that the app has been linked, the /data/sdext2 partitoin now shows 85,97MB used but when I go to apps, manage apps, I see that my mem has decreased in ~ 20 MB . Is that the expected behaivour?
This I explain myself clear? if not, sorry but I'm newb to this world
TIA,
Arnau
pelacables79 said:
Hello, first of all, thanks for your answer.
I guess you are talking about step 11, just after chossing the filesystem type:
If so, yes, after chossing ext2 it does not complain. After reboot I see a second partition "/data/sdext2" : Total:0.89GB used 64,91MB Free: 850MB.
(is it ext2? If I plug the mobile into my linux box it says it's FAT32):
Code:
Device Boot Start End Blocks Id System
/dev/sdc1 1 13564453 6782226+ c W95 FAT32 (LBA)
/dev/sdc2 13564454 15564799 1000173 83 Linux
Teh "problem" comes when doing "Placing the 2nd partition of SD Card to internal." :
I don't have that "/sd-ext" partition, so I cannot format it.
But I've continued with the manual and tried to install an app (whatsapp). Now Link2sd says that the app has been linked, the /data/sdext2 partitoin now shows 85,97MB used but when I go to apps, manage apps, I see that my mem has decreased in ~ 20 MB . Is that the expected behaivour?
This I explain myself clear? if not, sorry but I'm newb to this world
TIA,
Arnau
Click to expand...
Click to collapse
Yes, that's how Link2SD works. It will link the data associated with the app to ext partition. If you go to the Settings> Storage, you will see that the total internal memory remains the same. But you can still see the available memory has increased due to linking to ext. To see how much of the ext partition is used, just go to Link2SD> Storage. Now if you are not satisfied with Link2SD, you can try the CronMod Unofficial. First backup all the SD Card data. Also if you want to try CronMod Unofficial after installing Link2SD, it better to flash the custom rom again after formatting /system and /data from CWM. This will get rid of all Link2SD files which can otherwise mess with CronMod Official. Now go to CWM> Format /sdcard. This will delete the ext partition. Now CWM> Advanced> Partition SD Card> Size (Max 1GB, anymore and system will lag)> Swap (0MB) and wait for it to say "Partitioning done". Now download and place CronMod Unofficial to SD Card. Now again go to CWM> Mounts & Storage> Mount /system then flash the Cronmod Unofficial zip from CWM and finally unmount /system. Reboot and you are good to go. Now go to Settings>Storage to see the newly increased internal memory. Here is the link,
Cronmod Unofficial
Hope I Helped
Hi mahithm,
mahithm said:
Yes, that's how Link2SD works. It will link the data associated with the app to ext partition. If you go to the Settings> Storage, you will see that the total internal memory remains the same. But you can still see the available memory has increased due to linking to ext. To see how much of the ext partition is used, just go to Link2SD> Storage.
Click to expand...
Click to collapse
ops... I expected more space for installing apps, not just for data. Ok, I can install more apps than before, but not all the ones I want.
Now if you are not satisfied with Link2SD, you can try the CronMod Unofficial. First backup all the SD Card data. Also if you want to try CronMod Unofficial after installing Link2SD, it better to flash the custom rom again after formatting /system and /data from CWM. This will get rid of all Link2SD files which can otherwise mess with CronMod Official. Now go to CWM> Format /sdcard. This will delete the ext partition. Now CWM> Advanced> Partition SD Card> Size (Max 1GB, anymore and system will lag)> Swap (0MB) and wait for it to say "Partitioning done". Now download and place CronMod Unofficial to SD Card. Now again go to CWM> Mounts & Storage> Mount /system then flash the Cronmod Unofficial zip from CWM and finally unmount /system. Reboot and you are good to go. Now go to Settings>Storage to see the newly increased internal memory. Here is the link,
Cronmod Unofficial
Click to expand...
Click to collapse
A couple of questions:
1.-) So, with this method I'll be able to install all the app in SD?
2.-) 7-Flash your desired script : what does it refer to?
3.-) It also refer to sd-ext, but I can't format that partition... (as it was my original problem). is cronmod going to use it even if I don't format it? (as link2sd has done).
Hope I Helped
Click to expand...
Click to collapse
Yes!! Thanks a lot!
Arnau
pelacables79 said:
Hi mahithm,
ops... I expected more space for installing apps, not just for data. Ok, I can install more apps than before, but not all the ones I want.
A couple of questions:
1.-) So, with this method I'll be able to install all the app in SD?
2.-) 7-Flash your desired script : what does it refer to?
3.-) It also refer to sd-ext, but I can't format that partition... (as it was my original problem). is cronmod going to use it even if I don't format it? (as link2sd has done).
Yes!! Thanks a lot!
Arnau
Click to expand...
Click to collapse
1. Yes with this method you'll be able to install all apps to the ext partition of the SD Card as long as you have free space on ext partition
2. Flashing the desired script refers to flashing the script in question, i.e., CronMod Unofficial
3. Can you tell me what happens when you try Mounts & Storage> Format /sd-ext? CronMod uses you ext partition even if you don't format it. Its not compulsory and CronMod should work fine.
Sorry for the late reply. If you have anymore doubt, post here. I'll be glad to help
mahithm said:
1. Yes with this method you'll be able to install all apps to the ext partition of the SD Card as long as you have free space on ext partition
Click to expand...
Click to collapse
Great. But since yesterday I've been experience speed "problems". I'm wondering if makes snes to gain space but lose speed... Maybe I try and decide with this new method. (Maybe the ROM also affects? ace-i-sure 8 to 12 could cause such speed issues?)
2. Flashing the desired script refers to flashing the script in question, i.e., CronMod Unofficial
Click to expand...
Click to collapse
Why just say so thanks!
3. Can you tell me what happens when you try Mounts & Storage> Format /sd-ext? CronMod uses you ext partition even if you don't format it. Its not compulsory and CronMod should work fine.
Click to expand...
Click to collapse
I'll let you know after trying it, it will take a couple of days
Sorry for the late reply. If you have anymore doubt, post here. I'll be glad to help
Click to expand...
Click to collapse
You don't have to apologise!! Many thanks for your detailed answers and for your time!!
Cheers,
Arnau
Hi,
after a couple of days I've seen that the speed problems do not compensate teh fact of having more apps installed, so I'm not going to try this new approach.
I've re-flashed the rom without using externad SD and it's running really fine.
Many thanks for your help dude!
Cheers,
Arnau
pelacables79 said:
Hi,
after a couple of days I've seen that the speed problems do not compensate teh fact of having more apps installed, so I'm not going to try this new approach.
I've re-flashed the rom without using externad SD and it's running really fine.
Many thanks for your help dude!
Cheers,
Arnau
Click to expand...
Click to collapse
Glad I could help And yes irrespective of what method you choose to increase the internal memory, there will always be a lag after you exceed a certain number of app install. This is because in all cases the /data is moved to ext partition of the SD Card. SD Card R/W speed is always lesser than internal memory R/W speed. You can control this lag to a certain extend by using class 8 or higher SD Card and only installing necessary apps.
This is a framework to help "boot" Android from the external SD card.
[size=+3]Motivation:[/size]
I started this because I would like to have Xposed Framework installed in my STS, but I do not want to take ANY risks of bootloop modifying internal system partition. This way I made this framework to allow me to "boot" a copy of Android resident in the external SD card, so that in case of bootloop, I simple eject the SD card and boot from internal Android.
[size=+3]News:[/size]
{new} - 2014/07/29 - New Sys2sdManager V2, supporting ROM ramdisks (custom ROMs), and some bugfixes. Please install, "unhook" and then "hook" again the sys2sd framework for the changes to take effect. There is a new recovery too, so choose the menu option to install the recovery package.
{new} - 2014/07/29 - First CM9 ROM for the STS (alpha stage). Please read the #2 topic for details.
{new} - 2014/07/28 - I am working on a port of CM9 for the Sony Tablet S using the sys2sd framework.
[size=+3]How it works[/size]
First, you must partition your external SD card, and then clone system and data from internal to external sdcard.
Next, during the normal boot process, the framework intercepts the process, test for the existence of the previously prepared external SD card, and if found it pauses the internal boot process, mounts /data and /system partition from the SD card, and then resumes the boot process.
[size=+3]Features[/size]
- Boot Android from external SD card (mount SYSTEM and DATA from external SD card).
- Functional recovery framework, using adapted TWRP from Motorola Xoom tablet.
- The recovery package can reside in internal or external storage.
- Recovery wait time with LED notification and triggering via hardware keypress.
- Can boot other versions of Android compatible with the stock STS ramdisk (custom ROMs).
- (work in progress): can boot other versions of Android with alternative ramdisk.
[size=+3]Bootloop Safety[/size]
- Only hook into 1 internal system script: /system/etc/install-recovery.sh (or install-recovery2.sh if present)
- With no external SD card present, the internal boot process takes precedence unmodified.
- /data and /system residing in external SD card, so if one mess the external /data ou /system directory, the bootloop will be limited to booting from the external sdcard.
- Working recovery: you can apply zip or backup and restore (tested!) your external SD card data and system partion. All modifications in data and system will be limited to the external SD card.
[size=+3]Limitations[/size]
- All modifications must work with the stock STS kernel. No custom kernels until kexec or unlocked bootloader.
- Write speed of the SD card.
[size=+3]Requisites[/size]
- Rooted Android 4.0.3 Sony Tablet S.
- busybox installed in /system/xbin, containing the functions: mount, tar, gzip, awk, sed. I recommend Stericson Busybox Installer on the Play Store. {new} If you do not have buysybox, the installer will install one for you.
- External SD card of size 8Gb or more, SD or Microsd. See the Drawbacks section for speed class information.
- Partitioning software to partition the external SD card. I recommend Mini Tool Partition Wizard for Windows, or GParted for Linux.
[size=+3]Drawbacks[/size]
[size=+2]Speed[/size]
Because the STS will be running Android from the external SD card (system and data), this framework heavly depends on the SD card read and write speed for disk IO.
I have tested the framework with the following SD card classes:
App loading, closing, and file IO:
Microsd class 4: damn slow browsing
Microsd class 6: slow
Microsd class 10: fast, like internal storage
Gaming:
Microsd class 4: slow loading times, gaming normal
Microsd class 6: slow loading times, gaming normal
Microsd class 10: normal
Boot process:
+20 to 40 seconds delay
[size=+3]How it works - Technical details[/size]
[size=+1]The framework executes the following steps during the boot from sd process[/size]
- Intercepts the internal Android boot process via the /system/etc/install_recovery script, then looks for the special partitioned external sdcard, and if not found resumes the normal Android boot process. Otherwise, keep executing.
- Stops the normal Android boot process, stopping all init services.
- Try to soft boot into recovery (explained bellow) if got user keypress. If the recovery process was not started, the framework resumes execution.
- Umount /data and /system from the internal flash storage.
- Mount /data and /system from the external SD card partitions.
- Restart all services and resume boot
[size=+1]The framework executes the following steps during the recovery start process[/size]
- Searches for a recovery package (recovery.tgz), in the external and internal storage system partition. If not found, cancels the recovery start process.
- If recovery package found, blinks the notification LED (blue color) and waits for user keypress to enter recovery. The recovery can also be triggered by a special recovery file present in the /cache/recovey directory (boot, command or extendedcommand files).
- If the user press some key in the wait interval or any special file are found then the recovery process continues. Otherwise, cancels the process.
- Stop all init services
- Decompress the recovery package, like a recovery ramdisk
- Umount all file systems, including internal and external storage, DM and Vold volumes.
- Soft boot the recovery Ramdisk using CHROOT busybox command
- Note: if you want to build your own alternative recovery package, special care must be taken for the /system and /data partitions in the /etc/recovery.fstab recovery file.
[size=+1]External SD card partitioning[/size]
- I recommend that the partitions in the external SD card be aligned to 4MB boundaries (8192 blocks).
- The internal /data and /system can be mirrored manualy using the following commands:
Code:
#### mount external /system in /mnt/newsys
#### mount external /data in /mnt/newdat
busybox mount -o remount,rw /
busybox mkdir -p /mnt/newsys
busybox mkdir -p /mnt/newdat
busybox mount /dev/block/mmcblk1p2 /mnt/newsys
busybox mount /dev/block/mmcblk1p3 /mnt/newdat
#### copy files
cd /system ; busybox cp -a * /mnt/newsys
cd /data ; busybox cp -a * /mnt/newdat
busybox umount /mnt/newsys
busybox umount /mnt/newdat
[size=+3]Getting started[/size]
1) Get an external SD Card and partition/format it
2) Install sys2sd into STS
3) Clone internal data and system to external SD card
4) Boot STS with external SD card inserted
5) Identify the internal and external system (important)
6) Install recovery in external SD card
[size=+1]1) Get an external SD Card and partition/format it[/size]
You must parition your external SD card before using this framework. I recommend you to use "Mini Tool Partition Wizard" for Windows, or "GParted" for Linux. I like to use fdisk for Linux, too.
I recommend that the partitions in the external SD card be aligned to 4MB boundaries (8192 blocks) for maximal write speed.
All partitions must be primary partitions. You must create 3 partitions:
- 1: Type fat32/vfat. This will be your "external sdcard" by the point of view of the Android or Recovery. The "internal sdcard" will stay the same, at the internal flash storage.
- 2: Type ext4 (without journal if you have the option). This will be your "/system" partition (system apps and Android core). For your information, the internal system for 4.0.3 Sony firmware takes about 300Mb, so this must be somewhat bigger, like 400Mb or more. I use 1Gb, in preparation for custom ROMs.
- 3: Type ext4 (without journal if possible). This will be your "/data" partition (user apps and data). Mine is 4Gb larger.
Do not forget to format the partitions after partitioning. Do not forget to save modifications in the Partitioning software (press the apply button).
Performance tips:
- If your Partitioning software has the option, use partitions starting/aligned in 4Mb boundaries (multiple of 8192 blocks), for maximal write speeds. In the Mini Tool Wizard, use MB alignment.
Code:
Disk /dev/block/mmcblk1: 15.9 GB, 15931539456 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk1p1 8192 2105344 1048576+ 83 Linux
/dev/block/mmcblk1p2 2113536 10510336 4198400+ 83 Linux
/dev/block/mmcblk1p3 10518528 12615680 1048576+ 83 Linux
- Avoid to use ext2, because it was so damn slow in my tests.
- If your Partitioning software has the option, disable ext4 journaling, because it makes the external SD card wears fast.
- If possible, mark the ext4 partitions with stripe-write=1024 blocks and stride=256 blocks.
In linux, you can use:
Code:
mkfs.ext4 -E stride=256,stripe-width=1024 -O ^has_journal /dev/mmcblk0p2
[size=+1]2) Install sys2sd into STS[/size]
Get the Sys2sd Manager, decompress it in a folder, put the partitioned SD Card in the tablet, and then run run_windows.bat (run_linux.sh is work in progress).
In the menu, choose:
- Install / Install Sys2sd and busybox
- Install / Unhook sys2sd (if previusly hooked)
- Install / Hook sys2sd into System
[size=+1]3) Clone internal data and system to external SD card[/size]
With the partioned SD Card inserted into the Tablet, enter the Sys2sd Manager, and choose:
- Clone / Clone System and Data
[size=+1]4) Boot STS with external SD card inserted[/size]
In the Sys2sd Manager, choose:
- Advanced / Reboot device
[size=+1]5) Identify the internal and external system[/size]
- If you successfuly cloned the internal Android to external SD card, it will be hard to guess if you are running the internal or external Android, because it will apear the same.
- The best way to avoid this is to change something (wallpaper, icons disposition, etc) to help identify internal and external SD card boot
- Boot into internal Android and take note of the changes (icons, wallpaper)
- Boot into external Android and compare the changes
- Take care to uniquely identify booth systems, to help prevent unwanted changes to the internal system
[size=+1]6) Install recovery in external SD card[/size]
Boot into the external Android, and in the Sys2sd Manager, choose:
- Recovery / Install Recovery
[size=+3]FAQ - Frequently Asked Questions[/size]
(Q) What is this?
(A) This is a framework to help soft boot Android from the external SD card on the Sony Tablet S (STS)?
(Q) What is soft boot?
(A) It means that it is a hook in the booting process of the internal Android, using the same Kernel e RAMDRIVE. It is not a "boot from the SD card" like supported on some devices.
(Q) How to unninstall?
(A) Remove /system/xbin/sys2sd file.
(Q) Can I boot a custom Kernel?
(A) No, until we have kexec, unlocked bootloader, or other way of executing/flashing a custom kernel.
(Q) Can I boot a custom ROM?
(A) Yes, but the ROM must be made compatible to the STS hardware, and use the stock Kernel. Simply flash the ROM into the external SD card system partition using recovery.
(Q) How secure is the Recovery module?
(A) Totaly secure. It is bounded to the external data and system partitions presents in the external SD card, so it is impossible to make changes to the internal data and system partitions. The cache, primary SD card and secondary SD card partitions will be shared between the Android versions.
(Q) How about the "Android SD card"?
(A) The "Android SD card" (do not confuse this with the internal or external storage), also know as /sdcard directory, will be the same for the internal and SD card Android versions. You can keep your books, music, videos and other data here, like you do now. Also you can place your Recovery backups here.
(Q) How about the "Android second SD card"?
(A) The "Android second SD card" will be stored on the first partition of the external SD card, and it will be visible to booth internal and SD card Android versions, depending of the Apps support for a secondary SD card. You can place your Recovery backups here also.
(Q) On Android, will apps transfered to SD card work?
(A) Probably not, because you will have two Android versions running on the same device using a shared "Android SD card". Keep the apps installed on the data partition of each Android version.
(Q) How about the Sony extra partitions?
(A) All the /configs, /dataapp, /vendor and other Sony partitions are necessary to boot the Internal stock Android. DO NOT wipe, format, clean, exclude none of the internal partitions, on the risk of a bootloop and device brick.
(Q) Can I copy the contents of the data and system in the external SD card back to the internal storage?
(A) No. It is too risk.
(Q) The Android running from the SD card is too slow.
(A) Take a faster, or class 10 SD card. Mine is running fine.
(Q) Your recovery sucks. Can I create an alternative recovery?
(A) Take my Recovery as a template.
(Q) Can I start recovery from the command line?
(A)
Code:
sys2sd recoveryctl start /path/to/recovery.tgz
(Q) Can I make a dual recovery?
(A) Yes.
Code:
File: /system/recovery/start_recovery
-----
#!/system/bin/sh
# $1 can be: vol_down, vol_up, power, internal
if [ "$1" = "vol_down" ] ; then
/system/xbin/sys2sd recoveryctl start /system/recovery/twrp.tgz
exit $?
fi
if [ "$1" = "vol_up" ] ; then
/system/xbin/sys2sd recoveryctl start /system/recovery/cwm.tgz
exit $?
fi
/system/xbin/sys2sd recoveryctl start /system/recovery/default.tgz
exit $?
(Q) How to enter Recovery?
(A) See the next question.
(Q) What is the blinking blue LED during boot?
(A) It is the notification to enter Recovery. During the blue LED blinking, press a key (volume or power) to enter Recovery - after this, the LED will pulse green to indicate it will enter Recovery, or pulse red to indicate it will NOT enter Recovery.
(Q) The clone command fails with a message of "target device not found"?
(A) Is the SD Card inserted into the tablet, partitioned and formated? Are the partitions primary partitions? Have you pressed the apply button on the partitioning software?
[size=+3]TODO[/size]
- run_linux.sh in the Sys2sd Manager
- Guide on how to make custom recovery module
- Guide on how to make custom ROM ramdisk and entry points
- (done) Guide on how to make a dual recovery
[size=+3]Introduction[/size]
This is an Unofficial CyanogenMod 9.0 port for the Sony Tablet S.
[size=+3]Working[/size]
- Display (hw accelerated)
- Touch screen
- Lock screen
- Power button
- Adjustable display brightness
- Settings App (some parts are not working)
- ADB
[size=+3]Not working[/size]
- Front camera
- Rear camera
- Volume buttons
- Audio
- GPS
- Sensors
- Wifi
- Internal SD Card
- External SD Card
- USB mtp / storage
- USB host
[size=+3]How to install[/size]
1) Install the latest sys2sd framework and get it working on an SD Card
2) Install the recovery on sys2sd
3) Download the latest flashable zip on this thread and put it on the Internal or External SD Card on the Sony Tablet S
4) Reboot into recovery (sys2sd Recovery, NOT Stock recovery)
5) {optional} Make a backup of system and data
6) Flash the downloaded zip
7) Wipe data
8) Reboot system
Please note that the changes will be limited to the Android present on the external SD Card. No changes will be made to the internal Android. Reboot and eject the SD Card to boot into internal Android.
[size=+3]Downloads[/size]
This is the flashable zip for the CM9 version:
{latest} cm9-20140729T212846.zip, 144MB
http://www.mediafire.com/download/9wha2vgie4cbqro/cm9-20140729T212846.zip
[size=+3]Warnings[/size]
DO NOT flash any of this zip using the Stock Recovery, on the risk of a device brick.
Use always the sys2sd recovery (press a key during the flashing blue LED).
RESERVED for future use 2
RESERVED for future use 3
RESERVED for future use 4
What does a blue flashing light mean?
I'm not sure but in apps it means Facebook notifications
KnightOdin said:
I'm not sure but in apps it means Facebook notifications
Click to expand...
Click to collapse
No its not even booted yet. the boot animation gets stuck, then this blue light apears
Jure220 said:
What does a blue flashing light mean?
Click to expand...
Click to collapse
The flashing blue light is the notification to press a key to enter Recovery.
Anyway, I am actually working on a port of CyanogenMod 9 using this framework.
Bazoocaze said:
Anyway, I am actually working on a port of CyanogenMod 9 using this framework.
Click to expand...
Click to collapse
Tell me if you need any help, I would be glad to help you I think we have the same goal we follow.
Edit: Check the PM
Sent from my Xperia Z2 using Tapatalk
Wow :good: This is great! Thank you so much
It really is slow with a class 4 sd card??
limax182 said:
...
Click to expand...
Click to collapse
Hi,
I am glad you are trying to use the framework.
1) "without journal" is only available if you format ext4 using the command line mkfs.ext4 on a Linux system. I am working on a way to format from the Sys2sdManager, so do not worry about this option for now.
2) Same problem. For now, choose to align to MB in the Mini Tool Parition Wizard and you will be ok.
Clone System:
Sorry for the incomplete instructions. The clone option expects the SD card to be inserted into the tablet sdcard slot.
ERROR: Target device /dev/block/mmcblk1p2 not found
Click to expand...
Click to collapse
- Is the SD Card inserted into the tablet?
- Is the SD Card really partitioned? Have you pressed the "apply" button in Mini Tool Partition Wizard?
Bazoocaze said:
Hi,
I am glad you are trying to use the framework....
Click to expand...
Click to collapse
Finally installed the external Android. The problem was I made all the 3 partitions as Logical but today I made them Primary and it worked!
Now when I tried to install Xposed it gives me this message:
View attachment 2874253
Thanks for your help!
Sorry for bad english
Oh, my. I completely forgot to say that the partitions need to be primary. I will update the first post. Thank you.
About the fault in the Xposed installer, that is a know issue in the Xposed FAQ.
This post have the workaround for that:
http://forum.xda-developers.com/showpost.php?p=52292102&postcount=7
limax182 said:
Finally installed the external Android. The problem was I made all the 3 partitions as Logical but today I made them Primary and it worked!
Now when I tried to install Xposed it gives me this message:
View attachment 2874253
Thanks for your help!
Sorry for bad english
Click to expand...
Click to collapse
Bazoocaze said:
Oh, my. I completely forgot to say that the partitions need to be primary. I will update the first post. Thank you.
About the fault in the Xposed installer, that is a know issue in the Xposed FAQ.
This post have the workaround for that:
http://forum.xda-developers.com/showpost.php?p=52292102&postcount=7
Click to expand...
Click to collapse
Totally awesome work, working on kexec to support your work.
Sent from my Sony Tablet S using Tapatalk
smgdev said:
Totally awesome work, working on kexec to support your work.
Sent from my Sony Tablet S using Tapatalk
Click to expand...
Click to collapse
Wow, man! Nice to know that.
Do you think it will soon be possible to put CM9 on the internal storage after getting kexec worked on with a few fixes? This is just way too awesome to handle and we're finally going somewhere.
Funny enough, this isn't in the development thread.
I've tried this framework but I seem to be getting issues.
I've got around some errors regarding mounting but it seems that the recovery can touch the /cache partition causing it to have the wrong permissions or something, I had to factory reset to get the /cache partition to be reformatted.
Anyway, after all of the things after and before, I've finally got this thing working, the only problem now is that the ROM is stuck in a bootloop or something (staying in the boot animation, I think it did dim slightly after 10-20 minutes).
I'm using an 8GB class 4 SD card.
@Bazoocaze let me know if anything has to be done. And also let me know if you have knowledge about kernels, I am already working on kexec.
Sent from my Sony Tablet S using Tapatalk