Related
I have been a big fan of VEGAn Ginger -- sure it has some issues but it works pretty well. But recently I was wondering how much of an issue would it be to install CM7.02, the VTL Launcher, and whatever other extras and just keep up to date.
I did and for the most part it works the same. A few things were FC that didn't on VEGAn and a few things worked that FC on VEGAn. No big difference on too many things.
However, two issues came up.
1) CM really wanted to install ROM Manager. The CM forum implied it works ok so I tried it. It DOES work on my system but it expects everything on /mnt/emmc which was a pain since all my backups and recovery were on the external sdcard /mnt/sdcard2 in VEGAn and /mnt/sdcard in CM7. What's worse is apparently it will refuse to flash over it self with an old version! So it wasn't insurmountable, just required me to move everything for awhile. But I finally got tired of it and reflashed good old bekit 0.8 using nvflash. So if you experiment, be sure you have a backup of partition 9 (clockwork mod) or you know how to unpack the ZIP file and flash it.
2) This brings up an interesting issue. I was going to try it but I didn't because I realized I'd have to repack the root directory and I didn't want to do it. But if the Gingerbread ROM repackagers were interested this would be easy for them to do. I'd propose having 3 directories in /mnt (well, plus the others, but 3 we are interested in): /mnt/emmc /mnt/sdcard /mnt/sdcard2
What you would do is let CM7 mount /mnt/emmc as always and change vold.conf to mount the external card at /mnt/sdcard2. Then you bind mount /mnt/emmc over /mnt/sdcard. That way you have the exact same filesystem at /mnt/emmc and /mnt/sdcard and in CM7 and the other ROMs it would "just work" since regardless of where you were looking for the SDCARD you'd wind up with the internal unless you looked for sdcard2.
I understand not all devices have big internal SD and that's why CM is set up the way it is, but if we are mucking with the mount scheme anyway, why not like this?
I may go in and try it again if I reinstall CM7. Without having to recast the ROM you'd have to put a userinit script in that DID not block but would spin off a process to wait for /dev/emmc to mount and then moved /mnt/sdcard to /mnt/sdcard2 and then created /mnt/sdcard again and did the bind mount. This requires a remount of root to make it writeable, etc. Kind of a pain.
Something like this (untested):
#!/system/bin/sh
( until mount | grep -l sdcard
do
mount -o remount,rw / /
mv /mnt/sdcard /mnt/sdcard2
mkdir /mnt/sdcard
chown 1000 /mnt/sdcard
chgrp 1015 /mnt/sdcard # whatever sdcard_r gid is? 1015? 1025?
chmod 076 /mnt/sdcard
mount -o bind /mnt/emmc /mnt/sdcard
mount -o remount,ro / /
done ) &
Something like that. Would be easier if you could just get vold to mount on sdcard2 to start with and have /mnt/sdcard and /mnt/sdcard2 already created in /mnt.
Just a thought.
By the way, another trick like this that I do is to mount sdcard2 as a subdirectory of sdcard. That works great EXCEPT when you USB mount the tablet it never works until you unmount. Not a big deal but a pain.
Good suggestion, but it's easier to just symlink /mnt/sdcard to /mnt/emmc and mount the internal SD card there--assuming that vold does not check that the mount point is not a symbolic link. The external SD card can be mounted on /mnt/sdcard2.
However, this might be a temporary problem. Google, for Gingerbread, wants the removable SD card on all devices, whether cell phone or tablet, to always be mounted on /mnt/sdcard (or /sdcard) and the internal SD card to be mounted elsewhere (/mnt/emmc, I believe), which is why Gingerbread-based firmwares like CM7 have /mnt/emmc and /mnt/sdcard as mount points.
In 6 months, hopefully, everybody will be on Gingerbread+ and the current multiplicity of possible mount locations will cease to be an irritation.
you have emmc and sdcard mountable right now. you can also mount a usbdisk. you can have 2 mounts going at the same time currently.
Screenshots? Last I checked (7.0.2) you still could not take a SS by any method on CM7.
That's pretty much why I'm on VEGANginger.
I used the vold.fstab.zip thing floating around here or on the CM forums to change the fstab on CM7 to be like VEGANtab/froyo for mounting the internal sdcard - makes all the 3rd party apps happy.
schettj said:
Screenshots? Last I checked (7.0.2) you still could not take a SS by any method on CM7.
That's pretty much why I'm on VEGANginger.
I used the vold.fstab.zip thing floating around here or on the CM forums to change the fstab on CM7 to be like VEGANtab/froyo for mounting the internal sdcard - makes all the 3rd party apps happy.
Click to expand...
Click to collapse
Same thing here, it makes almost everything back to normal, unless you try to use ROM Manager automagically, which will fail.
rajeevvp said:
Good suggestion, but it's easier to just symlink /mnt/sdcard to /mnt/emmc and mount the internal SD card there--assuming that vold does not check that the mount point is not a symbolic link. The external SD card can be mounted on /mnt/sdcard2.
However, this might be a temporary problem. Google, for Gingerbread, wants the removable SD card on all devices, whether cell phone or tablet, to always be mounted on /mnt/sdcard (or /sdcard) and the internal SD card to be mounted elsewhere (/mnt/emmc, I believe), which is why Gingerbread-based firmwares like CM7 have /mnt/emmc and /mnt/sdcard as mount points.
In 6 months, hopefully, everybody will be on Gingerbread+ and the current multiplicity of possible mount locations will cease to be an irritation.
Click to expand...
Click to collapse
Symlinks don't work for everything -- especially any FS that is VFAT. Bind mounts always work even through a chroot, etc. I don't think you can mount on top of a symlink either although I could be wrong. Same problem with trying to symlink /mnt/sdcard/sdcard2 => /mnt/sdcard2. The sdcard FS is VFAT so...
schettj said:
Screenshots? Last I checked (7.0.2) you still could not take a SS by any method on CM7.
That's pretty much why I'm on VEGANginger.
I used the vold.fstab.zip thing floating around here or on the CM forums to change the fstab on CM7 to be like VEGANtab/froyo for mounting the internal sdcard - makes all the 3rd party apps happy.
Click to expand...
Click to collapse
screen shots are in cm7 now.
wd5gnr said:
Symlinks don't work for everything -- especially any FS that is VFAT. Bind mounts always work even through a chroot, etc. I don't think you can mount on top of a symlink either although I could be wrong. Same problem with trying to symlink /mnt/sdcard/sdcard2 => /mnt/sdcard2. The sdcard FS is VFAT so...
Click to expand...
Click to collapse
No, symlinks will work in this case because the link in not on the VFAT filesystem--it's outside it. And, you can mount through a symlink.
pershoot said:
screen shots are in cm7 now.
Click to expand...
Click to collapse
Hm... they didn't work in 7.0.2 when I flashed it. So they're in the nightly since? I could flash over and kick the tires.
I just got my first Android Device (Moto E) and tried to get around the small internal memory by using the sdcard instead of the internal memory for /data. As the KitKat mounting procedure does not seem to be based on vold.fstab anymore, the usual guides to doing that don't apply.
So my idea was to format the sdcard with ext4 and modify the /fstab.qcom file to mount the sdcard as /data instead of the internal data partition. But here's where I don't know how to proceed, as adb shell don't seem to have access to the proper partition during flashboot (though having mounted the rootfs parition which should contain those files?) and is unable to write to the file once the system is running.
I'd appreciate if anyone can point me in the right direction on how to do that.
lunaticat said:
I just got my first Android Device (Moto E) and tried to get around the small internal memory by using the sdcard instead of the internal memory for /data. As the KitKat mounting procedure does not seem to be based on vold.fstab anymore, the usual guides to doing that don't apply.
So my idea was to format the sdcard with ext4 and modify the /fstab.qcom file to mount the sdcard as /data instead of the internal data partition. But here's where I don't know how to proceed, as adb shell don't seem to have access to the proper partition during flashboot (though having mounted the rootfs parition which should contain those files?) and is unable to write to the file once the system is running.
I'd appreciate if anyone can point me in the right direction on how to do that.
Click to expand...
Click to collapse
A little late in the game (I am trying to do the same), but I come across this:
http://forum.xda-developers.com/showthread.php?t=443994
boot partition populates the rootfs. So hack the boot.img (unpack to analyze), and you may find your answer. Hope this helps.
I will give it a shot in the next week.
I have a Galaxy GIO, which is a fairly old low-end phone. On factory reset, I have about 100MB memory free for apps, and the phone seems to start complaining as soon as I hit the 50MB mark; that's about one or 2 installed applications.
Because I would like to actually be able to, well, use my phone for anything else than calling, I want to move the /data partition to my SD card. I know this'll be slow, but slow still is better than not working at all.
I have done a bit of research, and came around plenty of scripts which claim to mount the second partition of the sd card as /data; none of these scripts work. I have tried 'INT2EXT', 'D2EXT', and I've heard about something called 'A2SD' but I have yet to find a copy of it . To install these scripts I've extracted them, and copied the scripts to '/system/etc/init.d/', after mounting '/system', using ADB.
I for an instant thought maybe my second partition isn't formatted properly, but using adb I am able to successfully mount the ext2 partition as /sd-ext, so I don't see why mounting them as /data should be a problem.
I have also tried to symbollicly link /data to /sd-ext/data and automatically mount my /sd-ext on boot. Obviously this didn't work, because the symbolic link isn't actually saved to disk.
How would I go about moving my data partition to my sd card? I am not affraid of doing some dirty work manually. I am running Cyanogenmod 11.
Binero said:
I have a Galaxy GIO, which is a fairly old low-end phone. On factory reset, I have about 100MB memory free for apps, and the phone seems to start complaining as soon as I hit the 50MB mark; that's about one or 2 installed applications.
Because I would like to actually be able to, well, use my phone for anything else than calling, I want to move the /data partition to my SD card. I know this'll be slow, but slow still is better than not working at all.
I have done a bit of research, and came around plenty of scripts which claim to mount the second partition of the sd card as /data; none of these scripts work. I have tried 'INT2EXT', 'D2EXT', and I've heard about something called 'A2SD' but I have yet to find a copy of it . To install these scripts I've extracted them, and copied the scripts to '/system/etc/init.d/', after mounting '/system', using ADB.
I for an instant thought maybe my second partition isn't formatted properly, but using adb I am able to successfully mount the ext2 partition as /sd-ext, so I don't see why mounting them as /data should be a problem.
I have also tried to symbollicly link /data to /sd-ext/data and automatically mount my /sd-ext on boot. Obviously this didn't work, because the symbolic link isn't actually saved to disk.
How would I go about moving my data partition to my sd card? I am not affraid of doing some dirty work manually. I am running Cyanogenmod 11.
Click to expand...
Click to collapse
I will introduce how to COPY(NOT MOVING) /data partition to /sdcard.
1. You should ROOT First.
2. Use Rootexplorer to Copy /data to /sdcard (WARNING:If your sdcard emulated with /data, Data WON'T copy to SDCARD --You need external Sdcard!)
2-1. if you don't want to use RootExplorer, you can use Android Debugging Bridge(adb)
(Youshould download Android sdks from developer.android.com)
--Command : adb shell su -C cp /data /sdcard/data
3. That's all.
Jason Hyunwoo said:
I will introduce how to COPY(NOT MOVING) /data partition to /sdcard.
1. You should ROOT First.
2. Use Rootexplorer to Copy /data to /sdcard (WARNING:If your sdcard emulated with /data, Data WON'T copy to SDCARD --You need external Sdcard!)
2-1. if you don't want to use RootExplorer, you can use Android Debugging Bridge(adb)
(Youshould download Android sdks from developer.android.com)
--Command : adb shell su -C cp /data /sdcard/data
3. That's all.
Click to expand...
Click to collapse
Thanks, but that's not entirely what I meant. I can manage to move my data to the SD card no problem, but I want my phone to actually use my second partition on my sd card, as the /data partition.
Binero said:
Thanks, but that's not entirely what I meant. I can manage to move my data to the SD card no problem, but I want my phone to actually use my second partition on my sd card, as the /data partition.
Click to expand...
Click to collapse
Oops.. Sorry about that!
First, I am not sure that will work or not, maybe you should try to edit init.*.rc. Which is from boot.mg. I think, maybe mounting sdcard as data is impossible, but you may try editing init.rc(or init.*.rc, * is manufacture). You could unpack your boot img, and you could edit mounting point which is from init.rc!
I hope this thing will help you..
Jason Hyunwoo said:
Oops.. Sorry about that!
First, I am not sure that will work or not, maybe you should try to edit init.*.rc. Which is from boot.mg. I think, maybe mounting sdcard as data is impossible, but you may try editing init.rc(or init.*.rc, * is manufacture). You could unpack your boot img, and you could edit mounting point which is from init.rc!
I hope this thing will help you..
Click to expand...
Click to collapse
I have looked into init.rc, but that only seemed to create the /data mountpoint, but not actually mount to it. I've no idea how to edit the boot image, or what that even is. Is that the filesystem that is built into the kernel?
Binero said:
I have looked into init.rc, but that only seemed to create the /data mountpoint, but not actually mount to it. I've no idea how to edit the boot image, or what that even is. Is that the filesystem that is built into the kernel?
Click to expand...
Click to collapse
Umm.. You should download unpackbootimg or dsixda's Android Kitchen to edit boot.mg. You cannot edit init.rc on Root explore. Use unpack boot.img menu which is from Android Kitchen!
Jason Hyunwoo said:
Umm.. You should download unpackbootimg or dsixda's Android Kitchen to edit boot.mg. You cannot edit init.rc on Root explore. Use unpack boot.img menu which is from Android Kitchen!
Click to expand...
Click to collapse
I'll try that out. Still not sure where to look though. As I said, init.rc does not contain any commands mounting /data.
Binero said:
I'll try that out. Still not sure where to look though. As I said, init.rc does not contain any commands mounting /data.
Click to expand...
Click to collapse
or you could edit look at other *.rc files!
Isn't this what you're looking for?
http://forum.xda-developers.com/galaxy-s2/themes-apps/tool-directorybind-data-to-externalsd-t1410262
sndsnd said:
Isn't this what you're looking for?
http://forum.xda-developers.com/galaxy-s2/themes-apps/tool-directorybind-data-to-externalsd-t1410262
Click to expand...
Click to collapse
I want to mount my sd card to my /data. That simply creates a symbolic link.
Jason Hyunwoo said:
or you could edit look at other *.rc files!
Click to expand...
Click to collapse
There is only 2 rc files, and one of them is specific to my recovery image.
Hi,
I have managed to root my E3 Dual D2212, upgraded to KK 4.4.4, installed BusyBox, Universal init.d and everything works fine. Now I am attempting to expand internal storage on external SD card, but so far I could no manage to mount /sd-ext at boot.
I am able to remount / as rw, manually mkdir /sd-ext, mannually mount /dev/block/mmcblk1p2 there, but no way to make it happen on boot. Nandroid Backup Manager says my device is S-ON, but I had to unlock bootloader to root, so this makes no sense.
I have tried all init.d scripts I have found, all apps from PlayStore (I am looking to Mounts2SD, but anything would do!) but none really helped me.
Has anybody managed to use adittional sd-card partitions to expand internal memory? Any hint?
mmerlone said:
Hi,
I have managed to root my E3 Dual D2212, upgraded to KK 4.4.4, installed BusyBox, Universal init.d and everything works fine. Now I am attempting to expand internal storage on external SD card, but so far I could no manage to mount /sd-ext at boot.
I am able to remount / as rw, manually mkdir /sd-ext, mannually mount /dev/block/mmcblk1p2 there, but no way to make it happen on boot. Nandroid Backup Manager says my device is S-ON, but I had to unlock bootloader to root, so this makes no sense.
I have tried all init.d scripts I have found, all apps from PlayStore (I am looking to Mounts2SD, but anything would do!) but none really helped me.
Has anybody managed to use adittional sd-card partitions to expand internal memory? Any hint?
Click to expand...
Click to collapse
I don't know what you want to do. But if you mean making 2 partition on sd and moving apps to sd then. Make sure that your second partition is also primary and ext-4 file system then use an app like link2sd(app2sd) to create link.
vinay said:
I don't know what you want to do. But if you mean making 2 partition on sd and moving apps to sd then. Make sure that your second partition is also primary and ext-4 file system then use an app like link2sd(app2sd) to create link.
Click to expand...
Click to collapse
Main goal: bypass internal storage limitation.
I am an old-school linux guy and would rather mount than link. By mounting it is done one time only and it works for all, while by linking, well, you (or the app) have to manage dozens of links, new links for every new app, very bad. So I'd like to use Mounts2SD instead of any linking app.
I partitioned my 16GB SD card as (all primary):
8GB: fat32
6GB: ext[2,3,4]
2GB: reserved for a future /cache or swap
I assume that with such partition scheme and a /sd-ext folder on device M2SD would do the mount -t ext2 /dev/block/mmcblk1p2 /sd-ext automagically, but no.
So far I was able to mount -o remount,rw / && mkdir /sd-ext and do this mount by hand, but on reboot it erases /sd-ext and nothing happens.
Would it be safe to ditch those apps and simply edit /etc/fstab and manually copy things instead?
OR: how to keep /sd-ext after a reboot? Why does it vanishes? Why? Why?
Thanks for you prompt response, best regards.
mmerlone said:
Main goal: bypass internal storage limitation.
I am an old-school linux guy and would rather mount than link. By mounting it is done one time only and it works for all, while by linking, well, you (or the app) have to manage dozens of links, new links for every new app, very bad. So I'd like to use Mounts2SD instead of any linking app.
I partitioned my 16GB SD card as (all primary):
8GB: fat32
6GB: ext[2,3,4]
2GB: reserved for a future /cache or swap
I assume that with such partition scheme and a /sd-ext folder on device M2SD would do the mount -t ext2 /dev/block/mmcblk1p2 /sd-ext automagically, but no.
So far I was able to mount -o remount,rw / && mkdir /sd-ext and do this mount by hand, but on reboot it erases /sd-ext and nothing happens.
Would it be safe to ditch those apps and simply edit /etc/fstab and manually copy things instead?
OR: how to keep /sd-ext after a reboot? Why does it vanishes? Why? Why?
Thanks for you prompt response, best regards.
Click to expand...
Click to collapse
Make second partition ext-4 not 2-3 cause your device won't support it. And etc/fstab is unless i opened that file it doesn't contain link to internal sd.
Sent From My Sony Xperia E3 D2212 using XDA app.
Sent From My Sony Xperia E3 D2212 using XDA app.
mmerlone said:
Main goal: bypass internal storage limitation.
I am an old-school linux guy and would rather mount than link. By mounting it is done one time only and it works for all, while by linking, well, you (or the app) have to manage dozens of links, new links for every new app, very bad. So I'd like to use Mounts2SD instead of any linking app.
I partitioned my 16GB SD card as (all primary):
8GB: fat32
6GB: ext[2,3,4]
2GB: reserved for a future /cache or swap
I assume that with such partition scheme and a /sd-ext folder on device M2SD would do the mount -t ext2 /dev/block/mmcblk1p2 /sd-ext automagically, but no.
So far I was able to mount -o remount,rw / && mkdir /sd-ext and do this mount by hand, but on reboot it erases /sd-ext and nothing happens.
Would it be safe to ditch those apps and simply edit /etc/fstab and manually copy things instead?
OR: how to keep /sd-ext after a reboot? Why does it vanishes? Why? Why?
Thanks for you prompt response, best regards.
Click to expand...
Click to collapse
The only possible explanation to that lies in the ramdisk. I think you should edit the fstab because I remember seeing mount_all command in ramdisk pointing to the fstab.
In 4.4.4 kitkat you can only do this via ramdisc modifications no any other way. Don't waste time on /system and others.
Sent From My Sony Xperia E3 D2212 using XDA app.
vinay said:
In 4.4.4 kitkat you can only do this via ramdisc modifications no any other way. Don't waste time on /system and others.
Sent From My Sony Xperia E3 D2212 using XDA app.
Click to expand...
Click to collapse
I have no idea about what you are talking about and its implications (altough I know about ramdisk on linux, I dont know what that means and where its data came from on android). Any litterature to enlighten me?
mmerlone said:
I have no idea about what you are talking about and its implications (altough I know about ramdisk on linux, I dont know what that means and where its data came from on android). Any litterature to enlighten me?
Click to expand...
Click to collapse
Ramdisc is packed in boot.img with kernel.
Sent From My Sony Xperia E3 D2212 using XDA app.
vinay said:
Ramdisc is packed in boot.img with kernel.
Sent From My Sony Xperia E3 D2212 using XDA app.
Click to expand...
Click to collapse
Is there how to alter ramdisk on boot.img to create /sd-ext?
BTW, any RTFM about this booting process on Android or are those particularities vendor-dependent?
mmerlone said:
Is there how to alter ramdisk on boot.img to create /sd-ext?
BTW, any RTFM about this booting process on Android or are those particularities vendor-dependent?
Click to expand...
Click to collapse
I spend 10 to 20 min modding ramdisk then i packed it. And booted i found that my externel sd was unmounted. That,s all i got. I can,t do any more.
So i am sure there must be a was to swap sd in ramdisk.
Sent From My Sony Xperia E3 dual using XDA app.
vinay said:
I spend 10 to 20 min modding ramdisk then i packed it. And booted i found that my externel sd was unmounted. That,s all i got. I can,t do any more.
So i am sure there must be a was to swap sd in ramdisk.
Sent From My Sony Xperia E3 dual using XDA app.
Click to expand...
Click to collapse
I have attached files from ramdisk below.
these are files which contain,s information about mounting.
You can use text editor to edit them.
Tell me if you found some thing use full
vinay said:
I have attached files from ramdisk below.
these are files which contain,s information about mounting.
You can use text editor to edit them.
Tell me if you found some thing use full
Click to expand...
Click to collapse
only fstab.qcom and init.qcom.rc for editing
angiras said:
only fstab.qcom and init.qcom.rc for editing
Click to expand...
Click to collapse
These are only files that contain mount point,s.
Sent From My Sony Xperia E3 dual using XDA app.
vinay said:
These are only files that contain mount point,s.
Sent From My Sony Xperia E3 dual using XDA app.
Click to expand...
Click to collapse
Yes, some time ago i editing fstab.qcom and init.qcom.rc and change internal to external memory, but have bug after unpluging from PC :
in tree of device not found SDcard , but after wipe dalvic , it work OK under next connect to PC . it is problem of framework to mount point of SDcard
find my post on 4pda.ru , because i not have privelege to give access to page
angiras said:
Yes, some time ago i editing fstab.qcom and init.qcom.rc and change internal to external memory, but have bug after unpluging from PC :
in tree of device not found SDcard , but after wipe dalvic , it work OK under next connect to PC . it is problem of framework to mount point of SDcard
find my post on 4pda.ru , because i not have privelege to give access to page
Click to expand...
Click to collapse
It is harrd to find in a website which is not even in english.
Can,t tell me what didi you did.
Did you changed sdcard1 to 0 in fstab.qcom.
And in init.qcom.rc changed smlink or export link.
Sent From My Sony Xperia E3 dual using XDA app.
Hi!
This is a light version from the tutorial described below.
It create a full root WITH option to send your apps to sd card automatically!
How?
Because it create a funtional init.d folder in system/etc where you can put your own scripts to start on boot, giving you full control from your ROM/phone and if you have a ext4 partition in sd card ( 3 GB that's enough ), it will send your apps to sd card releasing storage.
LTE device have a default 2GB /data storage for apps and user definitions, phone call, etc. 3G device is worse!!!
So for a LTE device, 3GB from sd partition + 2GB from data partition = 5GB!
To show you why don´t need more, i have at this momente 61 app in /data/app ( in sd ext4 partition ) that fill 750MB - > 61 apps!!!
If you have a LTE device and your /data partiton is resized you can push a litle the size from external partition to 4GB ( that's enough ), im still trying to find a good size for external partition.
Why don´t need a bigger size?
Because there are file that still inside data partition, in /data/data and dalvik-cache, that still filling up data partition... you can´t take them all ...
3G devices need to be rooted with SuperSu zip first ( i don´t know way ) ... im a LTE user.
UPDATE-Kinguser-3.4.0-Modded_V2.zip
https://mega.nz/#!HoZniaSC
Key:
!tmmKUs-lnmAJo0Y4rcvxgZjYgsath0iTDBUYa7-T3YE
And this video shows how ROM works with a external ext4 partition in sd card what means that all apps go to sd card and let internal storage free:
https://youtu.be/7st6838_aAg
Use it only if you need it. Is your option.
I hope this helps you.
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
<<<<<<<The END of low storage>>>>>
I test it in L11 with B370 kit kat factory ROM. From 0.
!!!!Attencion!!!! 3G device users, read pinned post, you need to install SuperSU.zip first than this KingUser.zip to root OR WILL FAIL!!!!
In the step when you will install kinguser.zip change for this one, see the default tutorial here: https://www.facebook.com/groups/huawei.g6.development/permalink/578005512358705/
You need a primary external ext4 partition in sd card with the size you think you need for apps.
To create a primary ext4 partition in sd card with the size you want, you can use mini partition tool (for windows OS ).
http://www.partitionwizard.com/free-partition-manager.html
Need bootloader Unlocked:
https://www.facebook.com/groups/huawei.g6.development/permalink/504332286392695/
Need a custom recovery, i use TWRP for my L11, U models use more CWM, you can find it in G6SKnife.
Must have Windows OS to use G6SKnife:
https://www.facebook.com/groups/huawei.g6.development/permalink/577809609044962/
Than i modded this Kinguser flash zip that:
-Roots
-create a working init.d folder where you can store your scripts that will be executed on boot
-it will install busybox apk ( it need it to install some system tools )
- Rashr to change recoverys with the phone ( only need to have the images in sd card )
- It will automatically send all apps to your external ext4 partiton in sd card IF you have one!!!!
How to do it!!!!??????
READ IT CARFULL:
If you already have apps in phone do backup, use the phone default app for that.
Copy this zip to sd card:
UPDATE-Kinguser-3.4.0-Modded.zip
https://mega.nz/#!rhRknYDJ
Key:
!tnT9KAYOOcuSNm9eq7AcW_PHc2p-C4wjvssNI4IHAMU
Turn off and go to recovery ( TWRP or CWM ) by pressing at same time vol + and power.
Do a factory reset.
Go to install and search the UPDATE-Kinguser-3.4.0-Modded.zip and install it. The phone will reboot.
( A) After settings go to KingUser and open it to check if is ok than go back, open busybox, give root permissions, it will take some time seraching for old files than install it!!!!
( you will need this tools )
Reboot, and is done.
If you start from flash is the same process.
Now your apps go all to sd card.
This video show a flash of B370 and the root with this KingUser.zip:
https://youtu.be/CcFdbS20RrY
persona78 said:
#!/system/bin/sh
# apk to sd card
mount -t ext4 -o rw /dev/block/vold/179:66 /data/app
mount -t ext4 -o rw /dev/block/mmcblk1p2 /data/app
chown system system /data/app
# apk lib to sd card
mount -t ext4 -o rw /dev/block/vold/179:66 /data/app-lib
mount -t ext4 -o rw /dev/block/mmcblk1p2 /data/app-lib
chown system system /data/app-lib
chmod 773 /data/dalvik-cache
Click to expand...
Click to collapse
How is it possible to make the same source folder diferent and multiple target folder mount script?!! I think ther must be an error on this...
The first mount lines are pointing to /data/app and in the other lines pointing again to /data/app-lib?
its possible!
pestevao said:
How is it possible to make the same source folder diferent and multiple target folder mount script?!! I think ther must be an error on this...
The first mount lines are pointing to /data/app and in the other lines pointing again to /data/app-lib?
Click to expand...
Click to collapse
It's possible because works like a symlink. Imagine a room with several doors.
The mmcblk1p2 is the room, the /data/app , /data/app-lib are the doors.
Is working perfectly in my device. No lags.
http://postimg.org/image/8lc3of5pd/
http://postimg.org/image/jjnd6luap/
See this video, it have this script
pestevao said:
How is it possible to make the same source folder diferent and multiple target folder mount script?!! I think ther must be an error on this...
The first mount lines are pointing to /data/app and in the other lines pointing again to /data/app-lib?
Click to expand...
Click to collapse
This video shows how my ROM version works with a external ext4 partition in sd card what means that all apps go to sd card and let internal storage free:
https://youtu.be/7st6838_aAg
Hi!
I create a easy way, go here:
http://forum.xda-developers.com/ascend-g6/general/root-upadtekinguser-zip-modded-extras-t3349679
I've instaled the B370 and use Link2SD that have already bought. And it works perfectly and smooth!
With the original ROM / Android it displays a warning that mount must be done after a quick reboot but now everything is working on a normal reboot.
Used KingRoot 3.4.o modified to include /etc/init.d folder creation to Link2SD be able to write mount scripts and with the Huawei B370 cleans everything from Vodafone P that came hacked and pre-installed
Now is better than ever!
pestevao said:
I've instaled the B370 and use Link2SD that have already bought. And it works perfectly and smooth!
With the original ROM / Android it displays a warning that mount must be done after a quick reboot but now everything is working on a normal reboot.
Used KingRoot 3.4.o modified to include /etc/init.d folder creation to Link2SD be able to write mount scripts and with the Huawei B370 cleans everything from Vodafone P that came hacked and pre-installed
Now is better than ever!
Click to expand...
Click to collapse
With this option you don't need link2sd
http://forum.xda-developers.com/ascend-g6/general/root-upadtekinguser-zip-modded-extras-t3349679
Yeah you are maybe right. But when I make it with Link2SD I doesn't find yout tutorial (and even doesn't exists on xda forum) so right now is everything working there no reason to move away from Link2SD
This is how have my phone using a 64 GB SDCARD
pestevao said:
Yeah you are maybe right. But when I make it with Link2SD I doesn't find yout tutorial (and even doesn't exists on xda forum) so right now is everything working there no reason to move away from Link2SD
Click to expand...
Click to collapse
Hi!
I buy a 64 GB sd card, create 3 ext4 partitions and mounted like this:
So, now I have 24GB ext4 for data, 10GB ext4 storage and 27GB fat32 for external storage... For mt G6-L11. I had before resized data storage to 4GB.
By default is 2/3 , I can't remember.
Hi!
Main post is Update!
persona78 said:
Hi!
Main post is Update!
Click to expand...
Click to collapse
Great job congratulations!